MVSFORUMS.com

[PHacker]

At our site, we have quite a bit of JES code. I am restructuring most of it and find we have //SYSABOUT and //SYSDBOUT statements by the ton. Now we rarely have any kind but simple problems with the setup, and I understand these DD's are used in system dumps. Are they really needed for well over 100 EXEC statements per JCL?

Thanks,

Paul

[kolusu]

phacker,

On z/OS and OS/390, dump output is directed to SYSUDUMP, SYSMDUMP, or SYSABEND. On other systems, VS COBOL II run-time dump output is directed to SYSABOUT. (SYSABOUT is not used under Language Environment, even for VS COBOL II programs.)

For OS/VS COBOL programs that are compiled with the NORES compiler option, dump output generated using SYMDMP remains the same and continues to be directed to SYSDBOUT. If the RES compiler option is used, a CEEDUMP will be produced instead.

For VS COBOL II programs compiled with the FDUMP option, you could get a formatted dump of COBOL WORKING-STORAGE. VS COBOL II FDUMPs were directed to the SYSDBOUT data set.

So if you are operating system is Z/OS or OS390 , then you can actually remove those DDnames. Check this link

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IGY3MG10/3.1.2.1.3?SHELF=&DT=20020924162905&CASE=


Hope this helps...

Cheers

kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

[PHacker]

Kolusu,

Much thanks. I have looked over the compiler options in the A/P and Payroll sections and NO reference to any kind of dump options are there! Nor the RES or NORES options. I have this feeling the whole thing was set up without any thought to dumps. I have experimented with deleting both the SYSABOUT AND SYSDBOUT and I have seen no difference.

I guess I'm getting chicken in my old age. I'm about to move to producition something like 5k lines in two different systems and I really hate being called in the middle of the night by the operators.

Again, much thanks.

Paul