DSXchange

There is, to my mind, a better table at the end of Chapter 2 in the Server Job Developer's Guide (version 6.x and later), in which the number of key characters considered is also given.

Each server job and job sequences executes DSD.RUN. Thus, "DSD.RUN" is a better string on which to filter the output of such commands as PORT.STATUS or ps -ef. It is more accurate than "phantom", because phantom (background) processes also execute Transformer stages, via the DSD.StageRun routine.

Trailing spaces may be valid data. NULL would be OK in my routine, because Len(@NULL) is zero (go on, try it). However, my routine would return "" in that case, which may not be the desired result. If you're going to write a completely bullet-proof routine, you need also to check that the incoming ...

Just a thought: does resetting the base job clear these entries?

Clearing the Status file certainly would, but is too extreme a "solution".

You may need to refresh the Director view.

Departitioning might also be the "fan in" needed by some stages, such as the Sequential File stage, where only one writer is permitted. This is still configured - and can be made visible - as a link property.

Does the after-job routine attempt to do anything with the target files of the job?

Have you made an entry in the uvodbc.config file (in the project directory) of the following form?
The space either side of "=" is mandatory.

Most of the places I work that reply makes you a network expert! :D

All of that having been said - necessarily - the problem is not anything to do with hashed files. Error code 39202 relates to a failure to connect. It decodes (from the InterCall Developer's Guide from IBM) as "slave failed to give server the Go Ahead message", which is an internal coordination-betw...

NO! Never set 64BIT_FILES on. This means that EVERY hashed file on your system has 64-bit pointers. You neither need nor want this. I summon Phil, the Prince of Insufficient Light, to condemn the provider of that advice to Heck. Step 1 : do you really need all those columns and rows in the hashed f...

Get more sleep.

Here are two ways. Field_Name_A Matches "1N0N" This returns true if Field_Name_A consists of one numeric character followed by zero or more numeric characters. To collect signed integers extend the expression to Field_Name_A Matches "1N0N":@VM:"'-'1N0N" Field_Name_A = I...

Welcome aboard! Long way from Brisbane! About the only way to strip all non-printing characters is to create a Routine that processes each character. Oconv with "MCA", "MC/A", "MCN", "MC/N" and "MCP" are probably too specific for your needs. FUNCTION RemoveNonPrintingCharacters(TheString) An...

Job Sequences are not parallel jobs. The only possible way to send email from a parallel job would be to use any method for executing an operating system command. You really don't want to do this; it will slow your data processing immensely. Instead, run your parallel jobs from a job sequence (or fr...

You would think that leftmost variance would suit GENERAL best while rightmost variance (like an odometer) would suit SEQ.NUM best. It turns out that the hashing algorithm for dynamic hashed files performs a bit-rotate operation after each character processed, to achieve better "randomness", so it d...