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

1. IBM Tivoli Support Technical Exchange Web Seminar:Introduction to Job Scheduling Console 8.3October 13, 2006 Good Morning, My Name is Joe Lopez. Just a brief background on myself -- I have been with IBM for over 8 years, first as a Software Engineer for Lotus as a Certifed Lotus Professional, and the past 5 years as a Software Engineer in TWS Level 2 Support. Today’s presentation is “Introduction to Job Scheduling Console 8.3”. NEXT SLIDEGood Morning, My Name is Joe Lopez. Just a brief background on myself -- I have been with IBM for over 8 years, first as a Software Engineer for Lotus as a Certifed Lotus Professional, and the past 5 years as a Software Engineer in TWS Level 2 Support. Today’s presentation is “Introduction to Job Scheduling Console 8.3”. NEXT SLIDE

2. Agenda: Introduction Objectives Where to Find More Information Presentation Requirements What’s New Communication Installation Creating Objects Troubleshooting Q&A This is our agenda NEXT SLIDEThis is our agenda NEXT SLIDE

3. Introduction: This presentation will cover the basic install for the JSC – as well as – the changes in its communication with TWS and also how to define objects. NEXT SLIDEThis presentation will cover the basic install for the JSC – as well as – the changes in its communication with TWS and also how to define objects. NEXT SLIDE

4. 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 After all is said and done, you should understand the installation of the JSC and the fixpack. How it communicates with the machine it is connecting to, how to define most of the objects. And then have a few tips on how to troubleshoot the JSC. NEXT SLIDEAfter all is said and done, you should understand the installation of the JSC and the fixpack. How it communicates with the machine it is connecting to, how to define most of the objects. And then have a few tips on how to troubleshoot the JSC. NEXT SLIDE

5. Where to Find More Information: TWS 8.3 Manuals http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.tivoli.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 Here are a couple key spots for further information regarding TWS 8.3 and JSC 8.3 NEXT SLIDEHere are a couple key spots for further information regarding TWS 8.3 and JSC 8.3 NEXT SLIDE

6. Terms Tivoli Workload Scheduler (TWS) Job Scheduling Console (JSC) Master Domain Manager (MDM) Domain Manager (DM) Fault Tolerant Agent (FTA) Carry Forward (CF) This is a quick reference of some of the Acronyms that might be used in this presentation. NEXT SLIDEThis is a quick reference of some of the Acronyms that might be used in this presentation. NEXT SLIDE

7. Requirements Our first area is the Requirements NEXT SLIDEOur first area is the Requirements NEXT SLIDE

8. 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 Most operating systems require 100-120 MB of space, with the exception of HP-UX. It takes a bit more at 250 mb. The minimum RAM requirement is 256 megs, but we recommended 512 mb or higher. This presentation will not go into specifics for z/OS. But there is a great presentation that was previously given and available for replay on the 8.3 z/OS connector that addresses those environments. NEXT SLIDEMost operating systems require 100-120 MB of space, with the exception of HP-UX. It takes a bit more at 250 mb. The minimum RAM requirement is 256 megs, but we recommended 512 mb or higher. This presentation will not go into specifics for z/OS. But there is a great presentation that was previously given and available for replay on the 8.3 z/OS connector that addresses those environments. NEXT SLIDE

9. 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 This is the contents of the available JSC related CDs. You only need the one for the particular operating system you are installing on. NEXT SLIDEThis is the contents of the available JSC related CDs. You only need the one for the particular operating system you are installing on. NEXT SLIDE

10. What’s New What’s New in this version of the JSC? NEXT SLIDEWhat’s New in this version of the JSC? NEXT SLIDE

11. 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 The first enhancement for the 8.3 JSC is the engines.xml file. Admins can create one and send it out to any employees that will need to use the JSC. Or, if you are reinstalling the JSC for any reason, you can save this file off, and not have to set them all back up again. <ARROW or PAGE DOWN> The JSC infrastructure is now J2EE based instead of Tivoli Management Framework. Framework is not required at all for the JSC/TWS relationship. <ARROW or PAGE DOWN> The move from JnextDay to JnextPlan, opens up new plan capabilities. Trial Plans can be used for potential “what-if” scenarios, while Forecast plans can be used for different sets of jobs/criteria that need to be run in the future. NEXT SLIDEThe first enhancement for the 8.3 JSC is the engines.xml file. Admins can create one and send it out to any employees that will need to use the JSC. Or, if you are reinstalling the JSC for any reason, you can save this file off, and not have to set them all back up again. <ARROW or PAGE DOWN> The JSC infrastructure is now J2EE based instead of Tivoli Management Framework. Framework is not required at all for the JSC/TWS relationship. <ARROW or PAGE DOWN> The move from JnextDay to JnextPlan, opens up new plan capabilities. Trial Plans can be used for potential “what-if” scenarios, while Forecast plans can be used for different sets of jobs/criteria that need to be run in the future. NEXT SLIDE

12. 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 Job Streams now have an easy to use Explorer View. This allows seeing what jobs are in Streams and the dependencies related within a simple tree’d view. <ARROW or PAGE DOWN> When logging into previous versions of the JSC, you had to specify the login credentials to the TWS engine you wanted to connect to every time. The JSC 8.3 does not ask for that login up front. Once you are in the JSC, you can create multiple engines to be viewed in one screen. <ARROW or PAGE DOWN> Job streams can now be created as drafts, and will not be added into the plan, until they are taken out of the draft state. <ARROW or PAGE DOWN> There is an ignore flag available when creating workstations or workstation classes, which also prevents them from being used in the plan. This is very convenient in the instances where you are creating multiple instances, and do not want them in the plan until you are done creating them all. <ARROW or PAGE DOWN> Job definitions can be created directly from the job stream editor or by creating a copy of another existing job. NEXT SLIDE Job Streams now have an easy to use Explorer View. This allows seeing what jobs are in Streams and the dependencies related within a simple tree’d view. <ARROW or PAGE DOWN> When logging into previous versions of the JSC, you had to specify the login credentials to the TWS engine you wanted to connect to every time. The JSC 8.3 does not ask for that login up front. Once you are in the JSC, you can create multiple engines to be viewed in one screen. <ARROW or PAGE DOWN> Job streams can now be created as drafts, and will not be added into the plan, until they are taken out of the draft state. <ARROW or PAGE DOWN> There is an ignore flag available when creating workstations or workstation classes, which also prevents them from being used in the plan. This is very convenient in the instances where you are creating multiple instances, and do not want them in the plan until you are done creating them all. <ARROW or PAGE DOWN> Job definitions can be created directly from the job stream editor or by creating a copy of another existing job. NEXT SLIDE

13. Communication &Interoperability Communication & Interoperability Communication & Interoperability

14. 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. In most cases, we see the JSC connected to the Master Domain Manager. It provides a larger scope of data than just connecting to one Domain Manager or FTA. However, it can be connected to any of those machines. With the new J2EE infrastructure, the JSC connects to the engine through the WebSphere Application Server Express and connector. The connector is then responsible for translating the JSC instructions into TWS commands. NEXT SLIDEIn most cases, we see the JSC connected to the Master Domain Manager. It provides a larger scope of data than just connecting to one Domain Manager or FTA. However, it can be connected to any of those machines. With the new J2EE infrastructure, the JSC connects to the engine through the WebSphere Application Server Express and connector. The connector is then responsible for translating the JSC instructions into TWS commands. NEXT SLIDE

15. Interoperability Here is a chart of what versions JSC 8.3 or JSC 8.3 with Fixpack 1 can communicate with. Because of the change in the underlying architecture, it is not compatible with previous versions of TWS or Connector. However, that is not the case in the z/OS arena as you see here. NEXT SLIDEHere is a chart of what versions JSC 8.3 or JSC 8.3 with Fixpack 1 can communicate with. Because of the change in the underlying architecture, it is not compatible with previous versions of TWS or Connector. However, that is not the case in the z/OS arena as you see here. NEXT SLIDE

16. Installation Installation I will go through this section quickly, as the install is very simple. NEXT SLIDEInstallation I will go through this section quickly, as the install is very simple. NEXT SLIDE

