¿ªÔÆÌåÓý

Re: CMSBATCH Output


 

Hi Daniel,

It has been a long time since Ive used CMSBATCH, but looking at the statements in your job submission, you didn't actually print anything.? You did direct SYSPRINT and SYSOUT to the terminal, but not to the printer.? And the printer is what you spooled to your userid.

In order to see terminal output, you should spool the console as well, at the beginning of your job:

CP SPOOL CONSOLE TO userid START

and the very last statement should be:

CP SPOOL CONSOLE STOP CLOSE

The added benefit of this is that you can see any errors in the commands in the job stream when the console log is returned to you at end of job.

In lieu of the console log, you could remove the filedefs for SYSPRINT and SYSOUT, and then after the COBOL command you could physically print them with a PRINT command, for example:

PR SYSPRINT LISTING

I'm not sure that is the filename and filetype but you could determine those by running a Cobol compile in your own userid and see what ends up on your disk.

Regards,
Bob

Join [email protected] to automatically receive all group messages.