Defining the decollation mission

After running your production jobs with a dedicated MSGCLASS, order a generic decollation mission for the dedicated MSGCLASS output class. The generic decollation mission creates a cumulative CDAM file that contains the output of all the jobs that satisfy the decollation mission’s criteria. Each job has a single report entry for same-day viewing and tracking.

The following sample generic mission for JOB archiving is supplied as member JOBARC in the Control-D REPORTS library:

Figure 66 Job Archiving Decollation Mission Example

CATEGORY JOBARCHIVE JOBNAME * GENERIC Y MONITOR 1

===========================================================================

DEF COPIES LVL USER DEST MAX COPIES

===========================================================================

ON CLASS = R EXTWTR DEST FORM

PRT COPIES LVL USER DEST MAX COPIES

PRINT/CDAM PARMS = ALLOCOPT=JOBSDSN1

PRINT/CDAM PARMS =

DO

WHEN LINE - COL - PRINT REF NXT CT AND/OR

STRING =

DO NAME = %%JOBNAME(1,8)

DO USER = USERARC LVL LINE COL -

S A T B SYNONYM = CONCAT =

DO INDEX = JOBNAME_DDNAMES R G

DO REMARK = *+CC LINE 00004 COL 00073 - 00077

DO MIGRATE = JOBARC

DO

WHEN LINE - COL - PRINT REF NXT CT AND/OR

The following table provides guidelines for setting various parameters in the Job Archiving decollation mission:

Table 173 Guidelines for parameters in the Job Archiving decollation mission

Parameter and value	Description and guidelines
JOBNAME=*	The JOBNAME=* specification in the sample mission selects all output in Sysout class R. You can use this parameter to select the output based on job categories. For example, if you want only financial jobs, you can specify JOBNAME=FIN* (assuming that FIN is your prefix for financial jobs).
GENERIC=Y	Sets the decollation mission as generic.
CLASS	Ensure that the specified class (R in the example above) is defined as a generic Sysout class in CTDPARM.
PRINT/CDAM PARMS = ALLOCOPT=JOBSDSN1	Combines all Sysout gathered by this mission into one CDAM file.
DO NAME= %%JOBNAME(1,8)	Sets the report name to the first eight characters of the job name for each report.
DO USER=USERARC	Assigns the resulting reports to a user defined in the Recipient Tree to have access to these reports. If you create different generic missions for different categories of output (as described above for the JOBNAME parameter, or by using different Sysout classes), user assignment can be varied as well, to provide the relevant permissions to access the Sysout.
DO INDEX= JOBNAME_DDNAMES	Creates a special index structure that consists of a primary index named JOBNAME and a sub-index named DDNAMES. The primary index has a single value comprised of fixed-length fields separated by blanks, as listed in the next table below.
DO REMARK = *+CC LINE 004 COL 073 – 077	Identifies the position of the SMF ID that occurs in the MSGCLASS output and may need to be adjusted for your installation. CC refers to the highest Condition Code of the job. In this example, the values specified for LINE and COL capture the SMF ID in the JES2 message $HASP373.
DO MIGRATE = JOBARC	Ensures that these reports are not deleted before consolidation occurs. It is not interpreted as a migration mission name.

Table 173a JOBNAME Index value fields

Field Name	Description	Length
JOBNAME	Name of the job	8
JOBID	ID of the job. Format depends on JES definitions; either JOBn..n, where n..n is the job number containing 5 digits or Jn..n, where n..n is the job number containing 7 digits.	8
SMFID	SMF ID of the system in which the job ran	4
COMP‑CODE	Completion code of the job	5
DATE	Date of the job in the format DDMMYY	6
START‑TIME	Start time of the job in the format HHMM	4
END‑TIME	End time of the job in the format HHMM	4

For example:

Job PJOB1234 ran on system ZOS1 on December 12, 2012, starting at 1:17 PM , ending at 2:32 PM. It was assigned job number 8356 and completed with a condition code of 8. In this instance, the primary index would appear as follows:

PJOB1234 J0008356 ZOS1 C0008 121212 1317 1432

Parent Topic

Job Archiving