Previous Topic: Job Control Statements and Job File Format

Next Topic: Program Execution Section

Job Identification Section

This section identifies the ACID under whose authority the job is to be run and certain other options affecting the entire jobstream. The first statement in a job file must be a job control statement valid for the Job Identification Section. At present, this includes only the TSSJOB statement.

The format of the TSSJOB statement follows:

//TSSJOB   ACID=acid,PASSWORD=password

where “acid” denotes the CA Top Secret ACID of the user under whose authority the job is to be run, and “password” is that ACID’s password as defined on the local VM system.

Any number of blanks may separate “TSSJOB” from the following arguments.

//DD Control Card

The format of the Audit/Tracking File for Releases 1.2 and above has changed from previous releases. Since auditors are often required to have access to previously created security audit records, a method has been provided to access and report on old format Audit Files. The old format minidisk can be added to the CA Top Secret service machine at any unused virtual address. The release 1.1 file is identified to the TSSUTIL program by including a new control card, //DD, after the //TSSJOB card prior to submitting the job to the CA Top Secret server virtual machine. The syntax of the new card is as follows:

//DD AUDIT01,CUU=cuu,DSN=dsn
CUU

The address used when defining the old format minidisk to the service machine.

DSN

The data set name used for the old format audit/tracking file.

Note: You cannot produce a merged report of old and new format records using this feature. Inclusion of the //DD statement will provide you with information from a release 1.1 format file, omission of the statement provides you with information from the currently active release 1.2 format file.