What batch does:
The CA OLQ batch facility allows you to perform the same functions as command mode CA OLQ. Batch enables you to retrieve information from a CA IDMS/DB database and sequential files, and to build reports using that information. You can run the jobs offline and schedule them at times of the day when there are less demands on computer resources.
Commands you can use in batch:
CA OLQ batch supports the same set of processing commands as command mode CA OLQ except for the subset presented in Table 11.
Table 11. Commands Not Supported in CA OLQ Batch
|
Environment |
Invalid Commands |
|---|---|
|
Central version (CV CA OLQ batch) |
SHOW TABLES SHOW DESTINATIONS SUSPEND SWAP SWITCH YES/NO |
|
Local mode (Local CA OLQ batch) |
SAVE REPORT DISPLAY REPORT DELETE REPORT SHOW DIRECTORY SWAP SWITCH SUSPEND YES/NO |
How batch works:
With CA OLQ batch, you can:
Creating a command file:
A command file is a file that contains the CA OLQ commands to be executed during the batch job. You can store a command file in a sequential data set or list the commands in the job control language (JCL).
In batch, a line is the delimiter for entering commands. If a single command spans two or more lines, you must include continuation characters at the end of the continued lines to indicate to CA OLQ that the command continues on the next line. The default continuation character at system installation is the hyphen (-).
You must include a SYSIPT statement in your JCL. The SYSIPT statement defines the data set name of the file that contains the CA OLQ commands to be executed.
Executing jobs:
You can execute CA OLQ batch jobs either under the CA IDMS/DB central version or in local mode.
How to run a batch job:
There are two main steps to using the CA OLQ Batch facility:
Note: You can include the IDMSBCF statement in the JCL, but it must be run prior to the OLQBATCH job step.
To set up batch processing in CA OLQ, you:
|
Copyright © 2013 CA.
All rights reserved.
|
|