Posted: Wed Oct 22, 2008 7:51 pm Post subject: UNIT=TAPE - does not displaying SYSOUT Info
Hi,
I have job which writes the o/p file in a tape. Since the input file has Millions of records, we included some display statements in the program. So, everytime if the record count reach 1 million, it will display the count with the time in the SYSOUT.
When we run the job with SPACE=CYL, we are geting our message in the SYSOUT continously (for every Million records). Also when same job is submitted with UNIT=TAPE, we are getting the display correclty and then and there.
However, when the job is submitted with UNIT=TAPE,VOL=(,,,50), I am not seeing the display statement in the SYSOUT regularly. It takes almost 60-80 min and then provides the consolidated display..
What could be the reason for this ? . What changes, should i need to make to see the DISPLAY regularly ? .
Joined: 03 Dec 2002 Posts: 579 Topics: 1 Location: Iowa, USA
Posted: Thu Oct 23, 2008 8:03 am Post subject:
The UNIT on a separate DD will have no affect on the SYSOUT displays. Something else is going on here.
When you say that you eventually see "the consolidated display", do you mean that after 60 mins a series of records suddenly appeared in SYSOUT? Are you watching the SYSOUT file in SDSF as the job is executing?
It could be a buffering issue where you don't see updates until several records have been written. Back out and re-select the job every few minutes and see if the behavior is normal. _________________ Regards,
Bill Dennis
Disclaimer: My comments on this foorum are my own and do not represent the opinions or suggestions of any other person or business entity.
Actually i have not included the UNIT parameter in the DD statement. What i meant is that, when we give the space for the o/p file as UNIT=TAPE, we are getting the SYSOUT updated regulary(over a period of time). however when we try to have the UNIT=TAPE,VOL=(,,,50) for the output, SYOUST is not displaying regularly.
I agree the fact that SYSOUT cannot be blindly used as a real time update. However, it surprises me that, why it is behaving differenly
Joined: 08 Aug 2007 Posts: 291 Topics: 2 Location: Chicago
Posted: Fri Oct 24, 2008 3:36 pm Post subject:
As dbz stated, you can't rely on the 'real' time ouputs. Having said that, you could check a couple things to try to explain the behavior. Is the job running on the same machine? What about the job class and priority?
I include the periodic messages mostly for performance analysis, but I must admit, I'll occasionally peek while the job is running.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum