Holding and restarting background jobs

We are going perform a code page conversion of our SAP system this weekend.  The conversion is expected to run Friday at 5:00pm thru Sunday at 8:00pm.  We are planning to run program btctrns1 to hold the jobs on Friday at 5:00pm and then run btctrns2 to release the jobs on Sunday.  My question is what happens to jobs that were scheduled to run on Friday evening or Saturday.  Will these jobs get run as soon as they are released on Sunday?  What if they were workday only jobs and Saturday or Sunday are not workdays.  Thank you in advance for any insight you can provide on this.

Hi Russ.
all the jobs which are in status "released" will start to run, if the job scheduler finds an empty workprocess for them.
The date and time of the jobs is not affected if you execute btctrns1 they will just get a special status.
So after running btctrns2 everything works as normal again. This of course means workday jobs still will be scheduled only on workdays. But the rescheduling is done right before the job is executed. So a worday-only job normaly should not be scheduled for Sunday (if this is no workday).
I hope I made myself clear...
By the way, the ABAP Batch scheduling is explained in SAP class ADM100.
Regards,
Sascha

Similar Messages

  • GN_GENERATE_CHECK and SM_SERVICE_CONTENT_UPDATE background jobs are failing

    We recently upgraded our Solution Manager to 7 ehp1.  A couple of the background jobs are not able to complete.
    Both jobs have the following entry in the job logs
    Step 001 started (program RAGS_DSWP_SERV_CONTENT_UPDATE, variant , user ID SOLMAN_ADMIN
    No authorization
    I'm not sure where to look for the authorization issue.  Any advice would be appreciated.
    Thanks
    Laurie McGinley

    we are on SM 7.01 (EHP1)  - and we have the same problem:
    Jobs GN_GENERATE_CHECK and GN_WORKLIST_GENERATE
    both jobs end abnormal with joblog:
    Object requested is currently locked by user SOLMAN_BTC
    Job cancelled after system exception ERROR_MESSAGE
    but the job-start is not corresponding to the entries in table SMCONFIGJOBS
    both jobs are startet at 00:01:44 (both !!!) 
    in table SMCONFIGJOBS the entry are
    REPORTNAME         GN_GENERATE_CHECK
    REPVARIANT
    JOBNAME            GN_GENERATE_CHECK
    PRIORITY           50
    PERIOD TYPE        DAY
    PERIOD INTERVAL    1
    START TIME         00:15:00
    ISIMMEDIATE
    INACTIVE
    WORKLOAD           M
    COMM2SAP
    REPORTNAME         GN_WORKLIST_GENERATE
    REPVARIANT
    JOBNAME            GN_WORKLIST_GENERATE
    PRIORITY           50
    PERIOD TYPE        DAY
    PERIOD INTERVAL    1
    START TIME         00:01:00
    ISIMMEDIATE
    INACTIVE
    WORKLOAD           L
    COMM2SAP
    any suggestions why the jobstart is not corresponding to the starttime in table SMCONFIGJOBS
    what job is scheduling these 2 Jobs GN_GENERATE_CHECK and GN_WORKLIST_GENERATE
    which other job maybe responsible for the object lock???

  • How to transport variants and scheduled background jobs

    Hi all
       Could anyone let me know if  variants be transported .
       also can scheduled background jobs transported.
    Thanks in advance

    Hi,
    Run the program RSTRANSP and give the name of the program and the variant name.
    It will create a transport request for the variant.
    the rest of the process is the same as is the case with all other transport requests.
    Regards,
    Raghu
    Message was edited by:
            Raghu Reddy

  • Scheduler and the background jobs page

    I have just added a job to the sling scheduler, I thougt once added i was be shown in the background jobs page in the tools of cq5.
    Does Sling scheduler nothin to do with that? how could add a job background to the background jobs page in the tools of cq5??
    Thanks.

    For your use case you should be able to see at http://localhost:4502/system/console/events
    For the background jobs ex:- [1] will be displayed in tools.
    [1]   http://localhost:4502/system/bgservlets/test.html?sling:bg=true&cycles=1

  • Automatic Mail not getting generated through background job

    Hi Experts,
    We have set up a job variant with spool recipients. We are getting the automatic mail if the job is getting finished successfully. But we are not getting the automatic mail if the job is in cancelled status. Earlier we used to get the mail even if the job is in cancelled status. We are not sure if there is any setting which would restrict the automatic mail based on the job status.
    Appreciate your help in this regard.
    Thanks and Regards,
    Ranjani.

    Hi,
    Just for a work around, try checking the SAP user inbox for the user who has scheduled the background job.
    I don't there  is any seperate configuration in Spool List Recipient for the canceled jobs. We need to confirm that the email ids provided in the Spool List recipient are correct and the background job creates a spool request even if it is canceled.
    Also if possible try deleting the existing background job and create a new background job with the same parameters and valid email id's maintained in the Spool List recipient.
    OR
    Without deleting the existing background job, parallely create a new background job with the same parameters and valid email id's maintained in the Spool List recipient. If it works then delete the old background job.
    Thanks
    Harish

  • Background Job Scheduling

    Hi,
      I am scheduling a report to run in background.
    In this report it is creating background jobs automatically for different company codes.
    It submits the 1st background job and waits until it finishes.
    Then 2nd job starts in background and continues with other jobs.
    At end it finishes all the jobs and closes.
    Now my problem is.
    1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
    2.       If possible how can we do that.
    What I have written is
    loop at companycode.
    Create job name.
    call fun 'Job_Open'.
    submit xxxx user sy-uname via job job_name numer job_count
    to sap-spool
    spool parameters l_spool_parameter
    without spool dynpro
    with companycode
    with ......
    and return.
    endloop.
    Please help ASAP, urgent.

    hi praveen,
    Job Scheduling Explained
    Definition
    Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the job’s definition. There are several ways to schedule jobs:
    From Transaction SM36 (Define Background Job)
    With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
    Through the background processing system’s own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
    Through an external interface.
    Scheduling Background Jobs   
    Use
    You can define and schedule background jobs in two ways from the Job Overview:
    ·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
    ·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
    Procedure
           1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
           2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
           3.      Set the job’s priority, or “Job Class”:
    ·         High priority:      Class A
    ·         Medium priority: Class B
    ·         Low priority: Class C
           4.      In the Target server field, indicate whether to use system load balancing.
    ·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
    ·         To use a particular application server to run the job, enter a specific target server.
           5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
           6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
           7.      Define the job’s steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
           8.      Save the fully defined job to submit it to the background processing system.
           9.      When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
    Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
    Specifying Job Start Conditions
    Use
    When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
    Procedure
    Choose the Start condition button at the top of the Define Background Job screen.
    Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
    For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
    Once you’ve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
    No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
    Managing Jobs from the Job Overview
    Use
    The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
    Procedures
    To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
    To copy a single existing job, choose Job ® Copy.
    To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
    To repeat a single job, choose Job ® Repeat scheduling.
    To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
    You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
    To review information about a job, choose Job ® Job details. Details displayed can include:
    current job status
    periodicity, or the repetition interval
    other jobs linked to the current job, either as previous or subsequent jobs
    defined job steps
    spool requests generated by the current job
    To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
    To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
    To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
    To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
    To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
    To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
    regards
    karthik
    reward me points if helpfull

  • Pass lock to background job

    Hi,
    I'm looking for ideas.
    We have an inbound process for special messages transfered from XI system via asynchrounous call. Messages are identified by a GUID.
    The inbound process will save the messages in a database table and create background jobs for processing big messages while small messages are processed directly.
    To avoid any interference, we want to lock messages as long as they are processed. For this we have a lock object and the Enqueue/dequeue modules.
    Now my question is: How can I pass a lock to the background job (created by SUBMIT VIA JOB) and have it released there after processing is done. The Job will run in a new LUW.
    And then, if any error in background (or online) processing occurs, how to make sure all existing locks are released?
    Thanks for some good ideas on how to proceed.
    Regards,
    Clemens

    resolved - we won't do it. We'll create some kind of queue: A fully-buffered database table where we put the lock entries and remoce them when it's time to do so. This way we can integrate an activity monitor watching the objects being processed.
    Thanks for reading
    Clemens

  • Background job within another background job

    Hello Experts,
    I have a BDC program (for BW tcode OLI7BW) which executes by scheduling a number of background jobs. This report works fine when run manually. But doesn't work if it is scheduled as a background job through SM36. The status of the job is shown as finished, but the data is not uploaded.
    Is it not possible to execute a background job within another background job?
    If it's possible, what could be the possible cause of error?
    Thanks In Advance
    Radhika

    Hi Radhika,
    If you are trying to upload data from a file on ur desktop to Internal table, then background job doesn't work. Always remember GUI means ur front end and all background jobs are run on application server and they dont run w.r.t ur desktop.
    Kindly check it and get back to me incase of any queries.
    Dont forget to reward points, if found useful.
    Thanks and Regards,
    Satyesh

  • Call transaction in Background job

    Hi,
    I am executing a program in background. In that program I am having a CALL TRANSACTION as below:
    CALL TRANSACTION 'ME22'
        USING g_t_bdctab
        MODE 'N'
        UPDATE 'S'
        MESSAGES into g_t_bdcmsg.
    But it is not working. The same is working when the program is executed in foreground.
    Is this means, we cannot have CALL TRANSACTION in background?
    If Yes, then what could be the solution for it?
    Thanks,
    Pankaj.

    Hello Pankaj,
    Call transaction works in background.
    Provided you are not picking file from presentation server.
    If you are picking file from presentation server, place the same file in application server and during background job pick the file from application server then your program works perfectly.
    Regards,
    Tarun

  • Scheduled TMS_ # TMS_TP_IMPORT  background jobs fail with error code 0232

    Is anyone else having the problem we've just encountered since upgrading to ECC 6.0 and CRM 2007, where once setting up the automatic import ALL background jobs, to have all of the Transport Change Requests imported into the Q-Prod testing systems automatically, fail after several successful runs?
    After setting up the automatic import background job to run every 15 minutes, the first few run successfully (importing any transports as it should), then the transports stop being imported.
    The background jobs continue to run, but have the following in the job log overviews CRM 2007 - "Could not start transport control program tp". R\3 ECC 6.0 - "Transport control program tp ended with error code 0232".
    Only by deleting the background job and recreating it (or manually importing) from STMS, can the transports continue to be imported. Although I have noticed that there are multiple tp.exe processes started, which need to be deleted before the STMS and TMS Background jobs work again.
    The:
       DB is SQL Server 2005
       disp+work is at version 7000.150.14.48855
       R3Trans is at version 7000.149.14.47907
       tp is at version 7000.144.14.39594
    Any suggestions on how to cure this for good?

    Thanks All
    FYI
    SAP first suggested the following notes: 19466, 1150361, and to add a Startup profile parameter rfc/use_gwstart = 1. Which was only partially successful.
    I guess it had more to do with RFC processes hanging than it did with the tp, which was fixed in a later kernel patch level.
    I've upgraded the kernel to the latest (70000.181.0.0) and my problem was fixed.
    Ken

  • CCMS Monitor to Pager for Failed Background Jobs

    Hello Experts,
    I am currently leveraging Central CCMS monitoring to alert us via email whenever a background job fails in production using the MTE Class R3BPServerSpecAbortedJobs.
    I am trying to find a way that I can tweak the monitor to alert me ONLY when specific background jobs fail.
    We want this alert to notify the oncall pager only when a handful of critical jobs fail. Does anyone know how I can delimit this MTE?
    For example, we will be creating jobs that begin with Z_ALERT* that I will tie to an auto-react method that will email a pager.
    Thanks in advance.
    Bill

    Hi Sundara.
    From following link, you can download step by step setup information.
    So please check following documents.
    http://www.service.sap.com/bpm
    =>Media Library=>Technical Information
    =>1. Business Process Monitoring - Setup Roadmap
    =>2. Setup Guide - Business Process Monitoring
    Before you start setup, I recommend you to check
    SAP Notes 521820 to ensure whether you already fulfill
    prerequestions.
    Basically what you have to do is following.
    1. Describe your business process under following area.
       (T-CD DSWP =>Solution Landscape =>Solution landscape maintenance)
    2. Setup BPMon session.
       (T-CD DSWP =>Operation Setup => Solution Monitoring =>
        Business Process Monitoring)
       in BPMon session, select job monitoring. And define background
       job that you want to monitor.
       In BPMon job monitoring, you can monitor, cancel, delay, duration,
       unexpected parallelization, also job log and so on.
    I hope this information help you.
    Best Regards
    Keiji Mishima

  • CCMS Background Job Monitoring Runtime Alert

    Our Basis team has configured CCMS and the Background Job Monitoring for long-running jobs.  They want to set up a "generic" entry (for example, * for job name) so that all jobs will be monitored for runtime longer than 1 hours (will be longer duration when moved to production).  This seems to be working correctly but the alert message does not give the name of the background job that triggered the alert. The altert text is "Alert Text:3821 Sec > 3600 Sec Current value over threshold value System:DEV ".   This message is coming from message class RT, number 001.   How do we get the job name included in the alter message?  I have looked at the messages available in message class RT but do not see one that includes a variable for job name.  We do not know where to look to see what data is actually available for the alert text message and what other message classes might be possible.

    Hi,
    This is possible and perhaps the link in the thread below should help:
    Simple question for CCMS Output format
    Regards,
    Srikishan

  • Exact Steps to schedule a background job a specific time daily :

    Dear  All,
               Please let me know  the whole process involved in schedule a background job a specific time daily. what is calender id. I could not understand what it has given in SM36.
    Thanks in advance.
    Rgds
    Prem.

    Hi prem
    this is complte procedure for ur requirment.
    Scheduling Background Jobs 
    Use
    You can define and schedule background jobs in two ways from the Job Overview:
    Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
    The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
    Procedure
    Call Transaction SM36 or choose CCMS ® Jobs ® Definition .
    Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
    Set the jobu2019s priority, or "Job Class":
    High priority: Class A
    Medium priority: Class B
    Low priority: Class C
    In the Target server field, indicate whether to use system load balancing.
    For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
    To use a particular application server to run the job, enter a specific target server.
    If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
    Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
    Define the jobu2019s steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
    Save the fully defined job to submit it to the background processing system.
    When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
    pls give points if it is usefull
    Regards
    Saimedha

  • Error in MRP Run- Background Job.

    Hi PP Gurus,
    I defined scope of planning for two plants and defined counter too. And set background job through Transaction code MDBT taking 24Hrs as Schedule selection parameter.
    When I'm accessing MDBT after 24Hrs system is throwing following messages in Scheduling log:
    1. Please check the destination for Parallel MRP (message no. MD251)
    Diagnosis of Message:
    No destination have been entered in Customizing or none of the destinations (application server) entered are active. In Customizing for MRP, you define the logical destinations (servers) to be used for parallel processing.
    2. Job cancelled after system exception ERROR_MESSAGE (Message no. 00564)
    Though I tried to enter to Customization through Message no. 1 but system is not allowing for it.
    What could be the problem. No help is available through any OSS note also.
    Please suggest the required solution in terms of Configuration or any other changes?
    Thanks & Regards,
    Abu Arbab

    Hi,
    Two more queries:
    1. If I don't want to go for Parallel Processing MRP, I don't have to select 'Parallel Processing' in Transaction code MDBT variant. But when I'm trying to change it system is not allowing me. It's not allowing me to go further without selection of it. What could be the reason behind it? Either Customization problem or any other?
    2. If set 'Parallel Processing destination' through Customization, system is giving only Development server as available destination and also Customization Request is getting generated. But the request is going to be transported to Production server. Since Parallel Processing destination was selected 'Development server' earlier and now MRP will run on 'Production server', it has to be changed to 'Production server'. But as already mentioned Customization Request will be getting generated and further it is freeze for Customization. How could get rid of these issues?
    Please come back with prompt comments.
    Thanks & Regards,
    Abu Arbab

  • Submitting background jobs using an excecutable program

    Hi all
    Would anyone give an example program to submit jobs in background using job_open, job_submit, job_close F.M's,
    please dont give complex coded program,  easily understandable code with some useful comments will be apprecieated.
    Thanks

    Create a job using job_open
    Create your job with JOB_OPEN. The module returns a unique job
    number. Together with the jobname, this number identifies the
    job. Other parameters are available, but are not required.
    JOBNAME = 'Freely selectable name for the job(s) you create'.
    CALL FUNCTION 'JOB_OPEN'
    EXPORTING
    JOBNAME = JOBNAME
    IMPORTING
    JOBCOUNT = JOBNUMBER
    EXCEPTIONS
    CANT_CREATE_JOB = 01
    INVALID_JOB_DATA = 02
    JOBNAME_MISSING = 03
    OTHERS = 99.
    IF SY-SUBRC > 0.
    <Error processing>
    ENDIF.
    Adding job step
    Add a job step: ABAP program
    CALL FUNCTION 'JOB_SUBMIT'
    EXPORTING
    AUTHCKNAM = SY-UNAME " Runtime authorizations
    " user
    JOBCOUNT = JOBNUMBER " Value from JOB_OPEN
    JOBNAME = JOBNAME " Value from JOB_OPEN
    REPORT = 'REPORT' " Report to be run
    VARIANT = 'VARIANT' " Variant to use with
    " report
    PRIPARAMS = USER_PRINT_PARAMS " User printing options
    ARCPARAMS = USER_ARC_PARAMS " User archiving options
    " Both sets of options
    " come from
    " GET_PRINT_PARAMETERS
    EXCEPTIONS
    BAD_PRIPARAMS = 01
    INVALID_JOBDATA = 02
    JOBNAME_MISSING = 03
    JOB_NOTEX = 04
    JOB_SUBMIT_FAILED = 05
    LOCK_FAILED = 06
    PROGRAM_MISSING = 07
    PROG_ABAP_AND_EXTPG_SET = 08
    OTHERS = 99.
    IF SY-SUBRC > 0.
    <Error processing>
    ENDIF.
    **Closing job
    Submit job for processing: immediate start
    CALL FUNCTION 'JOB_CLOSE'
    EXPORTING
    JOBCOUNT = JOBNUMBER " Job identification: number
    JOBNAME = JOBNAME " and name.
    STRTIMMED = 'X' " Schedules the job for
    " immediate start. The job
    " is started immediately
    " only if the user has the
    " RELE authorization to
    " release a job to run.
    IMPORTING
    JOB_WAS_RELEASED = JOB_RELEASED " If user has authorization
    " to release jobs to run, job
    " is automatically released
    " when it is scheduled. This
    " field is set to 'x' if the
    " job has been released.
    " Otherwise, the job is sche-
    " duled but must be released
    " by an administrator before
    " it can be started.
    EXCEPTIONS
    CANT_START_IMMEDIATE No longer used. Replaced by IMPORTING
    parameter JOB_WAS_RELEASED.
    INVALID_STARTDATE = 01
    JOBNAME_MISSING = 02
    JOB_CLOSE_FAILED = 03
    JOB_NOSTEPS = 04
    JOB_NOTEX = 05
    LOCK_FAILED = 06
    OTHERS = 99.
    IF SY-SUBRC > 0.
    <Error processing>
    ENDIF.
    *Please note it's not my original code..I have done what you could do!! Just visited help.sap.com and typed Background jobs and got sample codes..

Maybe you are looking for