MVSFORUMS.com

ranjo · Beginner Joined: 11 Mar 2004 Posts: 6 Topics: 2

Are there any limitations on the EXEC CICS WRITE OPERATOR command ?
I am issuing them from a STARTED task that is not associated with a
terminal and the messages do NOT appear on the console. When I use
CEDF on this same program from my terminal the messages to appear on
the console. The program is not changed. Thank you

kolusu · Posted: Fri Mar 19, 2004 9:42 am Post subject:

Ranjo,

What is the resp code after the successful execuetion of the write command? Check this link for a detailed explanation of the WRITE OPERATOR command.

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DFHJAP44/1.266?DT=20000704150132

Hope this helps...

Cheers

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

ranjo · Beginner Joined: 11 Mar 2004 Posts: 6 Topics: 2

But I do NOT have a handle condition AND the transaction did not abend, so if the RESP/RESP2 was not zero would'nt it have abended ?

Manas Biswal · Posted: Fri Mar 19, 2004 6:10 pm Post subject:

ranjo,

What have you given in the ACTION parameter of the command. If you have given an ACTION of EVENTUAL, then the message will roll off the console's screen along with all the other messages. Try giving an ACTION of IMMEDIATE or CRITICAL.

Regards,
Manas

ranjo · Beginner Joined: 11 Mar 2004 Posts: 6 Topics: 2

The message NEVER appears on the console, this is the problem, not its rolling off. I use SDSF within TSO and I can see every console message issued by the CICS region from when it comes up to when it goes down. The messages that are issued from this program do NOT appear when it runs after being STARTED not running on a principal facility but when it runs under CEDF from my terminal they do appear.

Mike Chantrey · Posted: Mon Mar 22, 2004 11:46 am Post subject:

It's not clear to me if you are specifying the RESP keyword on your WRITE OPERATOR. If you specify RESP on the command but do not check the value, this implies NOHANDLE so you can get a non-zero RESP but the program will continue with no indication of failure. The presence of a principle facility should not be relevant.

Incidentally, you can use the command
CEDX transid
in more recent releases of CICS to trace background transactions. This may help.

ranjo · Beginner Joined: 11 Mar 2004 Posts: 6 Topics: 2

Mike, thanks for your response. I am not using RESP, I would be happy to get an abend because of a non-zero return code. CEDX, CEDF doesn't matter it will work. When the tran runs as a result of the EXEC CICS START TRANID(XXXX) it does not get an abend nor does the WTO appear but it does appear when running CEDF.

Mike Chantrey · Posted: Tue Mar 23, 2004 10:37 am Post subject:

I think you need to post the actual code (full program if short, or if it's long/sensitive just the relevant working storage, the WRITE OPERATOR and any variable assignments etc. relating to it.)
If you do this, apart from looking at it I can try the WRITE on my system if necessary.
I'm still not clear from your comments whether it did of did not work when you ran with CEDX.

ranjo · Beginner Joined: 11 Mar 2004 Posts: 6 Topics: 2

Thank you for your response and interest. This item has been resolved. We "forgot" about the XEIIN exit we are running, which was the heart of the problem. Thanks again.