Search

Help

Page 7 of 33. Showing 324 results (0.084 seconds)

  1. Sos_product_life_cycle.png

  2. Release 1.11.7

    Announcement Release Type: Last Public Maintenance Release This release represents the end of public maintenance for branch 1.11 Release 1.11 is not a Long … see Product Life Cycle Management Date of shipment: 2018-03-28 Release No major features are introduced, this release includes exclusively bug-fixes
    Product Knowledge BaseMar 28, 2018
  3. JobScheduler - Tutorial 5 - The YADE JITL Job - Configuring and running file transfer jobs

    their own real-life transfer operations. List of Tutorials The other tutorials in this series are: JobScheduler - Tutorials - Introduction and Requirements … to the Job Chain along with two end nodes as shown: jobscheduler-tut05- joe-jobchain1-steps.png Create and configure an Order for the Job Chain
    Product Knowledge BaseMay 16, 2017
  4. inventory.sql

    MINVALUE 1 CYCLE; '; END IF; RETURN; END; $$ LANGUAGE plpgsql; SELECT tmp(); COMMIT; CREATE OR REPLACE FUNCTION tmp() RETURNS VOID AS $$ DECLARE c … ") ) '; END IF; RETURN; END; $$ LANGUAGE plpgsql; SELECT tmp(); COMMIT; /* INVENTORY_INSTANCES */ CREATE OR REPLACE FUNCTION tmp() RETURNS VOID AS $$ DECLARE c
  5. diamond test case.xls

    executed at 15:00; I executed after end of D 4 1 1 0 0 B executed at 18:00; D executed after end of B; I executed after end of D 5 0 0 1 0 E executed at 16:00; I executed after end of E 6 1 0 1 0 B executed at 18:00; E executed after end of B; I executed after end of E 7 0 1 1 0 D executed at 15:00; E executed at 16:00; I
  6. Which Java versions is JobScheduler available for?

    in time provide Java LTS releases and respective Java updates then SOS will check to integrate into the life cycle. Oracle® GraalVM releases can be used for JS7 … Oracle® changed the JVM life cycle: New Java feature releases ship every 6 months, Java LTS releases ship approx. every 2 years, see the Java SE Support Roadmap
    Product Knowledge BaseMar 29, 2024
  7. reporting.sql

    = current_schema; IF sequence_exist = 0 THEN EXECUTE 'CREATE SEQUENCE REPORTING_SEQ_RT;'; END IF; END; END IF; RETURN; END; $$ LANGUAGE plpgsql; SELECT tmp(); COMMIT; /* Table for REPORTING_EXECUTIONS */ CREATE OR REPLACE FUNCTION tmp() RETURNS VOID AS $$ DECLARE
  8. reporting_cleanup_procedure.sql

    REPORTING_SEQ_RED RESTART WITH 1; END IF; IF cleanupRange = 'all' OR cleanupRange = 'dailyplan' THEN TRUNCATE TABLE DAILY_PLAN; ALTER SEQUENCE DAILY_PLAN_ID_SEQ RESTART WITH 1; END IF; IF cleanupRange = 'all' OR cleanupRange = 'yade
  9. report_daily_plan_windows.job.xml

    $JOCCockpitUrl -Credential $JOCCockpitCredential | Out-Null; # start mode mapping $startModes = @{"0"="single start"; "1"="repeat start-start"; "2"="repeat end-start … }}, ` @{name="Expected End Time"; expression={ Get-Date $_.expectedEndTime }}, ` @{name="Expected Duration (sec
  10. report_daily_plan_linux.job.xml

    $JOCCockpitCredential | Out-Null; # start mode mapping $startModes = @{"0"="single start"; "1"="repeat start-start"; "2"="repeat end-start … }}, ` @{name="Expected End Time"; expression={ Get-Date $_.expectedEndTime }}, ` @{name="Expected Duration (sec