You request CONNECT:Direct services in the batch environment through the
Batch Interface program DMBATCH. When you submit a job that contains
the CONNECT:Direct commands as SYSIN input, DMBATCH reads the
input stream and processes the requested functions.
DMBATCH supports all CONNECT:Direct commands.
Your Batch Interface job must meet the following requirements:
- You can't use process statements instream. Use the SUBMIT command with
a pre-existing process that contains the process statements.
- DMBATCH processing of the SUBMIT is asynchronous; the batch job is notified of a
successful SUBMIT, but not whether the COPY itself is executed.
- The first command in the instream must be a SIGNON command.
- Each new CONNECT:Direct command must start on a seperate line. You can
split a command across more than one line using the continuation mark.
Sample job Stream to run the Batch Interface:
//DMBATCH EXEC PGM=DMBATCH,PARM='YYSLYNN'
//STEPLIB DD DISP=SHR,DSN=CD.LINKLIB
//DMPUBLIB DD DISP=SHR,DSN=CD.PROCESS
//DMMSGFIL DD DISP=SHR,DSN=CD.MSG
//DMNETMAP DD DISP=SHR,DSN=CD.NETMAP
//NDMCMDS DD SYSOUT=* <= This is optional
//DMPRINT DD SYSOUT=*
//SYSIN DD DATA
SUBMIT PROC=PROCESS MAXDELAY=UNLIMITED
CONNECT:Direct is a peer-to-peer file-based integration middleware optimized for
assured delivery, high-volume and secure data exchange between enterprises. It moves
files containing any type of data across multiple platforms, multiple file systems, and
different media types.
The major components of CONNECT:Direct OS/390 are:
- Data Transmission Facility (DTF), which executes user commands and processes.
- Application Program Interface (API), which enables user interfaces to communicate
with the DTF.
- User interfaces, such as the Interactive User Interface (IUI), browser end
user interface (EUI), the batch interface (DMBATCH), and the CICS interface.
- Transmission Control Queue (TCQ), which is a VSAM RRDS dataset that stores
processes that are executing, queued for execution, held for retry, or held
for future execution.
The CONNECT:Direct process can include many automation options. Some of the
typical ones are:
- RUN JOB. The RUN JOB statement allows a job to be submitted through the JES
Internal Reader. The job must reside in a dataset that is on the node that will
be executing the statement.
- RUN TASK. The RUN TASK statement allows a user program to be executed on the
specified node. The RUN TASK statement is designed so that the process waits until
the task completes before the next process step executes.
- sUBMIT. The SUBMIT statement allows another process to be submitted to either
For more information, please refer to the following documents:
- CONNECT:Direct OS/390 Administration Guide.
- CONNECT:Direct Process Statements Guide.
- CONNECT:Direct OS/390 User's Guide.
all of which are available for licensed customers online at http://www.stercomm.com
, under Customer Support, Support on Demand.