Commands will then be logged in the Audit Journal. If you don't currently have an Audit Journal, instructions for setting one up are here:
Display the Audit Journal entries with Entry Type "CD" to view the commands. You can view these entries manually with the command DSPJRN JRN(QSYS/QAUDJRN) JRNCDE((T)) ENTTYP(CD) or you can display them to an outfile and run a query against it. Position 30 of the Entry specific data will have either a Y (indicating that the command was run from a CL program) or an N (indicating that the command was called from a command line or a menu option.)
For additional help with the Audit Journal, see Chapter 9 and Appendix F of the iSeries Security Reference, SC41-5302.
Dig Deeper on iSeries system performance and monitoring
Related Q&A from Scott Ingvaldson
On the AS/400 system, close all sessions in the receiving envrionment when transferring files from one environment to another if the sessions hold ... Continue Reading
After extending storage capacity on an IBM 520, the system performance depends on the workload amount and should not be affected negatively as long ... Continue Reading
When encountering problems using the SNDDST command to send a *LMSG on the iSeries, specify a valid SMTP name in the directory entry of the sender to... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.