The Create Save File (CRTSAVF) command creates a save file.
A save file can be used with save and restore commands to contain data that would otherwise be written to tape or optical media. A save file can also be used like a database file to read or write records that contain save or restore information. A save file can also be used to send objects to another user on the Systems Network Architecture distribution services (SNADS) network.
Restrictions:
An online save file should only be used for save/restore data. When restoring objects from the save file, the data in the file must have been produced by a save command. When records are written to a save file by using a high-level language program, the records must contain data produced by saving objects into the save file.
The records retrieved from a save file contain sequencing checksum information that is validated by the system when records are inserted into a save file. An attempt to insert records that are either out of sequence or have been changed since retrieval from a save file are rejected.
A save file can contain the output of only one save operation and one library, and all objects in the save file must have been saved from the same library. If the Send Network File (SNDNETF) command is used to send a save file, the maximum size of the save file is approximately 2 billion bytes. The number of objects saved in a save file is identical to the number of objects saved when saving to tape or optical media, as long as the file's maximum size is not exceeded. The exact number of objects saved into a save file depends on the object types and the object contents.
You must have object operational (*OBJOPR) authority to the CRTSAVF command in order to create a duplicate save file object or to restore a save file object.
You must have add (*ADD) and read (*READ) authority to the library in which the save file is to be created.
If the file is used in a high-level language program, the file name must be consistent with the naming rules of that language. Otherwise, the file must be renamed in the program.
This is a required parameter.
Qualifier 1: Save file
name
Specify the name of the save file to be created.
Qualifier 2: Library
*CURLIB
The current library for the job is used to locate the save file. If no library is specified as the current library for the job, QGPL is used.
name
Specify the library where the save file is located.
Specifies the maximum number of records the save file can contain. The number of bytes of space in the save file is estimated at 8192 + (512 x the number of records in the save file). There is room for approximately two thousand 512-byte records in 1 megabyte of space. If you wanted to ensure that the save file would not exceed approximately 20 megabytes you would specify 40000 records (20 megabytes x 2000 records/megabyte).
Note: The maximum amount of data that a save file can contain is approximately 2 terabytes. A message appears when the file is full.
*NOMAX
The maximum value of 4293525600 records is used.
1-4293525600
Specify the maximum number of records the save file can contain.
Specifies the number of seconds that the program waits for the file resources to be allocated when the file is opened, or the device or session resources to be allocated when an acquire operation is performed to the file. If the file resources cannot be allocated in the specified wait time, an error message is sent to the program.
*IMMED
The program does not wait. Immediate allocation of file resources is required.
*CLS
The job default wait time is used as the wait time for the file resources to be allocated.
1-32767
Specify the number of seconds to wait for file resources to be allocated.
Specifies whether the open data path (ODP) is shared with other programs in the same routing step. When an ODP is shared, the programs accessing the file share facilities such as the file status and the buffer.
*NO
The ODP is not shared with other programs in the routing step. A new ODP for the file is created and used every time a program opens the file.
*YES
The same ODP is shared with each program in the job that also specifies *YES when it opens the file.
Specifies the authority you are giving to users who do not have specific authority for the object, who are not on an authorization list, and whose group profile or supplemental group profiles do not have specific authority for the object.
*EXCLUDE
The user cannot access the object.
*ALL
The user can perform all operations except those limited to the owner or controlled by authorization list management (*AUTLMGT) authority. The user can control the object's existence, specify the security for the object, change the object, and perform basic functions on the object. The user also can change ownership of the object.
*CHANGE
The user can perform all operations on the object except those limited to the owner or controlled by object existence (*OBJEXIST) and object management (*OBJMGT) authorities. The user can change and perform basic functions on the object. *CHANGE authority provides object operational (*OBJOPR) authority and all data authority. If the object is an authorization list, the user cannot add, change, or remove users.
*LIBCRTAUT
The system determines the authority for the object by using the value specified for the Create authority (CRTAUT) parameter on the Create Library command (CRTLIB) for the library containing the object to be created. If the value specified for the CRTAUT parameter is changed, the new value will not affect any existing objects.
*USE
The user can perform basic operations on the object, such as running a program or reading a file. The user cannot change the object. Use (*USE) authority provides object operational (*OBJOPR), read (*READ), and execute (*EXECUTE) authorities.
name
Specify the name of an authorization list. Users included on the authorization list are granted authority to the object as specified by the list. The authorization list must exist when the object is created.
This command creates an online save file named ONLINE in the current library. The save file is in the system ASP with no maximum number of records. The public has no authority to this file; only the object owner and users that have the object owner user profile as their group profile can use this save file.