Job Schedule Sun thru Thurs only via TVARV using variant

Can someone tell me how to use TVARV to setup my job to run only on Sunday thru Thursday using my variant?

Hi,
Please check the below links.
http://help.sap.com/saphelp_nw04/helpdata/en/c0/9803aae58611d194cc00a0c94260a5/content.htm
Some sample code from seachsap site.
Have you ever wondered where your TVARV variables are being used in your batch jobs? How do you know if they change, and the impact it may have on your interfaces? The program below will provide a listing for you.
The program uses Job Count (job id) as the key versus Job Name as job names can be redundant. The code was written in R/3 v.4.6C, but should work in 3.x versions as well.
Code
PROGRAM: ZCAUS_EXTRACT_REPORT_VARIABLES
AUTHOR:  DYLAN HACK
CREATE DATE: 10/09/2002
PURPOSE: This program was developed to extract all jobs based on the
         "Job Status" selection criteria and find the relevant TVARV
         variable entries. Then the report can be downloaded and
         sorted on selection variables. Ultimate purpose is to know
         what jobs are affected by the individual TVARV variables.
         If a job exists but does not have a corresponding entry/use
         of a TVARV variable, it will not get listed.
JOB STATUS LEGEND:
R: job step running.
Y: job step ready (eligible to run, waiting for a work process).
P: job step scheduled.
S: job step released (eligible to run when the start condition of the
   job is fulfilled).
A: job step aborted.
F: job step successfully finished.
Z: system upgrade in progress, only upgrade-related jobs are allowed
   to run. Jobs and job steps with this status are ignored by the
   scheduler.
X: unknown status detected.
REPORT ZCAUS_EXTRACT_REPORT_VARIABLES .
tables: tbtcp, tbtco.
data: var like RSVARVAR occurs 0 with header line,
      begin of report_tmp occurs 0,
        jobname   like tbtcp-jobname,
        jobcount  like tbtcp-jobcount,
        stepcount type tbtcp-stepcount,
        progname  type syrepid,
        variant   type syslset,
      end of report_tmp,
      report like report_tmp occurs 0 with header line,
      begin of listing occurs 0,
        jobname  type tbtcp-jobname,
        jobcount  like tbtcp-jobcount,
        stepcount type tbtcp-stepcount,
        progname  type syrepid,
        variant   type syslset,
        variable type rsvarvar-variable,
      end of listing.
selection-screen begin of block a1 with frame title text-001.
selection-screen begin of block b1 with frame.
  select-options: s_status for tbtco-status.
selection-screen end of block b1.
selection-screen begin of block b2 with frame.
  selection-screen comment /5(75) com1.
  selection-screen comment /5(75) com2.
  selection-screen comment /5(75) com3.
  selection-screen comment /5(75) com4.
  selection-screen comment /5(75) com5.
  selection-screen comment /5(75) com6.
  selection-screen comment /5(75) com7.
  selection-screen comment /5(75) com8.
selection-screen end of block b2.
selection-screen end of block a1.
initialization.
move:
'R: Job Running' to com1,
'Y: Job Ready (Eligible to run, waiting for process)' to com2,
'P: Job Scheduled' to com3,
'S: Job Released (Eligible to run when start condition is trigerred)'
to
com4,
'A: Job Aborted' to com5,
'F: Job Successfully Finished' to com6,
'Z: Upgrade in process, job being ignored' to com7,
'X: Unknown Status Detected' to com8.
start-of-selection.
get all jobs in released status
  select jobcount from tbtco into report_tmp-jobcount
    where status in s_status.
    append report_tmp.
  endselect.
get all related variants for those jobs that meet the where clause.
  loop at report_tmp.
    select jobname jobcount stepcount progname variant
    into  corresponding fields of report
    from tbtcp where jobcount = report_tmp-jobcount and
                     variant not like '&%' and
                     variant <> space.
    append report.
    endselect.
  endloop.
