Save S/36 File (SAVS36F)

Where allowed to run: All environments (*ALL)
Threadsafe: No

The Save System/36 File (SAVS36F) command can create:

a copy of a single database physical file or logical file to diskette, tape magnetic media or another database physical file in the same format as if a System/36 has saved the file.
a copy of multiple database physical files or logical files to diskette or tape magnetic media in the same format as if a System/36 had saved the files as a save all set. The files can be all files in a library, all files that are not part of a file group, all files in a specific file group, or all files that begin with a specified set of characters.

A Save All Set is a group (set) of files that share the same group (set) name and that are saved (copied) to diskette or tape with one operation. The set of files can be restored (copied back from diskette or tape) with a single operation by referring to the set name (see the Restore System/36 Files (RSTS36F) command).

File groups are defined by file names that contain a period. The characters preceding the period identify the file group, and the characters following the period identify the file within the group. As with file names within the System/36 environment, the maximum number of characters is eight, including the period. Files with names that do not contain a period are not part of a file group. The following examples show the names of files within a file group.

    PAYROL.A
    PAYROL.B    Files in File Group PAYROL
    PAYROL.C
    A.ACCTS
    A.INV
    A.PROL      Files in File Group A
    A.B.GO
    A.B.INV
    A.B.GO
    A.B.INV     Files in File Group A.B

The saved files can be restored to the following systems:

System/36 (RESTORE procedure or $COPY utility)
i5/OS (Restore System/36 File (RSTS36F) command)

The SAVS36F command is intended for exchanging files with a System/36. For creating a backup version of a file, the i5/OS save commands (for example, Save Object (SAVOBJ) or Save Changed Object (SAVCHGOBJ)) should be used.

Restrictions:

The following authorities are required (normally only applies when running on a system using resource security):
- *USE authority for this command.
- *USE authority for the file or group of files specified in the FROMFILE parameter.
- *USE authority for the library specified in the FROMLIB parameter.
- *CHANGE authority to the file specified on the PHYFILE parameter if saving to an existing physical file.
- *USE authority for the library specified in the PHYFILE parameter if saving to a physical file.
- *CHANGE authority for the library specified in the PHYFILE parameter if saving to a physical file and the file does not exist.
- *USE authority for the diskette device description object, *USE authority for device file QSYSDKT, in library QSYS if saving to diskette.
- *USE authority for the tape device description object, *USE authority for device file QSYSTAP, in library QSYS if saving to tape.
- *USE authority for the based-on physical file if saving a logical file.
All diskettes that are used for the save operation should be initialized using the INZDKT CL command or the equivalent System/36 environment function (INIT operator control language (OCL) procedure or $INIT SSP utility). For a two-sided diskette, use a sector size of 256 or 1024. For a one-sided diskette, use a sector size of 128 or 512. If tape is used, each tape volume used should have been initialized with standard labels using the INZTAP CL command or the equivalent System/36 environment function (TAPEINIT OCL procedure or $TINIT SSP utility). Use a density of 1600 bits per inch when initializing the tape.
Note: If the tape or diskette has not been initialized as stated above, the System/36 will not be able to process the media.
Object-level and record-level functions, other than read operations, should not be attempted for a file being saved by SAVS36F. Concurrent activity against the file (for example, moving the file or adding or removing records) can cause:
- For a save operation of a single file (FROMFILE(file-name)), the save operation will end with escape message CPF9826 because the file cannot be allocated.
- For a save operation of multiple files (FROMFILE(*ALL or generic*-file-name)), the save function sends an inquiry message CPA2C6A because the file cannot be allocated. The message allows an ignore, retry and cancel response. The ignore response bypasses this file and attempts to save the next file selected.
When saving a single file to diskette, the diskette cannot already contain an active file with the same label and creation date as the new file to be created.
When saving multiple files to diskette, the diskette used for the save cannot contain any active files.
Not all physical and logical files can be saved with the SAVS36F command.
- Only logical files created under the System/36 environment (for example, through the BLDINDEX OCL procedure) or through a DDM request from a System/36 system can be saved. These files are saved as System/36 alternative index files.
- All physical files created under the System/36 environment (for example, through the BLDFILE OCL procedure) or through a DDM request from a System/36 system are saved using information stored within the i5/OS file description. These files are saved as System/36 sequential, direct, or indexed physical files.
- Any physical files created by i5/OS commands or utilities can be saved as long as the record length is not greater than 4096. These files are saved as System/36 sequential files.
To generate a save format which can be processed by the System/36 RESTORE procedure, the following information is not saved:
- If saving a logical file, only the description of the file is saved. The index (or access path) is not saved.
- If saving an indexed (keyed) physical file, the data is saved but the index is not. The index will be rebuilt after the file is restored.
The following restrictions apply to naming standards:
- When saving a single file, the specified name (FROMFILE parameter) must meet naming standards. If not, message CPF0001 is sent when the SAVS36F command is processed.
- If a file name is found during a save operation of multiple files (FROMFILE(*ALL or generic*-file-name)) that does not meet the System/36 naming standards, diagnostic message CPF2C0E is sent and the file is not saved.
Multiple files (FROMFILE(*ALL) or FROMFILE(generic*-name)) cannot be saved to a physical file.

Keyword	Description	Choices	Notes
FROMFILE	From file	Generic name, name, *ALL	Required, Positional 1
FROMLIB	From library	Name	Required, Positional 2
DEV	Device	Single values: *PHYFILE Other values (up to 4 repetitions): Name	Required, Positional 3
GROUP	File group qualifier	Character value, ALL, NONE	Optional
SET	Set identifier	Character value, #SAVE	Optional
TOLABEL	File label	Character value	Optional
SEQNBR	Sequence number	1-9999, *END	Optional
VOL	Volume identifier	Values (up to 50 repetitions): Character value, *MOUNTED	Optional
RETAIN	Retention period	0-999, 1	Optional
ENDOPT	End of tape option	REWIND, LEAVE, *UNLOAD	Optional
DTACPR	Data compression	YES, NO	Optional
PHYFILE	Physical file	Qualified object name	Optional
	Qualifier 1: Physical file	Name
	Qualifier 2: Library	Name, LIBL, CURLIB
MBROPT	Data base member option	NOREPLACE, REPLACE	Optional
CRTDATE	Creation date	Date, LAST, ALL	Optional

Save S/36 File (SAVS36F)

Parameters

From file (FROMFILE)

From library (FROMLIB)

Device (DEV)

File group qualifier (GROUP)

Set identifier (SET)

File label (TOLABEL)

Sequence number (SEQNBR)

Volume identifier (VOL)

Retention period (RETAIN)

End of tape option (ENDOPT)

Data compression (DTACPR)

Physical file (PHYFILE)

Data base member option (MBROPT)

Creation date (CRTDATE)

Examples

Example 1: Saving a Single File

Example 2: Saving a Single File

Example 3: Saving Multiple Files

Example 4: Saving Multiple Files

Example 5: Saving Multiple Files

Example 6: Saving Multiple Files

Error messages