jsc

44
IBM Software Services for Tivoli IBM Tivoli Support Technical Exchange Web Seminar: Introduction to Job Scheduling Console 8.3 October 13, 2006

Upload: sakina-khambaty

Post on 28-Nov-2014

94 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: JSC

IBM Software Services for Tivoli

IBM Tivoli Support Technical Exchange Web Seminar:Introduction to Job Scheduling Console 8.3

October 13, 2006

Page 2: JSC

2IBM Software Services for Tivoli

Agenda:

• Introduction•Objectives•Where to Find More Information•Presentation

• Requirements• What’s New• Communication• Installation• Creating Objects• Troubleshooting

•Q&A

Page 3: JSC

3IBM Software Services for Tivoli

Introduction:

This Tivoli Support Technical Exchange web seminar will cover basic navigation of the Tivoli Workload Scheduler’s (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.

Page 4: JSC

4IBM Software Services for Tivoli

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

Page 5: JSC

5IBM Software Services for Tivoli

Where to Find More Information:

• TWS 8.3 Manuals–http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.tivol

i.itws.doc/toc.xml

• TWS 8.3 & JSC 8.3 Patches –ftp://ftp.software.ibm.com/software/tivoli_support/patches/patches_8.3.0

• Redbook - Getting Started with IBM Tivoli Workload Scheduler V8.3–http://www.redbooks.ibm.com/redpieces/abstracts/sg247237.html?Open

Page 6: JSC

6IBM Software Services for Tivoli

Terms

•Tivoli Workload Scheduler (TWS)•Job Scheduling Console (JSC)•Master Domain Manager (MDM)•Domain Manager (DM)•Fault Tolerant Agent (FTA)•Carry Forward (CF)

Page 7: JSC

7IBM Software Services for Tivoli

Requirements

Page 8: JSC

8IBM Software Services for Tivoli

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

Page 9: JSC

9IBM Software Services for Tivoli

JSC & Connector CDs

•Job Scheduling Console installation CDs• 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

•z/OS connector installation CDs:• CD 1 – AIX, Solaris• CD 2 – Linux I386, Windows• CD 3 – Linux s390, Linux PPC, Windows• CD 4 – HP-UX

Page 10: JSC

10IBM Software Services for Tivoli

What’s New

Page 11: JSC

11IBM Software Services for Tivoli

Enhancements to JSC 8.3

• A common engine file (engines.xml) can be used in order to speed up the setup process

• The JSC is now based on a J2EE infrastructure, and no longer requires Tivoli Management Framework

• With the new JnextPlan capabilities, trial and forecast plans can now be created. Trial plans can be used for testing before being put into production, and forecast plans can be used at a future date

Page 12: JSC

12IBM Software Services for Tivoli

Enhancements to JSC 8.3 (cont.)

• 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

Page 13: JSC

13IBM Software Services for Tivoli

Communication &Interoperability

Page 14: JSC

14IBM Software Services for Tivoli

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.

Page 15: JSC

15IBM Software Services for Tivoli

Interoperability

JSC Version Connector TWS Engine

8.3, 8.3.0.01 8.3 8.3

8.3, 8.3.0.01 8.3.0.01 8.3.0.01

JSC Version Connector TWS for z/OS Engine

8.3, 8.3.0.01 8.3 8.2

8.3, 8.3.0.01 8.3 8.1

Page 16: JSC

16IBM Software Services for Tivoli

Installation

Page 17: JSC

17IBM Software Services for Tivoli

Installation of JSC 8.3

Page 18: JSC

18IBM Software Services for Tivoli

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 it’s parameters and their options. This options is available for the base install as well as the Fixpack installation.

• WindowsSetup.exe –silent –options <filename>

• UNIXSetup.bin –silent –options <filename>

Page 19: JSC

19IBM Software Services for Tivoli

Issues fixed in 8.3.0-TIV-TWSJSC-FP0001

•APAR IY75466 – JSC will not accept lowercase in workstation field of SAP job definition

•APAR IY79062 – JSC view of plan job stream properties show wrong production day, it shows the previous day

•APAR IY84552 – After calendar creation, going back into view dates shift back

Page 20: JSC

20IBM Software Services for Tivoli

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)

Page 21: JSC

21IBM Software Services for Tivoli

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 user’s home directory inside the .twsconsole directory.

Windows:

C:\Documents and Settings\<username>\.twsconsole\preferences.xml

UNIX:

/home/<username>/.twsconsole/preferences.xml

Page 22: JSC

22IBM Software Services for Tivoli

Installation of 8.3.0-TIV-TWSJSC-FP0001

Page 23: JSC

23IBM Software Services for Tivoli

Creating Objects

Page 24: JSC

24IBM Software Services for Tivoli

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

Page 25: JSC

25IBM Software Services for Tivoli

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

Page 26: JSC

26IBM Software Services for Tivoli

New Job Stream

• A list of jobs that run as a unit, along with run cycles, times, priorities, and other dependencies that determine the exact order in which the jobs run.

• Jobs can be added into a Job Stream from the Explorer View, Graph View, or by copying an existing job

Page 27: JSC

27IBM Software Services for Tivoli

New Job Definition

•A unit of work that resides in the database of the distributed TWS engine and can be added to a job stream. Job definitions can be created before creating a job stream, or can be created as part of the creation or modification of a job stream.

Page 28: JSC

28IBM Software Services for Tivoli

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

Page 29: JSC

29IBM Software Services for Tivoli

New Resource

•Either a physical or logical system resources. Resources are used as dependencies for jobs and job streams.

Page 30: JSC

30IBM Software Services for Tivoli

New Workstation Class

•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

Page 31: JSC

31IBM Software Services for Tivoli

New Prompt

•A dependency where an operator must respond affirmatively to a prompt so that the dependent job or job stream can run

Page 32: JSC

32IBM Software Services for Tivoli

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

Page 33: JSC

33IBM Software Services for Tivoli

New Windows User

• 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.

Page 34: JSC

34IBM Software Services for Tivoli

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.

Page 35: JSC

35IBM Software Services for Tivoli

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.

Page 36: JSC

36IBM Software Services for Tivoli

Change Password

Page 37: JSC

37IBM Software Services for Tivoli

Generate New Plan

• 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.

Page 38: JSC

38IBM Software Services for Tivoli

Set Alternate Plan

•Once a trial plan has been thoroughly tested, or it’s time for a forecast plan to be put in place

Page 39: JSC

39IBM Software Services for Tivoli

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.

Page 40: JSC

40IBM Software Services for Tivoli

Filters

Page 41: JSC

41IBM Software Services for Tivoli

Troubleshooting

Page 42: JSC

42IBM Software Services for Tivoli

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)

•Connector installation log• Windows – C:\Documents and Settings\<username>\Local Settings\Temp• UNIX - <user_home_dir>/tmp• File name is tws4zosconn.log

Page 43: JSC

43IBM Software Services for Tivoli

logging.properties

Key Valid Values Function

com.tivoli.logging True, False Enables or disables the tracing function

com.tivoli.levelOFF, INFO, WARNING, ERROR, FATAL, ALL

Sets error level logged in log file

handler.file.fileName <user specified file name> Name of the XML format log file

handler.file.fileDir<user specified directory>

<user_home>/.twsconsole/userdataSets path where log file is created.

handler.file.maxFiles<user specified number>

Default is 3Maximum number of log files that are created

handler.file.maxFileSize

<user specified size>

Default is 3072Maximum size of log file. Then creates new file, until maxFiles is reached.

handler.file.appending True, False Is new info appended or new file create.

Page 44: JSC

44IBM Software Services for Tivoli

Q&A: