I am having a heck of a time trying to get a medium sized Failure Hierarchy to load into a MAS 9 environment using MxLoader.

I first hit the issue that the NextGen MxLoader does not support the MXL_FAILURELIST. So I move back to 6.2 and then find that I cannot connect to MAS in 6.2.

Once I finally got REST connections working (in 8.4) after looking on various threads and trying to do a custom OS with FAILURELIST and FAILURECODE I could not get it to work to save my life.

My biggest issue is that I cannot find a way to OVERRIDE the FAILURELIST value as it goes into MBO and as such it generates its own new sequence values when I load. I need the values to stay what I want to be able to load a hierarchy I have already created. Anybody have the solution to this issue? The override cannot be selected in the OS definition. I have the data in a 7.6.1.3 env to pull out and want to move it with the same values to the new environment.

So, what I have got somewhat working is to use single MBO OS's one for FAILURECODE (MXL_FAILURECODE). And then my own OS with just FAILURELIST to do the FAILURECLASS load and then I use the OOTB - MXAPIFAILURELIST to load the PROBLEM,CAUSE and REMEDY.  But the hassle is I must find the newly generated PARENT values for the PROBLEM, CAUSE and REMEDY and that is a MAJOR hassle since they are multiple levels deep and very complex to get the PARENT value on each of those codes going in.

I cannot believe there is not an easier way to load a full hierarchy. I see why Bruno stopped supporting it in the NextGen API as it looks really complicate to achieve.

Anybody have any advice to provide or how they were able to do it?

Thanks,

IBM Response about trying to create an OS that will load Failure Hierarchy in MAS 9. I have tried Mxloader, REST API and Application Import/Export all with no success now:

Hi David

Unfortunately we do not have OOTB objects to support the process so you may need to build you own customer

to include all objects you planning to load , it may require the custom processing class to.

I have run this by dev and that what they said, sorry

My Response to them:

I am having a heck of a time trying to get a medium sized Failure Hierarchy to load into a MAS 9 environment using MxLoader.

I first hit the issue that the NextGen MxLoader does not support the MXL_FAILURELIST. So I move back to 6.2 and then find that I cannot connect to MAS in 6.2.

Once I finally got REST connections working (in 8.4) after looking on various threads and trying to do a custom OS with FAILURELIST and FAILURECODE I could not get it to work to save my life.

My biggest issue is that I cannot find a way to OVERRIDE the FAILURELIST value as it goes into MBO and as such it generates its own new sequence values when I load. I need the values to stay what I want to be able to load a hierarchy I have already created. Anybody have the solution to this issue? The override cannot be selected in the OS definition. I have the data in a 7.6.1.3 env to pull out and want to move it with the same values to the new environment.

So, what I have got somewhat working is to use single MBO OS's one for FAILURECODE (MXL_FAILURECODE). And then my own OS with just FAILURELIST to do the FAILURECLASS load and then I use the OOTB - MXAPIFAILURELIST to load the PROBLEM,CAUSE and REMEDY.  But the hassle is I must find the newly generated PARENT values for the PROBLEM, CAUSE and REMEDY and that is a MAJOR hassle since they are multiple levels deep and very complex to get the PARENT value on each of those codes going in.

I cannot believe there is not an easier way to load a full hierarchy. I see why Bruno stopped supporting it in the NextGen API as it looks really complicate to achieve.

Anybody have any advice to provide or how they were able to do it?

Thanks,

As expected IBM refuses to acknowledge this as a Defect which it is and I did not really expect anything less. While this does not help me in an IBM SaaS environment because you cannot do SQL to the DB, I did find this solution will work if you have backend DB access for a MAS 9 environment.

I created a custom Integration OS with FAILURELIST & FAILURECODE MBOs on it linked by FAILURECODE relationship.  Then if you do this insert using your OS name and obviously picking an ID value that is not duiplicate:

-- -- TABLE INSERT STATEMENTS-- INSERT  INTO    MAXIMO.MAXINTOBJCOLS    (      MAXINTOBJCOLS.INTOBJECTNAME,      MAXINTOBJCOLS.OBJECTNAME,      MAXINTOBJCOLS.NAME,      MAXINTOBJCOLS.INTOBJFLDTYPE,      MAXINTOBJCOLS.CHANGEBY,      MAXINTOBJCOLS.CHANGEDATE,      MAXINTOBJCOLS.MAXINTOBJCOLSID    )  VALUES    (      'EIP_FAILURE',      'FAILURELIST',      'FAILURELIST',      'NONRESTRICTED',      'MAXADMIN',      TO_DATE ('04/28/2025 05:51:46 PM',           'MM/DD/YYYY HH12:MI:SS AM'),      18472    )/

