DSXchange

You can run multiple instances simultaneously, in exactly the same way that you can run independent jobs simultaneously. The only restrictions are likely to be in the operating system; for example if the jobs (or instances) write to the same text file, only one at a time is permitted. You just need ...

The other possibility is that there is a Routine called IsBlank in the old project that has not been moved to the new project.

Welcome aboard! :D If this is something you're going to use often, you might like to create a Routine that is your own IsDate function. FUNCTION IsDate(Arg1) * Tests whether Arg1 is a valid date TheDate = Arg1 * Test for a YMD date Temp1 = Iconv(TheDate, "DYMD") Status1 = S...

1. A UNIX user can belong to any number of groups. 2. There will be no conflict of permissions in DataStage. If the user is neither the owner nor in the group with which a project protected, and "other" does not have write permission to the project, then that user will not be able to make changes to...

I haven't tried this but you might like to.

Set the initial value in the first UserVariable activity, run the first job, then set the new value in the second UserVariable activity.

Let us know if it does what you want.

The typeless variables in DataStage have an initial state of unassigned . This can (should?) be tested in routines using either the Assigned() or Unassigned() functions. If you use the stage variable properties grid to initialize a stage variable, the result of that expression is used to change the ...

After invoking the Connect method you should check the Error property of the session object, and clear it of any informational message. Otherwise you have a dirty handle, and almost nothing else will work properly (since most other objects are derived from the session object).

Only if you're attached to project directory and uvsh can be found via your PATH.

And no guarantees into the future - Hawk release promises an open, common repository.

And what about the requirement for display lengths?

Is your ini shell script invoked from $DSHOME/dsenv? This is where DataStage processes get their environment variables from.

That's the one. Create a new server job. Fill in the short and long description fields. Paste the code into the Job Control tab in Job Properties. Create the ten job parameters mentioned in the code. Put an annotation in the canvas to warn future developers that this job consists solely of job contr...

There was something posted (officially) recently on ADN about a memory problem in clients in 7.5 being fixed in 7.5A. Could be worth checking that post.

There's no easy way.

There's also no way that doesn't rely on undocumented information about the structure of repository tables, which is subject to change (and likely to change in the next release). And even then your shell script would need to invoke the DataStage (~ UniVerse) query engine.

There was a routine posted some time ago for dumping a table definition in CSV, XML or IMF format. Search for it. (IMF format is used by QualityStage.)

No idea. The character encoding should make no difference at all. Make sure (by inspection) that you don't have an extra empty line at the end of the UCS-2 file.

I have seen that behaviour before (in version 7.1r1) with the regular Annotation stage also. There wasn't anything obvious to cause it, and there was a sense of urgency to get the developer developing again, so we re-installed the client software. So I can't suggest what may have caused it, but that...