Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Damaged objet (save file) QPZA0000018 in QCAP3 library

154 views
Skip to first unread message

CENTRINO

unread,
Nov 25, 2009, 3:27:42 PM11/25/09
to
During option 21 menu save we got an error that stopped the save operation
becouse of a damaged object, a save file, named QPCA0000018 in QCAP3
library.

There are several save files like QPCA00* in the library.

Is such a save file important? Should I restore it or even delete it before
continuing the SAVE operation?

We are on V5R3M0

Our intention is to perform a RCLSTG after the save operation.

Thanks in advance.


Dr.Ugo Gagliardelli

unread,
Nov 26, 2009, 3:34:56 AM11/26/09
to
il 25/11/2009 21.27, Scrive CENTRINO 37951616:
Possibly they are save files related to temporary applied PTFs. On my
system I have not that library, so I'm not sure.
If you do DSPSFWRSC command and than press F11, you'll see the list of
installed products and their library, this way you'll be able to
identify whether QCAP3 is a product library or not.
Trying to permanently-apply all PTF of that product, all save files
related to PTFs of that product for the release installed should be
deleted. If some savf keep staying there and there are no ptf marked as
damaged and all PTFs show as perm. installed (show all ptf for that
product with DSPPTF <prod-id> command), maybe they refers to PTFs of a
past release/version of that product, in this case you can delete
remaining save files. Usualy such a figur happens when you install a new
version of an already-installed product omitting to change PTFs status
to somewhat permanent first.
Anyway a damaged object is not so useful!

--
Dr.Ugo Gagliardelli,Modena,ItalyCertifiedUindoscrasherA�ejoAlcoolInside
Spaccamaroni andate a cagare/Spammers not welcome/Spammers v�o � merda
Spamers iros a la mierda/Spamers allez vous faire foutre/Spammers loop
schijten/Spammers macht Euch vom Acker/Spamerzy wypierdalac'

amc

unread,
Nov 26, 2009, 4:59:26 PM11/26/09
to
On Nov 26, 6:34 pm, "Dr.Ugo Gagliardelli"
> Dr.Ugo Gagliardelli,Modena,ItalyCertifiedUindoscrasherAñejoAlcoolInside
> Spaccamaroni andate a cagare/Spammers not welcome/Spammers vão à merda

> Spamers iros a la mierda/Spamers allez vous faire foutre/Spammers loop
> schijten/Spammers macht Euch vom Acker/Spamerzy wypierdalac'

I think you will find that library QCAP3 is associated with Crypto
Access Provider LP (5722-AC3)

I have seen the following at Four Hundred Guru - "Cryptographic access
provider corruption is a known issue in i5/OS V5R3M0 after an i5/
iSeries partition is upgraded, migrated to another box, or restored. "

I think you can use option 11 on the GO LICPGM menu to reinstall the
software using media containing a prior save of the licensed program
or or use the original distribution media.

CRPence

unread,
Nov 28, 2009, 1:48:47 PM11/28/09
to
CENTRINO wrote:
> During option 21 menu save we got an error that stopped the save
> operation because of a damaged object, a save file, named
> QPZA0000018 in QCAP3 library.
>
> There are several save files like QPZA00* in the library.

>
> Is such a save file important? Should I restore it or even
> delete it before continuing the SAVE operation?
>
> We are on V5R3M0
>
> Our intention is to perform a RCLSTG after the save operation.
>

The RCLSTG only provides /damage notification/; i.e. do not
falsely infer that the request will correct damage. Although the
reclaim storage request can [appear to] correct some conditions,
objects marked with /physical damage/ can be corrected *only* by
deleting the object and then optionally recovering the object [and
data] by re-creating and\or restoring [the data]. A save request
stops whenever any newly detected condition of physical damage; had
the object been marked damaged prior to its detection during save,
the object would have simply been omitted and a message logged to
denote the object was skipped due to the indication of damage.

The QPZA* objects are part of a PTF. Whether or when the DLTF
[as recovery from the damage] will impact the PTF is moot; i.e. the
request is required irrespective of how it may impact PTF processing
for the LPP in the QCAP3 library. Deleting an active PTF object
will make a PTF become /damaged/ [logically, not physically damaged]
for which the recovery is to load the PTF again; whether the PTF is
then removed or applied is not relevant since that recovery.

Regards, Chuck

0 new messages