JR30322: WHEN IMPORTING AN INTEGER FIELD, NON-NUMERIC CHARACTERS DO NOT CAUSE A FORMAT ERROR.

APAR status

• Closed as program error.

Error description

• When importing
  an
  integer field, the parsing stops at the first non-integer
  character and
  ignores any remaining characters until the next field delimiter.
  This results in the tool silently throwing away data. That is
  unacceptable. The row should be rejected.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of the Sequential File Stage will not see rejected
  recordsif integer fields contain non-numeric characters.
  ****************************************************************
  PROBLEM DESCRIPTION:
  If users are using the Sequential File Stage to import integer
  fields and those fields contain non-numeric characters only the
  numeric piece of the field will be imported.  The record will
  beimported successfully.
  ****************************************************************
  RECOMMENDATION:
  Apply patch JR30333 and set APT_IMPORT_REJECT_INVALID_CHARS
  This change is included in 8.1 Fix Pack 1.
  ****************************************************************
  

Problem conclusion

• Added an option to allow the user to reject records with
  numericfields that contain non-numeric characters.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• SERVER
  

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R801 PSN

     UP