Back in Ye Olde Days I had such a problem (very annoying when users would call the support desk about these things).
We had a modified IKJEFLD that allowed overrides of PROCs and accounts without requiring UADS entries. What I did would call the accounting system to verify that the account was valid and I added 2 libraries to MSTJCL00, the user proclibs and the SP proclibs and verified that the override was in the proclib. This had the advantage that users could create their procs for their applications but not be able to use them for TSO. They would get messages such as "not authorized to such an account" or "proc not known" and would be able to reenter. I also added code to allow the user to permanently update these as well as the password from the logon prompt. On Thu, 5 Mar 2020 23:08:32 +0000 Jesse 1 Robinson <[email protected]> wrote: :>From the dawn of time, it was deucedly difficult to find the cause of a JCL error during TSO logon. Then several releases ago, we were treated to a 'fix'. The error would be displayed on the user's screen, allowing the problem to be corrected within seconds. Yesterday we had such a situation, but any helpful message flashed on the screen for milliseconds and then disappeared. In this case it turned out to be missing logon proc. :>I hunted in vain for doc on this problem, including maybe a need to set a parm somewhere. We run TPX, which it just now occurs to me might be the problem... -- 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: INFO IBM-MAIN