Once that row exists telling it that FAILURELIST attribute is  'NONRESTRICTED' you will then be able to move the Restricted setting on the Inbound Settings and make the FAILURELISTR Override in fact I make all the attributes on the FAILURELIST MBO Override including PARENT . My inbound settings can look like this:



At this point you can use MxLoader to load a hierarchy if you have your FALURELIST and PARENT id values set to appropriate numeric values building a full hierarchy. In my case I pull it out of a 7.6 env and it came out with the appropriate values in there. Note that you must get the FAILURECODES in standalone before doing the FAILURECLASS and PROBLEM, CAUSE and REMEDY values.

Anyway, hope this helps others in future to solve this problem in a MAS 9 environment. Shame IBM will not acknowledge it as an bug and fix it.  Also, I assume the Application Import and Export will work with these setting now if you use this OS and have appropriate values in the XML or JSON. Also, assume REST API will work if you have values as well

Good luck,

IBM Response about trying to create an OS that will load Failure Hierarchy in MAS 9. I have tried Mxloader, REST API and Application Import/Export all with no success now:

Hi David

Unfortunately we do not have OOTB objects to support the process so you may need to build you own customer

to include all objects you planning to load , it may require the custom processing class to.

I have run this by dev and that what they said, sorry

My Response to them:

I am having a heck of a time trying to get a medium sized Failure Hierarchy to load into a MAS 9 environment using MxLoader.

I first hit the issue that the NextGen MxLoader does not support the MXL_FAILURELIST. So I move back to 6.2 and then find that I cannot connect to MAS in 6.2.

Once I finally got REST connections working (in 8.4) after looking on various threads and trying to do a custom OS with FAILURELIST and FAILURECODE I could not get it to work to save my life.

My biggest issue is that I cannot find a way to OVERRIDE the FAILURELIST value as it goes into MBO and as such it generates its own new sequence values when I load. I need the values to stay what I want to be able to load a hierarchy I have already created. Anybody have the solution to this issue? The override cannot be selected in the OS definition. I have the data in a 7.6.1.3 env to pull out and want to move it with the same values to the new environment.

So, what I have got somewhat working is to use single MBO OS's one for FAILURECODE (MXL_FAILURECODE). And then my own OS with just FAILURELIST to do the FAILURECLASS load and then I use the OOTB - MXAPIFAILURELIST to load the PROBLEM,CAUSE and REMEDY.  But the hassle is I must find the newly generated PARENT values for the PROBLEM, CAUSE and REMEDY and that is a MAJOR hassle since they are multiple levels deep and very complex to get the PARENT value on each of those codes going in.

I cannot believe there is not an easier way to load a full hierarchy. I see why Bruno stopped supporting it in the NextGen API as it looks really complicate to achieve.

Anybody have any advice to provide or how they were able to do it?

Thanks,

Hi David,

We solved this also with a custom object structure and a processing class and it worked fine afterwards.

Kind Regards,

Liliana Malaescu
Senior Technical Maximo Consultant
ZNAPZ b.v
Bucharest, Romania

As expected IBM refuses to acknowledge this as a Defect which it is and I did not really expect anything less. While this does not help me in an IBM SaaS environment because you cannot do SQL to the DB, I did find this solution will work if you have backend DB access for a MAS 9 environment.

I created a custom Integration OS with FAILURELIST & FAILURECODE MBOs on it linked by FAILURECODE relationship.  Then if you do this insert using your OS name and obviously picking an ID value that is not duiplicate:

-- -- TABLE INSERT STATEMENTS-- INSERT  INTO    MAXIMO.MAXINTOBJCOLS    (      MAXINTOBJCOLS.INTOBJECTNAME,      MAXINTOBJCOLS.OBJECTNAME,      MAXINTOBJCOLS.NAME,      MAXINTOBJCOLS.INTOBJFLDTYPE,      MAXINTOBJCOLS.CHANGEBY,      MAXINTOBJCOLS.CHANGEDATE,      MAXINTOBJCOLS.MAXINTOBJCOLSID    )  VALUES    (      'EIP_FAILURE',      'FAILURELIST',      'FAILURELIST',      'NONRESTRICTED',      'MAXADMIN',      TO_DATE ('04/28/2025 05:51:46 PM',           'MM/DD/YYYY HH12:MI:SS AM'),      18472    )/

