CA 7: How to add batch terminals?

Products

• CA 7 Workload Automation

Issue/Introduction

This document explains how to add batch terminals to CA 7.  Batch terminals are used by program SASSBSTR (also known as the Batch Terminal Interface (BTI)) to execute CA 7 commands and provide the output from processing the commands in SYSPRINT. Up to 8 batch terminals can be defined and used in CA 7.

 

 

Environment

Release:
Component: 7

Resolution

If you have fewer than 8 batch terminals defined, you may want to increase the number available for command processing in CA 7. To define a new batch terminal, you will need to:

1. Allocate a BATCHIN data set. (NOTE: Best practices for the naming convention for batch terminal data sets is to use the same high-level qualifier as the UCC7CMDS file (Communications Data Set) and the suffix BATCHI#n (where n is the associated batch terminal number).) Following are the DCB attributes for the BATCHIN data set:

         DCB=(RECFM=FB,LRECL=80,BLKSIZE=80   x   n)

          NOTE:n is a user-defined value. 

The BATCHIN data set has to have enough space to hold all commands entered as SYSIN in the SASSBSTR program. Usually 5 tracks is sufficient. 
NOTE: The block size on the input data set must match BUFSIZE on the LINE statement in the initialization file.

2. Allocate a BATCHOUT data set (same NOTE as above for naming conventions, except the suffix BATCHO#N is used). Following are the DCB attributes for the BATCHOUT data set:

         DCB=(RECFM=VB,LRECL=137,BLKSIZE=137   x  n + 4)

          NOTE:n is a user-defined value. 

The BATCHOUT data set should be allocated large enough to hold the output from the commands that are processed. Best practices says to have at least one batch terminal with the BATCHOUT data set very large to hold all the output from a global RESOLV or generic job listing in CA 7 (this will vary by site). If the BATCHOUT data set is not large enough to hold all the output from the commands entered, you will receive a BSTR-17 message. This file should be no smaller than 10 cylinders. 

3. Add DDs in the CA7ONL procedure with the DD names of BTERM0nI and BTERM0nO (with n being the number of this batch terminal) as such: 
   //BTERM0nI DD DISP=SHR,DSN=high.level.qualifier.of.commds.BATCHI#n 
   //BTERM0nO DD DISP=SHR,DSN=high.level.qualifier.of.commds.BATCHO#n

 

4. Add GROUP, LINE, TERM and STATIONS statements for the new batch terminal in the CA 7 Initialization File (pointed to by the UCC7IN DD statement in the CA 7 online procedure). It is important to note that the 'number' of the batch terminal used in the BTI procedure will be based on the position of that terminal in the CA 7 Initialization File. In other words, if you had: 
   (NOTE: The following examples use BLKSIZE=3120 for the allocation of the BATCHIN data sets) 

        GROUP,NAME=BTERM02,DEVICE=BATCH,LNAME=BLINE2
        LINE,NAME=BLINE2,BUFSIZE=3120,TNAME=BTERM2

        TERM,NAME=BTERM2,DEVICE=BATCH,NLINE=60,LINLEN=137
        GROUP,NAME=BTERM01,DEVICE=BATCH,LNAME=BLINE1

        LINE,NAME=BLINE1,BUFSIZE=3120,TNAME=BTERM1

        TERM,NAME=BTERM1,DEVICE=BATCH,NLINE=60,LINLEN=137

5. The PARM of 1 in the BTI execution would not produce the results needed--it is best to be sure you keep the batch terminals in numeric order in the Initialization File. 
   Also, be sure to have the GROUP name match the DD name minus the I or O. For example: 

         GROUP,NAME=BTERM0n,DEVICE=BATCH,LNAME=BLINEn

         (where n is the number for this batch terminal) 

6. Shutdown CA 7 and do a specified ERST type start: 

         S  CA7ONL,TYPE=ERST

If you use dynamic BTI management, you may also need to change the POOL= keyword on the PARM for the BTI procedure if you want to have this batch terminal included in the available pool.