DSXchange

Great! Thanks to both of you for the quick response!

OK - My question is actually about the maximum length of the value that may be stored in a variable.

Does this mean that if I compare two different stage variables that are 40 characters long, only the first 32 characters will actually be used in the comparison?

A couple of simple questions...

Is there a maximum length for stage variables? How about variables used within routines?

Thanks!

Peter

I've written a routine that reads data from a file containing server/project/job names and accepts login information as parameters. The routine then executes the DSExport command using this information. If the user has incorrectly specified these parameters or job names, the routine hangs. I'm not c...

Is it as simple as concatenating multiple dsx files into one, or is it more complex than that?

This command seems to work well for what I'm trying to accomplish. I do, however, have one more question...

Is there any way I can specify more than one job to be exported using this command? Ideally, I'd like to specify a few jobs to be exported into a single dsx file.

Thanks again,

Peter

Glad to hear it! Thanks for the quick response.

I've created a job that uses DSJobStartDate to retrieve a related record from a database table and populate a hash file. The job flow is as follows: DB Referential Lookup | Transformer1 -->Transformer2-->HashFile In order to accomplish this, I've created the job such that Transformer1 does not have ...

Although the dscmdexport command provides a means to export an entire project, I would like to selectively export components. Is there a facility within DataStage that will allow me to do this without using the GUI found in Manager?

Thanks!

Peter

In our development environment, we're finding that some developers are occassionally unit testing jobs in which they've forgotten to specify a filename for sequential files. As a result, sequential files are automatically assigned their inbound linknames and placed in the project directory. Although...

So...is all metadata (i.e. data type, length etc.) except for the key column indicator ignored so far as the internal processing and data storage are concerned?

Thanks for the responses!

Cheers,

Peter

Sorry to keep this thread going, but now you've got me interested! If each row of the hash file is stored as one contiguous string, then how are the key fields identified and internally stored?

From the perspective of the processing logic and end results, is there any downside to the way it's defined? (I'm trying to determine how urgently a fix needs to be implemented...)