But i want the SYSOUT to be routed to a dataset instead. When i did an override and submit the job, the job would start executing and using the CPU, but it just would be there doing nothing. It was not waiting for a dataset or for the operator to release. It would just be there. But it would run fine if i dont do an SYSOUT override.
The overridden dataset has LRECL of 133. I tried giving RECFM of overridden dataset as FB,FBA,VBA but still had the same issue. I removed the HOLD parameter itself from STEP1 and the DEST parameter too, but still faced the same issue. Any help is very much appreciated. Thank you
Joined: 22 Apr 2006 Posts: 6258 Location: Mumbai, India
At the face value of what you've posted so far, all looks fine. So possibly, you can "compare" the JESMSGLG and/or JESYSMSG of both the Jobs - one which executes and the other which does not.
Second, you can try using DISP=(,CATLG,CATLG), for the 'SYSOUT-file', and try with TIME=2 (some small value after which Job abends with a Time-abend) in Job card. Check what is there in the SYSOUT dataset.
Okay, all this is to get you going - none of them is a solution.
Thank you for your time guys. It is working fine now.
The problem was, i noticed that this step is writing huge data to SYSOUT. And since i was routing SYSOUT to a dataset, the job was writing it to the dataset and there was obviously no messages in the spool indicating that the job was writing the output. But i didnt override, i could see the SYSOUT while the job was running!
I just submitted the job and left it overnight and gave it its time and it was fine. So, actually there was no problem at all! My bad! Thanks again