Peter, Your Syncsort doesn't have JPn for sure, but 2.1 does/should.
Or, to put it another way, someone the other day complained to me it doesn't
work how they want all the time, only some of the time (they wanted to replace
code with JPn as well as use another for testing to a value).
Some Syncsort features exist without being documented.
On Tuesday, 2 February 2016 22:18:24 UTC, Farley, Peter x23353 wrote:
> Bill,
>
> We use Syncsort here, and at least at our version and release level the JPn
> parameters as coded by Kolusu are not supported (this was done on z/OS 2.1)
> and I did not find anything similar in the Syncsort programmer's guide for
> our version:
>
> SYNCSORT LICENSED FOR CPU SERIAL NUMBER XXXXX, MODEL XXXX XXX
> LICENSE/PRODUCT EXPIRATION DATE: 99 XXX 9999
> SYSIN :
>
> OPTION COPY
>
>
>
> OUTFIL REMOVECC,NODETAIL,BUILD=(80X),
>
> HEADER1=('USER XXXXXXX',/,
>
> 'PROCESS',
>
> *
>
> 10:JP1,/,
>
> 'TRANS',
>
> 10:JP2,
>
> 11:'-',
>
> 12:JP3,/,
>
> 'RUNTYPE',
>
> 10:JP4)
>
> WER131I PARM FIELD ERROR - JP1"MY.D
>
> WER268A OUTFIL STATEMENT : SYNTAX ERROR
>
> WER211B SYNCSMF CALLED BY SYNCSORT; RC=0000
>
>
> HTH
>
> Peter
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
