DSXchange

Server jobs work fine in version 8.5 and 8.7. You may like to start switching to Connector technology for connections to data sources, and maybe organise your parameters using Parameter Sets.

Depending on what you need to do, you might investigate the Web Services Client stage. This encodes requests as SOAP mesasges and decodes responses from SOAP messages, using metadata defined for a web service operation in its WSDL.

Use a stage variable to extract the rightmost three characters, so you only need to do that calculation once. Maybe another two stage variables to evaluate equality with 'EOD' and 'SOD' respectively.

I agree. Your requirement was not well stated, but it appears that a Conditional lookup in the Lookup stage will achieve what you require.

For all practical purposes in DataStage, Decimal and Numeric can be regarded as synonyms.

In this case it was a simple PIC X(3). that was subject to the OCCURS.

Why not use a Routine activity as the first and last activity in the sequence? Otherwise create a simple job containing to interrogate the information for the sequence?

IMAM badly needs a command line interface for creating the import area and performing the initial import.

The structure of those rule set files has not changed between versions.

You can also run that query from the Command window in the Administrator. Search DSXchange for query examples involving DS_AUDIT table or UNNEST DS_AUDIT ON MODS text.

And, more specifically, if you don't have its parent directory in your PATH, then the answer is NO. (You will only be able to execute the command from its parent directory, and you never want to do that.)

echo $PATH to see the value of PATH.

Research what the other possibilities are in the CFF stage, other than "flatten".

Not in a position to test that at the moment. Working on a Business Glossary/Information Analyzer/Metadata Workbench installation.

Since when has 09 been an octal number?

Why do you believe that DataStage is looking for octal numbers? In particular can you cite a manual reference?

iskapalli's main problem is a misplaced belief that Oracle functions can be used directly in DataStage.