17. Installation of JSC 8.3 First you will see the JVM screen, followed by the language option. <ARROW or PAGE DOWN> The next screen informs you of the possible options the installer has – install or repair <ARROW or PAGE DOWN> The license agreement <ARROW or PAGE DOWN> This is where you can specify the target directory for the installation. The default for Windows is seen here <ARROW OR PAGE DOWN> Here you are given some options with regards to shortcuts & icons <ARROW OR PAGE DOWN> The summary screen of what you are about to do <ARROW OR PAGE DOWN> This is just a sample of what you will see while the install is occurring <ARROW OR PAGE DOWN> And your final installation completed summary NEXT SLIDEFirst you will see the JVM screen, followed by the language option. <ARROW or PAGE DOWN> The next screen informs you of the possible options the installer has – install or repair <ARROW or PAGE DOWN> The license agreement <ARROW or PAGE DOWN> This is where you can specify the target directory for the installation. The default for Windows is seen here <ARROW OR PAGE DOWN> Here you are given some options with regards to shortcuts & icons <ARROW OR PAGE DOWN> The summary screen of what you are about to do <ARROW OR PAGE DOWN> This is just a sample of what you will see while the install is occurring <ARROW OR PAGE DOWN> And your final installation completed summary NEXT SLIDE

18. 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. Windows Setup.exe –silent –options <filename> UNIX Setup.bin –silent –options <filename> A silent install is also an option for the JSC. A response file is included on the CDs for the JSC. You can copy the OS-specific response file to your system, fill out the options given, and then use one of the example commands here, to perform the silent install. This is a great option in instances where you do not have direct access to a machine’s Xwindows environment or just a great tool to have for installing numerous machines quickly. NEXT SLIDEA silent install is also an option for the JSC. A response file is included on the CDs for the JSC. You can copy the OS-specific response file to your system, fill out the options given, and then use one of the example commands here, to perform the silent install. This is a great option in instances where you do not have direct access to a machine’s Xwindows environment or just a great tool to have for installing numerous machines quickly. NEXT SLIDE

19. 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 Here are some issues that were addressed in FP01. The JSC can now accept lowercase characters in the workstation field of an SAP job definition. The JSC view for the plan’s job stream properties now indicates the correct production day. And after creating a calendar, going back into it to view, will not change the dates you just specified. NEXT SLIDEHere are some issues that were addressed in FP01. The JSC can now accept lowercase characters in the workstation field of an SAP job definition. The JSC view for the plan’s job stream properties now indicates the correct production day. And after creating a calendar, going back into it to view, will not change the dates you just specified. NEXT SLIDE

20. 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) Fixpack 1 also came with a few enhancements of it’s own. Multiple job deletion is now possible from the Job Stream editor. The previous CLI-only options of cancel pending and internetwork dependencies is now an available JSC option. A warning message is now displayed when renaming jobs or job streams. This is to inform users of the effects that the action can have on other versions of the same job or job stream. NEXT SLIDEFixpack 1 also came with a few enhancements of it’s own. Multiple job deletion is now possible from the Job Stream editor. The previous CLI-only options of cancel pending and internetwork dependencies is now an available JSC option. A warning message is now displayed when renaming jobs or job streams. This is to inform users of the effects that the action can have on other versions of the same job or job stream. NEXT SLIDE

21. 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 The fixpack is not an all inclusive package, the JSC 8.3 must be installed prior to installing the fixpack. The next thing is not necessarily a requirement, but a strongly recommended action is to back up the preferences.xml file for your specific settings and filters, as well as the engines.xml file mentioned earlier. NEXT SLIDEThe fixpack is not an all inclusive package, the JSC 8.3 must be installed prior to installing the fixpack. The next thing is not necessarily a requirement, but a strongly recommended action is to back up the preferences.xml file for your specific settings and filters, as well as the engines.xml file mentioned earlier. NEXT SLIDE

22. Installation of 8.3.0-TIV-TWSJSC-FP0001 The installation of the fixpack is very similar to the base install, and just as simple. First we have our options for installing listed – Apply, Rollback, Commit, & Repair <ARROW OR PAGE DOWN> License Agreement <ARROW OR PAGE DOWN> This screen lists where it has found your existing JSC 8.3 installation. Just verify it is correct and continue <ARROW OR PAGE DOWN> Since the fixpack has not been installed before, the only choice given is to apply the fixpack <ARROW OR PAGE DOWN> This is the summary screen for what will be done and where <ARROW OR PAGE DOWN> Progression screen <ARROW OR PAGE DOWN> And ending in our summary of the completed installation NEXT SLIDEThe installation of the fixpack is very similar to the base install, and just as simple. First we have our options for installing listed – Apply, Rollback, Commit, & Repair <ARROW OR PAGE DOWN> License Agreement <ARROW OR PAGE DOWN> This screen lists where it has found your existing JSC 8.3 installation. Just verify it is correct and continue <ARROW OR PAGE DOWN> Since the fixpack has not been installed before, the only choice given is to apply the fixpack <ARROW OR PAGE DOWN> This is the summary screen for what will be done and where <ARROW OR PAGE DOWN> Progression screen <ARROW OR PAGE DOWN> And ending in our summary of the completed installation NEXT SLIDE

