TIME FRAME IN JOB SCHEDULING

Hi all,
I am doing job scheduling in background.
But i am not able to do it twice a day, it means every 12 hours it should be done automatically.
Can anyone suggest me how to do with code.
Thanks in advance
Venkat

Hi venkat,
1. In that case ,
2. U can schedule TWO different jobs,
(with the same program name and variant)
3. DAILY
AT TWO DIFFERENT TIMES.
regards,
amit m.

Similar Messages

Rwrun reports stop working after a period of time using a job scheduler

Hello, I am having a strange issue. We use either Control-M or Windows Task scheduler to run a VBS script that calls rwrun to generate multiple reports for multiple properties. Initially everything worked without issues then after about 2 months the VB Script running through Control-M started Failing. I could still run them from command line on the same server without Issues. So I set them up in Windows Task Scheduler and again they worked for about 3 weeks then started to Fail. Again I could still run the same scripts from command line on the server and have no issues. So we moved the scripts to another App server and went back to Control-M. This time after about 3 months the jobs started to fail. Moved them to Windows TS and again after about 1 week they started to fail. The TRACEALL shows nothing but I am getting this error in the hs_err_pidxxxx.log files that it creates. Does anyone know if some type of Temp location needs to be cleared or what my issue might be? Stumped at this point. Also point out the the servers were rebooted and no patches or modifcations where done to them before they start to fail. Thanks for any suggestions.
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x64CA84F2
Function=utqks2q+0x90
Library=e:\oracle\10gdevr2\bin\UTL.dll
Current Java thread:
     at oracle.reports.engine.EngineImpl.CRunReport(Native Method)
     at oracle.reports.engine.EngineImpl.run(EngineImpl.java:437)
     at oracle.reports.server.JobManager.runJobInEngine(JobManager.java:916)
     - locked <0x100a0040> (a oracle.reports.engine.EngineImpl)
     at oracle.reports.server.ExecAsynchJobThread.run(ExecAsynchJobThread.java:54)
Dynamic libraries:
0x00400000 - 0x00424000      e:\oracle\10gdevr2\bin\rwrun.exe
0x7D600000 - 0x7D6F0000      C:\WINDOWS\system32\ntdll.dll
0x7D4C0000 - 0x7D5F0000      C:\WINDOWS\syswow64\kernel32.dll
0x77BA0000 - 0x77BFA000      C:\WINDOWS\syswow64\MSVCRT.dll
0x7D930000 - 0x7DA00000      C:\WINDOWS\syswow64\USER32.dll
0x7D800000 - 0x7D890000      C:\WINDOWS\syswow64\GDI32.dll
0x004E0000 - 0x0057B000      C:\WINDOWS\syswow64\ADVAPI32.dll
0x7DA20000 - 0x7DB00000      C:\WINDOWS\syswow64\RPCRT4.dll
0x7D8D0000 - 0x7D920000      C:\WINDOWS\syswow64\Secur32.dll
0x66220000 - 0x6623C000      e:\oracle\10gdevr2\bin\nn.dll
0x64CE0000 - 0x64DBD000      e:\oracle\10gdevr2\bin\UIW.dll
0x64CA0000 - 0x64CB1000      e:\oracle\10gdevr2\bin\UTL.dll
0x64CD0000 - 0x64CD7000      e:\oracle\10gdevr2\bin\UTC.dll
0x60730000 - 0x607DC000      e:\oracle\10gdevr2\bin\oracore10.dll
0x608D0000 - 0x60963000      e:\oracle\10gdevr2\bin\oranls10.dll
0x62B40000 - 0x62B53000      e:\oracle\10gdevr2\bin\oraunls10.dll
0x60C40000 - 0x60C47000      e:\oracle\10gdevr2\bin\orauts.dll
0x71C00000 - 0x71C17000      C:\WINDOWS\system32\WS2_32.dll
0x71BF0000 - 0x71BF8000      C:\WINDOWS\system32\WS2HELP.dll
0x76AA0000 - 0x76ACD000      C:\WINDOWS\system32\WINMM.dll
0x77670000 - 0x777A9000      C:\WINDOWS\syswow64\ole32.dll
0x64CC0000 - 0x64CC9000      e:\oracle\10gdevr2\bin\UTJ.dll
0x64F10000 - 0x64F21000      e:\oracle\10gdevr2\bin\UIIM.dll
0x73070000 - 0x73097000      C:\WINDOWS\system32\WINSPOOL.DRV
0x77530000 - 0x775C7000      C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_5.82.3790.3959_x-ww_78FCF8D0\COMCTL32.dll
0x64ED0000 - 0x64EF6000      e:\oracle\10gdevr2\bin\UIOLE.dll
0x762B0000 - 0x762F9000      C:\WINDOWS\syswow64\comdlg32.dll
0x00580000 - 0x005D2000      C:\WINDOWS\syswow64\SHLWAPI.dll
0x7C8D0000 - 0x7D0CF000      C:\WINDOWS\syswow64\SHELL32.dll
0x663D0000 - 0x66414000      e:\oracle\10gdevr2\bin\CA.dll
0x66340000 - 0x6636A000      e:\oracle\10gdevr2\bin\mmc.dll
0x616B0000 - 0x61891000      e:\oracle\10gdevr2\bin\oraclient10.dll
0x62B60000 - 0x62B66000      e:\oracle\10gdevr2\bin\oravsn10.dll
0x60D30000 - 0x60DE8000      e:\oracle\10gdevr2\bin\oracommon10.dll
0x60300000 - 0x60720000      e:\oracle\10gdevr2\bin\orageneric10.dll
0x629C0000 - 0x629D2000      e:\oracle\10gdevr2\bin\orasnls10.dll
0x62B80000 - 0x62C86000      e:\oracle\10gdevr2\bin\oraxml10.dll
0x5C6C0000 - 0x5C6D1000      C:\WINDOWS\system32\MSVCIRT.dll
0x607E0000 - 0x608CC000      e:\oracle\10gdevr2\bin\oran10.dll
0x62000000 - 0x6202C000      e:\oracle\10gdevr2\bin\oranl10.dll
0x62030000 - 0x62042000      e:\oracle\10gdevr2\bin\oranldap10.dll
0x62090000 - 0x62184000      e:\oracle\10gdevr2\bin\orannzsbb10.dll
0x61E10000 - 0x61E52000      e:\oracle\10gdevr2\bin\oraldapclnt10.dll
0x61F30000 - 0x61F47000      e:\oracle\10gdevr2\bin\orancrypt10.dll
0x71BB0000 - 0x71BB9000      C:\WINDOWS\system32\WSOCK32.dll
0x76CF0000 - 0x76D0A000      C:\WINDOWS\system32\iphlpapi.dll
0x76B70000 - 0x76B7B000      C:\WINDOWS\system32\PSAPI.DLL
0x005E0000 - 0x0066B000      C:\WINDOWS\syswow64\OLEAUT32.dll
0x621A0000 - 0x621D7000      e:\oracle\10gdevr2\bin\oranro10.dll
0x621F0000 - 0x621FC000      e:\oracle\10gdevr2\bin\orantcp10.dll
0x61F70000 - 0x61F76000      e:\oracle\10gdevr2\bin\oranhost10.dll
0x61F20000 - 0x61F26000      e:\oracle\10gdevr2\bin\orancds10.dll
0x62210000 - 0x62216000      e:\oracle\10gdevr2\bin\orantns10.dll
0x60970000 - 0x60C31000      e:\oracle\10gdevr2\bin\orapls10.dll
0x62500000 - 0x62507000      e:\oracle\10gdevr2\bin\oraslax10.dll
0x627B0000 - 0x628B3000      e:\oracle\10gdevr2\bin\oraplp10.dll
0x618B0000 - 0x61905000      e:\oracle\10gdevr2\bin\orahasgen10.dll
0x622B0000 - 0x622E6000      e:\oracle\10gdevr2\bin\oraocr10.dll
0x622F0000 - 0x62315000      e:\oracle\10gdevr2\bin\oraocrb10.dll
0x71C40000 - 0x71C97000      C:\WINDOWS\syswow64\NETAPI32.dll
0x62A80000 - 0x62AF6000      e:\oracle\10gdevr2\bin\orasql10.dll
0x65050000 - 0x6576D000      e:\oracle\10gdevr2\bin\rw.dll
0x64AB0000 - 0x64AC4000      e:\oracle\10gdevr2\bin\ZRC.dll
0x66AC0000 - 0x66AC5000      e:\oracle\10gdevr2\bin\D2SC.dll
0x66810000 - 0x66A2B000      e:\oracle\10gdevr2\bin\DE.dll
0x627A0000 - 0x627AF000      e:\oracle\10gdevr2\bin\oraplc10.dll
0x64E30000 - 0x64E93000      e:\oracle\10gdevr2\bin\UIREM.dll
0x659A0000 - 0x659EE000      e:\oracle\10gdevr2\bin\ROS.dll
0x662F0000 - 0x66320000      e:\oracle\10gdevr2\bin\mmi.dll
0x64F50000 - 0x64F66000      e:\oracle\10gdevr2\bin\UICC.dll
0x662C0000 - 0x662DF000      e:\oracle\10gdevr2\bin\mms.dll
0x662A0000 - 0x662B0000      e:\oracle\10gdevr2\bin\mmv.dll
0x73AC0000 - 0x73AD8000      C:\WINDOWS\system32\AVIFIL32.dll
0x77B70000 - 0x77B84000      C:\WINDOWS\system32\MSACM32.dll
0x75FC0000 - 0x75FE2000      C:\WINDOWS\system32\MSVFW32.dll
0x66250000 - 0x6627E000      e:\oracle\10gdevr2\bin\mmw.dll
0x64FB0000 - 0x64FDA000      e:\oracle\10gdevr2\bin\UCOL.dll
0x665F0000 - 0x665F5000      e:\oracle\10gdevr2\bin\dfc.dll
0x66210000 - 0x66215000      e:\oracle\10gdevr2\bin\obs.dll
0x65010000 - 0x6503E000      e:\oracle\10gdevr2\bin\rws.dll
0x64AD0000 - 0x64C05000      e:\oracle\10gdevr2\bin\VGS.dll
0x7DBD0000 - 0x7DCD3000      C:\WINDOWS\WinSxS\WOW64_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.3959_x-ww_5FA17F4E\comctl32.dll
0x08000000 - 0x08139000      E:\oracle\10gdevr2\jdk\jre\bin\client\jvm.dll
0x10000000 - 0x10007000      E:\oracle\10gdevr2\jdk\jre\bin\hpi.dll
0x024E0000 - 0x024EE000      E:\oracle\10gdevr2\jdk\jre\bin\verify.dll
0x024F0000 - 0x02509000      E:\oracle\10gdevr2\jdk\jre\bin\java.dll
0x02510000 - 0x0251D000      E:\oracle\10gdevr2\jdk\jre\bin\zip.dll
0x05500000 - 0x0550F000      E:\oracle\10gdevr2\jdk\jre\bin\net.dll
0x7DB30000 - 0x7DBB0000      C:\WINDOWS\System32\mswsock.dll
0x76ED0000 - 0x76EFA000      C:\WINDOWS\system32\DNSAPI.dll
0x76F70000 - 0x76F77000      C:\WINDOWS\System32\winrnr.dll
0x76F10000 - 0x76F3E000      C:\WINDOWS\syswow64\WLDAP32.dll
0x76F80000 - 0x76F85000      C:\WINDOWS\system32\rasadhlp.dll
0x056C0000 - 0x056C6000      E:\oracle\10gdevr2\BIN\rwu.dll
0x5F270000 - 0x5F2CA000      C:\WINDOWS\system32\hnetcfg.dll
0x71AE0000 - 0x71AE8000      C:\WINDOWS\System32\wshtcpip.dll
0x06300000 - 0x06306000      E:\oracle\10gdevr2\jdk\jre\bin\ioser12.dll
0x76C10000 - 0x76C38000      C:\WINDOWS\syswow64\imagehlp.dll
0x6D580000 - 0x6D628000      C:\WINDOWS\syswow64\dbghelp.dll
0x77B90000 - 0x77B98000      C:\WINDOWS\syswow64\VERSION.dll
Heap at VM Abort:
Heap
def new generation total 576K, used 445K [0x10010000, 0x100b0000, 0x113c0000)
eden space 512K, 74% used [0x10010000, 0x1006f488, 0x10090000)
from space 64K, 100% used [0x100a0000, 0x100b0000, 0x100b0000)
to space 64K, 0% used [0x10090000, 0x10090000, 0x100a0000)
tenured generation total 2192K, used 1577K [0x113c0000, 0x115e4000, 0x20010000)
the space 2192K, 71% used [0x113c0000, 0x1154a448, 0x1154a600, 0x115e4000)
compacting perm gen total 4864K, used 4697K [0x20010000, 0x204d0000, 0x24010000)
the space 4864K, 96% used [0x20010000, 0x204a6670, 0x204a6800, 0x204d0000)
Local Time = Tue Dec 08 10:53:04 2009
Elapsed Time = 1
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.4.2_06-b03 mixed mode)
#

