Unable to add new parameters to a dsx
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 47
- Joined: Tue Sep 13, 2005 4:28 am
Unable to add new parameters to a dsx
Team,
I have a requirement of addding three new parameters and annotations to a job.
I have taken the dsx of the job to my local machine.
I modified the annoation and saved the dsx and imported the DSX back. the change got reflected in the job.
Likewise i added three parameters under the cparameters in dsx and saved it.when i import the dsx the parallel job is showing an error as cdefn =class and root =" . then when i search for the job the parallel job is becoming into a server job.
I have a requirement of addding three new parameters and annotations to a job.
I have taken the dsx of the job to my local machine.
I modified the annoation and saved the dsx and imported the DSX back. the change got reflected in the job.
Likewise i added three parameters under the cparameters in dsx and saved it.when i import the dsx the parallel job is showing an error as cdefn =class and root =" . then when i search for the job the parallel job is becoming into a server job.
Kiran Kumar
-
- Premium Member
- Posts: 47
- Joined: Tue Sep 13, 2005 4:28 am
The reason for doing this , we have some 2500 odd jobs for which we need to add APT_Variables and change the annotation.
So thought if i can write a script and add the environmental variables and change the annotations a lot of manual effort would be reduced.
Requirement is we need add APT_GRID variables to all the jobs. so trying to reduce the manual effort
Please suggest.
So thought if i can write a script and add the environmental variables and change the annotations a lot of manual effort would be reduced.
Requirement is we need add APT_GRID variables to all the jobs. so trying to reduce the manual effort
Please suggest.
Kiran Kumar
You need to understand the full changes that need to be made, so I'd suggest first exporting a single job that needs the changes. Then do the work via the Designer in that same job and export it again. Compare the two. Take the changes you've identified and use them in your automation effort.
Hope you had a backup.
Hope you had a backup.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Premium Member
- Posts: 47
- Joined: Tue Sep 13, 2005 4:28 am
Re: Unable to add new parameters to a dsx
I have done as suggested by you. first i have a created a sample job without any parameters and then take the dsx.
Then created a job with the parameters added and then taken the dsx.
compared the dsx. then took the dsx of the job without the parameters in it and then added the values as present in the dsx with the parameters changed the job name and then taken the import.
When i tried to import of the job it gave an error message like this
Unknown property ".
Object=ROOT.
Class=CJobDefn.
Please suggest and advice.
Then created a job with the parameters added and then taken the dsx.
compared the dsx. then took the dsx of the job without the parameters in it and then added the values as present in the dsx with the parameters changed the job name and then taken the import.
When i tried to import of the job it gave an error message like this
Unknown property ".
Object=ROOT.
Class=CJobDefn.
Please suggest and advice.
Kiran Kumar
There's no way for us to know what you've done wrong other than to note that has happened somehow... something specifc to the Job Definition section of the dsx has been corrupted. What do you mean by 'changed the job name'? I would guess the problem lies there.
If they are small enough, post both your "before" and "after" dsx files wrapped in
If they are small enough, post both your "before" and "after" dsx files wrapped in
Code: Select all
tags.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Premium Member
- Posts: 47
- Joined: Tue Sep 13, 2005 4:28 am
Re: Unable to add new parameters to a dsx
Original DSX:
Modified DSX with the parameters added and job name changed.
Code: Select all
BEGIN HEADER
CharacterSet "CP1252"
ExportingTool "IBM InfoSphere DataStage Export"
ToolVersion "8"
ServerName "DSENGINE.DIF.HEW.US.ML.COM"
ToolInstanceID "MIDAS"
MDISVersion "1.0"
Date "2015-03-16"
Time "21.30.05"
ServerVersion "8.7"
END HEADER
BEGIN DSJOB
Identifier "Sample_TEST_4"
DateModified "2015-03-16"
TimeModified "21.28.08"
BEGIN DSRECORD
Identifier "ROOT"
OLEType "CJobDefn"
Readonly "0"
Name "Sample_TEST_4"
NextID "1"
Container "V0"
JobVersion "56.0.0"
ControlAfterSubr "0"
Parameters "CParameters"
BEGIN DSSUBRECORD
Name "$APT_GRID_COMPUTENODES"
Prompt "COMPUTENODES - Number of Compute Nodes"
Default "2"
ParamType "0"
ParamLength "0"
ParamScale "0"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "$APT_GRID_CONFIG"
Prompt "APT_GRID_CONFIG - Use this configuration template file vs. default grid_config.apt file"
ParamType "0"
ParamLength "0"
ParamScale "0"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "$APT_GRID_PARTITIONS"
Prompt "PARTITIONS - Number of partitions per Node (compute)"
Default "1"
ParamType "0"
ParamLength "0"
ParamScale "0"
END DSSUBRECORD
MetaBag "CMetaProperty"
BEGIN DSSUBRECORD
Owner "APT"
Name "AdvancedRuntimeOptions"
Value "#DSProjectARTOptions#"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "TraceMode"
Value "0"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "TraceSeq"
Value "1"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "TraceRecords"
Value "100"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "TraceSkip"
Value "0"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "TracePeriod"
Value "1"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "RecordJobPerformanceData"
Value "0"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "IdentList"
Value "Sequential_File_0|Sequential_File_3"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "ClientCodePage"
Value "1252"
END DSSUBRECORD
NULLIndicatorPosition "0"
OrchestrateCode =+=+=+=
#################################################################
#### STAGE: Sequential_File_0
## Operator
import
## Operator options
-schema record
{final_delim=end, delim=',', quote=double}
()
-rejects continue
-reportProgress yes
-file '/home/nbkmakl/sample_test1.dat'
## General options
[ident('Sequential_File_0'); jobmon_ident('Sequential_File_0')]
## Outputs
0> [] 'Sequential_File_0:DSLink2.v'
;
#################################################################
#### STAGE: Sequential_File_3
## Operator
export
## Operator options
-schema record
{final_delim=end, delim=',', quote=double}
()
-file '/home/nbkmakl/sample.test'
-overwrite
-rejects continue
## General options
[ident('Sequential_File_3'); jobmon_ident('Sequential_File_3')]
## Inputs
0< [] 'Sequential_File_0:DSLink2.v'
;
=+=+=+=
IsTemplate "0"
NLSLocale ",,,,"
JobType "3"
Category "\\test_j"
CenturyBreakYear "30"
NextAliasID "2"
ParameterFileDDName "DD00001"
ReservedWordCheck "1"
TransactionSize "0"
ValidationStatus "0"
Uploadable "0"
PgmCustomizationFlag "0"
JobReportFlag "0"
AllowMultipleInvocations "0"
Act2ActOverideDefaults "0"
Act2ActEnableRowBuffer "0"
Act2ActUseIPC "0"
Act2ActBufferSize "0"
Act2ActIPCTimeout "0"
ExpressionSemanticCheckFlag "0"
TraceOption "0"
EnableCacheSharing "0"
RuntimeColumnPropagation "1"
RelStagesInJobStatus "-1"
WebServiceEnabled "0"
MFProcessMetaData "0"
MFProcessMetaDataXMLFileExchangeMethod "0"
IMSProgType "0"
CopyLibPrefix "ARDT"
RecordPerformanceResults "0"
END DSRECORD
BEGIN DSRECORD
Identifier "V0"
OLEType "CContainerView"
Readonly "0"
Name "Job"
NextID "1"
IsTopLevel "0"
StageList "V0S0|V0S3"
StageXPos "120|384"
StageYPos "192|192"
StageTypes "CCustomStage|CCustomStage"
NextStageID "4"
SnapToGrid "1"
GridLines "0"
ZoomValue "100"
StageXSize "48|48"
StageYSize "48|48"
ContainerViewSizing "0000 0000 0429 0445 0000 0001 0000 0000"
StageNames "Sequential_File_0|Sequential_File_3"
StageTypeIDs "PxSequentialFile|PxSequentialFile"
LinkNames "DSLink2| "
LinkHasMetaDatas "False| "
LinkTypes "1| "
LinkNamePositionXs "232| "
LinkNamePositionYs "208| "
TargetStageIDs "V0S3| "
SourceStageEffectiveExecutionModes "1| "
SourceStageRuntimeExecutionModes "1| "
TargetStageEffectiveExecutionModes "1| "
TargetStageRuntimeExecutionModes "1| "
LinkIsSingleOperatorLookup "False| "
LinkIsSortSequential "False| "
LinkSortMode "0| "
LinkPartColMode "1| "
LinkSourcePinIDs "V0S0P1| "
END DSRECORD
BEGIN DSRECORD
Identifier "V0S0"
OLEType "CCustomStage"
Readonly "0"
Name "Sequential_File_0"
NextID "2"
OutputPins "V0S0P1"
StageType "PxSequentialFile"
AllowColumnMapping "0"
NextRecordID "0"
END DSRECORD
BEGIN DSRECORD
Identifier "V0S0P1"
OLEType "CCustomOutput"
Readonly "0"
Name "DSLink2"
Partner "V0S3|V0S3P1"
Properties "CCustomProperty"
BEGIN DSSUBRECORD
Name "schema"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "selection"
Value "file"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "keepPartitions"
Value " "
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "rejects"
Value "continue"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "reportProgress"
Value "yes"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "firstLineColumnNames"
Value " "
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "file "
Value "\(2)\(2)0\(1)\(3)file \(2)/home/nbkmakl/sample_test1.dat\(2)0"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "missingFile"
Value " "
END DSSUBRECORD
MetaBag "CMetaProperty"
BEGIN DSSUBRECORD
Owner "APT"
Name "SchemaFormat"
Value "final_delim=end, delim=',', quote=double"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "DiskWriteInc"
Value "1048576"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "BufFreeRun"
Value "50"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "MaxMemBufSize"
Value "3145728"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "QueueUpperSize"
Value "0"
END DSSUBRECORD
LeftTextPos "232"
TopTextPos "208"
LinkMinimised "0"
END DSRECORD
BEGIN DSRECORD
Identifier "V0S3"
OLEType "CCustomStage"
Readonly "0"
Name "Sequential_File_3"
NextID "2"
InputPins "V0S3P1"
StageType "PxSequentialFile"
AllowColumnMapping "0"
NextRecordID "0"
END DSRECORD
BEGIN DSRECORD
Identifier "V0S3P1"
OLEType "CCustomInput"
Readonly "0"
Name "DSLink2"
Partner "V0S0|V0S0P1"
LinkType "1"
ConditionNotMet "fail"
LookupFail "fail"
Properties "CCustomProperty"
BEGIN DSSUBRECORD
Name "schema"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "file"
Value "\(2)\(2)0\(1)\(3)file\(2)/home/nbkmakl/sample.test\(2)0"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "append\\overwrite"
Value "overwrite"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "nocleanup"
Value " "
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "rejects"
Value "continue"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "firstLineColumnNames"
Value " "
END DSSUBRECORD
MetaBag "CMetaProperty"
BEGIN DSSUBRECORD
Owner "APT"
Name "RTColumnProp"
Value "1"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "SchemaFormat"
Value "final_delim=end, delim=',', quote=double"
END DSSUBRECORD
TransactionSize "0"
TXNBehaviour "0"
EnableTxGroup "0"
LinkMinimised "0"
END DSRECORD
END DSJOB
Code: Select all
BEGIN HEADER
CharacterSet "CP1252"
ExportingTool "IBM InfoSphere DataStage Export"
ToolVersion "8"
ServerName "DSENGINE.DIF.HEW.US.ML.COM"
ToolInstanceID "MIDAS"
MDISVersion "1.0"
Date "2015-03-16"
Time "21.30.57"
ServerVersion "8.7"
END HEADER
BEGIN DSJOB
Identifier "Sample_TEST_8"
DateModified "2015-03-16"
TimeModified "21.28.50"
BEGIN DSRECORD
Identifier "ROOT"
OLEType "CJobDefn"
Readonly "0"
Name "Sample_TEST_8"
NextID "1"
Container "V0"
JobVersion "56.0.0"
ControlAfterSubr "0"
Parameters "CParameters"
BEGIN DSSUBRECORD
Name "$APT_GRID_COMPUTENODES"
Prompt "COMPUTENODES - Number of Compute Nodes"
Default "2"
ParamType "0"
ParamLength "0"
ParamScale "0"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "$APT_GRID_CONFIG"
Prompt "APT_GRID_CONFIG - Use this configuration template file vs. default grid_config.apt file"
ParamType "0"
ParamLength "0"
ParamScale "0"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "$APT_GRID_PARTITIONS"
Prompt "PARTITIONS - Number of partitions per Node (compute)"
Default "1"
ParamType "0"
ParamLength "0"
ParamScale "0"
END DSSUBRECORD
MetaBag "CMetaProperty"
BEGIN DSSUBRECORD
Owner "APT"
Name "AdvancedRuntimeOptions"
Value "#DSProjectARTOptions#"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "TraceMode"
Value "0"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "TraceSeq"
Value "1"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "TraceRecords"
Value "100"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "TraceSkip"
Value "0"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "TracePeriod"
Value "1"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "RecordJobPerformanceData"
Value "0"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "IdentList"
Value "Sequential_File_0|Sequential_File_3"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "ClientCodePage"
Value "1252"
END DSSUBRECORD
NULLIndicatorPosition "0"
OrchestrateCode =+=+=+=
#################################################################
#### STAGE: Sequential_File_0
## Operator
import
## Operator options
-schema record
{final_delim=end, delim=',', quote=double}
()
-rejects continue
-reportProgress yes
-file '/home/nbkmakl/sample_test1.dat'
## General options
[ident('Sequential_File_0'); jobmon_ident('Sequential_File_0')]
## Outputs
0> [] 'Sequential_File_0:DSLink2.v'
;
#################################################################
#### STAGE: Sequential_File_3
## Operator
export
## Operator options
-schema record
{final_delim=end, delim=',', quote=double}
()
-file '/home/nbkmakl/sample.test'
-overwrite
-rejects continue
## General options
[ident('Sequential_File_3'); jobmon_ident('Sequential_File_3')]
## Inputs
0< [] 'Sequential_File_0:DSLink2.v'
;
=+=+=+=
IsTemplate "0"
NLSLocale ",,,,"
JobType "3"
Category "\\test_j"
CenturyBreakYear "30"
NextAliasID "2"
ParameterFileDDName "DD00001"
ReservedWordCheck "1"
TransactionSize "0"
ValidationStatus "0"
Uploadable "0"
PgmCustomizationFlag "0"
JobReportFlag "0"
AllowMultipleInvocations "0"
Act2ActOverideDefaults "0"
Act2ActEnableRowBuffer "0"
Act2ActUseIPC "0"
Act2ActBufferSize "0"
Act2ActIPCTimeout "0"
ExpressionSemanticCheckFlag "0"
TraceOption "0"
EnableCacheSharing "0"
RuntimeColumnPropagation "1"
RelStagesInJobStatus "-1"
WebServiceEnabled "0"
MFProcessMetaData "0"
MFProcessMetaDataXMLFileExchangeMethod "0"
IMSProgType "0"
CopyLibPrefix "ARDT"
RecordPerformanceResults "0"
END DSRECORD
BEGIN DSRECORD
Identifier "V0"
OLEType "CContainerView"
Readonly "0"
Name "Job"
NextID "1"
IsTopLevel "0"
StageList "V0S0|V0S3"
StageXPos "120|384"
StageYPos "192|192"
StageTypes "CCustomStage|CCustomStage"
NextStageID "4"
SnapToGrid "1"
GridLines "0"
ZoomValue "100"
StageXSize "48|48"
StageYSize "48|48"
ContainerViewSizing "0000 0000 0429 0445 0000 0001 0000 0000"
StageNames "Sequential_File_0|Sequential_File_3"
StageTypeIDs "PxSequentialFile|PxSequentialFile"
LinkNames "DSLink2| "
LinkHasMetaDatas "False| "
LinkTypes "1| "
LinkNamePositionXs "232| "
LinkNamePositionYs "208| "
TargetStageIDs "V0S3| "
SourceStageEffectiveExecutionModes "1| "
SourceStageRuntimeExecutionModes "1| "
TargetStageEffectiveExecutionModes "1| "
TargetStageRuntimeExecutionModes "1| "
LinkIsSingleOperatorLookup "False| "
LinkIsSortSequential "False| "
LinkSortMode "0| "
LinkPartColMode "1| "
LinkSourcePinIDs "V0S0P1| "
END DSRECORD
BEGIN DSRECORD
Identifier "V0S0"
OLEType "CCustomStage"
Readonly "0"
Name "Sequential_File_0"
NextID "2"
OutputPins "V0S0P1"
StageType "PxSequentialFile"
AllowColumnMapping "0"
NextRecordID "0"
END DSRECORD
BEGIN DSRECORD
Identifier "V0S0P1"
OLEType "CCustomOutput"
Readonly "0"
Name "DSLink2"
Partner "V0S3|V0S3P1"
Properties "CCustomProperty"
BEGIN DSSUBRECORD
Name "schema"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "selection"
Value "file"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "keepPartitions"
Value " "
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "rejects"
Value "continue"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "reportProgress"
Value "yes"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "firstLineColumnNames"
Value " "
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "file "
Value "\(2)\(2)0\(1)\(3)file \(2)/home/nbkmakl/sample_test1.dat\(2)0"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "missingFile"
Value " "
END DSSUBRECORD
MetaBag "CMetaProperty"
BEGIN DSSUBRECORD
Owner "APT"
Name "SchemaFormat"
Value "final_delim=end, delim=',', quote=double"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "DiskWriteInc"
Value "1048576"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "BufFreeRun"
Value "50"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "MaxMemBufSize"
Value "3145728"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "QueueUpperSize"
Value "0"
END DSSUBRECORD
LeftTextPos "232"
TopTextPos "208"
LinkMinimised "0"
END DSRECORD
BEGIN DSRECORD
Identifier "V0S3"
OLEType "CCustomStage"
Readonly "0"
Name "Sequential_File_3"
NextID "2"
InputPins "V0S3P1"
StageType "PxSequentialFile"
AllowColumnMapping "0"
NextRecordID "0"
END DSRECORD
BEGIN DSRECORD
Identifier "V0S3P1"
OLEType "CCustomInput"
Readonly "0"
Name "DSLink2"
Partner "V0S0|V0S0P1"
LinkType "1"
ConditionNotMet "fail"
LookupFail "fail"
Properties "CCustomProperty"
BEGIN DSSUBRECORD
Name "schema"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "file"
Value "\(2)\(2)0\(1)\(3)file\(2)/home/nbkmakl/sample.test\(2)0"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "append\\overwrite"
Value "overwrite"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "nocleanup"
Value " "
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "rejects"
Value "continue"
END DSSUBRECORD
BEGIN DSSUBRECORD
Name "firstLineColumnNames"
Value " "
END DSSUBRECORD
MetaBag "CMetaProperty"
BEGIN DSSUBRECORD
Owner "APT"
Name "RTColumnProp"
Value "1"
END DSSUBRECORD
BEGIN DSSUBRECORD
Owner "APT"
Name "SchemaFormat"
Value "final_delim=end, delim=',', quote=double"
END DSSUBRECORD
TransactionSize "0"
TXNBehaviour "0"
EnableTxGroup "0"
LinkMinimised "0"
END DSRECORD
END DSJOB
Kiran Kumar
-
- Premium Member
- Posts: 47
- Joined: Tue Sep 13, 2005 4:28 am
-
- Participant
- Posts: 32
- Joined: Fri Nov 07, 2014 11:18 am
Re: Unable to add new parameters to a dsx
Try the same process but instead of the taking a standard dsx may be try with the XML option. I ll try and replicate the this here. WIll let you know what I find
POST - edit
So I did this experiment at my end. Simple job. Took the dsx , changed the job took the dsx (added an environment variable and a parameter set)
Now most differences I see are at the DSJOBEXEC section of the dsx. (And all those changes are for the environment variable.). In my case almost all the lines in that section has a reference of the padding character.
And same with the parameter Set as well, The DSEXECJOB section of the job had mentions of parameter Set.
And these are the changes which don't look straight forward like an initial declaration or something like that.
POST - edit
So I did this experiment at my end. Simple job. Took the dsx , changed the job took the dsx (added an environment variable and a parameter set)
Now most differences I see are at the DSJOBEXEC section of the dsx. (And all those changes are for the environment variable.). In my case almost all the lines in that section has a reference of the padding character.
And same with the parameter Set as well, The DSEXECJOB section of the job had mentions of parameter Set.
And these are the changes which don't look straight forward like an initial declaration or something like that.
that's wierd ?
-
- Premium Member
- Posts: 47
- Joined: Tue Sep 13, 2005 4:28 am
Re: Unable to add new parameters to a dsx
AshishDevassy wrote:Try the same process but instead of the taking a standard dsx may be try with the XML option. I ll try and replicate the this here. WIll let you know what I find
POST - edit
So I did this experiment at my end. Simple job. Took the dsx , changed the job took the dsx (added an environment variable and a parameter set)
Now most differences I see are at the DSJOBEXEC section of the dsx. (And all those changes are for the environment variable.). In my case almost all the lines in that section has a reference of the padding character.
And same with the parameter Set as well, The DSEXECJOB section of the job had mentions of parameter Set.
And these are the changes which don't look straight forward like an initial declaration or something like that.
Thanks for the info,what is the final conclusion, is it that can be achieved through DSX. will XML works?kiranh_1214 wrote:Team,
I have a requirement of addding three new parameters and annotations to a job.
I have taken the dsx of the job to my local machine.
I modified the annoation and saved the dsx and imported the DSX back. the change got reflected in the job.
Likewise i added three parameters under the cparameters in dsx and saved it.when i import the dsx the parallel job is showing an error as cdefn =class and root =" . then when i search for the job the parallel job is becoming into a server job.
Kiran Kumar
![Exclamation :!:](./images/smilies/icon_exclaim.gif)
(actually I'm going to leave it for awhile so you can see what I'm talking about, I'll fix it later. I get the impression too many people type something up and submit it without ever looking to see what the end result looks like or ever using the 'Preview' option to see what it is going to look like.)
As to your question, "it" can be achieved through either dsx or xml, use whatever you are more comfortable with. Understand the process that happens under the covers - when you ask for XML it first generates DSX and then converts it to XML. When you import XML, it first has to convert it to DSX and then import it. Me, I personally didn't like all those extra shenanigans (especially the increased import time) and stuck with DSX exports.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 32
- Joined: Fri Nov 07, 2014 11:18 am
@kiran_h
Yes it is doable , But the manual additions are not straight forward.
For Environment variables its more complicated and for parameter sets its less so.
For Parameter Sets you may just need to add a bunch of statements towards the declaration section of the DSX but for the ENvironment variable you will need to edit the existing statements in the DSJOBEXEC section. (And so the complexity would vary depending on how big your job is)
Yes it is doable , But the manual additions are not straight forward.
For Environment variables its more complicated and for parameter sets its less so.
For Parameter Sets you may just need to add a bunch of statements towards the declaration section of the DSX but for the ENvironment variable you will need to edit the existing statements in the DSJOBEXEC section. (And so the complexity would vary depending on how big your job is)
that's wierd ?
-
- Participant
- Posts: 32
- Joined: Fri Nov 07, 2014 11:18 am