On Mon, 26 Nov 2007 12:42:45 -0600 "John C. Wolf" <[EMAIL PROTECTED]> wrote:
:>On Mon, 26 Nov 2007 10:26:50 -0800, Ulrich Krueger <[EMAIL PROTECTED]> :>wrote: :>>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? :> I did get a slip for the 0C1 but not the IF. That should be good enough. What does R13 point at? The first 72 bytes. -- Binyamin Dissen <[EMAIL PROTECTED]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- 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
