on 11-14-2007 2:46 AM
Hello all,
The previous basis administrator seems to have created all the 'SM:* ' jobs (for example: 'SM:SELFDIAGNOSIS', 'SM:EXEC SERVICES', 'SM: SCHEDULER') to run under his name. After his user ID is locked in the satellite system, we receive the following RFC error under ST22 in satellite systems, 'CALL_FUNCTION_SYSCALL_ONLY'. I changed the background jobs to run under a valid user ID. Surprisingly, the job runs only once under the new user ID and switches back to the old user ID from the second run.
I followed the below thread:
and tried to apply the suggestions but, that didn't help me either. Please help me fix this problem.
One other thing that I notice in most of these "SM:* " jobs is that they don't seem to display the frequency of the job inspite of the fact they run weekly or daily.
Thank you.
This message was moderated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User Changed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I am having similar probem, there's OSS note #894279 which explains how to change the user.
I was trying to call proposed functional module but the job is still in status RELEASED.
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
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.