CA Allocate

Expand all | Collapse all

VSAM RLS and CA allocate

  • 1.  VSAM RLS and CA allocate

    Posted 10-25-2019 11:09 AM

    Hello All,

    We are this EOV related message in the log when a VSAM RLS file gets an EOV condition.

    VAM is  not getting involved and adding volumes..  

     

    IEC070I 104-0460,PPOSFOR2,PPOSFOR2,DHCFLOGH,C062,,                  

    IEC070I PSHROL.DHCLOGH.LOG.ARCHIVE,PSHROL.DHCLOGH.LOG.ARCHIVE.DATA, 

    IEC070I ICFCAT.PROD01                                                

     

    IEC070I - 104-204, an error occurred during EOV processing for a VSAM data set

     

     

    Application team backed out file from RLS control to a non-RLS dataset and now VAM is working as expected.

    They defined the dataset with the exact same definitions.

     

    V370040 END OF VOLUME RECOVERY OPERATION STARTING FOR             

    V370040 PPOSFOR2,PPOSFOR2,DHCFLOGH,PSHROL.DHCLOGH.LOG.ARCHIVE.DATA

    V370040 CURRENTLY ON EXTENT # 1 ON VOLUME PPICJ9                  

    V370040 END OF VOLUME RECOVERY OPERATION SUCCESSFUL FOR           

    V370040 PPOSFOR2,PPOSFOR2,DHCFLOGH,PSHROL.DHCLOGH.LOG.ARCHIVE.DATA

    V370040 NEW VOLUME SMS ADDED, NEW VOLUME COUNT 9      

     

    The define is exactly the same except the RLS Dataclass and Storclass are removed.

    VAM works when file is not an RLS dataset and does not when it is a RLS dataset.

    That is the only difference. We have seen this in more than 1 file.

      

    DEFINE CLUSTER                              

           (NAME(PSHROL.DHCLOGH.LOG.ARCHIVE)    

            BUFFERSPACE(55296)                  

            TO(99365)                           

            SHAREOPTIONS(2 3)                   

            INDEXED                             

            DATACLAS(EXTVSAM)                   

            SPEED)                               

           DATA                                 

           (NAME(PSHROL.DHCLOGH.LOG.ARCHIVE.DATA)

            CISZ(12288)                         

            CYL(1500 1500)                      

            VOLUMES (* *)                       

            KEY(61 0)                           

            RECORDSIZE(2046 2046)               

            FREESPACE (25 25))                  

           INDEX                                

           (NAME(PSHROL.DHCLOGH.LOG.ARCHIVE.INDX)

            NOIMBED                              

            NOREPLICATE                         

            CYL(25 25)

            VOLUMES (*)

            CISZ(512) )

     

    As you know, RLS is a very different design then non-RLS.  It has its own servers(SMSVSAM) and all the control blocks are inaccessible to other programs. Is it possible that the hooks that VAM has been using to intercept VSAM functions will not work with RLS?

    Thank you,
    Luke Kutner



  • 2.  RE: VSAM RLS and CA allocate

    Posted 10-29-2019 01:54 PM
    This is a duplicate of an already-opened support issue.

    Thank you.
       
    Paul Schuster
    CA Allocate
    L2 Support





  • 3.  RE: VSAM RLS and CA allocate

    Posted 10-30-2019 10:53 AM
    Case 20085743 is one of them, what is the other DUP case?
    Thanks,
    Don

    ------------------------------
    Principal Support Engineer
    Broadcom
    ------------------------------