I realize this is an old post, however I've had the exact same issue over the last week with the same UTL.dll showing in the hs_err_pidxxxx file.
Our VB6 app ran as a Windows 2003 scheduled task for almost two years before stopping all of a sudden. It ran fine when logged on, but would fail when we logged off. The task would run, but the program would fail. While we never did get the scheduled task working properly, I did find an alternate solution.
Instead of using rwrun.exe I updated the code in our app to use rwclient.exe. The command for rwrun and rwclient are very similar with rwclient requiring a server= setting.
Oracle Reports Components Overview

Difference between dispatch time in po and scheduled time in job

Hi all ,
can any one please explain me
what is the exact difference between dispatch time maintained in po and time/date set for job schedule
here my question is ,i maintained dispatch time as send job with periodically in PO and i had maintained date/time in job process steps with some period.
when po message is triggered ,which time will be consider system.time specified in job schedule or dispatch time in Po.
which one consider first?
Thanks
konidala

Dispatch time that is set up as part of the message output condition records, drives at which event does the output be transmitted. Conversely, the date/time during the batch job set up is the time when the batch job must execute the program.
For example, if you had selected the dispatch time for output NEU in the PO to be '1' and you had set up ME9F program as a background job running daily once at 1PM, when the PO is created and saved at 10AM, the output type NEU will be triggered and will be held in queue. At 1PM when ME9F program is run as part of the background job, it'll pick up this output type for execution and transmission.

