DSXchange

ExecTCL is a before/after subroutine. As such it has no syntax per se. You load it up in the properties of any job or active stage, and place the command to be executed in the Input Value field. If the command succeeds, the job keeps going. If the command fails, the job stops. Source code for ExecTC...

If that's the intended purpose then don't convert to Char(10). Instead convert to some delimiter character that does not appear in your data, for example "|" (as suggested) or "~" or "\".

DataStage is simply another client application as far as Informix is concerned. Therefore, it requires exactly the same configuration as any other client. In particular the relevant environment variables (including PATH, LD_LIBRARY_PATH as well as the Informix ones) must be set. For DataStage on UNI...

Strange. I searched for "status" and found lots of posts. Searching for "job status" was tighter, but still found quite a few posts.

You would also need some measure of clarity (lack of obfuscation). For example, does the job have "hidden" ingredients, such as before/after subroutines, about which the future maintainers are not warned with, say, annotations on the design canvas? Containers can add to or detract from clarity; so q...

If you don't know, you're using 32-bit hashed files.

You would have had to create 64-bit hashed files explicitly to have them, or have the configuration parameter 64BIT_FILES set (not recommended).

Depending on the O/S you may hit a limit where the number of directories in a directory is reached. On Solaris this seems to be 32767. Remember that each dynamic hashed file is a directory and that each job typically requires four new hashed files, and that suggest a limit of about 8000 jobs on that...

Doesn't Search work in your browser?

Check in on-line help for functions with names like DSGet... which interrogate the system for information.

Check out Kim's and Chuck's web sites for tools that already exist - why reinvent the wheel?

Your job that does it can emplace a flag, for example a record in a hashed file (SDKSequences would do). This record has a constant for its key, and the date as its non-key field. Look this up and proceed only if it's date is earlier than today's date.

Not only that, but DataStage still supports (and uses, internally, mainly 'coz Glenn Herbert lervs 'em) PROCs. These are derivative from the "Pick O/S". 0001: PQ 0002: IF %2 = "DICT" GOSUB 888 0003: IF %2 # "DICT" GOSUB 999 0004: C - Read first item 0005: F-READ 1 %%20 0006: MV &...

There is one RL lock on a non-existent record called project.&!DSADMIN!& for each connected client session. There is also one RU lock on that client's record in DS_LICENSE for each connected client. Please confirm that you have indeed released MAXRLOCK (use the smat -t command). Can you also...

Click on the Help button on the Format tab. It will also show you how to do it using the hexadecimal representation.

So you have no 01 level item at all?

However, it's grumbling about the UPDATE statement. Wrong number of parameters suggests that, while you have two columns in your WHERE clause, there are more than two - or only one - identified as Key in your metadata (the columns grid). Or, perhaps, that either START_DT or arr_id_acct are not colum...

No. "0A" will not be interpreted as a hex number; each @AM will be converted to "0" (the first character of the second argument. What you need is Convert(@AM,Char(10),Ans) or, if svLF is a stage variable initialized to Char(10) Convert(@AM,svLF,Ans) which means you only evalu...