IBM Support

PH27783: SERVICE FOR Z/OS DEBUGGER 14.1.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • z/OS Debugger service for
    IBM Developer for z/OS Enterprise Edition 14.1.12
     IBM Developer for z/OS 14.1.12
     IBM Debug for z/OS 14.1.12
    
    
    --- Service ---
    
    -The debugger doesn't stop in the second EC LINK PROGRAM to a
     LE assembler module.
     (PI50210 at 14.1)
    
    -Remote debug:  If an IGZEOPT CSECT is link-edited with a COBOL
     V5/V6 main, it causes IGZ0014W 'IGZEOPT is ignored' condition
     to be raised.  A Program Check at EQA0SDU+x'0872' is seen.
     (PH21857 at 14.1)
    
    -Incorrect location displayed for COBOL V6.2 side file in
     debugger Source Identification panel.  This happens for
     programs compiled with TEST(SEPARATE).
     (PH27129 at 14.1)
    
    -In IBM Debugger for z System, there are multiple places where
     storage leaks are occurring with the use of watch breakpoints.
     The storage leaks would happen for any watch breakpoint that
     contains either a conditional expression or a level 88
     variable.
     (PH27155 at 14.1)
    
    -Customers who use EQAUEDAT to provide a DEBUG file location
     and use an EQAUEDAC compiled with COBOL V5+ will see that the
     EQAUEDAT did not work properly and the debugger did not start.
    
     eqaw.SEQASAMP(EQAUEDAC) is the COBOL version of the assembler
     eqaw.SEQASAMP(EQAUEDAT).
    
     (PH28745 at 14.2)
    
     To complete this fix, the PTF for PH30064 for z/OS 2.3 or 2.4
     Language Environment is also needed.  The PTFs can be put on
     independently of each other.
    
    -IMS control region may issue pairs of messages "EQA9999I
     Cannot find IMS region". The messages are produced by internal
     tracing, which tries to locate an IMS isolation entry on a
     code branch that does not set the IMS id.
    
     The fix removes tracing calls from the branch where IMS id is
     not set.
    
     (PH30647 at 14.1)
    
    -Debugger is looping after its task was purged in CICS.
    
     The problem occurs in CICS when dual terminal mode is used.
     Scenario is this:  DTCN is used to set up dual terminal to
     stop in a COBOL program.  The terminal id for the debug
     session is available, but not in use (no one has signed on to
     it).  Start the transaction. CICS will issue an abend. Because
     LE TRAP option is TRAP(OFF) the debugger starts up.  But since
     no one is signed onto the terminal, CICS waits.
    
     CEMT SET PURGE TASK is done. The debugger is called to
     terminate, but starts looping.
    
     (PH31213 at 14.1)
    
    -Terminal Interface Monitor (TIM) ABENDS0C1 or ABENDS0C4 when a
     terminal disconnects.
     (PH31751 at 14.1)
    
    -When running SEQASAMP(EQAWTIMS),  the following messages are
     displayed.
    
     IEW2400I 5D10 A REQUEST TO DELETE CSECT OR SYMBOL DFSCSIF0 WAS
     RECEIVED, AND THE CSECT OR SYMBOL WAS NOT FOUND
     IEW2400I 5D10 A REQUEST TO DELETE CSECT OR SYMBOL DFSCSII0 WAS
     RECEIVED, AND THE CSECT OR SYMBOL WAS NOT FOUND.
    
     These informational messages don't affect a normal run of the
     job.
    
     The first message is from  the first step of the job that link
     edits the EQATIEDT user exit (transaction message edit).
    
     The second message is from the second step of the job that
     link edits the EQATIEXT(alias DFSMSCE0) user exit (transaction
     routing).
    
     They both are in response to the REPLACE  DFSCSII0,DFSCSIF0
     link edit statement In both steps.
    
     EQATIEDT has entry point DFSCSII0, doesn't have entry point
     DFSCSIF0.
     EQATIEXT has entry point DFSCSIF0, doesn't have entry point
     DFSCSII0.
    
     To eliminate these messages, the fix removes unnecessary names
     on the REPLACE statements.
    
    -When a COBOL V4 program is the main program, and a session
     variable is created by a z/OS Debugger command, there is a
     ABENDS0C4 abend in EQA00DCL+'1D0A'x when a COBOL V5 or V6
     program is called.
     (PH32942 at 15.0)
    
    -A debug session for a DB2 stored procedure displays "SOURCE:
     UNKNOWN?" when the stored procedure is a Cobol V5+ main
     program invoked by a secondary entry point. This also happens
     outside of DB2 when CEEPIPI Call_main of a Cobol V5+ program
     uses a secondary EP.
     (PH33168 at 14.1)
    
    -Remote debug: EQA2302E message in Japanese is garbled.
     (PH33160 at 14.1)
    
    -Loop in EQA00DTA in CICS region after QUIT command issued
     during debugging of a mix of COBOL and non-LE assembler.
     Problem occurs after QUIT ABEND or QQUIT command on CICS when
     stopped in a COBOL program and there are non-LE asm LINK
     levels active. Normally the transaction should end with a 4038
     abend.  In this case, could be a loop or other kinds of
     abends.
     (PH33738 at 14.1)
    
    -In CICS, when debugging Enterprise COBOL V5+ with debug data
     in the program object, the debugger shows "location unknown"
     after a STEP or GO into a NOTEST program.
     (PH34567 at 14.1)
    
    -ABEND U4036 reason=00000004 in EQA00OHH.
     Debugger's SVC screening intercepted a LOAD svc issued by LE
     ESPIE exit. EQA00OHH set a shunt for ApplR4Bad counting on
     protection by an existing ESPIE. Since it was running under an
     ESPIE exit, its own program check caused a percolation and an
     abend U4036-4.
     (PH35357 at 14.1)
    
    -Error in debugger's ESPIE exit, EQA00OHI, caused abnormal end
     of debugging session
    
     Debugger's ESPIE exit, EQA00OHI, at label ReallyPercolate
     deleted the ESPIE environment, intending to percolate the
     error.
    
     The return from OHI is SVC3 (EXIT macro), which in the absence
     of an ESPIE environment terminated the current RB and returned
     to its caller with OHI's registers. The calling program then
     made a wild branch and abended with S30A-14. Other abends are
     possible since there was a wild branch.
    
     ESPIE environment should not be deleted from inside an ESPIE
     exit.
    
     (PH35469 at 14.1)
    
    -Debugger does not stop / break in statically linked Enterprise
     COBOL V5+ subprograms compiled with TEST that puts the debug
     data in the program object and linked with PAGE.
    
     Message EQA4092E is now issued in this case.
    
     EQA4092E
              The COBOL program CUName is in a load module
              link-edited with the binder PAGE statement.
    
     Explanation
               The debug information for the COBOL program cannot
               be located in the load module because the load
               module was link-edited with the binder PAGE
               statement. The problem can occur for a COBOL program
               compiled with COBOL V5 with the TEST compiler option
               or for a COBOL program compiled with COBOL V6 or
               higher with the TEST(NOSEPARATE) compiler option.
    
     Programmer response
               Link-edit the load module without the binder PAGE
               statement or compile the program with the compiler
               option TEST(SEPERATE).
    
     (PH35413 at 14.1)
    
    -Remote debug ABENDS0C4 EQA00QNS+x'35C8' when Enterprise COBOL
     V5+ and more than one paragraph name at the same offset. For
     example:
    
            LABEL-00000001-AAAAAAAA.
                If work-value = 00000001 Then
                  move "00000001" to output-value
                End-If.
            LABEL-00000001-BBB.
            LABEL-00000001-CCC.
            LABEL-00000001-DDD.
            LABEL-00000001-EEE.
    
     (PH36249 at 14.1)
    
    -In CICS, doing code coverage on a mix of COBOL V4 and V5+ may
     result in an ASRA ABENDS0C1 branch to zero at
     EQA00GDF+x'1426'.
     (PH36773 at 14.1)
    
    
    For COBOL V5 and V6 usages above:
    FIXCAT KEYWORD: COB0501T/K COB0502T/K
                    COB0601T/K COB0602T/K COB0603T/K
    
    For z/OS Debugger:
    FIXCAT KEYWORD: DEBUGGER/K
    
    --- End Service ---
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * z/OS Debugger 14.1 users who have the problems described in  *
    * the Problem Description.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * z/OS Debugger service for                                    *
    *  IBM Developer for z/OS                                      *
    *  Enterprise Edition 14.1.12                                  *
    *  IBM Developer for z/OS 14.1.12                              *
    *  IBM Debug for z/OS 14.1.12                                  *
    *                                                              *
    *                                                              *
    * --- Service ---                                              *
    *                                                              *
    * -The debugger doesn't stop in the                            *
    *  second EC LINK PROGRAM to a LE                              *
    *  assembler module.                                           *
    *  (PI50210 at 14.1)                                           *
    *                                                              *
    * -Remote debug:  If an IGZEOPT CSECT is                       *
    *  link-edited with a COBOL V5/V6 main,                        *
    *  it causes IGZ0014W 'IGZEOPT is                              *
    *  ignored' condition to be raised.  A                         *
    *  Program Check at EQA0SDU+x'0872' is                         *
    *  seen.                                                       *
    *  (PH21857 at 14.1)                                           *
    *                                                              *
    * -Incorrect location displayed for                            *
    *  COBOL V6.2 side file in debugger                            *
    *  Source Identification panel.  This                          *
    *  happens for programs compiled with                          *
    *  TEST(SEPARATE).                                             *
    *  (PH27129 at 14.1)                                           *
    *                                                              *
    * -In IBM Debugger for z System, there                         *
    *  are multiple places where storage                           *
    *  leaks are occurring with the use of                         *
    *  watch breakpoints.  The storage leaks                       *
    *  would happen for any watch breakpoint                       *
    *  that contains either a conditional                          *
    *  expression or a level 88 variable.                          *
    *  (PH27155 at 14.1)                                           *
    *                                                              *
    * -Customers who use EQAUEDAT to provide                       *
    *  a DEBUG file location and use an                            *
    *  EQAUEDAC compiled with COBOL V5+ will                       *
    *  see that the EQAUEDAT did not work                          *
    *  properly and the debugger did not                           *
    *  start.                                                      *
    *                                                              *
    *  eqaw.SEQASAMP(EQAUEDAC) is the COBOL                        *
    *  version of the assembler                                    *
    *  eqaw.SEQASAMP(EQAUEDAT).                                    *
    *                                                              *
    *  (PH28745 at 14.2)                                           *
    *                                                              *
    *  To complete this fix, the PTF for                           *
    *  PH30064 for z/OS 2.3 or 2.4 Language                        *
    *  Environment is also needed.  The PTFs                       *
    *  can be put on independently of each                         *
    *  other.                                                      *
    *                                                              *
    * -IMS control region may issue pairs of                       *
    *  messages "EQA9999I Cannot find IMS                          *
    *  region". The messages are produced by                       *
    *  internal tracing, which tries to                            *
    *  locate an IMS isolation entry on a                          *
    *  code branch that does not set the IMS                       *
    *  id.                                                         *
    *                                                              *
    *  The fix removes tracing calls from                          *
    *  the branch where IMS id is not set.                         *
    *                                                              *
    *  (PH30647 at 14.1)                                           *
    *                                                              *
    * -Debugger is looping after its task                          *
    *  was purged in CICS.                                         *
    *                                                              *
    *  The problem occurs in CICS when dual                        *
    *  terminal mode is used. Scenario is                          *
    *  this:  DTCN is used to set up dual                          *
    *  terminal to stop in a COBOL program.                        *
    *  The terminal id for the debug session                       *
    *  is available, but not in use (no one                        *
    *  has signed on to it).  Start the                            *
    *  transaction. CICS will issue an                             *
    *  abend. Because LE TRAP option is                            *
    *  TRAP(OFF) the debugger starts up.                           *
    *  But since no one is signed onto the                         *
    *  terminal, CICS waits.                                       *
    *                                                              *
    *  CEMT SET PURGE TASK is done. The                            *
    *  debugger is called to terminate, but                        *
    *  starts looping.                                             *
    *                                                              *
    *  (PH31213 at 14.1)                                           *
    *                                                              *
    * -Terminal Interface Monitor (TIM)                            *
    *  ABENDS0C1 or ABENDS0C4 when a                               *
    *  terminal disconnects.                                       *
    *  (PH31751 at 14.1)                                           *
    *                                                              *
    * -When running SEQASAMP(EQAWTIMS),  the                       *
    *  following messages are displayed.                           *
    *                                                              *
    *  IEW2400I 5D10 A REQUEST TO DELETE                           *
    *  CSECT OR SYMBOL DFSCSIF0 WAS                                *
    *  RECEIVED, AND THE CSECT OR SYMBOL WAS                       *
    *  NOT FOUND                                                   *
    *  IEW2400I 5D10 A REQUEST TO DELETE                           *
    *  CSECT OR SYMBOL DFSCSII0 WAS                                *
    *  RECEIVED, AND THE CSECT OR SYMBOL WAS                       *
    *  NOT FOUND.                                                  *
    *                                                              *
    *  These informational messages don't                          *
    *  affect a normal run of the job.                             *
    *                                                              *
    *  The first message is from  the first                        *
    *  step of the job that link edits the                         *
    *  EQATIEDT user exit (transaction                             *
    *  message edit).                                              *
    *                                                              *
    *  The second message is from the second                       *
    *  step of the job that link edits the                         *
    *  EQATIEXT(alias DFSMSCE0) user exit                          *
    *  (transaction routing).                                      *
    *                                                              *
    *  They both are in response to the                            *
    *  REPLACE  DFSCSII0,DFSCSIF0 link edit                        *
    *  statement In both steps.                                    *
    *                                                              *
    *  EQATIEDT has entry point DFSCSII0,                          *
    *  doesn't have entry point DFSCSIF0.                          *
    *  EQATIEXT has entry point DFSCSIF0,                          *
    *  doesn't have entry point DFSCSII0.                          *
    *                                                              *
    *  To eliminate these messages, the fix                        *
    *  removes unnecessary names on the                            *
    *  REPLACE statements.                                         *
    *                                                              *
    * -When a COBOL V4 program is the main                         *
    *  program, and a session variable is                          *
    *  created by a z/OS Debugger command,                         *
    *  there is a ABENDS0C4 abend in                               *
    *  EQA00DCL+'1D0A'x when a COBOL V5 or                         *
    *  V6 program is called.                                       *
    *  (PH32942 at 15.0)                                           *
    *                                                              *
    * -A debug session for a DB2 stored                            *
    *  procedure displays "SOURCE:                                 *
    *  UNKNOWN?" when the stored procedure                         *
    *  is a Cobol V5+ main program invoked                         *
    *  by a secondary entry point. This also                       *
    *  happens outside of DB2 when CEEPIPI                         *
    *  Call_main of a Cobol V5+ program uses                       *
    *  a secondary EP.                                             *
    *  (PH33168 at 14.1)                                           *
    *                                                              *
    * -Remote debug: EQA2302E message in                           *
    *  Japanese is garbled.                                        *
    *  (PH33160 at 14.1)                                           *
    *                                                              *
    * -Loop in EQA00DTA in CICS region after                       *
    *  QUIT command issued during debugging                        *
    *  of a mix of COBOL and non-LE                                *
    *  assembler.  Problem occurs after QUIT                       *
    *  ABEND or QQUIT command on CICS when                         *
    *  stopped in a COBOL program and there                        *
    *  are non-LE asm LINK levels active.                          *
    *  Normally the transaction should end                         *
    *  with a 4038 abend.  In this case,                           *
    *  could be a loop or other kinds of                           *
    *  abends.                                                     *
    *  (PH33738 at 14.1)                                           *
    *                                                              *
    * -In CICS, when debugging Enterprise                          *
    *  COBOL V5+ with debug data in the                            *
    *  program object, the debugger shows                          *
    *  "location unknown" after a STEP or GO                       *
    *  into a NOTEST program.                                      *
    *  (PH34567 at 14.1)                                           *
    *                                                              *
    * -ABEND U4036 reason=00000004 in                              *
    *  EQA00OHH.  Debugger's SVC screening                         *
    *  intercepted a LOAD svc issued by LE                         *
    *  ESPIE exit. EQA00OHH set a shunt for                        *
    *  ApplR4Bad counting on protection by                         *
    *  an existing ESPIE. Since it was                             *
    *  running under an ESPIE exit, its own                        *
    *  program check caused a percolation                          *
    *  and an abend U4036-4.                                       *
    *  (PH35357 at 14.1)                                           *
    *                                                              *
    * -Error in debugger's ESPIE exit,                             *
    *  EQA00OHI, caused abnormal end of                            *
    *  debugging session                                           *
    *                                                              *
    *  Debugger's ESPIE exit, EQA00OHI, at                         *
    *  label ReallyPercolate deleted the                           *
    *  ESPIE environment, intending to                             *
    *  percolate the error.                                        *
    *                                                              *
    *  The return from OHI is SVC3 (EXIT                           *
    *  macro), which in the absence of an                          *
    *  ESPIE environment terminated the                            *
    *  current RB and returned to its caller                       *
    *  with OHI's registers. The calling                           *
    *  program then made a wild branch and                         *
    *  abended with S30A-14. Other abends                          *
    *  are possible since there was a wild                         *
    *  branch.                                                     *
    *                                                              *
    *  ESPIE environment should not be                             *
    *  deleted from inside an ESPIE exit.                          *
    *                                                              *
    *  (PH35469 at 14.1)                                           *
    *                                                              *
    * -Debugger does not stop / break in                           *
    *  statically linked Enterprise COBOL                          *
    *  V5+ subprograms compiled with TEST                          *
    *  that puts the debug data in the                             *
    *  program object and linked with PAGE.                        *
    *                                                              *
    *  Message EQA4092E is now issued in                           *
    *  this case.                                                  *
    *                                                              *
    *  EQA4092E                                                    *
    *           The COBOL program CUName is                        *
    *           in a load module link-edited                       *
    *           with the binder PAGE                               *
    *           statement.                                         *
    *                                                              *
    *  Explanation                                                 *
    *            The debug information for                         *
    *            the COBOL program cannot be                       *
    *            located in the load module                        *
    *            because the load module was                       *
    *            link-edited with the binder                       *
    *            PAGE statement. The problem                       *
    *            can occur for a COBOL                             *
    *            program compiled with COBOL                       *
    *            V5 with the TEST compiler                         *
    *            option or for a COBOL                             *
    *            program compiled with COBOL                       *
    *            V6 or higher with the                             *
    *            TEST(NOSEPARATE) compiler                         *
    *            option.                                           *
    *                                                              *
    *  Programmer response                                         *
    *            Link-edit the load module                         *
    *            without the binder PAGE                           *
    *            statement or compile the                          *
    *            program with the compiler                         *
    *            option TEST(SEPERATE).                            *
    *                                                              *
    *  (PH35413 at 14.1)                                           *
    *                                                              *
    * -Remote debug ABENDS0C4                                      *
    *  EQA00QNS+x'35C8' when Enterprise                            *
    *  COBOL V5+ and more than one paragraph                       *
    *  name at the same offset. For example:                       *
    *                                                              *
    *  LABEL-00000001-AAAAAAAA.                                    *
    *      If work-value = 00000001 Then                           *
    *        move "00000001" to output-value                       *
    *      End-If.                                                 *
    *  LABEL-00000001-BBB.                                         *
    *  LABEL-00000001-CCC.                                         *
    *  LABEL-00000001-DDD.                                         *
    *  LABEL-00000001-EEE.                                         *
    *                                                              *
    *  (PH36249 at 14.1)                                           *
    *                                                              *
    *  -In CICS, doing code coverage on a mix                      *
    *  of COBOL V4 and V5+ may result in an                        *
    *  ASRA ABENDS0C1 branch to zero at                            *
    *  EQA00GDF+x'1426'.                                           *
    *  (PH36773 at 14.1)                                           *
    *                                                              *
    *                                                              *
    * For COBOL V5 and V6 usages above:                            *
    * FIXCAT KEYWORD:                                              *
    *   COB0501T/K COB0502T/K                                      *
    *   COB0601T/K COB0602T/K COB0603T/K                           *
    *                                                              *
    * For z/OS Debugger:                                           *
    * FIXCAT KEYWORD: DEBUGGER/K                                   *
    *                                                              *
    * --- End Service ---                                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Installations that need these problem fixes should install   *
    * this service.                                                *
    ****************************************************************
    Miscellaneous service.
    

