Collecting data about MSC-related problems

If you use IMS MSC and experience a related problem, complete the following tasks:

• Create an SVC dump of the coupled IMS regions (minimally, the CTL regions, but the problem might reside in any IMS-related region). In addition, ensure that the VTAM® address space is also included. Create this dump as close to the time of the problem as possible, before you try to fix the problem.
• Save the IMS OLDS for both coupled systems from the time of the message creation.
• To show the status and queue counts for the logical link, issue the type-1 commands /DISPLAY LINK ALL and /DISPLAY LINK ALL MODE, or issue the type-2 command QUERY MSLINK NAME(linkname) SHOW(ALL).
• If the problem is recreatable:
  • Turn on the VTAM Internal Trace for both coupled systems:

    F  NET,TRACE,TYPE=VTAM,OPT=(API,PIU,MSG),DSPSIZE=5,SIZE=999 

  • Using the options shown above, the VIT (VTAM internal trace) is created in a VTAM data space. After the problem has been recreated, the dump parameters should also include the VTAM data space:

    DSPNAME=('NET'.ISTITDS1)

  • Turn on the MSC LINK trace for both coupled systems by issuing either the type-1 command /TRACE SET ON LINK link# LEVEL 3 MODULE ALL or the type-2 command UPDATE MSLINK NAME(linkname) START(TRACE).
    • The type-2 command UPDATE MSLINK NAME(linkname) START(TRACE) uses the same level and module settings that were used the last time the command /TRACE SET ON LINK link# was issued. If a /TRACE SET ON LINK link# command has not been issued since the last cold start, this command defaults to MODULE ALL and LEVEL 4.