JOINKEY SPACE EXCEEDED error



Support for NetApp SyncSort for z/OS, Visual SyncSort, SYNCINIT, SYNCLIST and SYNCTOOL

JOINKEY SPACE EXCEEDED error

Postby Jaggi » Thu Jan 17, 2008 6:50 am

Hi,

I am using SYNCSORT with JOINKEYS to compare 2 files.
I am Getting error - > WER488A JOIN CAPACITY EXCEEDED
There are 2 files to be compared with about 2 million records each. LRECL is 3665.
Can somebody give a pointer as to how to resolve this problem?

Thanks in advance.
Jaggi.
Jaggi
 
Posts: 3
Joined: Thu Jan 17, 2008 6:39 am
Has thanked: 0 time
Been thanked: 0 time

Re: JOINKEY SPACE EXCEEDED error

 

Re: JOINKEY SPACE EXCEEDED error

Postby dick scherrer » Fri Jan 18, 2008 1:05 am

Hello Jaggi and welcome to the forums,

How many of the records have the "same" key?

If you post your jcl and control statements, that may help us help you.

Do you have the Syncsort documentation? If not, it is availabel for free from Syncsort support (for licenesed users).
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times

Re: JOINKEY SPACE EXCEEDED error

Postby Jaggi » Fri Jan 18, 2008 4:27 am

Thanks dick scherrer!

I do not have SYNCSORT manual with me although searching for it for a long time.
Number of records in both the files are exactly 1 million each. JOINKEY is on 1st 10 bytes. Please find the complete sort card and
spool messages below.

I would appreciate any help in solving this problem. Thanks in advance.

SYNCSORT FOR Z/OS  1.2.3.0R    U.S. PATENTS: 4210961, 5117495   (C) 2005 SYNCSO

                                             AETNA INC.   z/OS   1.8.0       

PRODUCT LICENSED FOR CPU SERIAL NUMBER 36FAB, MODEL 2094 715              LICEN

PARMTBLE : BMSG,CORE=MAX                                                     

$ORTPARM : DYNALLOC=(SYSDA,200),VSCORE=6M,VSCORET=38M                         

SYSIN :                                                                       

**********************************************************************  0007511

*****      HERE FIRST 3 FILES FOR THE DESIGN ARE CREATED     *********  0007526

**********************************************************************  0007531

  JOINKEYS FILES=F1,FIELDS=(1,10,A)                                     0007600

  JOINKEYS FILES=F2,FIELDS=(1,10,A)                                     0008000

  REFORMAT FIELDS=(F1:1,3664,F2:1,3634),FILL=X'FF'                      0009006

  JOIN UNPAIRED                                                         0010000

  SORT FIELDS=COPY                                                      0011000

  OUTFIL FILES=01,INCLUDE=(1,1,BI,NE,X'FF',                             0014335

               AND,3655,10,CH,EQ,C'0001-01-01',AND,3665,1,BI,EQ,X'FF'), 0014348

                 OUTREC=(1,3634,C'U')                                   0014376

  OUTFIL FILES=02,INCLUDE=(3665,1,BI,NE,X'FF',                          0014396

                AND,1,1,BI,EQ,X'FF'),                                   0014406

                  OUTREC=(1:3665,3634,C'A')                             0014416

  OUTFIL FILES=03,INCLUDE=(1,1,BI,NE,X'FF',                             0014426

                  AND,3665,1,BI,NE,X'FF',                               0014436

                  AND,3655,10,CH,NE,C'0001-01-01'),                     0014446

                  OUTREC=(1:3665,3634,C'A')                             0014506

**********************************************************************  0015311

***** HERE TWO THINGS ARE DONE                                ********  0015326

***** FINDS ALL ACTIVE NPI'S IN EXTRACT FILE WHICH ALSO EXIST ********  0015331

***** IN GOVFILE                                              ********  0015341

***** 1. ALL SUCH RECORDS IN EXTRACT FILE ARE COPIED IN       ********  0015351

*****    R151PB.P51IA101.NPI.UPDATE2.INTERMED FILE            ********  0015365

***** 2. ALL SUCH RECORDS IN GOVFILE ARE COPIED IN            ********  0015371

