The following examples show different applications of the test
mode using the NDMPXTBL parameter table to define which Connect:Direct® Processes
to run and not run.
Specify
Which Processes Run
In this example,
Connect:Direct executes
all Processes that start with ACH or are named DITEST01 or DITEST02.
All other Processes are placed in the Hold queue.
* Enable processing. Only permit processes matching one of the patterns
* to execute. Hold processes that don't execute.
EH
I
PACH*
PDITEST01
PDITEST02
L
|
Specify
Which Processes to Exclude
In this example,
Connect:Direct does not
execute any Process that starts with ACH or is named DITEST01 or DITEST02.
All other Processes are executed.
* Exclude matching processes. Permit all others to execute.
EH
X
PACH*
PDITEST01
PDITEST02
L
|
Permit
Process Execution by Secondary Node and Submitter User ID/Node
In
this example,
Connect:Direct executes
all Processes that match one of the following criteria:
- The specific secondary node (SNODE) name is DI.NODE1
- An SNODE whose name starts with DI0017
- Any Connect:Direct submitter
ID from node DI0049
- The specific Connect:Direct submitter
ID SACHAPP from any node
All Processes not matching one of the
above criteria are flushed from the queue.
* Only permit matching processes to execute. Flush those that do not.
EF
I
NDI.NODE1
NDI0017*
S*@DI0049
SACHAPP@*
L
|
Stop
the Test Mode
In this example, no Processes will not be
executed, and a non-zero return code will be displayed, which signifies
an error along with message ID LPRX003E. The remainder of the table
is ignored (including the “F” code to flush Processes from the queue),
and all Processes are placed in the Hold queue.
To resume testing,
change the “D” command code to an “E.”
* Execute no processes at all. Put them in the hold queue and return.
DF
I
PACH*
PDITEST01
PDITEST02
L
|