The RESTORE procedure restores on the disk a diskette file that was copied from the disk by one of the following:
• the ORGANIZE procedure (see index entry: ORGANIZE procedure)
• the SAVE procedure (see index entry: SA VE procedure)
• the $COPY utility (see index entry: $COPY utility program)
The RESTORE procedure can also be used to restore to the disk one or all of the entire group of files previously saved by a SAVE ALL request.
When only one file is to be restored, you can change the space allocation of the disk file by specifying the RECORDS or BLOCKS parameter in the RESTORE command statement. If the diskette file size was increased, beyond the original file capacity, the RECORDS or BLOCKS parameter must be used.
A RESTORE request reconstructs a file on the disk with the same attributes, except location (see index entry: FILE statement for a description of the LOCATION parameter), that the file had before it was copied to the diskette.
Messages to insert a tfiskette for multivolume files are automatically displaye_d as required, with appropriate label and volume-sequence-number checking.
This procedure evokes the $COPY utility (see index entry: $COPY utility program).
IBM SCP Procedure Descriptions-RENAME 94~1
This page intentionally left blank
Page of GC21-7593~3
Issued 22 Novemberr 1978 By TNL: GN21-7993
RESTORE [ALLJ, #SAVE,ddmmyy ..
[ filename~~
[mmddYYu,yymmdd
[ ::d~~y~-
dd [RECORDS, ,BLOCKS, value-2value-l~
yymm RESTOR E filename-2,
All data files previously saved are to be restored to the disk.
Name associated with the entire set of files previously saved on the diskette by the SAVE (SAVE ALL) procedure. #SAVE is the default.
Name of the single diskette file that is to be restored to the disk.
Creation date of the diskette file.
Requests that the disk file be made large enough to contain the number of records indicated by value-l.
Specifies the number of records that the disk file is to accommodate.
Requests that the disk file be made large enough to contain the number of blocks indicated by value-2.
Specifies the number of blocks that the disk file is to accommodate.
Note: When restoring a file-and there alrea~y exists a file on the fixed disk with the same name- but with a different creation date and different number of blocks or records allocated, then the B LOCKS or RECORDS parameter should be used in the RESTORE procedure.
RESTORE Examples
To restore all files previously saved by a SAVE procedure, you would enter:
RESTORE
. ~
To restore a file named JOE that was saved or organized on a diskette, you would enter:
RESTORE JOE,;RECORDS,300
In the preceding example, RECORDS requests that the restored file be large enough to contain 300 records.
IBM SCP Procedure Descriptions-RESTORE 95,
SAVE PROCEDURE
The SAVE procedure causes (1) a single disk file or all disk files to be copied to disk~tte(s) or (2) a single disk file to be added to a file saved previously on diskette(s).
Sequential, indexed, and direct disk files can be copied to diskette(s) by SAVE, and can reside on disk~tte(s) as single volume ormultivQlume files. Sequenti~l, indexed, and direct disk files can also be added to files saved previously and can reside as single volume or multivolume files. Messages to insert a diskette are given to the operator whenever a SAVE request causes a multivolume diskette file to be created or extended (added toh
This procedure evokes the $COPY utility (see index entry: $COPY utility program).
Note: If, after saving a file by copying it to diskette(s), you delete the original file from the disk, the file on the diskette(s) becomes the master copy C?f the file.
SAVE Command Statement Format
Requests that all data files on the disk be copied to diskette.
The diskette should not contain any active files.
Name of one file on the disk to be saved. The diskette file will have the same name.
Number of days (0 to 999) the diskette file is to be retained.
Default is 1.
,vol-id
Note: A retention value of 999 makes a diskette file a perman-ent file.
Single disk file is to be added to a file previously saved on diskette.
Name associated with the entire set of saved files. #SAVE is the default value.
Creation date of the disk file. If not specified, the last file created with the name given in filename-2 is saved.
Volume label of diskette~ One to six alphameric character~
RESTOR E Command Statement Format
Name associated with the entire set of files previously saved on the diskette by the SAVE (SAVE ALL) procedure. #SAVE is the default.
Name of the single diskette file that is to be restored to the disk.
Creation date of the diskette file.
Requests that the disk file be made large enough to contain the number of records indicated by value-1.
Specifies the number of records that the disk file is to accommodate.
Requests that the disk file be made large enough to contain the number of blocks indicated by value-2.
Specifies the number of blocks that the disk file is to accommodate.
Note: When restoring a file and there already exists a file on the fixed disk with the same name but with a different creation date and different number of blocks or records allocated, then the BLOCKS or RECORDS parameter should be used in the RESTORE procedure.
RESTORE Examples
To restore all files previously saved by a SAVE procedure, you would enter:
RESTORE
To restore a file named JOE that was saved or organized on a diskette, you would enter:
RESTO~E JOE"RECORDS,300
In the preceding example, RECORDS requests that the restored file be large enough to contain 300 records.
IBM SCP Procedure Descriptions-RESTORE 97
SAVE PROCEDURE
The SAVE procedure causes (1) a single disk file or all disk files to be copied to d;sk~tte(s) or (2) a single disk file to be added to a file saved previously on diskette(s).
Sequential, indexed, and direct disk files can be copied to diskette(s) by SAVE, and can reside on diskette(s) as single volume or multivolume files. Sequential, indexed, and direct disk files can also be added to files saved previously and can reside as single volume or multivolume files. Messages to insert a diskette are given to the operator whenever a SAVE request causes a multivolume diskette file to be created or extended (added to).
This procedure evokes the $COPY utility (see index entry: $COPY utility program).
Note: If, after saving a file by copying it to diskette(s), you delete the original file from the disk, the file on the diskette(s) becomes the master copy of the file.
SAVE Command Statement Format
Requests that all data files on the disk be copied to diskette.
The diskette should not contain any active files.
Name of one file on the disk to be saved. The diskette file will have the same name.
Number of days (0 to 999) the diskette file is to be retained.
Default is 1.
,vol-id
Note: A retention value of 999 makes a diskette file a perman-ent file.
Single disk file is to be added to a file previously saved on diskette.
Name associated with the entire set of saved files. #SAVE is the default value.
Creation date of the disk file. If not specified, the last file created with the name given in filename-2 is saved.
Volume label of diskette. One to six alphameric characters.
SAVE Examples
To save all files for a period of seven days on a diskette labeled 345678, you could enter:
SAVE ALL,7,#SAVE,345678 or
SAVE ,7,,345678
To save a file named JOE (created on November 12, 1914) and to add this file to an existing diskette file named JOE (with a volume identification of 654321), you could enter:
SAVE JOE,ADD,741112,654321
SET PROCEDURE
The SET procedure establishes the following system environment items:
• Number of lines printed per page
• Print belt image
• System date format
• System date
The item(s) specified is placed in the library in the system configuration record, which defines system characteristics, and remains unchanged until a subsequent SET procequre js executed.
This procedure evokes the $SETCF utility (see index entry: $SETCF utility program).
SET Command Statement Format
, [MDY]
[mmddYY]SET [value] , [source-name],
DMY
,ddmmyyYMD
,yymmddNote: Though each individual parameter is optional, at least one parameter must be specified.
IBM SCP Procedure Descriptions-SET 99
SET Parameters value
source-name
MDY
DMY
YMD mmddyy ddmmyy yymmdd
The number of lines that are to be printed per page. The maxi-mum number of lines that can be specified is 84, minimaxi-mum value is 1.
Note: See index entry: II FORMS statement for the way the value specified determines the actual number of lines printed per page.
Name of the library source member containing the print belt image to be used by the system. The contents of the source member is described in the IMAGE statement (see index entry:
IMAGE statement).
Note: BEL T48, BEL T48HN (FORTRAN), BEL T64, and BEL T96 are library source members. The source-name/parameter is either BEL T48, BELT64, BELT96, or BEL T48HN when specifying the print belt image to be used by the system.
Specifies system date format to be month-day-year.
Specifies system date format to be day-month-year.
Specifies system date format to be year-month-day.
Specifies the system date in month-day-year format.
Specifies the system date in day-month-year format.
Specifies the system date in year-month-day format.
Note: Use yymmdd format if you are creating basic data exchange format diskettes to use with other systems.
SPECIFY PROCEDURE
The SPECIFY procedure alters the following SOLC (synchronous data link control) items in the system configuration record.
Item
SO LC station address Line type
Switch type Identification data
Parameter AOOR LINE SWTYP 10
Additional SOLC items that can be altered are included in the AL TERSOL procedure.
(See index entry: AL TERSDL procedure.) To identify the current values in these parameters, use the STATUS procedure. (See index entry: STATUS procedure.) The SPECIFY procedure evokes the $SETCF utility (see index entry: $SETCF utility program).
Note: The SPECI FY procedure is intended only for data communications program-ming that use SOLC. For background information on synchronous data link con-trol, see IBM Synchronous Data Link Control General Information, GA27-3093.
For information on data communications programming, see IBM System/32 Data Communications Reference Manual, GC21-7691.
SPECI FY Command Statement Format