Batch applications which require Com-plete services use ACCESS to communicate with the target Com-plete system. As the mechanism used to communicate with the Com-plete region is the Adabas router mechanism, this method of batch support can take advantage of the networking features provided by the Adabas router mechanism.
As each server Com-plete signs on to the router with a different data base ID (which is also unique within the network), several Com-plete regions can offer batch support, allowing a distribution of the batch workload between multiple address spaces.
For further information on how to install ACCESS, see the description of the ACCESS interface. For further information on how to install Natural Batch, see the description of the Natural interface.
Batch applications must be linked to the module COMPBTCH supplied on the Com-plete load library, which contains entry points for all Com-plete functions allowed from a batch environment.
COMPBTCH loads modules TUBATCH and TUBCONN to perform the required function. These load modules must therefore be contained in the STEPLIB concatenation of the batch job.
To issue the Adabas call to access Com-plete, a vanilla ADALNK must be also available in the STEPLIB concatenation of the batch job.
On the first call, TUBATCH will attempt to establish communication with the target Com-plete. To do this, TUBATCH requires two pieces of information: the NODEID of the target node and the SVC number of the Network Router (Adabas SVC) on which this node is established.
This information can be obtained in one of the following ways:
ACSTAB.
TUBATCH attempts to load a table ACSTAB
and, if found, will search this for the entry named BATCH, the values for
NODEID and SVC are then taken from this entry.
A sample ACSTAB is
delivered on the Com-plete source dataset. This member must be modified to suit
the installation requirements, assembled and linked to an appropriate data set
during installation of Com-plete. This library can then be included in the
STEPLIB concatenation of batch jobs.
COMBTCH JCL statement.
In addition to the above
procedure, TUBATCH will always attempt to find the NODEID and SVC from JCL DD
card COMBTCH.
COMBTCH DD DSN=NODEnnnn.SVCsss,DISP=....... or: COMBTCH DD DSN=NODnnnnn.SVCsss,DISP=.......
The values obtained will overwrite the values contained in the ACSTAB to allow individual jobs to override values specified in the ACSTAB.
Note:
The value of NODEID in the ACSTAB may be 1 - 65535. To
allow for 5-digit values, NODnnnnn is also supported
a combination of both. This method allows you to define multiple Com-pletes in one ACSTAB. You define ACSTAB entries using any names you like (e.g., jobname or installation ID or whatever) instead of or along with the "BATCH" entry. To select an entry, use a COMBTCH DD statement like this:
COMBTCH DD DSN=[any_prefix.]TARGET.target[.any_suffix],DISP=...
where target is the entry name associated with the COMPLETE you want the BATCH job to connect to. If this notation is used and NODEnnnn and/or SVCsss are also specified, then the latter are ignored.
The batch interface modules supply a default user name of BATCHCOM at logon to the target system, except when the job is submitted in an environment which is protected by an external security system; in this case, the user ID under which the job is submitted (taken from the ACEE) is passed to the target system.
Note:
The target Com-plete node must be started with BATCH=YES
specified in the system parameters.