DSXchange

Unless this has changed in 8.x you are not licensed to use the ODBC drivers that ship with the product outside of the GUI on a UNIX server. Any such BCI code will work for 30 days and then stop working. You'd need to purchase 3rd party drivers to make this work.

Right?

Not sure what to say. I know how it works, so not sure why you can't see jobs you've just scheduled. Where were you looking for these when you didn't see them? ps. For a 'next five minutes' job, those go into 'at' rather than 'cron' which is for recurring jobs. And once an 'at' job runs it is remove...

It only shows jobs scheduled by the current, logged on user. It just reads the user's crontab, so if you didn't schedule it there's nothing to show you.

As noted, this default value is not a Project level setting, it applies equally to all Projects connected to from that particular client.

:D

Search the forums for USERSTATUS, all the details are out there.

Not with that stage AFAIK. You could roll your own routine and call DSSendMail() there as one solution. Or a scripted call to sendmail.

From a Routine Activity stage, sure. Inside the routine use DSExecute and then remove any @FM before returning the result.

Welcome aboard. Sorry to whack you on your first post, but is this any kind of a 'testimonial'? In other words, you have posted in an inappropriate forum. There are two forums for questions of this nature (well, technically three if you count the catch-all 'General' forum), one meant for each job ty...

You might want to consider posting your actual abort messages. Otherwise, people will be just... guessing.

Right, now I recall the DSDIR versus DSDES distinction. None of this will solve the 'View the logs but not run the jobs' problem, though.

Is there now a role in 8.x for this? Or some other way to accomplish this?

Close, you should actually use the documented status codes rather than a direct numeric value:

Meaning, you are 'combining' them by choosing a Custom trigger and typing that string that you posted directly into the trigger expression? If so, it's not really working. As noted, those aren't expression but rather two text strings that you are or'ing. That should always resolve to 'true'... did y...

Ah, yes... but the Borg don't shout.

Resistance is futile.