Creating your first TWS Daily Plan

Configuration steps for UNIX Tier 1 and 2 installations

For installations on Tier 1 and Tier 2 UNIX platforms, perform the following configuration tasks.

1. Create a .profile file for the TWSuser, if one does not already exist (TWShome/.profile). Edit the file and modify the PATH variable to include TWShome and TWShome/bin. For example, if Tivoli Workload Scheduler has been installed in the /opt/maestro directory, in a Bourne/Korn shell environment, the PATH variable should be defined as follows:

   PATH=/opt/maestro:/opt/maestro/bin:$PATH
         export PATH

   In addition to the PATH, you must also set the TWS_TISDIR variable to TWShome. The TWS_TISDIR variable enables Tivoli Workload Scheduler to display messages in the correct language and codeset. For example,

   TWS_TISDIR=/opt/maestro
        export TWS_TISDIR

   In this way, the necessary environment variables and search paths are set to allow you to run commands, such as conman or composer commands, even if you are not located in the TWShome path. Alternatively, you can use the tws_env shell script to set up both the PATH and TWS_TISDIR variables. These variables must be set before you can run commands. The tws_env script has been provided in two versions:
   • tws_env.sh for Bourne and Korn shell environments
   • tws_env.csh for C Shell environments
   See step 1 in Configuring a master domain manager for information about the tws_env script on Windows systems.
2. To start the Tivoli Workload Scheduler network management process, Netman, automatically as a daemon each time you boot your system, add one of the following to the /etc/rc file, or the proper file for your system: To start Netman only:

   if [-x twshome/StartUp]
   then
   echo "netman started..."
   /bin/su - twsuser -c " twshome/StartUp"
   fi

   Or, to start the entire Tivoli Workload Scheduler process tree:

   if [-x twshome/bin/conman]
   then
   echo "Workload Scheduler started..."
   /bin/su - twsuser -c " twshome/bin/conman start"
   fi

Configuring a master domain manager

After you have installed a master domain manager, if you did not select to automatically add the final job stream during installation and want to do so, follow the steps in this section to add the final job stream to the database and run JnextPlan. This job stream is placed in production every day and runs JnextPlan prior to the start of a new day. The installation creates the FINAL file in the /TWA/TWS directory on your workstation containing the final job stream definition. You can use FINAL or create and customize a new file. See Tivoli® Workload Scheduler: User's Guide and Reference for details about customizing the final job stream.

The following is an example of how to configure a master domain manager after installation:

1. Log in as <TWS_user>.
2. Set the environment variables. See Setting the environment variables.
3. We must now add Schedule Final to the Scheduling Database by using the provided template. Logged in as your TWS admin user, at the "bash" prompt, type the following command after running the tws_env.sh script. It is a good idea to run this script after sourcing your .profile or .bashrc so that you will have the paths to all of the TWS binaries and scripts

   cd ~/TWS

   composer "add Sfinal"

   We can now run JnextPlan to create a sample production plan for today.

   Note:

   In general you can add not only default (Sfinal) but any custom job stream definition by running the following command:

   add FINAL_JOB_STREAM

   where FINAL_JOB_STREAM is the name of the file containing the definition of the Final job stream. (Default Final job stream supplied with TWS is called Sfinal is just one possibility, see above). You can also customize Sfinal provided with TWS 8.5
   
4. Run the JnextPlan job:

   JnextPlan

   You can automate this step after installation. See Tivoli Workload Scheduler: User's Guide and Reference.
5. When JnextPlan completes, check the status of Tivoli Workload Scheduler:

   conman status

   If Tivoli Workload Scheduler started correctly the status returned by the command is Batchman=LIVES.
6. Raise the workstation CPU limit value to allow jobs to run. The default job limit after installation is 0, so no jobs are permitted to run at a time. Raise the job limit to allow jobs to run, for example to 10 jobs:

   conman "limit ;10"

   If no workstation name is specified for the limit command, the default value is the current login workstation.

   Note:

   If priority of jobs is equal to HI (100) or GO (101), they will disregard the limit and run despite a limit=0, unless fence>=priority.

Additionally, the following configuration procedures might be necessary. For information about these procedures, see Tivoli Workload Scheduler: Administration Guide.

• Customizing and configuring global, local, and user options
• Customizing and configuring user authentication to allow users authorization on actions and objects, and to configure LDAP
• Setting connection security to enable SSL for inter-component communications

NEWS CONTENTS

• 200102 : My Tech Notes and Stuff TWS 8.3 Install ( My Tech Notes and Stuff TWS 8.3 Install, )
• 200102 : Creating the production day ( )

Old News

My Tech Notes and Stuff TWS 8.3 Install

Cleanup Commands: do not do in production:

ResetPlan -scratch

StartUp

Get things started after reset (only on a new setup):

JnextPlan

Set limit:

conman

lc ;10

Do a test command job from conman:

sbd "ls";logon=batch

Do a test script job from conman:

sbf "/path/to/script.sh";logon=batch

Do this when resetting plan for the day and do not want to extend (if there is a problem)

JnextPlan -for 0000 # To not extend the plan (i.e. just reset for today)

Show schedule

ss

Show jobs

sj

SG247237

Creating the production day

After you select and configure the length of the production day (as described in 7.1.2, Identifying the length of the production day), you have to create the production day. This section describes the steps to create the production day, and the background details regarding the creation of a production day. The production day is created only on the master domain manager. It must be distributed to all other workstations in the scheduling network before it can be used.

Creating the production day at the concrete level means generating a file called Sinfonia on the master domain manager. It is then automatically copied by Tivoli Workload Scheduler to the Symphony file. After Tivoli Workload Scheduler is installed for the first time, these files do not exist.

If you are installing a new instance of Tivoli Workload Scheduler on the master domain manager server, be sure to first add the Sfinal job stream and set the central processing unit (CPU) limit as described in section "Configuring a master domain manager" of Chapter 6, "Configuring after installation" of IBM Tivoli Workload Scheduler Planning and Installation Guide v8.3, SC32-1273.

If the Symphony file does not already exist in the TWShome directory of the master domain manager server, you can run JnextPlan manually.

If you are installing a new instance of Tivoli Workload Scheduler on the master domain manager server, be sure to first add the Sfinal job stream and set the central processing unit (CPU) limit as described in section "Configuring a master domain manager" of Chapter 6, "Configuring after installation" of IBM Tivoli Workload Scheduler Planning and Installation Guide v8.3, SC32-1273.

If the Symphony file does not already exist in the TWShome directory of the master domain manager server, you can run JnextPlan manually.

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