URL to the APAR please?  Google cannot find it.

Peter

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Peter Hunkeler
Sent: Wednesday, February 08, 2017 1:34 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AW: A further question regarding COBOL5 and CEEDUMP

>Anyway, TEST is much improved with COBOL V5/V6, we put the Debug data 
>in a NOLOAD class segment in the Program Object, so that it is always 
>available, always in sync with the load, and never takes up memory at runtime 
>unless it is needed.  An example of when it is needed is when a CEEDUMP is 
>being written/created by LE! 
 
But BEWARE the fact that each and every transaction abending in, say CICS, will 
now list all the working storage to the CICS SYSOUT if the LE options are 
TERMTHDACT(TRACE,,24)! This caused us a productin issue!

We do compile with TEST, but we did not copy the side files to production, so 
LE was not able to list the working storage; a simple single line message 
informed us about this. Fine.

Now with Cobol V5 (and later) the debug information is *always* there, there is 
no way to avoid this. Basically, a good thing, however not for your CICS 
regions. We ended up with millions of lines of TRACE output being written to 
CICS SYSOUT.

IBM LE/Compiler people should have thought of an additional TERMTHDACT option 
to *suppress* the listing of the working storage when not desired, suchas 
withing CICS. I had envisioned something like TERMTHDACT(TRACESHORT...) which 
would give us the same information a TRACE but without lilsting the working 
storage. 

We opened a PMR and the solution was to implement some Cobol runtime option via 
assembled module IGZUOPT (shudder, but unfortunately my voice was not heard). 
There is APAR PI75601 that will implement that change and is targeted for 
February.

--

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to