IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

WER027A Error


IBM Mainframe Forums -> SYNCSORT
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Chinnadu

New User


Joined: 05 Mar 2009
Posts: 46
Location: Hyderabad

PostPosted: Thu Aug 29, 2019 11:58 am
Reply with quote

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.

SYSIN :
Code:
 SORT FIELDS=(5,2,CH,A,16,5,CH,A,29,6,CH,A)
 RECORD  TYPE=F

WER813I INSTALLATION OPTIONS IN MFX LOAD LIBRARY WILL BE USED
Code:
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
WER036B  G=95994
WER027A  CONTROL FIELD BEYOND RECORD
Back to top
View user's profile Send private message
Nic Clouston

Global Moderator


Joined: 10 May 2007
Posts: 2455
Location: Hampshire, UK

PostPosted: Thu Aug 29, 2019 1:49 pm
Reply with quote

Please use the code tags.

What does the manual say?

Wild guess - you have a record so short that one of the controk fields specified is beyond the end of the record.

Your record type is specified as F but the RECFM seen by Syncsort is VB.
Back to top
View user's profile Send private message
Marso

REXX Moderator


Joined: 13 Mar 2006
Posts: 1353
Location: Israel

PostPosted: Thu Aug 29, 2019 3:51 pm
Reply with quote

1. The "RECORD TYPE=F" statement is ignored (and misleading) and should be deleted:
Syncsort Programmer’s Guide wrote:
Note: If the TYPE specification differs from the RECFM DCB parameter for the SORTIN/SORTINnn DD statement, the latter takes precedence.

2. Hint for WER027A error: use VLTESTI parameter in PARM option.
Back to top
View user's profile Send private message
Chinnadu

New User


Joined: 05 Mar 2009
Posts: 46
Location: Hyderabad

PostPosted: Thu Aug 29, 2019 5:32 pm
Reply with quote

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.
Back to top
View user's profile Send private message
Rohit Umarjikar

Global Moderator


Joined: 21 Sep 2010
Posts: 3048
Location: NYC,USA

PostPosted: Thu Aug 29, 2019 6:10 pm
Reply with quote

You can compare last successful run input Data set vs the failed one input Data set , and then you would know that’s the bad record , and that will be a easy to get to the cause of this problem.

If you need further assistance then show us sample input data ( good and bad one ) and Data set attributes and expected output.
Back to top
View user's profile Send private message
sergeyken

Senior Member


Joined: 29 Apr 2008
Posts: 2010
Location: USA

PostPosted: Thu Aug 29, 2019 7:17 pm
Reply with quote

Quote:
WER027A CONTROL FIELD BEYOND RECORD

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 field
in 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.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA

PostPosted: Thu Aug 29, 2019 7:27 pm
Reply with quote

Quote:
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.
Back to top
View user's profile Send private message
Chinnadu

New User


Joined: 05 Mar 2009
Posts: 46
Location: Hyderabad

PostPosted: Fri Aug 30, 2019 1:51 pm
Reply with quote

Robert Sample,

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.
Back to top
View user's profile Send private message
Nic Clouston

Global Moderator


Joined: 10 May 2007
Posts: 2455
Location: Hampshire, UK

PostPosted: Fri Aug 30, 2019 3:47 pm
Reply with quote

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.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> SYNCSORT

 


Similar Topics
Topic Forum Replies
No new posts Error to read log with rexx CLIST & REXX 11
No new posts Error when install DB2 DB2 2
No new posts CLIST - Virtual storage allocation error CLIST & REXX 5
No new posts Error while running web tool kit REXX... CLIST & REXX 5
No new posts Getting Error while trying to establi... DB2 3
Search our Forums:

Back to Top