Page 1 of 1
Last Modified Date of a Parallel Job
Posted: Wed Feb 27, 2013 11:11 pm
by arpitchopra
Hi Experts !
We work in an environment which is owned by another company and hence, do not have admin access to the application. As a result, we have to ask them to migrate our jobs and sequences from one environment to another (Example: From Test to Production server).
What is the best way of ensuring that they have done this correctly ? Is there a last modified date associated with every job ? If yes, then where do we look for it ?
If not, then is there any efficient way of testing whether all code components were migrated correctly ?
Posted: Thu Feb 28, 2013 1:28 am
by prasson_ibm
Hi,
If your jobs are migrated from IIS Manager then you can easily find out the last package they have created and you can also idetify the which jobs are changed.
Posted: Thu Feb 28, 2013 1:41 am
by arpitchopra
Hi Prasson,
I don't think that they use the IIS Manager for the migration. They export the jobs in .dsx format and then import this package in the Production server.
Posted: Thu Feb 28, 2013 1:57 am
by prasson_ibm
Hi Arpit,
Since you dont have admin access,you can add last modified date in the comment and then migrate your jobs from dev to prod.I think this is the easiest way.
Posted: Thu Feb 28, 2013 10:23 am
by sudha03_vpr
If you migrate the code to a different environment, the job status changes to compiled with a date against it if you double click the job at the director level. If you are not migrating high volumes then this may be helpful.
Posted: Fri Mar 01, 2013 2:43 am
by BI-RMA
Can you connect to the production environment either with DS-Designer or with Information Server Manager?
In both Tools You can search for changed items within a specified time frame. In Designer use the Advanced-Find dialogue, in ISM the Search Metadata Repository dialogue.
Posted: Fri Mar 01, 2013 12:57 pm
by priyadarshikunal
use the search functionality to search that job and click on the additional details or similar button on search result tab to see the last modified timestamp.
Posted: Fri Mar 01, 2013 6:13 pm
by PaulVL
I believe you would export your compiled objects into your DSX right?
You would want to ensure that the third party company didn't mess with your code (support reasons may arise), so you would want a combination of compile time and last modified time. The act of loading a DSX into an environment changes the last modified time, but not compile time.
*drops 2 cents into cup*
You should create a basic routine that dumps all jobs all compile and modified times to a text file and ask them to send you that file on an as needed basis.