IBM Z and LinuxONE IBM Z

  • 1.  Insufficient space for DB2 arclogs

    Posted Tue January 11, 2022 11:24 PM

    We're having a frequent issue with running out of space for our DB2 arclogs:

    SDSF SYSLOG   7900.111 S0W1 S0W1 01/11/2022 0W         3,302   COLUMNS 02- 161                                                  
COMMAND INPUT ===>                                            SCROLL ===> CSR                                                   
 0020000 S0W1     22011 21:58:34.07 STC07934 00000090  IKJ56893I DATA SET DSNC10.DBCG.ARCLOG1.D22011.T2158322.A0003290 NOT      
                                                       ALLOCATED+                                                               
 0020000 S0W1     22011 21:58:34.07 STC07934 00000090  IGD17273I ALLOCATION HAS FAILED FOR ALL VOLUMES SELECTED FOR DATA SET    
                                                       029                                                                      
                                         029 00000090  DSNC10.DBCG.ARCLOG1.D22011.T2158322.A0003290                             
 0020000 S0W1     22011 21:58:34.08 STC07934 00000090  IGD17277I THERE ARE (1) CANDIDATE VOLUMES OF WHICH (1) ARE ENABLED OR    
                                                       QUIESCED                                                                 
 0020000 S0W1     22011 21:58:34.08 STC07934 00000090  IGD17290I THERE WERE 1 CANDIDATE STORAGE GROUPS OF WHICH THE FIRST 1 031 
                                         031 00000090  WERE ELIGIBLE FOR VOLUME SELECTION.                                      
                                         031 00000090  THE CANDIDATE STORAGE GROUPS WERE:DB2ARCG                                
 0020000 S0W1     22011 21:58:34.08 STC07934 00000090  IGD17279I 1 VOLUMES WERE REJECTED BECAUSE THEY DID NOT HAVE SUFFICIENT   
                                                       SPACE (041A041D)                                                         
 8000000 S0W1     22011 21:58:34.08 STC07934 00000090  DSNJ103I  -DBCG DSNJDS01 LOG ALLOCATION ERROR 033                        
                                         033 00000090  DSNAME=DSNC10.DBCG.ARCLOG1.D22011.T2158322.A0003290, ERROR               
                                         033 00000090  STATUS=970C0000, SMS REASON CODE=00004379                                
 8000000 S0W1     22011 21:58:34.08 STC07934 00000090  DSNJ115I  -DBCG OFFLOAD FAILED, COULD NOT ALLOCATE AN ARCHIVE DATA SET

    Looking for some additional detail on storage group DB2ARCG, we found only volume VPARC1 in the group:

    RESPONSE=S0W1                                                          
 IGD002I 22:16:54 DISPLAY SMS 403                                      
                                                                       
 STORGRP  TYPE    SYSTEM= 1 2                                          
 DB2ARCG  POOL            + +                                          
   SPACE INFORMATION:                                                  
   TOTAL SPACE = 2432MB USAGE% = 52 ALERT% = 0                         
   TRACK-MANAGED SPACE = 2432MB USAGE% = 52 ALERT% = 0                 
                                                                       
 VOLUME UNIT MVS  SYSTEM= 1 2                             STORGRP NAME 
 VPARC1 03DB ONRW         + +                               DB2ARCG    
 ***************************** LEGEND *****************************    
 . THE STORAGE GROUP OR VOLUME IS NOT DEFINED TO THE SYSTEM            
 + THE STORAGE GROUP OR VOLUME IS ENABLED                              
 - THE STORAGE GROUP OR VOLUME IS DISABLED                             
 * THE STORAGE GROUP OR VOLUME IS QUIESCED                             
 D THE STORAGE GROUP OR VOLUME IS DISABLED FOR NEW ALLOCATIONS ONLY    
 Q THE STORAGE GROUP OR VOLUME IS QUIESCED FOR NEW ALLOCATIONS ONLY    
 > THE VOLSER IN UCB IS DIFFERENT FROM THE VOLSER IN CONFIGURATION     
 SYSTEM  1 = SVSCPLEX   SYSTEM  2 = S0W1

    Can you advise on the best way to address the insufficient space issue please? For information, our VPWRK* volumes are not SMS managed so I'm not sure what, if anything, the impact of adding one or more of them to the DB2ARCG storage group might be if this is the solution.

    Claire




    ------------------------------
    Claire Hamilton
    ------------------------------


  • 2.  RE: Insufficient space for DB2 arclogs

    IBM Champion
    Posted Wed January 12, 2022 07:38 PM
    Is the system part of the Dallas ISV Center? If so, try joining the user group at https://www.ibm.com/community/z/usergroups/ibm-z-dallas-isv-center/join and posting there.

    It should be actively monitored by the Dallas ISV people. 

    In any case, there might be some advises on the Db2 Reference Guide for the Remote Access Programs: http://dtsc.dfw.ibm.com/MVSDS/'HTTPD2.DSN01.PUBLIC.PDF(DB2REF)'

    ------------------------------
    Hartanto Ario Widjaya

    https://hartan.to | https://securitypuppy.com

    Check out https://mainframe.carrd.co for a collection of mainframe links!
    ------------------------------

    Original Message


  • 3.  RE: Insufficient space for DB2 arclogs

    Posted Thu January 13, 2022 10:04 AM

    By my experience, the simple way is to keep DSNC10.DBCG.ARCLOG1 30 gens for two cycles restore.

                                VTOC Summary Information                          

      Volume . : VPARC1                                                           

      Command ===>                                                                

                                                                                   

      Unit . . : 3390                                                             

                                                                                   

       Volume Data             VTOC Data              Free Space   Tracks    Cyls 

       Tracks . :   45,000     Tracks  . :        15  Size  . . :  32,885   2,191 

       %Used  . :       26     %Used . . :         5  Largest . :  30,960   2,064 

       Trks/Cyls:       15     Free DSCBS:       716  Free                        

                                                      Extents . :       6         

    That means you need to check this dataset gens regularly (every day) to delete extra gens and keep enough space for DB2.                                                                                

                                                                                   

                                                                                   

     

     

    Thank you very much.

     

    Best Regards,

    Jianfu Wang

    Sr. ITS Administrator

    Cognizant - TZUSA

    (270)792-8618

     

    This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.



    Original Message


  • 4.  RE: Insufficient space for DB2 arclogs

    Posted Thu January 13, 2022 11:00 AM

    I assume this is a test system.

    We use simple test databases and don't need log archives, so we purge them.

    e.g. nightly automation jcl

    //DELDB2 EXEC PGM=IDCAMS
    //SYSPRINT DD SYSOUT=*
    DELETE DSNC10.DBCG.ARCLOG1.D*.T*.* MASK PURGE
    SET LASTCC = 0
    SET MAXCC = 0



    ------------------------------
    Clark Hunter
    ------------------------------

    Original Message


  • 5.  RE: Insufficient space for DB2 arclogs

    Posted Sun January 16, 2022 12:03 AM
    Thank you everyone for your help. The issue occurs regularly for us and purging the log archives wasn't allowing us to keep on top of it. We've requested additional volumes be added to the storage group in question so hopefully this in conjunction with managing the log archives will stop it being a problem.

    ------------------------------
    Claire Hamilton
    ------------------------------

    Original Message


  • 6.  RE: Insufficient space for DB2 arclogs

    Posted Tue January 18, 2022 02:43 PM
    Hi Claire,
    You can manage these archive logs with HSM interval migration. When pool hits its threshold, these data sets could be migrated to tape or cloud storage automatically so you do not need to add new volumes to this storage group pool.

    ------------------------------
    Caglar Levent Demir
    ------------------------------

    Original Message