If you need help with any of the techniques described below, feel free to contact our support team.
I’m upgrading to OS/400 V6R1M0/V7R3M0: do I need a special version?
No, there is no special version of our software needed to run on either OS/400 V6R1M0 or OS/400 V7R3M0 (IBM i 6.1 or 7.3).
The only known issue that relates to any version of our software running on OS/400 V6R1M0 or later affects CoolSpools Version 5 (and earlier versions of CoolSpools) but is rather obscure and unlikely to be a problem for the vast majority of customers: namely, spooled files larger than about 16 Mb in size saved with our SAVSPLF command can give a memory error when restored with our RSTSPLF command because an IBM API default has changed at V6R1M0. Unless this sounds like something that is going to concern you, we would not recommend applying any of our fixes/PTFs before you upgrade. This issue was fixed in CoolSpools PLUS PTF 5CP0116 and CoolSpools PTF 5CV0219. We only recommend installing the latest fix/PTF before you upgrade if (a) this sounds like an issue that might affect you and (b) you do not already have that PTF or later applied.
We only recommend installing the latest fix/PTF before you upgrade if:
To check your PTF level, do DSPPTF 5COOLSP (CoolSpools PLUS) or DSPPTF 5CVTSPL (CoolSpools)
If this shows “No PTFs”, that simply means that you have not applied any PTFs since you installed: your installed code level could still include the relevant fixes. Do DSPPGM COOLSPV5R1/CS_RSTSPLR (CoolSpools PLUS) or DSPPGM CVTSPLV5R1/CS_RSTSPLR (CoolSpools): if the program creation date is 2008-06-24 or later, you do not need to apply the PTF for the fix described above.
Like all programs created on an earlier version of OS/400, you will, of course, need to ensure that CoolSpools programs are subjected to program conversion as part of your upgrade to V6R1M0 or V7R3M0 from a release prior to V6R1M0.
You can either use the STROBJCVN command against our product libraries or, if you are restoring objects to a new system, use the option to carry out conversion on the restore operation. We suggest you set the QFRCCVNRST system value to 2 (“Objects requiring conversion to be used on the current version of the operating system or on the current machine will be converted. Objects with validation errors will also be converted.”) or 7 (“All objects will be converted.”) and specify FRCOBJCVN(*SYSVAL) (the default) on the RSTxxx command when restoring objects to the new system. Conversion will then occur automatically.
When you run the ANZOBJCVN command against CoolSpools objects, it may report that object attributes will be lost on conversion. This can safely be ignored. The only object attribute affected is the digital signature, which is invalidated by the conversion process. The purpose of the digital signature is to prove that the objects you download and install are genuine and have not been tampered with since we created them. The digital signature is not required for the objects to function correctly and the objects will run as before once they have been converted.
You should only need new license keys when the serial number and/or software processor group code (P05-P50) of your system changes as part of a hardware swap or upgrade. So, if all you’re doing is upgrading the operating system, no new license key should be needed.
However, it does happen occasionally that customers find they are told their license keys have expired after an OS/400 upgrade. We believe that happens if a scratch install is done or if library QUSRSYS (where OS/400 stores its license keys) gets overwritten or restored as part of the upgrade. If that happens to you, you just need to re-enter your original license keys by re-running the ADDLICKEY command you were sent when you first purchased the license.
If you no longer have a note of your license key(s), just contact our support team and ask for a reminder.