Expected schedule jobs in BO in time frame

Hello,
information about planed Jobs are all stored in CMS-DB (Crypted form). Is there any possibility to know what are all planed Jobs on the system for a time between X - Y. A kind of standard Reports or Graphic.
in The Acitivity reports. It s possible to know the failure rate of reports. Is it also possible to know which reports were failed because of missing capacity. ?? That means the reports were queed for the configured waiting time but the job server was busy for the wohle time. Consequently it failed ..

Yes there are some report in system folder. These reprots are based on activity universe. Try opening the report which shows the refresh time of reports. Modify the logic a bit and u will be able to get what u want.

Changing job schedule time

Hi,
I have scheduled a job to execute at a specific time daily.
But now I want to change the execution time, job will execute daily.
How to do that ?
Regards,
Amit R.

hi,
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 youve 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.
i got this from link,
http://help.sap.com/saphelp_nw04/helpdata/en/c8/6a56389f64246fe10000009b38f889/frameset.htm
Regards,
Arunsri

Requested start time during job scheduling population in local time.

Hello Experts,
Could you please help on the issue.
Requested start time during job scheduling populated with local time even though we have assigned the GMT time zone.
Could you please help , how to change the settings of request start time calender icon to populate the GMT time.
thanks,
Suresh.

Hello Gerben,
Thanks for the reply, even though the default time zone set as GMT in user settings, the requested start time calender pop up the local time instead of GMT time.
Previously requested start time poped up the GMT time, we have observed this change once we have ran the redwood script for time window elements change and imported some of the job definitions, applications & time windows from other system.
Below is the script we have ran thought shell script
Script Fuctionality
1. Take the mentioned time window
2. iteratate thought the time window elements and add 1 hour to the "time to day from" & "time to day to" parameters.
3. set the changed parametes to time window and persist the changes.
// Variable Declarations
String timewindow = null;
String query = null;
TimeWindow tw = null;
TimeWindowElement twe = null;
long otdvalue = 3600000;
long l1 = 0;
long l2 = 0;
long threshold = 0 ;
long expvalue = 82800000;
long expvalue1 = 85500000;
long indto1 = 0;
long indfrom1 = 300999;
long indto2 = 2700000;
long indfrom2 = 3000999;
Job job = null;
//Declare all the time windows in array
String[] timewindows = {"XX_TIMEWINDOW_01_GMT"};
          for( int i = 0 ; i < timewindows.length; i++)
          timewindow = timewindows<i>;
          jcsOut.println("TimeWindow"i":"+timewindows<i>);
          tw = jcsSession.getTimeWindowByName(timewindow);
          for (Iterator it1 = tw.getTimeWindowElements(); it1.hasNext();)
               twe = (TimeWindowElement) it1.next();
               Long otd = new Long(otdvalue);
               jcsOut.println("************************");
               jcsOut.println(twe.getTimeOfDayFrom());
               jcsOut.println(twe.getTimeOfDayTo());
               jcsOut.println("************************");
               Long todf = (Long) twe.getTimeOfDayFrom();
               Long todt = (Long) twe.getTimeOfDayTo();
                                  threshold = todf.longValue();
                        // if timeday from equal to 23 GMT assign the 0 GMT
                                  if(threshold == expvalue )
                jcsOut.println("timewindow with 23 GMT");
               l1 = indto1;
               l2 = indfrom1;
                        //if timedayfrom equal to 23:45 GMT assign 0:45 GMT
               else if(threshold == expvalue1)
               jcsOut.println("timewindow with 23:45 GMT");
               l1 = indto2;
               l2 = indfrom2;
                        // Add 1 hour for current time of day from
               else
               l1 = todf.longValue() + otdvalue;
               l2 = todt.longValue() + otdvalue;
               Long ll1 = new Long(l1);
               Long ll2 = new Long(l2);
               twe.setTimeOfDayFrom(ll1);
               twe.setTimeOfDayTo(ll2);
               jcsOut.println("After Change:"+ twe.getTimeOfDayFrom());
               jcsSession.persist();
