APAR status
Closed as program error.
Error description
Using System exception destination for Sequential Outbound queue doesn't work as expected When using the System exception destination so that if an error occurs and the message cannot be delivered, the message will be moved into the system exception destination and the next message can be processed. However the message is not being moved to the system exception destination - the message just disappears (it's not in the sqout queue either) and the next message is not being processed.
Local fix
Problem summary
Problem conclusion
The fix for this APAR is contained in the following maintenancepackage: Release 7.6.1.3 of Base Services
Temporary fix
Comments
APAR Information
APAR number
IJ38814
Reported component name
INTEGRATION
Reported component ID
5724R46I1
Reported release
761
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2022-03-17
Closed date
2022-03-25
Last modified date
2022-03-25
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
INTEGRATION
Fixed component ID
5724R46I1
Applicable component levels
[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761"}]
Document Information
Modified date:
26 March 2022