Follow-up and results:
Expanding spool and page within an already CP-Owned disk does not seem to
cause any issues. Everything survived the change. DCSSBKUP didn't work well
for me, but it could have been the size of the virtual machine I ran it in.
It also does not back up any of the other SDF
On Wednesday, 09/19/2007 at 05:32 EDT, RPN01 [EMAIL PROTECTED] wrote:
With more and more tapeless systems, something other than SPXTAPE is
required. As more and more products are delivered electronically, and
there
is less need for tape other than backup, you'll see more systems without
On: Thu, Sep 20, 2007 at 01:07:06PM -0500,RPN01 Wrote:
} Expanding spool and page within an already CP-Owned disk does not seem to
} cause any issues. Everything survived the change. DCSSBKUP didn't work well
} for me, but it could have been the size of the virtual machine I ran it in.
The vm
I think I asked this once, but didn¹t get an answer
The 5.3 install allowed me to format page and spool as 3390 mod 9 devices
(10017 cylinders). But in fact, I was using 3390 mod 27 disks (32760
cylinders). If I go into the devices with ICKDSF and change the remaining
cylinders to PAGE and
RPN01 wrote:
I think I asked this once, but didnt get an answer
The 5.3 install allowed me to format page and spool as 3390 mod 9
devices (10017 cylinders). But in fact, I was using 3390 mod 27 disks
(32760 cylinders). If I go into the devices with ICKDSF and change the
remaining
True... But I was hoping to get a Yes, this will work. or No this will
fail. just so I know where I'm going
On 9/19/07 1:36 PM, Kim Goldenberg [EMAIL PROTECTED] wrote:
RPN01 wrote:
I think I asked this once, but didnt get an answer
The 5.3 install allowed me to format page and
The thing I would be concerned about, is changing the order of the
CPOWNED volumes.
In this case, you are not.
But, is there some requirement of keeping the spool volumes in the same
order?
In other words, if PACK03 will now contain spool files, what would
happen if the cpowned list shows:
In this case, we're not adding a spool volume; just re-allocating space on
an existing one. In practice in the other case, I've always added spool
volumes to the end of the list. It may be ok in a Reserved slot already in
the list. And, never under any circumstances remove a volume from the
Operating System IBMVM@LISTSERV.UARK.EDU
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: Extending the 5.3 install page and spool
True... But I was hoping to get a Yes, this will work. or No this will
fail. just so I know where I'm going
On 9/19/07 1:36 PM, Kim Goldenberg [EMAIL PROTECTED
I can't really address Robert Nix's question. I'd be leery of trying it
without doing a SPXTAPE dump, however.
The question that Tom raised however referring to changing the order in
the CP owned list of a spool volume cannot be done without dumping and
reloading the spool. This is because
[mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch
Sent: Wednesday, September 19, 2007 4:59 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Extending the 5.3 install page and spool
The question I was trying to bring up, as modified by your comments:
Spool files are addressed as volume_number, cyl
The question I was trying to bring up, as modified by your comments:
Spool files are addressed as volume_number, cyl, track, record.
Is the volume_number always the cpowned number, or is it based on
type, in this case spool type?
Since we haven't come up with a definitive answer, and I guess
With more and more tapeless systems, something other than SPXTAPE is
required. As more and more products are delivered electronically, and there
is less need for tape other than backup, you'll see more systems without
access to a tape drive. Only one of my two z/VM systems has access to tape
at
I have a SVM that uses DCSSBKUP to backup to disk files all of the
DCSSes. What I cannot backup this way are the CMS and GCS NSSes. CMS can
be resaved by IPLing 190 with the savesys option after doing a defsys
command. GCS needs to have the nucleus card deck punched to a virtual
rdr and then
14 matches
Mail list logo