Once after the script competetion the time window time zone remains in GMT.
Could you please check script once and help us the time zone change caused the by script or not?
Thanks,
Suresh

SQL Server Agent Job Scheduler- Set time less than 10 seconds

Hi,
Could any one please let me know how to change the SQL server agent Job scheduler time to less than 10 secs?
I wan to schedule a SSIS package run for every 5 secs.
Thanks..

Be careful, it is a bad idea to blindly just issue a new package run without knowing whether the previous package ended.
It may lead to locking/dead-locking.
Now re the Agent: the seconds are not exposed at all, why you say 10?
But, there is a way, not through the UI, explained there:http://stackoverflow.com/questions/5569415/is-there-a-way-to-set-a-sql-server-job-scheduled-to-run-every-30-seconds + http://www.sqlservercentral.com/articles/Administration/sqlserverjobscheduling/2288/
PS you can have it every sec
Arthur My Blog

Job Scheduler Timer issue in Cisco Prime Infrastructure 1.2 ?

Has anyone run into this issue where the job scheduler in CPI 1.2 report that the job that is being scheduled is before the current time even though it isn't ?
This only started happening after our time change yesterday. The system is setup for the correct time (NTP) this is confirmed in the app and also on the CLI console access (show clock)
Anyway we get this error message (attachment) in the lower right corner of the attachement.
It's not allowing the jobs to be scheduled. Rebooted the system yesterday and thought that it fixed it, but evidently I tried another scheduled job today and it's got the same issue.
TAC Case is already opened on this but I thought I'd ask here as well.
Regards,
Tom W.

I'm answering my own question: upgrade to 1.3 from 1.2 and the problem is resolved. Rebooting the VM on 1.2 did help for 1 day but then the problem came back, so my advice is simply to upgrade to 1.3 which I would have done initially if I had known that 1.3 was available. Hope this helps. The problem itself in 1.2 is unclear what is causing it because NTP and the APP and the underlying time in the console (cli) are all good; so somewhere in the scheduler it may have gone off track after the daylight savings time shift this past week. Bottom line: 1.3 upgrade and keep hope alive, bro.

FTP Adapter restrict polling frequency active time frame in a day

Hi All,
Is there anyway I can restrict FTP adapter polling frequency to be active during a particular time frame of the day. Say, my service should poll the incoming location for Sales order data for every hour during business hours of the day.
Thanks,
AG

Hi
SOA Suite 12c will expose Oracle ESS as the scheduler.
ESS will allow you to schedule soa composites / OSB services etcand allow you to enable / disable them based on jobs, which is what you desire.
12c SOA Suite is expected later this Summer.
Cheers
iain

Run steps in a chain at a specific time frame

