Posts

Showing posts from June 27, 2021

List of things checked by Maximo Integrity checker

Maximo Integrity checker is a pretty useful tool to identify issues in Maximo database  Below are some of the things checked by integrity checker and the sample errors returned. 1. Extra tables in database which are not part of Maximo BMXAA0442W -- Warning - BMXAA0475W -- The following tables should be removed from the database because they do not exist in the schema: Sun May 30 12:08:47 GST 2021    APPLICATIONAUTH_BKP    DOCLINKS_POBKP    ABC_MIGR_TEST 2. Missing Indexes BMXAA0443E -- Error - BMXAA0465E -- The following indexes are missing from the database. Use the Database Configuration application to remove the index definition. 3. Missing user groups, invalid users etc BMXAA0455E -- The following users should be removed because they are not authorized. To correct this error, run the Integrity Checker in repair mode. BMXAA0458E -- The following user groups were not found in the MAXGROUPS table. Run the Integrity Checker in repair mode. 4. Invalid M...

Automation script to implement Yes/No confirmation messages in Maximo

Below script can be used to implement Yes/No prompt message taken from IBM documentation . 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 # Business logic implementation if user selects Yes choice (clicks Yes button) def yes (): service . log( "Sending Email" ) # Business logic implementation if user selects No choice (clicks No button) def no (): service . log( "Not Sending Email" ) # Business logic to present the choice message initially def dflt (): params = [ str (priority)] service . log( "Throw ERROR" ) # Use the service utility's yncerror() method to push the choice message # The below key and group combination should be added in Database configuration -> Messages service . yncerror( "asset" , "assetpriorityemail" ,params); service . log ( '$$SAM$ - entering ASSETPRIORITYVAL' ) # Declare the user input choices and the corresponding functions impleme...