MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » December 2013

Re: Damaged QSYS2/SYSIXADV *FILE



fixed

Hi,

Below is the procedure how to recover this damaged *FILE from IBM:

This document explains how to recover from a damaged SYSIXADV file.

To recover from having a damaged SYSIXADV file, you should follow these
steps:

1. Replace QSYS2 with QSYS2nnnnn for an IASP.
2. Replace zz with the CCSID used by character columns using the DSPFFD
command on QSYS/QADBXREF file.

These steps are best executed when application activity is quiesced.

ALCOBJ OBJ((QSYS2/SYSIXADV *FILE *EXCL)) CONFLICT(*RQSRLS)
DLTF QSYS2/SYSIXADVIX
DLTF QSYS2/CONDIDXA
DLTF QSYS2/SYSIXADV
CHGJOB CCSID(zz)
CALL QSYS/QSQSYSIBM
CALL QSYS/QSQIBMCHK

You should also check for the following PTFs:

*R540*
o MF52711
o MF52919
o MF55209
o MF56030

*R545*
o MF52712
o MF52920
o MF55210
o MF56031

*R610*
o MF52651
o MF52921
o MF56500
o MF55204
o MF56032

*R611*
o MF52652
o MF52922
o MF56501
o MF55205
o MF56033

*R710*
o MF52923
o MF56499
o MF55203
o MF56034

Best regards
Tsetso


On Tue, Dec 17, 2013 at 4:58 PM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

Rob,

I'm not surprised at your findings. True, if BRMS finds an object it
cannot
back up, it continues to get everything it can then reports that in the
BRMS
log. What I have my technicians doing is check the BRMS log every day
looking for the completion messages. If no error which is the normal
status, good to go, if not then we investigate.

While we do it a bit differently ( we use a piece of software to monitor
the
BRMS message queue to look for those things rather than do it manually ) we
are following the procedure you've outlined with all of our customers.
Last night we had a production save fail due to a bad tape unit so we
dispatched IBM to fix it even before we called the customer.

Looks like a RCLSTG *DBXREF is in your near future......... Have a nice
weekend.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, December 17, 2013 8:18 AM
To: Midrange Systems Technical Discussion
Subject: Re: Damaged QSYS2/SYSIXADV *FILE

Just noticed that I have this same object damaged on two lpars: GDISYS,
GDIHQ.


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: rob@xxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Date: 12/17/2013 09:02 AM
Subject: Damaged QSYS2/SYSIXADV *FILE
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Damaged objects will not blow up a BRMS save. You really have to review
it to even realize there was a damaged object.

I am mulling over these special instructions
DSPLOGBRM PERIOD((hhmm mmddyy) (hhmm mmddyy)) OUTPUT(*PRINT)
where the time and dates span the entire save length
DSPSPLF FILE(QP1ALG) SPLNBR(*LAST)
Browse for "libraries saved". It should appear twice. First for the *IBM

save, then for the *ALLUSR save.
Record the number of libraries saved for *IBM ___________
Record the number of libraries saved for *ALLUSR _____________
Did you see any "partially saved"? __________
If so:
Then you should see messages like the following immediately after that
message:
CPF3741 60 *FILE SYSIXADV in QSYS2 not saved.
CPF3763 60 *DTAQ JOBNOTIFY in library QGPL previously damaged.
CPF3763 60 *DTAQ IMWDDQ in library MKSIM previously damaged.
Record these into an email to Rob Berendt. The system name should be part

of the subject line.
Do a DSPJOB. Record the job name, number and user. Add that to the email

also.

In the joblog I see:

CPF3285
Message . . . . : Damage found on file SYSIXADV in library QSYS2.
Cause . . . . . : The requested operation was not done for file SYSIXADV

in
library QSYS2 because of damage to the file. File SYSIXADV is either
damaged or destroyed. Recovery . . . : Delete and then create file
SYSIXADV again. Then try the request again.

CPF3741
Message . . . . : FILE SYSIXADV in QSYS2 not saved.

CPF3777
Message . . . . : 810 libraries saved, 3 partially saved, 0 not saved.

CPF3771
Message . . . . : 292 objects saved from QSYS2. 1 not saved.

How do I fix this?
Note: Had a drastic power failure Friday.

Also, is there something like DSPOBJD which will say if the object is
flagged for damage?

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

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact