DSXchange

Stack overflow by chance? There's a client patch. I don't have access to the details or the ECase number associated with it, but Support should know about the issue. Just a matter of replacing a DDL and recompiling.

Hold on... ECase 62595. Annotated in the Sequence job that needs it.

So not all that weird after all. Actually, a fairly common issue when lookups don't seem to be working.

Thanks for posting your resolution.

I've done it - but you can't just supply your own XSLT. You need to read the XML PACK Designer Guide pdf, specifically the sections on this subject in the Advanced Transformations chapter. Basically, you need to access the one the stage generates and then modify that. Or is that what you are doing?

Post what in have in both the Filename and Filter boxes in the stage.

Yea verily, thou shalt respect the Schwarzschild Radius.

Arnd - I need to pick up the latest in the saga.

Post the code block for CheckJobStatusAndSubmit and anything it else it references that you haven't already posted. And use [code] tags, not bold to post them, please.

No, I actually meant 'farm' but you can say 'harvest' or 'mine' or whatever you like.

Mine are 544 or -r-xr--r-- so it is readable by all.

Neither is 'back door', which is another variation on what you might mean, I think. Where did this so called 'problem' come from?

Same way you would run any kind of script -

* Execute Command stage in a Sequence job
* ExecSH in the Before/After job section of a Server or PX job
* Call DSExecute in a custom routine or job control

Off the top of my head.

You should also consider the possibility that you've got a bad disk if it happens in the exact same place each time. Can you get another?

Because you haven't created an alias for the job, so it has got nothing to show you.

It's documented in the Server Job Developer's Guide as part of the Command Line Interface section. Specifically, check the 'Setting an Alias for a Job' paragraph.

Never had any use for it myself.

After doing all that, did you reboot first and then try the install?

As far as I know, you must always BUILD an index after CREATE'ing it. And, as noted, the syntax can be found by searching the forum - this is one such example.

Not sure. One example here seemed to indicate that or that they got it after the license had expired. Others had 'library path' or permission changes that corrected it.