IBM Support

PI81505: AN API PROGRAM CANNOT VERIFY THE UNAUTHORIZED COMMANDS SPECIFIED IN A USER FILE RECORD (SAME AS PI76811)

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A user file record can contain several commands or command
    abbreviations that the user is not authorized to use. An API
    program can read a user file record and access each unauthorized
    command in the record. The program is not able to verify whether
    a command or its abbreviation has been defined in MERVA.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All MERVA ESA users.                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: A MERVA API program cannot verify the   *
    *                      unauthorized commands specified in a    *
    *                      user file record.                       *
    ****************************************************************
    * RECOMMENDATION: This has been corrected. An API program can  *
    *                 now verify any unauthorized command or its   *
    *                 abbreviation in a user file record.          *
    *                 The DSLAPI call FLDG (Get a MERVA variable)  *
    *                 can now be used to indicate whether or not   *
    *                 an unauthorized command has been defined in  *
    *                 a command table. The FLDG call is described  *
    *                 in the MERVA ESA book                        *
    *                 "Application Programming Interface Guide"    *
    *                 in Chapter 9 "DSLAPI Functions".             *
    ****************************************************************
    A MERVA API program cannot verify the unauthorized commands
    specified in a user file record. Verifying means to determine
    whether a command has been defined in one of the MERVA command
    tables.
    

Problem conclusion

  • A command or its abbreviation is verified by specifying the
    qualified name 'CMD.cccccccc' as the field name in the FLDG
    call. 'cccccccc' stands for the command or its abbreviation.
    It can be specified in its actual length with a maximum of
    8 bytes. Padding with blanks is not necessary.
    
    An FLDG call for CMD.cccccccc returns the 1-byte character
    value '0' or '1'.
    Value '0' indicates that cccccccc has not been defined in a
    command table.
    Value '1' indicates that cccccccc has been defined in a
    command table.
    
    The command tables are the nucleus command table DSLNCMT and
    each table specified in the EUD program table DSLEPTT.
    The FLDG call requires that MERVA must be active.
    
    DSLEPTT contains the following IBM provided command tables:
    - DSLECCMT
    - DSLECMDT
    - DSLEFCMT
    - DSLEMCMT
    - DSLEUCMT
    - DSLMCMDT
    - DWSECMDT
    - EKAMSCMT
    
    If the FLDG call is successful, field INTRC contains the return
    code blank. Otherwise, INTRC contains '02'. Then field INTERMSG
    contains error message DSL883I.
    The return code in DSL883I can be one of the following:
    - RC=08
      The specified field name is not known.
    - RC=12
      MERVA is not ready.
    - RC=16
      Either the EUD program table DSLEPTT cannot be loaded or the
      DSLNIC parameter list is not available.
    
    Here are some coding examples. The syntax is similar to REXX.
    The field name is enclosed in parentheses.
    
    A. Verify different occurrences of the operator command
    TERMINAT:
    Call FLDG ('CMD.TERMINAT') returns '1' (defined in DSLNCMT).
    Call FLDG ('CMD.T')        returns '1' (defined in DSLNCMT).
    Call FLDG ('CMD.TE')       returns '0' (invalid abbreviation,
                                         less than four characters).
    Call FLDG ('CMD.TER')      returns '0' (invalid abbreviation,
                                         less than four characters).
    Call FLDG ('CMD.TERM')     returns '1' (valid abbreviation,
                                        minimum of four characters).
    
    B. Verify different occurrences of the session command
    HARDCOPY:
    Call FLDG ('CMD.HARDCOPY') returns '1' (defined in DSLECMDT).
    Call FLDG ('CMD.HCO')      returns '1' (defined in DSLECMDT).
    Call FLDG ('CMD.HAR')      returns '0' (invalid abbreviation,
                                         less than four characters).
    Call FLDG ('CMD.HARDCO')   returns '1' (valid abbreviation,
                                         more than four characters).
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI81505

  • Reported component name

    MERVA ESA 4.1.0

  • Reported component ID

    5648B2900

  • Reported release

    410

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-12

  • Closed date

    2017-05-17

  • Last modified date

    2017-06-02

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

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

    UI47238

Modules/Macros

  • DSLAPIFL DSLCSD41 DSLEPT   H0B0410J
    

Fix information

  • Fixed component name

    MERVA ESA 4.1.0

  • Fixed component ID

    5648B2900

Applicable component levels

  • R410 PSY UI47238

       UP17/05/19 P F705

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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7LGL","label":"MERVA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"","label":""}},{"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":"410","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 June 2017