The parsed replication Engine script, VSMTOVSM will run on the z/OS platform. In this case JCL similar to sample member SQDATA (SQDAMAST as a started task) included in the distribution can be edited to conform to the operating environment, including the necessary Public / Private key files.
//SQDATA JOB 1,MSGLEVEL=(1,1),MSGCLASS=H,NOTIFY=&SYSUID
//*
//*--------------------------------------------------------------------
//* Execute the Connect CDC SQData Engine standalone in Batch
//*--------------------------------------------------------------------
//* Note: 1) This Job may require specification of the Public/Private
//* Key pair in order to connect to a Capture/Publisher
//* running on another platform
//*
//* 2) To run the SQDATA Engine as a started task, refer to
//* member SQDAMAST
//*
//* Required DDNAME:
//* SQDFILE DD - File that contains the Parsed Engine Script
//*
//*********************************************************************
//*
//JOBLIB DD DISP=SHR,DSN=SQDATA.V400.LOADLIB
//*
//SQDATA EXEC PGM=SQDATA,REGION=0M
//SQDPUBL DD DISP=SHR,DSN=SQDATA.NACL.PUBLIC
//SQDPKEY DD DISP=SHR,DSN=SQDATA.NACL.PRIVATE
//SYSPRINT DD SYSOUT=*
//SQDLOG DD SYSOUT=*
//*SQDLOG DD DUMMY
//CEEDUMP DD SYSOUT=*
//*
//*---- PARSED ENGINE SCRIPT FILE ----
//SQDFILE DD DISP=SHR,DSN=SQDATA.V400.SQDOBJ(VSMTOVSM)Note: The Controller Daemon (both Capture and Engine) uses a Public / Private key mechanism to ensure component communications are valid and secure. While it is critical to use unique key pairs when communicating between platforms, it is common to use the same key pair for components running together on the same platform. Consequently, the key pair used by an Engine may be the same pair used by its Controller Daemon.