on 03-25-2019 11:14 AM
James - does your program perhaps call an SAP standard routine which in turn triggers multiple executions of the program in parallel processing on more than one server?
What might help is to add a few fields to the SM37 list:
That way, you'll be able to tell if - for whatever reason - multiple work processes get triggered and/or which servers are involved.
Hope this helps!
Bärbel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the reply, Colleen.
It's a custom generated program, but it occurs with any job I run, though not frequently. The problem happens regardless of whether or not the job and its variant are the same.
I know it's very difficult to pinpoint the problem, but in general, do you happen to know when it tends to happen? Have you ever had a similar problem? And if so, how did you go about fixing it?
Thanks in advance
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check in table TBTCO, are there one or four records for this job name/user name at this date/time, If 4, then your assertion is false, else if 1 there is a bug in the tool used for reporting...
How is the job scheduled,
(*) status: released, ready, running
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
which job/program are you executing? Does it occur with a specific job or any job that you run?
Is the job steps and variant the same?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.