APAR status
Closed as duplicate of another APAR.
Error description
An application probram abends. Fault Analyzer invoked and a fault ID assigned. There are no error messages in JES log. The entry shows up in The Fault Entry List, but no data is in the entry. The abend code showing in the fault entry is U4038. However, the JES log shows U0241, SD37, U4093 reason code 0000001C (storage problem). Since no IDI error messages were seen, the client expected something in the fault entry. When typing 4 by the fault entry and pressing Enter, the Interactive Reanalysis Report appears. Just under Fault Summary, we see: "No abend could be determined--possible loop or wait situation."
Local fix
n/a
Problem summary
Problem conclusion
Temporary fix
Comments
COMMENTS.1 This APAR is a duplicate of PM96424
APAR Information
APAR number
PM95415
Reported component name
FAULT ANALYZER
Reported component ID
5655W4600
Reported release
B10
Status
CLOSED DUB
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-08-19
Closed date
2013-10-02
Last modified date
2013-10-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B10","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSXJAJ","label":"Fault Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B10","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
02 October 2013