DSXchange

You really shouldn't see a problem like that. Both 'at' and 'cron' per user should show in the Schedule tab. You may need to open a support case with your official provider if no-one else has anything to add.

What flavor of UNIX by the way?

What do your XPath Expressions look like for your example? And what are your XML Input settings?

As far as I know, yes - Java is used from the XML parser (and perhaps even RTI) and is why we needed to worry about patching it (pita, btw) for the DST start/stop changes over here in the States. As noted, I'm sure Ernie will confirm or deny, if he wanders in here.

I voted #1 as that was where it all started. Of course there's been plenty of self-study over the years but classes from Ardent / Ascential and Informix were the foundation. Oh, and for RTI there was #4.

Never mind the fact that you are hijacking someone else's thread.

suchit1983 wrote:In the sequential file. I am creating a Test1.dat and in the filter option, the command is gzip -c Test1.dat.

For the Filter command, try just "gzip": no filename, no "-c".

I mentioned doing it 'after job' and I meant that literally as an After-Job Subroutine. If the job doesn't run then the script wouldn't be run. Or if you want to do it in a separate step, then code for the possibility as Ray notes.

Or... create it with a static name and then rename it after job. You could easily build a generic 'datestamp a file' script for this.

Interesting... I don't recall the Filter option as being available on the output side of the house. Ah well, you learn something new every day!

You won't be able to directly create the gzipped output, so create the output file and then arrange the gzip 'after job' - either directly from the command line or write a generic gzip script anyone can leverage.

Forget the source. The log should also contain an entry labelled "Executed command:" and then your complete command. Double-click on it to see the output, which may help you figure out where it is going wrong.

Hi Craig, My apologies if it sounded as though i was not satisfied with your reply.. of course, your reply was useful and informative.. I think you answered my questions in full and more... So, the rating that I had input was probably inadvertant... No worries, just bugs me sometimes. I should have...

As noted, just put them in the stage.

Either do that directly, separated by a space or a semi-colon or a comma or whatever works for you - or use a Job Parameter and do the same for the parameter's default value.

First response would be - ok, go ahead! Or maybe Ok_Go_Ahead! But I guess you are asking, in spite of the lack of an actual question, how one would do that, yes? Two simple answers: 1) Use an email group. To me, that is the preferred answer as changes to recipients is done outside of the job, mainta...

Actually, that was what I would consider fairly "in detail". What part is unclear? The Projects directory? If you have a 'standard' install, then cd to the DSEngine directory and slide over from there: cd `cat /.dshome` cd ../Projects/<YourProjectName> Something else? You could also trying searching...