Can somebody tell me how to get rid of WER027A error? Below is the log and error that I'm getting, Nothing has been changed in our system in last 5 years, I'm wondering why we are getting this error now.
WER813I INSTALLATION OPTIONS IN MFX LOAD LIBRARY WILL BE USED
WER276B SYSDIAG= 1040817, 1621925, 1621925, 3113670
WER164B 23,440K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED,
WER164B 0 BYTES RESERVE REQUESTED, 23,344K BYTES USED
WER108I SORTIN : RECFM=VB ; LRECL= 173; BLKSIZE= 27998
WER073I SORTIN : DSNAME=XYX.YX.YYYYY.YYYY.YYYY
WER110I SORTOUT : RECFM=VB ; LRECL= 173; BLKSIZE= 27998
WER074I SORTOUT : DSNAME=YYY.YY.YYY.YYYYY.YYYY.YYYY
WER410B 22,412K BYTES OF VIRTUAL STORAGE AVAILABLE ABOVE THE 16-MEGABYTE LINE
WER410B 0 BYTES RESERVE REQUESTED, 22,412K BYTES USED
WER027A CONTROL FIELD BEYOND RECORD
I tried VLTESTI option and tried by removing "RECORD TYPE=F" option as well.No luck with either of the options. Is there a way to skip failed records and write them to error file ? I would like to continue with rest of the good records.
EXPLANATION: The last byte of a SORT/MERGE or JOINKEYS control
field is located beyond the maximum record length specified or column
32750, or a variable-length record is shorter than the ending
location of a specified SORT/MERGE or JOINKEYS control fieldin an
execution for which this is defined as cause for MFX termination (see
“VLTEST” on page 5.31). Program HISTOGRM may be used to determine
the length of the shortest record in the input file.
1) RECORD TYPE=F is wrong, and misleading when using RECFM=VB, and/or VLTESTI option, and/or other varying record's stuff.
2) First of all, run with SORT FIELDS=COPY and verify everything else is OK.
3) Then add SORT FIELDS=(field1,...) - one by one!, until you get your error. It will point you exactly: which of your field definitions does not match your actual record(s).
4) All said above are the basics of any software development and debugging. Those who has no idea about any of those statements has to think seriously about changing their job.
Joined: 06 Jun 2008 Posts: 8526 Location: Dubuque, Iowa, USA
Nothing has been changed in our system in last 5 years, I'm wondering why we are getting this error now.
Yes, something has changed -- the data you're using in your data set (unless you keep rerunning the same data over and over for the last 5 years). The error you got can be caused by the data, and nothing else needs to have changed to get the error.
You really, really, REALLY need to change to Beginners and Students Forum because you may have been on this forum for 10 years but your attitude and experience level tells us you are a beginner.
Thank you for your assessment, but my sincere advise to you is that don't try to judge anybody by a single line statement. A learner is always a learner irrespective of his/her seniority. Anyways I figured out the problem way and solved it on my own. I would rather prefer to have helpful technical discussion on this forum.
Joined: 10 May 2007 Posts: 2312 Location: Hampshire, UK
Just because you are an expert at some things does not mean you are an expert in all things. I am not an expert in sort so I post my sort questions on the beginners forum. Everyone should consider which forum to post to for each question depending on their expertise in that particular area. So do not knock people when they suggest you make a particular post on the other forum.
It would also help if you provided the solution that you used. These forums are an archive of questions and solutions. I occasionally go around deleteing topics that have no solution because what is the point of the topic being there? It adds nothing to the knowledge base if there is no solution provided.