SYSOUT is getting deleted after execution of the JOB

amrita.chatterjee · Posted: Mon Oct 05, 2009 10:30 am

One REXX program is calling one COBOL program. In the COBOL program, I have added some display statements. In the REXX program, i am allocating the sysout by the following command.
"ALLOC F(SYSOUT) DA(*) SHR"
once the execution is done, I am releasing the SYSout by the following command.
"FREE F(SYSOUT)"
Hence, during the execution of the job, sysout is there in the spool but once the execution is done, SYSout is getting vanished from SPool - So I am not able to see the SYSout after the execution.
after that I have removed the "FREE F(SYSOUT)" statement from the REXX and now SYSout is there also after the execution. As this is a normal practice to FREE something after the execution so this is not a elegant solution may be.

Could someone please throw some light on this?

ofer71 · Posted: Mon Oct 05, 2009 10:45 am

DA(*) means that you allocate the file to your terminal. Why can't you allocate it to a permanent dataset?

O.

amrita.chatterjee · Posted: Mon Oct 05, 2009 10:49 am

Actually I don't want to allocate SYSOUT to a parmanent dataset. is there any option so that SYSOUT won't be deleted after the execution?

Thanks

gcicchet · Posted: Mon Oct 05, 2009 11:07 am

Hi,

change the SYSOUT statement to "ALLOC FI(SYSOUT) SYSOUT(X)"

or to a class that is not purged.

Gerry

Anuj Dhawan · Posted: Mon Oct 05, 2009 12:09 pm

Is this again something to do with "Bull Mainframe Systems"?

PS. Sorry, if I add clutter... just thought that thread may have a clue...

amrita.chatterjee · Posted: Mon Oct 05, 2009 12:58 pm

Thanks Gerry.
I have "ALLOC FI(SYSOUT) SYSOUT(J)" but still the sysout is not coming. Do you have any idea how can I use the CATALOG command in REXX with SYSout. Actually I have jus chcked that if I will use CATALOG command then it will be catalogged after the FREE.

Please help...

sijayapal · New User Joined: 23 Dec 2008 Posts: 69 Location: India

I am not a expert in rexx.. but i believe u can write the sysout in a file instead of writing to a spool...

amrita.chatterjee · Posted: Mon Oct 05, 2009 3:00 pm

but the requirement is that i need to write in the Spool itself.

Please help.

expat · Posted: Mon Oct 05, 2009 3:24 pm

This works perfectly well for me

Craq Giegerich · Posted: Mon Oct 05, 2009 5:59 pm

change the SYSOUT statement to "ALLOC FI(SYSOUT) SYSOUT(X)"

SYSOUT(X) whould have to be a class that is held on your system!

Bill Dennis · Posted: Mon Oct 05, 2009 7:44 pm

Also, ensure that the ALLOC command completes successfully by keeping MSGS ON. The SYSOUT DD is fairly common and may have already been allocated in your LOGON procedure.

Pedro · Posted: Mon Oct 05, 2009 9:23 pm

amrita.chatterjee · Posted: Mon Oct 05, 2009 10:59 pm

Thanks Craq. I will try the SYSOUT(X) option tomorrow. I have already used so may options like NOHOLD, CATALOG, KEEP etc but none of them are working.
Regarding Pedro's comment. Actually if I am removing the FREE option then my purpose is getting solved but as we always should free all the files whatever we have allocated during the program - hence this is not an elegant solution.

Pedro · Posted: Tue Oct 06, 2009 12:58 am