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.

Similar Messages

  • Expecting a response within a specified time frame

    I need urgent help please.
    I am expecting some data from the server within 20 seconds.
    If I dont receive this data within the time frame,I exit from
    the application else If i receive this data I will display it.
    Please can any write a small example for this threading concept.
    I am very new to this.
    Ajay

    Let suppose this is your communication dialog window:
    call createTimer(int sleep) after you send a request to the server
    class MyDialog  extends JDialog implements ActionListener
        private javax.swing.Timer   m_timer    = null;
        public MyDialog(*********)
            super(*********);
            addActionListener(this);
        private void createTimer(int sleep)
            m_timer = new javax.swing.Timer(sleep, this);
            m_timer.setRepeats(false);
            m_timer.start();
        public void actionPerformed(ActionEvent e)
            if(e.getSource() == m_timer)
                // check your "response flag"
    }lic void actionPerformed(ActionEvent e)
    if(e.getSource() == m_timer)
    // check your "response flag"

  • Expecting a respone withing a specified time frame

    I need urgent help please.
    I am expecting some data from the server within 20 seconds.
    If I dont receive this data within the time frame,I exit from
    the application else If i receive this data I will display it.
    Please can any write a small example for this threading concept.
    I am very new to this.
    Ajay

    Say, you wouldn't want someone here to do something so unethical as to do your homework assignment now would you?
    see java.util.Timer and java.util.TimerTask

  • Schedule Job Execution problem

    Hi All,
    The schedule jobs are taking more time.... to complete
    We have schdule jobs which will run for every hour,soo to execute the job sometimes it is taking 1hr and sometime 30mins
    please help me to have the Job execution total time to be constant to near 30mins.

    preethi wrote:
    Hi All,
    The schedule jobs are taking more time.... to complete
    We have schdule jobs which will run for every hour,soo to execute the job sometimes it is taking 1hr and sometime 30mins
    please help me to have the Job execution total time to be constant to near 30mins.Thread: HOW TO: Post a SQL statement tuning request - template posting
    HOW TO: Post a SQL statement tuning request - template posting

  • BI Publisher Bursting sending Email even after I delete schedule job

    I am facing some weird issue in BI Publisher. We have a BI Publisher report and we are using Bursting query to burst the report to destination Email. It works fine when i run manually. It also worked fine when i schedule it first time for particular time. few days ago client wanted to change the scheduling time. Since there is no way to modify the scheduling time, i deleted the old schedule jobs from BI Publisher as well as i truncated the following tables from DB where it stores scheduling job information.
    XMLP_SCHED_JOB
    XMLP_SCHED_OUTPUT
    XMLP_SCHED_SUBSCRIPTION
    I also created the new scheduling job based on new time. The issue is Clients are getting the emails in old time as well as new scheduling timel. I can see the new scheduling information in following table so no information of old scheduling time. How BI Publisher is still running the report on old time. I research a lot but still i am not able to find the place from where it is still sending the old emails. Can anyone please have any idea to resolve this?

    Did you delete the job schedule using the GUI first? Otherwise by manually deleting the records from XMLP_ tables
    may somehow have corrupted the scehduling option.
    There are other components for the scheduler which are not only saved in XMLP_ tables and these
    are the QUARTZ tables.
    As of release 11g there is not mechanism to manage BIP scheduler tables.
    regards
    Jorge

  • How to Schedule Jobs to only run during a time window

    I have a long running task that needs to schedule jobs to process data.
    I only want these scheduled jobs to start during a specific window of time each day, probably 10:00 PM to 6:00 AM.
    If the scheduled jobs do not begin during the specified time frame, they must wait until the next day to start running.
    Each scheduled job will only be executed once and then auto dropped.
    How should I go about creating these scheduled jobs?

    Hi Jeff,
    I agree that the documentation isn't clear enough about the purpose of windows.
    You can indeed use windows for changing the resource plan, but you can also use them for scheduling your jobs.
    I did a simple test in real-time to illustrate the latter.
    At around 10.30 am today I created a table that will populated by a job:
    CREATE TABLE TEST_WINDOW_TABLE(EVENT_DATE DATE);
    Then, I created a window whose start_date is today at 10.40 am :
    dbms_scheduler.create_window(
                                 window_name     =>'TEST_WINDOW',
                                 resource_plan   => NULL,
                                 start_date      => to_date('10/04/2014 10:40:00', 'dd/mm/yyyy hh24:mi:ss'),
                                 repeat_interval => NULL,
                                 duration        =>interval '5' minute
    You can see that this window doesn't have a resource plan, and its repeat interval is NULL (so it will be opened only once).
    The window will stay open for 5 minutes.
    Finally, I created a one-off job whose schedule is the previously created window:
    DBMS_SCHEDULER.create_job (
                               job_name      => 'TEST_WINDOW_JOB',
                               job_type      => 'PLSQL_BLOCK',
                               job_action    => 'BEGIN insert into test_window_table values (sysdate); COMMIT; END;',
                               schedule_name => 'SYS.TEST_WINDOW',
                               enabled       => true,
                               auto_drop     => true
    Checking the user_scheduler_job_log before 10.40 would return no rows, which mean the job hasn't started yet since the window was not open.
    Now, from 10.40, it shows one entry:
    SQL> select log_date, status from user_scheduler_job_log where job_name = 'TEST_WINDOW_JOB';
    LOG_DATE                                                                         STATUS
    10/04/14 10:40:02,106000 +02:00                                                  SUCCEEDED
    The TEST_WINDOW_TABLE has also got the row:
    SQL> select * from TEST_WINDOW_TABLE;
    EVENT_DATE
    10/04/2014 10:40:02
    Voilà.
    In your case, since you want to run the jobs daily between 10 pm and 6 am (duration of 8 hours), the window would look like this:
    dbms_scheduler.create_window(
                                 window_name     =>'YOUR_WINDOW',
                                 resource_plan   => NULL,
                                 repeat_interval => 'freq=daily;byhour=22;byminute=0;bysecond=0',
                                 duration        =>interval '8' hour
    For your jobs, you may need to specify an end_date if you want to make sure the job gets dropped if it couldn't run in its window.

  • Scheduled jobs do not run as expected after upgrading to 10.2.0.3 or 4

    FYI, we've had a ticket open for several days because our scheduled jobs (dbms_scheduler) would no longer run as scheduled after an upgrade to 10.2.0.4 on HPUX, couldn't find the solution by searching in metalink, nor did I find it here or using Google - obviously I wasn't searching correctly. There is a note id that references a set of steps that appears to have resolved our problem. I am putting this note out here so that if you encountered the same difficulty you may come across this note earlier in your troubleshooting efforts rather than later. The full title of the note is: 'Scheduled jobs do not run as expected after upgrading to either 10.2.0.3 or 10.2.0.4'. The Doc ID is: 731678.1.

    Thanks - our ticket should be getting closed out on it (our dba will be updating it), the scheduler has been running reliably since we took the steps in the doc mentioned.

  • Event based scheduler job - 2 events at the same time only 1 run

    Hi,
    i converted our dbms_job - jobs to the newer package dbms_scheduler.
    It is a 10.2.0.4 patch 23(8609347) database on an windows server 2003 R2 Enterprise x64 Edition SP2.
    The Jobs(about 130) are nothing special ... only some statistics, matview-refreshes and so on.
    For the notification of failed jobs and jobs which run over the max_run_duration i downloaded and installed the job notification package.
    The jobs are assigned to different departments and the corresponding developer teams in our company.
    I created a notification job for each department and if a job fails we (the database administrators) and the corresponding deverlopers will be informed.
    Now i ascertained that only 1 email will be send if 2 jobs of the same department fails at the same time.
    The emailer-jobs are auto-generated by the job notification package. I only modified them to look after all jobs of special department and not only after one job. (--> event_condition ... object_name LIKE 'XXX%')
    example for dba-jobs(copy of the script output of TOAD):
    SYS.DBMS_SCHEDULER.CREATE_JOB
           job_name        => 'DBA_JOBS_EMAILER'
          ,start_date      => NULL
          ,event_condition => tab.user_data.object_name LIKE ''DBA%'' AND tab.user_data.event_type in (''JOB_FAILED'',''JOB_OVER_MAX_DUR'')'
          ,queue_spec      => 'SYS.SCHEDULER$_EVENT_QUEUE, JOB_FAILED_AGENT'
          ,end_date        => NULL
          ,program_name    => 'SYS.EMAIL_NOTIFICATION_PROGRAM'
          ,comments        => 'Auto-generated job to send email alerts for jobs "DBA%"'
        );I thought that a queue is used to manage all events from the scheduler jobs. So i made a test with 2 dba jobs and simulated a failure at the same time but i received only one mail.
    So what is happend with the second event? I looked for the events in the qtab(SCHEDULER$_EVENT_QTAB) which belongs to the event queue(SYS.SCHEDULER$_EVENT_QUEUE) and no event was missing.
    So i think the emailer job has to run 2 times.
    Is anyone able to explain or to find my mistake?
    I know that the easiest way is to create one emailer job for each normal job but i think this is a little bit costly because all the arguments are the same for one department.
    Thanks & Regards

    Thanks for your fast answer.
    You are right with the "enabled => TRUE;" part and i only forgot to post it.
    So the Job is enabled (otherwise it would not send any mail). Because it is sending one mail i think it is also not necessary to hand over a job_type.
    Additionally the job starts a program ... so it is right to set the job_type='STORED_PROCEDURE' isn't it?
    And also right ... i already added the agent as subscriber to the queue.
    Anyway i think the whole thing do what it have to do. So in my oppinion there are no big mistakes in creating the job or at adding the subscriber.
    There are also no problem in raising the events by itself and enqueue them in the scheduler event queue.
    There is only a problem when 2 jobs fails (or run out ouf max duration) at exactly the same time.
    If i understand it right:
    The agent/subscriber will find the "JOB_FAILED"-event for the first Job in the queue and starts the emailer Job.
    The agent will also find the "JOB_FAILED"-event for the second Job and wants to start the emailer Job again.
    I don't know if this is really the problem but perhaps the emailer-job can not be started in consequence of the second event because ist is already running.
    I also don't know if this is a mistake of the agent or of the emailer-job by itself.
    I only want that it runs two times (one run for each event). I my case it also doesn't matter which email is send at first.

  • Scheduler Jobs that run between certain times?

    Is there an easy way to query which dbms_scheduler jobs run between any given times?
    If I look at repeat_interval in user_scheduler_jobs, for example, I've got things like "FREQ=DAILY; BYHOUR=14,16,18,20,8,10,12; BYMINUTE=30" and "FREQ=HOURLY; INTERVAL=2;" and "FREQ=DAILY;", and it's not therefore clear to me how I could write a query that would find which jobs run between (say) 17:00 and 19:00.
    Is there a function, or a neat bit of sql, that will 'explode' the repeat interval (presumably, in the case of the last two examples above, with reference to the start_date) into standardized times which I could then query? Or is there some other way of doing it?

    There are no schedules used here. The repeat interval is specified for all jobs at the time of creating the job.
    Besides, that wouldn't address the issue, even so. Even if schedules are in use, they declare their repeat interval in the form "freq=daily;byhour=3,4,5,6;byminute=0;bysecond=0", stored in a text field. Exactly the same, in fact, as the repeat_interval column in the user_scheduler_jobs column.
    So how do you derive from that the knowledge that the job can run some time between 2 and 8AM?
    I want to list all jobs which might start between those two times, but I do not know syntactically or logically how it is possible to query either user_scheduler_jobs or all_scheduler_schedules to select all rows where repeat_interval "is somehow covered by the time range 2 to 8".
    Thanks for replying, though.

  • 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

  • Troubled to get scheduler job to run?

    Hi all friends:
    I'm having trouble getting any scheduler jobs (here, troubled job name is CUSTMASTER_CHANGES_01) to actually run.
    when
    sql>select job_name,state,enabled,retry_count,failure_count,run_count,restartable,start_date,repeat_interval,job_class
    from all_scheduler_jobs;
    JOB_NAME STATE ENABL RETRY_COUNT FAILURE_COUNT RUN_COUNT RESTA START_DATE REPEAT_INTERVAL JOB_CLASS
    CUSTMASTER_CHANGES_01 SCHEDULED TRUE 0 0 0 FALSE 14-JAN-08 09.46.14.6 FREQ=SECONDLY;I SCANNER_JO
    72965 AM AMERICA/NEW NTERVAL=5 B_CLASS
    _YORK
    for job 'CUSTMASTER_CHANGES_01'
    we can see RUN_COUNT 0 and restartable false.
    I upped slave processes to 5. dbms_scheduler.run_job('CUSTMASTER_CHANGES_01') works, but it's still not executing on the schedule
    when run as sysdba
    SQL> exec dbms_scheduler.run_job('CUSTMASTER_CHANGES_01');
    ERROR at line 1:
    ORA-27475: "SYS.CUSTMASTER_CHANGES_01" must be a job
    ORA-06512: at "SYS.DBMS_ISCHED", line 150
    ORA-06512: at "SYS.DBMS_SCHEDULER", line 441
    ORA-06512: at line 1
    to resolve that,
    we found
    When you create your job by using dbsm_scheduler, it has a parameter called ‘auto_drop’, is by default, =’true’, like, auto_drop => TRUE
    see below;
    dbms_scheduler.create_job(
    job_name IN VARCHAR2,
    job_type IN VARCHAR2,
    job_action IN VARCHAR2,
    number_of_arguments IN PLS_INTEGER DEFAULT 0,
    start_date IN TIMESTAMP WITH TIME ZONE DEFAULT NULL,
    repeat_interval IN VARCHAR2 DEFAULT NULL,
    end_date IN TIMESTAMP WITH TIME ZONE DEFAULT NULL,
    job_class IN VARCHAR2 DEFAULT 'DEFAULT_JOB_CLASS',
    enabled IN BOOLEAN DEFAULT FALSE,
    auto_drop IN BOOLEAN DEFAULT TRUE,
    comments IN VARCHAR2 DEFAULT NULL);
    The job you manually run once and then it drops itself when you test.
    so I am specifiying auto_drop to be false, but it is showing it has true as the attribute.
    DBMS_SCHEDULER.CREATE_JOB(
    job_name => scanner.scanner_name,
    job_type => 'PLSQL_BLOCK',
    job_action => 'BEGIN IF EEG_SCAN.GET_RUNNING_JOBS_COUNT('
    ||''''||UPPER(scanner.scanner_name)||''''
    ||') < 2 THEN '||scanner.scanner_proc_name||'; END IF; END;',
    repeat_interval => 'FREQ=SECONDLY;INTERVAL=5',
    job_class => c_job_class_name,
    auto_drop => FALSE,
    enabled => true
    scheduler job is still not working as expected.....?
    Can you help me for this??
    thanks a lot in advance.
    Message was edited by:
    jerrygreat
    Message was edited by:
    jerrygreat

    Hi,
    There are a few other limits you could check .
    Make sure that you have not exceeded the maximum number of sessions or the maximum number of processes or the maximum number of scheduler jobs
    select * from dba_scheduler_global_attribute;
    and
    select name,value from v$parameter where name like '%process%';
    select name,value from v$parameter where name like '%session%';
    Also check how many jobs are currently running
    select count(*) from dba_scheduler_running_jobs;
    select count(*) from dba_jobs_running ;
    select count(*) from v$session ;
    One of these limits may need to be increased.
    The run_job succeeds because it runs in the current session by default, if you use use_current_session=>false, does it still work ?
    Also auto_drop only drops the job when it has completed e.g. past its end_date or exceeded its max_runs.
    Finally note that there is a dedicated forum for dbms_scheduler located here
    Scheduler
    Hope this helps,
    Ravi.

  • DPM 2010 Scheduled Jobs Disappear rather than Run

    I have a situation where I have a DPM server that appears to be functioning fine, but none of the scheduled jobs run.  No errors are given, there are no Alerts, and there is nothing in the Event log (Application and System) which indicates a failure. 
    All my Protection Groups show a green tick to indicate that they are fine, but the last successful backup for all of them is Friday the 8th of February.
    If I go to Monitoring and Jobs I see the jobs scheduled, but when the time comes for the job to run, it does not go into the "All jobs in progress", it just merely disappears, like thus:
    And a few minutes later,
    As you can see, the jobs disappear from the queue, and the total number of jobs decreases accordingly.  These jobs do not go into any of the other 3 Statusses (Completed, Failed or In Progress), they just disappear without a trace.
    There is some unallocated space, albeit not much (Used space: 21 155,05 GB Unallocated space: 469,16 GB). If space was an issue I would expect to see errors to indicate this.
    DPM 2010 running version 3.0.8193.0 (hotfix rollup package 6) using remote instance of SQL 2008 which is functioning fine.  I have tried stopping/starting the services, and even rebooted the server twice.  The remote instance of SQL server is using
    a domain account as its service account.  There are no pending Windows updates, i.e. it is fully up-to-date.
    The System Center Data Protection Manager 2010 Troubleshooting Guide (July 2010) does not show how to troubleshoot this particular probelm.
    Does anybody know how to resolve this issue or which logs might help me troubleshoot it?

    OK,
    Did you change the SQL Agent user account ?
    If so, DPM enters the SQL Agent account name into the registry and later we check that account each time the DPM engine launches.  The internal interfaces to DPM are secured using this account so the account name needs to match the account the SQL Agent
    is using. 
    Step 1
    In the registry HKLM\Software\Microsoft\Microsoft Data Protection Manager\Setup alter  both
    SqlAgentAccountName and SchedulerJobOwnerName keys to reflect the SQL Agent user account being used.
    Step 2
    Update DCOM launch and access permissions to match what was granted to the Microsoft$DPM$Acct account.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
    This posting is provided "AS IS" with no warranties, and confers no rights.

  • BO XI 3.1 Re-schedule failed scheduling job

    Hi...
    I am not sure if I am just unable to find matching resources, but maybe someone can just point in the right direction.
    In a custom application, we have a scheduling overview, where we imitate some of the CMC behaviour.
    Now I need to add a feature to restart failed scheduling jobs.
    Some lines of pseudocode or a hint where I can find samples, documentation or anything will help.
    Any help is appreciated.
    Regards
    Jan

    Hi Ryan,
    Thanks for your reply. I have followed the same sequence but somehow the code is not functioning as expected.
    <%@ page import = "com.crystaldecisions.sdk.occa.infostore.*" %> 
    <%@ page import = "com.crystaldecisions.sdk.framework.CrystalEnterprise" %> 
    <%@ page import = "com.crystaldecisions.sdk.exception.SDKException" %> 
    <%@ page import = "com.crystaldecisions.sdk.framework.IEnterpriseSession" %> 
    <% 
        // logon information 
        String boCmsName  = "***" ; 
        String boUsername = "***" ; 
        String boPassword = "***" ; 
        String boAuthType = "secEnterprise" ; 
              // report 
        String reportName = "SDK_TEST" ; 
              // logon 
        IEnterpriseSession ceSession = CrystalEnterprise.getSessionMgr().logon( boUsername, boPassword, boCmsName, boAuthType ) ; 
        IInfoStore         oInfoStore = (IInfoStore)ceSession.getService( "", "InfoStore" ) ; 
        IInfoObjects oInfoObjects = oInfoStore.query("select top 1 * from ci_infoobjects where SI_NAME='" + reportName + "' " );
        IInfoObject oI = (IInfoObject) oInfoObjects.get(0);
              IInfoObject oSched = (IInfoObject) oInfoObjects.get(0);
               oSched.getSchedulingInfo().setRightNow(true);
               oSched.getSchedulingInfo().setType(CeScheduleType.ONCE);                    oInfoStore.schedule(oInfoObjects);
         %>
    What is happening here is, report is getting scheduled but it is not sending mail/attachment unlike the original schedule instance.
    Below are the details of the rescheduled instance
    Quote:
    Title: SDK_TEST
    Document Type: Web Intelligence Report
    Status Success
    Destination: Default
    Owner: ****
    Creation Time: 5/15/2014 1:53 AM
    Start Time: 5/15/2014 1:53 AM
    End Time: 5/15/2014 1:53 AM
    Duration: 3 sec
    Server Used: mdwnew.AdaptiveJobServer
    PID: 27131966
    Parent Object Path: **********
    Remote Instance in Federated Cluster: No
    Expiry: 5/15/2024 1:53 AM
    Formats: Web Intelligence
    Now my doubt is can we reschedule the report directly or we need to get all the scheduling info like from/to/events etc and then apply them for the new schedule? I think it will be a tedious job as it could be SMTP or FTP or inbox or anything.

  • 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

  • Dynamically Set date not changing in schedule Job

    Hi,
    I have created a report with "Order Date" as one of the parameters on the selection screen. I have created a variant, say 'X' , to set this date parameter dynamiccaly as "Current date - 31 days".
    I have scheduled this program to run in background with the 'X' variant daily at certain time.
    Now, for the day on which I created this job , the Order Date is set to correct date . For ex if I am scheduling the job tdy it will be set to 06/10/08. However, for next day , that is tom this date is not getting changed. i.e Tommorrow again Order date is 06/10/08 but it should have been 07/10/08.
    So basically this dynamically set date is not chaning in the scheduled job.
    Any idea why this is happening and what is the corrective measure for this.
    Thanks!

    There is an INITIALIZATION event in the program.......
    Do the processing your date in that event only....
    for ex....
    select-options: date for order-date.
    INITIALIZATION.
    date-low = sy-datum or wat ever.
    Thanks
    Saurabh

Maybe you are looking for