DSXchange

I access DataStage server via VPN over 128kbps ISDN (over the Intenet) with very good results in terms of performance. In fact, I now do a lot of my Designer programming remotely. There was no special setup on the client side as long as it "thinks" it is all part of the same network and ca...

I would agree with David. I have also struck this at one of my clients and I admit should have submitted a GTAR request, but there were more pressing things for me to look at. When I get a chance I will dig out the offending lines of code, using VLIST. Phil Walker Gnosys Consulting Limited Auckland ...

Ray, With this problem/error that Mark is getting ... If there was an error in his job definition or data definition, wouldnt the program name in the error message reflect the job name (if in job control) or the stage name (if a data error in the processing in a stage)?? If memory serves me correctl...

This is a topic for an orphaned message.

Another thing to look for is an uninitialised variable used within a routine. X += 1 assumes that X has a value to begin with. If no value has been assigned prior, X is assumed to have a value of VARCHAR[0]. Thus Datastage is forcing a conversion of the datatype from VARCHAR to Integer. Datastage al...

This is a topic for an orphaned message.

I am also getting this messsage on every job I run and have been for both v3.2 and v3.6 and I cannot find the error in my jobs. I think its one of the various bugs in DataStage. Mark Griffin AMP Sr. Application Developer Data Warehouse Systems CIGNA Healthcare Two College Park Drive, 454 Hooksett, N...

This is a topic for an orphaned message.

This is almost certainly a problem in one of your job designs or routines, rather than in DataStage. Its reported by DSD.RUN because this is the program that runs a job. "Non-numeric data where numeric required. Zero used." is DataStage (UniVerse RDBMS) trying to be helpful. Somewhere you ...

This is a topic for an orphaned message.

There are only three exit status values once a job has been started. The job either completes (with or without warnings) or is stopped/aborted. If it does not complete it must be reset. Perchance an enhancement request? Currently we cant help you. Easier if the job control were in a separate job, so...

I feared as much. Yes, separate jobs are probably the cleanest approach. Oh well, Ill add it to my list...(along with 101 other things). -----Original Message----- From: Ray Wurlod [SMTP:ray.wurlod@informix.com] Sent: Tuesday, 15 August 2000 14:31 To: informix-datastage@oliver.com Subject: RE: job c...

That raises an interesting point... I thought you had to be subscribed to the list to be able to post to it. This would imply that you are currently still subscribed, unless you resubscribed in order to make this post. If you didnt resubscribe, then I would suggest that you are not unsubscribed. Did...

True, job control or before job routine, 6 of one and half a dozen of the other. As I said, my current approach is to abort the job (in this case, from the job control) to stop the stages from running. My point is though, that Id like to stop the job without aborting it. Youre not wrong about "...

None of which stops you having a before-job subroutine as well. I have used DSStopJob(DSJ.ME) in the past and, while it stops the job, its ugly. > ---------- > From: David Barham[SMTP:David.Barham@anglocoal.com.au] > Reply To: informix-datastage@oliver.com > Sent: Tuesday, 15 August 2000 11:14 > To:...