sort and delete duplicates (if any)
sort report by jobname jobcount stepcount progname variant.
delete adjacent duplicates from report comparing all fields.
get TVARV selection variables
loop at report.
clear var. refresh var.
  call FUNCTION 'RS_VARIANT_VARIABLES'
    EXPORTING
       PROGRAM = report-progname
       VARIANT = report-variant
    TABLES
     VAR = var
    EXCEPTIONS
        VARINT_NOT_EXISTENT.
move the data to a listing table
  if var-variable <> space.
   loop at var.
    move: report-jobname   to listing-jobname,
          report-jobcount  to listing-jobcount,
          report-stepcount to listing-stepcount,
          report-progname  to listing-progname,
          report-variant   to listing-variant,
          var-variable     to listing-variable.
    append listing.
   endloop.
  endif.
endloop.
sort and delete dups from listing
sort listing by jobname jobcount stepcount progname variant variable.
delete adjacent duplicates from listing comparing all fields.
data: count type i. loop at listing. count = count + 1. endloop.
write out the listing
write: 'Count', count. skip.
write: 2   'Job Name',
       36  'Job #',
       48  'Step',
       54  'Program name',
       95  'Variant',
       110 'Variable'.
loop at listing.
    write: / listing-jobname,
             listing-jobcount,
             listing-stepcount,
             listing-progname,
             listing-variant,
             listing-variable.
endloop.
Thanks,
Ramakrishna

