DSXchange

I would like to email a file attachment only if the number of rows is greater than zero. If someone has done this with Version 7 I would greatly appreciate to know how. Look in the Routines (from DS Manager), possibly under the Utility or SDK section. There may be an example there (called something...

You can remove the uncertainty by using the Expression Editor to build your expressions ... Unfortunately that is not correct. Using the expression editor will not yield correct results. Using the Expression Editor with the GetEnvironment(%envvar%) function, then letting it substitute an JobParamet...

We had a couple surprising experiences while testing the upgrade to 7.5.1a (from version 6.x). Both were explained as changes made by an engineer without a spec to make the change. I recommend opening and issue with IBM/Ascential to let them determine the root cause. Our experiences: 1) Comments wer...

I would suspect that when you changed the DSN, the underlying database table is defined differently than the one that ran successfully. Scrutinize the actual table definitions (and get the current definitions from the database itself, not from the DDL you "think" was used to create them).

(I realize this is more than a year later!)

On the job that experienced the error, where did the error occur (for instance, during a "view data"?)

What stage were you in, and what database or file type were you referencing?

We are running 7.5.1 on AIX.

To get DSGetLinkMetaData to work, we had to use the CALL format, and pass 4 arguments (contrary to the docs or the function header):

1) A name to represent the dynamic result array
2) Job name
3) Stage name
4) Link name

DSGetLinkMetaData is referenced in the Server Job Developer's Guide, although the documentation is extremely weak!

Like you, you would like to think that if a vendor is going to build an interface layer on a technology, that they would make the effort to do the human factors for all levels of users and mask complexities. The 2.0 pack works well, but as pointed out there are some "nuances". Human Factor...

As an addendum to dgreco's post, it just so happens we are in the process of upgrading to 7.5.1, so we have both 6.0r3 and 7.5.1 installed. 7.5.1 supports schemas (but not DTDs I think), just the reverse of 6.0. We were able to import the schema into 7.5.1, export the table definition, then import t...

You should be able to kill the specific process. Suppose your job name is: mySleepJob Issue the command: ps -ef | grep mySleepJob (or any portion of the string) If the job is actually running, you should see the process id (on the left) and the parent's process id (DataStage engine probably) on the ...

Have you tried using the new Environment Variables feature of 7.5? Although this may not match the "intended" use, you define them in the Project, include them as "Job Parameters", then you can access and set them in your logic (such as a Derivation). Something to try to see if i...

Gee...DataStage as "middleware"....what a concept! If it only worked with "older" middleware, like MQSeries...Oh wait, it does! As an architect for a corporation, some questions you should always consider with any technology which has proprietary languages (DataStage, bi tools, c...