As Barry Schwarz' response has already correctly implied, the TSO logon
command is not stored in the users profile data set but in the COMMAND
field of the TSO segment of the user's RACF user profile, so changing
the user's ISPF profile dataset will have no effect. The only way to
change the logon command if the logon panel is non-functional is for
someone to manually update the RACF user profile.
The default RACF behavior allows only a RACF SPECIAL user to issue the
ALU command to update a user profile. It is possible for an
installation to explicitly grant users the authority to update specific
fields in their own user profile, but since the TSO logon panel
already provides (under normal circumstances) a route for the ordinary
user to update his logon proc, account number, and logon command in the
RACF USER TSO segment, it would be unlikely for an installation to
enable update of these fields via the ALU commend.
Simplest solution is for the user to find a RACF administrator and
request execution of the ALU <user> TSO(NOCOMMAND) to wipe out his bad
logon command.
J C Ewing
Raymond Noal wrote:
If the user's TSO logon proc will allocate a new profile data set if one is not present, either rename and/or delete the user's current profile data set.
HITACHI
DATA SYSTEMS
Raymond E. Noal
Senior Technical Engineer
Office: (408) 970 - 7978
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 05, 2007 2:48 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject:
Have someone with system special issue
ALU user TSO(NOCOMMAND)
Possibly have the user logon through telnet or other non-3270 method and
issue the command himself. Not sure how much authority a user has over
his own account.
-----Original Message-----
From: George, William (DHS-ITSD) [mailto:snip]
Sent: Tuesday, June 05, 2007 2:23 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject:
A peer of mine is caught in a bind.
He entered a command in the COMMAND field of the logon screen. The
command was one he cut and pasted from and email sent to him explaining
what to enter there. Unfortunately, the quotes around the
dataset(member) were MS word type quotes (forward and backword quotes).
His attempt to logon errored and he tried to get back to the logon
screen to fix his problem.
However, apparently those quotes are non-displayable characters for TSO
(or ISPF) and are stored no permanently in his profile.
He now continually gets a screen eraser error when ever the LOGON panel
attempts to display.
I'm assuming this is due to the COMMAND field having that
non-displayable character stored there. He is unable to clear this.
Anyone know of a means, via a non sysprog point of view, to clear the
COMMAND field on the logon panel so he may start fresh.
--
Joel C. Ewing, Fort Smith, AR [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