Once that row exists telling it that FAILURELIST attribute is  'NONRESTRICTED' you will then be able to move the Restricted setting on the Inbound Settings and make the FAILURELISTR Override in fact I make all the attributes on the FAILURELIST MBO Override including PARENT . My inbound settings can look like this:



At this point you can use MxLoader to load a hierarchy if you have your FALURELIST and PARENT id values set to appropriate numeric values building a full hierarchy. In my case I pull it out of a 7.6 env and it came out with the appropriate values in there. Note that you must get the FAILURECODES in standalone before doing the FAILURECLASS and PROBLEM, CAUSE and REMEDY values.

Anyway, hope this helps others in future to solve this problem in a MAS 9 environment. Shame IBM will not acknowledge it as an bug and fix it.  Also, I assume the Application Import and Export will work with these setting now if you use this OS and have appropriate values in the XML or JSON. Also, assume REST API will work if you have values as well

Good luck,

IBM Response about trying to create an OS that will load Failure Hierarchy in MAS 9. I have tried Mxloader, REST API and Application Import/Export all with no success now:

Hi David

Unfortunately we do not have OOTB objects to support the process so you may need to build you own customer

to include all objects you planning to load , it may require the custom processing class to.

I have run this by dev and that what they said, sorry

My Response to them:

I am having a heck of a time trying to get a medium sized Failure Hierarchy to load into a MAS 9 environment using MxLoader.

I first hit the issue that the NextGen MxLoader does not support the MXL_FAILURELIST. So I move back to 6.2 and then find that I cannot connect to MAS in 6.2.

Once I finally got REST connections working (in 8.4) after looking on various threads and trying to do a custom OS with FAILURELIST and FAILURECODE I could not get it to work to save my life.

My biggest issue is that I cannot find a way to OVERRIDE the FAILURELIST value as it goes into MBO and as such it generates its own new sequence values when I load. I need the values to stay what I want to be able to load a hierarchy I have already created. Anybody have the solution to this issue? The override cannot be selected in the OS definition. I have the data in a 7.6.1.3 env to pull out and want to move it with the same values to the new environment.

So, what I have got somewhat working is to use single MBO OS's one for FAILURECODE (MXL_FAILURECODE). And then my own OS with just FAILURELIST to do the FAILURECLASS load and then I use the OOTB - MXAPIFAILURELIST to load the PROBLEM,CAUSE and REMEDY.  But the hassle is I must find the newly generated PARENT values for the PROBLEM, CAUSE and REMEDY and that is a MAJOR hassle since they are multiple levels deep and very complex to get the PARENT value on each of those codes going in.

I cannot believe there is not an easier way to load a full hierarchy. I see why Bruno stopped supporting it in the NextGen API as it looks really complicate to achieve.

Anybody have any advice to provide or how they were able to do it?

Thanks,

Hi Liliana,

That's great news, are you willing to share how you configured the object structure and processing class which got it working? I am working on a similar issue and your example could save hours of trial & error and debugging time for others in the future looking at the same issue. We sure would be grateful.

Cheers,

James

------------------------------
James Earley

Original Message:
Sent: Wed April 30, 2025 12:36 PM
From: Liliana Malaescu
Subject: MAS 9 FAILURE HIERARCHY LOAD WITH MXLOADER?

Hi David,

We solved this also with a custom object structure and a processing class and it worked fine afterwards.

Kind Regards,

Liliana Malaescu
Senior Technical Maximo Consultant
ZNAPZ b.v
Bucharest, Romania

------------------------------
Liliana Malaescu

Original Message:
Sent: Tue April 29, 2025 01:57 PM
From: David Miller
Subject: MAS 9 FAILURE HIERARCHY LOAD WITH MXLOADER?

As expected IBM refuses to acknowledge this as a Defect which it is and I did not really expect anything less. While this does not help me in an IBM SaaS environment because you cannot do SQL to the DB, I did find this solution will work if you have backend DB access for a MAS 9 environment.

I created a custom Integration OS with FAILURELIST & FAILURECODE MBOs on it linked by FAILURECODE relationship.  Then if you do this insert using your OS name and obviously picking an ID value that is not duiplicate:

