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

[rob@xxxxxxxxx]

Instead of messing with CL I just run the RTVDSKINF and PRTDSKINF to a 
single string job queue.  But then, the standards here allow us to create 
job queues on a whim.  And I use two ADDJOBSCDE's to schedule them; with 
the PRTDSKINF 5 minutes later.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Jones, John (US)" <John.Jones@xxxxxxxxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/03/2003 02:42 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     "Midrange Systems Technical Discussion" 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        RE: RTVDSKINF (was: Perm. apply PTF's thoughts)


It really depends on how often you need updated info.  I publish
database & system DASD growth stats weekly so I run it every Sunday
morning at 4AM (pretty much right after backups complete).  I added a CL
to the scheduler that runs the RTVDSKINF and then does a couple of
PRTDSKINF runs to generate my reports.  When I come in on Monday morning
the reports are ready.

- John

-----Original Message-----
From: Tom Jedrzejewicz @ San Pedro [mailto:TJedrzejewicz@xxxxxxxxxxxx] 
Sent: Thursday, April 03, 2003 11: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.

This e-mail is for the use of the intended recipient(s) only.  If you have 
received this e-mail in error, please notify the sender immediately and 
then delete it.  If you are not the intended recipient, you must not use, 
disclose or distribute this e-mail without the author's prior permission. 
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any 
attachment to this message.  We cannot accept liability for any loss or 
damage caused by software viruses.



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