I missed that there was an optional third parm for object name.
Adding the object name made the results return almost immediate.
Thanks.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Kevin
Bucknum
Sent: Thursday, September 17, 2020 3:02 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Finding all occurrences of an object
select objlib, objtype, objtext
from table(object_statistics('*ALLUSR','*ALL', 'SOMEOBJECT'))
On Thu, 2020-09-17 at 14:40 -0400, smith5646midrange@xxxxxxxxx wrote:
I am in the early stages of writing a small archiving program. The user (IT
is my user) will be able to enter an object name and my program will return
a screen showing every location of every type of object that matches the
name. This includes file, dataareas, programs, etc. It will also show
anywhere that if finds a source member with that name. The user will then
be able to select what should or should not be archived. What else they
want on the screen has yet to be defined. I will guess that at some point
when it finds a physical file that they will want to see all of the logical
files too.
If I use the following SQL, it chugs FOREVER (it is still running after 15
minutes).
select objlib, objtype, objtext
from table(object_statistics('*ALLUSR','*ALL'))
where objname = 'SOMEOBJECT'
If I do dspobjd obj(*allusr/someobject) objtype(*all) output(*outfile)
outfile(qtemp/dspobjd), it returns in a second or two.
So, a few questions.
1. Why is the SQL statement so slow?
2. Before I spend time writing a program to use the QUSLOBJ API, does
anyone know if it runs about as fast as DSPOBJD or is it more in line with
the time of the SQL because of the amount of information that it returns
3. Is there another way to retrieve this info that I'm not thinking of?
[
https://www.medtronsoftware.com/img/MedtronMinilogo.bmp] Kevin Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
https://www.medtronsoftware.com
CONFIDENTIALITY NOTICE
This document and any accompanying this email transmission contain
confidential information, belonging to the sender that is legally
privileged. This information is intended only for the use of the individual
or entity named above. The authorized recipient of this information is
prohibited from disclosing this information to any other party and is
required to destroy the information after its stated need has been
fulfilled. If you are not the intended recipient, or the employee of agent
responsible to deliver it to the intended recipient, you are hereby notified
that any disclosure, copying, distribution or action taken in reliance on
the contents of these documents is STRICTLY PROHIBITED. If you have
received this email in error, please notify the sender immediately to
arrange for return or destruction of these documents.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
