Not sure if this is relevant to your situation, but we had a problem with some scheduled jobs where only the first step of the job would execute and then end with "step-insert error (TBTCP)"; check in SM21... The solution was HP 22 (Note 307970). All this on a 46B system with 46D Kernel.
Mit freundlichen Grüßen / Best regards Bernd Schäfers Tel.: +49 (0)241-96602-13 Fax: +49 (0)208-833-876257 Email: beschZd...
---------------------- Weitergeleitet von Bernd Schäfers/DVO/BABCOCK am 18.01.2001 08:42 ---------------------------
"Mike Martin, IS, Sousa" <MMartinZs...> am 17.01.2001 19:48:52
An: "SAP - AS/400 List (E-mail)" <sap400Zm...> Kopie: Thema: Batch jobs won't start - New problem?
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.
Thanks, Mike D. Martin SAP Basis Administrator SOLA Optical, USA 707-763-9911 x6106 mmartinZs...