CA DISK/OS LUSEDATEn parameter not honored

Products

• Disk Backup and Restore - MVS
• DISK BACKUP AND RESTORE- ADD-ON OPTIO
• DISK BACKUP AND RESTORE

Issue/Introduction

When we restore an arcive datasets in batch or by dmsar using LUSEDATE set to N, the last used date of restored file is not the original last use date. The last date use is the job restore date.

How can we get the original last use date for our restored file ?

 

Environment

Release:
Component: DISKOS

Resolution

What we need to check exactly is:
if the hooks are applied 
and
the value of  the LUSEDATE used during the restore.

To verify if the hooks have been applied we should run the following job:

/DUMPT EXEC PGM=AMASPZAP 
//SYSPRINT DD SYSOUT=* 
//SYSLIB DD DSN=SYS1.LPALIB,DISP=SHR <= from z/OS 2.3 system! 
//SYSIN DD * 
DUMPT IGC0001I IFG0196W 
DUMPT IFG0194A IFG0194E 
DUMPT IGGDADSM IGGDAU01 
DUMPT IGC00020 IFG0201R 

and then compare with the OPEN ZAPs of CA DISK/OS. 

If the hooks are not applied, please contact CA Technologies to provide them to you.

To verify the value of the LUSEDATE used during the restore we need to add SYSPARMSS on the //SYSPARMS dd 

//SYSPARMS DD * 
SYSPARMSS 

and then check the values.

You can change it in the SYSPARMS member from the CCUWPARM CA DISK  library - and in this case the value of the parameter will be applied on all restore's  batch and DMSAR or override it on the batch coding 

//SYSPARMS DD *
LUSEDATEN 

and restore the file.  

LUSEDATEn
Valid for RESTORE, RECOVER, and VRECOVER
This system parameter controls whether or not restore processing should alter the format-1 last use date of the data set being restored. The default value of N leaves the last use date unaltered. Specifying a value of Y causes restore to set the last use date to the current date.
Note: For VSAM, this system parameter supports only clusters cataloged in ICF catalogs.


For any more information please contact CA Technologies.