DSXchange

Expired password? Have you done a Search? What's changed between then and now?

I was going to challenge that too, but held back seeing the version number. The product has not changed, but the platform on which it runs certainly has. It now has to run over Information Server, effectively using a one-node configuration file on the server machine. The service-oriented metadata an...

Without seeing your script, no idea.

Actually, the idea is "tighten up control in your script". The dsjob command will always return when the job status changes from Running.

So what else are you doing in your script?

Can you please be clearer in your answers? I appreciate that your first language may not be English, but I really don't understand what you have just written. Please answer each of my questions separately. We do strive for a professional standard of written English here at DSXchange, not least becau...

Have you undertaken a Search?

This question has been answered previously.

I guess all of Craig's FROM clauses are shorter than 64 characters!

You can "sort of" figure out what's going on by reading the comments in the header file, but you'll never be sure that you've got all the possibilities.

Are you running this from a job sequence?

What does your official support provider have to say?

Looks like there might be an issue with how an abort caused by ErrorCode being non-zero in an after-job subroutine is handled.

An "exact match" search on ".v in its name" returned 24 hits.

Any routine with a DSD or DSR name is part of DataStage server engine. Source code is intellectual property of IBM (and heavily guarded) and there is no documentation in the public domain. The Call @SUBR(args) form is documented in the DataStage BASIC manual. Search for "indirect call" in the sectio...

Welcome aboard.

What rule set are you using for your Standardize stage?

You almost had it! The technique is called inline prompting. In its simplest form it is the prompt text surrounded by double angle brackets: SELECT * FROM DS_JOBS WHERE NAME=<<Job name>> ; The parameter value can be supplied in response to the prompt from a "here script" within your script. cd `cat ...

You can help yourself. Find out why the job monitor is not starting by trying to start it and capturing any output, especially from stderr, and inspecting the same.

It probably failed because IsNull() is not really the test you wanted. It was IsNotNull(), as I posted.