View previous topic :: View next topic
|
Author |
Message |
sasikumar1984
Active User
Joined: 02 Jul 2007 Posts: 109 Location: Chennai - India
|
|
|
|
I have a PS which is used as Input for a SAS step, but the step is always going down with SPACE issue. Actually this PS is created in the previous step in same job using SAS. But in the next step while using this as input, the job is going down with SPACE problem.
Please find few details of the Dataset
Record Length : 6144
Block Size : 6144
Total num of Records :
Regards,
Sasikumar.K |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
post the jcl and the syslog/msglog |
|
Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004 Posts: 4652 Location: Raleigh, NC, USA
|
|
|
|
I don't understand.
1. Why would a dataset be allocated with the LRECL and BLKSIZE the same?
2. How can an INPUT dataset have a space problem? That's not logical. |
|
Back to top |
|
|
Devzee
Active Member
Joined: 20 Jan 2007 Posts: 684 Location: Hollywood
|
|
|
|
Quote: |
Why would a dataset be allocated with the LRECL and BLKSIZE the same? |
I assume you know this - There is no restrictions. This takes more DASD space and should be realized by the person who is creating with this DCB parameter. |
|
Back to top |
|
|
abhishekmdwivedi
New User
Joined: 22 Aug 2006 Posts: 95 Location: india
|
|
|
|
Shashi ,
Can you please post the SASLOG for the same. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
Quote: |
Everything that has a begining has a end..... |
it depends...
salami/sausages are universally considered as having two ends |
|
Back to top |
|
|
cpuhawg
Active User
Joined: 14 Jun 2006 Posts: 331 Location: Jacksonville, FL
|
|
|
|
SAS datasets are unique to SAS processing. A DCB of FS/6144/6144 with a DSORG of PS is perfectly normal, although FS/27648/27648 is probably a little more efficent. A SAS input dataset may also be an output dataset based on the logic in the SAS program.
You can use the following SAS JCL to list the contents of your SAS dataset:
Code: |
//XSAS EXEC SAS RSYSOUT='*',LSYSOUT='*'
//SYSIN DD *
PROC CONTENTS DATA=PROD1._ALL_ ;
//SAS.PROD1 DD DSN=HLQ.SAS.INPUT.DATASET,DISP=OLD
|
This should provide a list of all the members inside the SAS input dataset.
If any of the members are unneeded, they may be deleted to free up space using:
Code: |
//XSAS EXEC SAS RSYSOUT='*',LSYSOUT='*'
//SYSIN DD *
PROC DELETE DATA=PROD1.ACCT;
//SAS.PROD1 DD DSN=HLQ.SAS.INPUT.DATASET,DISP=OLD
|
If there is nothing to be deleted, you may need to consider allocating additional SAS datasets and referencing them in the SAS program. If some of the steps in the SAS program are writing to the SAS dataset, but are unnecessary to the final output, these may be written to temporary SAS work datasets by changing:
to
Without the PROD. prefix, SAS will assume the file is temporary and will write it to the temporary work DD in the program. You may all allocate your own temporary WORK files such as:
Code: |
//WORKX DD DSN=&&TEMPWK1,UNIT=SYSDA,SPACE=(6144,(&WORK),,,ROUND),
// DCB=(RECFM=FS,LRECL=6144,BLKSIZE=6144,DSORG=PS),
// DISP=(NEW,PASS)
|
SAS could then reference the WORKX file by using:
Also note that you can allocate your original SAS dataset using the maximum amount of SPACE your installation will allow.
Code: |
//SAS.SASLIB DD DSN=HLQ.INPUT.SAS.DATASET,
// UNIT=SYSDA,RETPD=120,DISP=(,CATLG),
// DCB=(RECFM=FS,LRECL=27648,BLKSIZE=27648),
// SPACE=(CYL,(550,50))
|
|
|
Back to top |
|
|
hemu
New User
Joined: 04 Jan 2008 Posts: 3 Location: chennai
|
|
|
|
Hi Sasikumar,
Allocate the PS by giving primary quantity as 1000 then I hope you wont get space problem. |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
hemu wrote: |
Hi Sasikumar,
Allocate the PS by giving primary quantity as 1000 then I hope you wont get space problem. |
1000 what, Kb, Mb, Tracks, Cylinders, Blocks ??? |
|
Back to top |
|
|
hemu
New User
Joined: 04 Jan 2008 Posts: 3 Location: chennai
|
|
|
|
Hi,
Sorry for the confusion . need to allocate 1000 cylinders in primary |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
Quote: |
Allocate the PS by giving primary quantity as 1000 then I hope you wont get space problem. |
Just being picky..
why 1000 ??
do You have some kind of interest in selling auxiliary storage
allocations should be made after having evaluated the needs and the consequences,
not by just plugging in some value hoping not to get in trouble until the next time |
|
Back to top |
|
|
Alan Voss
New User
Joined: 29 Nov 2006 Posts: 32 Location: Jacksonville, FL
|
|
|
|
We're all still pretty much just guessing how to resolve this problem without many facts. It would still be helpful to see the SASLOG and the JCL. And, it seems that the original poster has been surprisingly quiet in this whole interchange of ideas. Maybe "the problem has gone away". |
|
Back to top |
|
|
imthyaz_shaik
New User
Joined: 22 May 2007 Posts: 3 Location: Bangalore
|
|
|
|
simple solution create sas data set with null option.. data _null_;
it won;t give the space pb. only thing is u won't use this dataset again with set para meter |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
imthyaz_shaik wrote: |
simple solution create sas data set with null option.. data _null_;
it won;t give the space pb. only thing is u won't use this dataset again with set para meter |
If the data is reread in SAS format then by doing this a rewrite of following code will be required.
As the OP never told us the true nature of the problem, it could be that the file with space problems is already an external file. |
|
Back to top |
|
|
|