|
Files and Job Variables created by CFS
File lists saved by the user with the command SL mn, or saved by CFS itself. These file lists can be displayed again with the command RL [mn]. The #CFS.SAVELIST. prefix can be amended by the system administrator.
#Zelement If a library element is marked with the Action Code D (Display), CFS will create a temporary file with the specified name. After the Display mode has been terminated, the temporary file will be erased.
#file If a file is erased with the Action Code E, and if the ERT option (Erase with Retain of Tempfiles) is set, then this file will be recataloged by CFS to a temporary file with the name #file. If a library element is erased with E, CFS will create a temporary library called #library, and will transfer the element to this library before deleting it from the original library.
The temporary file created by CFS will be erased automatically at /LOGOFF.
$TSOS.CFSCOM This file will be created under $TSOS by CFS when it is loaded for the first time. It will be cataloged with a read password, and be made shareable. Enhancement requests and fault reports in relation to CFS are deposited in this file by the user through the MES command.
CFS.COMPLIST.tsn.yymmdd.hhmmss
Protocol produced when comparing two files or library elements (COMP command).
CFS.DO.ARCHIVE.tsn
DO procedure created by an ONXARCHIVE Variable Action. This DO procedure can be started in dialog, or as an Enter job. If this procedure is run as an Enter job, CFS will create an additional Enter file called CFS.ENT.ARCHIVE.tsn.
CFS.DO.tsn.hhmmss
A procedure created by the ONXDO Variable Action, in which the CALL to the main procedure contains the file names as parameters. This created procedure cannot be erased by CFS automatically. Deleting DO procedures with this naming convention is the responsibility of the user.
CFS.E.tsn.hhmmss Enter file created by the Job Report System if a DO procedure is started as an Enter job. These files will normally be erased automatically by CFS at the end of the job.
CFS.EDTSAV [.jobname].tsn.yymmdd.hhmm.x
In the event of an STXIT ABEND condition, for example in the event of the loss of a line connection, CFS will check if the user has processed a file or library element with an EDT, EDF or EDL Action Code. If so, all utilised EDT levels at the point at which the ABEND occured will be saved automatically to the above-named backup file.
x: Number between 0 and 9, indicating the EDT level.
If a name was specified in the LOGON command, this will appear in the name of the EDTSAVE file created.
CFS.HARDCOPY.jobname.yymmdd.hhmm.tsn
Hardcopy file created by an HC command from the main CFS task, into which all screens can be captured in formatted form. If no file name is specified with the HC command, the standard name as described above will be used.
CFS.JR.SYSOUT.tsn.hhmmss | CFS.JR.SYSLST.tsn.hhmmss
SYSOUT/SYSLST file created by the Job Report System when a DO procedure is started in Enter mode with an E command. This file will be erased by CFS at the end of the job if the user acknowledges the SYSOUT listing with an E (End) command, or by pressing the K1 key.
CFS.JR.xxxxx.yymmdd.hhmmss
Monitor Job Variable created by the Job Report System for the Enter job to be monitored. This Job variable will be erased by CFS automatically after the job has finished, and after the user has acknowledged the SYSOUT listing with an E (end) command, or by pressing the K1 key. The portion xxxxx represents the Job Report Identification under which the Enter job was started. For further information, see page 11-.
CFS.J2.xxxxx.yymmdd.hhmmss
Job Variable created by the Job Report System on the occurence of a /REMARK JRIC command in the procedure file. This Job variable will be erased by CFS automatically after the job has finished, and after the user has acknowledged the SYSOUT listing with an E (END) command, or by pressing the K1 key. The portion xxxxx represents the Job Report Identification under which the Enter job was started. For further information, see page 11-.
CFS.JRSAVE.... Catalog created by the Job Report System in which the procedure parameter assignments saved with an SP %name command are stored, as well as Search statements saved with an SP %name command. The same file will be accessed in the event of an E %name, DO %name or S,%name command. The exact name of the JRSAVE file to be used is determined as follows:
a) Has the user issued a /FILE ... ,LINK=JRSAVE command?
b) Does a file named CFS.JRSAVE exist?
c) Was a job name specified by the user in the LOGON command, and does a file named CFS.JRSAVE.jobname exist?
d) If no Job name was specified, and the conditions a) to c) are not fulfilled, then the JRSAVE file will be called CFS.JRSAVE.acct-#.
The first condition to be met will determine the name of the JRSAVE file. The name of the standard JRSAVE file can be changed by the user by modifying a CFS internal table. For further information, see page 18-.
The user can also specifiy the name of the JRSAVE file directly in the SP, E, DO, or S commands by combining it with the %name option as follows: %name, jrsave.
CFS.LOG.yymmdd.hhmm.tsn
Logging file created by CFS when a LOG command is entered. The LOG file will contain input/output messages for a Connection, and will always be created in the CFS main task. The standard name will be used if the command is entered as LOG STD.
CFS.MEM.STD. .... The contents of the internal CFS Command Memory will be saved to a file with this name if an SM (Save Memory) command is entered. If no file name is entered in the SM command, the file will be named CFS.MEM.STD.jobname. jobname is the job name specified in the LOGON command. If no job name was specified, the file will be named CFS.MEM.STD.acct (acct: Account number of the userid).