Dataset backup process not updating LBACKUP date in catalog entry It is showing zeros.
search cancel

Dataset backup process not updating LBACKUP date in catalog entry It is showing zeros.

book

Article ID: 271374

calendar_today

Updated On:

Products

Disk Backup and Restore - MVS

Issue/Introduction

1) Users are backing up datasets, and the LBACKUP date in the catalog entry is zeros, indicating no backup done. 

Is there a Disk Backup configuration option set incorrectly? Or is this working as designed?

 

2) Does CA Disk check management class ADMIN OR USER COMMAND BACKUP attribute? We're thinking of changing those for another product.

 

Environment

Release : 14.0

Resolution

1) Yes, it is normal to have zeros. (Additionally, LISTCAT will provide LBACKUP details only for SMS managed datasets)  You can refer to the LISTD report if backup details are needed for any particular dataset from DISK.

Also the technical reason for leaving LBACKUP date as zeros is because it's an IBM used field and this way Disk will  be able to stay in the out their lane when both Disk and HSM are used in the same shop.  Disk won't change it in case HSM does.

 

2)See :

https://techdocs.broadcom.com/us/en/ca-mainframe-software/performance-and-storage/ca-disk-backup-and-restore/14-0/using/backup-archive/backup-command/sms-and-backup.html

for SMS and BACKUP

it has a section that states;

Admin or User Command Backup (MC)

This required field can be defined BOTH, ADMIN, or NONE. The default is BOTH. When this field is defined BOTH, both the Storage Administrator and the user can explicitly back up a data set. When this field is defined ADMIN, only the Storage Administrator can explicitly back up a data set. When this field is defined as NONE, neither can explicitly back up. To define a Storage Administrator to Disk, use the SMSSTGAD sysparm.