Re: QMAXSGNACN

[rob@xxxxxxxxx]

Interesting.  I'll keep that in mind about QSECOFR being able to use the 
system console even when disabled.  Does it bark at you and warn you? 
There's so much that depends on QSECOFR not being disabled that I would 
like to know it is disabled.
> From the console:
chgusrprf qsecofr status(*disabled) 
SIGNOFF
Signed on as QSECOFR.
DSPMSG QSYSOPR.  Nothing.
DSPMSG QSECOFR.  Nothing.
DSPLOG PERIOD((1335)).  Nothing.
DSPJOBLOG.  Nothing.
> From another session:
CPF1394 User profile QSECOFR cannot sign on. 
Back at console
chgusrprf qsecofr status(*enabled)
User profile QSECOFR changed. 
Granted, if it was disable via QMAXSGNACN there would be one message in 
QSYSOPR.
My concern is that a coworker could assist me with one of my downtime 
weekends, disable QSECOFR and I not know it.  Then stuff stops working and 
I waste time trying to figure if it was some new ptf or some such thing.

Right now, if the device is disabled after 3 tries, and the device happens 
to be one of our wireless scanners, then Message Labs will vary the device 
back on for 5 tries.  Effectively raising QMAXSIGN for just those devices 
to 15 (3 x 5).  I could work with that.

I still do not like them being able to disable ROB, PEGGY, CHRIS and a 
host of others so easily though.


Rob Berendt