DSXchange

Maveric wrote:Any ideas how to remove this warning?

Without really looking at anything else, I assume it is because you are falling through your 'error exit' all the time, and when all is well 'k' is not set. Try changing the 'ErrorCode = 0' near the end to 'k = 0' and see what happens.

In that case the link COUNT_VALUE.$CommandOutput >0 should run when the count is greater than zero but that is not happening. The message in the job log is :- JobControl (@COUNT_VALUE): Executed: COUNT_VALUE=`cat /file_path/hotel_count_file.txt` Reply=0 Output from command ====> What you sh...

Ok, now it's time to search the forums for your actual error: "Nonnumeric data when numeric required. Zero used." - the truth is out there.

Ah... a 'functional' user, I guess.

Generate the HTML job report from the Designer and copy out whatever you want from there. Or if you have the metadata saved in the Manager 'Table Definitions' - double-click on it, switch to the Layout tab, right-click in the data and select 'Save as html file'.

As for Sequence jobs replying back to job control that they are finished without waiting for executing jobs to complete, you're going to have to fix your Sequence in some fashion to prevent that. If the Sequence terminates with executing jobs, there's no way for the calling process to know that it'...

I'm lost on what you are up to here, but you do realize that the 'Before SQL' tab of the DB2 stage only executes once when the job starts, yes? Not for every row.

That's quite the interesting JobControlHierarchy file you've got there, a little overboard with the milestones in my book. You also seem to be running some sort of modified KBA or at least a different version than I have as I've never seen the columns you have after Milestone Indicator, everything f...

Before a post is replied to, it can be deleted. So rather then edit these duplicates, simply start at the bottom and delete them one by one. And you delete them by selecting the Edit/Delete option and then checking the 'Delete this post' box before clicking on Submit.

3. Those are not 'expressions' - you have assignment statements in your triggers. An expression evaluates to TRUE or FALSE, nothing more, and the value that the expression resolves to determines if the trigger 'fires' (TRUE) or doesn't fire (FALSE). They should simply have the following: COUNT_VALUE...

Ah... misread 8.1 as 8.x for some silly reason. D'oh!

Possibly... if they don't use Sequence jobs and allow the job control to run each job individually. However, then you'd lose any conditional or branching logic you may have in the sequence.

Odd. Let's level set here - what exact version of DataStage and what O/S? I thought that job sequences would finish their job processing before reporting back to a controlling batch success or failure. Am I incorrect in this? No, you're not. I've been using KBA utilities for several years with great...

I would like to know the restartablity option in version 7.0. None what so ever, unless you are willing to write quite a bit of hand-coded job control code. Assuming you are correct about there being no checkpoints in that version, of course. Why not upgrade so that you not only have automatic Sequ...

If I'm understanding what exactly it is you are doing... it sounds like you always 'pass' 19 parameters even if the job only needs 16 of them. That you cannot do, you can only set parameters in the job that exist in the job, sending it parameter names it doesn't have will generate the error you men...