Product Maintenance or Version Upgrades
No new passwords are required; however, you must ensure that your authorization tables reside in the new production libraries. If you install products in a test environment before moving them to production, the authorization tables must also reside in the test libraries. If you try to execute the product on a different CPU, that CPU must also be licensed.
The product authorization tables should be copied from the 'old' library to the 'new' library that contains the product's new maintenance or upgrade.
Although the product authorization tables typically reside in the product's load library, these tables are not load modules. If you are running ISPF V4.2 or above, you might not be able to copy these tables using the ISPF Move/Copy utility (option 3.3). You could receive a STOW error or one or more of the following error messages:
IEW2522E 470E MEMBER cccTBL3n IDENTIFIED BY DDNAME ISPxxxxx... IS NOT A LOAD MODULE- (INVALID RECORD TYPE).
IEW2307S 1032 CURRENT INPUT MODULE NOT INCLUDED BECAUSE OF INVALID DATA.
COPY FAILED FOR MEMBER cccTBL3n. FAILURE IN IEWBIND INCLUDE, RETURN CODE 8 REASON CODE 83000507
where xxxxx is the ddname, ccc is the 3-character product code and n is either P (permanent) or T (temporary).
If you receive any of these messages, use the IEBCOPY utility to copy the tables. Do not use the IEBCOPY COPYMOD parameter when copying the product authorization tables.