A fix is available
APAR status
Closed as program error.
Error description
--- Service --- -Exception in EQA00ANC with Smart/Restart. (PI56113 at 13.1) -Debug Tool not starting up in remote debug session when using delay debug. EQA9999W - FeName=EQACSMTP Loc=230 Func=SHUTDO Rc=-1 Fc=10108 (PI82494 at 13.1) -Debug Tool IMS Transaction Isolation Facility abend in DFSMSCE0+'058A'x with Debug Tool IMS ISO setup active. (PI91350 at 13.1) -If you use an ISPF 0 to set a terminal type of 8. 3277KN or 9. 3278KN (which is a Katakana terminal type) and then go to Debug Tool Utilities option 4 and then 0 you get 2 messages EQAZ037E Invalid keyword INCLUDE found in member 0. INCLUDE ; and then an ISPF DIALOG ERROR error saying VARIABLE 'MPRDEBUG' IS SYNTACTICALLY INCORRECT. on VPUT (MprDebug,MprNoDbg,MprBmp) PROFILE (PI89417 at 14.0) -When creating a Debug Tool IMS Transaction Isolation private message region, the private region is not a clone of the active MPP region. Private region is for Java, where the active MPP is for COBOL. (PI89515 at 13.1) -Add functionality to provide additional Language Environment runtime options for Debug Tool IMS Transaction Isolation Facility private message region on the 'Manage additional libraries and delay debug options' panel. (PI89474 at 13.1) -When using Debug Tool with SET EXPLICITDEBUG ON, unable to view content variables in automonitor of a second Enterprise COBOL V6.1 submodule that is called from a Enterprise COBOL V4.2 main module. FIXCAT KEYWORD: COB0501T/K COB0502T/K COB0601T/K COB0602T/K (PI89795 at 13.1) -ABENDS0C4 in Debug Tool module EQA00TMM caused ABENDS0C4 in IMS MPR, which in turn caused IMS Control Region to abend with U113. EQA00TMM gets control for an STIMERM exit. Debug Tool is not active when the exit call is made by the Operating System. Debug Tool must have been active when the STIMERM SVC was issued, but out of the picture when the exit was called. Messages include: DFS0613I CTL RGN U113 DUE TO S0C4 U0000 DURING DL/I CALL IN MPP (PI90265 at 13.1) -Configuration via IMS Transaction Isolation option 4.6 was successfull, and now trying to configure the IMS Transaction Isolation with option 4.5,and receive following error screen: 143 +++ Do TranCt=1 To TranBlks IRX0041I Error running EQAXTIMS, line 143: Bad arithmetic conversion -The output from EQANICRT for the stage-1 input macros is incorrect. (PI89515 at 13.1) -ABENDU4088 in assembler session caused by large variable size and smaller STACK init size. (PI91762 at 13.1) -"AT ENTRY entryName" in the remote debugger may not set entry breakpoint as expected when the load module has an alias name. -The JCL analyzer fails to resolve all substitution symbols in DD cards, if the DD cards override a DD in the invoked PROC. -If a DTU user's job card from DTU option 0 contains JES2 control statements, the resulting private MPR JCL is not formatted correctly when the user performs the START action on DTU 4.5. For example, the following DTU 0 input: //USRT001Z JOB MSGLEVEL=(1,1), // TIME=1440,MSGCLASS=H,NOTIFY=&SYSUID. /*JOBPARM SYSAFF=* //* Will result in the following job card: //USRT001Z JOB CLASS=A,MSGCLASS=H,MSGLEVEL=(1,1), // NOTIFY=&SYSUID.JOBPARMSYSAFF=*,REGION=0M,TIME=1440 -LMA (Load Module Analyzer) does not show COMPOPTS or valid LEINFO for COBOL V2/V3/V4 CSECTS if COBOL V5/V6 CSECTS are in the same program object. The problem is related to how the C_CODE and B_TEXT segments are ordered in the program object. FIXCAT KEYWORD: COB0501T/K COB0502T/K COB0601T/K COB0602T/K (PI94034 at 13.1) -STC Userid used in IMS CC scenario instead of Userid associated with the transaction. CCOUTPUT will show Userid which started the IMS region and not the Userid running the transaction. (PI95556 at 13.1) -STEP OVER a PERFORM statement not working for COBOL V5+ programs in Debug Tool. FIXCAT KEYWORD: COB0501T/K COB0502T/K COB0601T/K COB0602T/K (PI95699 at 13.1) -DTU option 2 Debug Tool Setup File (and others that process JCL via the JCL Analyzer, EQASUJCL): When processing JCL which contains a CONTROL-M statement, an error message like CEE0454S The message number 1026 could not be found for facility ID EQA. could be issued, and the JCL is not processed. DTU option 2 Debug Tool Setup File (and others that process JCL via the JCL Analyzer, EQASUJCL): When processing JCL which contains no JOB card, an error message like CEE3204S The system detected a protection exception (System Completion Code=0C4). From entry point DMHGetMessage at compile unit offset +0000011C at entry offset +0000011C at address 2AD3F8DC could be issued, and the JCL is not processed. (PI96647 at 13.1) --- End Service ---
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Debug Tool 13.1 users who have the problems described in the * * Problem Description. * **************************************************************** * PROBLEM DESCRIPTION: * * --- Service --- * * * * -Exception in EQA00ANC with * * Smart/Restart. * * (PI56113 at 13.1) * * * * -Debug Tool not starting up in remote * * debug session when using delay debug. * * EQA9999W - FeName=EQACSMTP Loc=230 * * Func=SHUTDO Rc=-1 Fc=10108 * * (PI82494 at 13.1) * * * * -Debug Tool IMS Transaction Isolation * * Facility abend in DFSMSCE0+'058A'x * * with Debug Tool IMS ISO setup active. * * (PI91350 at 13.1) * * * * -If you use an ISPF 0 to set a * * terminal type of * * 8. 3277KN * * or * * 9. 3278KN * * (which is a Katakana terminal type) * * * * and then go to Debug Tool Utilities * * option 4 and then 0 you get 2 * * messages * * * * EQAZ037E Invalid keyword INCLUDE * * found in member 0. INCLUDE ; * * * * and then an ISPF DIALOG ERROR error * * saying * * * * VARIABLE 'MPRDEBUG' IS SYNTACTICALLY * * INCORRECT. * * * * on * * * * VPUT (MprDebug,MprNoDbg,MprBmp) * * PROFILE * * * * (PI89417 at 14.0) * * * * -When creating a Debug Tool IMS * * Transaction Isolation private message * * region, the private region is not a * * clone of the active MPP region. * * Private region is for Java, where the * * active MPP is for COBOL. * * (PI89515 at 13.1) * * * * -Add functionality to provide * * additional Language Environment * * runtime options for Debug Tool IMS * * Transaction Isolation Facility * * private message region on the 'Manage * * additional libraries and delay debug * * options' panel. * * (PI89474 at 13.1) * * * * -When using Debug Tool with SET * * EXPLICITDEBUG ON, unable to view * * content variables in automonitor of a * * second Enterprise COBOL V6.1 * * submodule that is called from a * * Enterprise COBOL V4.2 main module. * * * * FIXCAT KEYWORD: * * COB0501T/K COB0502T/K * * COB0601T/K COB0602T/K * * * * (PI89795 at 13.1) * * * * -ABENDS0C4 in Debug Tool module * * EQA00TMM caused ABENDS0C4 in IMS MPR, * * which in turn caused IMS Control * * Region to abend with U113. * * EQA00TMM gets control for an STIMERM * * exit. Debug Tool is not active when * * the exit call is made by the * * Operating System. Debug Tool must * * have been active when the STIMERM SVC * * was issued, but out of the picture * * when the exit was called. * * Messages include: * * DFS0613I CTL RGN U113 DUE TO S0C4 * * U0000 DURING DL/I CALL IN MPP * * (PI90265 at 13.1) * * * * -Configuration via IMS Transaction * * Isolation option 4.6 was successfull, * * and now trying to configure the IMS * * Transaction Isolation with option * * 4.5,and receive following error * * screen: * * * * 143 +++ Do TranCt=1 To TranBlks * * * * IRX0041I Error running EQAXTIMS, line * * 143: Bad arithmetic conversion * * * * -The output from EQANICRT for the * * stage-1 input macros is incorrect. * * (PI89515 at 13.1) * * * * -ABENDU4088 in assembler session * * caused by large variable size and * * smaller STACK init size. * * (PI91762 at 13.1) * * * * -"AT ENTRY entryName" in the remote * * debugger may not set entry breakpoint * * as expected when the load module has * * an alias name. * * * * -The JCL analyzer fails to resolve all * * substitution symbols in DD cards, if * * the DD cards override a DD in the * * invoked PROC. * * * * -If a DTU user's job card from DTU * * option 0 contains JES2 control * * statements, the resulting private MPR * * JCL is not formatted correctly when * * the user performs the START action on * * DTU 4.5. For example, the following * * DTU 0 input: * * * * //USRT001Z JOB MSGLEVEL=(1,1), * * // TIME=1440,MSGCLASS=H, * * // NOTIFY=&SYSUID. * * / *JOBPARM SYSAFF=* * * * * * * Will result in the following job * * card: * * * * //USRT001Z JOB CLASS=A,MSGCLASS=H, * * // MSGLEVEL=(1,1), * * // NOTIFY=&SYSUID.JOBPARMSYSAFF=*, * * // REGION=0M,TIME=1440 * * * * -LMA (Load Module Analyzer) does not * * show COMPOPTS or valid LEINFO for * * COBOL V2/V3/V4 CSECTS if COBOL V5/V6 * * CSECTS are in the same program * * object. The problem is related to * * how the C_CODE and B_TEXT segments * * are ordered in the program object. * * * * FIXCAT KEYWORD: * * COB0501T/K COB0502T/K * * COB0601T/K COB0602T/K * * * * (PI94034 at 13.1) * * * * -STC Userid used in IMS CC scenario * * instead of Userid associated with the * * transaction. * * CCOUTPUT will show Userid which * * started the IMS region and not the * * Userid running the transaction. * * (PI95556 at 13.1) * * * * -STEP OVER a PERFORM statement not * * working for COBOL V5+ programs in * * Debug Tool. * * * * FIXCAT KEYWORD: * * COB0501T/K COB0502T/K * * COB0601T/K COB0602T/K * * * * (PI95699 at 13.1) * * * * -DTU option 2 Debug Tool Setup File * * (and others that process JCL via the * * JCL Analyzer, EQASUJCL): * * * * When processing JCL which contains * * a CONTROL-M statement, an error * * message like * * * * CEE0454S The message number 1026 * * could not be found for facility ID * * EQA. * * * * could be issued, and the JCL is not * * processed. * * * * DTU option 2 Debug Tool Setup File * * (and others that process JCL via the * * JCL Analyzer, EQASUJCL): * * * * When processing JCL which contains * * no JOB card, an error message like * * * * CEE3204S The system detected a * * protection exception (System * * Completion Code=0C4). * * From entry point DMHGetMessage at * * compile unit offset +0000011C at * * entry offset +0000011C at address * * 2AD3F8DC * * * * could be issued, and the JCL is not * * processed. * * * * (PI96647 at 13.1) * * * * --- End Service --- * **************************************************************** * RECOMMENDATION: * * Installations that need these problem fixes should install * * this service. * **************************************************************** Miscellaneous service.
Problem conclusion
Problems resolved.
Temporary fix
Comments
APAR Information
APAR number
PI89402
Reported component name
DEBUG TOOL Z/OS
Reported component ID
5655Q1000
Reported release
D10
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-10-27
Closed date
2018-05-15
Last modified date
2018-06-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI55864
Modules/Macros
EQA00BKP EQADCCN0 EQA00CEM EQA00OEH EQA00OEI EQA0SBKP EQA08CUS EQA00CUS EQA00CEE EQA00LNG EQACSINT EQA00EHI EQA00CCV EQA10PRC EQA00FRE EQA00NAM EQA05CUS EQA00EHB EQA00TMX EQA00GTO EQANCHAB EQATIEXT EQA0XCUS EQA00NML EQA00REG EQA00MSG EQANCREL EQA0AIP2 EQA0SRSM EQA00CND EQAAFSPS EQA0SDU EQA03CUS EQA00SVC EQA00CVT EQA00SET EQA00ABE EQA00AEI EQA0SDLD EQA00HKN EQA0SRGU EQA00LST EQA00HKS EQA00DTA EQA00DTC EQA00GIV EQANMDBG EQA00PBK EQA00OHT EQAEV006 EQANBSWT EQA00CIC EQA00OHV EQA04CUS EQA00EMG EQA00RWD EQA0SRQ2 EQA00AEH EQASUER0 EQASUER1 EQA00DBG EQALMBND EQANCABE EQA00DBH EQA00OHC EQA00DBI EQA00DBJ EQA00OHE EQA01SV2 EQA00OHH EQA00OHI EQA0SQFY EQA00OHL EQA00LIS EQA00NMU EQASUJCL EQA0SCHG EQANMEST EQA00RES EQA00CHG EQA00DEH EQA00DEI EQA00EH2 EQA00EXE EQA00LMS EQA0SCL2 EQA0SCL1 EQA00TMM EQA0SDBI EQANICRT EQA00DU EQA02CUS EQANCLDE EQAYSMMN EQA0CINF EQA00LLF EQA0SCBP EQA00LDD EQANCFRM EQANCTER EQA00INT EQANIPSB EQA00MEM EQA00ANC EQA00EVH EQA0SBPP EQA07CUS EQA00DTL EQALMA EQA00CV EQA0SRP1 EQA0SRP2 EQAXSS1 EQAXTU1 EQAXPBLX EQAXPFLX EQAXBTS1 EQAXCCV1 EQAXBPR1 EQAXIIMS EQAXTIMS EQAXBKV1 EQAPMPRG EQAXBTS EQAXIMSP EQAXBFIB EQAXCJ EQAXDSP EQAXFOR EQAXCJ3 EQAXCJ2 EQAXMPRO EQAXMPRS EQAXVARS EQAXMPRX
Fix information
Fixed component name
DEBUG TOOL Z/OS
Fixed component ID
5655Q1000
Applicable component levels
RD10 PSY UI55864
UP18/05/18 P F805 ¢
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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSTQWA","label":"IBM Debug for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"D10","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
04 June 2018