I've got an ETL process running in a scheduler chain. First steps are extracting data from remote servers. Each remote server has it's own time frame in which I can extract the data. Once the window is closing I need to kill the job immediately.
My question is, Is it possible to define a time frame for single steps in a chain ?
Other options i'm considering (but all are less favorable)
Create a job with max_run_duration for each extraction step and manually time the transformation / load chain steps after. Advantage - simple, Disadvantage - A lot of ideal time.
Same as above but make the transformation / load chain with an event based job to when all extraction jobs are done. Advantage - Less ideal time, Disadvantage - More complex, error prune.
These two options requires a sniper job to catch JOB_OVER_MAX_DUR event and kill the job.These options also require breaking up the chain - something I would like to avoid. Another option that keeps the chain intact is
Defining the step rule with a time based condition (and using low evaluation_interval ~ 60 seconds) But then I cannot set max_run_duration and there for cannot stop the job if it's working when the time frame is closing.
I would appreciate any ideas on solving this problem.

Hello,
You can for instance execute the following when you create your Refresh Group:
BEGIN
DBMS_REFRESH.MAKE(
name => '"{color:red}schema{color}"."{color:red}refresh_group_name{color}"',
list => '',
next_date => TRUNC(SYSDATE) + 1 + 1/24,
interval => 'TRUNC(SYSDATE) + 1 + 1/24',
implicit_destroy => FALSE,
lax => FALSE,
job => 0,
rollback_seg => '{color:red}rollback_segment{color}',
push_deferred_rpc => TRUE,
refresh_after_errors => TRUE,
purge_option => NULL,
parallelism => NULL,
heap_size => NULL);
END;
/Then you add your MV to the Refresh Group as follow:
BEGIN
DBMS_REFRESH.ADD(
name => '"{color:red}schema{color}"."{color:red}refresh_group_name{color}"',
list => '"{color:red}schema{color}"."{color:red}MV_name{color}"',
lax => TRUE);
END;
NB: The syntax and option can change with the Release (this syntax is well tested on 8.1.7).
Hope it can help.
Best regards,
Jean-Valentin
Edited by: Lubiez Jean-Valentin on Dec 16, 2009 9:04 AM

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 jobs 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 systems 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 jobs 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 jobs 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 youve 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

Job Scheduling in Solution Manager - Error creating Periodic Job

Hi all,
I am in the process of testing the Job Scheduling functionality using the Solution Manager. I have setup the criteria manager, ec. in the satellite system, and done the config in Solman as well.
I am able to successfully setup up a 'on-time' job.
it's only when I try to setup a periodic job, I end up getting following error
Any thoughts? Is there any piece of config that's missing? All the SICF services needed for this functionality are running fine.
Thanks for the help.
500 Internal Server Error
Error when processing your request
What has happened?
The URL https://fsspsm.target.com:/sap/bc/webdynpro/sap/wd_ags_ejr_job_req_gaf_app was not called due to an error.
Note
The following error text was processed in the system PSM : Message was not created
The error occurred on the application server fsspsmap01_PSM_00 and in the work process 1 .
The termination type was: ERROR_MESSAGE_STATE
The ABAP call stack was:
Function: BAPI_NOTIFICATION_CREATE of program SAPLDSWP_NOTIF
Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
Method: SUBMIT_REQ_CRM_DATA of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
Method: SUBMIT of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
Method: PROCESS_SCENARIO_PERIODIC of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: PROCESS_JOB_SCENARIO of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: IF_AGS_EJR_JSM_PROC_FPM_CTRL~AFTER_PROCESS_EVENT of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
Method: IWCI_IF_FPM_APP_CONTROLLER~AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
Method: CALL_UIBB_PROCESS_EVENT of program CL_FPM========================CP

Hello,
This is the basic Job Scheduling functionality and not the Redwood Job scheduling, correct?
Have you performed the IMG Activiteis in SPRO?
See the following Help link:
http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/c5/7edcbd58ce4e29bc1baf1c4761d71f/frameset.htm
Change a job
You can change the scheduling of a job as long as it has not been completed. Proceed as follows:
Make changes.
Note
When you change a periodic job, the system searches for the changeable successor and only changes this successor.
If there is more than one changeable job with the same name, the system does not change any of these jobs.
End of the note.
Save your entries.
To release the job in the target system, select Release.
You go to the transaction SM37 in the target system.
You just may want to ensure HTTP Services have been enabled. I realize you said the services workin SICF, but this needs to be verified as 500 Internal Server Error most often means the HTTP services are not activated.
Regards,
Paul

Error in Backup job scheduling in DB13

