Defining the remote APPC system

A remote APPC system is defined with a CONNECTION resource.

To define a remote APPC system, create a CONNECTION resource with the following attributes:
NETNAME(name)
ACCESSMETHOD(VTAM®)
Note: VTAM is now z/OS® Communications Server.
PROTOCOL(APPC)
SINGLESESS(NO)
QUEUELIMIT(NO|0-9999)
MAXQTIME(NO|0-9999)
AUTOCONNEC(NO|YES|ALL)
SECURITYNAME(value)
ATTACHSEC(LOCAL|IDENTIFY|VERIFY|PERSISTENT|MIXIDPE)
BINDPASSWORD(password)
BINDSECURITY(YES|NO)
USEDFLTUSER(NO|YES)
PSRECOVERY(SYSDEFAULT|NONE)

You must specify ACCESSMETHOD(VTAM) and PROTOCOL(APPC) to define an APPC system. The CONNECTION name (that is, the sysidnt) and the netname have the meanings explained in Identifying remote systems (but see the box that follows).

Important:

If you are defining an APPC link to a terminal-owning region that is a member of a z/OS Communications Server generic resource group, NETNAME can specify either the TOR's generic resource name, or its applid. For advice on coding NETNAME for connections to a generic resource, see Configuring z/OS Communications Server generic resources.

Because this connection will have multiple sessions, you must specify SINGLESESS(N), or allow it to default. (The definition of single-session APPC terminals is described in Defining single-session APPC terminals.)

The AUTOCONNECT attribute specifies which of the sessions associated with the connection are to be bound when CICS is initialized. Further information is given in The AUTOCONNECT attribute.

The QUEUELIMIT attribute specifies the maximum number of requests permitted to queue for free sessions to the remote system. The MAXQTIME attribute specifies the maximum time between a queue becoming full and it being purged because the remote system is unresponsive. Further information is given in Intersystem session queue management.

If you are using z/OS Communications Server persistent session support, the PSRECOVERY attribute specifies whether sessions to the remote system are recovered, if the local CICS fails and restarts within the persistent session delay interval. Further information is given in Using z/OS Communications Server persistent sessions on APPC links.

For information about security options, see Implementing LU6.2 security.

Note: If the intersystem link is to be used by existing applications that were designed to run on LUTYPE6.1 links, you can use the DATASTREAM and RECORDFORMAT attributes to specify data stream information for asynchronous processing. The information provided by these attributes is not used by APPC application programs.


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