PH31193: ADDING FILTERING TO DATAMOVER CAUSES MANY MESSAGES: DRLJ0113E I-JOIN OUTPUT - PACKET SEQUENCE XX SKIPPED FROM X TO XX.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Adding filtering to datamover causes many messages:  DRLJ0113E
  I-JOIN Output - Packet sequence XX skipped from X to XX.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IBM Z Performance and Capacity      *
  *                 Analytics Version 3.1.0 using the            *
  *                 Data Mover or Collator                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. Messages DRLJ0113E and DRLJ0112E     *
  *                      are issued repeatedly when filtering    *
  *                      is used.                                *
  *                                                              *
  *                      2. Messages written to stdout are       *
  *                      formatted with a 12 hour timestamp.     *
  ****************************************************************
  * RECOMMENDATION: Apply the provided PTF.                      *
  ****************************************************************
  1. When multiple senders connect to a configuration that accepts
  input from a TCPIP stage and feeds it into a SPLIT/JOIN stage,
  the JOIN stage complains about the sequence numbers on the data
  packets. Messages are  DRLJ0112E and DRLJ0113E.
  
  DRLJ0113E I-JOIN Output - Packet sequence 0 skipped
  from 198 to 0
  
  DRLJ0112E 'stage type' Output - First packet in
  sequence 127.0.0.1:51739 had sequence number 199
  
  2. Messages written to stdout are formatted with a 12 hour
  timestamp. This makes it difficult to determine from the
  log when messages were issued.
  

Problem conclusion

• 1. When a configuration is used that feeds multiple datastreams
  received over TCPIP into a SPLIT/JOIN stage the JOIN stage
  complains about sequence skipping in the streams.  This is
  because it is missing logic to differentiate between the
  streams and is seeing them as a single stream.
  
  Logic has been added to recognize each data stream as being a
  separate stream and to perform sequence checking independently
  for each stream.
  
  2. The timestamp has been enhanced to be Year, Month and Day
  followed by a 24 hour time. This should make it easier to
  determine exactly when a message was issued.
  

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:

  UI73074

Modules/Macros

• DRLPJCO  DRLPJDM
  

Fix information

• Fixed component name

  TDS FOR Z/OS

• Fixed component ID

  569510100

Applicable component levels

• RC01 PSY UI73074

     UP20/12/15 P F012

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.