DSXchange

Use the Print option in Director. It has a Print to File option.

There is no specific source code control system (SCCS) for DataStage (after all, it uses a GUI, not source code). Some sites choose to use DataStage export files as the "source code" and park that into the SCCS in order to gain the check-out, check-in capability.

In Director you can set new defaults for the main controlling sequence on the other system(s). On the Job menu choose Set Defaults.

May we enquire what training you did? There is no reference to pointers in the standard training classes. Just curious.

OK, under those circumstances. Also, it seems to have changed in 7.5 with the new mechanism - in 7.0 you can only have a quoted string or a "job parameter" (something from upstream) and even then you have to type in the activity variable name!

Did the JCL actually get there? Was it both the compile JCL and the run JCL, or just one? The message suggests that the transfer has been switched (from active) to passive mode because a non-printable ASCII character has occurred in the JCL. Inspect the JCL that was generated and see whether you can...

Welcome aboard. :D

Check that you have write permission to the target directory (/usr).

Apparently there's a "$" sign in your input data. You can't apply arithmetic functions (like SUM) to non-numeric data.

In FTP (and Sequential File) stages you will only be able to see those rows that match the metadata (columns) on the link. A Rejects link will handle the others. You can define "missing columns" rules, or pre-process the file to strip the header and trailer record into separate streams.

mkapoor wrote:for deconcatenating the column into 48 columns

prior to pivoting

The "ipc" in "ipc_open()" is for "inter process communication". One player process (stage TO_XFM_DT_TM-Input, link TO_XFM_DT_TM on node #0 (the first node defined in your configuration file) is reporting that the file it needs to use can not be found. Does the Lookup File Set exist on the second sys...

Mappings that you produced in PowerCenter are, in general, not suitable for use with DataStage at all. The two products take a different approach to the design process. The usual approach is to create DataStage routines or transforms that perform the same tasks as the mappings. Metabrokers are only ...

If "it is real urgent" then your premium support contract with your support provider will gain you a "real fast" response. This is an all-volunteer site; we don't do "urgent".

Welcome aboard. :D

Lots of folks can, indeed lots of folks already have (try search).

And please try to post on the correct forum - this one is for feedback about the site/forum.

In theory at least the Column Generator stage should be more efficient than a Transformer stage, (a) because it does so much less work and (b) because it doesn't need to be compiled into a separate C++ function.