-- -- TABLE INSERT STATEMENTS-- INSERT  INTO    MAXIMO.MAXINTOBJCOLS    (      MAXINTOBJCOLS.INTOBJECTNAME,      MAXINTOBJCOLS.OBJECTNAME,      MAXINTOBJCOLS.NAME,      MAXINTOBJCOLS.INTOBJFLDTYPE,      MAXINTOBJCOLS.CHANGEBY,      MAXINTOBJCOLS.CHANGEDATE,      MAXINTOBJCOLS.MAXINTOBJCOLSID    )  VALUES    (      'EIP_FAILURE',      'FAILURELIST',      'FAILURELIST',      'NONRESTRICTED',      'MAXADMIN',      TO_DATE ('04/28/2025 05:51:46 PM',           'MM/DD/YYYY HH12:MI:SS AM'),      18472    )/

Once that row exists telling it that FAILURELIST attribute is  'NONRESTRICTED' you will then be able to move the Restricted setting on the Inbound Settings and make the FAILURELISTR Override in fact I make all the attributes on the FAILURELIST MBO Override including PARENT . My inbound settings can look like this:



At this point you can use MxLoader to load a hierarchy if you have your FALURELIST and PARENT id values set to appropriate numeric values building a full hierarchy. In my case I pull it out of a 7.6 env and it came out with the appropriate values in there. Note that you must get the FAILURECODES in standalone before doing the FAILURECLASS and PROBLEM, CAUSE and REMEDY values.

Anyway, hope this helps others in future to solve this problem in a MAS 9 environment. Shame IBM will not acknowledge it as an bug and fix it.  Also, I assume the Application Import and Export will work with these setting now if you use this OS and have appropriate values in the XML or JSON. Also, assume REST API will work if you have values as well

Good luck,

------------------------------
David Miller
Managing Partner - Maximo Consultant
Enterprise Integration Partners LLC

Original Message:
Sent: Mon April 28, 2025 03:38 PM
From: David Miller
Subject: MAS 9 FAILURE HIERARCHY LOAD WITH MXLOADER?

IBM Response about trying to create an OS that will load Failure Hierarchy in MAS 9. I have tried Mxloader, REST API and Application Import/Export all with no success now:

Hi David

Unfortunately we do not have OOTB objects to support the process so you may need to build you own customer

to include all objects you planning to load , it may require the custom processing class to.

I have run this by dev and that what they said, sorry

My Response to them:

------------------------------
David Miller
Managing Partner - Maximo Consultant
Enterprise Integration Partners LLC

Original Message:
Sent: Thu April 24, 2025 05:54 PM
From: David Miller
Subject: MAS 9 FAILURE HIERARCHY LOAD WITH MXLOADER?

I am having a heck of a time trying to get a medium sized Failure Hierarchy to load into a MAS 9 environment using MxLoader.

I first hit the issue that the NextGen MxLoader does not support the MXL_FAILURELIST. So I move back to 6.2 and then find that I cannot connect to MAS in 6.2.

Once I finally got REST connections working (in 8.4) after looking on various threads and trying to do a custom OS with FAILURELIST and FAILURECODE I could not get it to work to save my life.

My biggest issue is that I cannot find a way to OVERRIDE the FAILURELIST value as it goes into MBO and as such it generates its own new sequence values when I load. I need the values to stay what I want to be able to load a hierarchy I have already created. Anybody have the solution to this issue? The override cannot be selected in the OS definition. I have the data in a 7.6.1.3 env to pull out and want to move it with the same values to the new environment.

So, what I have got somewhat working is to use single MBO OS's one for FAILURECODE (MXL_FAILURECODE). And then my own OS with just FAILURELIST to do the FAILURECLASS load and then I use the OOTB - MXAPIFAILURELIST to load the PROBLEM,CAUSE and REMEDY.  But the hassle is I must find the newly generated PARENT values for the PROBLEM, CAUSE and REMEDY and that is a MAJOR hassle since they are multiple levels deep and very complex to get the PARENT value on each of those codes going in.

I cannot believe there is not an easier way to load a full hierarchy. I see why Bruno stopped supporting it in the NextGen API as it looks really complicate to achieve.

Anybody have any advice to provide or how they were able to do it?

Thanks,

------------------------------
David Miller
Managing Partner - Maximo Consultant
Enterprise Integration Partners LLC
------------------------------