Hi All
Backup job scheduled in DB13 kicks error ,I am using Oracle as database and ERP6.0
database and application are on diffrent servers.Before it was working fine,I didn't changed any password
I can run backupjob sucessfully directly from BRtools on database server.Please provide any hint
Job started
Step 001 started (program RSDBAJOB, variant &0000000000060, user )
No application server found on database host - rsh/gateway will be used
Execute logical command BRBACKUP On host DLcSapOraG08
Parameters:-u / -jid INLOG20090120204230 -c force -t online -m incr -p initerd.sap -w use_dbv -a -c force -p in
iterd.sap -cds -w use_rmv
BR0051I BRBACKUP 7.00 (31)
BR0128I Option 'use_dbv' ignored for 'incr'
BR0055I Start of database backup: bdztcorv.ind 2009-01-20 20.42.31
BR0484I BRBACKUP log file: D:\oracle\ERD\sapbackup\bdztcorv.ind
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance ERD failed
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance ERD failed
BR0056I End of database backup: bdztcorv.ind 2009-01-20 20.42.32
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0054I BRBACKUP terminated with errors
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0291I BRARCHIVE will be started with options '-U -jid INLOG20090120204230 -d disk -c force -p initerd.sap -cds -w use_rmv'
BR0002I BRARCHIVE 7.00 (31)
BR0181E Option '-cds' not supported for 'disk'
BR0280I BRARCHIVE time stamp: 2009-01-20 20.42.33
BR0301W SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310W Connect to database instance ERD failed
BR0007I End of offline redo log processing: adztcorw.log 2009-01-20 20.42.32
BR0280I BRARCHIVE time stamp: 2009-01-20 20.42.33
BR0005I BRARCHIVE terminated with errors
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.33
BR0292I Execution of BRARCHIVE finished with return code 3
External program terminated with exit code 3
BRBACKUP returned error status E
Job finished

Hi,
not sure if the recommendations given will address this issue.
You are getting this error:
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
the log file indicates:
> No application server found on database host - rsh/gateway will be used
This indicated that the user that is connecting from the AS to the DB server is not properly configured to perform the DB tasks on it.
So, first question would be to know if you have configured a gateway on the DB server and how, or if you are using remote shell.
Second question, you can do backups on the DB server.
> I can run backupjob sucessfully directly from BRtools on database server
How did you run exactly the backup job (what is the exact command line, what is the exact OS user that executed it)?
What is the OS of the DB server?
I have reread your post, your OS is windows therefore you fall in the "typical" error in Windows.
You have executed your backup as <sid>ADM and it works. Unfortunatelly, in windows, SAP is exectuted by SAPSERVICE<sid>, and this is the user who should be connecting to your DB server, and this is the user who cannot execute the backup.
The fact that you can run the backup with <sid>ADM in Windows does not means that you have SAPService<sid> properly configured.
For the error (see before) I think your ops$ user for this user is not properly configured in the DB server. take a look at the note mentioned by KT and pay attention to the SAPSERVICE<sid> configuration
Edited by: Fidel Vales on Jan 24, 2009 12:45 AM

Regarding Background Job scheduling for file to file scenario

Hi Guru's
Good morining all of u
I have one doubt on ...
can we do background job scheduling for file to file scenario?
Please give me response as early as possible.
thanks and regards
sai

background jobscheduling for file adapter...
you can schedule the file adapter according to your requirement as follows:
In the Communication Channel Monitoring Locate the link Availability Time Planning, In Availability Time Planning, choose the Availability time as daily and say create, give the time details, select the communication channel in your case file adapter , goto the Communication Channels tab and filter and add the respective channel, save it
/people/shabarish.vijayakumar/blog/2006/11/26/adapter-scheduling--hail-sp-19-

Hi any one please explain background job scheduling

Hi any one please explain background job scheduling . Good answer can be rewarded.
Thanks

Background jobs are pgms that are scheduled to be run in the Background without user interaction. So this can be done only for Type 1(executable) Program and not for Module-Pool Programs. Typically, a variant is defined and the pgm is run using the same.
The transaction code is sm36 -Define Background job. Using the Start Condition tab you can define when you want the job to run (specific time or if it has to follow after a particular job is done etc.,) Using the Step tab you can assign the pgm name and variant.
After the job is scheduled, you can check the status in sm37, along with the Job log and Spool.
For more info:
http://help.sap.com/saphelp_bw30b/helpdata/en/c4/3a7f87505211d189550000e829fbbd/content.htm

TIME FRAME IN JOB SCHEDULING

Similar Messages

Maybe you are looking for