23. Creating Objects Creating Objects from the JSC NEXT SLIDECreating Objects from the JSC NEXT SLIDE

24. 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 The Actions list appears on the far left side of the main window of the JSC. The arrows indicate where you can expand & collapse sections to navigate. The Work with Engines pane appears to the right of the Actions List. If you have multiple engines, you will entries here for each one you have defined. NEXT SLIDEThe Actions list appears on the far left side of the main window of the JSC. The arrows indicate where you can expand & collapse sections to navigate. The Work with Engines pane appears to the right of the Actions List. If you have multiple engines, you will entries here for each one you have defined. NEXT SLIDE

25. 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 The engine is the core piece of the TWS environment. You can define multiple engines here. You fill out the name you want to call the engine, what type – distributed or z/OS, the hostname, port number - the port you specified during the TWS install for bootstrap. The default is 31117, and login credentials. You then have the option to save the password to ease startup. Or you can opt not to, and you would have to bring up this properties screen everytime, fill out the login info, and submit. NEXT SLIDEThe engine is the core piece of the TWS environment. You can define multiple engines here. You fill out the name you want to call the engine, what type – distributed or z/OS, the hostname, port number - the port you specified during the TWS install for bootstrap. The default is 31117, and login credentials. You then have the option to save the password to ease startup. Or you can opt not to, and you would have to bring up this properties screen everytime, fill out the login info, and submit. NEXT SLIDE

26. 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 A job stream is a collection of jobs paired with run cycles, times, priorities, and other dependencies. <ARROW OR PAGE DOWN> I won’t go over every aspect of every screen here, but I will point out the new “Is Draft” option, here on the first screen. <ARROW OR PAGE DOWN> Here you can put any comments you want or need for the stream <ARROW OR PAGE DOWN> Dependencies criteria – what effect should the dependency have on the stream <ARROW OR PAGE DOWN> Here you can specify time restrictions – for example: run at a specific X time, but perhaps you don’t want it to run any later than Y time. <ARROW OR PAGE DOWN> You can add any resources the stream will need – printers, tape drives, etc <ARROW OR PAGE DOWN> Ad hoc or predefined prompt – an ad hoc prompt is defined within the properties of a job or job stream and is unique to that job or job stream, whereas a predefined prompt is defined in the database and can be used by any job or job stream<ARROW OR PAGE DOWN> Files are not objects, but rather dependencies whose existence a job or job stream must verify before being allowed to start<ARROW OR PAGE DOWN> NEXT SLIDEA job stream is a collection of jobs paired with run cycles, times, priorities, and other dependencies. <ARROW OR PAGE DOWN> I won’t go over every aspect of every screen here, but I will point out the new “Is Draft” option, here on the first screen. <ARROW OR PAGE DOWN> Here you can put any comments you want or need for the stream <ARROW OR PAGE DOWN> Dependencies criteria – what effect should the dependency have on the stream <ARROW OR PAGE DOWN> Here you can specify time restrictions – for example: run at a specific X time, but perhaps you don’t want it to run any later than Y time. <ARROW OR PAGE DOWN> You can add any resources the stream will need – printers, tape drives, etc <ARROW OR PAGE DOWN> Ad hoc or predefined prompt – an ad hoc prompt is defined within the properties of a job or job stream and is unique to that job or job stream, whereas a predefined prompt is defined in the database and can be used by any job or job stream<ARROW OR PAGE DOWN> Files are not objects, but rather dependencies whose existence a job or job stream must verify before being allowed to start<ARROW OR PAGE DOWN> NEXT SLIDE

