II12159: DOC PROBLEMS ASSOCIATED W/OEM PRODUCTS AFFECTING SMS, ISMF AND DFSMS. 566528462, 5695DF101, 566528461 AND 5695DF161. OEM BUGS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as canceled.

Error description

  • THIS IS AN INFO APAR CREATED TO DOCUMENT PROBLEMS ASSOCIATED
    WITH OEM PRODUCTS AFFECTING SMS, ISMF, NAVIQUEST AND DFSMS.
    RELATED COMPIDs include: 566528462, 5695DF101, 566528461 AND
    5695DF161.
    
    1. An SMS data set is allowed to be created even though the
       user is not authorized to create the data set.  The security
       package, TOP SECRET, failed the data set allocation.  The
       following failure messages were seen in the JOBLOG output:
       TSS7227E CREATE Access Not Granted to Dataset
       PCP.SAVRRRL.COD140A.ACCDALPH.TEST2
       IGD308I DATA SET ALLOCATION REQUEST FAILED -
        RACF FUNCTION: RACDEF FOR
        DATA SET: PCP.SAVRRRL.COD140A.ACCDALPH.TEST2 WITH RETURN
          CODE 08 REASON CODE 00
       The following SMS message was also found in the JOBLOG which
       indicates that the data set was actually allocated:
        IGD101I SMS ALLOCATED TO DDNAME (DD1     )
        DSN (PCP.SAVRRRL.COD140A.ACCDALPH.TEST2          )
        STORCLAS (STORAGE) MGMTCLAS (        ) DATACLAS (      )
        VOL SER NOS= RST084
     An OEM product owned by Sterling, SAM ALLOCATE, gets control
     after SMS and executes its own ACS routines.  SAM ALLOCATE is
     also ignoring the RC08 set by SMS for the security failure
     SAMS ALLOCATE (STERLING) was contacted and provided additional
     information.
     Here is the information from Sterling:
    PTF SS03567 for PV9803 (the fix number and release)
    
    > Following is the description of that fix:
    > Previously STERLING put in a fix to allow ALLOCATE ACS
    > routines to continue processing for a dataset which
    > received a RC 4 or 8.  This new change will fail the
    > request that are passed to us (STERLING) with a RC of
    > 8 or above.
    
    While the above problem was detected using TOP SECRET's
    security package, this type of failure can occur while
    using any security package, ie RACF, if the user is also
    using the SAM ALLOCATE product.  Check with the VENDOR
    (STERLING) to determine if your current verion has the fix
    on which allows ALLOCATE ACS routines to continue for a RC08.
    2. IGD308I RC08 RSN00 AND IGD17354I RC 08 RSN1026 when
      attempting to allocate an SMS managed dataset / or DSS
      restore of an SMS managed dataset.  Also receive:
      ACF99913 ACF2 VIOLATION-08,06...
      This problem is caused by ACF-2 and is corrected by
      CA fix TA7333B  (As of DEC. 2004)
    
    3.S0C9-9 in IGDVTSC1 at x'2B0E' in z/OS 1.12.
    
      There is a hook from SMS code into DTS ACCHOOK product.
    
      The DTS fix number is DTS51159.
    
    4. The following message is received when creating an SMS
       managed GDS dataset that is 43 bytes long using EMCSNAP.
    
      ACF99058
        INVALID DSN JCL.DS.E.O0607C.HFRLOANA.EOD.SSHTX.G0001V00. OR
         LIB SYS1.EMC.LINKLIB.
    
      Note the . at the end of the GDS dataset.  We have found the
      caller of SMS to be CA but, as CA notes it intercepts the call
      to SMS so although it appears that module calls SMS, it
      technically does not.  Upon digging deeper we find EMC's call
      to SMS gets intercepted by CA.
    
      EMC has resolved this in EMC Mainframe Enablers as follows:-
    
      Release:
      7.0          PTF SN70089
      7.2          PTF SN72083
      7.3          PTF SN73067; Also in Level Set 7304.
      7.4          PTF SN74006; Also in Level Set 7401.
      7.5          Base code
    
    
    
    5. Mainview SRM (ie. Stopx37) changes:
       A new SPACPRIM process was introduced in BMC APAR BAG4079
       and is available under all releases of z/OS. The "old"
       StopX37 recovery process for an IDCAMS define would just
       reduce the primary to fit on the volser passed in the CPL.
       This new process will replace the volser and UCB with the
       first available volume in the IGDVLD with sufficient space
       to handle the original primary request.
    
    
       New BMC APAR BAG4265, will prevent the MainView SRM SPACPRIM
       function from assigning an OVERFLOW storage volume during
       an IDCAMS DEFINE without issuing a new SVM4113I message
       to indicate is was necessary to recover the allocation.
       The following is an example of the messages seen under this
       condition:
    
       SVM4000I STEVE1SP, STEP10, $NONE$, ATTEMPTING SPACPRIM FOR
        STEVE1.SPACPRIM.SMSPILL2, MINI2E, 0
       SVM4113I ASSIGNED OVERFLOW VOLSER MINI2E TO SATISFY PRIMARY
        REQUEST FOR STEVE1.SPACPRIM.SMSPILL2
       IGD17223I JOBNAME (STEVE1SP) PROGRAM NAME (IDCAMS )
        STEPNAME (STEP10 ) DDNAME (N/A )
        DATA SET (STEVE1.SPACPRIM.SMSPILL2 ) WAS ALLOCATED
        TO AN OVERFLOW STORAGE GROUP MINIOVFL
    
       APAR BAG4265 is not going to issue any SPACPRIM messages if
       StopX37 should find a volume in a non-overflow storage group
       with sufficient space to satisfy the primary request.
    
    6.  IGD17204I on temporary dataset
    
        IGD17204I UNABLE TO ENQUEUE ON DATA SET
        SYS13030.T040000.RA000.OPEJSDEL.JSFILE.H01
        ENQUEUE RETURN CODE IS 0 ENQUEUE REASON CODE IS 528
        IGD306I UNEXPECTED ERROR DURING IEFAB4C3 PROCESSING
        RETURN CODE 8 REASON CODE 528
        THE MODULE THAT DETECTED THE ERROR IS IGDVTSV1
        SMS MODULE TRACE BACK - VTSV1 VTSVS VTSCR SSIRT
        SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00014
    
       Client resolved issue with CA MIM R11.9.
    
    
    7. Storage leak in DTS DIF/SRS - FIX is DTS51198
    
       The dump shows 3 areas of storage with x'1000' bytes
       getmained and x'208' bytes free within the page.  All three
       are in subpool 230 key 1 at the following addresses:
    
    Data for subpool 230, key  1 follows:
     -- DQE Listing (Virtual 24, Real 24)
      DQE:  Addr 0077B000 Size     1000
                                       FQE: Addr 0077B000 Size 208
      DQE:  Addr 00789000 Size     1000
                                        FQE: Addr 00789000 Size 208
      DQE:  Addr 0078A000 Size     1000
                                        FQE: Addr 0078A000 Size 208
    
    These three areas show the same type of storage like this:
    0077B200   02404F88   0241A5B0   00000000   00000000
    0077B210.:77B64F.--All bytes contain X'00'
    0077B650   00000000   00000000   40000180   00000000
    0077B660   00000000   0246AF00   02469F00   7D1D6A28
    0077B670   00F52000   00050005   00000000   007E5CAC
    0077B680.:77B69F.--All bytes contain X'00'
    0077B6A0   00000000   00000000   00000000   02441118
    0077B6B0.:77BAFF.--All bytes contain X'00'
    0077BB00   40000180   00000000   00000000   01016F00
    0077BB10   01013F00   7DDD5DA8   00F52000   00080008
    0077BB20   00000000   007E5CAC   00000000   00000000
    0077BB30.:77BF9F.--All bytes contain X'00'
    0077BFA0   00000000   00000000   40000180   00000000
    0077BFB0   00000000   01016F00   01013F00   7DDD5DA8
    0077BFC0   00F52000   00070007   00000000   007E5CAC
    
    ~
    All three STORAGE OBTAINs are being issued from the same address
    which points to an area of storage which contains eyecatcher:
    .........00..-DI
    F2006     #GETMA
    IN 12/23/08 15.2
    8  .....{.{.{.{.
    
    8. Multiple IGD17272I messages indicating insufficient space
       with each subsequent message reducing the space requested.
       The primary allocation is successful and the IGD17272I
       messages are for 2ndary space when extending to another
       volume (in this case).
       The 2ndary space is extremely over-allocated causing an
       insufficient space condition.
       BMC Stopx37 release 7.5.02 was being used.
    
       This issue was corrected by upgrading to BMC Stopx37 Rlse
       7.7.00
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  •  See II14673 for additional information.
    

APAR Information

  • APAR number

    II12159

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    1999-12-07

  • Closed date

    2013-10-15

  • Last modified date

    2013-10-15

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

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

Fix information

Applicable component levels



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

z/OS family

Software version:

001

Operating system(s):

MVS, OS/390, z/OS

Reference #:

II12159

Modified date:

2013-10-15

Translate my page

Machine Translation

Content navigation