• Keine Ergebnisse gefunden

SAVE - SAVE PERMANENT DATASET

Im Dokument COMPUTER SYSTEMS (Seite 155-163)

PERMANENT DATASET MANAGEMENT 9

9.6 SAVE - SAVE PERMANENT DATASET

The SAVE control statement makes a local dataset permanent and defines its associated characteristics for the system. For mass storage datasets, saving involves making entries in the system catalogs, which uniquely identify the dataset. For magnetic tape datasets, saving involves front-end servicing on the defined front-end computer system.

Under the appropriate conditions, SAVE forces any unwritten data (left in the output buffer) to be written, ensuring that all the data is made permanent. Because this situation occurs when the dataset has been

recently written but not yet rewound or closed, SAVE attempts to close the dataset. CLOSE disposes of current positioning information for that

dataset. Therefore, subsequent operations on that dataset must reopen i t and begin at the beginning of the dataset (BOD). The specific conditions that the dataset must meet are described under the SAVE macro (refer to the Macros and Opdefs Reference Manual, CRI publication SR-0012). A permanent dataset is uniquely identified by permanent dataset name (PON), additional user identification (ID), edition number (ED), and ownership value. SAVE is a system verb.

NOTE

Because COS does not identify unblocked and random datasets, these datasets must be assigned as unblocked or random (use the ASSIGN control statement) after they have been accessed.

SAVE creates an initial edition or an additional edition of a permanent dataset.

SR-0011 0 9-21

Format:

9-22

SAVE,DN=dn,PDN=pdn,ID=uid,ED=ed,RT=rt,R=rd,W=wt,M=mn,UQ,NA,ERR, ON

MSG,EXO=OFF,PAM=mode,ADN=adn(m),TA=opt,TEXT=text,NoTES=notes,

ONLINE YES

RESIDE=OFFLINE,BACKUP=NO .

DN=dn

PDN=pdn

ID=uid

Local dataset name. The name the job uses to refer to the dataset while i t remains local to the job. This dataset can be closed before the dataset is made permanent. This is a required parameter.

Permanent dataset name. The default value is

dn.

The name can be 1 to 15 alphanumeric characters.

Additional user identification. uid can be 1 to 8

alphanumeric characters assigned by the dataset creator.

The default is no user ID.

Edition number.

dataset creator.

A value from 1 through 4095 assigned by the The default value is:

• 1, if a permanent dataset with the same PDN and ID does not exist

• The current highest edition number plus one, if a permanent dataset with the same PDN and ID does exist Retention period. User-defined value from 1 through 4095 specifying the number of days a permanent dataset is to be retained by the system. The default value is an

installation-defined parameter.

Read control word; 1 to 8 alphanumeric characters assigned by the dataset creator. The read control word of the highest-numbered existing edition of a permanent dataset applies to all subsequent editions of that dataset. The default is no read control word.

Write control word; 1 to 8 alphanumeric characters assigned by the dataset creator. The write control word of the highest-numbered existing edition of a permanent dataset applies to all subsequent editions of that dataset. To obtain write permission, you must also have unique access

(UQ) to that dataset. The default is no write control word.

SR-0011 0

- - - - - - -

-I

Maintenance control word; 1 to 8 alphanumeric characters.

The maintenance control word must be specified if a

subsequent edition of the same permanent dataset is saved.

The default is no maintenance control word.

Unique access. If the UQ parameter is specified, only this job can access the permanent dataset at the completion of the SAVE function. Otherwise, multiple-user read access to the permanent dataset is granted.

No abort. If this parameter is omitted, an error causes the job to abort.

Error message. If this parameter is specified, error termination messages are suppressed.

MSG Termination message. If MSG is specified, normal termination messages are suppressed.

EXO=ON

specified, it overrides permitted and public access modes.

PAM=mode Public access mode. The following options are allowed: nullifies any other permissions specified.

If the dataset is to be used for a segmented load with SEGLDR, use PAM=R (rather than PAM=E) to enable SEGLDR to read the dataset.

Name of the attributes dataset from which attributes, indicated by the modifier

m,

are selected. If no modifiers are present, all attributes are selected.

Attribute parameters such as NOTES=, TEXT=, PAM=, R=, and so

SR-OOll 0 9-23

I

ADN=adn(m)

(continued) on, take precedence over the modifiers. adn must be the local dataset name of a permanent dataset. The modifiers must be enclosed with parentheses and separated by colons.

