----------------------
-- APPLY ENGINE
----------------------- NAME =DB2TODB2 -- JOBNAME (ENGINE) IN SCRIPT
- PGM =SQDATA
- AUTOSTART =Y
- NEWADDRSP =N
- SCRIPT =SQDATA.V400.SQDOBJ(DB2TODB2)
- QUEUE =DB2TODB2@SHM -- JOBNAME (ENGINE) IN SCRIPT @SHM
NAME
Only Apply Engines can run as subtask in the Master's address space and it recommended that the NAME be the same as the JOBNAME in the Apply Engine script. While not recommended by Precisely, the SQDaemon listener, Db2/z Log Capture, IMS Log Capture and the zLogc Publisher can run as started tasks in a NEWADDRSP=Y under the Master where the NAME is the started task PROC in your system PROCLIB.
PGM
Valid program names for the Agent being executed under the Master include:
- Daemon - program SQDAEMON
- DB2 Capture - program SQDDB2C
- IMS Log Capture - program SQDIMSC
- zLOGC Publisher - program SQDZLOGC
- General Apply Engine - program SQDATA
- IMS Apply Engine - program SQDATAI
Note, Precisely recommends using the Master Controller only when implementing large numbers of Apply Engines on z/OS.
AUTOSTART
Specifies whether the Agent should automatically start when the Master starts.
Valid values are:
Y - autostart
N - do not autostart
NEWADDRSP
Specifies whether or not an Agent should run as a started task in a separate address space.
Valid values are:
Y - run the Agent as a started task
N - run the Agent as a subtask under the Master
The following Agents must run as started task (NEWADDRSP=Y):
Daemon - program SQDAEMON
DB2 Capture - program SQDDB2C
IMS Log Capture - program SQDIMSC
zLOGC Publisher - program SQDZLOGC
The following Agents can run as a subtask in the Master's address space (NEWADDRSP=N):
General Apply Engine - program SQDATA
IMS Apply Engine - program SQDATAI
SCRIPT
Specifies the name of the parsed/compiled Apply Engine script used only by Apply Engine agents.
For example, if a parsed engine script named ENGINE1 is in library CDC.SQDOBJ, you will set the SCRIPT parm as follows:
SCRIPT='CDC.SQDOBJ(ENGINE1)'
- The Apply Engine library/member name must be enclosed in single quotes.
- SCRIPT= should be specified for all other Agent types
QUEUE | CABFL
Specifies the method of communication and the object required to communicate with a particular Agent. Generally, QUEUE is used for Apply Engines and the Daemon, while CABFL is used for Capture and Publisher Agents. The two parameters are Synonyms that can be used interchangeably.
The following lists the Agent types and their required QUEUE|CABFL= values.
Apply Engine: QUEUE=<engine_name>@SHM
Where:
<engine_name> is the name of the engine as specified in the JOBNAME keyword in the engine script.
@SHM - required and indicates that communication will be through a shared memory area
Daemon - QUEUE=<host_name> -s <port_number>
Where:
<host_name> is the name of the host that the daemon resides on
-s <port_number> is the port number that the Daemon is listening on
DB2 Capture: CABFL=<cab_file_name>
Where:
<cab_file_name> is the fully qualified directory/file name of the CAB file for the DB2 Capture Agent
IMS Log Capture: CABFL=<cab_file_name>
Where:
<cab_file_name> is the fully qualified directory/file name of the CAB file for the IMS Log Capture Agent
zLOGC Publisher: CABFL=<cab_file_name>
Where:
<cab_file_name> is the fully qualified directory/file name of the CAB file for the IMS/VSAM Publisher