DSXchange

They also exist in on-line help. Open the Index and type in DSG and you'll be right where you need to be.

No and yes. ProfileStage works quite happily with DB2 as the PSDB. It's installing the PSDB on Oracle on Windows 2003 Server where we have the problem. We recreated the problem exactly with a new copy of the software today. This information, complete with screen shots, has been sent to the support p...

Make sure that there's an entry for the DataStage RPC daemon (using port number 31538) in the /etc/services file. Make sure that any DataStage user, including interactive users on the server, have run the $DSHOME/dsenv script. Omit can only be used if DataStage server is running on Windows platform....

Welcome aboard. :D You use encrypted job parameters in exactly the same way as any other job parameter types. To supply the default value double-click in the cell which opens an editor in which you have to enter the encrypted value twice, identically. To make reference to the job parameter in a fiel...

I'm sure there's a property for this, but can't recall its name. Search the forum - you'll probably find it.

Beyond that, because of a bug in the DB2 Enterprise stage, you can not use it with DB2 Connect to access tables on mainframe or AS/400 systems; you must use DB2 API stage.

I wonder if the certification exam requires you to be aware of bugs.

Transformer stages can perform both pieces of functionality. Depending on how they're combined (fixed width) you may be able to use a Modify stage to separate them later.

ODBC is limited to 400 columns and a row length of 16KB by default. These limits can be changed by setting MAXFETCHCOLS and MAXFETCHBUFF respectively in the uvodbc.config file. There is no documented limit for the Sequential File import, other than the tedium of checking that each column definition ...

ODBC is limited to 400 columns and a row length of 16KB by default. These limits can be changed by setting MAXFETCHCOLS and MAXFETCHBUFF respectively in the uvodbc.config file. There is no documented limit for the Sequential File import, other than the tedium of checking that each column definition ...

The operating system will not permit multiple writers to a Sequential File.

Therefore the parallel Sequential File mandatorily executes in sequential mode and imposes a Collector on its input link.

This can not work in a parallel job, where a CHAR must contain the correct number of characters.

Why not test your theory? Make $APT_CONFIG_FILE a job parameter, and supply a legal non-default value through a -param option on your dsjob command line. Look in the "Job started" event or the configuration file event in the job log to determine what parameter value was actually used.

This afternoon a patch is arriving. It's apparently related to the Oracle installation - we could create a DB2 PSDB quite happily. Will post again when results to hand. Vendor claims it was successful at their place.

Let me be the first to second that!

Sequential File stage which you then FTP to Windows and initiate the bulk load into SQL Server.