CICS front end

When CICS is the front-end system, you can use CICS START and RETRIEVE commands to process IMS nonresponse mode and nonconversational transactions, message switches, and the IMS /DIS, /RDIS, and /FOR operator commands.

Note: When you issue the IMS /DIS, /RDIS, and /FOR operator commands, unless you send change direction (CD), IMS expects you to request definite response. You must do this by coding the PROTECT option on the START command.

The general command sequence for your application program is shown in Figure 1.

After transaction TRANA has obtained an input message from the terminal, it issues a START NOCHECK command to initiate the remote IMS transaction. The START command specifies the name of the IMS editor that is to be initiated to process the message, and the IMS transaction or logical terminal (LTERM) that is to receive the message. It also specifies the name of the CICS transaction that is to receive the reply, and the name of the associated CICS terminal.

The PROTECT option must be specified on the START command to ensure delivery of the message to IMS.

The start request is not shipped until your application program either issues a SYNCPOINT command, or terminates. However, the request does not carry the syncpoint-indicator unless PROTECT was specified on the START command.
Figure 1. START and RETRIEVE asynchronous processing–CICS front end
A CICS region and an IMS region are joined by an LUTYPE61 link. A transaction, TRANA, obtains some terminal input, then issues an EXEC CICS START NOCHECK PROTECT request to initiate a remote transaction on the IMS region. When TRANA issues a SYNCPOINT or RETURN command, CICS ships the start request to IMS. When the remote IMS transaction has completed its processing, IMS sends the reply to CICS by issuing a START request which specifies TRANB and the terminal named in the first START command. On CICS, TRANB is started. It retrieves the reply by issuing an EXEC CICS RETRIEVE command.

Although CICS allows an application program to issue multiple START NOCHECK commands without intervening syncpoints (see Deferred transmission of START requests with NOCHECK option for ISC links ), this technique is not recommended for CICS-to-IMS communication.

IMS sends the reply by issuing a start request that is handled in the normal way by the CICS mirror transaction. The request specifies the CICS transaction and terminal that you named in the original START command. The transaction that is started (TRANB) can then retrieve the reply by issuing a RETRIEVE command.

In the example, it is assumed that there are two separate CICS transactions; one to issue the START command and one to receive the reply and return it to the terminal. These two transactions can be combined, and there are two ways to do this:
  • Write a transaction that contains both the START and the RETRIEVE processing, but that performs only one of these functions for a specific execution. The CICS ASSIGN STARTCODE command can be used to determine whether the transaction was initiated from the terminal, in which case the START processing is required, or by a start request, in which case the RETRIEVE processing is required.
  • Write a transaction that, having issued the START command, issues a SYNCPOINT command to clear the start request, and then waits for the reply by issuing a RETRIEVE command with the WAIT option. The terminal is held by the transaction during this time, and CICS returns control to the transaction when input directed to the same transaction and terminal is received.

In all cases, make no assumptions about the timing of the reply, or its relationship to a specific previous request. A RETRIEVE command retrieves any outstanding data intended for the same transaction and terminal. Correlation of requests and replies is the responsibility of your application program.



dfht1c00202.html | Timestamp icon Last updated: Monday, 5 June 2017