|
View previous topic :: View next topic
|
| Author |
Message |
santuece1
New User
Joined: 20 Jul 2017
Posts: 5
Location: india
|
|
|
|
Hi
I am facing issue with work space library in sas i tried increasing it as work=(cyl,(4000,3500)) it was still showing the error sb37 .could you please help me on this |
|
| Back to top |
|
 |
santuece1
New User
Joined: 20 Jul 2017
Posts: 5
Location: india
|
|
|
|
| can anyone there to help me |
|
| Back to top |
|
|
santuece1
New User
Joined: 20 Jul 2017
Posts: 5
Location: india
|
|
|
|
| can anyone there to help me |
|
| Back to top |
|
|
santuece1
New User
Joined: 20 Jul 2017
Posts: 5
Location: india
|
|
|
|
 can anyone help me on sas workspace issue |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8796
Location: Welsh Wales
|
|
|
|
1) DO NOT tag on to an existing thread over 10 years old
2) DO NOT moan because it isn't answered fast
3) Try multi volume or multi work library |
|
| Back to top |
|
|
santuece1
New User
Joined: 20 Jul 2017
Posts: 5
Location: india
|
|
|
|
sry iam not getting exactly what you are referring to
could you please elaborate it |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8796
Location: Welsh Wales
|
|
|
|
If it is a batch job then use the JCL to make the WORK DD name multi volume
Or define a DD WORK2 and use that in conjunction with WORK - code changes will be required
AND have you spoken with your storage management team to see if they can help - it may be a site related issue. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8700
Location: Dubuque, Iowa, USA
|
|
|
|
This is a VOLUNTEER forum -- as in, questions are answered when people have the time, the interest, and the knowledge to respond. It is not unusual for posts to go without answers for days ... weeks ... months ... years and hence pleading for responses (especially after a short time) actually REDUCES the chance you will get answers as people who would have responded decide your pleading makes it not worth the time to respond.
Unless you have specified DSNTYPE=LARGE, using SPACE=(CYLS,(4000,3500)) is useless. Without DSNTYPE=LARGE, the biggest data set you can allocate is 4,369 cylinders on a single volume. So you're not able to get 3500 cylinders as a secondary.
Read in the MVS JCL Reference manual about the DD statement and how to allocate multi volume data sets. |
|
| Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010
Posts: 3076
Location: NYC,USA
|
|
|
|
| ..DATACLASS ? |
|
| Back to top |
|
|
vasanthz
Global Moderator
Joined: 28 Aug 2007
Posts: 1744
Location: Tirupur, India
|
|
|
|
Hi, Could you please explain, how would DATACLAS help?
These are the two options I could understand,
DSNTYPE=LARGE
Allocating work dataset in multiple volumes
Regards,
Vasanth.S |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8700
Location: Dubuque, Iowa, USA
|
|
|
|
| SAS uses the WORK DD name to hold temporary (one-level) SAS data sets. WORK is not related to the SORTWKnn DD statements. One thing I've done in the past is to allocate a large SAS data set and use DATA DDNAME.SASNAME instead of DATA SASNAME -- the latter uses WORK.SASNAME by default and if you're having trouble with WORK space using the two-level name can help alleviate the issue. |
|
| Back to top |
|
|
vasanthz
Global Moderator
Joined: 28 Aug 2007
Posts: 1744
Location: Tirupur, India
|
|
|
|
| Quote: |
| WORK is not related to the SORTWKnn DD statements. |
I totally overlooked. Thanks for the correction.
I corrected my post, so it does not mislead people. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8796
Location: Welsh Wales
|
|
|
|
After a little investigation and play, mainly because I experienced a little grief with space needed to process one beast of a dataset ..............
This is on the server, and of course names have been changed to protect the innocent  The following gave me exactly what I wanted by replacing the pre allocated - and not so big and within a shared area with many users - WORK libname with Workx.
| Code: |
Libname Work1 "D:\SAS Work Extended D";
Libname Work2 "E:\SAS Work Extended E";
Libname Workx Clear;
Libname Workx (Work1 , Work2);
Options User = Workx;
All of my super SAS code in here
/***
Revert back to the real WORK library now
***/
Options User = Work;
Libname Work1 Clear;
Libname Work2 Clear;
|
As I don't have mainframe access any more, it's 2014 since I last had my very own TSO session  so maybe someone with a spare few minutes may test this in a MF batch job
Allocate the two libnames via JCL and see what happens, Would like to know as it certainly works on the server and my laptop. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8700
Location: Dubuque, Iowa, USA
|
|
|
|
| Code: |
11 The SAS System 08:14 Tuesday, September 25, 2018
NOTE: Copyright (c) 2002-2012 by SAS Institute Inc., Cary, NC, USA.
NOTE: SAS (r) Proprietary Software 9.4 (TS1M2)
Licensed to <removed>, Site <removed>.
NOTE: This session is executing on the z/OS V02R01M00 platform.
NOTE: Running on IBM Model 2818 Serial Number <removed>.
NOTE: Additional host information:
IBM 2818-H02, SYSP, FMID HBB7790, CPU: 2, GP: 2, zAAP: 0, zIIP: 0
Welcome to SAS
This message displays in the SAS log when the NEWS option is specified.
You can replace it with your own message by editing the NEWS file.
NOTE: The SASUSER library was not specified. SASUSER library will now be the same as the WORK library.
NOTE: All data sets and catalogs in the SASUSER library will be deleted at the end of the session. Use the NOWORKTERM option to
prevent their deletion.
NOTE: SAS system options specified are:
SORT=4
NOTE: 64M bytes were available above the line at initialization.
NOTE: 11240K bytes were available below the line at initialization.
NOTE: 65024K bytes were available above the line after adjustment for MEMLEAVE=512K.
NOTE: The initialization phase used 0.18 CPU seconds and 20996K.
NOTE: The address space has used a maximum of 896K below the line and 22776K above the line.
1 Libname Work1 "RLS.WORK1.SAS";
NOTE: Libref WORK1 was successfully assigned as follows:
Engine: V9
Physical Name: RLS.WORK1.SAS
2 Libname Work2 "RLS.WORK2.SAS";
NOTE: Libref WORK2 was successfully assigned as follows:
Engine: V9
Physical Name: RLS.WORK2.SAS
3
4 Libname Workx Clear;
WARNING: Libref WORKX is not assigned.
5 Libname Workx (Work1 , Work2);
NOTE: Libref WORKX was successfully assigned as follows:
Levels: 2
Engine(1): V9
Physical Name(1): RLS.WORK1.SAS
Engine(2): V9
Physical Name(2): RLS.WORK2.SAS
6
12 The SAS System 08:14 Tuesday, September 25, 2018
7 Options User = Workx;
8
9 DATA _NULL_ ;
10 DO I=1 TO 1000000 ;
11 X = 3;
12 END;
13
14 Options User = Work;
15
16 Libname Work1 Clear;
NOTE: Libref WORK1 has been deassigned.
17 Libname Work2 Clear;
NOTE: Libref WORK2 has been deassigned.
NOTE: The DATA statement used 0.11 CPU seconds and 24216K.
NOTE: The address space has used a maximum of 896K below the line and 26052K above the line.
NOTE: The SAS session used 0.39 CPU seconds and 24216K.
NOTE: The address space has used a maximum of 896K below the line and 26052K above the line.
NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414 |
One warning but nothing serious.
WORK1 and WORK2 were both defined as 4000 cylinder data sets. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8796
Location: Welsh Wales
|
|
|
|
Thanks for that Robert .............  |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 592
Location: London
|
|
|
|
Pedant mode on:
Large Format QSAM datasets can be SMS or NONSMS managed and allow up to 16 extents per volume with no size limit per volume, and can extend to the maximum 59 volumes, therefore 944 extents. So total size depends on the volume capacities you're allocating on.
They are recommended for SORTWK datasets, and can be used to replace standard QSAM, although there are some program restrictions (i.e.BLOCKTOKENSIZE=LARGE parameter is required on the DCBE macro in some cases) |
|
| Back to top |
|
|
|
|