*****    R151PB.P51IA101.NPI.ADD3.INTERMED FILE               ********  0015385

**********************************************************************  0015391

  OUTFIL FILES=04,INCLUDE=(1,1,BI,NE,X'FF',AND,3665,1,BI,NE,X'FF',      0015916

                  AND,3655,10,CH,EQ,C'0001-01-01'),                     0015926

                  OUTREC=(1,3634,C'B')                                  0015966

  OUTFIL FILES=05,INCLUDE=(1,1,BI,NE,X'FF',AND,3665,1,BI,NE,X'FF',      0015986

                  AND,3655,10,CH,EQ,C'0001-01-01'),                     0015996

                  OUTREC=(1:3665,3634,C'A')                             0016006a

WER161B  ALTERNATE PARM USED                                                 

WER276B  SYSDIAG= 309700, 3624568, 3624568, 5667039                           

WER164B  92,832K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED,           

WER164B     0 BYTES RESERVE REQUESTED, 1,373,384 BYTES USED                   

WER146B  20K BYTES OF EMERGENCY SPACE ALLOCATED                               

WER481I  JOINKEYS REFORMAT RECORD LENGTH= 7298, TYPE = F                     

WER110I  SORTOF01 : RECFM=FB   ; LRECL=  3635; BLKSIZE=  7270                 

WER110I  SORTOF02 : RECFM=FB   ; LRECL=  3635; BLKSIZE=  7270                 

WER110I  SORTOF03 : RECFM=FB   ; LRECL=  3635; BLKSIZE=  7270                 

WER110I  SORTOF04 : RECFM=FB   ; LRECL=  3635; BLKSIZE=  7270                 

WER110I  SORTOF05 : RECFM=FB   ; LRECL=  3635; BLKSIZE=  7270                 

WER488A  JOIN CAPACITY EXCEEDED                                               

WER211B  SYNCSMF  CALLED BY SYNCSORT; RC=0000                                 

WER449I  SYNCSORT GLOBAL DSM SUBSYSTEM ACTIVE                                 

WER482I  JNF1 STATISTICS                                                     

WER483B  2,604K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED,           

WER483B     0 BYTES RESERVE REQUESTED, 1,580K BYTES USED                     

WER108I  SORTJNF1 : RECFM=FB   ; LRECL=  3664; BLKSIZE=  7328                 

WER483B  1,264K BYTES OF VIRTUAL STORAGE AVAILABLE ABOVE THE 16MEG LINE,     

WER483B     0 BYTES RESERVE REQUESTED, 1,264K BYTES USED                     

WER483B  G=15                                                                 

WER416B  SORTJNF1 : EXCP'S=1,UNIT=3390,DEV=8174,CHP=(87A7ADB7C1D7F4FF,3),VOL=BI

WER416B  TOTAL OF 1 EXCP'S ISSUED FOR SORTING                                 

WER487I  FILESIZE 0 BYTES                                                     

WER482I  JNF2 STATISTICS                                                     

WER483B  89,232K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED,           

WER483B     0 BYTES RESERVE REQUESTED, 88,148K BYTES USED                     

WER108I  SORTJNF2 : RECFM=FB   ; LRECL=  3634; BLKSIZE= 18170                 

WER483B  87,892K BYTES OF VIRTUAL STORAGE AVAILABLE ABOVE THE 16MEG LINE,     

WER483B     0 BYTES RESERVE REQUESTED, 87,832K BYTES USED                     

WER483B  G=5047,B=15,BIAS=00                                                 

WER483B  72,000 PREALLOCATED SORTWORK TRACKS, 0 DYNAMICALLY ALLOCATED,       

WER483B     0 ACQUIRED IN SECONDARY EXTENTS, 0 RELEASED, TOTAL OF 66,766 TRACKS
Jaggi
 
Posts: 3
Joined: Thu Jan 17, 2008 6:39 am
Has thanked: 0 time
Been thanked: 0 time

Re: JOINKEY SPACE EXCEEDED error

Postby dick scherrer » Fri Jan 18, 2008 10:55 pm

Hello,

As i asked before, how many records might have the same "key value"?

You might try using REGION=0M.

