Sample Test Scenarios
The following examples show different applications of the test mode using the NDMPXTBL parameter table to define which IBM® Connect:Direct® Processes to run and not run.
Specifying Which Processes Run
In this example, IBM Connect:Direct executes all Processes that start with ACH or are named DITEST01 or DITEST02. All other Processes are placed in the Hold queue.
|
Specifying Which Processes to Exclude
In this example, IBM Connect:Direct does not execute any Process that starts with ACH or is named DITEST01 or DITEST02. All other Processes are executed.
|
Permitting Process Execution by Secondary Node and Submitter User ID/Node
In this example, IBM 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 IBM Connect:Direct submitter ID from node DI0049
- The specific IBM Connect:Direct submitter ID ACHAPP from any node
All Processes not matching one of the above criteria are flushed from the queue.
|
Stopping the Test Mode
In this example, no Processes will 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.”
|