Batch Processing › SARBCH Control Statements › ADDJOB

ADDJOB

The ADDJOB control statement creates control records that let users use JOB mode to access reports that were archived before JOB mode existed.

• If the sysout dataset list contains 5 or fewer DD statements, the job records are created automatically.
• If the sysout dataset list contains more than 5 DD statements and resides on tape, load the sysout index to disk before you enter the ADDJOB command. Statements are generated in the CTLCARDS DD to load the sysout index to disk.
• JOB mode records are created only for jobs that contain reports that were processed by SARSTC, SARFSS text collector, SARXTD, or SARDBB.
• JOB mode records are not created for jobs that contain binary, AFP, PDF, Xerox, or CA Deliver reports.
• Some older database report control records may not contain dataset list information. These reports are not eligible for JOB mode processing and are bypassed.
• Running ADDJOB creates index records, which requires sufficient free space in the CA View database. For example, adding 100,000 jobs via ADDJOB requires approximately 36,000 data blocks (400 cylinders) free in the master index.

  Carefully monitor your database index utilization by using SARDBASE STATUS or the online ST command.

  Important! If your database index fills up while ADDJOB is running, the job terminates with RC=16. In addition to the job terminating, these events occur:

  • The following message appears:

    SARDBI07 No more index file space in database
    

  • Other archiving tasks (for example, SARSTC, SARFSS, and archival from CA Deliver) are interrupted.

  To avoid filling your index, consider using the ADDJOB parameters, including wildcard characters, to limit the number of jobs in a run.

  If necessary, use SARDBASE ADDDS to add additional space to your database index and data areas.

• Depending on the number of reports being scanned and the number of job records being created, ADDJOB may take a long time to complete and may generate a high amount of I/O’s.

  Running ADDJOB with no parameters creates JOB mode records for all eligible reports on the database.

  Omitting the ID parameter causes ADDJOB to read through all of the report index records in the database.

  For large databases, consider running ADDJOB in off hours when it does not conflict with online activity or backup cycle processing.

  /ADDJOB    JOBNAME=jobname
             DATE=mm/dd/yyyy | mm/dd/yyyy:mm/dd/yyyy
             GEN=number
             SEQ=number
             ID=id
             REDO
  

where:

JOBNAME=jobname

Specifies the 1-8 character job name.

To specify a generic job name, specify the jobname prefix, followed by an asterisk, for example, pay* or bld*.

DATE=mm/dd/yyyy | mm/dd/yyyy:mm/dd/yyyy

Specifies either the date or the range of dates when the job was submitted.

In a date range, use a colon (:) to separate the start and end dates.

Gen=number

Specifies the generation number (1-65535) for the sysout.

Seq=number

Specifies the sequence number (1-65535) for the sysout.

ID=id

Specifies the specific or generic sysout id (1 to 32 characters).

Default: blank (all sysouts)

REDO

Re-creates the JOB mode data.

Note: If you version a database back to CA View 12.1 or earlier, the JOB mode data is removed. If you version the same database up to CA View 12.2 or later again, to re-add JOB mode data, use the REDO command.