|
midrange.com
The SAV/RST commands started supporting /QNTC with V4R5. From V4R2 to V4R4
you could not SAV/RST /QNTC.
Nothing about /QNTC is dependent on an IPCS/INS/IXS/FSIOP. It is just
built into the base OS.
Hope this helps.
Mark Phippard
Robin Coles
<robin@ringbase.com To:
"'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
> cc:
Sent by: Subject: RE: Backing up the
IFS - what actually gets backed up?
owner-midrange-l@mi
drange.com
06/28/01 12:42 PM
Please respond to
MIDRANGE-L
Rob,
I don't think you can back up directly from QNTC (maybe you can if you have
an IPCS or whatever it's called these days). I can happily copy, delete
etc. files on QNTC, but SAV just says "Can't". I don't have an IPCS
installed. I can copy from QNTC to a directory on the IFS and then save
from there with no problems. This is on V5R1.
Cheers
Robin
-----Original Message-----
From: rob@dekko.com [mailto:rob@dekko.com]
Sent: 28 June 2001 15:34
To: MIDRANGE-L@midrange.com
Subject: Re: Backing up the IFS - what actually gets backed up?
Bruce, one of us, is totally misled.
Item 1) QNTC.
My belief is that QNTC is NOT the storage for integrated netfinity servers
on the same 400. My belief is that QNTC is used for the 400 to have access
to PC's within the network. For example, if I have a PC named ROB in a
different building then I can do a CPY from /QNTC/ROB/... as long as the
400
user/pwd matches a user/pwd that has access to the share on that PC. Now,
my
userid/pwd has administrator access to every PC in our network. That's over
800. If it didn't automatically exclude QNTC then I would be backing up
every PC in my organization when I saved the IFS. I'd rather continue to
use ADSTAR to do this, thank you.
Item 2) QFileSvr.400
If I do the following
MD '/QFileSvr.400/rmt400'
then
WRKLNK '/QFileSvr.400/rmt400/*'
Then I can see everything on the remote 400. Therefore I would hope that
this gets automatically excluded, or in effect I am backing up two 400's
from one.
Rob Berendt
==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.
"R. Bruce Hoffman,
Jr." To:
<MIDRANGE-L@midrange.com>
<rbruceh@attglobal. cc:
net> Subject: Re: Backing up
the IFS - what actually gets backed up?
Sent by:
owner-midrange-l@mi
drange.com
06/28/2001 07:25 AM
Please respond to
MIDRANGE-L
-----Original Message-----
From: Peter Dow <pcdow@yahoo.com>
To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
Date: Wednesday, June 27, 2001 6:52 PM
Subject: Backing up the IFS - what actually gets backed up?
>My question is, what about other servers that are accessible via the
>IFS? Does the command
>
>SAV DEV('/QSYS.LIB/media-device-name.DEVD') |
> | | | | OBJ(('/*') ('/QSYS.LIB' *OMIT) +
>|
> | | | | ('/QDLS' *OMIT)(1) +
>|
> | | | | ('/QIBM/ProdData' *OMIT) +
>|
> | | | | ('/QOpenSys/QIBM/ProdData' *OMIT))
>+|
> | | | | UPDHST(*YES)
>
>which is run by option 23 of the SAVE menu, backup any attached NT
servers?
>What about servers connected via QFileSvr.400? The Backup/Recovery
>Guide
is
>less than forthcoming about this.
>
Yes, so long as the server is varied off during the save. The space
(physically) in QNTC is not really what you are after. The QFPNWSSTG is
the
space your after. In either event, the omits above a specifically omit QSYS
(saved by normal library saves) QDLS (saved by SAVDLO) and IBM product
information in the directories (don't store anything there thinking it's
PRODUCTION instead of PRODUCT <vbg>)
>I would guess that they're automagically omitted instead of having to
>be explicitly omitted as /QDLS is in the above command, but I don't
>know and
I
>don't see any documentation that says so.
>
No, they are automatically included.
>When I tried to backup an object from a QNTC NT server, I got an error
>stating that QSECOFR was not authorized to the NT server. Presumably if
she
>had been, it would've worked. How about with QFileSvr.400?
Again, why QNTC? It's just a lump, a heap. And what about QFileSvr.400?
Without OS/2, I don't think (pretty sure) anything goes in here. That was
the space for OS/2. But the data actually showed on QFPNWSSTG, like the NT.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com. To
| subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. To
| unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com. To
| subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. To
| unsubscribe from this list send email to
| MIDRANGE-L-UNSUB@midrange.com. Questions should be directed to the
| list owner/operator: david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
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.
