IJ40948: CRON TASK LOGS NOT WRITING TO LOG FILES AFTER APPLYING 7612 IFIX020

APAR status

• Closed as program error.

Error description

• After installing IFIX020 for TPAE 7.6.1.2, Cron Task logs are
  not writing to log the files.
  
  Steps to reproduce (Using OOTB logger and appender)
  1) Set crontask root logger to INFO,
  
  2) Enable PMWoGenCronTask logging with PMWoGenCronTask appender
  using MXFileAppender implementation class
  3)  Ensured that the PMWoGenCronTask Cron is running every.
  
  
  Notice log file created, but with 0 byte size and no log
  written into it, even after JVM is restarted.
  
  
  
  System Inforation:
  App Server: IBM WebSphere Application Server 9.0.5.11
  
  Version:
  Tivoli's process automation engine 7.6.1.2-IFIX20220426-1324
  Build 20200715-0100 DB Build V7612-284 HFDB Build HF7612-92
  IBM Maximo Asset Management Work Centers 7.6.0.4 Build
  20200715-0100 DB Build V7604-119 HFDB Build HF7680-10
  IBM Maximo Asset Management Scheduler 7.6.8.0 Build
  20200715-0100 DB Build V7680-148 HFDB Build HF7680-26
  IBM Maximo Anywhere 7.6.4.0 Build 20200117_195427-0500 DB Build
  V7640-12
  IBM Tpae Integration Framework
  7.6.1.2-MIF_7612_IFIX.20220404-1408 Build 20200715-1444 DB Build
  V7612-11 HFDB Build HF7612-02
  IBM Maximo Asset Management 7.6.1.2 Build 20200715-0100 DB Build
  V7611-01
  IoT Connection Utility 7.6.0.3 Build 20200701-1409 DB Build
  V7603-32
  TPAE OSLC Object Structure 7.6.4.0 Build 20200219_092917-0500 DB
  Build V7640-04
  Server OS: AIX 7.2
  Server DB: Oracle 19.0 (Oracle Database 19c Enterprise Edition
  Release 19.0.0.0.0 - Production Version 19.14.0.0.0)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * _MAXIMO_                                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * After applying a Log4j remediated version of Maximo,         *
  * generating custom loggers that hadn't existed previously     *
  * weren't being created properly.                              *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package: release\fix pack for Release 8.x Product
  

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

• Fixed component name

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels