DFHZXRL module

Input to routine ZXRL_COMMANDS in DFHZXRL is the application command in the form of a DFHLUC macro call parameter list.
  1. ZXRL_COMMANDS normally wraps up the command to be shipped and relevant TCTTE fields by calling a transformer routine in DFHXTP.
    However, if the first syncpoint flow has been received, then:
    • Application requests ISSUE-ERROR and ISSUE-ABEND are sent unwrapped on the link session.
    • All other requests are rejected with a state error.
  2. ZXRL_COMMANDS tests the state of its link with the terminal-owning region (this may not be the same as the state of the application):

    If it finds that it is in ‘RECEIVE’ state, it issues a DFHTC TYPE=(READ,WAIT) in order to receive the change direction (CD) indicator from the terminal-owning region. Except during syncpoint processing, however, the session is normally in ‘SEND’ state when a command is issued.

  3. ZXRL_COMMANDS then sends the wrapped-up request to the remote system using the DFHTC macro. To reduce the number of flows when the command may result in the termination of the conversation, the following rules are applied for both MRO and ISC links:
    • If the application command is SEND LAST WAIT and the application program is in ‘SEND’ state, the command is sent using a DFHTC TYPE=(WRITE,LAST) macro.
    • If the application command is WAIT and the application program is in ‘FREE PENDING AFTER SEND LAST’ state, the command is sent using a DFHTC TYPE=(WRITE,LAST) macro.
    • If the end bracket (EB) indicator has been sent to the terminal-owning region all other commands result in a state error return code.

    In other cases and when the link between the terminal-owning region and application-owning region is MRO, ZXRL_COMMANDS issues a DFHTC TYPE=(WRITE,WAIT,READ).

    However, when the link is LU6.2, the following additional rules are applied in order to exploit the buffering provided by LU6.2:
    • When the application’s command is a SEND and the application is in ‘SEND’ state ZXRL_COMMANDS, issues a DFHTC TYPE=(WRITE,WAIT) macro to send the request without waiting for a response.
    • When the application’s command is a SEND and the application is not in ‘SEND’ state ZXRL_COMMANDS, issues a DFHTC TYPE=(WRITE,WAIT,READ) so that it can get the state error back from the remote system immediately.
    • For all other commands, including SEND INVITE and so on, ZXRL_COMMANDS issues a DFHTC TYPE=(WRITE,WAIT,READ).
  4. ZXRL_COMMANDS receives the response to its DFHTC macro call. This may be:
    • An ATNI or ATND abend. ZXRL_COMMANDS frees the link session and returns ‘TERMERR’ to the application.
    • ‘SIGNAL’, which is used by the terminal-owning region when it is in ‘RECEIVE’ state to indicate to the application-owning region that there is an abnormal response pending.

      ZXRL_COMMANDS issues a DFHTC TYPE=(WRITE,WAIT,READ) to send the change direction indicator and get the abnormal response from the terminal-owning region.

  5. When the DFHTC macro included a READ, and the request was succesfully processed, ZXRL_COMMANDS checks for a wrapped reply from the terminal-owning region, and calls DFHXTP to unwrap the reply. When the resulting DFHLUC parameter list indicates SYNCPOINT or SYNCPOINT ROLLBACK, and the link is an MRO connection, ZXRL_COMMANDS issues a DFHTC TYPE=READ, because there is a SYNCPOINT or ROLLBACK flow pending.

    When there is no wrapped reply, ZXRL_COMMANDS checks for SYNCPOINT ROLLBACK received (the only possibility under these circumstances).



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