The System i Management Tips blog brings over 80 useful tips from Vision technicians.
The blog has been opened to tips from our followers! For each tip you submit that that is posted on the blog, you'll be contacted to select one item from our selection of Vision-logo items. Examples include coffee mugs, t-shirts, golf balls, flash drives and more!
Send your tips to: itips@visionsolutions.com
You may want to determine what jobs or objects are responsible for generating journal entries in a journal's receiver chain, for example, if you notice that many receivers are being created for the journal.
To determine what jobs or objects are responsible for generating journal entries in a journal's receiver chain, create an outfile from the DSPJRN command and run an SQL query on the outfile:
1. Create the outfile by running one of the following DSPJRN commands:
If you are using a logical replication or high availability solution and you have certain files that are cleared on a regular basis, the following command can be used to identify those objects. If the file is cleared then it may be a file that does not need to be replicated, which will save you bandwidth in the replication process.
If you need to delete several journal receivers that have not been saved there are several ways to go about it.
If you use OPTION 4 from PDM or WRKOBJ screens you will receive an *INQUIRY message for each unsaved receiver telling you that is has not been saved and asking you to Ignore or Cancel. Deleting the receiver from within the WRKJRNA display will give you the same messages.
There is a quicker way.
From the command line enter DLTJRNRCV JRNRCV(receiverlib/receivername) DLTOPT(*IGNINQMSG)
The DLTOPT(*IGNINQMSG) parameter will suppress the messages.
Note: You can enter a generic for the receiver name.
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).
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.
System managers who work with journals don’t always realize when they create new journals that an authority can be designated for the journal receiver that differs from the object being journaled.
The size of the receivers in the above example are .5 GB or larger. Press the Enter key to move from library to library, viewing the size of each receiver, look for receivers with a size of 10 positions which would indicate a receiver with the size of 1 GB or larger.
Employment at Vision Solutions. Vision Solutions seeks experienced IBM i (i5/OS) and AIX technical and support personnel. To learn more and see available openings click here
