Simulator request initiation fields

A description of the fields that are available when you start the Simulator.

The program is DFHMASP1, which is indicated at the top of the screen. The field descriptions are as follows:
INITIATE VIA:
X(01). Choose the method by which you will initiate the IVP. Valid values include:
  • D = Initiate the IVP through a DPL.
  • M = Initiate the IVP through the WebSphere® MQ-CICS bridge.
Identifies the queue on which the service requestor sends an adapter request message. This causes WebSphere MQ to send a trigger message to the initiation queue as defined. The WebSphere MQ trigger monitor program starts the CICS® bridge monitor task, part of the WebSphere MQ-CICS bridge.
SYSID:
9(4). For DPL initialization only.

If the simulator is installed in the same region as the CICS Service Flow Runtime server run-time, leave this field blank.

If the simulator is not installed in the same region as the CICS Service Flow Runtime server run-time, type in the SYSID of the CICS Service Flow Runtime server run-time.

REQUEST QUEUE:
X(48). Identifies the queue on which the service requestor sends an adapter request message. This causes WebSphere MQ to send a trigger message to the initiation queue as defined. The WebSphere MQ trigger monitor program starts the CICS bridge monitor task, part of the WebSphere MQ-CICS bridge.
REQUEST NAME:
X(8). The request name indicates the name of the request to process. The value specified is used to read the CICS Service Flow Runtime Properties file to determine processing flow and parameters.
TYPE:
X(1). Indicates the processing mode. Valid entries are:
  • 0 = request processing will be run asynchronously. For requests that will be updating information when adapter request processing runs in asynchronous mode, syncpoints are taken while the Navigation Manager, Navigator and server adapters complete their processing. These synchronization points provide the necessary state, status and journaling information in the event of subsequent failure. This information can in turn be used in a compensation flow.
  • 1 = This type must be used unless modifications have been made to DFHMAID3 to change the request type on TYPE=R RECORD. A 1 indicates that the request processing will be run synchronously. For requests that will be making inquiries only (i.e., the request will not result in information being updated).
  • 2 = request processing will include rollback processing. Synchronous Rollback is a processing mode where the CICS Service Flow Runtime BTS process and all activities run within the process are initiated and run in synchronous mode (i.e., BTS RUN ACQPROCESS SYNCHRONOUS and RUN ACTIVITY( ) SYNCHRONOUS commands), however, any failure within any activity within the process results in an abend of the process. This has the effect of returning the state of any and all recoverable resources updated during adapter request processing to its original state, that is, the state prior to the execution of the failed adapter request or process.
PROCESSTYPE:
X(8). This field indicates the type of the new CICS Service Flow Runtime process instance.
FAIL PROCTYPE:
X(8). For Asynchronous mode (type 0) only. If the request fails, this field is populated with the failed process type. You can cancel the failed process by selecting (7) CANCEL REQUEST, or if the request has a compensating flow associated with it, you can select (6) COMP. REQUEST to invoke compensation. This field is also populated for informational purposes only when the process fails in synchronous mode. For detailed information on compensation, see How compensation processing works. Also, see DFHMAH field definitions for information on DFHMAH-UOWCONTROL.
FAIL PROCNAME:
X(36). For Asynchronous mode (type 0) only. If the request fails, this field is populated with the failed process name. You can cancel the failed process by selecting (7) CANCEL REQUEST, or if the request has a compensating flow associated with it, you can select (6) COMP. REQUEST to invoke compensation. This field is also populated for informational purposes only when the process fails in synchronous mode. For detailed information on compensation, see How compensation processing works. Also, see DFHMAH field definitions for information on DFHMAH-UOWCONTROL.
REPLY QMODEL:
X(48). Name of the model reply queue.
DYNAMIC QNAME:
X(48). Prefix used for the name of the Reply Queue when dynamically built.
WAIT INTERVAL:
9(4). Identifies how long the Simulator waits for a response. The default value is 30 seconds.
USERID:
X(8). Valid CICS UserID. This is used for authentication in WebSphere MQ-CICS bridge and to allocate a PassTicket in the FEPI server adapter.