× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I think the DSPOBJD will work.  I haven't processed in a while, but can
remember processing something like that.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ron Adams
Sent: Friday, November 18, 2005 9:29 AM
To: Midrange Systems Technical Discussion
Subject: Re: Determine name of query that created data file

I don't know of a way to determine what query created the data just by
looking at the object, but you can turn on the Audit Journal, WRKSYSVAL
-
QAUDLVL - *CREATE which will log all object creations on your system.
You
may also have to change jobd's to keep the job log, which will further
help
in determining who/what created the file.
 We use the query product from NGS, Interactive Query, and you can setup
the
configuration to force all output files to a specific library, which
we've
done. We set up a temporary library called QRYTMP that gets cleared
every
Saturday before our full backup. I would imagine you can do something
similar with IBM query, or maybe using security, force them to do this.

Ron
 On 11/15/05, John Earl <john.earl@xxxxxxxxxxxxx> wrote:
>
> Another way to keep users from putting their queries into QGPL is to
> remove *PUBLIC's data *ADD rights to the library. In order to place an
> item into a library, you must have data *ADD rights to the library.
>
> The risk? I bet somewhere between *SLIM and *NONE. After all, how many
> of your users _need_ to create new objects into QGPL?
>
> jte
>
> (Sorry for the old post - I have a lot of catching up to do)
>
>
> --
> John Earl | Chief Technology Officer
> The PowerTech Group
> 19426 68th Ave. S
> Seattle, WA 98032
> (253) 872-7788 ext. 302
> john.earl@xxxxxxxxxxxxx
> www.powertech.com <http://www.powertech.com>
>
>
>
> This email message and any attachments are intended only for the use
of
> the intended recipients and may contain information that is privileged
> and confidential. If you are not the intended recipient, any
> dissemination, distribution, or copying is strictly prohibited. If you
> received this email message in error, please immediately notify the
> sender by replying to this email message, or by telephone, and delete
> the message from your email system.
> --
>
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
> > bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
> > Sent: Tuesday, November 01, 2005 7:18 AM
> > To: Midrange Systems Technical Discussion
> > Subject: RE: Determine name of query that created data
> > file
> >
> > To discourage users from creating files in QGPL change
> > their user
> > profiles.
> > CHGUSRPRF CURLIB(...)
> > Pick something besides *CRTDFT or QGPL as they are one and
> > the same.
> >
> > Had the same problem here.
> >
> > Rob Berendt
> > --
> > Group Dekko Services, LLC
> > Dept 01.073
> > PO Box 2000
> > Dock 108
> > 6928N 400E
> > Kendallville, IN 46755
> > http://www.dekko.com
> >
> >
> >
> >
> >
> > "Lapeyre, Francis" <FLAPEYRE@xxxxxxxx>
> > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > 11/01/2005 09:40 AM
> > Please respond to
> > Midrange Systems Technical Discussion <midrange-
> > l@xxxxxxxxxxxx>
> >
> >
> > To
> > "'Midrange Systems Technical Discussion'" <midrange-
> > l@xxxxxxxxxxxx>
> > cc
> >
> > Fax to
> >
> > Subject
> > RE: Determine name of query that created data file
> >
> >
> >
> >
> >
> >
> > Once I had level check on a normally stable program. The
> > file in question
> > had not been changed lately, nor had the program, so I was
> > puzzled --
> > until
> > I looked more closely at the message and saw that the file
> > in question was
> > in QGPL, and not the data library (QGPL was the second
> > library on the
> > library list, right after QTEMP). Somebody created the
> > file with Query
> > (with
> > the same name as the production data file); I renamed the
> > file, answered
> > the
> > message, and found out who created the QGPL version by
> > doing a DSPFD on
> > it,
> > and admonished him to not create files in QGPL. We have
> > libraries we
> > create
> > for users to create their own queries and the files
> > generated thereby, and
> > he apparently forgot about that memo. We have since locked
> > down QGPL and
> > the
> > data libraries so people can't create new files there
> > anymore.
> >
> > In any event, I suppose you need to work backwards - find
> > the owner of the
> > file with DSPFD, then look for *QRYDFN objects that user
> > created, and look
> > at the output files they create.
> >
> > Francis Lapeyre
> > IS Dept. Programmer/Analyst
> > Stewart Enterprises, Inc.
> > E-mail: flapeyre@xxxxxxxx
> >
> >
> >
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Erin
> > Botkin
> > Sent: Monday, October 31, 2005 3:32 PM
> > To: midrange-l@xxxxxxxxxxxx
> > Subject: Determine name of query that created data file
> >
> > Does anyone know who to determine the name of a query that
> > created a data
> > file?
> >
> > Erin K. Botkin
> > Application Analyst
> > Spotsylvania County
> > Information Services
> > PHN: 540-582-7055 ext. 232
> > FAX: 540-582-9840
> >
> > ebotkin@xxxxxxxxxxxxxxxxxx
> > --
>
>

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.