DSXchange

To remind you that the steps ArndW has provided can be further simplified to meet your requirement.

But I will be surprised to see even any IBM mainframe or financial organisation expecting date in that format as 05 in year will always represent 21st century....especially after the Y2k changes.

The problem is not with DataStage. So whatever you change in DataStage (apart from load stage properties) will not affect the result as they will still load the whole set in the dbms.

So you need to either break the load into smaller chunks or increase the capacity of rollback segment in your dbms.

Few examples of each possible scenario may lead you to better answers.

I agree with Ray.

Also in the sequencer, you need to add a new stage for each action whereas in Job Control you can achieve the same with one or two lines of code.

You can use DS/390.

Check whether all jobs are against the same db.

Reset the job and see whether more info is available in the logs.

I think the same error was posted a few days ago. Do a search.

Either store it in a file and retrieve later or use status and sequencer to pass the values to next job.

I have noticed opting 'Yes' to save resulting in changes not being recorded properly. This is due to the OLE problem.

So it is better to opt 'No' and redo the changes.

Look into the logs. You will be able to locate the stage that throws that error. Sometimes you also get the data in the same or separate log entry.

Or simply use UpCase function in the link to reference.

Test the compare function in a simple job or routine.

View -> Filter Entries.

You have some casting function in the input or output sql and passing values to that column which is different from expected format.

You need to check your sql.