|
midrange.com
> From: rob@xxxxxxxxx
>
> Another approach I do is create multiple image catalogs.
> md '/fixes'
> md '/fixes/cume'
> md '/fixes/SF99529'
> md '/fixes/SF99269'
> CRTIMGCLG IMGCLG(CUME) DIR('/fixes/cume')
> CRTIMGCLG IMGCLG(SF99529) DIR('/fixes/SF99529')
> CRTIMGCLG IMGCLG(SF99269) DIR('/fixes/SF99269')
> ...
> Then you just run multiple
> LODIMGCLG IMGCLG(CUME) DEV(OPTVRT01) OPTION(*LOAD)
> GO PTF, Option 8, no ipl
> LODIMGCLG IMGCLG(CUME) DEV(OPTVRT01) OPTION(*UNLOAD)
> LODIMGCLG IMGCLG(SF99529) DEV(OPTVRT01) OPTION(*LOAD)
> GO PTF, Option 8, no ipl
> LODIMGCLG IMGCLG(SF99529) DEV(OPTVRT01) OPTION(*UNLOAD)
I barely have room for a single image catalog, so I think I'll do this
one step at a time. But I'm going to try performing the ADDIMGCLGE for
each .bin file and then deleting the .bin file. After all are loaded,
I'll do the verify and then the load and apply.
Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.
