We just migrated from 4.4 to 5.2 RSU 0601 and we saw a similar condition. The spool filled up prematurely while migrating 50,000 spool files to 5.2 using SPXTAPE. The spool area completely filled, and when we purged out all the visible spool files, not SDFs, utilization still showed 17%. When we reIPLed, utilization dropped to 2%. One 3390 mod-9 should have given us enough space when compared to the 4.4 system which used 5 mod-2s (2226 cyl. each). We had to scramble and set up 2 more mod-9s to finish the cutover. Since we had only a 2 hour window, needless to say things got a little challenging!
We didn't have time to IPL again after the SPXTAPE LOAD. Should we anticipate a big reduction in spool usage stats after the next outage? Ray Mrohs U.S. Department of Justice 202-307-6896 -----Original Message----- From: VM/ESA and z/VM Discussions [mailto:[log in to unmask]] On Behalf Of Hans Rempel Sent: Monday, March 06, 2006 5:26 AM To: [log in to unmask] Subject: Re: Problem moving spool files from z/vm 3.1 to z/vm 5.2 using spxtape Thanks Mike. I read you e-mail earlier but didn't have a chance to reply. You're correct. I used a spxtape to backup of nss files from 5.2 system and found that it used much more space than necessary about 13% when I loaded them the 5.2 syste. I than IPL'ld and it dropped to 3%. So its not just between releases. SPXTAPE 5.2 is bad. Your comments made me comfortable to proceed with the spxtape load. I just added an additional 3 spool volumes to the 4 I had. Hans
