I can't help much, but may be able to 'reinforce' your experience.
I was helping a customer install one of our systems and migrate their 4.4
system to it and change to 5.2. When we loaded the SPXTAPE spool files
they seemed to occupy 2 to 3 times as much space as they had on the 4.4
system. We had to add a new spool volume to be able to load them all.
But, when we re-IPL'ed, the 'missing space' reappeared and the correct
amount of spool space/cylinders was allocated.
It looks like there may be some kind of SPXTAPE problem on 5.2
Mike
C. M. (Mike) Hammock
Sr. Technical Support
zFrame & IBM zSeries Solutions
(404) 643-3258
[EMAIL PROTECTED]
Janice Calder
<[EMAIL PROTECTED]
mber.ca> To
Sent by: VM/ESA [email protected]
and z/VM cc
Discussions
<[EMAIL PROTECTED] Subject
.UARK.EDU> Problem moving spool files from
z/vm 3.1 to z/vm 5.2 using spxtape
03/05/2006 02:23
PM
Please respond to
VM/ESA and z/VM
Discussions
<[EMAIL PROTECTED]
.UARK.EDU>
When loading spool files using spxtape we appear to be using
up a lot of spool
pages that are not identified or associated with regular spool entries but
are
flagged as in use. VMspool identifies them as "Other" in the sysuse screen.
I tried loading by userid only, issuing Q ALLOC SPOOL command frequently
and
the number of spool pages loaded was about 1/3 the number being used up.
The spxtape dump on 3.1 dumped approx 11,000 files using about 800,000
pages
which looks fine. The loading appears to be the problem.
Problem has been report to IBM but this problem does not appear in their
database. More help from them tomorrow but I like to get a work around
today.
Any comments or suggestions would be appreciated.
Thanks
Hans Rempel / Janice Calder
