Orchestrate code in dsx

vinsashi · Post by **vinsashi** » Thu Dec 03, 2009 8:02 am

Hi,
I have removed orchestrate code from dsx(one job of dsx) and again i imported dsx(which has with out orchestrate code) after that also i got succeed in importing and i got job in designer.what is the purpose of oshcode.

Code: Select all

#################################################################
#### STAGE: TGT_SBJ
## Operator
copy
## General options
[ident('TGT_SBJ')]
## Inputs
0< [] 'LKP_SBJ_KEY:TO_TGT_SBJ.v'
## Outputs
0>| [ds] '[&"PARAM.wipfilepath"][&"PARAM.wip_filename"]'
;

if i remove oshcode and importing dsx is any problem in future..
Thanks
vin...

chulett · Post by **chulett** » Thu Dec 03, 2009 8:16 am

Why bother with doing something like this? What you've removed is what the job needs to run, forcing a recompile.

vinsashi · Post by **vinsashi** » Thu Dec 03, 2009 8:25 am

Hi,
from existing dsx i am creating multiple dsx files with different metadata for example
source
eid,dept
1,cse
2,ece
3,cse
the source is txt file and loading into dataset i did one job for this one.i
next i am getting another new file but i wont do new job
with existing dsx i wil change metadata .at that time i didnt change oshcode.but i am getting correct job after importing with new metada..

thanks
vin..

chulett · Post by **chulett** » Thu Dec 03, 2009 8:35 am

So... let me get this straight. Rather than create multiple jobs, or perhaps leverage a schema file, you instead are willing to export the job / change the metadata / reimport the job back and forth as needed? Or have some mechanism to import the 'proper' dsx for the file to be processed?