Академический Документы
Профессиональный Документы
Культура Документы
3
October 13, 2006
IBM Software Services for Tivoli
Agenda:
Introduction Objectives Where to Find More Information Presentation
Q&A
Introduction:
This Tivoli Support Technical Exchange web seminar will cover basic navigation of the Tivoli Workload Schedulers (TWS) Job Scheduling Console (JSC) 8.3 with Fixpack 01. This will include basic functions like requirements for installation, defining objects, and understanding how the JSC communicates.
Objectives:
Upon completion of this Tivoli Support Technical Exchange web seminar, you will be able to: Understand what is required for installing and running the JSC Understand how the JSC communicates with the machine that it connects to. (i.e. Master Domain Manager (MDM)) How to define each object available Troubleshoot issues that may arise with the JSC
Terms
Tivoli Workload Scheduler (TWS) Job Scheduling Console (JSC) Master Domain Manager (MDM) Domain Manager (DM) Fault Tolerant Agent (FTA) Carry Forward (CF)
Requirements
System Requirements
AIX 100 MB (65 MB needed for temporary space) HP-UX 250 MB (210 MB) Linux on Intel 110 MB (75 MB) Linux on PPC 110 MB (75 MB) Linux on S390 110 MB (75 MB) Solaris 120 MB (90 MB) Windows 100 MB (60 MB) Language Packs (all languages) 60 MB RAM Minimum 256 MB Recommended 512 MB Please see the JSC Release Notes for z/OS connector information
CD 1 Linux, Linux PPC, Windows CD 2 AIX, HP-UX, Solaris CD 3 Contains the software package blocks for the Java Virtual Machine installation
CD 1 AIX, Solaris CD 2 Linux I386, Windows CD 3 Linux s390, Linux PPC, Windows CD 4 HP-UX
Whats New
10
11
Explorer View for job streams Engines can be created at any time from with the JSC Job streams can also be created as drafts and not added into the plan The ignore flag can be used when creating workstation classes, preventing them from being used by the plan Job definitions can be created directly from the job stream editor or by creating a copy of an existing job definition
12
13
Connection
Most often the JSC is connected to the Master, however, it can be connected to a domain manager or FTA The JSC connects to engines through the embedded version of WebSphere Application Server Express and corresponding connector. The connector then translates JSC instructions into scheduler commands.
14
Interoperability
JSC Version 8.3, 8.3.0.01 8.3, 8.3.0.01 JSC Version 8.3, 8.3.0.01 8.3, 8.3.0.01 8.3 8.3 8.3 8.3.0.01 Connector Connector 8.3 8.3.0.01 TWS for z/OS Engine 8.2 8.1 TWS Engine
15
Installation
16
17
Silent Install
By using the corresponding operating system response file located on the installation media - an unattended installation can be used in instances where a local install is not an option. The response file itself is well documented with its parameters and their options. This options is available for the base install as well as the Fixpack installation.
Windows Setup.exe silent options <filename> UNIX Setup.bin silent options <filename>
18
19
Enhancements in 8.3.0-TIV-TWSJSC-FP0001
Multiple jobs can be deleted concurrently from the Job Stream editor Cancel Pending command now available from the JSC previously only available from CLI (conman) Warning message issued when renaming jobs and job streams Inter-network dependencies can be specified on submit previous only available from CLI (conman)
20
Fixpack Requirements
The JSC must be installed prior to installing the Fixpack Create a backup copy of the Job Scheduling Console preferences file located in the users home directory inside the .twsconsole directory.
Windows: C:\Documents and Settings\<username>\.twsconsole\preferences.xml UNIX: /home/<username>/.twsconsole/preferences.xml
21
Installation of 8.3.0-TIV-TWSJSC-FP0001
22
Creating Objects
23
Actions List
The Actions list is an administrative panel. Objects can be created, and plans can be altered The Work with Engines list is where the database(s) and plan(s) can be viewed from your defined engines
24
New Engines
The core software for the scheduling environment. It can be either z/OS or distributed Specify hostname, port number, username, and password for the machine the JSC is connecting to Option: save password for faster startup
25
26
27
New Workstation
A definition of an individual computer or computer partition on which jobs and job streams are run Types of workstation vary depending on the type of engine
28
New Resource
Either a physical or logical system resources. Resources are used as dependencies for jobs and job streams.
29
A group of workstations with similar job-scheduling characteristics. Any number of workstations can be placed in a class. Job streams and jobs can be assigned to run on a workstation class. This makes replication of a job or job stream across many workstations easy
30
New Prompt
A dependency where an operator must respond affirmatively to a prompt so that the dependent job or job stream can run
31
New Parameter
An entity that enables job instance-specific values to be substituted in job and job stream scripts, either from values in the database or at run time. Parameters cannot be used when scripting extended agent jobs
32
The maximum length is 31 characters. Windows user names are case-sensitive. A Windows user needs access to the workstation where Tivoli Workload Scheduler launches jobs, and have the right to Log on as batch. When a name is not unique it is considered to be a local user, a domain user, or a trusted domain user, in that order.
33
New Domain
A named group of workstations in a distributed TWS network, consisting of one or more agents and a domain manager acting as the management hub. All domains have a parent domain except for the master domain.
34
New Calendar
A list of scheduling dates. Calendars are defined in the database and are mostly assigned to run cycles. Calendars can be used either to identify the dates when job streams or jobs can be run (when used with inclusive run cycles), or when they cannot be run (when used with exclusive run cycles). A calendar can also be designated for use as a freedays calendar in a job stream.
35
Change Password
36
A forecast plan is a projection over a selected timeframe based on the job streams and dependencies defined in the database. A trial plan is a projection of the current production plan for a different period, using the same start date. It is used to determine the effect of different plan decisions.
37
Once a trial plan has been thoroughly tested, or its time for a forecast plan to be put in place
38
Restore Plan
Restore the previous plan if the need arises If an alternate plan had not been chosen, selecting to restore would generate the above informative message.
39
Filters
40
Troubleshooting
41
Log Files
JSC Installation log file
Windows C:\Documents and Settings\<username>\Local Settings\Temp UNIX - <user_home_dir>/tmp Log file names are twsconsole_ismp.log (ISMP) and TWSJSC^8.3.log (Software Distribution)
Windows C:\Documents and Settings\<username>\Local Settings\Temp UNIX - <user_home_dir>/tmp File name is tws4zosconn.log
42
logging.properties
Key
com.tivoli.logging
Valid Values
True, False OFF, INFO, WARNING, ERROR, FATAL, ALL <user specified file name> <user specified directory> <user_home>/.twsconsole/userdata <user specified number> Default is 3 <user specified size> Default is 3072 True, False
Function
Enables or disables the tracing function
com.tivoli.level
handler.file.fileName
handler.file.fileDir
handler.file.maxFiles
Maximum number of log files that are created Maximum size of log file. Then creates new file, until maxFiles is reached. Is new info appended or new file create.
handler.file.maxFileSize
handler.file.appending
43
Q&A:
44