Think we found it. In our VTAMLST definition for TSO, we had this IST080I TSOH878 ACT/S TSOH879 ACT/S TSOH880 ACT/S IST080I TSOH8H8 CONCT TSOH882 CONCT TSOH883 CONCT IST080I TSOH884 CONCT TSOH885 CONCT TSOH886 CONCT
After TSOH880 comes TSOH8H8. And that is where we are stopping. So I am guessing that VTAM stopped because the TSOH8H8 was not acceptable for some reason. At least that is what coincidence is telling me. We will change the TSOH8H8 to TSOH881 and cycle the TSO ACB tonight. Will let you know how it works. Lizette >No - no network issues, the D NET,PENDING has nothing queued. NETSTAT does >not show any issues. > >We are at z/OS V1.7. We made no changes to any parms. Our MAX Address space >in IEASYS00 is 375, we currently have 363 address spaces running. In TSOKEY00 >our USERMAX=160 (D TS indicates only 80 out of 160 being used). We show VTAM >TSO Appl display with 256 appls but up to 80 show ACT/S the rest are CONCT. > >Confusion abounds. There are no additional error messages indicating a >problem. I may open an ETR to IBM if I am unable to resolve this issue. > >Do you think any USS processes may be affecting my MAX Address Space >information? Or am I barking up the wrong O'Ladder? > >So - other than VTAM TSO Appl definitions and USERMAX, anything else to look >at for TSO? > >Lizette > > > >> >>>> >>Hard to tell w/o more info. Normally TCP recycles APPLIds. Are you >>experiencing network problems? D net,pending or a few NETSTAT commands ought >>to give >>you a clue. >> >> ---------------------------------------------------------------------- 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
