|
If there is a more recent ptf for V4R5, and if it was still supported (hee
hee)
Hey the object is already wacked. You can't save it, (try saving it to a
save file), might as well delete it while you are hunting for a copy from
someone. At least your GO SAVE 21 won't hurl.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
"Steve Moland" <Steve@xxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/31/2007 04:25 PM
Please respond to
Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
To
<midrange-l@xxxxxxxxxxxx>
cc
Fax to
Subject
Re: DASD upgrade and start Mirroring
Chuck,
Thank you,,,,,,and Wow, that's some knowledge that is really down in the
lower layers of the trenches.
As a general comment to the community, could I solicit a volunteer to
send me a savefile of object QSYS/QKRBGSS from a system at V4R5. .....
Pretty please!
Steve Moland
Access Paths Inc
12 Parmenter Rd Unit C4
Londonderry NH 03053
603 845-0190 Ext 2
steve@xxxxxxxxxxx
date: Thu, 31 May 2007 13:58:18 -0500
from: CRPence <crp@xxxxxxxxxxxxxxxxxxxx>
subject: Re: DASD upgrade and start Mirroring
FWiW a RCLSTG can *not* _correct_ 'physical' damage. Thus that
request can not resolve the condition of damage for the two objects
noted to have already been identified as damaged.
The two objects noted:
QSYS/QKRBGSS *SRVPGM 1 <- Kerboros
QSYS/QDPDD1P *FILE 1 <- Problem Determination (DSPF)
WRKOPTVOL and look for the display file (DSPF) in a directory like
the following: OPTFILE( '/Q5722SS1/Q5400024/Q00/Q90' ) to
issue a RSTOBJ
from, after DLTF QSYS/QDPDD1P
The *SRVPGM I believe, after DLTSRVPGM QSYS/QKRBGSS, can be safely
restored from any system of the same release; or on v5r4, by load and
apply of PTF SI25838 which includes that object, if not already perm
applied.
Regards, Chuck
--
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.
As an Amazon Associate we earn from qualifying purchases.
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.