RE: RTVDSKINF (was: Perm. apply PTF's thoughts)

I run this weekly, on Sunday nights.

Regards,

Mike Shaw

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tom Jedrzejewicz @
San Pedro
Sent: Thursday, April 03, 2003 9:37 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RTVDSKINF (was: Perm. apply PTF's thoughts)

Newbie admin question . . .

How often do you folks recommend that this be done, and what is the
recommended method to run it?

My initial thought is weekly (say Saturday night) run from a job
schedule entry.

Thanks.

>>> mhshaw@xxxxxxxxxxxxxxxx 03/28/03 02:31PM >>>
Jan,

If you are retrieving disk information on a weekly basis an easier way
to do it is with SQL:

Select *
   From qusrsys/qaezdisk
Where diobat = 'SAVF '
Order by diobli

You can get the field names for the file qaezdisk with dspffd
qusrsys/qaezdisk.

Sure beats running your system into the ground doing wrkfil *all/*all.

Regards,

Mike Shaw



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx 
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jan Megannon
Sent: Friday, March 28, 2003 1:41 PM
To: Midrange Systems Technical Discussion
Subject: Re: Perm. apply PTF's thoughts

rob@xxxxxxxxx wrote:

>Good idea Pete, but what I was describing, (among other things) is
when

>the boss sticks a ptf save file in his library and not QGPL.  I had 
>forgotten about the save files in the product libraries (well, maybe I

>referred to them indirectly with 'ability to remove a ptf').
>
>Rob Berendt
>  
>

If you just need to see which/how many savf's there are on the system,

wihout viewing the size, I find the following quite useful:
WRKF FILE(*ALL/*ALL) FILEATR(SAVF).

Jan

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
or email: MIDRANGE-L-request@xxxxxxxxxxxx 
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
or email: MIDRANGE-L-request@xxxxxxxxxxxx 
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO
WHICH IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED,
CONFIDENTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW.  If the
reader of this message is not the intended recipient, or the employee or
agent responsible for delivering the message to the intended recipient,
you are hereby notified that any dissemination, distribution, copying,
downloading, storing or forwarding of this communication is prohibited.
If you have received this communication in error, please notify us
immediately via email and delete the message from your computer files
and/or data base.  Thank you.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.