Re: PTF Steps?

Thanks .. this is excellent.  I am going to try it with the July cume this
weekend; the binaries are downloading right now.

I have a couple of conclusions; please let me know if they are not correct.

1 -- all of the steps until the INSPTF can be done anytime.
2 -- for the cume, the INSPTF should be done at a time when an IPL can be
performed.  It may take a while.
3 -- the ADDIMGCLGE must be done for each binary file, and it must be done
in the sequence that the binary files should be processed.  That sequence is
the sequence (PTF_1, PTF_2 ... ) that IBM specifies via the names of the
files.
4 -- Due to the binary file sequencing, the INSPTF will end up processing
the fixes in the proper order (?HIPER, Group, DB, etc.).

Is this making sense?

On 9/29/06, Peter Levy <plevy@xxxxxxxxxxxx> wrote:

I normally FTP them from IBM directly to the iSeries, but no matter...

First FTP it from your PC to the /tmp IFS directory:
- FTP <iseries.system.name or ip-address>
- cd /tmp
- lcd /mylocalptfdirectory
- bin
- put <binaryfile>.bin
- quit
Then do the following to create a virtual CD drive & image catalog and
install the PTFs:
- CRTDEVOPT DEVD(OPTVRT01) RSRCNAME(*VRT)
- VRYCFG CFGOBJ(OPTVRT01) CFGTYPE(*DEV) STATUS(*ON)
- CRTIMGCLG IMGCLG(PTFINSTALL) DIR('/ptfinstall') CRTDIR(*YES)
- ADDIMGCLGE IMGCLG(PTFINSTALL) FROMFILE('/tmp/<binary file>.bin')
- LODIMGCLG IMGCLG(PTFINSTALL) DEV(OPTVRT01)
- VFYIMGCLG IMGCLG(PTFINSTALL) TYPE(*PTF) SORT(*YES)
- INSPTF LICPGM((*ALL)) DEV(OPTVRT01) INSTYP(*DLYALL) (Note: If this
command doesn't exist on your system then do GO PTF, option 8.)