IBM Support

IJ45729: SCHEDULER 761 UNABLE TO ACCESS PERSON RECORDS TO TO LARGE AMOUNT OF RECORDS.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • If the Person application contains a large number of records
    (more than 25 000) it will lead to an issue with the approval of
    work order records when in the Large Projects application.
    
    
    Steps to reproduce the issue:
    
    1	Create a new schedule in the Graphical Scheduling - Large
    Projects application.
    
    2	In Work Queries, set Data Source as WORKORDER, with a query
    that will bring back a few open work order records (eg. WONUM
    like '%100%')
    3	Click the Graphical View tab
    4	Click the check box associated with 2 work order records with
    a different status
    5	Right-click and choose change status
    6	Attempt to change the status to something that is not the
    current status for either work order record
    
    The status of the records do get update and an error is thrown
    in the log.
    
    
    User Name : MAXADMIN
    
    06 Jan 2023 05:51:51:611 [INFO] [MXUI1] [] BMXAA6705I - Query :
    select * from person  for read only
    
    06 Jan 2023 05:51:51:611 [INFO] [MXUI1] [] BMXAA6706I - MboSet
    Name : PERSON Reference =
    psdi.plusg.app.person.PlusGPersonSet@7b94df99
    
    06 Jan 2023 05:51:51:611 [INFO] [MXUI1] [] BMXAA6707I - MboSet
    Size : 6,000
    
    06 Jan 2023 05:51:51:611 [INFO] [MXUI1] [] BMXAA6708I - Fetch
    count so far : 6,000
    
    06 Jan 2023 05:51:51:611 [INFO] [MXUI1] []
    psdi.util.MXSystemException: BMXAA6709I - Printing StackTrace:
    java.lang.Exception
    
    java.lang.Exception: null
    
    Expected Results:
    
    Status of the record would have been updated.
    
    
    Reported in Version:
    
    Management Scheduler 7.6.8.0
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Scheduler users                                              *
    ****************************************************************
    

Problem conclusion

  • A fix for this APAR will be included in a future release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ45729

  • Reported component name

    MAXIMO SCHEDULE

  • Reported component ID

    5724R46SE

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-03-07

  • Closed date

    2023-03-17

  • Last modified date

    2023-03-17

  • 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 SCHEDULE

  • Fixed component ID

    5724R46SE

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9NUN","label":"Maximo Asset Management Scheduler"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
17 March 2023