On Thu, 23 May 2013 12:40:18 -0500, Dana Mitchell <[email protected]> wrote:
>We have 2 systems in a basic sysplex, sharing everything: RACFDB, JES2, Master
>catalog, Parmlibs etc. The only differences between the sytems is that they
>are each on a different CEC, and one system has a few licensed products that
>the other doesn't such as MQ, Syncsort, Qwikref.
>
>We define a new user to RACF, and all options defined on TSO segment. New
>user can logon to system 1 successfully. Then logon to system 2 successfully.
> Everybody is happy. If the new user tries to log onto system 2 *first* the
>logon fails with:
>
>IEC143I 213-04,IFG0194D,MSTJCL00,CTPROC,SYSUADS,E39E,Z13RES,SYS1.UADS
>IEF170I 3 MPETER3 IEC143I 213-04,IFG0194D,MSTJCL00,CTPROC,SYSUADS,E39
>IKJ601I TSO LOGON ATTEMPTING RETRY. ABEND 213, USER MPETER3 , PROC
>UNKNOWN
>IEA995I SYMPTOM DUMP OUTPUT 692
>SYSTEM COMPLETION CODE=213 REASON CODE=00000004
> TIME=10.21.43 SEQ=59394 CPU=0000 ASID=0044
> PSW AT TIME OF ERROR 075C1000 80D081B6 ILC 2 INTC 0D
> NO ACTIVE MODULE FOUND
> NAME=UNKNOWN
> DATA AT PSW 00D081B0 - 4100302C 0A0D010D A7E50126
> AR/GR 0: 008FE040/00D08474 1: 00000000/A4213000
> 2: 00000000/00007CD0 3: 00000000/00D08448
> 4: 00000000/008F2410 5: 00000000/008F27A4
> 6: 00000000/008F274C 7: 00000000/008F27A4
> 8: 00000000/008F276C 9: 00000000/008F1EC0
> A: 00000000/80D0A7C2 B: 00000000/00D0B36A
> C: 00000000/80D0B55C D: 00000000/7FFB4D20
> E: 00000000/80D07A14 F: 00000000/00000004
> END OF SYMPTOM DUMP
>
>IF the user goes back and logs onto system #1, it is successful. THen back
>to system #2, now it's successful too.
>
>There are very few differences between these systems. Everyone uses RACF for
>TSO logon, the only thing in uads is IBMUSER0. SYS1.UADS is catalogged in the
>shared master catalog on a different volume, Z13RES is the currently IPLed
>sysres volume. MSTJCL00 contains:
>
>//SYSUADS DD DSN=SYS1.UADS,DISP=SHR
>
>I can't find anywhere uads is referenced by volser, or ****** or &SYSR1 or
>anyting. I cannot explain why initial logon works on one system and not the
>other. Does anybody have ideas of what else to check? I've about run out of
>things to look at.
>
These sort of things are often very hard to figure out (it not impossible)
without
being on the system to poke around or having more doc (which you did not
provide).
Some things I would ask for / look at.
1) Listcat of SYS1.UADS from both systems (even though you say the MCAT is
shared)
2) CTPROC listing + logon clist listing
3) Are you sure the proc is coming from the same place on both systems
4) Are you sure MSTRJCL=(00) is specified / defaulted in each system?
5) Even if sure about #4, do the parmlib concatenations match an/or are you
sure you know where MSTJCLxx is being pulled from.
6) Output from failed logon (if it purges, use a JES command to change
the msgclass - JOBCLASS(TSU) - attributes to keep the output.
7) Syslog from IPL
Ok, now that I wrote that I re-read your post. This is a one time thing only
with a new user? If so, what if the user is defined by the RACF admin
from system #2? Does you see this failure if the new user logs onto
system #1 first?
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
mailto:[email protected]
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://expertanswercenter.techtarget.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
