IBM Support

IJ04919: PMWOGEN LOG IS HARD TO READ BASED ON HOW THE LOG IS FORMATTED.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The following log format issue has been identified in both 7609
    and 750.11 as of now, may exist in other versions as well.
    
    Once the PMWOGEN is run and one is reviewing the log, the
    format makes it hard to read.
    
    Here is an example of what the logs looks like in 7609 & 750.11
    
    Example 7.5.0.11---
    
    Generate work order from PMs on site XXX finished 3/6/18 12:01
    AM. BMXAA3191E - PM 101001 is not due yet, or it does not fall
    within the active season. Generate work order from PMs on site
    XXX finished 3/6/18 12:01 AM. BMXAA3191E - PM 1011015 is not
    due yet, or it does not fall within the active season. Generate
    work order from PMs on site XXX finished 3/6/18 12:01 AM.
    BMXAA3208I - PM 1011016 created work
    order 668923. Generate work order from PMs on site XXX finished
    3/6/18 12:01 AM. BMXAA3191E - PM 1011018 is not due yet, or it
    does not fall within the active season. Generate work order
    from PMs on site XXX finished 3/6/18 12:01 AM. BMXAA3191E - PM
    1011019 is not due yet, or it does not fall within the active
    season. Generate work order from PMs on site XXX finished
    3/6/18 12:01 AM. BMXAA3191E - PM
    1011020 is not due yet, or it does not fall within the active
    season. Generate work order from PMs on site XXX finished
    3/6/18 12:01 AM. BMXAA3191E - PM 1011021 is not due yet, or it
    does not fall within the active season. Generate work order
    from PMs on site XXX finished 3/6/18 12:01 AM. BMXAA3191E - PM
    1011022 is not due yet, or
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO users                                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * PMWoGenCronTask log formatting is difficult to read.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The following PMWoGenCronTask log format issue has been
    identified in both 7609 and 750.11.
    
    Here is an example of what the logs looks like in 7609 & 750.11
    
    Example 7.5.0.11---
    ------------------------------------
    Generate work order from PMs on site XXX finished 3/6/18 12:01
    AM. BMXAA3191E - PM 101001 is not due yet, or it does not fall
    within the active season. Generate work order from PMs on site
    XXX finished 3/6/18 12:01 AM. BMXAA3191E - PM 1011015 is not
    due yet, or it does not fall within the active season. Generate
    work order from PMs on site XXX finished 3/6/18 12:01 AM.
    BMXAA3208I - PM 1011016 created work
    order 668923. Generate work order from PMs on site XXX finished
    3/6/18 12:01 AM. BMXAA3191E - PM 1011018 is not due yet, or it
    does not fall within the active season. Generate work order
    from PMs on site XXX finished 3/6/18 12:01 AM. BMXAA3191E - PM
    1011019 is not due yet, or it does not fall within the active
    season. Generate work order from PMs on site XXX finished
    3/6/18 12:01 AM. BMXAA3191E - PM
    1011020 is not due yet, or it does not fall within the active
    season. Generate work order from PMs on site XXX finished
    3/6/18 12:01 AM. BMXAA3191E - PM 1011021 is not due yet, or it
    does not fall within the active season. Generate work order
    from PMs on site XXX finished 3/6/18 12:01 AM. BMXAA3191E - PM
    1011022 is not due yet, or
    ------------------------------------
    
    The log appears to be missing line feeds.
    

Problem conclusion

  • The fix for this APAR is included in the following package:
                           | Release 7.6.1.0 of Base Services.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ04919

  • Reported component name

    SYSTEM CONFIG

  • Reported component ID

    5724R46S1

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-03-14

  • Closed date

    2018-05-02

  • Last modified date

    2018-05-02

  • 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

    SYSTEM CONFIG

  • Fixed component ID

    5724R46S1

Applicable component levels

  • R760 PSY

       UP



Document information

More support for: Maximo Asset Management

Software version: 760

Reference #: IJ04919

Modified date: 02 May 2018