|
On 03/01/2007, at 10:01 AM, Dave Murvin wrote:
midrange.com
I have a software product that I am updating from V1R1M0 to V2R1M0. I
am running on V5R3M0. My process (which I believe is the same as
when I created V1R1M0) is as follows:
Create Service programs for OS version V5R1M0
Create application programs for OS version V5R1M0
Create the Software product by:
Deleting old product definition and product load
Not necessary if you define your product to allow multiple releases.
Create new product definition using QSZCRTPD
Create new product load using QSZCRTPL
Change product load using QLICOBJD (set Licensed
Program, Product Option Load ID, Product Option ID)
Also have to use QLICOBJD to change all the objects in the product to mark them as belonging to a product option.
Package Product Options using QSZPKGPO
At this point I run CHKPRDOPT and receive CPI0C22 - Product 5N8ZMDT
release V2R1M0 option *BASE load 5001 correctly packaged.
This just means that the package step worked successfully. That is: *PRDDFN, *PRDLOD, and objects added to *PRDLOD exist.
I don't see where you defined the product licence information by calling QLZADDLI.
SAVLICPGM to a save file with TGTRLS of V5R1M0 For testing I DLTLICPGM from my machine. Then RSTLICPGM from the save file previously created. During the Restore Licensed Program process I create a temporary 30 day key for the application using QLZAGENK to Generate the License Key then QLZAADDK to Add the License Key.
Not necessary if you define a 30-day grace period. Your product will work for 30 days without a key and then stop until a valid key is added to the licence repository.
The error I am getting is from the QLZAGENK API. CPF9E41 - Product 5N8ZMDT V2R1M0 feature 5001 not found or not correctly installed.
Probably because you are trying to generate the key before the product is properly installed. If you must generate a 30-day key then try it from a Post Operation Exit Program defined on the Product Load. As I said above it is better/easier to use the grace period for this purpose.
Note: If the key is being generated on the same system on which it will be used (dumb idea actually) then it is not necessary to call QLZAADDK. QLZAGENK puts the key in the repository itself.
I am pretty sure it is something I am doing differently from my V1R1M0 version, but I have not been able to find the problem over several days. I guess what I don't understand is why CHKPRDOPT says all is okay before I save and restore the LicPgm but the QLZAGENK API doesn't seem to like it.
Because CHKPRDOPT doesn't check the licensed program is installed. It just checks that each of the objects listed in the Product Load can be found (i.e. no missing objects).
Is there something else I could use to help pin down what is missing (how can I see if all the required information for the product is actually there) or what is incorrectly installed?
Use GO LICPGM to view the actual status of your product when the error is sent from QLZAGENK. You can also use the QSZRTVPR API with format PRDR0100 to see the Load State and Symbolic Load State. My guess is that the product will show as *LOADED but ought to be *INSTALLED.
As far as I recall the only requirement for QLZAGENK is that the *PRDDFN object can be found. This holds the product licensing definition (). The rest of the product does not need to exist. So my guess is that you are calling QLZAGENK too early in the RSTLICPGM process. Or possibly your code is using the old release product identifiers. Or that you haven't defined licence information into the product definition.
Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400, iSeries, System i Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
