DSXchange

The only option is "Replace Existing Items" but this does not help me in this scenario Actually that can help you: just delete the job you want to restore then uncheck that box when you import the full archive and the information server manager will ignore all your jobs except the one you...

That link may help you -> How to configure Information Server Manager to use Subversion

The "Description" line must be added under the job name, on the DSRECORD token, not on the DSSUBRECORD.

You can do it that way: Create a job to load one sequential file to a table, set your input stage file property option to a job parameter. Create a text file who lists every files you have to load Create a sequence job like that: Execute Command --► Start loop activity ------► Job Activity ▲ | | | |...

If your stage fails when a bad record is read by the sequential file stage, the option 'Reject mode' must be set on 'Fail'.
Just change it to 'Continue' or 'Output' if you want to redirect them to a reject link and your job will process only with the good records.

For me, the first step is to create a job to put all the records from your base to a Dataset. Then, you can create a multiple instance job to modify your schema like that: Input Dataset ---> Modify ---> Output Dataset In the modify, set the specification to "KEEP #PARAM1#" where PARAM1 is ...

Did you try using the Operations Console ?

To avoid that mass update thing you can put your global parameters to the value "$PROJDEF" and define their values on the DataStage Administrator client.
Updating the whole project will be much easier that way.

Did you consider using the information server manager source control?

Yes passing the job name. invocation id That's strange, i just try : hJob = DSAttachJob('Jx_001_JobControl', DSJ.ERRFATAL) Status = DSGetJobInfo(hJob, DSJ.JOBSTATUS) Here Statuts = 99 Then i try : hJob = DSAttachJob('Jx_001_JobControl.L_01', DSJ.ERRFATAL) Status = DSGetJobInfo(hJob, DSJ.JOBSTATUS) ...

To get the real statut of the job, 'JobName' have to contain the job name and the invocation ID.

Job parameters can't be null, your job will abort if they are. To check if the parameters are given or not by the main program you can initialize them with a default value and in the job, check for that value. Ex: Parameter : LPAR_TMP -> Default value : 'NULL' On a Transformer : If LPAR_TMP = 'NULL'...

DataStage will adapt the input data to the output format, so, from a decimal to a smallint field just mapping your field will do the required conversion

Is >That< the link you want ?

You can compare the 'DSParams' files from your projects to see which parameter is different.
The 'DSParams' files are on your projects folders, ex :
/opt/datastage/IBM/InformationServer/Server/Projects/ADMIN