DSXchange

Not by default. But you could create your precise requirement as a routine (calling DSSendMail) and invoke that from a Routine activity.

You can not. It's just how it works.

DSINCLUDE is upper case in the VOC file, and therefore you use the upper case variant in a $INCLUDE declaration.

As to DS_JOBOBJECTS.H, that is something that ag_ram incorporated; it does not exist (as Craig noted).

My punt would be DS_JOBS, because there should never be a job number 0.

Use Start Loop and End Loop activity in a job sequence, driven by the result of your query. Or create a server job that reads a file containing the result of the query and uses UtilityRunJob to run the file creation for each society processed. (A parallel job in this instance is a waste of resources.)

You can use Oconv(InLink.TheString, "MX0C") to convert all characters to hex-encoded equivalents.

Very urgent? In that case please sign up with your support provider for premium service, and learn the true cost of "urgent". DSXchange is an all-volunteer (unpaid) site, whose participants post as and when they can. A job sequence is a special case of a server job. Therefore there is no such thing...

You may find this thread informative.

How do you know that "the C++ compiler is properly installed" on the UNIX system (and that environment variables such as PATH and LD_LIBRARY_PATH properly refer to it)? Which particular C++ compiler is installed? What settings do you have for APT_COMPILER, APT_COMPILER_OPTIONS, APT_LINKER and APT_LI...

Are you sure it's a space, and not a newline? I suspect the latter, which will have been converted to a field mark (@FM). You need to remove whatever it is from the $CommandOutput activity variable, for example using Convert() or Trim() function.

Welcome aboard.

Have you read the pertinent Chapter in the manual? You need three jobs, one to create the state file (the stage has no links), one to initialize the state file (the stage has an input link), and one in which surrogate keys are delivered (the stage, if used, has an output link).

Good point, and I can see how you could believe that. However, from day one we've categorized based on job type. There is a good case to change the forum names.

Possibly, but you have not told us how you are initializing the key generator (state file?). This normally has to be done in a separate job.

NEVER kill a DataStage process. All you have to do in this case is to release the lock.