MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » December 2013

RE: Damaged QSYS2/SYSIXADV *FILE



fixed

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





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