DSXchange

THe job control of the sequence inherits the limit set during run time. If you always want it to be a constant limit then I dont see why setting it from director is a problem, or while doing individual manual runs, setting it during run time from gui. For a scheduled mechanism use either DSSetJobLim...

Look at my code again. No hashes around CommandName.$CommandOutput

Try either of the following:

You dont need to build a whole seperate job to do this. You can simply provide a command line cat to achieve this

Welcome to DSXchange
You can do that only while running the job. Other way is to set it project wide from director as you mentioned.
If you are running it from command line you can use dsjob -warn n to set the warning limit, where n will be the limit.

Two options:
1) Do it in a server job.
2) Do it in two seperate px jobs.

Please advise the different transformations you are doing. Maybe both can be incorporated into one and the same shall be advised. Help us to help you.

O yea thats right, what was I thinking

Better to do it in sequence job with 'Execute Command Stage'. The transformer will only allow before/after triggers which need to be a C routine. Too much extra work. Simplest way is to do it in a sequence job as I advised. If this has nothing to do with any datastage jobs then why are you getting D...

It wont let you do that. The sequential file stage supports only a reject link as the second link. What transformations are involved? Cant you do all in just one transformer stage?

Make sure you run in sequential mode for craigs solution. If thats not what you want then provide the following filter command to restrict the first 5 rows at the sequential file stage itself.

In routines, under utilities you have DSSendMailAttachmentTester(). Test that out and see if it works there first. If it does, look at its code and use that to send an attachment.

How are you converting them to decimal, as in what function are you using?
What is the precision and scale of your target decimal field?

Seems like your running out of space and this particular hashed file got corrupted. Clear the file, clear your logs, save it by some other name and delete the original job so that this file also gets deleted.
Also try to keep the log file sizes in check.

I have seen that behaviour too. Never chased it to the very end. Something to do with the way your stage variable is defined I believe. Is the stage variable nullable?