You won't need a routine. BitTest is an intrinsic function. What you don't need is the "DSLink23.bit2=". Instead, you define an output column called Bit2 on the output link DSLink23, and the derivation for that column is BitTest(DSLink22.MEXSTAT3,2) Note that bits are counted from right to l...
Does the second Transformer stage have a reference input that returns multiple rows? Are there embedded end-of-line characters in, or being introduced into, your data? If not, how are you generating duplicate rows? Can you please describe the constraints and output derivations used in both Transform...
Provided you disable write cache, and set the read cache to "disabled, lock for updates", Craig's solution will work. The hashed file stage is not suited to what you are trying to do. Because of the way a hashed file works, calculating the actual (physical) location of the record based on the key va...
Note that the Bit... functions expect to work on integer arguments.
Most bit masking does anyway, and most bit masks contain combinations of powers of 2. So it's OK.
The reason is one of synchronization.
There is no way that DataStage could guarantee that you were processing the same input row when the links are coming out of different Transformers, so it simply prohibits grouping of those rows into a single transaction. It's for your own safety, really.
You may have the names of the clients confused, or I may have misunderstood your meaning. The Director client IS read-only.
Do you mean that they can't be permitted to start jobs, only to view log files?
Enjoy the class. I'm sure you'll get great benefit from it.
Here's an after-stage subroutine I baked earlier. It is passed the file pathname via the Input Value field - a job parameter reference can be used there. The purpose of this was to add the date between the base part of the file name and its suffix. SUBROUTINE RenameFileWithDate(InputArg, ErrorCo...
In version 4.x, DataStage was built on UniVerse, and shared the uniprcd which listened on port number 31438. At version 6.0, DataStage became separate from UniVerse. UniVerse's unirpcd listens still on port number 31438 but the dsrpcd listens on port number 31538. Therefore, connecting to UniVerse r...
Setting the row limit is one of those things that you can't do in a job sequence, as far as I have been able to determine, except by using the generated code as a prototype in the job control part of a server job. So how it might have picked up 2000 is a mystery. In Director, under Tools > Options (...
Resource files (for example DS_RESENU for English (United States), DS_RESJPN for Japanese) are the means by which messages to be emitted by DataStage are localized. Within DataStage every message is encoded, or tokenized, and the resource files are used to translate. They are hashed files within the...
Curious. "2046" does not appear in the source code for dsjob (see Appendix A, Server Job Developer's Guide ). The only 2046 in the resource table (DS_RESENU) carries the message "finished waiting for job". I suspect that the code has attempted to find the string associated with this (functionally eq...
When the job request is made someone requested a row limit of 2000. How was the job run request issued? If from Director, the Job Run Options dialog (where you enter parameter values) has a Limits tab. Defaults can be set from Tools > Options. If from a job control routine, or a batch, the function ...
use a comma-separated list of table names on the General tab load required column definitions on the Columns tab specify your join criteria on the Selection tab in the WHERE field (you don't need the word WHERE)