DSXchange

I was going to mention that, but they stated they didn't just see one but rather it was coming in as the 'pad' character in varchar fields from some reason.

Does it work properly if you pass in the user credentials on the command line?

Ray - I just want to convert seq file into xml , i gave all the schema in the Description for each data element and i am using the same job flow as you said seq---tx---xmloutput . In my output i am getting first record in xml format starting with <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE TCRM...

I'm guessing that this is a query from their BI tool and what they are being asked to do is 'convert' this query into a DataStage job that builds a reporting table instead. This way the BI tool can just select from there after DataStage has done all the heavy lifting. [shrug]

Fine... be that way. Still, my point stands. The XML Output stage will do all of the conversions the OP asked for automatically. Well, except for "\ with &quot;" which I assumed was a typo.

Perhaps they are doing all of their XML work manually for speed, that I could understand.

Looks like you are not sourcing your dsenv file in the script to properly establish the environment needed.

Well, the only reason I suggested that was because you said it 'worked fine' if you recompiled it, which is no different from not having checkpoint restarts enabled in the first place. If a particular stage (like your routine, for example) should be excluded from the checkpointing, then you can chec...

That's the thing - the loop is superfluous and totally unneeded here. The timeout value is the longest it will wait for the file to show up, the moment it does show up it will cease to wait and pass on control to the next stage. There is no 'waiting for the remaining time'.

trammohan wrote:Use Start loop and End loop stages in your job sequence and set loop for 10 times i.e from 1 to 10.... and wait stage for 30 minuters...

Curious how this is any different from simply setting the timeout to 5 hours and waiting once?

Durga wrote:I need to process that file as soon as it lands in the unix directory.

I need to check for the file for every half an hour from 11:00 am to 4:pm

These two statements are mutually exclusive.

It skips processes that ran ok when you have 'checkpoints' enabled in the Sequence. If you don't want that, disable that option, and it will always start over from the beginning.

Why not just set the timeout to 5 hours and be done with it?

It was too difficult to arrange 'sudo' privledges so they just gave you the root password? Err... ok. By default, 'dsadm' is the administrator id, nothing magical you have to do except under Tru64 from what I recall. All you should have to do is make sure it is created before you start the install.

We'd need to see the routine, not just a portion of one line of code, to be able to provide much more help.

Yah, that too!