Similar Messages

  • Reporting Agent Job Scheduling problem

    hi All,
    I am trying to schedule reporting agent job. I have few pre calculated webtemplates in one reporting agent scheduling package. when i try to schedule it and go to "start condition" - I want to put "After Event". I am selecting Event and giving the parameter name. But when i save and go out the job is already scheduled (checked in sm37). so I tried to chk the job condition again and the event i selected is not there !!!!
    I want to create after even condition and schedule that parameter via mainframe as our all job schedule through main frame only !!! can some one tell me why its not working with reporting agent ??
    I will definately assign the points.

    dinesh and SB,
    thank you for your reply. understood your point. but what i m asking is when i put "after event" criteria in the start selection... wouldnt it show that always when ever i go to Reporting Agent scheduling Package --> right click --> schedule --> start condition (i meant the event name and parameter should be saved there)
    but once i save it and get out from the scheduling package i can see the job has been scheduled but its not showing that its even controlled job !!!
    is it possible to use "after event" option in Reproting agent's job ?
    I have few queries under one Reporting Agent scheduling package which is added in one process chain - the PC is running once a month - i added RA at the end of the process chain and the variant will be schedule by mainframe once the process chain has completed successfully. now 2nd thing is: i need to run Reporting Agent job every single day. so need to schedule it twice. we schedule everything by main frame. so if i can save "after event" criteria then i can schedule that parameter by mainframe. the problem is the start condition is not saving my after event condition entries or parameter names.
    I hope i m clear. pl. guide its kind a urgent.

  • 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

  • Issue in Job Scheduling

    Hi Friends,
    I Developed a Bdc Program which is Daily backgroud Job Scheduled, But in my Program I am using GUI_DOWNLOAD to download
    the data which is in internal table to a flat file. Issue is the Background Job is failing, because iam using the FM-->GUI_DOWNLOAD
    so, Please help me is there any way to download the internal table data to a Flatfile without using FM-->GUI_DOWNLOAD. or pls
    help me with any links.
    Regards,
    Neetha
    Moderator message: FAQ, please search for previous discussions of this topic.
    Edited by: Thomas Zloch on Aug 4, 2011 12:03 PM

    The issue was with RFC user Authorization.

  • How to schedule a job Monday thru Friday only

    How can I schedule a job Monday thru Friday only?  I tried to use a Factory Calendar but we do not have any M-F calendars setup.  If I need to create a new factory calendar, how can I create on without any holidays?
    Thanks.
    Ryan

    Hi
    see this
    Create a Variant for the Program and
    Schedule JOB in background:
    Go to SM36 create a Job
    enter Program and Variant for that program in STEP..
    click on Start Condition
    Click on DATE and TIME enter date scheduled Start and END times
    click on Period Values
    Click on HOURLY/WEEKLY etc
    CLick on RESTRICTIONS also to use further criteria.
    so your job will be scheduled and run as per your requirement.
    and in SM37 Transaction check the status of that JOB
    Check this link for scheduling jobs..
    http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/3a7f87505211d189550000e829fbbd/content.htm
    Regards
    Anji

  • Want to run OWB mappings thru Autosys Job Schedule

    How can I execute OWB mapping (pl/sql code) thru the Autosys Job scheduler? Can you please provide some examples.
    Thanks, in advance
    Carol-Ann

    Pawan
    Process Flows in OWB get deployed to Oracle Workflow only. That is, Oracle Workflow Server is requried to run Process Flows.
    Process Flows can be run from sqlplus using the run_my_owb_stuff procedure, and Mappings can be run as written.
    A Process Flow is required if you have multiple Mappings that require to be strung together, and also if you require the management framework that comes along with Oracle Workflow.
    If the Mapping is self contained, then it can be scheduled standalone also. I personally prefer to have it done through process flows always.
    This is how my anonymous block looks like:
    declare n number; begin n := my_owb_run_pf('runtime_user','prcFlowModuleLocation','PROCESS','processName); end;
    - Jojo
    Message was edited by:
    user467494
    Message was edited by:
    user467494

  • Job with Multiple Schedule of same time & only one is executed, Why

    Hi ALL,
    I've Created a package to notify report in email  as excel, which is using a path to render report and save it as excel.
    This package was need to be schedule every first day of month and on every Friday even at morning 7 AM.
    So logically these are two events.
    But if we see on 1 May 2015 we have Friday and plus first day of month
    So technically this should fail.
    either for IO operation for render &
    storing data over same location with same file name.
    To replicate this i created two three schedule
    Below is the job history, job is invoked by only one schedule
    Question-
    1) Why one one schedule execute?
    2) why "sched2" only , it could be "sched3" only or "DentalOperationStackAndRank-Sched1" Only?
    Another this i result into error if different job executing same package at same schedule.
    FYI- package is deployed at database level
    HS

    Hi HS,
    As described in this
    article, more than one job can run on the same schedule, and more than one schedule can apply to the same job.
    And I make a test about your scenario, when configuring a SQL Server job with three schedules that reference same dates and times, my job behaves as yours that only one schedule is executed, but the job is invoked by schedule2 or schedule 3 in my environment.
    It is a normal behavior of SQL Server job in my opinion. For more details about such scenario, you can track the job following this
    blog.
    However, when I configure three jobs that run on the same schedule, everything works well and the three jobs all run successfully.
     I recommend you configure three different jobs that execute same package at same schedule .
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • Scheduled jobs are in released state only

    Dear Experts,
    we shedule jobs in background periodically. But for a particular time, all scheduled jobs are in released state only. Please suggest what might be the issue. Even some SAP std jobs have have not started.

    Hi Raghavendra,
    Have you checked enough BTC work process available in your SAP system.
    Use SM65 transaction,goto =>Additional Tests ;check mark "Determine work process status" and "Determine no of jobs in queue"
    and see the test results for any problems.
    Best Regards,
    Shyam Dontamsetty

  • How should i execute file transfer via batch job scheduling

    Hi guys,
        i want to call unix transfer script via batch job scheduling. Executing the system commands witin ABAP is as below:
             DATA: BEGIN OF ITAB occurs 0,
                         LINE(200),
                        END OF ITAB.
            UNIXCOMM = '/usr/sap/trans/data/*******'
            CALL 'SYSTEM' ID 'COMMAND' FIELD UNIXCOMM
                    ID 'TAB'     FIELD itab-sys.
    Now i plan to assign application server ('Exec Target') to it and let it implement in the background.
      Should i do it via batch job?
    Any info is appreciated very much.

    Instead of using
    CALL 'SYSTEM' u can use FM..
    SXPG_COMMAND_EXECUTE  .. in which u have to pass a command name which u can create or get from SM49...
    In CALL 'SYSTEM' .. u can not catch exceptions.. but in FM given above u can check
    SY-SUBRC, STATUS and EXITCODE  for successful  command execution..
    for successful command execution..
    sy-subrc = 0
    STATUS = 'O'  " Capital O
    exitcode = 0
    For batch scheduling, you can use this FM in a report  with one parameter for additional parameter which u need to pass to this FM  and create a JOB for that report and schedule it..
    I've used it and  find it useful even for batch scheduling..
    Reward if useful
    Regards
    Prax

  • 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

  • Help! job scheduled in DB13 cannot run successfully

    Hi! I am a basis administrator of an automobil company.
    Job scheduled in DB13 in our PRD system cannot run successfully.
    We have Central instance(ci) and Database instance(db) installed on seperated hosts. We use SUN cluster 3.1 technology.
    The problem occurs after my college restarted the whole system accidentally. After that, all the job scheduled in DB13 report the same error,job log looks like:
    Job started
    Step 001 started (program RSDBAJOB, variant &0000000000192, user ID ***)
    No application server found on database host - rsh will be used
    Execute logical command BRCONNECT On host orahost
    Parameters: -u / -c -f check
    BR801I BRCONNECT 6.20 (113)
    BR252E Function fopen() failed for '/oracle/PR1/sapcheck/cduuoiij.chk' at location main-8
    BR253E errno 2: No such file or directory
    I manually type the 'rsh' command on ci to invoke 'brconnect' on db. It works all right. And I check the rfc destination 'SAPXPG_DBDEST_ORAHOST' in sm59 , it's normal. There is no gateway instance on database server.
    The parameter 'SAPDBHOST' = orahost (the database server is  called orahost)
    the parameter 'SAPLOCALHOST' = cihost(the central instance is located on cihost)
    Any suggestion is very appreciated.
    Thx!

    Hi Joe,
    DB13 will run only on application server as for that matter any SAP program. It will then connect to database at OS level. I mean you normal reports also fetch data from database for which they have to connect to DB  but they all run on application server. The problem is coming in connection to database through the application layer.
    Please again review the OSS notes sent by Sunil and me. I think a greater focus on Sunil`s notes should help you out.
    Regards.
    Ruchit.

  • Unable to execute Copy or Delete from Job Scheduler job

    I am executing a COPY command and also a DEL command via the job scheduler and am receiving an "ORA-27370: job slave failed to launch a job of type EXECUTABLE ORA-27300: OS system dependent operation:accessing execution agent failed with status 233 ORA-27301:OS failure message:No process is on the other end of the pipe.ORA-27302:failure occurred at:sjsec 9 ORA-27303:additional information:No process is on the other end of the pipe." Any idea what is happening here? I receive the same error on any DEL or COPY command.
    Thanks,
    Susan

    Hi Susan,
    There are two possible issues here.
    - first make sure the scheduler extjob service is running, and try restarting it. That may fix the problem.
    - the second possibility is that the DEL or COPY are built-in commands and cannot be called directly. The Scheduler can only execute Windows executables, not built-in commands or batch scripts. The job_action (or program_action) must be of the form c:\path\program.exe .
    If the second is the case, you may need to use c:\windows\...\cmd.exe as your job_action and then as arguments, use
    /q
    /c
    del
    filename
    An example using a batch file instead of a command is
    SQL> begin
    2 dbms_scheduler.create_job('t1',
    3 job_action=>'C:\WINDOWS\SYSTEM32\CMD.EXE',
    4 number_of_arguments=>3,
    5 job_type=>'executable', enabled=>false);
    6 dbms_scheduler.set_job_argument_value('t1',1,'/q');
    7 dbms_scheduler.set_job_argument_value('t1',2,'/c');
    8 dbms_scheduler.set_job_argument_value('t1',3,'c:\temp\test2.bat');
    9 dbms_scheduler.enable('t1');
    10 end;
    11 /
    Hope this helps,
    Ravi.

  • KRONOS - EJB Job scheduler for Weblogic

    Paramus, NJ - February 22, 2002 - Indus Consultancy Services (ICS) today
    announced the latest in a series of improvements to Kronos Enterprise
    Scheduler, a full-featured job scheduling system written for the
    Enterprise Java (J2EE) environment.
    This version fixes some minor bugs reported by customers, and adds a new
    security feature to control user visibility to jobs, tasks, and
    schedules. A new environment setting allows the Kronos Enterprise
    Scheduler administrator to restrict users to seeing only those items
    which they have created. Administrators still have full visibility to
    all items.
    ICS is also proud to have Kronos Enterprise Scheduler competing in the
    Java Developer's Journal 2002 Readers' Choice Awards. Every year, Java
    Developer's Journal holds voting for products in a variety of
    categories. This year, Kronos Enterprise Scheduler is nominated in
    three of those categories:
    · Best Java Application (Standing as of 2/22/02 : 16th out of 69
    products with votes.)
    · Best Java Component (Standing as of 2/22/02 : 10th out of 26 products
    with votes.)
    · Most Innovative Java Product (Standing as of 2/22/02 : 21st out of 63
    products with votes.)
    To vote, visit the Java Developer's Journal website at
    <http://www.sys-con.com/java/readerschoice2002>
    To find out more about Kronos Enterprise Scheduler, and learn why
    companies around globe are selecting this powerful product to handle
    their scheduling needs, visit the ICS website at <http://www.indcon.com>
    and request a FREE 30-day evaluation.
    © 2002 Indus Consultancy Services, Inc. All rights reserved. Java and
    all Java-based marks are trademarks or registered trademarks of Sun
    Microsystems, Inc. in the U.S. and other countries. All other product
    and company names are trademarks of their respective owners.

    I would hope that BEA will step up and develop a replacement for their
    deprecated APIs. It is unfair to ask their customers to buy something they
    got previously for free. I also understand that the future EJB spec will
    contain scheduling features.

  • Job scheduling

    Hi Friends,
             i have a problem with job scheduling.
    two jobs need to be scheduled. (job1 and job2)
    i used
    job_open.
    submit job1 using parameters.
    job_close.
    then for second job.
    job_open.
    submit job2 using parameter2.
    job_close.
    when i go and look in sm37. i see when job1 is running the job2 is in release status.
    but what we need is when job1 is running job2 should be in schedule status. it should start only after job1 is completed.
    in the job2 job_close i used job1 as the PRED_JOBNAME.
    but i when i run the program job2 is in released status , not in schedule mode.
    is there any way we can make the job2 in scheduled mode instead of release.
    can we use event to control this. if yes please let me know how we can do it.
    Thanks

    Hi,
    As Appana wrote - i'm not sure there's a problem, but why don't u make one job with 2 steps? this way u will be perfectly sure that job2 (2nd step in the new job) will run only after job1 (1st step n the new job)...
    Good luck
    Igal

  • Internal error occurs in background job scheduling

    Hi Experts,
    We are facing an error message "Internal error occurs in background job scheduling" while trying to execute a custom report(Z report) in background in SA38.
    Please find the following observation on our side on this message.
    1) This message is not coming for only one report not for others.
    2) SU53 screen shot shows that SE38 check is failed, but the weird thing is not happening for other report.
    3) Persons having SE38 auhtorization are able to run this report.
    Please advise.
    Thanks in advance,
    Viven

    What is the message ID and number? Have you tried OSS search and debugging?
    What does this program do, in a nutshell?

Maybe you are looking for