Page 1 of 1

SB37 Error

PostPosted: Fri Mar 05, 2010 7:12 pm
by bsmadevan
Hi I am getting SB37 error,
I tried to change the space paramaeter in the JCL but still getting the error, Can any one help me out on this.
I gave the code as follows:

//IPFILE DD DSN=TEST.ipfile1,DISP=SHR
//OPFILE6 DD DSN=&&TESTMAST,
// DISP=(NEW,PASS,DELETE),
// UNIT=DISK,
// DCB=(RECFM=FB,LRECL=782,BLKSIZE=0),
// SPACE=(7820,(782,391),RLSE)
//* SPACE=(0,(17640,4410),RLSE)
//* SPACE=(CYL,(25,15),RLSE)

Please advise.

Thanks,
Madev

Re: SB37 Error

PostPosted: Fri Mar 05, 2010 7:18 pm
by ctrevino
Try this // SPACE=(7820,(782,391,2),RLSE)

Re: SB37 Error

PostPosted: Fri Mar 05, 2010 7:22 pm
by bsmadevan
Hi,

after changing the space to 'SPACE=(7820,(782,391,2),RLSE)' I am getting error as follows:

SYSIN :
SORT FIELDS=(1,4,CH,A) COMPANY CODE 0000010
OUTREC FIELDS=(1,782,10X) 0000020
WER276B SYSDIAG= 28253, 291768, 291768, 945087
WER164B 24,448K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED,
WER164B 0 BYTES RESERVE REQUESTED, 2,028K BYTES USED
WER146B 20K BYTES OF EMERGENCY SPACE ALLOCATED
WER108I SORTIN : RECFM=FB ; LRECL= 782; BLKSIZE= 27370
WER180A SORTIN MEMBER NOT SPECIFIED
WER449I SYNCSORT GLOBAL DSM SUBSYSTEM ACTIVE

Please advise.
Thanks,
Bala.M

Re: SB37 Error

PostPosted: Fri Mar 05, 2010 8:06 pm
by MrSpock
Other than the obvious warning message from Syncsort:

WER180A SORTIN MEMBER NOT SPECIFIED

what problem are you experiencing?

Re: SB37 Error

PostPosted: Sat Mar 06, 2010 12:52 am
by dick scherrer
Hello and welcome to the forum,

When asking about a problem, it is best to post the complete JCL for the problem step (sometimes even more is needed) rather than only what you believe we need to see.

Re: SB37 Error

PostPosted: Sat Mar 06, 2010 6:36 am
by Robert Sample
How many records are you putting into the file? That usually determines how much space to give the file. Unless you know the number of records, you cannot correctly specify the file size.

Why are you specifying SPACE=(7820, ... yet saying DCB=BLKSIZE=0? You do realize, I hope, that these parameters directly contradict each other? And I do hope you've read the manual to verify which one will take precedence.

Finally, Christy T's suggestion is worse than useless -- it is changing a physical sequential (PS) file to a partitioned data set (PDS) without doing a single thing about the original lack of space.

Re: SB37 Error

PostPosted: Tue Mar 09, 2010 12:55 am
by ctrevino
Thanks, Robert. I was only trying to help. It's nice to know that my help is useless and therefore not needed here.

Re: SB37 Error

PostPosted: Tue Mar 09, 2010 1:35 am
by dick scherrer
Hi Christy,

It's nice to know that my help is useless and therefore not needed here.
As often happens - you have overreacted. . .

There is considerable difference between told that an off-the-wall (untested?) suggestion was "tossed" and being told "my help is useless". . . We certainly welcome help. We also react when a "solution" appears to be untested (i.e. why create a temporary pds?).

How often does creating a pds resolve a space issue? How would the PASSed pds be used in the next step(s)?

Be well,

d

Re: SB37 Error

PostPosted: Tue Mar 09, 2010 4:09 am
by Robert Sample
Christy, what did you think putting the ,2 on the space parameter would do? While your suggestion actually made the situation worse, I did not mean to imply your attempted help was not appreciated -- but your solution was flat out wrong. If you don't test your solution before posting, or reference the manual extensively, it is quite easy to get things wrong when posting. Since these posts can be here for literally years, posting wrong information is not good.

What your suggestion actually does is take the exact same file space parameter that is already known not to work and use it again, while changing the sequential file to a PDS. Hence the SORTIN MEMBER NOT SPECIFIED message -- you must provide the member name for the PDS. So not only is the exact same space issue going to recur, it is now masked by a spurious member name message generated because the file has been converted to a PDS. This is what I meant in my post -- your solution did not fix the problem, and added a new error message not previously seen.