DSXchange

We are even more at a loss to explain this than you are - since you haven't explained any details; it is akin to saying "my car won't start" - that could be because the key is missing, someone put sugar into the tank, because the battery is dead, etc. Take a specific example - one row from your data...

I think that you need to look at the administrator client, not the director.

Is this regarding lookup stage results?

This is vaguely familiar. I seem to recall having had a similar problem in a job sequence where it would bomb after numerous iterations. It might have been 1024. I think what happened is that the memory allocated during one of the stages in the loop wasn't being freed. It could have been the job-act...

This is an Oracle error and your DBA will explain it in detail. Have you tried connecting to the database from the UNIX "sqlplus" command? If not, try doing so and you will get the same error message.

I assume that the AT schedule is gone. Re-enter your scheduling from DataStage (actually, do the old schedules still show in the director?).
Did you enter the "AT" command from a shell to see what entries are present?

sgubba - although you don't think it important, I feel that telling us which stages (particularly input and output ones) you are using and what the program logic does is useful in analyzing your problem. Also, do you have different configurations in use and is the hardware platform the same?

a) what has changed between the time when it worked and when it stopped working?

b) what is displayed on your DataStage server in a CMD window when logged in with the userid that you use in DataStage, you enter the command "at"?

For test purposes try: $INCLUDE DSINCLUDE JOBCONTROL.H CallingJobName = DSGetJobInfo(DSJ.ME,DSJ.JOBNAME) IF FIELD(Arg1,'.',1)=CallingJobName THEN Ans = DSMakeJobReport(DSJ.ME,2,"CRLF") END ELSE JobHandle = DSAttachJob(Arg1, DSJ.ERRNONE) IF JobHandle>0 THEN C...

Yep, that was what I wanted to check - we know now that the job itself can call and get a return value from the routine with no issues, so your error is coming from the routine. $INCLUDE DSINCLUDE JOBCONTROL.H CallingJobName = DSGetJobInfo(DSJ.ME,DSJ.JOBNAME) IF FIELD(Arg1,'.',1)=Cal...

Could you post your actual error message as well, please. Also, what is the length given for the integer columns?

What data types and sizes have you declared the various columns (tatic_id, opp_no, opp_id) as? Which one(s) are you using as the key(s)?

Change the routine to have the first line do a "RETURN(1)" - that will mean the error is in the calling and return mechanism and not part of your code.

Can the routine be being passed the name of the job that is calling it? This is not allowed, you need to modify your code to include something like: $INCLUDE DSINCLUDE JOBCONTROL.H IF DSGetJobInfo(DSJ.ME,{can't recall the correct parameter}) = Arg1 THEN JobHandle = DSJ.ME ELSE JobH...

If the "7z" program expects terminal input it won't return until it gets it, and DataStage won't supply it.