DSXchange

Universe is not written in BASIC but it does have a BASIC compiler. DataStage routines use the same syntax as Universe BASIC. You can run jobs from TCL. You can get a list of commands with LISTV or HELP at TCL. You can get help on BASIC with HELP BASIC. There is also HELP SQL for help on Universe SQL.

It works.

Do a search. This has been covered a lot. Basically the VOC is the system table for Universe. Universe was the basis for the DataStage engine. You talk to this database through the uvsh or dssh called the Universe shell or DataStage shell. If you telnet into a DataStage server on Windows the n you s...

I wish there was an exception handler for unhandled results. So a warning without a link will not just stop the sequence.

I wish, I wish, I wish.

If you say it three times does it come true?

I looked around and it appears APM.VERSION seems to be the file.

LIST DICT APM.VERSION

To show you all the fields available.

Do a search. This has happened to others.

Run sysdef and show just the kernel parameters on the last few lines. It looks like MFILES may need to increase. The %user says what you are doing is not very effective. The 100% cpu says you are cpu bound and not IO bound but most DataStage processes are heavy IO. How long have these processes been...

In the SDK included with DataStage there is a function called KeyMgtGetNextValue. It updates a hash file called SDKSequences. You need to put the current max surrogate key in this hash file. Most use a job that has a parameter for table and key name. select max(#KeyName#) from #TableName#; This is o...

Common or Named Common only exist across a single connection to Universe or the Engine. Each job has its own connection. I would use hash files or sequential files. Create a hash file to store each section and the result. Maybe clear this file at the begining. If you have known keys to this like Sec...

You may found a bug. Report it to ASCL.

It looks like you just do a chmod command and never execute the command. Call DSExecute("UNIX", 'chmod +x' :"/apps/Ascential/Projects/TIP/ExecFTPScript.sh": Cmd,output,SystemReturnCode) Even in this I think you need a space between +x and the path. I think Tony's solution...

They are on version 6. Wait to version 7 to switch to sequences. I agree with the DBA part.

I think our Designer problem is a Windows 2000 issue. The memory leak is a server side problem. I think a lot of issues are going away except for these 2. If you use XP and have no issues with 7.5.1 or 2000 and you do then please post. The memory leak kicks in on about 2 million rows. We had this in...

The Designer seems to be unstable. If you pull up more than one Designer or too many jobs then it will error out and disappear. It does not leave jobs locked though. That helps. Also we cannot copy parts of a sequence in the Designer either in the same job or to another sequence. The server seems to...

It probably thinks you are trying to use a parameter name. The other issue is maybe ODBC cannot create these types of temp tables. Just a guess.