Surrogate Key using sequence ?
Moderators: chulett, rschirm, roy
Thank you very much for responce
I passed
type /demo/....../filename.txt but still it is giving me following massage:
k_ren..JobControl (@Execute_Command_2): Command type /demo/....../filename.txt did not finish OK,
reply = '1'
AND
Message:
k_ren..JobControl (@Job_Activity_7): Controller problem: Error calling DSSetParam(Return), code=-4
[ParamValue/Limitvalue is not appropriate]
Thanks in advance
I passed
type /demo/....../filename.txt but still it is giving me following massage:
k_ren..JobControl (@Execute_Command_2): Command type /demo/....../filename.txt did not finish OK,
reply = '1'
AND
Message:
k_ren..JobControl (@Job_Activity_7): Controller problem: Error calling DSSetParam(Return), code=-4
[ParamValue/Limitvalue is not appropriate]
Thanks in advance
Who said anything about UNIX? It says 'command prompt', that's a generic expression for your operating system. I guess for Windows, working outside the GUI is becoming a lost art...
Click on 'Start', then 'Run...'. In the Run box put cmd and click OK, that will get you a command prompt, a.k.a a DOS prompt. Try it there. You are typing the actual full pathname to the file and not that version with six dots in the middle you keep posting, right?
This is not a valid pathname: /demo/....../filename.txt
Your second error message is a direct consequence of the first error. You didn't get a valid value back from your routine and the Sequence job was busted for passing in a value that was 'not appropriate'. Fix one and fix the other.
Click on 'Start', then 'Run...'. In the Run box put cmd and click OK, that will get you a command prompt, a.k.a a DOS prompt. Try it there. You are typing the actual full pathname to the file and not that version with six dots in the middle you keep posting, right?
This is not a valid pathname: /demo/....../filename.txt
Your second error message is a direct consequence of the first error. You didn't get a valid value back from your routine and the Sequence job was busted for passing in a value that was 'not appropriate'. Fix one and fix the other.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
What is the number in the file?
When you did 'type yourfilename' from the dos prompt, what did you see, did you see the contents of your file?
What have you set the parameter type in your second job? Is it set as string?
When you did 'type yourfilename' from the dos prompt, what did you see, did you see the contents of your file?
What have you set the parameter type in your second job? Is it set as string?
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
Inside the jobactivity, where your specifying $CommandOutput, provide the following
OR simply
Code: Select all
Field(Execute_Command_2.$CommandOutput,@FM,1)
Code: Select all
Execute_Command_2.$CommandOutput<1>
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
The output is in the form of a dynamic array with other contents in it. They are seperated by a field marker (@FM). We are only concerned with the contents of the first field. The first code in my previous post extracts everything before the first @FM. The second code extracts the contents of the first field in the dynammic array.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The output from the command contains line terminators. So that a single string can be returned infallibly, DataStage converts the line termintators to field marks (which can be represented by the @FM system variable).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.