Defining multiple links to an IMS system

You can define more than one intersystem link between a CICS® and an IMS™ system.

About this task

To defined multiple links to an IMS system, create two or more CONNECTION definitions (with their associated SESSION definitions) with the same netname, but with different sysidnts. Although all the system definitions resolve to the same netname, and therefore to the same IMS system, the use of a sysidnt name in CICS causes CICS to allocate a session from the link with the specified sysidnt.

It is recommended that you define up to three links (that is, groups of sessions) between a CICS and an IMS system, depending upon the application requirements of your installation:
  1. For CICS-initiated distributed transaction processing (synchronous processing).

    CICS applications that use the SEND/RECEIVE interface can use the sysidnt of this group to allocate a session to the remote system. The session is held (busy) until the conversation is terminated.

  2. For CICS-initiated asynchronous processing.

    CICS applications that use the START command can name the sysidnt of this group. CICS uses the first non-busy session to ship the start request.

    IMS sends a positive response to CICS as soon as it has queued the start request, so that the session is in use for a relatively short period. Consequently, the first session in the group shows the heaviest usage, and the frequency of usage decreases towards the last session in the group.

  3. For IMS-initiated asynchronous processing.

    This group is also useful as part of the solution to a performance problem that can arise with CICS-initiated asynchronous processing. An IMS transaction that is initiated as a result of a START command shipped on a particular session uses the same session to ship its "reply" START command to CICS. For the reasons given previously in (2), the CICS START command was probably shipped on the busiest session and, because the session is busy and CICS is the contention winner, the replies from IMS may be queuing for a chance to use the session.

    However, facilities exist in IMS for a transaction to alter its default output session, and a switch to a session in this third group can reduce this sort of queuing problem.

Table 1. Defining multiple links to an IMS node
CICS
System Initialization parameters:
SYSIDNT=CICL,
APPLID=SYSCICS
Resources for CICS-initiated distributed transaction processing
CONNECTION(IMSA)
NETNAME(SYSIMS)
ACCESSMETHOD(VTAM)

SESSIONS(csdname)
CONNECTION(IMSA)
SESSNAME(IMS1)
NETNAMEQ(DTP1)
PROTOCOL(LU61)

SESSIONS(csdname)
  .
  .
Resources for CICS-initiated asynchronous processing
CONNECTION(IMSB)
NETNAME(SYSIMS)
ACCESSMETHOD(VTAM)

SESSIONS(csdname)
CONNECTION(IMSB)
SESSNAME(IMS1)
NETNAMEQ(ASP1)
PROTOCOL(LU61)

SESSIONS(csdname)
  .
  .
Resources for IMS-initiated asynchronous processing
CONNECTION(IMSC)
NETNAME(SYSIMS)
ACCESSMETHOD(VTAM)

SESSIONS(csdname)
CONNECTION(IMSC)
SESSNAME(IMS1)
NETNAMEQ(IST1)
PROTOCOL(LU61)

SESSIONS(csdname)
  .
  .
Note: VTAM® is the previous name for z/OS® Communications Server.


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