IBM Support

OA48775: NEW FUNCTION - SMF_RECORD() AUTHORIZATION CAN BE BASED ON SMF RECORD TYPE AND SUBTYPE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • NEW FUNCTION - smf_record() allows authorization
    based on SMF TYPE and SUBTYPE
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of z/OS UNIX System Services for   *
    *                 HBB7780 HBB7790 and HBB77A0.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Add support to the USS smf_record()     *
    *                      (BPX1SMF, BPX4SMF) syscall to allow     *
    *                      authorization based on the SMF record   *
    *                      type and subtype.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Support is provided for more granular authorization to the
    smf_record service (BPX1SMF/BPX4SMF) using a new facility
    class profile, BPX.SMF.type.subtype where type is the SMF
    record type and subtype is the SMF record subtype that is
    to be recorded.
    If this new facility class is defined and the user is permitted
    to it, the smf_record service will allow the caller to write an
    SMF record of the specified type and subtype only.
    Use of the BPX.SMF.type.subtype facility class profile has some
    additional requirements over the use of the BPX.SMF facility
    class.  To use the BPX.SMF.type.subtype facility class profile,
    the caller must be running in a clean program-controlled
    environment. The smf_record syscall will verify that the
    environment is clean and any future loads or execs to files that
    reside in uncontrolled libraries will be prevented.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    OA48775

  • Reported component name

    OPENMVS SYS SRV

  • Reported component ID

    5695SCPX1

  • Reported release

    790

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function

  • Submitted date

    2015-08-27

  • Closed date

    2015-12-17

  • Last modified date

    2016-01-04

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

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

    UA80086 UA80087 UA80088

Modules/Macros

  • BPXCTFMM BPXMIMST BPXMRCHK BPXMRSMF
    

Publications Referenced
GA22780019SA22780314SA22782113SA22763321GA32088400
SA23228101SC14731401SA38067001GA32088401SA23228102
SC14731402SA38067002   

Fix information

  • Fixed component name

    OPENMVS SYS SRV

  • Fixed component ID

    5695SCPX1

Applicable component levels

  • R7A0 PSY UA80086

       UP15/12/30 P F512

  • R780 PSY UA80087

       UP15/12/30 P F512

  • R790 PSY UA80088

       UP15/12/30 P F512

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":"790","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 January 2016