USING KSAMUTIL IN BATCH MODE

A batch job can be developed on the text editor (EDITOR) and then executed with the MPE :STREAM command. In order to distinguish the MPE commands within a streamed batch job from those external to the job, an exclamation point (!) is used as the command prefix rather than a colon (:). KSAMUTIL commands have no command prefix when executed in a batch job.

In the job illustrated in Figure 2-1 EDITOR Listing of Job to be Streamed, the first step after job initialization with the !JOB command is to purge all KSAM and non-KSAM files that will be created within the job. This insures that there are no files in the account with names duplicating files that will be created programmatically with the job.

Following initialization, the first program in the job is run. Since this program uses a KSAM file, MANPN, this file is created with the KSAMUTIL BUILD command before the program is executed. Note that the program is purged immediately before calling BUILD to create it. This is done to make sure that no duplicate key or data file exists in the account.

The newly created KSAM file is used in program MAN1, which was previously compiled and is input from the file CARDIN; output from the program goes to the file REPORT associated with the line printer. An !EOD command follows the program. If data is entered here rather than from the input file, then the !EOD follows the data. Any other programs in the job stream follow the !EOD each with its own terminating !EOD. The entire job is terminated by an !EOJ command.

Figure 2-1 EDITOR Listing of Job to be Streamed is an EDITOR listing of a job entered to a file through the EDITOR program. This job could also have been punched on cards or any other device that accepts jobs, but in that case, the standard command prefix, the colon (:), would be used. (Refer to the EDIT/3000 Reference Manual for instructions on using the EDITOR.)

In order to run this job, you can enter the command:

   :STREAM filename 

where filename identifies the EDITOR file where the job was saved.

Batch jobs need not be streamed, but can be entered entirely as a card deck or through some other input device. Streaming allows you to develop and execute the job interactively at your terminal. For a full discussion of using the :STREAM command to introduce jobs in a session, refer to the MPE Commands Reference Manual.

Batch jobs do not support the OFFLINE parameter for the KEYDUMP, KEYINFO, KEYSEQ, and VERIFY commands.

Figure 2-1 EDITOR Listing of Job to be Streamed