3/26/10 Additional ways to see the contents of a user space (*USRSPC)

Note: This tip expands on the tip: How to see the contents of user spaces, published on 4/17/09.

If you have RPG programming skills then you can retrieve the content with the QUSRTVUS API as documented here:

V5R4 - http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/apis/qusrtvus.htm

V6R1 - http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/apis/qusrtvus.htm

However, if you don't have programming skills there is another way to see the contents of a user space:

Dump the users space with the CL command

DMPOBJ OBJ() OBJTYPE(*USRSPC) .

This will create a spool QPSRVDMP with a dump of the content in hex and in readable text.

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 2009, Vision Solutions, Inc. All rights reserved. Vision Solutions develops and sells iSeries high availability and AIX replication and clustering solutions. IBM, System i, iSeries, and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.

01/29/10 How to determine the jobs or objects responsible for generating journal entries in a journal receiver?

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:

To specify a receiver range:

DSPJRN JRN(/)
RCVRNG(/ /)
OUTPUT(*OUTFILE)
OUTFILFMT(*TYPE1)
OUTFILE(/)

To specify an entry time range:

DSPJRN JRN(/)
RCVRNG(*CURCHAIN)
FROMTIME( )
TOTIME( )
OUTPUT(*OUTFILE)
OUTFILFMT(*TYPE1)
OUTFILE(/)

Note: The outfiles can grow quite large, so make sure you are not near critical storage on DASD. The outfiles should be close to the same size as the receivers whose entries you are extracting.

2. Run the following SQL statements to find the jobs or objects that are responsible for generating the journal entries. You can cut and paste a statement into a SQL command line on the iSeries after issuing the STRSQL command. If you do not have STRSQL, you can use iSeries Navigator by expanding the system name, expanding the database branch, right-clicking the RDB name (most likely the same name as the system), and selecting Run SQL Scripts. Cut and paste the SQL statement into that window, change the slash (/) to a period (.), and click the Run>All menu command or toolbar button.

To find the jobs that are responsible for generating the journal entries, use this statement:

SELECT jojob, count(*) FROM /
GROUP BY jojob ORDER BY 2 desc

The output from this statement is a list of distinct job names sorted by the number of times each name occurs in the journal's outfile.

To find the objects that are responsible for generating the journal entries, use this statement:

SELECT joobj, count(*) FROM /
GROUP BY joobj ORDER BY 2 desc

The output from this statement is a list of distinct object names sorted by the number of times each name occurs in the journal's outfile.

Note: If the library name and object name are unreadable, the object is most likely an IFS object. In this case, you can determine the object name by performing the following steps:

a. Retrieve the sequence number from the column titled MIN(JOSEQN) and enter it in the following command:

DSPJRN JRN(/)
RCVRNG(*CURCHAIN)
FROMENTLRG()
OUTPUT(*)

b. Apply option 5, "Display Entire Entry"; the object name should be displayed at the top of 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 2010, Vision Solutions, Inc. All rights reserved. Vision Solutions develops and sells System i (iSeries) high availability and AIX replication and clustering solutions. IBM, System i, iSeries, and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.