DSXchange

kcbland wrote:Day 0 in the DS BASIC internal date world is 1969-12-31. Somehow you're getting to there in your manipulations.

1967-12-31

VarChar is always safe. SQLSTATE is never more than 20 characters long, DBMSCODE never more than 10, and the REJECTED variables are true/false (1 or 0). However, depending on the database, LASTERR can be very long indeed; for any Microsoft data source I allow VarChar(4000) or even more, since they g...

Stopped jobs also must be reset before they can be re-run.

Ultimately the answer to the original problem is to force the supplier of the file to be consistent in the style of delivery. Other than that, test the fnal byte (prior to any end-of-file indicator) of the file to determine whether it is a line termination character, if it isn't then you have an unt...

If you use Usage Analysis in Manager or MetaStage, and expect it to work properly in the new environment, then you must migrate the table definitions.

I too would update DS_JOBS, since this is the only location that job names are stored.

Find out who the DBA is, as I suggested near the beginning of this thread, then log in as that user to grant privileges to other users. This is the only way you can solve this.

Get more disk. Disk is cheap.

Also find out whether all the processing nodes are actually being used. Do any stages specify an explicit node pool? Are any nodes in the configuration file NOT in the default node pool?

Basically no.

The Operator role does not let them see design-time objects at all, so that's not what you want.

You could figure out, by elimination, which objects can't be read-only. These would include DS_LICENSE in the UV account, and VOC in the project. Not too many others, afaik.

This one usually means that there's already some other (telnet?) service holding port number 23. For example it might be the MKS Toolkit's telnet listener. However, in your case, the message also reveals that the DataStage Resource Service is not starting. This is the problem that you must solve fir...

It's a database called the project's Repository, as others have noted. Design-time objects are stored in tables whose names begin with DS_, while run-time information is stored in tables whose names begin with RT_.

Can you confirm that all stage variables have been properly initialized?

[ur=http://tinyurl.com/kaeca]This link[/url] might also prove interesting (once you've signed up).

You name both input files within the Stage properties. The Merge stage only has an output link.