TWS Job Scheduling Console

Job Scheduling Console for the Tivoli Workload Automation portfolio is a  rather primitive Java application that tries (rather unsuccessfully) to provide interactive interface for creating, modifying, and deleting objects in the TWS  database. It also helps you monitor and control objects scheduled in the current plan. Generally command line tools are a better deal.

In recent version of  JSC architecture changed and insteas of the Tivoli Framework WebSphere Application Server is used.

To run the console, you only have to be able to log into a scheduling engine through a connector. This means that you can manage plan and database objects from any system, including a laptop, on which the Job Scheduling Console is installed and from which you can reach via TCP/IP a server running the connector for Tivoli Workload Scheduler or for Tivoli Workload Scheduler for z/OS. When a user logs on to the JSC, the logging process goes through the WebSphere Application Server on the master domain manager (or a relevant domain manager or a fault-tolerant agent (FTA)), and using the connector instance, information is retrieved from the Tivoli Workload Scheduler engine and displayed on the console.

Connectors manage the traffic between the Job Scheduling Console and the job schedulers. Connectors are installed separately on a Tivoli management server and on managed nodes that have access to the scheduler. Job Scheduling Console uses Hypertext Transfer Protocol (HTTP) to connect to Tivoli Workload Scheduler engine. This is achieved by using the following components of the WebSphere Application Server:

• Bootstrap/RMI. Remote Method Invocation (RMI) system, which provides remote communication between JSC and Tivoli Workload Scheduler engine; by default, it uses port 31117.
• SOAP connectors SOAP, which is used to manage the traffic between the JSC and the Job Schedulers; by default, it uses port 31118.
• HTTP Transport Standard WebSphere communication protocol; the default port is 31115.
• HTTPS Transport. This is used by the composer when Hypertext Transfer Protocol-Secure (HTTPS) is used. By default, the port value is 31116.

The Job Scheduling Console provides two main functions:

• Scheduling Allows you to define and list job streams, jobs, and resource availability in the scheduler database.
• Monitoring and control Allows you to monitor and control scheduled jobs and job streams in the scheduler plan. In the Job Scheduling Console, a scheduled job stream is called a job stream instance whereas a scheduled job is called a job instance.

For each of these functions, you can use a list creation mechanism to list database or plan objects that you select according to filtering criteria. Filtering criteria narrow a list down to selected objects that you want to work with. You can list objects without using filtering criteria. In this case, the list displays all the existing objects of a kind. You can use both pre-defined lists that are packaged with the Job Scheduling Console and lists that you create.

Job definition

The job is the basic unit of work in a TWS environment. It is essentially just a named pointer to an executable command, program, or script.

Job definition panel in Job Scheduling Console has two pains: General and Task. When windows opens, "General" pane is active and task pane is hidden.

When you define a job, you must specify at least six pieces of information:  four on General pane and two on Task pane:

• On the "General" pane you need to define at least  four values:
  • Task type. They are available from top-down menu on General pane. You can chose from four options: Windows, UNIX, Other, and SAP.
  • Name. You can chose any name you want and it can be different from the name of script or command that you want to run.
  • Workstation name (this is host name on the workstation on which you will be running the job). Workstation should correspond to the task type selected above (Unix/Windows).  You can either type in the name or find it by clicking the ellipses button at right.
  • Login -- the user under which the job will be run.
• On the task pane you need to specify two values:
  • Whether this job is execution of a command or a script
  • The actual command to be executed.

After that you can click OK and there is no errors job will be saved. There will be no confirmation screen and no ability to edit the job.

But such ability exists if go to "work with engine" tab highlight the job left click to get menu and click on properties.

You can also create a new job from the existing job.

Job streams definition

Defining job streams has been changed quite significantly. The "on request" option has been removed and the "valid from/to" date option has been added. It is also possible to define a job stream as a draft.

Another new feature of V8.3 is the validity interval of a job stream, which defines the time interval within which the job stream definition is used. Job streams are selected to be included in the production plan if they fall within their defined interval.

To create a new job stream, choose New Job Stream option from the Actions list of the JSC. In the General window, the following new options have been introduced:

This option is the date of the first day when the job stream must become valid (active).

This option is the date after which the job stream is no longer active. You can leave this field blank.

This option shows that the job stream is still in the draft stage and must not be in production.

Figure 6-6 Job stream definition: General properties

The summary of the available tabs include:

New features in V8.3: Job stream versions and dependency resolution

Multiple versions of the same job stream can now exist at the same time: Each one of them now has a user defined "valid from" and "valid to" date. Different versions share name, workstation, and lock status fields. Versions of referenced instances are resolved according to their scheduled time.

The selection of the referenced instances follows the dependency resolution rule:

The job or job stream instance to resolve dependency is the one which is the closest in time before the instance that includes the dependency.

The job or job stream instance to resolve the dependency is the closest one in the day within which the instance that includes the dependency is scheduled to run.

The job or job stream instance to resolve the dependency is the closest one in a time interval, which is defined relatively to the time that the instance which includes the dependency is scheduled to run.

The job or job stream instance to resolve the dependency is the closest one in a time interval, defining the time of the day on which the interval starts and the time of the day on which it ends, whether within the same day of the instance that includes the dependency, or within a day defined relatively to this one.

Time restriction, resource, prompt, and file dependency tabs have not changed from previous versions of JSC.

New features in V8.3: Run cycle definition changes

Run cycle panels have been modified and changed, and new cycles have been added. The list of cycles available in this version of JSC include:

Note: Depending on the cycle that you select, different views are available for different run cycles.

In JSC V8.3, a new view has been added in the Job Stream Editor: An Explorer view (see Figure 6-9). Explorer view allows selection of jobs from the list or from the tree on the left to work with job properties.

You can now add multiple jobs to the job stream. You can also add new job definitions on the fly with the Edit

The Actions menu of the job stream editor has the following options:

Recommended Links

SG247528

5.1.1Create a job

5.1.2Create a new job from an existing job

5.1.3Create a job stream containing multiple jobs

5.1.4Schedule a job stream for automatic submission

5.1.5Submit a job stream

5.1.6Submit an ad hoc job

5.1.7Browse a job log

Introduction to the Tivoli Dynamic Workload Console

Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotes :  Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce :  Bernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS :  Programming Languages History : PL/1 : Simula 67 : C : History of GCC development :  Scripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month :  How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019