A fix is available
APAR status
Closed as program error.
Error description
Miscellaneous bug fixes.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All Fault Analyzer Version 12 users. * **************************************************************** * PROBLEM DESCRIPTION: 01. MSGIDI0103I when LLA managed load * * module part of analysis. * * APAR PI78886 * * 02. ABEND0C4 in IDISAMAN after S222. * * APAR PI78887 * * 03. "Data set is not a history file" * * message issued incorrectly. * * APAR PI78888 * * 04. Abend S0C4 at xmemmove + X'29C88'. * * APAR PI78889 * * 05. FA does not report COBOL V5/V6 * * Working Storage when NORENT * * compiler option in effect. * * APAR PI78890 * * 06. Loop in IDIXDCAP processing a * * system abend in CICS address space. * * It is also possible to experience * * an ABEND0C1 in IDIXDCAP with this * * problem. * * APAR PI78891 * * 07. IDI0005S when processing COBOL * * listing. * * APAR PI78892 * * 08. Redundant messages for LANG(JPN) * * APAR PI78893 * * 09. IDIALLOC DEST allocates DUMMY * * APAR PI78894 * **************************************************************** * RECOMMENDATION: Apply the provided PTF. * **************************************************************** 01. When an LLA managed load module is part of analysis then a bad concatenation number is used to locate the module data set for the binder. 02. Register not initialized correctly. 03. A migrated data set is part of a VIEW. Attempting to use the VIEW results in a "data set is not a history file" message. 04. Incorrect length used when moving a character string. 05. NORENT static expected from IGZXAPI, but gives rc = -5. 06. Code that sets a base register was bypassed leading to an incorrect branch. 07. One of the processing routines was not FREEing all storage that had been getmained during its processing. 08. Duplicate messages are being output when LANG(JPN) is used. 09. Internal field was too small to receive the specification and triggered a dummy allocation.
Problem conclusion
01. BLDL is used to identify the correct data set for the binder. 02. Register is initialized before referencing storage. 03. Fault Analyzer will now recall the data set before testing the data set characteristics when the data set is defined to a VIEW. 04. The length has been corrected. 05. NORENT static address retrieved from PPA4. 06. Base register is set properly. 07. All storage is now FREEd. 08. Duplicate messages have been removed. 09. IDIALLOC is corrected to allocate the SYSOUT DEST file.
Temporary fix
Comments
APAR Information
APAR number
PI74738
Reported component name
FAULT ANALYZER
Reported component ID
5655W6900
Reported release
C10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-01-10
Closed date
2017-03-28
Last modified date
2017-04-19
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI45944
Modules/Macros
IDICAASM IDICABND IDICADYN IDICAFAT IDICALE IDICALOC IDICASUB IDICCFND IDICISA2 IDICNOTA IDICNOTR IDICOPYR IDICRXDX IDICRXEI IDICRXET IDICRXHC IDICRXLE IDICSDB2 IDICSMF IDICSPC IDICSSRB IDICSVCR IDICSV11 IDICSV12 IDICSV15 IDICUXCS IDICUXWR IDIDA IDIDASUB IDIDATSA IDIDATST IDIECASB IDIGMAIN IDIGUOPT IDIGWEB IDIHPMSG IDIMCICS IDINDEX IDIPADIR IDIPASUB IDIPBRWS IDIPDA IDIPDDIR IDIPDSCU IDIPIPV IDIPIPVS IDIPLT IDIPLTD IDISAMAN IDISAQUE IDISAREQ IDISASUB IDISCJST IDISDB2P IDISDB2S IDISFPEX IDISIFND IDISJL IDISJLD IDISJLOG IDISLEEP IDISLKUP IDISLOG IDISMAIN IDISREG IDISRFRA IDISRFRD IDISROPT IDISSREQ IDISTIME IDISUOPT IDISUPDI IDISVIEW IDISXCFA IDIUOPT IDIUTIL IDIVPCOB IDIXALGL IDIXALOG IDIXASUB IDIXCCEE IDIXCC52 IDIXCEE IDIXCE53 IDIXCE67 IDIXCE68 IDIXCE69 IDIXCM53 IDIXCM67 IDIXCM68 IDIXCM69 IDIXCX52 IDIXCX53 IDIXDCAP IDIXDUMP IDIXFA IDIXIPV IDIXIPV2 IDIXLINK IDIXOPT IDIXSNAP IDIXTSEL
Fix information
Fixed component name
FAULT ANALYZER
Fixed component ID
5655W6900
Applicable component levels
RC10 PSY UI45944
UP17/03/31 P F703
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"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":"C10","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":"C10","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
19 April 2017