Search

Search

Help

Page 85 of 111. Showing 1,104 results (0.011 seconds)

  1. Jobs Reserving Resources

    All of these resources must be reserved by jobs processes by setting the "reservations" field at job submission. For example, setting the reservations field to global.shake=1 will have the job reserve 1 of the global.shake resources for each job process.…
    Qube 6.5Oct 18, 2012
  2. Global Resources

    Global resources are defined in the Supervisor using the qb.conf file. The configuration parameter is called supervisor_global_resources. The following specifies the configuration entry: supervisor_global_resources = resspec [, resspec,…] where resspec is…
    Qube 6.5Mar 26, 2013
  3. Generating agendas

    The qb::genframes() function returns a reference to a hash array, keyed to individual frames. This array is called an "agenda." Qb::genframes() contains a parser that can handle a number of ways of specifying lists of frames. Example Single frame 1 Frame…
    Qube 6.5Oct 12, 2012
  4. Job type configuration

    The purpose of the job.conf is to describe to Qube the vital statistics about the Job Type, and where to find the auxiliary files for both submission and execution. The format of the job.conf file is: [topic]key = value Example job.conf file.##[d…
    Qube 6.5Oct 19, 2012
  5. Submission front end

    For the submission front-end, see the SimpleSubmit framework documentation. It is almost identical to the SimpleCmd framework except it calls the jobtype backend rather than a commandline. See the QubeGUI's "Help->SimpleCmd Developer Guide" for the docume…
    Qube 6.5Oct 19, 2012
  6. Execution back end

    When designing the Job Type, the developer must decide on both the method to execute the job, and the name of the file to bind. Example Specifying a file binding is simple. You must include both the 'type' of binding, and the name of the file. execute_bin…
    Qube 6.5Oct 19, 2012
  7. Windows

    worker_template_path="C:/Program Files/qube/types;//server/share/site/qube\types"…
    Qube 6.5Oct 19, 2012
  8. Unix_Linux

    worker_template_path="/usr/local/pfx/qube/types:/site/qube/types" In the above example, the administrator properly specified Qube's default types as well as included a network-mounted directory, which contains the studio's custom job types. Once this is d…
    Qube 6.5Oct 19, 2012
  9. The Qube callback language code strings

    Code strings The following strings are can be used as callbacks code value when the callback's language is defined as "qube" Job-level code unblock-self block-self fail-self kill-self migrate-self preempt-self interrupt-self suspend-self resume-self Agend…
    Qube 6.5Jul 31, 2013
  10. Trigger Event Syntax

    Breaking down the trigger event name-type-context-extra specification syntax, it's composed of 4 parts: Event names Event types Event contexts Context-specific extra fields (only certain context need this) Referring to other jobs in a callback via job lab…
    Qube 6.5May 06, 2014