PM08345: TRACE EVENT RECORD 170 NOT PRODUCED FOR SCI SEND/RECEIVE EVENTS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This APAR will address the following problems:
  - Trace event record 170 not produced for SCI send receive
    events
  - Recorder Trace Utility does not format ODBM trace records
    correctly when IPB/OPB data length is zero
  - TCPIP MAXSOC keyword can have leading zeros for IMS Connect
    parser without errors. The CEX parser generates an error
    if the leading zeros make the length of the keyword value
    more than 5 characters.
  - The CEX parser generates an error if some of the HWS CONFIG
    members keyword values begin with a numeric value.
  - ABEND0C4 CEXCETL +x'66BA' when running option CEXTRACE
    BUFSIZE=4.
  - MSGFUN2211I Syntax error at line  XX: the input RUNOPTS is
  not a known command
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IMS Connect Extensions V2.2         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Trace event record 170 not produced     *
  *                      for SCI send/receive events.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This APAR is correcting the following:
  1. Trace event record 170 not produced for SCI send/receive
  events.
  2. Recorder Trace Utility does not format ODBM trace records
  correctly when IPB/OPB data length is zero.
  3. TCPIP MAXSOC keyword can have leading zeros for IMS Connect
  parser without errors. The CEX parser generates and error if the
  leading zeros make the length of the keyword value more than 5
  characters.
  4. The CEX parser generates and error is some of the HWS CONFIG
  members keyword values begin with a number value
  5. A multi-segment input message from WAS may result in an
  invalid Client Id in the CEX Console Active session display.
  6. Remove event records for OTMA Degraded system monitoring
  heartbeat notification.
  7. An 0C4 can occur when the CEX OTMA trace is active and the
  size of the data being traced is only 1 or 2 bytes longer than
  the trace buffer size.
  

Problem conclusion

• The following changes have been made for the above problems:
  1. Corrected module CEXTECL to produce the trace event when
  requested.
  2. Corrected utility to format ODBM trace records correctly.
  3. Corrected parser to accept leading zeros up to a maximum
  length of 6 characters. The resulting value of MAXSOC cannot
  exceed the IMS Connect allowed maximum of 65,535.
  4. Changed the CEX parser to allow keyword values to begin with
  a numeric character when the keyword value does not refer to a
  PDS member name.
  5. Corrected module CEXEVT01 to correctly process WAS
  multi-segment input message.
  6. Changed CEXTECL to not record events for system monitoring
  heartbeat messages.
  7. Corrected CEXTECL to properly track the amount of data that
  has been moved to the trace buffer.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK56413

Modules/Macros

• CEXBCMD0 CEXCR65  CEXEVT01 CEXMAIN  CEXPRSR
  CEXRCDUT CEXTECL
  

Fix information

• Fixed component name

  IMS CONNECT EXT

• Fixed component ID

  5655K4800

Applicable component levels

• R220 PSY UK56413

     UP10/05/01 P F004

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.