DSXchange

Note that I did not suggest using a server job.

Create a sequence to run them all, then the client has only the one "job" with which to interact.

Not really. The trailing & still means "create a background process" in ksh, and the nohup simply specifies not to wait for it to finish. What exactly do you mean by "hangs"? The mkdbfile command works perfectly well in a background process in my experience, provided its synt...

bob7027 wrote:bash file is executing perfectly but the expected output is wrong

You're executing a bash script using ExecDOS ?

Or do you mean a batch file?

Still waiting to see what you've put in the Input Value field.

Keep in mind that Connectors typically install on the Engine tier while bridges install on the Client tier. If these are different machines you will definitely need separate Metadata Interchange Servers defined - one for bridges and one for Connectors.

Keep in mind that Connectors typically install on the Engine tier while bridges install on the Client tier. If these are different machines you will definitely need separate Metadata Interchange Servers defined - one for bridges and one for Connectors.

Nagaraj has it wrong. A Data Set consists only of the descriptor file and its associated segment (data) files. There are no "control" files (this term is sometimes used to refer to the descriptor file). There are no separate header files. Each segment (data) file has its own internal head...

Try preceding the mkdbfile command with nohup so that its controller can return straight away.

Test this in the Administrator client command window, preceded by SH -c.

In general what you have outline is not possible, for the reasons Andy gave.

But you could create protected projects - non-editable copies of your primary base project.

IMAM, as far as I can determine, is the import tool of choice where a metabroker or bridge is required. It supersedes Import/Export Manager in this role (though I still prefer the IEM command line for some things). Importing table definitions does not require a metabroker or bridge. It uses the Conn...

Show us the method you are using in DataStage. For example are you using a before-job subroutine to invoke ExecDOS? If so, what are you putting into the Input Value field?

Open the Data Set Management tool in DataStage Designer. Open any of your valid Data Sets. The tool will show you the contents of the descriptor file (the *.ds file). It also shows the location and names of the segment files on each node (as you select each node) that contain the data. Nagaraj has i...

Welcome aboard.

DataStage is really set up to stream data through it. Recursion and going back multiple levels is not really supported, without multiple passes over the data.

The first argument of date_from_string must be the name of a column on the input link.

Not a constant.

Not a job parameter.

Not anything else.

Normally one imports table definitions through a tool such as DataStage Designer or Information Analyzer.