DSXchange

Viewing data on the Sequential File stage won't provide any useful diagnostic information. What happens with View Data on the ODBC stage?

Because it isn't.

Only parallel jobs support message handlers in version 7.5.x and earlier.

Change your job design so that it segregates inserts and updates into separate streams into DB2.

Obviously yes.

Did your job compile successfully? Can you use View Data on the Row Generator stage? (If not, is it the same error message, or a different one?)

Can you post the generated OSH ?

You may have a bad osh.exe of course. Check with your support provider.

Note that the last paragraph of the previous post is a SERVER solution as stated - you won't be able to use it in a parallel job.

Perhaps you could send a private message to Sunshine2323, the author of the post you quoted.

The Aggregator stage uses dfloat internally. If you specify int32 as the output, you will get the warning, because not all dfloat numbers will fit into an int32. It's annoying, but that's how it is. Your choices are to specify dfloat as the data type of the column on the link between the Aggregator ...

You don't need to attach the first job, since you don't do anything with num_link.

You DO need to detach the second job, to prevent potential "job locked" problems.

kadf88 wrote:guys,

it seems to work when I change DSJ.ERRWARNING to DSJ.ERRFATAL...

didn't like that errwarning errormode...

Ought not the constant to have been DSJ.ERRWARN rather than DSJ.ERRWARNING?

That's not the routine you tested. The routine you tested contains at least 90 lines. Read the error messages again.

I believe that a separate forum for Job Sequences is highly desirable; these are separate from other "general" topics as far as I am concerned. I would also like to see a "sin bin" style penalty for other than newcomers posting in the incorrect forum. Perhaps a delay in responding. [Penalty: incorre...

ds1user1 wrote:

ray.wurlod wrote:An approach using stage variables may be found here

I am unable to see the replies.

Thanks

For less than $1 per week (which goes towards paying for this site's bandwidth) you can.

It is not possible to use Transforms within Routines. You can, however, copy the Transform's definition expression and use that in a Routine. In the case of a Transform that invokes another Routine (like TAG.TO.DATE) you will also need a DEFFUN declaration for that other routine.

There's clearly a lot wrong with your routine. Please post the whole routine - don't make any assumptions, don't try to "dumb it down". Without this it's unlikely we'll be able to help you further.

Most probable cause is as gateleys identified.

Could also be because the subroutine has not been successfully compiled.

Could simply be that the client has not refreshed its view of the Repository (choose Refresh from the View menu).

Reverse engineering from OSH is not supported.