Dear Marc
In my experience, I can assure you that corrupted downloaded file is one common issue when the file is in GB range and it happens to all types of file, not just the installation image. It did not happen too many times but more than a few times. Adding each downloaded image file one by one as an image catalog entry is the right thing to do to detect corrupted file.
------------------------------
Right action is better than knowledge; but in order to do what is right, we must know what is right.
-- Charlemagne
Satid Singkorapoom
------------------------------
Original Message:
Sent: Fri September 23, 2022 02:27 PM
From: Marc Carpenter
Subject: OS Upgrade Image Catalog failing verification
Thank you, I had done that and applied about 4 PTFs that were missing.
I resolved the issue.. turned out to be a corrupt IBM image file.
I deleted the catalog and added the entries back one by one and ran verification.
Verification finally failed on a file, so I deleted that file, and downloaded it again from ESS.
After adding the new one to the catalog, it verified successfully.
Very strange way to find out I had a bad file, because in every other way, it looked good.
Thank you.
------------------------------
Marc Carpenter
Original Message:
Sent: Fri September 23, 2022 12:02 PM
From: Paolo Salvatore
Subject: OS Upgrade Image Catalog failing verification
Hi Marc,
before upgrading from v7r1 to v7r2, I suggest to read memo to user, and check for every requirements including PTF.
Probably you don't have some ptf.
Check it.
Bye
------------------------------
Paolo Salvatore
Original Message:
Sent: Thu September 22, 2022 06:46 PM
From: Marc Carpenter
Subject: OS Upgrade Image Catalog failing verification
I've been asked to upgrade a v7r1 server to v7r2 (I know...)
Coming here because there is no extended support on this server, but we are addressing that with IBM, but in the meantime...
I downloaded the LICPGM udf files from ESS and put them into an image catalog.
But when I run a verify on the catalog, it fails with OPT1325
I've searched this error code and can find nothing helpful.
From joblog:
Volume 220922184052179 added to optical device.
Optical volume format not recognized.
Pointer not set for location referenced.
And if I work with the optical volumes, it shows the volume type as "damaged".
Anyone seen this before?
I also downloaded PTFs for 7.2 and that catalog loads and verifies fine.
------------------------------
Marc Carpenter
------------------------------