27. 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. A job is a task that you want done – a script or command <ARROW OR PAGE DOWN> Here we see 4 task types – Windows, UNIX, Other, SAP – SAP will only be displayed if the Extended Agent for SAP has been installed <ARROW OR PAGE DOWN> Next, there are the Recovery options – there are different ways you can deal with recovery Stop – do not continue with the next job instance Continue – Continue with the next job instance Rerun the job instance The name of a recovery job to run. Recovery jobs are run only once for each instance of the parent job instance And of course, the workstation you want the recovery job to run on – this is entered automatically when the recovery job is selected <ARROW OR PAGE DOWN> Here is where you define what type of job it will be and what it will actually be doing NEXT SLIDEA job is a task that you want done – a script or command <ARROW OR PAGE DOWN> Here we see 4 task types – Windows, UNIX, Other, SAP – SAP will only be displayed if the Extended Agent for SAP has been installed <ARROW OR PAGE DOWN> Next, there are the Recovery options – there are different ways you can deal with recovery Stop – do not continue with the next job instance Continue – Continue with the next job instance Rerun the job instance The name of a recovery job to run. Recovery jobs are run only once for each instance of the parent job instance And of course, the workstation you want the recovery job to run on – this is entered automatically when the recovery job is selected <ARROW OR PAGE DOWN> Here is where you define what type of job it will be and what it will actually be doing NEXT SLIDE

28. 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 A workstation is a definition of an individual computer where jobs and job streams will run <ARROW OR PAGE DOWN> Your tasks will vary depending on the type of engine – here it shows Domain Manager, FTA, Extended Agent, and Standard Agent <ARROW OR PAGE DOWN> Security Options Disabled – the workstation does not use SSL Allow Incoming – The workstation uses SSL authentication to accept any incomining connection from its parent domain manager if it is not an SSL connection Upward Forced – The workstation uses SSL authentication when it connects with its domain manager. The domain manager uses SSL authentication when it connects to its parent domain manager, and the master domain manager has SSL authentication enabled. All Forced – The workstation uses SSL authentication for all of its connections. It will refuse any incoming connection if it is not an SSL connection. <ARROW OR PAGE DOWN> Mailman Server IDs are for FTAs and Standard Agents only. It is a mailman on the domain manager that handles communication with agents. Using servers reduces agent initialization time and improves message efficiency. The options are A-Z and 0-9 for a total of 36 and are unique to each domain manager, so the same IDs can be used in other domains without issue. If not specified, the communication with the agents is handled by the main mailman process on the domain manager.<ARROW OR PAGE DOWN> NEXT SLIDE A workstation is a definition of an individual computer where jobs and job streams will run <ARROW OR PAGE DOWN> Your tasks will vary depending on the type of engine – here it shows Domain Manager, FTA, Extended Agent, and Standard Agent <ARROW OR PAGE DOWN> Security Options Disabled – the workstation does not use SSL Allow Incoming – The workstation uses SSL authentication to accept any incomining connection from its parent domain manager if it is not an SSL connection Upward Forced – The workstation uses SSL authentication when it connects with its domain manager. The domain manager uses SSL authentication when it connects to its parent domain manager, and the master domain manager has SSL authentication enabled. All Forced – The workstation uses SSL authentication for all of its connections. It will refuse any incoming connection if it is not an SSL connection. <ARROW OR PAGE DOWN> Mailman Server IDs are for FTAs and Standard Agents only. It is a mailman on the domain manager that handles communication with agents. Using servers reduces agent initialization time and improves message efficiency. The options are A-Z and 0-9 for a total of 36 and are unique to each domain manager, so the same IDs can be used in other domains without issue. If not specified, the communication with the agents is handled by the main mailman process on the domain manager.<ARROW OR PAGE DOWN> NEXT SLIDE

29. New Resource Either a physical or logical system resources. Resources are used as dependencies for jobs and job streams. A resource can be either a physical or logical resource. They are used as dependencies for jobs and job streams. Here I used a Printer as a resource. NEXT SLIDEA resource can be either a physical or logical resource. They are used as dependencies for jobs and job streams. Here I used a Printer as a resource. NEXT SLIDE

