Hi List - I have a question on how other shops have their TCPIP.SEZATCP allocated.
Recently I applied 3 PTFs (UQ95225, UQ95175, and UQ92269 respectively) to fix a problem with the CICS CSKL listener abending. Over night the test CICS regions recycled, loading the new EZACIC02(and other) load modules from SEZATCP. The Foundation server that we use as a front end would not connect up to the listener afterwards, and after backing out the changes and recycling the CICS regions, it functioned fine. In doing some research, I noted that SEZATCP was in the TCPIP Steplib, and in doing some more research in looking at the example TCPIPROC, it did not have SEZATCP in the steplib. Furthermore, the default LNKLST that we received with z/OS 1.4, it only had SEZALOAD in the LNKLST. I am thinking the problem is that the TCPIP address space has one copy of EZACIC02, and the CICS region has a different one, and therefore they are not working together. So I am wondering how others have their TCPIP libraries set up. Does anyone or everyone steplib to SEZATCP, or shouldn't this be done? Does the TCPIP stack need SEZATCP at all? If so, should SEZATCP be in the LNKLST? Does everyone else have only SEZALOAD in the LNKLST? TIA for all all those who respond. Patrick Lyon ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
