RE: identify/list any duplicate objects from any two libraries.

Rob,

I tried your various SQLs, works great.
I wanted to be able to see any dups for a specific library.
Not sure if the SQL could have done this.

I created a utility to find and list any duplicates sorted by library (556 libraries)
3 dspobjd, 1 CL, and 1 AS/400 M2 query.

Outfile of all objects on system
DSPOBJD OBJ(*ALLUSR/*ALL) OBJTYPE(*ALL) DETAIL(*BASIC) OUTPUT(*OUTFILE) OUTFILE(QGPL/DSPOBJD) OUTMBR(*FIRST *REPLACE).

Outifle of all libraries
DSPOBJD OBJ(QSYS/*ALL) OBJTYPE(*LIB) OUTPUT(*OUTFILE) OUTFILE(QGPL/DSPOBJDLIB)

CL to reads DSPOBJDLIB

DSPOBJD OBJ(&ODOBNM/*ALL) OBJTYPE(*ALL) OUTPUT(*OUTFILE) OUTFILE(QGPL/DSPOBJDDUP) OUTMBR(*FIRST *REPLACE)

RUNQRY QRY(DSPOBJDDUP) /* 2=Matched records with primary file */
DSPOBJDDUP M2 DSPOBJD

Loop

Paul





-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, February 10, 2015 8:30 AM
To: Midrange Systems Technical Discussion
Subject: Re: identify/list any duplicate objects from any two libraries.

I wonder how fast that command is on a large list of objects?
Pretty cool though.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Bryan Dietz <bdietz400@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 02/09/2015 05:04 PM
Subject: Re: identify/list any duplicate objects from any two
libraries.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



be careful when querying the QAEZDISK file, unless that file is
consistently updated you not find what you are looking for.

IBM released table function returns information about objects in a
library.

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/QSYS2.Object_Statistics%20table%20function%20ease%20of%20use


if you really want to do this real time I would look into the QUSLOBJ API

Bryan


Steinmetz, Paul wrote on 2/9/2015 3:56 PM:

Rob,

Maybe I should look at this from a different angle, as you suggested.
We have had more instances lately where someone needs to access

something from another application.

When this happens, an addlible XXX is inserted, code executed, rmvlible

xxx is inserted.

This is fine, as long as no dups.

So maybe I should dspobjd for XXX, then query that against the rest of

the objects in QUSRSYS/QAEZDISK.

This would only give the dups for the library in question.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of

rob@xxxxxxxxx

Sent: Monday, February 09, 2015 3:31 PM
To: Midrange Systems Technical Discussion
Subject: Re: identify/list any duplicate objects from any two libraries.

Well, if it is just QSYS2 you're concerned about, you could always just

DSPOBJD the items in QSYS2 and then query that against the rest of the
objects in QUSRSYS/QAEZDISK.

That also might be easier for you to understand instead of joining the

same table to itself.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600

Mail to: 2505 Dekko Drive

Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Gqcy <gmufasa01@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 02/09/2015 03:15 PM
Subject: Re: identify/list any duplicate objects from any two
libraries.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



in the case of this object (QSYS2/LIBLIST)
the "creation" date as seen in DSPOBJD is the date the PTF came active
(upon IPL, 02/01/2015).

On 2/9/2015 1:33 PM, rob@xxxxxxxxx wrote:

There is no create date.

Would that be accurate? For example, if you put on a PTF from IBM do

they

'create' LIBLIST or 'restore' it?
Well, maybe they do 'create' it...
Creation information:
Creation date/time . . . . . . . . . : 12/12/14 21:32:06
Created by user . . . . . . . . . . : QSYS
System created on . . . . . . . . . : GDISYS

Which happens to match the date we last ran a RCLSTG.


Rob Berendt