PH54707: INTEGRATION NODE ON Z/OS JOBLOG BIP MESSAGES INCLUDES THE THREADID

APAR status

• Closed as documentation error.

Error description

• The following topic in the Infocenter (https://www.ibm.com/docs
  /en/integration-bus/10.1?topic=logs-zos-viewing-integration-nod
  e-job)includes information relating to the format of the Joblog
  messages as below:
  
  For each message, the following information is available:
     Date and time: The exact date and time when the event was
  written to the log.
     JOBID: The started task job identifier of the address space.
     Message Number: The message number that identifies whether
  the event is information, a warning, or an error, with
  diagnostic text.
     JOBNAME: The JOBNAME of the address space issuing the
  message. This name is always the same as the integration node
  name.
     STEPNAME: The STEPNAME of the address space that is issuing
  the message. For the control address space, this name is the
  same as the integration node name; for integration servers, it
  is the same as the last eight characters of the integration
  server that is issuing the message.
     PROCSTEP: The procedure STEPNAME, which equals BROKER for the
  main integration node control address space. For integration
  server address spaces, this is either EGNOENV, if there is not
  an integration server specific profile, or EGENV if there is an
  integration server specific profile.
  
  This does not mention the fact that these messages also include
  the thread id number as in the examples below:
  (thread ids: 0, 30, 38, 2):
  
  15.33.18 STC01881 +BIP9108I (Msg 1/1) MQ21BRK 0 INTEGRATION NODE
  SERVICE VALUE IS IMBSERV.V10R0M0.FP21.....
  15.33.31 STC01881 +BIP9153I (Msg 1/1) MQ21BRK 30 THE MQTT
  PUB/SUB BROKER HAS STARTED SUCCESSFULLY, CONFIGURED TO LISTEN ON
  PORT 11885.
  15.33.33 STC01881 +BIP3132I (Msg 1/1) MQ21BRK 38 THE HTTP
  LISTENER HAS STARTED LISTENING ON PORT '4421' FOR 'WebAdmin
  http' CONNECTIONS.
  15.47.09 STC01881 +BIP1286I (Msg 1/1) MQ21BRK 2 INTEGRATION
  SERVER 'IS1' ON INTEGRATION NODE 'MQ21BRK' IS RUNNING.
  
  This paragraph in the topic should be updated to include the
  THREAD ID NUMBER as below:
     STEPNAME: The STEPNAME of the address space that is issuing
  the message. For the control address space, this name is the
  same as the integration node name; for integration servers, it
  is the same as the last eight characters of the integration
  server that is issuing the message.
  <<<< THREAD ID NUMBER:  The number of the current thread. >>>>
     PROCSTEP: The procedure STEPNAME, which equals BROKER for the
  main integration node control address space. For integration
  server address spaces, this is either EGNOENV, if there is not
  an integration server specific profile, or EGENV if there is an
  integration server specific profile.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
   All users of IBM Integration Bus on z/OS
  
  
  Platforms affected:
  z/OS
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The joblog for the Integration Node on Z/OS contains BIP
  messages that include the thread id number. This part of the
  message is not detailed in topic 'z/OS: Viewing integration node
  job logs' .
  

Problem conclusion

• This topic in the Knowlege Center has been updated to include
  details about the Thread Id part of the Joblog BIP messages.
  

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:

Fix information

Applicable component levels