Hi Cameron, check  the APAR PI65115 for COBOL 5.2     

  Release 52H   : UI39595 available 16/07/29 (F607 )
  Release 520   : UI39594 available 16/07/29 (F607 )
  Release 521   : UI39596 available 16/07/29 (F607 )
  Release 522   : UI39597 available 16/07/29 (F607 )

And 
APAR Identifier ...... PI68274      Last Changed ........ 16/10/03
  WRITING BEYOND THE END OF A TABLE IN V5.X CAN CORRUPT INDEX
      NAMES IN THAT TABLE.
 
  Symptom ...... AB ABEND             Status ........... CLOSED  PER
  Severity ................... 4      Date Closed ......... 16/09/08
  Component .......... 5655EC600      Duplicate of ........
  Reported Release ......... 610      Fixed Release ............ 999
  Component Name ENT COBOL FOR Z      Special Notice
  Current Target Date ..16/09/16      Flags
  SCP ...................
  Platform ............
 
  Status Detail: SHIPMENT - Packaged solution is available for
                            shipment.
 
  PE PTF List:
 
  PTF List:
  Release 610   : UI40709 available 16/09/24 (F609 )

For Cobol 6.1 

Roland

-----Ursprüngliche Nachricht-----
Von: IBM Mainframe Discussion List [mailto:[email protected]] Im Auftrag 
von Cameron Conacher
Gesendet: Montag, 9. Januar 2017 20:39
An: [email protected]
Betreff: Re: COBOL5 and ceedump

Hello everyone,
Does anyone know if this APAR is available for COBOL 5.2 and if it is available 
for COBOL 6.1?
I mean, would a specific APAR even be need for COBOL 6.1? Or would this APAR 
(PI65115) be part of the original 6.1 distribution?

Thank you,

.......Cameron

On Sun, Jan 8, 2017 at 12:48 PM, Roland Schiradin <[email protected]>
wrote:

> Hi Steff,
>
> depending on your service level the index is defined in front of the 
> array. Look at this APAR text
>
> Starting with COBOL V5.1, index-names were located in memory
>   immediately following the memory for the associated table,
>   which meant that programs that modify dsta beyond the end of a
>   table could corrupt their associated index-names.
>
>
>
>   PROBLEM CONCLUSION:
>   Index-names for tables defined in WORKING-STORAGE or
>   LOCAL-STORAGE sections have been moved to the top of the
>   associated storage area.
>
> HTH Roland
>
>
> -----Ursprüngliche Nachricht-----
> Von: IBM Mainframe Discussion List [mailto:[email protected]] 
> Im Auftrag von Steff Gladstone
> Gesendet: Sonntag, 8. Januar 2017 17:51
> An: [email protected]
> Betreff: COBOL5 and ceedump
>
> Are there any whizzes out there who specialize in reading and 
> deciphering CEEDUMPs?
> I have a question for you.  In a COBOL5  CEEDUMP, how do I locate the
> *index* of an array (i.e., an array that is defined with "indexed by") 
> in the dump?
>
> Thanks in advance,
> Steff Gladstone
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to