RE: Preventing user profile lockout -- MIDRANGE-L

Hi, Siva

I'm responding to a couple of your posts here. As you are learning about the iSeries, you will do well for yourself by digging into the various manuals. You will get answers to your questions there, plus you will get the perspective and context you need. Handling messages is well-covered in the "CL Programming" manual. Your other post on changing the length of a spooled file is handled with overrides and is discussed in the "Database File Management" manual.

Monitoring for messages is covered to a degree in the "CL Programming" manual - RCVMSG is the command. You might look at the break-handling program citations in there, as well.

And you will do well to get very familiar with the menus that list commands by topic. GO CMDMSG, e.g., gives you all the commands related to, guess what, messages. The general format is GO CMDxxx, where "xxx" is a part of a command, such as "DSP" or "JOBD". What these parts are is discussed in one of the appendices of the "CL Reference". There are also special ones like GO SUBJECT and GO VERB.

At V5R3 InfoCenter, I recommend going to the "Printable PDFs and manuals" link on the main page.

For CL, there are also some non-IBM books on the various techniques you can use. www.mcpressonline.com is a source of some of these.

Good luck
Vern

At 06:21 AM 3/22/2005, you wrote:

Hi

Could you please tell wats the CL comamnd to monitor for the messages in the QSYSOPR? Sorry i could not find anything.

Thanks
Siva.


.com> wrote:
Messages are logged to QSYSOPR and/or QSYSMSG for account lockouts. You can
monitor these message queues and take the appropriate action which should
include notifying management and logging the occurrence.

Chris Bipes

-----Original Message-----

I have a requirement to prevent certain service/connection accounts from
being locked out - for example due to password validation errors. This
is to prevent the profiles being deliberately locked out as part of a
denial of service attack.

We do not want to set QMAXSIGN to *NOMAX as this applies at a system,
rather than an individual profile level.

Does anyone know of a way to do this? Is there an exit point we can hook
into when a user profile is disabled and use this either to stop the
profile from being disabled or re-enable the profile? Is there a way to
override this system value at an individual user profile level?
--
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.

---------------------------------
Do you Yahoo!?
 Yahoo! Small Business - Try our new resources site!
--
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.