Please enable JavaScript to view this site.

Estate Forums

Invantive Estate

It´s possible to request the running of a background process to Invantive Vision from your own program. Use a PL/SQL code like:

begin

 --

 -- Start a job with parameters.

 --

 -- Log on to Invantive.

 --

 bubs_session.set_session_info

 ( 'my_program_name'

 , 'start etl process'

 , 'system'

 , 'no query'

 , coalesce(sys_context('userenv', 'ip_address'), '?')

 , sys_context('userenv', 'host')

 , 'my_url'

 , '$Header: http://svn.invantive.com/repos/p104/trunk/help/nl/manual/Topics/voorbeeld-eigen-achtergrondproces.xml 19891 2012-10-09 13:23:03Z gle3 $' || to_char(sysdate, 'YYYYMMDDHH24MISS')

 );

 --

 -- Submit background job.

 --

 bubs#background_jobs.submit('BUBS_RUN_ETL', sysdate);

 --

 -- Fill parameters (optional).

 --

 bubs#background_jobs.set_parameter('p_etl_file', '../etl/example.kjb');

 bubs#background_jobs.set_parameter('p_log_level', 'BASIC');

 bubs#background_jobs.finish_parameter_entry;

 --

 -- Save to allow job to be picked up by schedulers.

 --

 commit;

 --

 -- Wait till job ends (optional).

 --

 -- Starting release b41, you can substitute this code by:

 --

 -- bubs#background_jobs.wait_for_finish_job

 --

 declare

   l_dummy pls_integer;

 begin

   while true

   loop

     select 1

     into   l_dummy

     from   bubs_background_jobs_v bjb

     where  1=1

     and    bjb.bjb_seq         = bubs#background_jobs.get_bjb_seq_last_submitted

     and    bjb.bjb_datum_einde is null

     ;

   end loop;

 exception

   when no_data_found

   then

     null; -- Job ended.

 end;

end;

You can also use one job to start other jobs. In that case you only need to use the code from ‘Submit background job’. Waiting for the completion of all initiated jobs can be done with:

bubs#background_jobs.wait_for_finish_all_child_jobs;

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.
  
Disclaimer