DSXchange

Neither do we. What the heck is a 'web character'?

D'oh!

Chulett..in production we are using production files. Of course. I'm concerned about your hashed files, not your file files. My point is your assertion that the jobs are using account based (not pathed) hashed files in the dev project account. I can only see this continuing to work if your Producti...

But not for anyone else. You must understand you've just set the default warning limit for the Director client on your PC and nowhere else.

Unless. Of course.

I don't have an answer for you, but just wanted to compliment you on your post. If anyone needed a model for getting help on a problem, they have one now. Excellent.

Use LOGTO <ProjectName> to get to your project and then try DS.TOOLS - all upper case. There's nothing to add, it's everywhere you need it.

The 'new' Oracle TIMESTAMP fields are not supported natively, and as you've found, are created as DATE fields instead. If you really want the field created as a flavor of TIMESTAMP, switch the table creation option to 'User Defined DDL' and make it create it however you want.

What about when the job goes to Production? You still going to be accessing the hash in the Dev Account?

Please post a few of your Credit Card numbers from production with the Expiration dates and 4 digit verification codes from the back and I'll try them out. I'll have an answer for you in a couple of weeks. Ones with large limits would be prefereable for true stress testing. Guys - be aware that a c...

There are two places you need to do edits, none of them where you've tried yet. I'd suggest you undo whatever you did and then read this post:

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

No such thing ships with the product, must be something developed there.

Note the difference in the usage statement generated by your error and the way you are calling dsjob. The Project and Job Name must be the last two entries on the command line.

Did this work before and then suddenly stop? Or hasn't worked yet? Post the dsjob syntax you are using and the complete error message.

Fills me with an urge to...