IBM Support

OA63093: USING DEVICE_CLASS=DASD STILL RESULTS IN TAPE DEVICES BEING READ

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Using DEVICE_CLASS=DASD still results in tape devices being read
    
    When running a compliance report that includes the CARLa
    statement DEVICE_CLASS=DASD, multiple CKR0305, CKR0307, and
    CKR0703 messages are issued indicating a problem with tape even
    though tape should be excluded.
    

Local fix

  • Suppress tape error messages as an interim work around
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of zSecure Audit exploiting the        *
    *                 "Sensitive Data Set Names" report (newlist   *
    *                 type SENSDSN) and/or the "Data Set Names"    *
    *                 report (newlist type DSN).                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: zSecure Audit performs analysis of      *
    *                      tape data sets even if these data sets  *
    *                      are excluded by the selection on the    *
    *                      DEVICE_CLASS field for SENSDSN/DSN      *
    *                      reports. As result, a series of         *
    *                      MSGCKR0305, MSGCKR0307, and MSGCKR0703  *
    *                      might be issued.                        *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF provided.                      *
    ****************************************************************
    When tape data set analysis is excluded from the SENSDSN/DSN
    reports (for example, by the DEVICE_CLASS=DASD clause on the
    SELECT statement), the zSecure Audit still processes tape data
    set information stored in a CKFREEZE data set. This might result
    in a series of the following messages:
     o MSGCKR0305 (Catalog entry conflicts with tape management
       system...).
     o MSGCKR0307 (Conflicting tape management information...).
     o MSGCKR0703 (First volume conflict tape...).
    

Problem conclusion

  • zSecure Audit has been modified so that tape data sets are
    excluded from the analysis in cases where the selection on the
    DEVICE_CLASS field (SENSDSN/DSN reports) excludes these data
    sets, so that no MSGCKR0305, MSGCKR0307, and MSGCKR0703 are
    issued in this case.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA63093

  • Reported component name

    AUDIT-R,A,T ACF

  • Reported component ID

    5655T0200

  • Reported release

    250

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-04-19

  • Closed date

    2022-08-18

  • Last modified date

    2022-09-01

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

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

    UJ08952

Modules/Macros

  • CKASLGIN CKRCFS   CKRCFV   CKRCINI2 CKRINMO  CKRINP@  CKRLINIT
    CKRMAIN  CKRPREP  CKRSYDB  GKRCFS   GKRCFV   GKRCINI2 GKRINMO
    GKRINP@  GKRLINIT GKRMAIN  GKRPREP  GKRSLGIN GKRSYDB
    

Fix information

  • Fixed component name

    ZSEC BASE,ADMIN

  • Fixed component ID

    5655T0100

Applicable component levels

  • R250 PSY UJ08952

       UP22/08/19 P F208

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPQTM","label":"IBM Security zSecure Admin"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"250","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
01 September 2022