RSTLICPGM question

[Troy Paulson]

My company started licensing our programs using IBM's licensing commands
(CRTPRDDFN, ADDPRDLICI, CRTPRDLOD, SAVLICPGM, RSTLICPGM, etc.). This worked
well for our first version of our software. Now we have come out with our
second version using licensing. The restore of the program worked OK on our
system, but when I installed it at a client site, the RSTLICPGM command
placed all of the objects in libraries for the previous version (we use
different libraries for each version), instead of creating the new libraries
and placing the objects in them. If anyone knows of any gotcha's that I may
have missed, or would like to see more information on our problem, please
let me know. You contact me through this newsgroup or via email
tpau...@nsc-inc.com.

TIA
Troy

[Dan Hicks]

I don't know all the details, but I do know that there are a lot of
somewhat strange restrictions in the LICPGM stuff. It's best to make
the different versions of your product be features of the LICPGM, vs the
LICPGM itself, so that they can be installed simultaneously and into
different libs.

(This is the extent of my knowledge -- I just got this from being caught
in a development project that ran into similar problems.)

--
Dan Hicks
If a vegetarian eats vegetables, what does a vulgarian eat?

[Alex Nubla]

Hello Troy:

Product Definition (*PRDDFN) & Product Load Definitions (*PRDLOD) are
part of the IBM Application Development Manager Product.

I think your problem could be when you created the *PRDLOD (using
CRTPRDLOD), you may not be pointing to the correct primary library
(PRILIB). I am guessing that you are pointing to previous version's
library. On a RSTLICPGM, it looks at both *PRDDFN & *PRDLOD
information to determine what license program description to use and
where to restore the product library to.

I could be wrong (last time I used this was in 1995), I am not sure if
these commands are still supported under V4R5 and up. But I used this
technique before to package my software.

Regards,
Alex Nubla

"Troy Paulson" <tpau...@nsc-inc.com> wrote in message news:<wfA38.3$ae4.106@client>...

[Ugo Gagliardelli]

If a previous release has been already installed its libraries will be
used installing a new one, unless you deny dynamic naming during the
product creation, then permit or deny multiple release support at your
coice.
--
Dr.Ugo Gagliardelli,Modena,Italy-Certified uindoscrasher-AlcoolInside
Spaccamaroni andate a cagare/Spammers not welcome
Spamers iros a la mierda/Spamers allez vous faire foutre
Spammers loop schijten/Spammers macht Euch vom Acker

[Ugo Gagliardelli]

Ugo Gagliardelli wrote:
>
> Troy Paulson wrote:
> >
> > My company started licensing our programs using IBM's licensing commands
> > (CRTPRDDFN, ADDPRDLICI, CRTPRDLOD, SAVLICPGM, RSTLICPGM, etc.). This worked

[cut]

> If a previous release has been already installed its libraries will be
> used installing a new one, unless you deny dynamic naming during the
> product creation, then permit or deny multiple release support at your
> coice.

P.S. I don't know with paramter or command because I'm using the
equivalent Licensed Product APIs (no cost), I guess you should seek
somewhere in CRTPRDDFN command.

[Worley Barry]

On Wed, 23 Jan 2002 09:01:41 -0600, Troy Paulson wrote:

>My company started licensing our programs using IBM's licensing commands
>(CRTPRDDFN, ADDPRDLICI, CRTPRDLOD, SAVLICPGM, RSTLICPGM, etc.). This worked
>well for our first version of our software. Now we have come out with our
>second version using licensing. The restore of the program worked OK on our
>system, but when I installed it at a client site, the RSTLICPGM command
>placed all of the objects in libraries for the previous version (we use
>different libraries for each version), instead of creating the new libraries
>and placing the objects in them.

I'm using API;s instead of commands to create products, but
I'm reference the corresponding command here. I have trouble
matching API parameters and Command Keywords

I have a complex product with multiple libraries and
features. That is, a common database library for data files,
feature(option) libraries for executable programs, a general purpose
library for OUTQs, JOBQs. SBSDs etc.

CRTPRDDFN and CRTPRDLOD have different libraries labels.
Development Libraries, Primary Libraries, Principal Libraries, etc.
CHGPRDOBJD accepts different libraries for objects in a PRDLOD.

RSTLICPGM (F9 more prompts) allows the entry of 10 different libraries.

IBM does allow multiple releases of your products BUT NOT DUPLICATE
RELEASES in different Libraries. Therefore I must delete the libraries
used to create the distribution (Tape or SAVF) before I can restore it.

1st guess, You can specify replace release *FIRST or *ONLY with
RSTLICPGM, which might put your new release in the old library.

My 2st guess, is that creating the distribution on your
system forced you to delete all references to it on your system but
left something on the client system.

3rd guess, The libraries on CRTPRDDFN and CRTPRDLOD are not
defaulting as you expected.

Regards, Worley