It's really up to the customer, if they want to sync a database with one on
a workstation, they will make sure it's possible. I feel we can live with a
few "false positives". Actually, VSAM is a bit of a rare case, the main use
of the product is syncronise enormous source libraries which are being
developed on workstations.

Thanks
Robin

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Lizette Koehler
Sent: 25 November 2013 20:26
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Getting a VSAM data set's system timestamp

I do not think that will be much better.

For example. If I am using HSM in my shop and do an HBACKDS command, it will
change the Last Backup Date even though the data in the file was not
altered.  This may also be true for DFDSS dumps and possibly other "backup"
functions

You may also have challenges if the VSAM files is handled under RLS (Record
Level Sharing).



Lizette


> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Robin Atwood
> Sent: Monday, November 25, 2013 1:48 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Getting a VSAM data set's system timestamp
> 
> Thanks to everyone who replied. The server is a part of a product and 
> so
installation
> must have a minimal impact on a customer's system. I am currently 
> going
with
> using the last backup date as an indicator that the data set has been
written and a
> sync is required.
> 
> Thanks
> Robin
> 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to