Re-posting as the previous post was posted in a non-syncsort forum. Apologies if it seems a duplicate.
I have a unique problem with how syncsort is working. My shop uses 2 mainframe environments - one runs on OS390 while other runs on Z/os 2 .
The job which performs sort and so far seems to be working perfectly in one mainframe system however the same job with same code is giving an error in different environment. The only visible difference i see is with the Syncsort for Z/os Version.
Below is the code snippet. Trying to understand what might possibly be wrong/incompatible here.
Log from the Code that works ----
Code:
SYNCSORT FOR Z/OS 2.1.4.1R
SYSIN :
SORT FIELDS=(13,31,A,211,27,A,5,7,A),FORMAT=BI
There was an mistake in copying the output of the errored part - Posting the correct one here as not able to edit the one earlier and also the SORT step.
The record length of the input and output file being created is 654. No changes being done there on the length. I am confused about why its working in one environment and not the other?
With RECFM=VB, LRECL=654 each particular record can have any LRECL, between 4 and 654 bytes. Whenever your particular specific record is shorter than 238, you get the error you mentioned.
Again: RTFM, RTFM, and RTFM!!!
P.S.
Maybe, your different environments do have different SORT default options established, to ignore specific situations with records.
Anyway, you need to understand well all those details, starting from understanding LRECL when RECFM=VB...
If you read carefully the explanation of WER147W message (can you?) then you would easily find that SORT parameter VLTEST causes different behavior of the utility in those your two environments.
Why you are not able to read the manual before starting your screaming at the forum? Do you speak English?
Besides, Syncsort releases don’t look the same and in one you already have a warning and in second that warning turned into an error. The error one looks to be the older version of the synsort.
VLSHRT is an option for DFSORT utility, not for SYNCSORT.
That's correct.
If I remember VLTEST=1 is the default and equivalent of VLSHRT in DFSORT. So in SYNCSORT , if you provide VLSHRT then internally it will convert to VLTEST equivalent instead of a syntax error.
If TS make a use of PARM VLSTEST=1 then error should go away and on the side can as well try for OPTION COPY,VLSHRT.
VLSHRT is an option for DFSORT utility, not for SYNCSORT.
That's correct.
If I remember VLTEST=1 is the default and equivalent of VLSHRT in DFSORT. So in SYNCSORT , if you provide VLSHRT then internally it will convert to VLTEST equivalent instead of a syntax error.
If TS make a use of PARM VLSTEST=1 then error should go away and on the side can as well try for OPTION COPY,VLSHRT.
The printed explanation of WER147I message clearly points to VLTEST parameter. The only thing the TS needs to do is, read the manual about this message found in his own log. Plus:<deleted by mod>
