Documentation View

We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

00619 - Batch jobs won't start - New problem?

00619 - Batch jobs won't start - New problem?

CL_GUI_FRONTEND_SERVICES - Frontend Services   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Batch jobs won't start - New problem?

SAPers,

This was a very strange phenomenon which finally required OSS's help to
resolve. I thought I should send the solution to the group to conclude this
thread.

Apparently, when our servers were stopped and restarted (the previous
weekend) only our DB/central instance was bounced. Our app. server instance
was left running. This is 'OK' from SAPs viewpoint as long as there is no
activity on the app. server during the central instance downtime. For
example, this is a good method of keeping buffers active while stopping the
central system for a full, offline backup.

Unfortunately for us, we did have activity. Batch jobs were scheduled to
run, etc. Through all this, the standard batch scheduling jobs (SAP kernel
type jobs) were not started correctly. These can be viewed via SM61, which
is a display of table BTCCTL. When I selected the action log of the
'Time-driven scheduler', the 'Last run' date was not the current date
(instead, it was the date of our last successfully started batch job).

If you see this occur, you simply have to bounce the systems (stop/restart
SAP). This should reinitialize the batch scheduler and restart the
scheduler jobs.

Regards,
Mike D. Martin
SAP Basis Administrator
SOLA Optical, USA
707-763-9911 x6106 <mailto:x6106mmartinZs...>
mmartinZs...<?xml:namespace prefix = o ns =
"urn:schemas-microsoft-com:office:office" />

-----Original Message-----
From: Mike Martin, IS, Sousa [mailto:MMartinZs...]
Sent: Wednesday, January 17, 2001 10:49 AM
To: SAP - AS/400 List (E-mail)
Subject: Batch jobs won't start - New problem?



SAPers,

I have a batch job that has been scheduled to start the past two mornings.
It remains in 'Released' status. If I check status, everything is OK. If I
check the app. server that this job runs on, all other jobs on that server
processed normally, even during the same time period (not OP mode). In
addition, there were many BTC work processes available (not reserved for
class A) as there has been since.

Yesterday, I copied the job and resubmitted it to run last night which also
didn't work. The user ID that it was schedule with is fine and the user ID
belonging to each step is fine (both of these users are used to schedule all
of our jobs).

The only difference I see with this program is that it is a one-time job
(not periodic) and was scheduled a few months back. However, we
pre-scheduled these monthly jobs at the beginning of our fiscal year (April)
for the entire year. December's job ran fine.

Any ideas?

Thanks,
Mike D. Martin
SAP Basis Administrator
SOLA Optical, USA
707-763-9911 x6106
mmartinZs...



[Non-text portions of this message have been removed]


Durban Tours - Südafrika Safari

TXBHW - Original Tax Base Amount in Local Currency   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 3776 Date: 20221203 Time: 000205     sap01-206 ( 3 ms )