Have at least one set of larger batch data sets to use for commands such as RESOLV or generic listings because these commands can produce much output.
You can have up to eight batch terminal definitions. If you currently do not have eight defined, you can add batch terminals by updating the initialization file and the CA7ONL procedure. The Batch Terminal Interface (BTI) input and output data sets are pointed to in CA7ONL. Each data set has a ddname that matches the GROUP name in the initialization file. The first seven characters of these ddnames must match the initialization file GROUP statement NAME parameter. The last (eighth) character is either an I or O indicating either an input or output data set. In the initialization file, each batch terminal data set pair is defined as a batch terminal by having its own GROUP, LINE, TERM, and STATIONS statement. BTI input files are known as BATCHIN and output files as BATCHOUT. The LINE statement for each batch terminal must have the BUFSIZE keyword match the block size (BLKSIZE) of the BATCHIN file.
The PARM on the execution of SASSBSTR (program executed for BTI) determines the number of the batch terminal (and corresponding BATCHIN and BATCHOUT data sets) that are used. This number corresponds to the order of the batch terminal definitions in the initialization file. If 0 is used in the PARM, you are using dynamic allocation of the BTI terminals and BATCHIN and BATCHOUT.
Changing terminal definitions requires a specified ERST type start of CA7ONL.
Business Value:
This change results in faster processing of batch terminal input commands and fewer BATCH TERMINAL IN USE messages.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|