MVSFORUMS.com

[cobcurious]

Hi,
I have a query for all you gurus out there.I have a query related to my observation about SYSOUT that when we run the job that executes a COBOL program and suppose we have DISPLAYS in our cobol program...I can go to the joblog (while the job is running) and see the messages written so far to SYSOUT and I press the ENTER key,I get to see some more of them,if they are written to SYSOUT.This is not observed for normal datasets because one is not allowed to browse a dataset to which the data is being written.What makes SYSOUT display data ,as explained ,and why is not possible with the normal datasets like a sequential dataset ?
Thanks
Cobcurious

[kolusu]

Cobcurious,

Try this.

1.Pre-allocate a dataset for sysout prior running your actual cobol pgm.
2.In your PGM step allocate the above pre-allocated file to sysout with disp=shr
3.Submit your program
4.You can Browse the pre-allocated dataset while the pgm is still writting to it.

Hope this helps...

Cheers

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

[cobcurious]

Hi Kolusu,
Let me first thank for your reply.Kolusu,I have still got the answer as to

[semigeezer]

While the data set is open, there is no end-of-file (EOF) mark, so you can't tell where the data ends. If you use ISPF browse, for example, to read it. you will see I/O errors near the bottom of the data. In addition, buffering may keep data from being written to the file until the block is full so you won't see output immediatly.

[cobcurious]

Hi semigeezer,

[Mike Chantrey]

JES spool datasets *are* a bit different to ordinary datasets (I think they're particularly intended to be read while being written for example). I don't know if the JES manuals would explain the details of the differences.