Re: How to use i navigator to copy image catalog data between systems

<snip>
Because the image catalog has to first be saved with *PRV release support.
</snip>
does it? I thought you only needed to specify TGTRLS(*PRV) if you WERE
doing a save. I didn't think that changed the object; just the save file
containing the object. But it's been a long time since I've had a mixed
release environment.
I transfer .bin objects using ftp from my PC to my i and it doesn't care
about TGTRLS(*PRV). Why would that apply in an i-to-i environment? I am
thinking that if you bypass the whole save file then you get past that
*PRV garbage.

Well, you really don't have to recreate the image catalog on the target
system. I just leave it there all the time. All you have to do is rerun
the ADDIMGCLGE as I did in my previous email.



Rob Berendt
-- IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com From: Gerald Kern <jp2558@xxxxxxxxx> To: Midrange <midrange-l@xxxxxxxxxxxx>, Date: 09/19/2012 10:01 AM Subject: Re: How to use i navigator to copy image catalog data between systems Sent by: midrange-l-bounces@xxxxxxxxxxxx "Why on earth would you do that versus a straight binary transfer of the .bin (or .iso) files themselves?" Because the image catalog has to first be saved with *PRV release support. And there is a note in the IBM doc that says the following: *"FTPing Images Without Saving/Restoring and then Re-Creating the Image Catalog Object* These commands are run on the target system where you want to move the images to. The image catalog object (type *IMGCLG) will need to be re-created because it cannot be FTPed."
-- Thanks, Jerry Gerald Kern - Information Technology Programming Supervisor IBM Certified RPG IV Developer Lotus Notes/Domino Administrator The Toledo Clinic, Inc. 4235 Secor Road Toledo, OH 43623 Phone 419-479-5535
--