|
I keep thinking of other stuff to check, after having sent in an e-mail. When a user is created, they get a MSGQ for their messages to go to.Most 400 objects have a creation date and other statistics which you can get at via DSP something dump to a work *OUTFILE that you can then examine via Query/400 or HLL.
If you are doing security auditing, there is a hit in the audit every time someone forgets their password. Does this happen to everyone once in a while & how long do you keep your audit journal? When there are non-employees with access to our systems, there are often contracts that got signed at the start of the relationship. If certain users consistently use certain work station names, and you are not doing a good job of cleaning up workstation members and in those files that have work members, you might check the member statistics on creation by user workstation names. >Inventory transactions have who keyed them in, so you can see how far back >that goes. Sometimes we print OS/400 reference data ... the security >files have some clues like when their password was last changed, which for >some people would be when their sign-on was first created. Some companies >do their own payroll, and have some kind of record on when someone was >hired, but we also have non-employees, like contractors, who have access >to our systems. > >>Hi All, >> >> >> >>Is there a way of finding when a BPCS user was created? Can that be >>determined on the iSeries? >> >> >> >> Regards, >> >>Isaac A. Antwi -- This is the SSA's BPCS ERP System (BPCS-L) mailing list To post a message email: BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/bpcs-l or email: BPCS-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/bpcs-l. Delivered-To: macwheel99@xxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.