As i may have mentioned n the other forum, the documentation is available for free from Syncsort support.
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times

Re: JOINKEY SPACE EXCEEDED error

Postby Jaggi » Wed Oct 26, 2011 12:34 am

Number of records in both the files are exactly 1 million each. JOINKEY is on 1st 10 bytes. Please find the complete sort card and
spool messages below.

I would appreciate any help in solving this problem.

PARMTBLE : BMSG,CORE=MAX

$ORTPARM : DYNALLOC=(SYSDA,200),VSCORE=6M,VSCORET=38M

SYSIN :

********************************************************************** 0007511

***** HERE FIRST 3 FILES FOR THE DESIGN ARE CREATED ********* 0007526

********************************************************************** 0007531

JOINKEYS FILES=F1,FIELDS=(1,10,A) 0007600

JOINKEYS FILES=F2,FIELDS=(1,10,A) 0008000

REFORMAT FIELDS=(F1:1,3664,F2:1,3634),FILL=X'FF' 0009006

JOIN UNPAIRED 0010000

SORT FIELDS=COPY 0011000

OUTFIL FILES=01,INCLUDE=(1,1,BI,NE,X'FF', 0014335

AND,3655,10,CH,EQ,C'0001-01-01',AND,3665,1,BI,EQ,X'FF'), 0014348

OUTREC=(1,3634,C'U') 0014376

OUTFIL FILES=02,INCLUDE=(3665,1,BI,NE,X'FF', 0014396

AND,1,1,BI,EQ,X'FF'), 0014406

OUTREC=(1:3665,3634,C'A') 0014416

OUTFIL FILES=03,INCLUDE=(1,1,BI,NE,X'FF', 0014426

AND,3665,1,BI,NE,X'FF', 0014436

AND,3655,10,CH,NE,C'0001-01-01'), 0014446

OUTREC=(1:3665,3634,C'A') 0014506

********************************************************************** 0015311

***** HERE TWO THINGS ARE DONE ******** 0015326

***** FINDS ALL ACTIVE NPI'S IN EXTRACT FILE WHICH ALSO EXIST ******** 0015331

***** IN GOVFILE ******** 0015341

***** 1. ALL SUCH RECORDS IN EXTRACT FILE ARE COPIED IN ******** 0015351

***** R151PB.P51IA101.NPI.UPDATE2.INTERMED FILE ******** 0015365

***** 2. ALL SUCH RECORDS IN GOVFILE ARE COPIED IN ******** 0015371

***** R151PB.P51IA101.NPI.ADD3.INTERMED FILE ******** 0015385

********************************************************************** 0015391

OUTFIL FILES=04,INCLUDE=(1,1,BI,NE,X'FF',AND,3665,1,BI,NE,X'FF', 0015916

AND,3655,10,CH,EQ,C'0001-01-01'), 0015926

OUTREC=(1,3634,C'B') 0015966

OUTFIL FILES=05,INCLUDE=(1,1,BI,NE,X'FF',AND,3665,1,BI,NE,X'FF', 0015986

AND,3655,10,CH,EQ,C'0001-01-01'), 0015996

OUTREC=(1:3665,3634,C'A') 0016006a

WER161B ALTERNATE PARM USED

WER276B SYSDIAG= 309700, 3624568, 3624568, 5667039

WER164B 92,832K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED,

WER164B 0 BYTES RESERVE REQUESTED, 1,373,384 BYTES USED

WER146B 20K BYTES OF EMERGENCY SPACE ALLOCATED

WER481I JOINKEYS REFORMAT RECORD LENGTH= 7298, TYPE = F

WER110I SORTOF01 : RECFM=FB ; LRECL= 3635; BLKSIZE= 7270

WER110I SORTOF02 : RECFM=FB ; LRECL= 3635; BLKSIZE= 7270

WER110I SORTOF03 : RECFM=FB ; LRECL= 3635; BLKSIZE= 7270

WER110I SORTOF04 : RECFM=FB ; LRECL= 3635; BLKSIZE= 7270

WER110I SORTOF05 : RECFM=FB ; LRECL= 3635; BLKSIZE= 7270

WER488A JOIN CAPACITY EXCEEDED

