RE: PC console

["MITTELHEISSER Jean Claude" <mitteljc@xxxxxxx>]

Rob,

QSECOFR becomes sometimes disabled (often because of uppercase in password). 
Each time user 11111111 with password 11111111 could help me enable QSECOFR. 
But last time I was near to disable this user too. So I created 2 SST users 
more.

Thanks.
JC Mittelheisser

-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] 
De la part de rob@xxxxxxxxx
Envoyé : vendredi 17 juin 2005 16:41
À : Midrange Systems Technical Discussion
Objet : Re: PC console

It's probably a waste of my typing, and will either send you off 
slathering, or grinning in your happy 5250 world, but here goes...

He is trying to use Operations Console instead of a 5250 terminal.  We've 
been there and might still be using it if it wasn't for the new HMC's on 
i5's.  When Operations Console connects via the way it does, it request a 
service tools user id and password.  As others pointed out, you can add a 
secondary service tools user id and lock them down tighter than a nun's 
knees.  In fact, I recommend a secondary SST user in case someone bones up 
QSECOFR as a service tool user.  I have a whole lot more confidence using 
the secondary to reset QSECOFR than I do going into DST.

STRSST
8. Work with service tools user IDs and Devices
1. Service tools user IDs


Rob Berendt