APAR status
Closed as program error.
Error description
ERROR DESCRIPTION: Maximo Formulas Duration function not working for ALN type attributes PROBLEM: In Database Configuration, Add/Modify Formula for Attribute from Database Configuration that is ALN type makes the DURATION function not work as expected in 7.6.1.3 STEPS TO REPRODUCE: In Database Configuration, create the following 3 attributes for the MAXUSER object: BOBDATE1 (TYPE=DATE; LENGTH=4) BOBDATE2 (TYPE=DATE; LENGTH=4) TESTTERMS (TYPE=ALN; LENGTH=50) Configure you changes. Add a new Formula for Attribute as below: OBJECTNAME = MAXUSER ATTRIBUTENAME = BOBDATE2 FORMULA EXPRESSION = BOBDATE1+DURATION(0, 0,TESTTERMS, 0, 0 ,0) ACTIVE= (checked) In Application Designer, ensure that you make the 3 new fields visible on the Users application Save changes Now, go to Users app and test this scenario by doing this. Search for any record and open it on the screen Today's date on the BOBDATE1 field Type 5 in the TESTTERMS field and hit TAB You will notice that instead of the BOBDATE2 field being correctly calculated to a date of 5 days from today's date, it gets a completely different date. This only happens when the TESTTERMS attribute is set to ALN type. If that is set to INTEGER, it works fine. NOTE: Customer said this worked fine in 7.6.1.2, even having the TESTTERMS as ALN type. (Tivoli's process automation engine 7.6.1.2-IFIX20210920-2314) CURRENT ERRONEOUS RESULT: In Database Configuration, Add/Modify Formula for Attribute from Database Configuration that is ALN type makes the DURATION function not work as expected in 7.6.1.3 EXPECTED RESULT: Add/Modify Formula for Attribute works for ALN type and DURATION function ENVIRONMENT (SYSTEM INFO): Tivoli's process automation engine 7.6.1.3-IFIX20230914-0042 Build 20220823-0909 DB Build V7613-344 HFDB Build HF7613-122 IBM Maximo Calibration 7.6.1.0 Build 20220823-0909 DB Build V7600-08 IBM Maximo Application Framework 8.8.0 Build 20220823-1257 DB Build V7600-23 IBM Maximo Asset Management Scheduler 7.6.8.2 Build 20220823-0909 DB Build V7682-23 HFDB Build HF7682-10 IBM Maximo Anywhere 7.6.4.0 Build 20220526_150517-0400 DB Build V7640-12 IBM Maximo for Nuclear Power 7.6.2.0-20230906-1707 Build 20200201-0717 DB Build V7620-50 HFDB Build HF7620-17 IBM Tpae Integration Framework 7.6.1.3 Build 20230913-1052 DB Build V7613-61 IBM Maximo Asset Management 7.6.1.3 Build 20220823-0909 DB Build V7611-01 IoT Connection Utility 7.6.0.4 Build 20220303-1642 DB Build V7604-01 TPAE OSLC Object Structure 7.6.4.0 Build 20220526_150508-0400 DB Build V7640-09 Server OS Linux 3.10.0-1160.31.1.el7.x86_64 Server DB Oracle 19.1 (Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Version 19.20.0.0.0)
Local fix
Problem summary
Problem conclusion
A fix for this APAR will be included in a future release.
Temporary fix
Comments
APAR Information
APAR number
IJ50215
Reported component name
SYSTEM CONFIG
Reported component ID
5724R46S1
Reported release
761
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2024-02-22
Closed date
2024-03-12
Last modified date
2024-03-12
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
SYSTEM CONFIG
Fixed component ID
5724R46S1
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:
01 April 2024