APAR status
Closed as program error.
Error description
The skdproject.commitby field is not being updated from NULL when a commitment change is made. STEPS TO REPRODUCE: 1. Query the database > SELECT COMMITTIME , COMMITBY FROM SKDPROJECT WHERE NAME ='XXX' 2. Commit a change in Graphical Scheduler (using either the More Action menu or right-click commit option) 3. Re-run your query in the database RESULTS: SKDPROJECT.COMMITTIME is updated. SKDPROJECT.COMMITBY is left NULL. EXPECTED RESULTS: SKDPROJECT.COMMITBY should be updated according to the username that committed the change. REPORTED IN VERSION: IBM Maximo Asset Management Scheduler 7.6.8.0 IBM Maximo Asset Management 7.6.1.2
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Scheduler users * ****************************************************************
Problem conclusion
The fix for this APAR is contained in the following maintenancepackage: Release 7.6.1.3 of Base Services
Temporary fix
Comments
APAR Information
APAR number
IJ40053
Reported component name
MAXIMO SCHEDULE
Reported component ID
5724R46SE
Reported release
768
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2022-05-18
Closed date
2022-05-22
Last modified date
2022-05-22
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
[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"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":"768"}]
Document Information
Modified date:
23 May 2022