Thanks for your response.
By using your command, I got the following messages:
For RC = 30:
FPLSFS733E Return code 8 reason code 54000 from DMSRDDBK
FPLMSG003I ... Issued from stage 1 of pipeline 1
For RC = 42:
FPLDBK124E Error reading file: Length of record is 24672 but file has
logical
Now you've got CSL reason codes and can ask help for them, like this:
HELP ROUTINES dmsrddbk (ERRORS
and look for 54000
if still not found:
HELP ROUTINES REASCODE
Some of these PIPE messages sound really alarming. Did you do
something special with this SFS server? I didn't have any corrupted
I've never worked with SFS before. The SFS was designed and put into 24x7
production use circa 1996. There are few trails to follow. Presently there
is a daily backup of the system plus weekly DDR's of the volumes. Due to
production I cannot shutdown for much more time than the backup takes. I
query ibmvm
query ibmvm
NOTICE:
This e-mail is intended solely for the use of the individual to whom it is
addressed and may contain information that is privileged, confidential or
otherwise exempt from disclosure. If the reader of this e-mail is not the
intended recipient
You said your weekly backups are done with DDR, you didn't mention what
method you use for your daily backups.
If you only have DDR backups, then there is no easy way to get one (or
any) individual file(s) restored ... you have to restore the DDR for
*all* minidisks that make up the FilePool.
The daily backup is created from the SFS system via backup. Which since it
has no parameters associated with it, I am assuming that everything is
backed up.
Phil
Imler, Steven J steven.im...@ca.com
Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
12/23/2008 08:36 AM
You'd need to restore the DDR backup to a new filepool user (with
exactly the same minidisk configuration, for example userid NEWSFS).
After the restore, link to the restored NEWSFS 191 and
- RENAME oldSFS DMSPARMS fm NEWSFS = =
- change the filepool ID in NEWSFS DMSPARMS to e.g. TEMPSFS
- RENAME
If your daily SFS backups were created by the FILEPOOL BACKUP command
you could use FILEPOOL FILELOAD to restore individual files.
If the daily SFS backup was created by FILEPOOL UNLOAD, you can use
FILEPOOL RELOAD to restore individual files.
From: The IBM z/VM Operating System
Unless you have a product or process that does file level backups (look in the
list of file pool administrators for clues) you are going to be in trouble.
Physical backups of a running SFS server are generally not of much use.
From: The IBM z/VM Operating
Your assumption may be faint.
You issue BACKUP on the SFS server's console (or CP SEND VMSERVx
BACKAUP, what is the same) do you?. If this is the case, you only
have a backup of the SFS control data (that is, who is enrolled, which
GRANTs are given, etc), but **not** of the data residing in these
Your best bet at restoration is to do as Kris suggests. I would not,
under any circumstances, restore directly to the corrupted file pool
from the DDR backup unless it was taken while the file pool was down and
before the corruption occurred. Even then, you would back level all
files and catalog
In looking at the VDISK Storage by User display (ESALPS) I noticed that
SYSTEM was the 10th largest user of VDISK during one interval, but fell
to 0 the next. What causes SYSTEM to show up as a user of VDISK? Perhaps
something in the DEFINE or DETACH processes?
Regards,
Richard Schuh
SYSTEM as displayed by ESALPS components is not system as in SYSTEM VMDBLK. System is
really system totals. Which screen exactly are you looking at? (There isn't a vdisk
storage by user display).
The ESAASPC shows all the address spaces including VDISK, and shows 'SYSTEM'. The ESAVDSK
just
I was looking at the web displays and that is the heading on the screen.
Picture (Device Independent Bitmap)
Regards,
Richard Schuh
-Original Message-
From: The IBM z/VM Operating System
[mailto:ib...@listserv.uark.edu] On Behalf Of Barton Robinson
Sent: Tuesday,
15 matches
Mail list logo
