DSXchange

Thanks for sharing that.

Were the output mappings left in place in the Standardize stage? (I believe they should have been.)

SIGKILL usually means that someone has killed one or more of the job processes on the engine machine, or perhaps that a Stop request has been issued from dsjob or Designer or Director client.

The second argument of DSAttachJob() specifies error handling. If you use DSJ.ERRNONE you have to handle error conditions yourself. $INCLUDE DSINCLUDE JOBCONTROL.H hJob = DSAttachJob(JobName, DSJ.ERRNONE) CheckName = DSGetJobInfo(hJob, DSJ.JOBNAME) If CheckName = DSJE.BADHANDLE Then Ans = @NULL ErrM...

Use the Administrator client. Check each project's properties on the Logging tab. Make sure that "Enable Operational Repository logging" is NOT checked. (If you are on an earlier version than 8.7, you will need to check in each project's DSParams file for RTLogging and ORLogging settings. ...

Isn't "as soon as the first warning is generated" the same, but more efficient, than "if any warnings are thrown"? If you want to process all rows then abort if any warnings are thrown, you can implement an after-job subroutine to check the interim status (for example if that is ...

Yes and no. It is not the File Set itself that imposes this limit; it's the underlying file sytem. Each of the segment files that make up the File Set can only have one writer at a time. The same is true for Data Sets, Sequential Files, and all other structures that rely directly upon files in the f...

Have you read the pertinent chapters in the Parallel Job Developer's Guide ? Data Sets and File Sets are both parallel mechanisms for data storage. They each have file(s) for each node when being written to. Data Sets store data in DataStage internal format; primarily this means that numeric data ar...

Are you storing your job logs in XMETA? These will consume a lot of space. That space can be cleared by purging the logs.

Best practice is not to store job logs in XMETA but, rather, to store them locally in the DataStage project.

Software can only be downloaded from IBM Passport Advantage site. (That means that you have purchased a licence, and your copy will be legal.)

Only DataStage clients can be installed on Windows 7.

The engine, services and repository tiers can not be installed on Windows 7.

Nothing is ever deleted automatically from XMETA; rather things are marked as deleted.

There are some cleanup scripts; check with your support provider to get the script names for Oracle.

Can you be more specific about what "not giving proper output" means?

Welcome aboard. If you are using Char data type, then DataStage will pad these to the designated length using the character specified in APT_STRING_PADCHAR, the default value of which is 0x00. If you want it to pad Char data types with space, change the value of APT_STRING_PADCHAR to space, or to 0x...

Are both jobs using the same configuration file ($APT_CONFIG_FILE)?

And, if you believe you have a supported C++ compiler installed, have you set the four compiler-related environment variables correctly?

• APT_COMPILER
  
  APT_COMPILEOPT
  
  APT_LINKER
  
  APT_LINKEROPT

What does DB2 error code SQL0969N mean?