John, tell me, what's the common denominator, the thing that's special with the failing logonIDs? In other words, what's different when compared to a logonID that works? Logon proc? Dataset allocation accessing obsolete / backlevel version of software? Startup Clist/Exec? Personal customization? Homegrown commands with a dependency on JES2 level (that need recompiling)? Is SDSF up to speed?
When the S0C1 occurs, does the session just fail or does it recover? Did you get a SYSUDUMP to look at? Did you try a simple, more generic SLIP to trap any S0C1 occurrence? Regards, Ulrich Krueger -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of John C. Wolf Sent: Monday, November 26, 2007 10:09 To: [email protected] Subject: branching to zero I have a problem with some TSO users getting 0C1s at logon. It appears that some module is branching to zero but I can't find it. I set a IF slip for range 0 to 10 but it will not spring. I did install a new version of JES2 V1R7 on Friday but only a few TSO users have this problem. Does any one have any ideas on how to shoot this problem. ---------------------------------------------------------------------- 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
