Job Ended NOTOK without its corresponding sysout record.

[divinogaitanjmp]

Hi. I got several jobs that at their logs you can find the legend "ENDED NOTOK" , but if you look at the sysout to see what happend, you realize that nothing was generated at the time the job failed.

This is the log for one of those jobs.
15/11/07 14:29:21 CD5065 ORDERED JOB:252901; DAILY SYSTEM, ODATE 20071115
15/11/07 14:37:19 SL5120 JOB STATE CHANGED TO Wait Condition
16/11/07 02:06:49 SL5208 QUANTITATIVE RESOURCE OPS-DB-INST-ARBORCAT QUANTITY 1 ALLOCATED
16/11/07 02:06:49 SL5208 QUANTITATIVE RESOURCE OPS-DB-INST-MACPR1 QUANTITY 1 ALLOCATED
16/11/07 02:06:49 SL5105 SUBMITTED TO vsgnmysw2k306
16/11/07 02:24:16 TR5134 ENDED NOTOK
16/11/07 02:24:16 TR5120 JOB STATE CHANGED TO Analyzed
16/11/07 02:24:16 SL5214 QUANTITATIVE RESOURCES RELEASED
16/11/07 02:24:16 SL5120 JOB STATE CHANGED TO Post processed

As you see, the job fails at 2.24 am. The agent is a Virtual Windows PC. I look at the PROCID folder at agent and found several files at the same time that jobs failed with this description.
1116 02:24:40:53 ctmag:checkFileExist - FAIL to find file C:\Program Files\BMC Software\CONTROL-M Agent\Default\PROCID\2d57v_1.dat / C:\Program Files\BMC Software\CONTROL-M Agent\Default\PROCID\2d57v_1.dat.tmp after 500 times
1116 02:24:40:64 ctmag:Fail to submit ctmrjob. C:\Program Files\BMC Software\CONTROL-M Agent\Default\PROCID\2d57v_1.dat not exist

I did not found any information on this file for the job i listed above.

Any useful information on whats happening?

[fyot]

Hi,

Sysout contain all information sent to the standard output, using echo command for example.

So are you sure that you job send something to your standard output ?

[Darvedd]

Offhand it looks to me like the Control-M Agent hasn't been able to create the file it uses to submit the job process on that system.

Try checking that the Control-M Agent has sufficient privileges to create files in the PROCID folder.

You're not seeing any sysout in this instance because the job process did not execute at all - hence no sysout.

Anytime you don't see sysout for a failed job, you'll usually find info in the job's LOG instead.

Good luck!