WER211B SYNCSMF CALLED BY SYNCSORT; RC=0000

WER449I SYNCSORT GLOBAL DSM SUBSYSTEM ACTIVE

WER482I JNF1 STATISTICS

WER483B 2,604K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED,

WER483B 0 BYTES RESERVE REQUESTED, 1,580K BYTES USED

WER108I SORTJNF1 : RECFM=FB ; LRECL= 3664; BLKSIZE= 7328

WER483B 1,264K BYTES OF VIRTUAL STORAGE AVAILABLE ABOVE THE 16MEG LINE,

WER483B 0 BYTES RESERVE REQUESTED, 1,264K BYTES USED

WER483B G=15

WER416B SORTJNF1 : EXCP'S=1,UNIT=3390,DEV=8174,CHP=(87A7ADB7C1D7F4FF,3),VOL=BI

WER416B TOTAL OF 1 EXCP'S ISSUED FOR SORTING

WER487I FILESIZE 0 BYTES

WER482I JNF2 STATISTICS

WER483B 89,232K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED,

WER483B 0 BYTES RESERVE REQUESTED, 88,148K BYTES USED

WER108I SORTJNF2 : RECFM=FB ; LRECL= 3634; BLKSIZE= 18170

WER483B 87,892K BYTES OF VIRTUAL STORAGE AVAILABLE ABOVE THE 16MEG LINE,

WER483B 0 BYTES RESERVE REQUESTED, 87,832K BYTES USED

WER483B G=5047,B=15,BIAS=00

WER483B 72,000 PREALLOCATED SORTWORK TRACKS, 0 DYNAMICALLY ALLOCATED,

WER483B 0 ACQUIRED IN SECONDARY EXTENTS, 0 RELEASED, TOTAL OF 66,766 TRACKS
Jaggi
 
Posts: 3
Joined: Thu Jan 17, 2008 6:39 am
Has thanked: 0 time
Been thanked: 0 time

Re: JOINKEY SPACE EXCEEDED error

Postby dick scherrer » Wed Oct 26, 2011 1:28 am

Hello,

You need to re-post this using the tags properly and using the Preview function to see how your post will appear to the forum. When the post is as you want, then Submit.

Did you look at the WER488A message in the documentation? Do you now have the documentation? It has been nearly 3 years so there is no reason for not having the documentation. If not, you can still get it free from Syncsort Support if your organization is licensed to use the product. Also, you are running an "old" release of Syncsort. . .

Are the files basically a one-for-one match or are there many records with the same key?
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times

Re: JOINKEY SPACE EXCEEDED error

Postby Ed Goodman » Fri Oct 28, 2011 7:38 pm

Seriously???? Has it really been three years, or is this something that got the date messed up?
Ed Goodman
 
Posts: 342
Joined: Thu Feb 24, 2011 12:05 am
Has thanked: 3 times
Been thanked: 17 times

Re: JOINKEY SPACE EXCEEDED error

Postby BillyBoyo » Fri Oct 28, 2011 7:56 pm

He just found an old "To Do" list down the back of his drawer...

Good spot Ed. Curious.
BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

Re: JOINKEY SPACE EXCEEDED error

Postby dick scherrer » Fri Oct 28, 2011 8:56 pm

Hello,

Yup, the topic is from Jan, 2008. . .

We get lots of re-activated topics :)

I don't believe this one fell into a "black hole".

d
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times

Re: JOINKEY SPACE EXCEEDED error

Postby Ed Goodman » Mon Oct 31, 2011 8:36 pm

Wow...my mind is blown.

Why would anyone come back, three years later, and say they have the same problem? Did they not get it fixed, or worked-around, in 36 months? Has this job been failing for three years now?

I just can't get my head around it. I wonder if three years from now, this person will come back and explain.

Maybe this IS some sort of time rift! The TS is stuck in some temporal storm, and they think they are asking questions every few hours, but in our universe it's three years. That would make more sense to me than what really seems to have happened.
Ed Goodman
 
Posts: 342
Joined: Thu Feb 24, 2011 12:05 am
Has thanked: 3 times
Been thanked: 17 times


Return to Syncsort/Synctool

 


  • Related topics
    Replies
    Views
    Last post