DSXchange

Umm... are you sure that this code is working, even for the other logs? I would use the line TableName = "RT_LOG":FIELD(JobList, "|",2)<5> This uses the 5th field of the data, which contains the job number. The more I look at it, the more I think that the original code would neve...

The dynamic variable contains the key (job name) then the record data separated with a pipe, which is why that is being displayed - the "NRO" is the first data column and means that the job is not read only. So you can ignore that display, it indicates that the job is working correctly. Yo...

Couldn't that mean it was modified at 07:45 (somewhere), then written to a .dsx file and imported to the current project at 18:15?

I would not shell out to a database, but either write a routine in C++ and bind that to the job, or use a date dimension table.

The slow compile is usually due to Transform stages. Is that correct in your case, meaning do the jobs that compile quickly not have transform stages?

Yes, you can raise MFILES without fear in this case. The RT_STATUSnnn files are dynamic files (Type 30) and thus affected by the T30FILE parameter, and if you had reached this limit the error message would have been clear. Or it should be, what is your T30FILE setting? Is this problem always for one...

Can you just add a before-job UNIX call to "touch" all the files, this would create an empty file for the ones that don't exist and just update the timestamp on those that do exist.

Could the key contain a @FM or other nondisplayable character such as a 0x0?

The "J" conversion will give you the day number (1-366) in the year. Since there are various rules for computing Calendar Week you will have to choose the appropriate one and do the math from there. If you can choose, then just INT(ICONV(@DATE,'MDJ')/7) for CW 0 through 52.

True, using that method would release all jobs open in that session. The locks should show up in the LIST.READU command.

The suggested will work if the server machine is the same as the client machine.

Why not use the web console, as suggested earlier? It is simple and accurate.

What URL did you use? (n.b. it expects the ":9080" port to be part of the url).

See my response to your other thread on this same subject.

As far as I know, Vista is not a supported platform for the server. See IBM Infosphere DataStage for the list of supported platforms. The client must connect to a server, and you need to provide the connection information such as host name, user-id and password for that machine. If you didn't instal...