Skybot Software Announces the Acquisition of Open Systems Management      Learn more

Java based Graphical User Interface

(Click on images for higher definition view)

cosbatch 3.1 provides for a comprehensive Command Line Interface (CLI) for embedding into applications and a Java Swing based graphical user interface (GUI).  Using the GUI, IT operations staff can monitor and manage job requests remotely, so removing the need for constant, on-site supervision.

The use of the SOAP layer means that cosbatch 3.1 is designed to be extensible into a “cloud” based service.

This GUI provides all the functionality expected of a modern product, including:

UI architecture

  • multi-frame windows;
  • flexible (configurable) views;
  • drag and drop capabilities;
  • wizards for creating and updating cosbatch objects;
  • resizeable frames;
  • graphing for displaying the inter-relationships between objects;
  • graphing for creating and displaying the preconditions between suite jobs;
  • assumption of local personality (looks like MS Windows on Windows, X Windows on Linux etc.)
  • makes use of WebStart.  Java Web Start (also known as JavaWS or as javaws), allows users to start the application directly from the Internet using a web browser;
  • inline and online help.

Comprehensive and granular job control

One of the strongest features of cosbatch is the range of job control facilities available and the granularity with which jobs may be managed and monitored. Any job attributes which are not specified at submission time will be inherited, most probably from those attached to the queue.  cosbatch supports four levels of default attribute sets, each level overriding the other.  The GUI uses the defaults facility to pre-populate the prompt forms for job and suite addition/clone with the appropriate default values. The defaults system is underpinned by a table of default sets. A single default set (specified by its name) may optionally be associated with each of a host, role, queue or user.

gui screen

Once jobs have been submitted to the cosbatch queues they may be monitored by anybody with the appropriate access privileges.  They may request a summary of all jobs on all queues, or just of those within a particular queue.   

Each job in cosbatch passes through a succession of states. There are seventeen states in total. 

There are also six basic control commands:

  • Release allows a job which has been submitted with the attribute “hold before” to start its progress down the queue towards being executed. It also restarts a paused job.
  • Force sets a job off on its journey down the queue even if its schedule dictates another time.
  • Hold puts the job into “hold” status awaiting manual intervention.
  • Pause simply pauses the processing of a running job, but does not kill it. The release command is used to re-start it.
  • Jump relates to a job in a suite. It tells cosbatch to jump it in the control logic of the suite, but sets its exit status to successful completion.
  • Abort will kill an executing job.

Similar commands are also provided to control the operation of a suite.

In addition to these basic commands, operators may change the selected job’s attributes, including moving the job to another queue. There is also a function to view the entries of the job’s log files.

These control commands may also be available (depending on assigned access rights) to users in connection with their own batch jobs.