30. 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 Workstation classes are groups of workstations. These can be any type of grouping. Some examples are – All Windows machines, or Unix machines. Another way of grouping workstations could be departmental – all the workstations for Accounting or Sales. Any sort of grouping that makes sense for the situation and types of jobs that may need to be run in your environment. NEXT SLIDEWorkstation classes are groups of workstations. These can be any type of grouping. Some examples are – All Windows machines, or Unix machines. Another way of grouping workstations could be departmental – all the workstations for Accounting or Sales. Any sort of grouping that makes sense for the situation and types of jobs that may need to be run in your environment. NEXT SLIDE

31. New Prompt A dependency where an operator must respond affirmatively to a prompt so that the dependent job or job stream can run This is what was referred to earlier as a Predefined Prompt. You may need to create a prompt if you have a job or job stream that requires a prompt to be answered before it can start. The maximum number of characters for the prompt name is 8 characters. The default behavior of a prompt is to display a message and wait for a reply. In the text field, start the string with a colon (:) to display the message with no reply necessary. Start it with an exclamation point (!) point to receive a reply when no message is logged. NEXT SLIDEThis is what was referred to earlier as a Predefined Prompt. You may need to create a prompt if you have a job or job stream that requires a prompt to be answered before it can start. The maximum number of characters for the prompt name is 8 characters. The default behavior of a prompt is to display a message and wait for a reply. In the text field, start the string with a colon (:) to display the message with no reply necessary. Start it with an exclamation point (!) point to receive a reply when no message is logged. NEXT SLIDE

32. 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 A parameter may be used when your job definitions have values that are relevant to several fields. You can create a parameter so that you do not need to enter the value each time you create a new job definition. The name of the parameter must start with a letter and can contain alphanumberic characters, dashes, and underscores. The maximum length is 8 characters. The value is assigned to the parameter. Do not include the names of other parameters. If you are creating a parameter that is to be used in job scripts or commands, youc annot use double-quotes (“) in the value. Be aware that if you rename a parameter, any action you perform that refers to the old name will return an error. NEXT SLIDE A parameter may be used when your job definitions have values that are relevant to several fields. You can create a parameter so that you do not need to enter the value each time you create a new job definition. The name of the parameter must start with a letter and can contain alphanumberic characters, dashes, and underscores. The maximum length is 8 characters. The value is assigned to the parameter. Do not include the names of other parameters. If you are creating a parameter that is to be used in job scripts or commands, youc annot use double-quotes (“) in the value. Be aware that if you rename a parameter, any action you perform that refers to the old name will return an error. NEXT SLIDE

33. 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. When you are running jobs in a Windows environment, you need to create the user details in the JSC database. Windows users must be defined on the workstation where they launch the job also, with the appropriate user rights. NEXT SLIDEWhen you are running jobs in a Windows environment, you need to create the user details in the JSC database. Windows users must be defined on the workstation where they launch the job also, with the appropriate user rights. NEXT SLIDE

34. 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. TWS Domains. The name can start with a letter or with a number and can contain alphanumberic characters, dashes, and underscores. The maximum length is 16 characters. Domain names must be unique and cannot be the same as workstation and workstation class names. NEXT SLIDE TWS Domains. The name can start with a letter or with a number and can contain alphanumberic characters, dashes, and underscores. The maximum length is 16 characters. Domain names must be unique and cannot be the same as workstation and workstation class names. NEXT SLIDE

35. 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. Calendars. The maximum size of the calendars you create and manage depends on the size of your system’s RAM. For example, the maximum calendar size for a computer with 256 MB RAM is 1000 consecutive days (3 years). If you select a calendar for a job that is large than what your RAM can manage, the job stream definition process hangs and must be stopped. The name of the calendar must start with a letter and contain alphanumeric characters, dashes, and underscores. The maximum length is 8 characters. The description has a maximum length of 120 characters Two default calendars are provided – HOLIDAYS and FREEDAYS – which can be edited to suit your needs. NEXT SLIDECalendars. The maximum size of the calendars you create and manage depends on the size of your system’s RAM. For example, the maximum calendar size for a computer with 256 MB RAM is 1000 consecutive days (3 years). If you select a calendar for a job that is large than what your RAM can manage, the job stream definition process hangs and must be stopped. The name of the calendar must start with a letter and contain alphanumeric characters, dashes, and underscores. The maximum length is 8 characters. The description has a maximum length of 120 characters Two default calendars are provided – HOLIDAYS and FREEDAYS – which can be edited to suit your needs. NEXT SLIDE

