DSXchange

From hanging out here, it seems that DB2 is the only stage that wants DATE fields in internal rather than the external format the others use. You should be able to search for various posts to this effect.

It's called 'escaping' and the back-slash is the default escape character. It is usually used to tell something to ignore a metacharacter and (as Arnd notes) accept it 'unparsed'. In this case it also works for quotes. I didn't mention it because in my experience with the Server product it doesn't h...

You are right, the quotes in String parameter values get stripped.

Do you need to pass the entire phrase? Can you just pass the date?

Is this one client machine running XP Pro with Service Pack 2? If so, have you installed the SP2 patch on it?

And on the chance you meant zero fill (or pad) a field to 10 characters that may have less than 10 characters in it, check out the FMT function.

I'd start by rebuilding the repository indexes. There a ton of posts that reference DS.REINDEX if you need help with the syntax.

First question would be - what is it? That might help direct the solution.

Or check the log for a job that creates a hash file in an 'Account', the full create syntax it used will be there.

As long as people understand that the 'it' that will work under XP Pro SP2 is the client. It's still not a supported platform for the Server.

We have access to Perl in 7.0.1 as well, having installed the Click Pack. Others have asked the same question here, but I have no idea if we have any Perl experts handy or if they could be press-ganged into rowing an oar on this barge. I think we'll end up sticking with the lesser of our known evils.

Argh! You said the 'S' word!

ArndW wrote:The trigger of "OK - Conditional" will continue on an exit status of OK or OK with warnings

'Fraid that's not true, Arnd.

The Custom Condition would need to check for a $JobStatus of 1 or 2, btw.

anupam wrote:But i want it to check it every 10 minutes. Can it be done with the Job ?

Actually, you said you want to check it 'continuously'. And your routine is only sleeping 10 seconds between tries. Is that really what you meant to do?

Thanks Kim. Yah, I'm sure we'll end up doing something akin to that. This actually gets incorporated into an XML feed to an outside vendor, so now they're talking about a Java based post-processing step to run the XML through that will stick the encrypted/encoded string in with everything else.

Surely. Search the forums and you'll find two other posts that discuss this, including this one in the FAQ forum.