How to identify jobs or projects that have changed

[bcarlson]

We have weekly backups of our DataStage enviroments - XMETA database, WAS, etc. But this requires downtime.

We would like to do daily online backups to guard against loss of work, espeically in development.

One option we are considering is simply identifying projects or jobs that have changed and using istools to export to ISX files and writing to tape. Simple and requires no downtime, and easy to recover your work.

Is there a simple way to identify projects/jobs that have changed? Some UV command or query?

Thanks!

Brad.

[bcarlson]

By the way, I know I can use a simple Unix find command and search for any item changed inthe last day:

Code: Select all

find <projdir> -mtime -1

I opened a project, compiled a job and immediately got the following list from the find command:

eiw_lwd_icon/DS_AUDIT/DATA.30
eiw_lwd_icon/DS_JOBOBJECTS/DATA.30
eiw_lwd_icon/DS_JOBOBJECTS/OVER.30
eiw_lwd_icon/DS_JOBS/DATA.30
eiw_lwd_icon/DS_ROUTINES/DATA.30
eiw_lwd_icon/DS_STAGETYPES/DATA.30
eiw_lwd_icon/DS_TEMP1/DATA.30
eiw_lwd_icon/DS_TEMP1/OVER.30
eiw_lwd_icon/RT_CONFIG1/DATA.30
eiw_lwd_icon/RT_CONFIG1/OVER.30
eiw_lwd_icon/RT_LOG1/DATA.30
eiw_lwd_icon/RT_SC1
eiw_lwd_icon/RT_SC1/OshExecuter.sh
eiw_lwd_icon/RT_SC1/OshScript.osh
eiw_lwd_icon/RT_STATUS1/DATA.30
eiw_lwd_icon/RT_STATUS1/OVER.30
eiw_lwd_icon/VOC

Just wondering if there is a cleaner way to do this.

Thanks!

Brad.

[asyed]

You could query the DS_AUDIT table to obtain the list of jobs recently modified

[ray.wurlod]

DS_AUDIT is not reliable in version 8. I think Brad's technique is about as clean as you're going to get. The DTM is available through XMETA, but querying that is ugly, even if you use Metadata Workbench.

[PaulVL]

Let's not forget about the non job items that can change in DEV. Parameter sets, routines, etc...

compiled jobs is probably not a safe enough way to back up dev.