CONNECT PROCESS
Initiate an APPC mapped conversation.
Description
CONNECT PROCESS allows an application to specify a process name and synchronization level to be passed to CICS® and used when the remote partner is attached.
Options
- CONVID(name)
- identifies
the conversation to which the command relates. The 4-character name
specifies the token returned by a previously executed ALLOCATE command
in EIBRSRCE in the EIB.
For compatibility with earlier releases, SESSION is accepted as a synonym for CONVID. New programs should use CONVID.
- PARTNER(name)
- specifies the name (8 characters) of a set of definitions that includes the name (or extended name) of a remote partner transaction (TPNAME or XTPNAME). You can use this option as an alternative to PROCNAME and PROCLENGTH.
- PIPLENGTH(data-value)
- specifies the total length (halfword binary value) of the specified process initialization parameter (PIP) list.
- PIPLIST(data-area)
- specifies the PIP data to be sent to the remote system. The PIP list consists of variable-length records, each containing a single PIP. A PIP starts with a 2-byte inclusive length field (LL), followed by a 2-byte reserved field, and then the parameter data.
- PROCLENGTH(data-value)
- specifies the length (as a halfword binary value in the range 1–64) of the name specified by the PROCNAME option.
- PROCNAME(data-area)
- specifies
the partner process (that is, the transaction) to be attached in the remote system.
One byte is sufficient to identify a CICS transaction. The APPC architecture allows a range of 1–64 bytes but leaves each product free to set its own maximum. CICS complies by allowing a range of 1–64 bytes. If the remote system is CICS, this option can specify the 4-byte transaction identifier or the TPNAME value given in the relevant TRANSACTION definition. Alternatively, you can examine the full identifier by coding the user exit XZCATT.
No character checking is performed on the TPN by CICS.
For programming information about the user exit XZCATT, see CICS statistics record format .
- SESSION(name)
- specifies the symbolic identifier (1–4 characters) of a session TCTTE. This option specifies the alternate facility to be used.
- STATE(cvda)
- gets
the state of the current conversation. The cvda values returned by CICS are:
- ALLOCATED
- CONFFREE
- CONFRECEIVE
- CONFSEND
- FREE
- PENDFREE
- PENDRECEIVE
- RECEIVE
- ROLLBACK
- SEND
- SYNCFREE
- SYNCRECEIVE
- SYNCSEND
- SYNCLEVEL(data-value)
- specifies
the synchronization level (halfword binary value) for the current
conversation. The possible values are:
- 0 None
- 1 Confirm
- 2 Syncpoint
Conditions
- 16 INVREQ
- RESP2
values:
- 200
- A distributed program link server application specified the function-shipping session (its principal facility) on the CONVID option.
also occurs (RESP2 not set) in any of the following situations:- A synchronization level other than 0, 1, or 2, has been requested in the SYNCLEVEL option.
- The command is not valid for the terminal or LU in use.
- The command has been used on a conversation that is in use by CPI-Communications or that is an APPC basic conversation. In the latter case, GDS CONNECT PROCESS should have been used.
Default action: terminate the task abnormally.
- 22 LENGERR
- occurs
in any of the following situations:
- An out-of-range value is supplied in the PROCLENGTH option.
- The value specified in the PIPLENGTH option is less than 0.
- The value specified in the PIPLENGTH option exceeds the CICS implementation limit of 32 763.
- A PIPLIST length element (LL) has a value less than 4.
- The sum of the length elements (LLs) in the PIPLIST does not equal the value specified by PIPLENGTH.
Default action: terminate the task abnormally.
- 61 NOTALLOC
- occurs
if the specified CONVID value does not relate to a conversation owned
by the application.
Default action: terminate the task abnormally.
- 97 PARTNERIDERR
- occurs
if the name specified in the PARTNER option is not recognized by CICS.
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) can cause this condition if the task has an outstanding terminal control request active when the node abnormal condition program handles the session error.
Default action: terminate the task abnormally with abend code ATNI.