Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
Sort product, usually require, SYSOUT data-sets to write the system-generated messages.Well knowing this is not really necesary , keeping the error message you got, in mind - why have you not just added the SYSOUT, which is quite evident from the error mesage itself?
SYNCSORT LICENSED FOR CPU SERIAL NUMBER 6585F, MODEL 2097 705 LICEN
SYSIN :
SORT FIELDS=COPY
WER002A EXCESS CARDS
WER211B SYNCSMF CALLED BY SYNCSORT; RC=0000
WER449I SYNCSORT GLOBAL DSM SUBSYSTEM ACTIVE
am getting the error as excess cards.i have used around 1300 condition like above.i tried with 3 or 4 condition the job is running fine.is there any limit for include condition?
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
Hello,
To get help, you need to post the complete diagnostic informaton generated by the run.
Quote:
is there any limit for include condition?
Yes.
Syncsort wrote:
EXPLANATION: The static internal storage area is inadequate for the
quantity and/or complexity of the control statements in this application.
Either the minimum storage value set at installation time is too low, or
insufficient storage is available in your region.
ACTION: Ask the systems programmer in charge of SyncSort installation
to increase the minimum storage (MINCORE) value unless the
storage available in the region is less than the minimum storage value.
In that case, increase the storage available in the region or partition so
that it at least equals the minimum storage value.
I also believe that you can't OMIT and INCLUDE in the same step.
This is correct. The OMIT statements will need to be added to the INCLUDE portion as NE (not equal to the value) instead of EQ.
balajipradeep wrote:
am getting the error as excess cards.i have used around 1300 condition like above.i tried with 3 or 4 condition the job is running fine.is there any limit for include condition?
There is no numerical limit to the number of comparisons that can be in an INCLUDE or OMIT statement. The limitation is based upon your system resources, specifically MINCORE (a subset of your below the line resources.) You can try passing a higher MINCORE value as a runtime parameter to get around the problem. For example, try adding the following statements to the SORT step in question:
Code:
//$ORTPARM DD *
MINCORE=512K
You can increase this value as needed in 256K increments up to about 2M. If you are still encountering the WER002A, then I might suggest writing all the INCLUDE values to another file and then coding a JOIN application to acquire the desired output. If you would like further assistance with that, then please contact me offline at alissa.margulies@syncsort.com and I would be happy to help you.
