DSXchange

In the Sequence job, before the FTP step, check the size of the file and don't trigger the FTP if the file is empty. Or check in your FTP script.

Take the error to a SysAdmin.

I stick with -jobstatus rather than interogate the job again after it finishes. Perhaps this recent post would help.

Add -jobstatus to your command line so you get more information on the status of the job. Look in $DSHOME/include/dsapi.h for the error codes to check for: /* 'jobStatus' values... */ #define DSJS_RUNNING 0 /* Job running */ #define DSJS_RUNOK 1 /* Job finished a normal run with no warnings */ #defi...

Pretty much what I said as well, just didn't use all the right words I guess.

What 'steps' are you looking for? Something that's not in the official documentation?

Error -12 is DSJE_BADNAME as in a job name is wrong. Without seeing your code, I'm assuming you are not using DSJ.ME for the 'current job' but rather an explicit name, and you've gotten it wrong.

From what I recall, you'd need to use it in a BASIC Transformer, with all the caveats that brings to the table. You would pass $UserStatus as a job parameter to use it 'in the table'.

From the Status view in the Director, Control-T or View/Filter Entries will show you all of the available options to filter the display of jobs there.

First suggestion would be to get a Premium membership, either yourself or via your company. You've been here for awhile, so you've seen the value of the information here. A little something I stole from Ray: For less than 30c per day you can purchase premium membership which, among other things, all...

You should be able to add a link to the WFF stage to handle that 'failure' - your 'file not found' situation. For example, an 'OK' link for when the file arrives and an 'Otherwise' link / trigger that will fire when the stage times out. Then you can do something other than go to the Exception Handle...

Actually, you can resolve this. Search the forum for "has import error and no default value" - this has been asked and answered quite a number of times already.

The 'issue' with the system variables is their format - internal. Meaning, they typically need to be futzed with to get them into the external format that you need. I prefer the DSGetJobTimestamp macro since it delivers an ISO standard timestamp and the issue of efficiency is easily resolved by call...

I would think it wouldn't matter, either could be just as 'fast'. The question would come down to what you were more comfortable with supporting or perhaps were 'required' to use. IMHO.

Several ways... most would involve 'landing' the data in some fashion and then using a form of job control to pick the values up and pass them to the jobs that required them. Simplest would probably be putting the value in a flat file and then using 'cat' to capture the content. This can either be d...