Effect on FEPI application programs

It is likely that FEPI application programmers have little say in the way that persistent session support is used in the back-end system.

They therefore need to be aware of the different ways in which terminal sessions can be recovered, so that their applications cater for all possibilities. The way in which a session is recovered depends on the setting of the RECOVOPTION and RECOVNOTIFY options of the TYPETERM definition.

RECOVOPTION(SYSDEFAULT)
On restart within the persistent session delay interval, CICS selects the optimum procedure to recover a session.

For LU2, if the session is busy and CICS is in send mode, CICS sends an end bracket. If the session is busy and CICS is not in send mode, CICS sends an SNA CLEAR request to reset the conversation state.

If a FEPI conversation is in progress when the target system terminates, your application could see one of the following:
  • A timeout on a RECEIVE, CONVERSE, or START command, while it waits for the target to restart.

    Deal with this in the normal way for a timeout.

  • A FEPI RECEIVE or CONVERSE command completes as a result of the end bracket sent by CICS. The RU on this data flow may be empty or may contain a user-defined message, depending on the value of the RECOVNOTIFY option.

    Your application may need to perform some backout processing.

  • An INVREQ response with a RESP2 value of 230 on a FEPI SEND, RECEIVE, CONVERSE, ISSUE, or START command, indicating that an SNA CLEAR was received.

    Your application may need to perform some backout processing.

You must also consider the value specified for RECOVNOTIFY:

RECOVNOTIFY(MESSAGE)
A message (defined in the BMS maps DFHXRC3 and DFHXRC4) is sent to the “terminal”. Your FEPI application must contain logic to deal with this data flow.

If there is no active conversation at the time of restart, the flow is received as unsolicited data at the FEPI front-end.

RECOVNOTIFY(TRANSACTION)
A transaction is initiated in the target. The default is the Good Morning transaction. Your application must contain logic to deal with this data flow.

If there is no active conversation at the time of restart, the flow is received as unsolicited data at the FEPI front-end.

RECOVNOTIFY(NONE)
The “terminal” is not notified that a restart has occurred. Your application need take no special action.
RECOVOPTION(CLEARCONV)
On restart within the persistent session delay interval, CICS sends an SNA CLEAR request to reset the conversation states. The CLEAR is sent only if the session was busy at the time of system restart. If a FEPI conversation is in progress when the target system terminates, your application could see one of the following:
  • A timeout on a RECEIVE, CONVERSE, or START command, while it waits for the target to restart.

    Deal with this in the normal way for a timeout.

  • An INVREQ response with a RESP2 value of 230 on a FEPI SEND, RECEIVE, CONVERSE, ISSUE, or START command, indicating that an SNA CLEAR was received.

    Your application may need to perform some backout processing.

You must also consider the value specified for RECOVNOTIFY. The possible values are as described for RECOVOPTION(SYSDEFAULT).

RECOVOPTION(RELEASESESS)
On restart within the persistent session delay interval, CICS sends an UNBIND request to release an active session. The request is sent only if the session was busy at the time of system restart.
If a FEPI conversation is in progress when the target system terminates, your application could see one of the following:
  • A timeout on a RECEIVE, CONVERSE, or START command, while it waits for the target CICS to restart.

    Deal with this in the normal way for a timeout.

  • An INVREQ response with a RESP2 value of 215 on any FEPI command, indicating a 'session lost' condition.

    Deal with this in the normal way for a session loss.

RECOVOPTION(UNCONDREL)
On restart within the persistent session delay interval, CICS sends an UNBIND request to release an active session. The request is sent whether or not the session was busy at the time of system restart.

If a FEPI conversation is in progress when the target system terminates, your application could see either of the symptoms described for RECOVOPTION(RELEASESESS).

RECOVOPTION(NONE)
Even if the system is restarted within the persistent session delay interval, the session is not recovered; it has no persistent session support.

Deal with this in the normal way for a session loss.



dfhp7c0066.html | Timestamp icon Last updated: Sunday, 4 June 2017