|
midrange.com
What was the physical link for FROMFILE('iptf0098_1.bin')? Meaning, if
you did a WRKLNK '/*' and chased up the tree and found the file, then did
an F22 what would the entire file name be?
If you did a WRKIMGCLGE on your image catalog what is the directory name
at the top?
What I am suspecting is that these were different directories and it
copied from one to the other. I'd sure be happy to hear otherwise, and
how.
Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin
bdietz@xxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/03/2003 02:16 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc
Subject
RE: ADDIMGCLGE
this worked for me the other day
Message . . . . : -ADDIMGCLGE IMGCLG(IPTF)
FROMFILE('iptf0098_1.bin')
TOFILE(*fromfile) REPLACE(*INSERT)
00 10/30/03 19:45:24.703184 QVOIADDE QSYS 05EA
QWCCDSAC QSYS 0543
Message . . . . : Image catalog entry added to image catalog IPTF.
-------------------------
Bryan Dietz
3X Corporation
614-410-9205
midrange-l-bounces@xxxxxxxxxxxx wrote on 11/03/2003 02:05:19 PM:
> ADDIMGCLGE IMGCLG(PTFCATALOG)
> TOFILE(*FROMFILE)
> CPDBC2A - FROMDEV or FROMFILE parameter required.
>
> Rob Berendt
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
>
>
>
> bdietz@xxxxxx
> Sent by: midrange-l-bounces+rob=dekko.com@xxxxxxxxxxxx
> 11/03/2003 01:58 PM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> cc
>
> Subject
> RE: ADDIMGCLGE
>
>
>
>
>
>
>
>
>
>
> I think you need to get rid of the directory path. Since the IMGCLG
knows
> where the files are kept there is no need for the directory path.
>
>
> -------------------------
> Bryan Dietz
> 3X Corporation
> 614-410-9205
>
>
>
>
>
>
>
> rob@xxxxxxxxx
> Sent by:
> midrange-l-bounce
To
>
> s@xxxxxxxxxxxx Midrange Systems Technical
> Discussion
> <midrange-l@xxxxxxxxxxxx>
> 11/03/2003 08:57
cc
>
> AM
>
Subject
>
> RE: ADDIMGCLGE
> Please respond to
> Midrange Systems
> Technical
> Discussion
> <midrange-l@midra
> nge.com>
>
>
>
>
>
>
> Gave the following a try:
> ADDIMGCLGE IMGCLG(PTFCATALOG)
> FROMFILE('/fixes/iptf0045_1.bin')
> TOFILE(*fromfile)
>
> CPDBC29
> Message . . . . : Image already exists in image catalog PTFCATALOG.
> Cause . . . . . : Image iptf0045_1.bin already exists in image catalog
> PTFCATALOG at index 1.
> Recovery . . . : Either specify REPLACE(*YES) or a different file
name
> on
> the TOFILE parameter and try the request again.
>
> Apparently it insists on doing the copy. But it will use the same file
> name provided that the directory of the FROMFILE parameter is not the
same
> as
> CRTIMGCLG IMGCLG(PTFCATALOG) DIR('/fixes') TEXT('PTF image catalog')
> So evidently there is no getting around the sucking sound of disk space
> and wasted, wasted time.
>
> Rob Berendt
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
>
>
>
> rob@xxxxxxxxx
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 10/15/2003 01:00 PM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> cc
>
> Subject
> RE: ADDIMGCLGE
>
>
>
>
>
>
> Thanks for slapping that into my head. Pi$$ed away a few hours
yesterday
> waiting for ADDIMGCLGE to complete.
>
> Rob Berendt
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
>
>
>
> bdietz@xxxxxx
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 10/15/2003 12:26 PM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> cc
>
> Subject
> RE: ADDIMGCLGE
>
>
>
>
>
>
>
>
>
>
> Rob did you get the note about ho to not have the files duplicated??
> I use the following
>
> ADDIMGCLGE IMGCLG(PTF19)
> FROMFILE('/fixes/P19/iptf0019_1.bin')
> TOFILE(*FROMFILE)
>
> Using *FROMFILE will not give you the duplicate ones.
>
> >From the help:
> <snip>
> *FROMFILE
> The file name will be the same name as source image. If the
> source image is from optical media, the name given to the file
> will be the volume ID. If the source image is from another
> directory, the file will be given the same name as that in the
> source directory.
> </snip>
>
>
> -------------------------
> Bryan Dietz
> 3X Corporation
> 614-410-9205
>
>
>
>
>
>
>
> rob@xxxxxxxxx
> Sent by:
> midrange-l-bounce
To
>
>
> s@xxxxxxxxxxxx Midrange Systems Technical
> Discussion
> <midrange-l@xxxxxxxxxxxx>
> 10/15/2003 10:38
cc
>
>
> AM
>
Subject
>
>
> RE: ADDIMGCLGE
> Please respond to
> Midrange Systems
> Technical
> Discussion
> <midrange-l@midra
> nge.com>
>
>
>
>
>
>
> Dang! You have to run the ADDIMGCLGE!
>
> > CRTIMGCLG IMGCLG(PTF19) DIR('/fixes/p19')
> Ownership of object PTF19 in QUSRSYS type *IMGCLG changed.
> Image catalog PTF19 created in library QUSRSYS.
> > vrycfg cfgobj(optvrt01) cfgtype(*dev) status(*on)
> Device OPTVRT01 currently on-line.
> > lodimGCLG IMGCLG(PTF19) Dev(optvrt01)
> No image catalog entries are in loaded status.
> Image catalog PTF19 not loaded to device OPTVRT01.
>
> > DSPMSGD CPDBC10
> Message . . . . : No image catalog entries are in loaded status.
> Cause . . . . . : The loading of image catalog PTF19 found no catalog
> entries to be loaded.
> Recovery . . . : Use the WRKIMGCLGE command to ensure there is at
least
> one
> image catalog entry is in loaded status and retry the command.
>
> > WRKLNK '/fixes/P19/*'
> Object link Type
> . DIR
> .. DIR
> ftp0019.txt STMF
> ilst0019.txt STMF
> iptf0019_1.bin STMF
>
> > ADDIMGCLGE IMGCLG(PTF19) FROMFILE('/fixes/P19/iptf0019_1.bin')
>
> > WRKLNK OBJ('/fixes/P19/*')
> Object link Type
> . DIR
> .. DIR
> ftp0019.txt STMF
> ilst0019.txt STMF
> iptf0019_1.bin STMF
> iptf0019_1.bin01 STMF
>
> > LODIMGCLG IMGCLG(PTF19) DEV(OPTVRT01)
> Volume *VIRTUALEXPORT removed from optical device.
> Volume C5302273_01 added to optical device.
> Image catalog PTF19 loaded in device OPTVRT01.
>
> > VFYIMGCLG IMGCLG(PTF19) TYPE(*PTF) SORT(*YES)
>
> > GO PTF
> > 8. Install program temporary fix package
>
> Rob Berendt
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
>
>
>
> "Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 10/09/2003 02:46 PM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> "'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx>
> cc
>
> Subject
> RE: ADDIMGCLGE
>
>
>
>
>
>
> You shouldn't need to, the CRTIMGCLG IMGCLG(PTFCATALOG) DIR('/fixes')
> associates the directory with the image catalog and the LODIMGCLG
> IMGCLG(PTFCATALOG) DEV(OPTVRT01) loads whatever image is in that
> directory.
>
>
> I have not done this with downloaded fixes, but I did a v4r5 to v5r2
> upgrade
> and preloaded the image catalog for PTF's by creating it on a v5r2
system
> and restoring the directory to the v4r5 system. After the upgrade I
just
> did the CRT and the LOD. I did the VFY and the images were even in the
> correct order.
>
> Scott Ingvaldson
> AS/400 System Administrator
> GuideOne Insurance Group
>
> -----Original Message-----
> date: Thu, 9 Oct 2003 14:04:41 -0500
> from: rob@xxxxxxxxx
> subject: RE: ADDIMGCLGE
>
> Then what associates that particular .bin with the virtual optical
drive?
>
> Rob Berendt
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
>
> "Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 10/09/2003 01:34 PM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> "'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx>
> cc
>
> Subject
> RE: ADDIMGCLGE
>
> You should be able to skip the ADDIMGCLGE step if the image already
exists
> in the directory.
>
> Regards,
>
> Scott Ingvaldson
> AS/400 System Administrator
> GuideOne Insurance Group
>
> -----Original Message-----
> date: Thu, 9 Oct 2003 10:04:36 -0500
> from: rob@xxxxxxxxx
> subject: ADDIMGCLGE
>
> I've been using ftp to download ptf's. The steps basically are:
> Find out what ptf's you want.
> Use iPTF to order them.
> Read your email for the ftp is ready email.
> Use ftp from your iSeries to get them into the IFS.
> CRTDEVOPT DEVD(OPTVRT01) RSRCNAME(*VRT) ONLINE(*YES) TEXT('Virtual
optical
>
>
> drive for image catalog')
> VRYCFG CFGOBJ(OPTVRT01) CFGTYPE(*DEV) STATUS(*ON)
> CRTIMGCLG IMGCLG(PTFCATALOG) DIR('/fixes') TEXT('PTF image catalog')
> ADDIMGCLGE IMGCLG(PTFCATALOG) FROMFILE('/fixes/TheFtpFileNameHere')
> LODIMGCLG IMGCLG(PTFCATALOG) DEV(OPTVRT01)
> VFYIMGCLG IMGCLG(PTFCATALOG) TYPE(*PTF) SORT(*YES)
> GO PTF
> 8. Install program temporary fix package
>
>
> The problem I have is with the
> ADDIMGCLGE IMGCLG(PTFCATALOG) FROMFILE('/fixes/TheFtpFileNameHere')
> For example, if I ftp down this file, iptf0021_1.bin, with a size of
> 500611072, then run the ADDIMGCLGE, I'll now have two files; the
original
> and a iptf0021_1.bin01, both of the same size.
>
> Is there some option on ADDIMGCLGE that says not to copy the data over,
> but just point to it?
>
>
> Rob Berendt
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
> This message and accompanying documents are covered by the Electronic
> Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains
> information
> intended for the specified individual(s) only. This information is
> confidential. If you are not the intended recipient or an agent
> responsible
> for delivering it to the intended recipient, you are hereby notified
that
> you have received this document in error and that any review,
> dissemination,
> copying, or the taking of any action based on the contents of this
> information is strictly prohibited. If you have received this
> communication
> in error, please notify us immediately by e-mail, and delete the
original
> message.
>
> _______________________________________________
> 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 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 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 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.
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.
