| Date: | Thu, 17 Jul 1997 11:10:00 -0400 |
| Reply-To: | "Russell, Heather" <hbr9@CDC.GOV> |
| Sender: | "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU> |
| From: | "Russell, Heather" <hbr9@CDC.GOV> |
| Subject: | Re: MVS SAS Fatal Volume Switching error |
| Content-Type: | text/plain |
|---|
In addition, I would suggest typing =3.1 in ISPF and use the compress
option to free up space.
This has worked for me whenever I have encountered this message.
HTH,
Heather Russell
Data Systems Analyst
OAO
----------
From: Roland
To: SAS-L@UGA.CC.UGA.EDU
Subject: Re: MVS SAS Fatal Volume Switching error
Date: Thursday, July 17, 1997 7:05AM
The B37 Abend handler is doing this. It means you have run out of space
(probably a work file) in trying to extend it. It is moving the whole
file over to a different volume.
The best thing is to allocate enough space in the first place without it
being excessive. Then you shouldn't get this problem. Maybe the work
packs are clogged up with undeleted rubbish. Do other jobs get this
problem? It may require increasing the size of the DASD pool, changing
file sizes, tidying up the packs or scheduling the jobs better.
Roland
REMOORE wrote:
>
> First time in the newsgroup and I've got a problem. Running 6.08 on
MVS, we
> get a U0318 error "Attempting to Volume Switch" during execution of
various
> nightly update jobs. Is this an absolute intolerable situation for
SAS, or
> is there some remedy we can add to the JCL/working storage allocation?
|