This website is not affiliated with, sponsored by, or approved by SAP AG.

Is it possible to detect submitted jobs...

Basis (Basis Technology Modules: Basis Component/System Administration, GUIs)

Moderators: Snowy, thx4allthefish

Is it possible to detect submitted jobs...

Postby DrSidewalk » Tue Dec 03, 2013 5:26 am

Guys,

I am planning to monitor (in a way) all submitted/scheduled jobs and have the job class changed accordingly. When jobs are moved to 'Released' status I would like to trigger an event, or user exit, and have the code in this exit check the job name/program name against a Z table and decided whether this job should run as a Class A or Class C job, and then change the job details accordingly. Is this a possible, or just pure fantasy?.

Dr Sidewalk
DrSidewalk
 
Posts: 180
Joined: Thu May 03, 2012 9:35 am

Re: Is it possible to detect submitted jobs...

Postby QZ » Tue Dec 03, 2013 7:51 am

Hi Dr. Sidewalk,

I haven't come across a way to change the job class after release, but a typical
way to ensure that high-priority jobs are type A, is to put in place
a process that the major batch jobs are scheduled only by non-dialog users
(For example, BATCH-FINANCIALS, etc..), and have a handful of people
responsible for ensuring that the jobs (A or C) are set properly.

Also, if the work processes are set properly, jobs did hardly ever (or never)
need to wait for a free batch process, so even type C jobs will get
processed immediately.

QZ
QZ
 
Posts: 221
Joined: Wed Nov 14, 2007 11:02 am

Re: Is it possible to detect submitted jobs...

Postby DrSidewalk » Tue Dec 03, 2013 11:13 am

What we tend to do at month end is to lock out users from submitting manually submitted jobs, by just not allowing any background work processes to class C jobs (defaul class) and allocate all work processes to class A jobs, being the regularly scheduled jobs. Although this is a sledge hammer approach, I must admit. Is there way to temporarily lock out the users from submitting jobs, but still allow some of the transactions (like payment run) that submit jobs in background?. That would be the ideal solution.

We also have ALL scheduled jobs set with tha Target.server set to <PROCESS>. But there seems to be no way to allocate ALL backgrond work processes to be available to jobs with this target.server name. Or at least I don't think there's a way.

Ideally, if we could lock out users from submitting jobs via SM36 but still allow programs to submit background jobs then that would be the ideal solution. Is there a way to inhibit SM36 for all except SAP do you know?

Dr Sidewalk
DrSidewalk
 
Posts: 180
Joined: Thu May 03, 2012 9:35 am

Re: Is it possible to detect submitted jobs...

Postby blueteeth » Tue Dec 03, 2013 12:53 pm

Ideally, it is nice to have a couple of SAP instances which are batch specific (large number of BTC processes) and near to DB Instance.

Please explore authorization object S_BTCH_JOB. Perhaps you can do something there.

Also look at SAP Note 786412

Best,
BT
blueteeth
 
Posts: 499
Joined: Sat Apr 05, 2008 12:22 pm

Re: Is it possible to detect submitted jobs...

Postby QZ » Wed Dec 04, 2013 4:41 am

Dr. Sidewalk,

Can you set an operation mode in which all of the batches are type A,
and, like BT said, using auth. object S_BTCH_JOB (Or others, I
haven't checked into the details), allow users to submit
type C jobs only in SM36.

So, for example, if you want type A only between 5PM and 7PM,
set an Op Mode that has only type A batch WPs so people
cannot submit during that time.


QZ
QZ
 
Posts: 221
Joined: Wed Nov 14, 2007 11:02 am


Return to Basis

Who is online

Users browsing this forum: Google [Bot] and 3 guests





loading...


This website is not affiliated with, sponsored by, or approved by SAP AG.