Re: PTF Steps?

[Pete Massiello <pmassiello@xxxxxxxxxxxxxxxx>]

Rob,

   Only one suggestion. I don't like to do *IMMDLY because I want the 
whole Cume to be loaded at the same time.  But I understand your issue 
with dedicated system time being at a premium.  In those cases, I would 
keep it at *DLYALL, but 1 or 2 hours before bringing the system down, I 
would run the command APYPTF LICPGM(*ALL)  APY(*TEMP) DELAYED(*IMMDLY). 
That would give us the best of both worlds.

Pete

rob@xxxxxxxxx wrote:

> 1 - They can ALL be done anytime.  Change INSTYP to either *DLYALL or 
> *IMMDLY.  Why increase your dedicated system time to do that part of the 
> INSPTF?
> 2 - See 1.
> 3 - Yes.  Keep in mind, that if you've done the ftp to get the binary in 
> the same ifs directory as your image catalog you can do a ADDIMGCLGE 
> TOFILE(*fromfile) and not have to have the binary in your ifs twice.  And, 
> the big kicker, that addimgclge will run like a scalded dog.
> 4 - I make 3 image catalogs for ptf's:  CUME, all groups, and one called 
> MISC.  I do
> ADDIMGCLGE IMGCLG(CUME) TOFILE(*FROMFILE) (repeat as necessary)
> LODIMGCLG IMGCLG(CUME) DEV(OPTVRT01)
> INSPTF LICPGM((*ALL)) DEV(OPTVRT01) INSTYP(*DLYALL)
> LODIMGCLG IMGCLG(CUME) DEV(OPTVRT01) OPTION(*UNLOAD)
> ADDIMGCLGE IMGCLG(GROUP) TOFILE(*FROMFILE) (repeat as necessary)
> LODIMGCLG IMGCLG(GROUP) DEV(OPTVRT01)
> INSPTF LICPGM((*ALL)) DEV(OPTVRT01) INSTYP(*DLYALL)
> LODIMGCLG IMGCLG(GROUP) DEV(OPTVRT01) OPTION(*UNLOAD)
> ADDIMGCLGE IMGCLG(MISC) TOFILE(*FROMFILE) (repeat as necessary)
> LODIMGCLG IMGCLG(MISC) DEV(OPTVRT01)
> INSPTF LICPGM((*ALL)) DEV(OPTVRT01) INSTYP(*DLYALL)
> LODIMGCLG IMGCLG(MISC) DEV(OPTVRT01) OPTION(*UNLOAD)
> Followed by a lot of RMVIMGCLGE's.
>
> Wait until the weekend.  IPL.
>
> I also put all the steps in the email to download the data in a script 
> file.  See also II-B at
> http://faq.midrange.com/data/cache/67.html
>
> Rob Berendt
>