DSXchange

The output from the cat command (I presume it's lower case, despite what you posted) contains line terminator characters. These are mapped by DataStage into field marks (@FM) so that a single string can be returned. The Field() function offered above removes the first line from the command output. P...

"Record not found" is a problem with your logic - you are not searching for the same key values that you wrote to the hashed file. Describe fully the job that writes data from Sybase into the hashed file. What is the key column name, and what values do you assign to it? What is the non-key column na...

The Trans() function is intrinsic to the DataStage BASIC language - you will find it in the DataStage BASIC manual. To use it you will need a VOC pointer to the hashed file - search the forum for SETFILE.

My error. It doesn't work like that - you need to parse the values into separate columns for the Pivot stage to work. However, the technique outlined above for leveraging the "multi-valued field" technology will work - all you have to do is to change the internal delimiters to @VM before writing the...

When you define environment variables in the Administrator client they are stored on the server in a file called DSParams in the project directory. DSParams is a text file and can be edited. But, of course, each environment variable appears only once, so you may as well edit them from the Administra...

What did you try? The short answer is that there's nothing provided out of the box. Easiest for an inexperienced user is to create the table in Informix, then to import it into DataStage from there. Needless to say it can be done, but requires detailed knowledge of the Repository structures. A table...

Tell us ALL the stages in your job design (draw us a picture), and at precisely what point in the job design that this error occurs.

One which will is

You don't need to. You tell the Pivot stage what the internal delimiter is. It generates a sufficient number of rows. Read the Pivot.pdf manual.

Not easily. The output from the Change Capture stage is intended to be used by the Change Apply stage. It would require further modification to be able to be used by other stages. You would also need to ensure that you do not introduce locking conflicts in that table.

Use these system variables (and @VM and @SM) wherever you like, but primarily in dynamic arrays. It is often useful to convert delimited strings into dynamic arrays so that you have more tools with which to process them.

Three jobs in a job sequence. Job1 executes query A and has two triggers to Job2 (which executes query B) and to Job3 (which executes query C).

If you import the data rows as single strings (VarChar) the delimiter and quote characters are irrelevant. Each should be set to none.

Create a job the effects the insert, and run that job within the batch.

That's exactly what the Pivot stage does.