PH17537: CLOUD TAPE CONNECT V2R1 MULITPLE FIXES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This APAR addresses the following issues:
  1) History processing abends S430 with large number of files
  2) SVC 26 Hook Debug needs to use filtering on jobname
  3) RESTORE RC=0 if Warning message is in joblog
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IBM Cloud Tape Connector for z/OS   *
  *                  (FMID=HCUZ210)                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1) A Return Code of Zero is being set   *
  *                         for a recovery with warning messages *
  *                         displayed                            *
  *                                                              *
  *                      2) A CSA Storage Leak has been          *
  *                         discovered for messages residing in  *
  *                         a print queue. Messages are not      *
  *                         being printed during shut down and   *
  *                         are orphaned in CSA.                 *
  *                                                              *
  *                      3) History Processing Abends with S430  *
  *                                                              *
  *                      4) If copy to cloud compress options    *
  *                         has been set to "Yes" and zEDC is    *
  *                         not available, the copy to cloud     *
  *                         process is bypassed.                 *
  *                                                              *
  *                      5) When max cloud backup generations    *
  *                         parmlib option is decreased, the old *
  *                         generations are not deleted from the *
  *                         repository and the cloud.            *
  *                                                              *
  *                      6) If the repository backup list file   *
  *                         is allocated when the next backup    *
  *                         interval starts, the repository      *
  *                         backup fails. If it's allocated when *
  *                         the STC starts, it will shutdown.    *
  *                                                              *
  *                      7) Catalog Intercept (SVC 26) is        *
  *                         ignoring jobname filtering when      *
  *                         debug is turned on.                  *
  *                                                              *
  *                      8) If history processing is active when *
  *                         the STC is in shut down mode, it     *
  *                         doesn't check the shut down flag     *
  *                         until the next interval.             *
  *                                                              *
  *                      9) TCP sockets with RST flag turned on  *
  *                         may sporadically fail during restore *
  *                         processing. This condition           *
  *                         terminates the restore tasks.        *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  This APAR fixes the following problems of IBM Cloud Tape
  Connector:
  
  1) When a restore job displays warning message of dataset
     allocation failure on DASD but successful on tape, the return
     code is being set to 0 instead of 4.
  
  2) The CUZCLOUD STC puts messages in a queue to be printed to
     CUZOUT DD. When many messages are being added to the queue at
     the same time, it's possible that the queue list gets
     corrupted and messages can be orphaned in CSA storage. When
     the STC is shut down, there are 13 messages pending in the
     queue that will be orphaned as well.
  
  3) When a history interval is triggered and their datasets
     actively being copied to the cloud, the module terminates
     waiting for active tasks to complete. The termination of this
     tasks issues a DEQ, but the ENQ was never executed.
  
  4) If a cloud definition has compression turned on, but no zEDC
     is available, a message is displayed and the copy to cloud
     process terminates. This has been changed to copy the dsn to
     the cloud without compression.
  
  5) If parmlib option Max Backup Generations has been decreased
     and datasets have more backup generations then the new value,
     the older generations are never cleared from the repository.
  
  6) If the repository backup list file was not copied to the
     cloud successfully and not deleted, the next backup interval
     will fail because the dataset can't be allocated. If this
     dataset is cataloged at the time the CUZCLOUD STC is started,
     the STC will be terminated.
  
  7) When debug by jobname has been turned on in the parmlib, the
     Catalog Intercept (SVC 26) is ignoring the jobname filtering
     and displays debug information for all. Every TSO/ISPF user
     will receive messages every time a catalog locate is done on
     a file.
  
  8) The history include / exclude module could run for some time.
     When this process is complete, it's not checking to see if a
     stop command has been issued for the STC. The STC waits for
     all processes to shut down before terminating completely. The
     shut down is checked before going into a STIMER wait.
  
  9) Restore of a large dataset attempts to read from socket
     fail sporadically due to TCP packet with RST flag turned on.
     It led to error during restore and a message CUZS098E. S3
     plugin was changed, so that it could request the rest of the
     file from server and finish restore successfully.
  

Problem conclusion

• The following modules has been modified to fix the problems:
  
    Object Lib Members:
    CUZ$SERV CUZ#API  CUZ#HIST CUZ#INEX CUZ#LEVL CUZ#MAIN CUZ#PARM
    CUZ#RAMR CUZ#RBKP CUZ#RSTG CUZ#RSTR CUZ#STAT CUZ#TERM CUZ@MSG
    CUZ@MSGP CUZ@MSGS CUZ@REST CUZSVH26 CUZ1CLDI CUZ2CDAB CUZ2CDEA
    CUZ2CDEC CUZ2CDED CUZ2CDIO CUZ2CDMS CUZ2CDMT CUZ2CDRK CUZ2CDSV
    CUZ2CDUT CUZ2CDXM CUZ2CLDC CUZ2FTPC CUZ2HDSC CUZ2SLYC CUZ2S3C
    CUZ2THR  CUZ3AES  CUZ3BS64 CUZ3CKDS CUZ3CLIB CUZ3CPCF CUZ3CPHR
    CUZ3HASH CUZ3HMAC CUZ3ICFR CUZ3ICSF CUZ3IKEY CUZ3IUTL CUZ3KEY
    CUZ3PKDS CUZ3RCPH CUZ3RKEY CUZ3RNDM CUZ3SESS CUZ3WRAP CUZ4ALOC
    CUZ4MTIO CUZ4MTSK CUZ4OS   CUZ4QSAM CUZ4TUTL CUZ4UTLS CUZ4XLAT
    CUZ4XML
  
    Panels (ACUZPENU)
    CUZ$SERV
  

Temporary fix

Comments

APAR Information

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

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

  UI66074

Modules/Macros

• CUZ#API  CUZ#HIST CUZ#INEX CUZ#LEVL CUZ#MAIN CUZ#PARM CUZ#RAMR
  CUZ#RBKP CUZ#RSTG CUZ#RSTR CUZ#STAT CUZ#TERM CUZ$SERV CUZ1CLDI
  CUZ2CDAB CUZ2CDEA CUZ2CDEC CUZ2CDED CUZ2CDIO CUZ2CDMS CUZ2CDMT
  CUZ2CDRK CUZ2CDSV CUZ2CDUT CUZ2CDXM CUZ2CLDC CUZ2FTPC CUZ2HDSC
  CUZ2S3C  CUZ2SLYC CUZ2THR  CUZ3AES  CUZ3BS64 CUZ3CKDS CUZ3CLIB
  CUZ3CPCF CUZ3CPHR CUZ3HASH CUZ3HMAC CUZ3ICFR CUZ3ICSF CUZ3IKEY
  CUZ3IUTL CUZ3KEY  CUZ3PKDS CUZ3RCPH CUZ3RKEY CUZ3RNDM CUZ3SESS
  CUZ3WRAP CUZ4ALOC CUZ4MTIO CUZ4MTSK CUZ4OS   CUZ4QSAM CUZ4TUTL
  CUZ4UTLS CUZ4XLAT CUZ4XML  CUZ@MSG  CUZ@MSGP CUZ@MSGS CUZ@REST
  CUZSVH26
  

Fix information

• Fixed component name

  CLD TAPE CONNEC

• Fixed component ID

  5698ABD00

Applicable component levels

• R210 PSY UI66074

     UP19/10/29 P F910

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.