IBM Support

PM87939: USER RECEIVES A FIELD MAPPING ERROR MESSAGE WHEN USING DBCS ITEMS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • User is submitting a batch job using the DSCMP function.  They
    are receiving the following error:
    
       FMNBB451 Field mapping error:  .SçSáVäfäìäóç¾çS  was not
                found in copybook/template.
    
    The field contains double-byte characters.
    

Local fix

  • Remove the period from the field name.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All File Manager Users of functions that     *
    *                 support the specification of field names.    *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. A function using a template that     *
    *                      contains DBCS field names issues the    *
    *                      message FMNBB451 'Field mapping error'  *
    *                      and terminates.                         *
    *                      2. Field names starting with F or U are *
    *                      incorrectly interpreted when specified  *
    *                      in an XML template expression or the    *
    *                      selection criteria of a VIEWIMS call.   *
    *                      3. When qualification is required to    *
    *                      make a field name reference unique,     *
    *                      File Manager may not correctly          *
    *                      identify the field that has been        *
    *                      specified.                              *
    *                      4. ABENDS0C4 occurs if more than 500    *
    *                      symbols are specified in a template     *
    *                      expression.                             *
    *                      5. Fields are displayed when they are   *
    *                      deselected in the XML template the      *
    *                      function is running with.               *
    *                      6. The dpc attribute of the <cobol>     *
    *                      element is not recognized when an XML   *
    *                      template is processed.                  *
    *                      7. File Manager issues msgFMNBB312      *
    *                      'Storage exhausted' when a template     *
    *                      expression is too large. This message   *
    *                      doesn't adequately describe the error   *
    *                      condition.                              *
    *                      8. When a template is exported to XML,  *
    *                      the <exp>criteria</exp> elements        *
    *                      should specify the field names and not  *
    *                      the field reference numbers (#nn).      *
    *                      Field names are better for maintenance  *
    *                      and readability.                        *
    *                      9. File Manager loops when importing or *
    *                      using an XML template that references a *
    *                      field name that cannot be found in the  *
    *                      specified copy members.                 *
    *                      10. File Manager (PBK) Print and View   *
    *                      Copybook function may ABENDS0C4 when    *
    *                      trying to print or view an XML          *
    *                      template.                               *
    *                      11. Trying to import an XML view or     *
    *                      criteria that does not have a           *
    *                      <layout> tag results in an ABENDS0C4.   *
    *                      12.You cannot specify an unformatted    *
    *                      field reference when using the          *
    *                      #field_name syntax in expressions.      *
    *                      13. Related criteria for XML            *
    *                      templates running under REXX do not     *
    *                      give the correct results.               *
    *                      14. ABENDS0C4 performing an editor      *
    *                      insert with a dynamic template that     *
    *                      has a field defined with length *.      *
    *                      15. <syslib> data sets specified in XML *
    *                      templates are ignored when the function *
    *                      runs under ISPF or CICS.                *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    1. When processing field names a period is assumed to be a
    delimiter between qualifiers.
    

Problem conclusion

  • File Manager has been modified as follows:
    1. Functions correctly process DBCS field names and C'dbcs name'
    can now be specified to avoid keyword translation in English.
    2. Field names starting with F or U are correctly interpreted
    when specified in an XML template expression or the selection
    criteria of a VIEWIMS call.
    3. When qualification is used to make a field name reference
    unique, File Manager correctly identifies the field that has
    been specified.
    4. File Manager does not abend when there are more than 500
    symbols in a template expression.
    5. Fields are not displayed when they are deselected in the XML
    template the function is running with.
    6. The dpc attribute of the <cobol> element is processed
    correctly.
    7. File Manager issues msgFMNBA825 'Resultant expression has
    exceeded the maximum limit of &MAX characters' when a template
    expression is too large.
    8. Exported template expressions will now specify the field
    names.
    9. File Manager issues an error message when field name
    references cannot be found in the specified copy members.
    10 and 11. ABENDS0C4s have been corrected.
    12. A new syntax #U:field_name will be used to indicate an
    unformatted reference will be produced and accepted where
    #field_names can be entered in expressions.
    13. Related criteria for XML templates running under REXX give
    the correct results.
    14. ABENDSOC4 in editor insert processing corrected.
    15. Specified <syslib> data sets will now be used when the
    function runs under ISPF or CICS.
    Publication Closing Code: DEVCHNG
    For the documentation changes associated with this APAR,
    please refer to:
    ftp://public.dhe.ibm.com/software/websphere/awdtools/
        filemanager/fmv12apar.pdf
    
    The changes are to the following publications:
    
    PUB ID        PUB NAME
    ------------  ----------------------------------------
    
    SC19-3674-00  File Manager for z/OS V12R1 User's Guide
                  and Reference
    
    
    The latest published manuals can be found at:
    http://www.ibm.com/software/awdtools/filemanager/library/
           index.html.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM87939

  • Reported component name

    FILE MANAGER Z/

  • Reported component ID

    5655W6800

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-04-26

  • Closed date

    2013-07-23

  • Last modified date

    2013-08-02

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

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

    UK95967 UK95980 UK95981 UK95982 UK96027 UK96028 UK96046 UK96047

Modules/Macros

  • FMNAFTBL FMNASMX  FMNBA82  FMNCHJCL FMNCREXX FMNDSM   FMNEDIT1
    FMNEDIT3 FMNEDIT5 FMNEDIT6 FMNFTEXC FMNLOCAL FMNMAIN  FMNMSELR
    FMNPBK   FMNPPCLA FMNPRMLB FMNRDRCV FMNRDR2  FMNRMCPL FMNRMDAT
    FMNRMR2  FMNRUNRX FMNRXBFC FMNRXBFL FMNRXBFT FMNRXBGL FMNRXBIL
    FMNRXBMD FMNRXBOF FMNRXBOL FMNRXBPC FMNRXBRC FMNRXBRI FMNRXBRO
    FMNRXBSC FMNRXBSR FMNRXBTF FMNRXBTV FMNRXFNT FMNRXFUN FMNRXIBV
    FMNRXLTB FMNSMF3S FMNSMF3X FMNTMPX  FMNTMPXR FMNTMPXU FMNTPBFD
    FMNTREXX FMN0LVL  FMN0LVLJ FMN0LVLK FMN0MENU FMN0MJPN FMN0MKOR
    FMN0RETC FMN0RETI FMN1FEB1 FMN1FLGE FMN1FTEX FMN1IEB  FMN1IEBO
    FMN1INIT FMN1LOCL FMN1LVL  FMN1LVLJ FMN1LVLK FMN1MAIN FMN1PBB1
    FMN1PEB1 FMN1REBO FMN1RMDT FMN2FDBC FMN2FDBI FMN2FDBP FMN2FDBX
    FMN2FD2G FMN2FTPI FMN2LVL  FMN3CICS FMN3LVL  HADLC10J
    

Fix information

  • Fixed component name

    FILE MANAGER Z/

  • Fixed component ID

    5655W6800

Applicable component levels

  • RC1A PSY UK95980

       UP13/07/25 P F307

  • RC1C PSY UK95981

       UP13/07/25 P F307

  • RC10 PSY UK95967

       UP13/07/25 P F307

  • RC11 PSY UK95982

       UP13/07/25 P F307

  • RC12 PSY UK96027

       UP13/07/25 P F307

  • RC14 PSY UK96028

       UP13/07/25 P F307

  • RC15 PSY UK96046

       UP13/07/25 P F307

  • RC16 PSY UK96047

       UP13/07/25 P F307

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C10","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSXJAV","label":"File Manager for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C10","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
02 August 2013