DSXchange

For only a few cents per day you can be a premium member.

Premium membership revenue is 100% devoted to bandwidth costs of DSXchange. By buying premium membership you are not only helping yourself, you are also helping DSXchange to stay operational.

Check the permissions on every directory in the path

Something HAS changed. "Permission denied" does not magically appear out of thin air.

Better is entirely up to your judgement.

However, all inputs to the Join stage must specify the same join key(s), so your design would require four (cascaded?) Join stages.

Try the DataStage BASIC manual. By default, System(12) returns the current system time in seconds (local time, in seconds since midnight, the internal format DataStage uses for times). If the TIME.MILLISECOND option is set (using $OPTIONS), System(12)returns the current system time in milliseconds.

Check the permissions on every directory in the path of the file you are attempting to write. Also check the permission on the file itself. Find out when and by whom the change was wrought. Complain to them.

Why? It's already posted on the IBM web site and in paper form from your local IBM Education Center. Try searching there for +DataStage +training core - you get 863 hits if you limit your search to the United States

The Field() function can do this.

Yes, as I said, the error is being generated by the driver. Contact the driver vendor (Data Direct) to find out what 7500 means.

What notBrian meant to say was that we want to know what stage types you have used in the job design and how they are connected together. That is, we want to know what your job design is. How your job is designed, might be another way to express that.

Rather than I'd prefer

I think the problem is that no email is being sent. They can resolve the "always running" issue once they can receive email that the job is running. Take a look at the DSSendMailTester routine, and see how it's done there. Then try to emulate that. I don't think three arguments in the InputArg are e...

Search the forum for the correct procedure for shutting down. You might also search for debugging the dsrpcd daemon.

No.

NOT NULL means "this column does not accept nulls".

You can push them, but the database server (or ODBC driver) will reject them.

If you can use a dBase IV stored procedure, you can use Stored Procedure stage to invoke it.

How are you proposing to connect? You may need Sybase OC (client) or you may be able to use the ODBC driver shipped with DataStage.