ISSUE SIGNAL (LUTYPE6.1)

Request change of direction from sending transaction on LUTYPE6.1 conversation.

Read syntax diagramSkip visual syntax diagram
ISSUE SIGNAL (LUTYPE6.1)

>>-ISSUE SIGNAL--+---------------+-----------------------------><
                 +-CONVID(name)--+   
                 '-SESSION(name)-'   

Conditions: NOTALLOC, TERMERR

 

Description

ISSUE SIGNAL, in a transaction in receive mode, signals to the sending transaction that a mode change is needed. It raises the SIGNAL condition on the next SEND, RECEIVE, or CONVERSE command executed in the sending transaction, and a previously executed HANDLE CONDITION command for this condition can be used either to take some action, or to ignore the request.

If both CONVID and SESSION are omitted, the principal facility for the task is used.

Options

CONVID(name)
identifies the conversation to which the command relates. The 4-character name identifies either the token returned by a previously executed ALLOCATE command in EIBRSRCE in the EIB, or the token representing the principal facility (returned by a previously executed ASSIGN command).
SESSION(name)
specifies the symbolic identifier (1–4 characters) of a session TCTTE. This option specifies the alternate facility to be used.

Conditions

61 NOTALLOC
occurs if the facility specified in the command is not owned by the application.

Default action: terminate the task abnormally.

81 TERMERR
occurs for a session-related error. Any action on that conversation other than a FREE causes an ATCV abend.

A CANCEL TASK request by a user node error program (NEP) may cause TERMERR if the task has an outstanding terminal control request when the node abnormal condition program handles the session error.

Default action: terminate the task abnormally with abend code ATNI.



dfhp4_issuesignallutype61.html | Timestamp icon Last updated: Thursday, 27 June 2019