DSXchange

I think it is explained above. Write a job which reads the value in Oracle and stores it in a hash file. The key should be hard coded to some value like "MyDate". Use the above routine to return this value in an argument. This argument is available in a sequence after you call this routine in a rout...

You have a second job messed up RT_LOG29. Look for job number 29. You can restore this job from a backup or save it to a new name delete the old job name. Next it save it back as the original name. Either way will give this job a new job number and create a new log file. Unless you know how to repai...

ps -ef | grep phantom | grep MyJobName This should find the PID. You can do a kill PID. DO NOT DO A kill -9 PID. This is not the recommended way to stop a job but it should work. If you are killing PIDs attached to client processes then this is not good. If you kill a DataStage Designer process the...

I agree with Craig. Keep it simple unless some strong need changes it.

You could use MetaStage or Reporting Assistant. In the later look in DSColumns for ColumnName. Do a search it is a little tricky to get around the doc_tool.mdb default menu.

It is even more complicated to go against DS_JOBOBJECTS.

You probably ran out of dick space. RT_STATUS42 is associated with job number 42. You need to find out which job this is. SELECT * FROM DS_JOBS WHERE JOBNO = '42'; Run this SQL in the Administrator in the project that has the issue. This will tell you the bad job. You can import this job from a back...

Why not use the dsjob command?

There are other problems with multiple instance jobs which existed in version 6. I have not tried them in version 7 so I do not know if they still exist. You could not stop multiple instance jobs in BASIC. Someone said there is a patch to fix it but I would bet that these are related.

All of this is available in EtlStats and GenHtml. Both are free. EtlStats can get row counts and run times for a sequence and populate several tables so you can run reports to see if a job is slowing over time. A lot of this types of reports are included. The reports can be automated so they will em...

You have a messed up job. The job number is 328. At TCL type: select * from DS_JOBS where JOBNO = '328'; This will give the name of the job which is bad. Restore this job from a DSX backup. You may need to reindex. This should only happen when you run out of disk space or some other error which Data...

Craig

I looked at this and it does look too complicated to do in BASIC. I agree with Arnd. If you can have the Java stuff or a C program which can take standard input and output to standard output then

ExecSH "SH -c Base64 <FileIn "

Why wouldn't this work?

User defined is usually slower because it is more complicated otherwise why not use the SQL builder in DataStage.

How about this one

http://www.dsxchange.com/viewtopic.php?t=85364

Do a search on dynamic type 30 and kcbland as a poster. Should find some more.

EtlStats can be used in a batch way to get all job stats in one run. It uses dsjob -report Project Job XML as a source. You can do this at the command prompt and output it as text or XML. I am not sure what you want.

Craig

Send me the Java. I will see if it is doable.