DSXchange

thanks, but we can't guarantee it will be AM, it could be AM or PM Carter's method should work just fine - if you have complete faith in the validity of the incoming data: TO_DATE(YourField,'MONTH DD YYYY HH:MI AM') In your target stage, probably via Custom SQL. The 'AM' in the date formatt...

If it was a Server job, I'd tell you to remove the newline in the derivation of the field by using Ereplace, for example: EReplace(YourField,CHAR(10)," ",-1,0) This would replace all newline characters in the field with a space. I'm assuming there must be something equivale...

I know what the problem is! I've run into it before... Check the current default for the Manager's 'Export DataStage Components' screen. If you have 'Export as XML Document' checked, it will stop and prompt you with this strange little question. This in spite of the fact that you are not creating an...

If you are curious about the 'printer segment' messages, search the forum. The cause and possible solutions have been posted several times, from what I remember.

Sorry, I thought you said you were trying to compile the DSSendMailTester routine. That is what I was referring to when I said you can 'test' it to see if you can send email from DataStage. And DataStage uses 'sendmail' on UNIX under the covers to do the actual work, so no difference there. If you a...

There's really only one way to avoid the warning of reject records - don't create any. In other words, don't send any records to your target that you know will be rejected. Besides doing everything you can to ensure the data is 'clean', you can logically reject known problem records via a contraint ...

Well, you are not meant to compile it, simply to Test it and see what results it gives on your system.

Any reason why you are not using the Notification Activity stage?

You should be able to use Job Parameters on either of the lines, including the 'parameter' line - which really should be labelled 'Arguments' IMHO. As noted, the problem is they don't translate in the actual command being issued. They look fine in the log, which makes it interesting to trouble shoot...

Ditto on the Roy/Ray style except I use three slightly different triggers most times: Finished Ok Finished with Warnings Otherwise I prefer the catch-all 'Otherwise' trigger for checking for problems as jobs can fail for more reasons that just 'Aborted'. Granted, it doesn't happen very often, but wh...

In other words, add a Routine Activity stage that calls a custom routine you create to sleep X number of seconds. Pass in the time to sleep as an argument to the routine so it becomes 'generic'.

Exactly... so it depends on his version as to how easy or difficult this will be.

My server running in unix environment and i require to call my sequence from a command line from my client machine. That's the sticky wicket - running the command from the client. From what I remember for 7.5, they have started delivering the components of 'dsjob' to the client all of the time, so ...

You need to let us know what database you are having the issue with, what stage you are using (seems like ODBC) and how the field is defined both in your database and your job. Then people will be able to give you some specific help. Bascially, you are going to need to take the output of @DATE and g...

That's an interesting thought. Try branching to a dummy routine or perhaps a Notification Activity if any of the 'required' parameters are missing, otherwise run the job(s).

I don't think you can, per se. Some are required by definition - for example, Date parameters must have a value. I think Encrypted and List types as well. Others, however, are perfectly happy to be left empty. About the only way to make them required is to ensure that the jobs abort if they are not ...