FAILED JOBS

You did not mention what jobs you are running. If you are a user, this problem should be addressed to your analyst or programmer. This could just be a simple errors in parameters. There may also some steps that you have to do before running the jobs. In this case then you will have to ask your functional people who knows GL. If you are a programmer then go to job scheduler and see the log of your failing jobs(I assumed you know how to do this) and post it here that we may be able to help you.

The print file is "owned" by the user who submitted it for recovery. They will need to "send to user" to you in order for you to see it in your print manager.

As for why any new jobs fail and need recovery, you'd have to have your administrator look at the 'examine log' to see why they are failing and fix that problem.

Thank you very much Sam and John for responding to my posting. The job I am running are mostly update jobs eg GL256, GL290, GL291, GL292. and I just realize that all users are face same problem I am facing, even those using different modules like HR, AR and CB.

As for the failing jobs log, this is it ERROR: Stopped On Exit 1.

Thanks.

The first rule of troubleshooting is to find out what has changed. Since you say the problem just started two weeks ago, that leads me to believe that something in the environment probably changed ... i.e. were patches loaded, did your systems administrator change permissions?

The message "ERROR: Stopped On Exit 1. " can be almost anything. Your systems administrator should be looking at ladb.log to see if additional error messages can help you...

AP module users and any new jobs which they are summitted failed and needed recovery. Even after the recovery we can not see the jobs in print manager for screen viewing or printing. Even after recompiled the AP Module, there is no change.Kinldy a help us regarding this issue