Problem conclusion

  • Service available.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH27783

  • Reported component name

    ZOS DEBUGGER

  • Reported component ID

    5724T0713

  • Reported release

    E10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-07-23

  • Closed date

    2021-05-10

  • Last modified date

    2021-06-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UI75337

Modules/Macros

  • EQALDR31 EQA04PST EQA10XSC EQA00CVC EQA00POP EQA03PFM EQA0SBKP
    EQAS0GFU EQA00CEC EQA00CUS EQA00CEE EQAS0OHH EQARCEXP EQACSINT
    EQA00EHI EQA00CTX EQAS0DU  EQAS0DBH EQAS0OHC EQAS0DBJ EQASYCUS
    EQA00STO EQA08PFM EQAS0DBG EQAEVDBG EQA00GLV EQA00TVT EQA01TSR
    EQARCCDA EQA00STT EQA00STU EQA00CCV EQASPDBI EQA00XML EQA00CCX
    EQA10PRC EQA05CUS EQA0SMSU EQA0SUT1 EQA00EHB EQA02BLK EQAS0BND
    EQA0SUT2 EQANCEST EQAS0HKS EQAS0HKN EQADCDEL EQA00NML EQA10OSM
    EQA0CFUN EQA00REG EQA00QRY EQAS0OHT EQA0SCLU EQAD3CSR EQAS0OHV
    EQAS0DSF EQA03BLK EQANCDBG EQAS0INT EQA0AIPD EQAS0MVS EQAMVS31
    EQA00RSV EQA00CEX EQA0AIP2 EQA0AIP1 EQAAFSPS EQADCMGR EQAS0DTL
    EQA08BLK EQAS0EVH EQAS0ANC EQA00SVC EQA00CVT EQA0SBLD EQA00SET
    EQAYBGID EQAS0GIV EQA00ABE EQAS0EH2 EQA00AEI EQACIC32 EQA04CMS
    EQAS0FIN EQA0SDTL EQA07STT EQA10OUT EQAS0DEH EQAS0DEI EQA00PST
    EQA0SRPC EQANMDBG EQAS0SBM EQA0SINP EQA0SLDD EQA00PBK EQACTL
    EQAEV006 EQA00CIC EQAS0QNS EQA0SRQ1 EQA00EMG EQA00RWD EQA01SVC
    EQA0SRQ2 EQA0SRQ3 EQA0SRQ4 EQA00AEH EQAS0STO EQA00FA  EQACIC41
    EQARCI3E EQA05PST EQAS7BLK EQAS0EHI EQA01SV2 EQA04PFM EQAS0EHB
    EQA00LIS EQA00NMU EQAZPCM  EQANCGET EQA00GPA EQANMEST EQA0SEXA
    EQA0SEXE EQA00RES EQA00QCS EQA00CHG EQASAIP1 EQAS0POP EQA00GSV
    EQAS0M99 EQAS0CEE EQASAIP2 EQA00LMS EQA0STRE EQA00TMM EQA05PFM
    EQA0SCPU EQAS0CUS EQA0SUTI EQA0SDBI EQA00PDM EQA00DU  EQA02CUS
    EQAS0STT EQARCVND EQASAIPD EQA00QFY EQA0CINF EQA00LLF EQA00LLH
    EQA0SCBP EQANCFRM EQA00ENV EQANIPSB EQAS0SET EQA02STT EQAS0ABE
    EQA00LLT EQA50VAT EQANCFRE EQA0SBPP EQA07CUS EQA00DLD EQA00CV
    EQA04BLK EQADCCXR EQADCREP EQA0SRP1 EQA10CND EQA0SRP2 EQA0SRP3
    EQA0SLCM EQA0SRP4 EQA00LLC EQACSSIF EQADCCN1 EQADCVSA EQA00BKP
    EQADCCN0 EQADFHNO EQA10LST EQA03STT EQA00OEH EQA00OEI EQARCPDC
    EQARCOBD EQA00GDV EQA05BLK EQA08CUS EQA00ER0 EQA00ER1 EQA00LNG
    EQA0YCUS EQA00GDD EQA00VAR EQARCHEX EQA00GDF EQA00GDG EQA08STT
    EQA00GDP EQASSUT1 EQAS0QCS EQA00FRE EQA00NAM EQAS0NMU EQA00TMX
    EQA00GTO EQAS0REG EQA0SXR1 EQA10XIF EQANCHAB EQATIEXT EQAS0PST
    EQA0SEXN EQACIC51 EQA0SEXP EQA0SIPD EQA0XCUS EQAS7CUS EQA0OIP1
    EQA0PDBI EQA0OIP2 EQASG006 EQA0SEXU EQA02PST EQANISET EQAS0EMG
    EQAS0RWD EQA00GFU EQA00GFV EQANCRTO EQA10MG0 EQA10MG1 EQAL6Z3
    EQA07PST EQAL6Z6  EQA10MVS EQAW3Z3  EQA10BPR EQAW3Z6  EQANCREL
    EQA0SRSM EQA00CND EQA00BLD EQA10DTL EQA0SDU  EQA03CUS EQA50XIO
    EQAS7STT EQA00BLK EQA0SDLD EQA00HKN EQA08PST EQA10M99 EQASXCUS
    EQA0SRGU EQA00DCL EQA00LST EQANICTL EQAS0OSM EQA00HKS EQADCTSQ
    EQA00DTA EQA00DTC EQA00TSR EQA00GIV EQA00LBL EQA00DSF EQA00OHT
    EQANBSWT EQA00OHV EQA00LSE EQA04CUS EQA0SXU1 EQACMDRV EQA00DBG
    EQANCABE EQA00DBH EQA00OHC EQA00DBI EQA00DBJ EQA00OHE EQARCTRC
    EQA04STT EQA00OHH EQA00OHI EQA0SQFY EQAS0GTO EQAS0LNG EQA00OHL
    EQA04API EQA00BND EQA00LAM EQAS0NAM EQA0SCHG EQA03ASN EQA00LRC
    EQA00E40 EQAS0LMS EQA00E41 EQA00TRA EQA0SXUT EQA00ALO EQA00DEH
    EQAD3PXT EQA00DEI EQA00FIN EQAMVS64 EQA00EH2 EQA05STT EQAIIRMG
    EQA00EXE EQA0SCL2 EQA0SCL1 EQAXPL31 EQA00QNS EQA02PFM EQADCXXT
    EQANCCSE EQARCDBG EQA00LDR EQA07BLK EQANICRT EQA0SXRI EQAS7PST
    EQA00LDU EQA02LOC EQA00SBM EQAS0GDV EQA10QRY EQAD3XXT EQANXPOP
    EQAWTIMS EQANCLDE EQAS0GDP EQAYBCNM EQAYSMMN EQALDR64 EQA00LDD
    EQA00TTL EQANCTER EQA03PST EQA00INT EQARCL4  EQA00MEM EQA00ANC
    EQA00LCM EQAS0BLK EQA00EVH EQA00DTL EQALMA   EQA0STKH EQAS0CND
    EQA00ANL EQA50VIO EQA00BPP EQA00RPB
    

Fix information

  • Fixed component name

    ZOS DEBUGGER

  • Fixed component ID

    5724T0713

Applicable component levels

[{"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSJK49","label":"IBM Developer for z Systems"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"E10"}]

Document Information

Modified date:
25 June 2022