APAR status
Closed as program error.
Error description
Change CI status with NOACCESSCHECK flag breaks status propagation PERFORMANCE ISSUE: NO STEPS TO REPRODUCE: Using script to change CI status with mbo.NOACCESSCHECK flag breaks status propagation. The status change is successful but upon checking further, only the status of the main CI is changed and every related CI is not changed. This leads to wrong data. Assuming you have: - - 1 CINUM with ciid 1001 (ComputerSystem) and it has 1 related CI (IP-Interface). All CIs have status NOT READY - 1 CINUM with ciid 1002 (ComputerSystem) and it has 1 related CI (IP-Interface). All CIs have status NOT READY Sample script << CITEST.py >> ######## from psdi.server import MXServer mxServer = MXServer.getMXServer() userInfo = mxServer.getSystemUserInfo() #Change CINUM with ciid 1001 to OPERATING with no flag ciSet = mxServer.getMboSet("CI",userInfo) ciMbo = ciSet.getMboForUniqueId(1001) ciMbo.changeStatus("OPERATING",None,"No flag") ciSet.save() ciSet.close() ciSet.cleanup() #Change CINUM with ciid 1002 to OPERATING with NOACCESSCHECK flag ciSet = mxServer.getMboSet("CI",userInfo) ciMbo = ciSet.getMboForUniqueId(1002) ciMbo.changeStatus("OPERATING",None,"NOACCESSCHECK flag",ciMbo.NOACCESSCHECK) ciSet.save() ciSet.close() ciSet.cleanup() ######## Use this sample script << CITEST.py >> to reproduce the issue. 1. Login to ICD/Maximo 2. Go To -> System Configuration -> Platform Configuration -> Automation Script 3. More Actions -> Create -> Action Launch Point (a) In Step 1 Name: RUN Action: CITESTRUN Object <blank> (b) Click Next and in Step 2 Script: CITEST (c) Click Next and in Step 3 Paste the sample script << CITEST.py >> (d) Click Create 4. Open the script and click "Test Script" 5. Enter "CI" as object path 7. Click on Test. CURRENT ERRONEOUS RESULT: The script changes status on the ComputerSystem (CINUM with ciid 1001) to OPERATING and the IP-Interface is automatically changed to OPERATING as well. So the status propagation works correctly. ciMbo.changeStatus("OPERATING",None,"No flag") After this, it changes the status of the ComputerSystem (CINUM with ciid 1002) to OPERATING but with mbo.NOACCESSCHECK flag. As per check, only the status of the ComputerSystem is changed to OPERATING, the status of IP-Interface is not changed and remains in NOT READY. <-- The issue ciMbo.changeStatus("OPERATING",None,"NOACCESSCHECK flag",ciMbo.NOACCESSCHECK) EXPECTED RESULT: When you change the status of ComputerSystem with mbo.NOACCESSCHECK flag, the status of related CI should automatically change too. ADDITIONAL INFO: Case: TS014925529 ENVIRONMENT: - ICD 7.6.1.4 - Tpae 7.6.1.2
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: * * MAXIMO * **************************************************************** * PROBLEM DESCRIPTION: * * CHANGE CI STATUS WITH NOACCESSCHECK FLAG BREAKS STATUS * * PROPAGATION * **************************************************************** CHANGE CI STATUS WITH NOACCESSCHECK FLAG BREAKS STATUS PROPAGATION
Problem conclusion
This fix will be included in future release.
Temporary fix
Comments
APAR Information
APAR number
IJ51455
Reported component name
MAXIMO ASST MGM
Reported component ID
5724R46AM
Reported release
761
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2024-06-13
Closed date
2024-06-25
Last modified date
2024-08-29
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
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
29 August 2024