Defining compatible CICS APPC nodes

When you define an APPC link between two CICS® systems, you must ensure that the definitions of the link in each of the systems are compatible.

The following table summarizes the compatibility requirements. Related options and operands are shown by identical numbers.
  CICSA CICSB
System initialization parameters
APPLID=CICSA          1 
 3       APPLID=CICSB
CONNECTION resource
CONNECTION(CICB)      2 
NETNAME(CICSB)        3 
ACCESSMETHOD(VTAM)
PROTOCOL(APPC)
SINGLESESS(N)         4 
QUEUELIMIT(500)
MAXQTIME(500)
BINDPASSWORD(pw)      5 
 10      CONNECTION(CICA)
  1      NETNAME(CICSA)
         ACCESSMETHOD(VTAM)
         PROTOCOL(APPC)
  4      SINGLESESS(N)
         QUEUELIMIT(NO)
         ATTACHSEC(IDENTIFY) 
  5      BINDPASSWORD(pw) 
SESSIONS resource
SESSIONS(csdname)
CONNECTION(CICB)      2 
MODENAME(M1)          6 
PROTOCOL(APPC)
MAXIMUM(ss,ww)        7 
SENDSIZE(kkk)         8 
RECEIVESIZE(jjj)      9 
         SESSIONS(csdname)
 10      CONNECTION(CICA)
  6      MODENAME(M1)
         PROTOCOL(APPC)
  7      MAXIMUM(ss,ww)
  9      SENDSIZE(jjj)
  8      RECEIVESIZE(kkk) 
Notes:
  • VTAM® is the previous name for z/OS® Communications Server.
  •  7  The values specified for MAXIMUM on either side of the link do not need to match, because they are negotiated by the LU services managers. However, a matching specification avoids unusable TCTTE entries, and also avoids unexpected bidding because of the "contention winners" negotiation.
  •  8 , 9  If the value specified for SENDSIZE on one side of the link does not match that specified for RECEIVESIZE on the other, CICS negotiates the values at BIND time.


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