Thomas Conley wrote:
<snip>
Please pass along to
the SDSF designer that it would be a whole lot easier if SDSF would just
issue the @#$%^&* ICH408I, without jumping through the PROFILE WTPMSG
hoop. NOWTPMSG is the default for a new TSO user, so debugging these
errors is a huge PITA.
<snip>
Sorry if I missed it earlier in the thread, but...there's nothing
(i.e., no ICH408I message) in SYSLOG?
(Nit: Of course, SDSF does not issue of ICH408I, RACF does.
However, a caller can control the whether messages are issued;
see the doc for RACROUTE REQUEST=AUTH for the gory details. This
could become important to you later...or not.)
From a TSO/E message standpoint, I think SDSF and RACF are
acting properly, at least for the first case you describe.
That's the entire intent of WTPMSG/NOWTPMSG, and how it's worked
for at least 25 years. If I could go back in time and had the
power to do so, I'd probably choose to make the defaults WTPMSG
and MSGID, but it seems far too late to do that now. (Can you
imagine the help desk calls from people who didn't understand all
the "new" messages? *-Shiver-*)
For the second case, my personal opinion (which, when combined
with a dollar, won't even get you coffee at Starbucks these days)
is that there should be a way to diagnose the second problem from
either messages issued to the user or messages recorded in SYSLOG
without having to resort to SMF records and such.
--
John Eells
z/OS Technical Marketing
IBM Poughkeepsie
[EMAIL PROTECTED]
----------------------------------------------------------------------
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
