Re: QMAXSGNACN and QMAXSIGN

[Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx>]

A few thoughts.  If you make a job that wakes up once an hour to *ENABLE,
that user who is punching in and disables it, will be pretty porked for the
next 59 minutes.  You could create the message queue QSYSMSG in QSYS, keep
that message queue in BREAK, and have break handling program that looks for
the appropriate message with the appropriate substitution variables, and
then re-enables.

Caution, if QSYSMSG exists in QSYS, other security messages will also be
send there, and no longer sent to QSYSOPR.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

"i" comes before "p", "x" and "z"
e gads

Our system's had more names than Elizabeth Taylor!

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com
http://www.as400connection.com



                                                                           
             "Tony Corbett"                                                
             <tcorbett@spacefl                                             
             ooring.com>                                                To 
             Sent by:                  <midrange-l@xxxxxxxxxxxx>           
             midrange-l-bounce                                          cc 
             s@xxxxxxxxxxxx                                                
                                                                   Subject 
                                       QMAXSGNACN and QMAXSIGN             
             05/27/2005 02:38                                              
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
             Midrange Systems                                              
                 Technical                                                 
                Discussion                                                 
             <midrange-l@midra                                             
                 nge.com>                                                  
                                                                           
                                                                           




Hi,

I'm in the process of system testing and implementation of a little "time
clock" type subsystem on the AS400 and as part of this, I created a simple
userid and password for signing on a workstation in the warehouse(s).  I
plan to just put this userid and password on a sticky on the workstation.
This profile is only allowed a little 3 option menu and has no rights to
anything else, so I think it's "safe".



Anyway, this same userid is used in 16 locations and invariably, someone
will *DISABLE the user profile trying to spell the really simple password.
I don't want to change the system values from the current values of 4 tries
then disable, but I need for this user profile not to get disabled.



I already thought of scheduling a job to re-enable it every hour or so, but
does anyone have a better idea to prevent this profile from getting
disabled??



TIA



Tony Corbett, IT Director

Space Flooring and Supplies, Inc.

http://www.spaceflooring.com <http://www.spaceflooring.com/>

tcorbett@xxxxxxxxxxxxxxxxx

(770) 333-5134

(770) 431-8282 (fax)

(404) 784-4737 (cell)



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.