I ran option 22 from the save menu and the LPP's didn't save, so I'm wondering
how the savsys completed successfully but LPP's didn't save.



-----Original Message-----
From: qsrvbas@xxxxxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Sent: Thu, 5 Apr 2007 2:51 PM
Subject: Re: SAVLICPGM changing QBRMS?


Tom Liotta wrote:
fbocch2595@xxxxxxx wrote:

Hi folks, I ran green screen cmd SAVLICPGM and selected all licpgm's (I
didn't want to run SAVSYS) and after it completed my audit report shows that
usrprf QBRMS was changed to password of *NONE.

Any idea why that is or if it's possible that running cmd SAVLICPGM would
change usrprf QBRMS?

Frank:

I can't answer "Why?" but I can tell you it's definitely possible
that SAVLICPGM could change a password.

It's common for LPPs to have exit programs that are called before
and/or after SAVLICPGM, RSTLICPGM, DLTLICPGM and CHKPRDOPT. Setting
attributes of user profiles associated with an LPP is a kind of
action that such an exit program would reasonably do.

Whether setting password to *NONE makes sense for QBRMS...? I don't
know. If that's an expected attribute, then it _might_ have been
coded by the developer of the BRMS exit programs.

One minor additional note...

AFAIK, SAVLICPGM and SAVSYS are practically unrelated. Except for
OS/400 and LIC, I don't think much overlap exists between the two.
For any given LPP (other than 5722SS1), you need to run SAVLICPGM if
you expect ever to RSTLICPGM.

Even a full-system save doesn't exactly give you RSTLICPGM
capability. Of course, if you do a full-system restore from a
full-system save, you pretty much get it all back; but that's a hard
way to go if you only want to restore a particular product.

Again, that's all "AFAIK". Others might have better info to add.

Tom


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.