IP CICS Sockets and EZY1315E error message
cogitoergosum
(Note: I posted this in cics-l too. Thought, I would toss it here
too.)
We have a Java class invoked by a servlet in Tomcat container. This
class invokes a CICS transaction by first connecting to mainframe
using java.net.Socket and then writing to it in the 'Listener Input
Format' as documented here (http://publibz.boulder.ibm.com/cgi-bin/
bookmgr_OS390/BOOKS/F1A1G130/6.5.1?DT=20050708130727)
I keep getting the error message EZY1315E as explained here
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1C950/SPTWQ104
As per the documentation for the error message, I have confirmed that,
the transaction ID being passed is indeed in four characters and in
uppercase alphabets encoded in EBCDIC. The only resolution as per the
link is to do a packet trace and see what's coming into CICS.
Although, I have also confirmed that, TLS is not implemented in Tomcat
server.
My questions :
1. What is involved in setting up packet trace in CICS ?
(Gotchas,pitfalls, tricks, tips, etc.) I have gathered the basics from
'z/OS
Diagnostic Data Collection and Analysis' (http://www.redbooks.ibm.com/
abstracts/sg247110.html?Open) and probably IBM-SYSTCPDA would help
too. (http://www.ibm.com/support/docview.wss?
rs=852&context=SSSN3L&dc=D400&uid=swg24007395&loc=en_US&cs=UTF-8&lang=en)
2. I have gone through the manual 'CICS IP Sockets Guide' (http://
publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1G140/
CCONTENTS?
DT=20070530144048) and notice that everything is prim and proper in
our CICS system as described in this manual. Why does this manual not
mention the TCPIP and TCPIPSERVICE CICS resources ? Are they not
required ? I do not see them on our CICS region anyway. In fact, the
CICS startup job has TCPIP=NO !
3. Finally, this is one of those "it used to work, now it doesn't" of
problems. And, unfortunately, no one knows if the sun someday rose
from west or something.
Waiting eagerly to hear from this forum.
Nagesh