DSXchange

You could capture it using an Execute Command stage and 'echo'. Or add it as a job parameter to the sequence and set it to $PROJDEF. Depends on what 'based on an input parameter' means.

How did you define the Environment Variables in your job? Did you set their default value to $PROJDEF? I would guess not if they are still using the "old" values.

Not mandatory as it will default to 'the current working directory' - i.e. your Project. Generally a Bad Idea, btw.

What do you believe the 'correct date and time format' is? Apparently not what Oracle believes it to be. If you are using generated SQL (as you should be IMHO) and a Timestamp datatype in the job (again, as you should be IMHO) then that format needs to be this: YYYY-MM-DD HH24:MI:SS If instead you a...

You should be able to find discussions on this searching for a common parameter handling problem when pulling these parameter values from a file. Do an exact search for "[ParamValue/Limitvalue is not appropriate]" to turn them up. Basically, the output from the OS command is returned in a dynamic ar...

manuel.gomez wrote:I set the routine activity trigger condition OK, but it seems routines dont return this status

'OK' means it checks for a zero, and since your routine returned a six...

During a DataStage 8 install I got a wizard prompt that asked if I wanted MQ and the stages showed up after the install. There might be a similar prompt on a DataStage 7 install There's no wizard and no MQ that comes with 7 that I've ever seen. What you do get, from what I recall, are the MQ stages...

Other than not creating the error in the first place, no.

Yah, it was a little further down than I thought it would be when I went hunting.

There's probably more than just a 6 there but only the 6 is visible. Suggest you take the value you cat from the file and do this to it before it gets to the Loop: Convert(@FM,"",YourValue) This will remove any Field Marks added by the command stage and should make the loop more ha...

First you need to determine how it got there, what the source was. This is typically caused by an NLS_LANG handling / conversion error during processing of the data.

First observation, you've got the Conv brothers backwards. IConv first, meaning innermost and then OConv second meaning outermost.

From your Start menu, navigate to 'Ascential DataStage / Online Manuals / DataStage Documentation'. From that pdf, scroll down and open the Server Job Developer's Guide for Server and the Parallel Job Developer's Guide for PX jobs. It's all there. I'd also suggest you check out the Designer Guide as...

The same way. The MKS Toolkit will have a 'cat' command, I assume, or you can use the DOS command 'type' which will accomplish the same thing.

I'm sure you could just export one of each and check with Mr Eyeball.

If you did, you'd find an entry of JobType with various numeric values:



I'll let you determine the rest, if you like.