Letter from the Editor

I want to thank Patrick Townsend of Patrick Townsend Security Solutions for his great series on System Logging and the IBM i. The three-part series wraps up in this issue of the newsletter. I have included links to the first two installments for your convenience. I also want to thank Larry Youngren for his continued series on "Journal Insights." This series is a treasure trove of knowledge and understanding regarding the journaling facilities on the IBM i. In this issue, Larry examines some

From the Editor

Dear Reader, In this issue of the Systems Management Newsletter, guest author Patrick Townsend, Founder of Patrick Townsend Security Solutions, begins a 3-part series entitled "System logging and the IBM i". This technical series will explore the topic of event logging and integrating the logs from one or multiple systems into a useable format to enhance the management of our systems. I hope you enjoy the series. In this first installment, Patrick examines the four sources of event

From the Editor

Dear Reader, I am very excited to share with you this issue of The Systems Management Newsletter. Several months ago I was looking for a command that would list all the Control Language commands that were usable by “Limited Capability” users. I know that IBM ships several commands, like DSPMSG and DSPJOBLOG that allowed these “Limited Users” to run the command at a command line. But I also know, that I did not have any idea what other commands on my system might have been modified or

Let Users View the Active Joblog of an *ALLOBJ

When a job is active for a user that has *ALLOBJ special authority, the joblog of the active job is typically not accessible to other users on the system. This can present big problems for the operations staff for scheduled jobs and other batch jobs that run under the profile of a powerful *ALLOBJ user. In the event of a batch program failure, a message arrives on the QSYSOPR message queue which often states, "See Joblog for more information." But, if the operator does not have *ALLOBJ

QPWDCHGBLK Revisited for V5R4 – Password Change Blocking

In the last issue I discussed the new i/OS 6.1 system value of QPWDCHGBLK(Password Change Blocking). This is a new system value that allows you to specify a password change block time. For example, you can set the system value to 24, which tells the system that a user may not change their password again within 24 hours of a successful password change. A very nice reader wrote in and asked how this function could be duplicated on V5R4 and before. Here's some ideas on how to do this.

How to Delete Old User Profiles