Defining compatible MRO nodes

An MRO link must be defined in both of the systems that it connects. You must ensure that the two definitions are compatible with each other. For example, if one definition specifies six sending sessions, the other definition requires six receiving sessions.

About this task

The compatibility requirements are summarized in the following table. Related resources and attributes are shown by identical numbers.
Note: VTAM® is now z/OS® Communications Server.
  CICSA CICSB
System initialization parameters
APPLID=CICSA          1 
 4       APPLID=CICSB
CONNECTION resource
CONNECTION(CICB)      2 
NETNAME(CICSB)        4 
ACCESSMETHOD(IRC)
QUEUELIMIT(500)
MAXQTIME(500)
INSERVICE(YES)
  3      CONNECTION(CICA)
  1      NETNAME(CICSA)
         ACCESSMETHOD(IRC)
         QUEUELIMIT(NO)

         INSERVICE(YES)
         ATTACHSEC(LOCAL)  
SESSIONS resource
SESSIONS(csdname)
CONNECTION(CICB)      2 
PROTOCOL(LU61)        5 
RECEIVEPFX(<)
RECEIVECOUNT(8)       6 
SENDPFX(>)
SENDCOUNT(10)         7 
         SESSIONS(csdname)
  3      CONNECTION(CICA)
  5      PROTOCOL(LU61)  
         RECEIVEPFX(<)
  7      RECEIVECOUNT(10)
         SENDPFX(>)
  6      SENDCOUNT(8)
Note: VTAM is the previous name for z/OS Communications Server.


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