Background jobs run in a special type of work process—the background work process—that is different from dialog work processes in two ways:
1. A dialog work process has a run-time limit that prevents users from interactively running especially long reports. that limit is always in effect for dialog work processes. No such limit applies to background work processes.
2. Background work processes allocate memory differently than dialog work processes so that background work processes can become as large as they need to in allocated memory to allow for processing large volumes of data.
<b>Use</b>
Using background work processes also lets you optimize both background or dialog processing. In “night” mode, more servers can offer more work processes to accommodate background processing jobs that are scheduled to run when there are lower numbers of interactive users. In “day” mode, you could limit background processing to fewer servers and/or fewer background work processes.
When a time-driven scheduler is activated, it starts the jobs for which it has free work processes. If there is another background processing server, then the scheduler on that server starts the remaining jobs for which it has capacity, and so on.
<b>PROCESS</b>
Assigning the program to the variant in T/C SE38
Enter the Program,
Enter Variant Radio Button ON,
Name the Variant
Assigning the varient job to its importancy & Frequency in T/C SE36
Enter Variant Job Name -- Save,
Class--- Save ,
Period Values---Save
Executing the Varient Jobs in T/C SM37
Enter The Jobname --- Execute
Hope This Works For you..Reward if its helpful
Regards,
Rajasekaran.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.