36. Change Password Changing a Windows User’s password. When you change a Windows user’s password, it will only be relevant to the current plan. Once Jnextplan is run, it will restore the previous Windows user password. In order to change it permanently, you would need to change it in the database directly. NEXT SLIDEChanging a Windows User’s password. When you change a Windows user’s password, it will only be relevant to the current plan. Once Jnextplan is run, it will restore the previous Windows user password. In order to change it permanently, you would need to change it in the database directly. NEXT SLIDE

37. 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. There are two types of plans you can create here. Trial & Forecast – trial is for testing, and forecast is a projection over a selected timeframe based on job streams and dependencies in the database. There is the option to immediately switch to the newly generated plan. NEXT SLIDEThere are two types of plans you can create here. Trial & Forecast – trial is for testing, and forecast is a projection over a selected timeframe based on job streams and dependencies in the database. There is the option to immediately switch to the newly generated plan. NEXT SLIDE

38. Set Alternate Plan Once a trial plan has been thoroughly tested, or it’s time for a forecast plan to be put in place Set an alternate plan when you are ready to put one of your plans into place. NEXT PLANSet an alternate plan when you are ready to put one of your plans into place. NEXT PLAN

39. 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. There is also the option to restore the previous plan. Here, I’ve listed a message you get when you try to restore a plan, when an alternate plan was not in place. NEXT SLIDEThere is also the option to restore the previous plan. Here, I’ve listed a message you get when you try to restore a plan, when an alternate plan was not in place. NEXT SLIDE

40. Filters Filters are useful if you have a large listing of data and you only want to see a specific subset. Here is a sample view of the jobs in the database <ARROW OR PAGE DOWN> I right click on the column I want to sort. Here you can see the option of showing the filter row. This will show which column is being sorted, and on what. By clicking on Edit Filter… <ARROW OR PAGE DOWN> You can specify what you are wanting to filter on. Here I select that I want to see only job names that contain the string SLOW <ARROW OR PAGE DOWN> The resulting view shows the 2 job that meet the criteria. Note the filter row being displayed here NEXT SLIDEFilters are useful if you have a large listing of data and you only want to see a specific subset. Here is a sample view of the jobs in the database <ARROW OR PAGE DOWN> I right click on the column I want to sort. Here you can see the option of showing the filter row. This will show which column is being sorted, and on what. By clicking on Edit Filter… <ARROW OR PAGE DOWN> You can specify what you are wanting to filter on. Here I select that I want to see only job names that contain the string SLOW <ARROW OR PAGE DOWN> The resulting view shows the 2 job that meet the criteria. Note the filter row being displayed here NEXT SLIDE

41. Troubleshooting Troubleshooting the JSC NEXT SLIDETroubleshooting the JSC NEXT SLIDE

42. 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 If there are any issues with the installation, the JSC installation log file can be found in these default locations depending on operating system. If there are connector installation issues, here are the locations NEXT SLIDEIf there are any issues with the installation, the JSC installation log file can be found in these default locations depending on operating system. If there are connector installation issues, here are the locations NEXT SLIDE

43. logging.properties The first time you log in to the Job Scheduling Console, the logging.properties configuration file is copied to the user home directory in the .twsconsole subdirectory. This prevents the information in the logging.properties file from being overwritten when another user logs in to the Job Scheduling Console. If you want to refresh the file contents, you can rename or move the existing logging.properties file so that the Job Scheduling Console creates a new one when you next log in. Here are the different options in the file, and valid values. Exit the JSC, edit the logging.properties file – a common setting would be to change the com.tivoli.logging to True and to increase the level of com.tivoli.level – Restart JSC, recreate the issue, then review the log file. NEXT SLIDE The first time you log in to the Job Scheduling Console, the logging.properties configuration file is copied to the user home directory in the .twsconsole subdirectory. This prevents the information in the logging.properties file from being overwritten when another user logs in to the Job Scheduling Console. If you want to refresh the file contents, you can rename or move the existing logging.properties file so that the Job Scheduling Console creates a new one when you next log in. Here are the different options in the file, and valid values. Exit the JSC, edit the logging.properties file – a common setting would be to change the com.tivoli.logging to True and to increase the level of com.tivoli.level – Restart JSC, recreate the issue, then review the log file. NEXT SLIDE

44. Q&A: Any Questions?Any Questions?