Rob and the group,
I'm rethinking the way I run my BRMS STRBKUBRM dedicated system saves. Years back, we switched from running interactively from the console to SBMJOB(*CTLSBS).
IBM has been unable to identify the reason for the "hung" system save, because the LPAR was forced down, unable to achieve the necessary docs, (joblog, ect.
There was a major reason for this, but I can't remember what that is.
When you do SBMJOB(*CTLSBS), you give up your console and access to the LPAR.
http://www-01.ibm.com/support/docview.wss?uid=nas8N1019121
If a problem occurs, instead of forcing the LPAR, I could have forced DST, but that would require an IPL, not what I really want.
If your system is in a restricted state and you force DST to your HMC console, the console job is ended and an IPL is required to get a new console.
http://www-01.ibm.com/support/docview.wss?uid=nas8N1018885
So, do I run the STRBKUBRM interactively from the console??
How are most running their system saves?
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, October 27, 2014 7:27 AM
To: Midrange Systems Technical Discussion
Subject: Re: CPF7001 - Damage was detected but has been ignored ; CPF0C4D - Error occurred while processing object QSZPAVLI in library QUSRSYS.
http://lmgtfy.com/?q=QSZPAVLI
The first link on the above was very helpful
http://www-01.ibm.com/support/docview.wss?uid=nas8N1017418
Just in case your company does not allow you to use the web at all and that is why you couldn't find that here's what that link said
Damaged Object Named QSZPAVLI
Technote (troubleshooting)
Problem(Abstract)
This document describes a damaged object named QSZPAVLI that was found in message CPF0C4D during an IPL.
Resolving the problem
A damaged object named QSZPAVLI was found in message CPF0C4D during an IPL.
The object QSZPAVLI is the Product Availability Index object which is used to list and provide the available products on the system. It can be found damaged following an abnormal system end (for example, a system crash, utility power outage, and so on).
If it gets damaged, it can be re-created with the Display Software Resource (DSPSFWRSC) command, a call to QSZPAVLI, or during the next successful partition IPL.
Historical Number
22984516
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 10/26/2014 02:35 PM
Subject: CPF7001 - Damage was detected but has been ignored ;
CPF0C4D - Error occurred while processing object QSZPAVLI in library
QUSRSYS.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
I was doing a dedicated system save following an IPL for PTF apply.
The save appeared to be hung, did not see any activity to the tape library
for over an hour.
From the HMC , I forced down the LPAR.
The following IPL resulted in the 1 CPF0C4D and 19 CPF7001.
Each of the CPF7001 occurred while the system was creating and detaching
system journal receivers.
I performed another system save, which was successful, followed by 2 more
IPLs, which were error free.
Do I need to be concerned with the damaged objects, or did the additional
IPLs resolve the issue?
Message ID . . . . . . : CPF0C4D Severity . . . . . . . : 30
Message type . . . . . : Escape
Date sent . . . . . . : 10/25/14 Time sent . . . . . . : 22:08:02
Message . . . . : Error occurred while processing object QSZPAVLI in
library
QUSRSYS.
Cause . . . . . : While processing object QSZPAVLI type *PRDAVLI in
library
QUSRSYS an error occurred which prevented the operation from completing
successfully. The return code is 0099-DAMAGED.
Recovery . . . : See the previously listed messages. Correct any
errors,
and try the request again.
Message ID . . . . . . : CPF7001 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Date sent . . . . . . : 10/25/14 Time sent . . . . . . : 22:08:13
Message . . . . : Damage was detected but has been ignored.
Cause . . . . . : Damage was detected during the requested operation.
However, the operation was completed.
Recovery . . . : Look at the job log (DSPJOBLOG command) for the
messages
that identify the cause of the damage.
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
midrange.com
