Defining an MRO link
To define an MRO link, create a CONNECTION resource and an associated SESSIONS resource.
Procedure
- Create a CONNECTION resource. Specify the following attributes:
- CONNECTION(sysidnt)
- sysidnt is the local name for the CICS system to which the link is being defined.
- NETNAME(name)
- The netname must be the name with which the remote system logs on to the interregion SVC; that is, its applid. If you do not specify a netname, then sysidnt must satisfy these requirements. There can be only one MRO link between any two CICS regions; that is, each CONNECTION must specify a unique netname.
- ACCESSMETHOD(IRC|XM)
- QUEUELIMIT(NO|0-9999)
- The maximum number of requests permitted to queue for free sessions to the remote system.
- MAXQTIME(NO|0-9999)
- The 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.
- INSERVICE(YES)
- ATTACHSEC(LOCAL|IDENTIFY)
- USEDFLTUSER(NO|YES)
For information about the ATTACHSEC and USEDFLTUSER security attributes see Specifying user security in link definitions.
- Create a SESSIONS resource.
If you are using RDO, the CONNECTION and SESSIONS must be in the same GROUP.
Specify the following attributes:- SESSIONS(csdname)
- CONNECTION(sysidnt)
- The CONNECTION attribute must match the sysidnt specified for the CONNECTION. Only one SESSIONS definition can be related to an MRO CONNECTION.
- PROTOCOL(LU61)
- RECEIVEPFX(prefix1) and SENDPFX(prefix2)
- Specify the prefixes which allow the sessions to be named. A prefix is a one-character or two-character string that is used to generate session identifiers (TRMIDNTs). If you do not specify prefixes, they default to '>' (for SEND) and '<' (for RECEIVE). It is recommended that you allow the prefixes to default, because:
- This guarantees that the session names generated by CICS are unique; prefixes must not cause a conflict with an existing connection or terminal name.
- If you specify your own 2-character prefixes, the number of sessions you can define for each connection is limited to 99. If you specify your own 1-character prefixes, the limit increases to 999—the same as for default prefixes—but you may find it harder to guarantee unique session names.
For an explanation of how CICS generates names for MRO sessions, see SESSIONS definition attributes
- RECEIVECOUNT(number1)
- SENDCOUNT(number2)
Specify the number of RECEIVE and SEND sessions that are required (at least one of each). Initial requests can never be sent on a RECEIVE session. Bear this in mind when deciding how many RECEIVE and SEND sessions you need.
- SESSPRIORITY(number) and IOAREALEN(value)
dfht1c00114.html |
Last updated: Sunday, 4 June 2017