The following modifiers are supported:

9-24

Selection from Attributes Dataset All attributes

Control words Notes attribute

Public access mode attribute Permit list

Text attribute

Public access tracking attribute Track accesses.

opt

can be either YES or NO and

indicates whether the owner requires that public accesses to the dataset be tracked. Refer to section 6 for a all permanent dataset attributes.

NOTES=notes

explanation of all permanent dataset attributes.

ONLINE RESIDE=OFFLINE

The preferred residency of a dataset. ONLINE specifies the dataset should remain on-line. This option requires the SCRESON privilege.

OFFLINE specifies the dataset should receive priority when datasets are selected for migration. The speed with which the dataset migrates depends on factors such as how often the site runs space management. This option does not require a privilege.

SR-OOll 0

I

9.7

If RESIDE is not specified, the dataset's selection for migration is based on site-defined criteria established for space management.

YES BACKUpt=NO

Dataset backup. YES specifies the dataset should be backed up after i t is created and whenever i t is modified. NO specifies the dataset should not be backed up under any circumstance. The default is YES.

EXAMPLES OF PERMANENT DATASET CONTROL STATEMENTS

To clarify the permanent dataset management control statements, some examples follow:

Example 1:

A user identified as USERXYZ creates a permanent dataset that no other user can access. All subsequent editions of this dataset share this attribute.

SAVE,DN=ABC,PDN=EXAMPLE1,ED=1,PAM=N,TA=NO.

Example 2:

A user identified as USERXYZ creates a permanent dataset that can be accessed by all other users in read mode.

SAVE,DN=XYZ,PDN=EXAMPLE2,ED=1,PAM=R,TA=NO.

Example 3:

An alternate user is accessing the permanent dataset created in example 2.

ACCESS,DN=LOCAL,PDN=EXAMPLE2,ED=1,OWN=USERXYZ.

The system does not track the alternate user access because the dataset was created with TA=NO.

I

t Deferred implementation

SR-0011 0 9-25

Example 4:

Allow another user (known in this example as USERl) to access the permanent dataset created in example 1 in read and execute mode only.

PERMIT, PDN=EXAMPLE1,USER=USER1,AM=R: E.

Example 5:

Enable public access tracking for the permanent dataset created in example 2.

ACCESS,DN=LOCAL,PDN=EXAMPLE2,ED=l,UQ.

MODIFY,DN=LOCAL,TA=YES.

Example 6:

Permit write mode access for PDN=EXAMPLE2 to users known as USER2 and USER3.

PERMIT,PDN=EXAMPLE2,USER=USER2,AM=W.

PERMIT,PDN=EXAMPLE2,USER=USER3,AM=W.

Example 7:

Change the permission granted to USER1 in example 4 to AM=W.

PERMIT,PDN=EXAMPLEl,USER=USER1,AM=W.

Example 8:

Remove the access permission granted to USER1 in example 7.

PERMIT, PDN=EXAMPLEl,USER=USER1, RP.

Example 9:

User USERXYZ acquires a dataset, then permits another user to use it and subsequently partially deletes the dataset to retain just the PERMITs and TEXT information. Section 10 discusses the ACQUIRE control statement.

9-26

ACQUIRE,DN=EX9,TEXT=' . . . ',UQ.

PERMIT ,PDN=EX9,USER=SOMEONE,AM=R.

DELETE ,DN=EX9,PARTIAL.

SR-0011 0

Example 10:

User USERXYZ creates a permits template.

SAVE,DN=EX10,PDN=PERMS,

NOTES='PERMITS TEMPLATE FOR AERO USERS.

'THESE PERMITS SHOULD BE REMOVED AFTER OCT 31, 1983. I,UQ.

PERMIT,PDN=PERMS,USER=USERA,AM=E.

PERMIT,PDN=PERMS,USER=USERB,AM=R.

PERMIT,PDN=PERMS,USER=USERC,AM=W.

DELETE,DN=EX10,PARTIAL.

Example 11:

User SOMEONE acquires the dataset that was partially deleted in example 9. Section 10 discusses the ACQUIRE control statement.

ACQUIRE,DN=LOCAL,PDN=EX9,OWN=USERXYZ.

The TEXT need not be specified and after the dataset has been acquired from the front-end computer system, i t is made permanent and belongs to user USERXYZ.

SR-0011 0 9-27

- - -- -- - - -- -

Im Dokument COMPUTER SYSTEMS (Seite 155-163)