× 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.



OS Level is v7.3 and as far as the auditors are concerned, and for the
purpose of our current requirements, we just want to see traditional
objects, not IFS.

Ideally, we would like to produce a report showing PTF Number, Date
Applied, Object, Object Type, Object Library, Object Change Date, Size,
etc.


On Fri, Aug 2, 2019 at 6:15 AM Rob Berendt <rob@xxxxxxxxx> wrote:

What is your definition of an "object"? Just stuff in the qsys.lib file
system and not stream files in other places of the IFS?
If that's the case I was going to suggest querying OBJECT_STATISTICS
however, while that does have many of the fields it does not have the PTF
number as displayed in
DSPOBJD OBJ(QSQROUTE) OBJTYPE(*PGM) DETAIL(*SERVICE)
Sorry.


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


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Ron
Adams
Sent: Thursday, August 1, 2019 10:41 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: PTF Object Manifests?

CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.


We had an odd request by auditors to verify objects changed by PTFs.
Is there an easy way to do this? I see there is an API (QPZRTVFX), but I
was hoping for something more standardized like an already existing CMD.
I suppose we could capture the log messages when we apply fixes, but that
only helps us for the future. We need to show past changes right now.


--
Ron Adams
--
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@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
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@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.