DSXchange

That would be a conversation to have with your DBA or someone else in your organization whom may already have something you could leverage.

rupesh_datastage wrote:hi my is is rupesh_datastage@yahoo.com.... i want a tutorial to satrt with datastage..

Comes with the product.

Well... as best as I can tell, your file check will need to be inside the loop. So, perhaps: * Start Loop (1 thru 5 step 1) * JobActivity C * WFF stage (0 wait) * File not found trigger -- Routine sleep 5 -- End Loop (continue) * File found trigger -- Branch out of loop -- Main sequence job -- succe...

From dsjob with the -run option you're not going to get "words" only the numeric status code. However, if after the job completes you interrogate the status with the -jobinfo option you'll get more text. Same applies if you check while it is running. Grep out the Job Status information: ds...

Yes, it does, but it is not a good practice to check for a "1" you should check for DSJS_RUNOK instead. All of those defined constants are in the same file that I posted as the answer to your other question:

$DSHOME/include/dsapi.h

$DSHOME/include/dsapi.h

Why not just do the whole thing in a Sequence job? That script just complicates understanding and maintenance. Sure seems like you could do the whole thing between the Start/End Loop stages with a routine (or a WFF stage) to check for the existence of your file.

Why would you be executing this from a Command Activity stage? Wouldn't you just run it from the command line yourself? Biggest thing that jumps out at me: the lack of a -wait or -jobstatus option being used, so the job is started but then immediately moves on to the next line of the script. Oh, and...

Something like this or this exactly? You need a comma between the job name and DSJ.ERRFATAL, not a dot. And you've got "JJob1" in the DSRunJob call rather than "hJob1". Details are important, you know.

Any chance you can link us to the post you found? That search returns 14 matches and it may save the next poor sap from searching all of them.

How about an alternate solution? Drop the filename to a flat file then use a Routine Activity to echo it and pass that to the Job Activity parameter.

:cry: You recall incorrectly. Upper-case cataloging only applies to the routines supplied with DataStage, such as the SDK routines. User-written routines have case-sensitive Catalog names, with "DSU." as their prefix. Cut me some slack... recalled somewhat correctly and it was before 6AM l...

You would use dssearch for this, from what I recall.

'Not able to' why? From what I recall they are catalogued in upper-case, see if DSU.REP works in the DEFFUN statement.

Then just split it before the XML Output stage, using a function like Field() perhaps.