DSXchange

It does get deleted normally, was hoping it might not have with the failure. Add this line to top of your "dssendmail_template.txt" file in the job's project:

cat sendmail_*.sh

This will capture the generated contents into the job's log. Don't forget to remove the line when we're done.

Can you still find the .sh shell script mentioned above after the failure? If so, can you post the contents wrapped in [code] tags?

The Sequence job must abort (so the status says "Aborted/Restartable") for this to work. Which is what the "Automatically handle" option does for you - or you need to ensure it happens, with something like the Terminator stage, for instance.

What does "not getting compiled" mean? What happens when you try - do you get an error or... ? Have you tried a "force compile"?

There's no automated way to do what you want. AFAIK, you will need to treat the record as one long varchar field in job and append the columns and field delimiters based on what you find in the input.

As noted above, you would need to create a routine to dump the desired log to a text file, then that file can be added as an attachment to a Notification email. The "7.5 version" reference was for the attachment part, not the job log part.

Setup whatever you think the maximum number of columns are and use Field() to populate each. Filter the empty/null ones out afterwards.

krishna81 wrote:there is no consistency in delimited fields.

What does this mean?

That would seem to be the case, yes, if what you are saying is true. Only you can compare the user profiles and tell, of course.

You need to enter it as posted, things are case-sensitive there to a great degree. And it loves the upper cases.

Exactly, it's all right there. At the very least enable the 'Add checkpoints' option and possibly the 'Automatically handle' one as well, depending on how explicitly you want to code your triggers.

Short answer? Yes.

Actually, 'dsjob' is a UNIX function heavily documented in the included pdfs and here as well. You cannot use it 'through the Administrator'.

I imagine that could be if they are overridden in the dsenv file. Check the second log entry for the job, that will show all environment variables in play while the job was running.

Or:


Will just pull the third entry in the returned dynamic array.

That would be a question for your DBA.