PI14161: ABEND 0C7 BECAUSE OF LONG NUMERIC FIELD

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• --------------------------------------------------------------
  PMR 54244,697,760 - Abend 0C7 because of long numeric field
  
  
  Date reported: 01/30/2014
  
  
  Prerequisites - All PTFs to date
  
  Dependencies: This APAR contains a fix for PMR 00111,082,000
  Error Msg EZT000-20 ILLEGAL OR UNDEFINED NAME
  
  
  Severity: Medium
  
  Users Affected:
   All IMU users of MU V4.1
  
  Problem Description:
   Customer is getting SC07 because a defined numeric field was 19
   digits long but IMU reduced it to 18 digits automatically,
    causing improper record layout (short by 1 byte).
  
   Customer is asking that long numeric fields are flagged as an
   error.
  
  Problem Summation
   By design, IMU re-sizes all numeric fields over 18 bytes down
   to 18 bytes.
  
  
  Problem Conclusion:
   A new option NUMLIMIT= was added to EASYTRAN/EZPARAMS to
   provide control of numeric fields length with  the following
   choices:
  
   NUMLIMIT=NATIVE Re-size long numeric field down to 18 bytes
   with an informational message.
   This is the default and the way IMU works today.
  
   NUMLIMIT=EASYT Flag long numeric fields (over 18 bytes) as an
   error. This is compatible with Easytrieve plus.
  
  
   NUMLIMIT=EXTEND Allow long numeric fields up to 31 bytes in
   length. This option forces PROCESS ARITH(EXTEND) COBOL
   Compiler option automatically. When this option is in use,
   numeric fields can be defined up to 31 bytes in length.
   Long numeric fields defined with decimal places cannot be used
   on REPORT SUM, LINE and DISPLAY (in report exits)
   statements because total accumulators cannot be handled due to
   size restrictions.
  
  Impact on existing users
   Users who wish to flag long numeric fields as an error must add
   NUMLIMIT=EASYT to the EZPARAMS table.
  
   There is no impact on users who do not wish to alter the way
   things work now.
  
  Changed modules
  FSOFT01.V3R2M0.SFSYFJCC
   EASYT007 - existing byte code macro
   EASYTRAN - existing byte code macro
   EASYOVRD - existing byte code macro
  
  FSOFT01.V3R2M0.SFSYLOAD
   FSCCOBOL - existing module
   xxCCOBOL - existing module
   FSCASSEM - existing module
   FSCCOB31 - existing module
  ----------------------------------------------------------------
  
  
  ----------------------------------------------------------------
  PMR 00111,082,000 error Msg: EZT000-20 ILLEGAL OR UNDEFINED NAME
  
  Prerequisites - All PTFS to date
  
  Date reported: 02/14/2014
  
  Severity: low
  
  Users Affected:
   All IMU users of MU  V4.10
  
  Problem Description:
   Customer is getting an error when a TITLE or a LINE statement
   ends with "."  (a period).
    Example: TITLE 1 'TEST TITLE'  +20.
  
               Would be rejected with:
  
            *ERROR*  EZT000-20,012  "" :ILLEGAL OR UNDEFINED NAME
  
  
  Problem Summation
   IMU parsing logic fails to properly account for the ending
   period
  
  Problem Conclusion:
   Logic was corrected to properly account for the ending period.
  
  Changed Modules
  FSOFT01.V3R2M0.SFSYFJCC
   EASYT007 - existing byte code macro
  -------------------------------------------------------------
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMU V4.1 users.                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. User is getting SC07 because a       *
  *                         defined numeric field was 19         *
  *                         digits long but IMU reduced it       *
  *                         to 18 digits automatically,          *
  *                         causing improper record layout       *
  *                         (short by 1 byte).                   *
  *                                                              *
  *                      2. User is getting an error when        *
  *                         a TITLE or a LINE statement ends     *
  *                         with "."  (a period).                *
  *                                                              *
  *                         Example: TITLE 1 'TEST TITLE' +20.   *
  *                                                              *
  *                           Would be rejected with:            *
  *                                                              *
  *                         *ERROR*  EZT000-20,012  ""           *
  *                         :ILLEGAL OR UNDEFINED NAME           *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF.                               *
  ****************************************************************
  1. By design, IMU re-sizes all
     numeric fields over 18 bytes
     down to 18 bytes.
  
  2. IMU parsing logic fails to
     properly account for the
     ending period.
  

Problem conclusion

• 1. A new option NUMLIMIT= was added to EASYTRAN/EZPARAMS
     to provide control of numeric fields length with the
     following choices:
  
  NUMLIMIT=NATIVE  Re-size long numeric field down to 18
                   bytes with an informational message.
                   This is the default and the way IMU
                   works today.
  
  NUMLIMIT=EASYT   Flag long numeric fields (over 18 bytes)
                   as an error. This is compatible with
                   Easytrieve plus.
  
  
  NUMLIMIT=EXTEND  Allow long numeric fields up to 31 bytes
                   in length. This option forces PROCESS
                   ARITH(EXTEND) COBOL Compiler option
                   automatically. When this option is in use,
                   numeric fields can be defined up to 31
                   bytes in length. Long numeric fields
                   defined with decimal places cannot be
                   used on REPORT  SUM, LINE and DISPLAY
                   (in report exits) statements because
                   total accumulators cannot be handled
                   due to size restrictions.
  
  Impact on existing users:
  
     Users who wish to flag long numeric fields as an error
     must add NUMLIMIT=EASYT to the EZPARAMS table.
  
     There is no impact on users who do not wish to alter
     the way things work now.
  
  
  2. Logic was corrected to properly account for the
     ending period.
  

Temporary fix

Comments

APAR Information

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

  PI12945

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

  UI16328

Modules/Macros

•    FSYASSEM FSYCCBOL FSYCCB31 FSYESORD FSYETRAN
  FSYET007 FSYXCOBO
  

Fix information

• Fixed component name

  MIGRATION UTILI

• Fixed component ID

  5697N4400

Applicable component levels

• R410 PSY UI16328

     UP14/03/27 P F403

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.