GDS CONNECT PROCESS

Initiate an APPC basic conversation (assembler-language and C programs only).

GDS CONNECT PROCESS (APPC basic)

Read syntax diagramSkip visual syntax diagramGDS CONNECT PROCESSCONVID( name)PROCNAME( name)PROCLENGTH( data-value)PARTNER( name)PIPLIST( data-area)PIPLENGTH( data-value)SYNCLEVEL( data-value)CONVDATA( data-area)RETCODE( data-area)STATE( cvda)

 

Description

EXEC CICS® conditions are never raised on GDS commands.

The return code is given in RETCODE (see Table 1). For a list of return code values, see the Return codes for APPC basic conversations. EXEC CICS conditions are never raised on GDS commands.

GDS CONNECT PROCESS allows the application program to specify a partner application that is to run in the remote system.

Options

In general, the arguments can be replaced by absolute or relocatable assembler-language expressions.

CONVDATA(data-area)
specifies the 24-byte application data area into which conversation-related information is to be moved. A description of the format of the data area is given in the discussion of CONVDATA fields in the Testing indicators .
CONVID(name)
identifies the conversation to which the command relates. The 4-character name identifies either the token returned by a previously executed GDS ALLOCATE command, or the token representing the principal session (returned by a previously executed GDS ASSIGN command).
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 of the process initialization parameter (PIP) list specified on a CONNECT PROCESS command.
PIPLIST(data-area)
specifies the PIP data that is to be sent to the remote process.
PROCLENGTH(data-value)
specifies the length (as a halfword binary value in the range 1–64) of the target process name.
PROCNAME(name)
specifies the name of the remote application. The APPC architecture allows names of lengths (1–64 bytes), but leaves each product free to set its own maximum. If the remote system is CICS, you can use the standard 4-character transaction ID. You can also use the TPNAME value in the transaction definition.
RETCODE(data-area)
specifies the 6-byte application data area into which return code information (shown in Table 1) is to be moved.
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) intended for the current conversation. The possible values are:
  • 0 None
  • 1 Confirm
  • 2 Syncpoint
Table 1. GDS CONNECT PROCESS return codes
RETCODE (hexadecimal) Description
02 0C 00 PARTNER is not known.
03 00 CONVID is for a session that is not APPC.
03 00 CONVID is for a session that is in use by CPI Communications.
03 04 CONVID is for a conversation that is not basic.
03 0C The SYNCLEVEL option specifies a value other than 0, 1, or 2.
03 0C The SYNCLEVEL option requested either 1 or 2, but it was unavailable.
03 08 A state check occurred.
04 CONVID is for a session that is not allocated to the task, or that is a relay link.
05 00 00 00 00 20 PROCLENGTH is outside the range 1–64.
05 00 00 00 7F FF The PIPLENGTH value is outside the range 4–763.
05 00 00 00 7F FF The 2-byte length field (LL) for one of the PIPs is less than 4.
05 00 00 00 7F FF The total of the LLs in PIP data is greater than the PIPLENGTH value.