APAR status
Closed as program error.
Error description
PROBLEM: After upgrade of Maximo SCCD 7.5 to Maximo 7.6 we experienced a problem with Related Records only displaying one Related Record on the Related Record tab in Service Request. We found that the setting the value in system properties to 1000000 then shows multiple rows. The system property in question is mxe.db.fetchResultStopLimit Setting the value to -1, only shows one related record on SR when creating a Change (CR), if we can cancel the CR, then create a new CR, the new CR record does not show on the related records tab in SR, but it does exist on the database. When we change the value to 1000000, then all related records are shown on the panel. mxe.db.fetchResultStopLimit = -1 mxe.db.fetchStopLimitEnabled = 1 mxe.db.fetchStopExclusion is NULL When set to -1 the limit is supposed to behave as if there is no limit. But instead it acts as if the limit is zero. PERFORMANCE ISSUE: no STEPS TO REPRODUCE: 1) set this system property: mxe.db.fetchResultStopLimit = -1 2) in a ticket app (SR, Inc, Problem) create a ticket. Then create three related records of type Change or WO from it. I created a SR with 3 Change records. 3) notice that only the first of the related records shows up on the Related Record tab of the SR in the "Related Work Orders" table. <<< 4) - I also created a Change with 3 related SRs. The Change app correctly shows all the SRs. - I also created a Change with 3 related WOs and that too was correct. - I create a SR with 3 Incidents and that shows correctly (that is, the issue in the tickets is only with the Related WO table, and not with the Related Tickets table - I then tried on a TPAE only machine and found their SR app behaves the same as ours (broken) and their WO app functions correctly. CURRENT ERRONEOUS RESULT: Only the first of multiple related tickets rows shows up. EXPECTED RESULT: All of them should show up. All rows. ADDITIONAL INFO: none ENVIRONMENT: - SCCD: 7601 and 76 - TPAE: 7603 and 7601
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Users with mxe.db.fetchresultstoplimit set to -1 * **************************************************************** * PROBLEM DESCRIPTION: * * When mxe.db.fetchresultstoplimit is set to -1, and multiple * * related records are created against a single WO or SR, only * * the first one can be viewed through the Related Records tab. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
This is a duplicate of IV94242, and is resolved by that APAR.
Temporary fix
Comments
APAR Information
APAR number
IV94286
Reported component name
ADMINISTRATION
Reported component ID
5724R46A1
Reported release
760
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-03-15
Closed date
2017-03-27
Last modified date
2017-03-27
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
ADMINISTRATION
Fixed component ID
5724R46A1
Applicable component levels
R760 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPP5","label":"System Related"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
27 March 2017