11/19/08 Use the Security Audit journal to find out when an object was deleted and by whom

Ever wonder what happened to one an object that is missing on a system? If not too much time has elapsed, you might be able to track what happened to that object (or set of objects) by viewing the Security Audit journal on the local system (provided you have access to the journal and the Audit Journal is running).

Enter the following command:

DSPAUDJRNE ENTTYP(DO) OUTPUT(*PRINT) JRNRCV(*CURCHAIN)

The value in the ENTTYP parameter represents the type of audit entry to display. For example, ‘DO’ represents ‘object deletion’ actions. ‘CO’ represents ‘object creation‘ actions (to see the eligible values for this parameter and their meanings, press the Help key).

This command creates a spool file for each of the entry types specified on the ENTTYP parameter. View the resulting spool file and search for the name of the object and/or library for which you are interested. The entry, if found, will show the job name and the time of when the object was deleted.
There are other obvious audits that you can also accomplish with this tool, such as viewing when system values have changed and who may have changed them. The ENTTYP for system value changes/modifications is ‘SV’.

The DSPAUDJRNE command can be subset by starting and ending date/time if you know an approximate time period that is of interest to you.

The CPYAUDJRNE command provides similar functionality, except that output can be directed to an outfile, which may be more useful in an automated environment.

Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2008, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, i5/OS and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.


11/12/08 WRKACTJOB - the F21 key

By default, the WRKACTJOB screen shows commands at the top of the screen, but when you press F21, these commands are hidden and you will see six additional jobs on the screen.

Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2008, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, i5/OS and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.

11/5/08 WRKACTJOB - the JOB parameter

When using the WRKACTJOB command, the JOB parameter can be used to see all jobs (*ALL appears by default) a specific active job by name, or to select and view multiple jobs using a wildcard.

As an example of a wildcard, the following would show all jobs that start with "BATCH":

WRKACTJOB JOB(BATCH*)


Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2008, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, i5/OS and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.

10/29/08 WRKACTJOB - The SBS parameter

When using the WRKACTJOB command, the SBS parameter defaults to *ALL, but you can use this parameter to show one, several or many subsystems.

For instance, the following command will show jobs associated with three different subsystems:

WRKACTJOB SBS(QBATCH QBATCH1 QBATCH2)



Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2008, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, i5/OS and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.

10/22/08 How to view remote systems that can be accessed from a local system.

To show what remote systems you can access from a local system, simply use the WRKLNK/QFileSvr.400/* command. This will show you the remote system names that are accessible as they will appear as directories.

What if the remote system you wish to access does not appear in the list of directories? Simply create a directory of the same name as the system you wish to access. The name of the system is the TCP/IP host name or the SNA name of the remote system. Note: The QSERVER subsystem must be active on the remote system that you wish to connect to in this way.




Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2008, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, i5/OS and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.

10/15/08 How to access IFS objects on a remote system.

To access the IFS on a remote system, type the following on a command line: WRKLNK/qfilesvr.400/(system name). For instance, if you are on system "ABC02" and want to access the IFS on system "ABC01", the command would be: WRKLNK/qfilesvr.400/ABC01.
The resulting screen shows the entire IFS file system on system ABC01. From here, you can do anything in the IFS that you can do if you were locally connected to ABC01 (including creating IFS objects, removing IFS objects, etc.).

Next week’s tip will show you how to quickly see what remote systems you can access from a local system, and even how to access a system that you can’t see.



Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2008, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, i5/OS and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.

10/08/08 Easy way to look up and verify i5/OS commands:

If you happen to forget a command, or need to verify which command to use, start with the WRKCMD command. Specify *ALL and leave the Library as *LIBL. When you press Enter, a list of all commands will appear with a description of what each does.

Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2008, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, i5/OS and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.