Tivoli Workload Scheduler for z/os Nested Dependent Variables

Transcription

1 Tivoli Workload Scheduler for z/os Nested Dependent Variables This document can be found on the web at Search for author s name under the category of White Papers. Version Date: September, 2012 IBM Advanced Technical Support Mike Sine I/T Specialist sine@us.ibm.com

2 Special Notices This flash reflects the IBM Advanced Technical Skills organizations understanding of IBM s Tivoli OMEGAMON XE on z/vm and Linux product. It was produced and reviewed by the members of the IBM Advanced Technical Skills organization. This document is presented As-Is and IBM does not assume responsibility for the statements expressed herein. It reflects the opinions of the IBM Advanced Technical Skills organization. These opinions are based on the author s experiences. If you have questions about the contents of this document, please contact the authors at sine@us.ibm.com. Trademarks The following are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. IBM, the IBM logo, Candle, DB2, developerworks, iseries, Passport Advantage, pseries, Redbooks, Tivoli Enterprise Console, WebSphere, z/os, xseries, zseries, System z, z/vm. A full list of U.S. trademarks owned by IBM may be found at NetView, Tivoli and TME are registered trademarks and TME Enterprise is a trademark of Tivoli Systems, Inc. in the United States and/or other countries. Microsoft, Windows, Windows NT, Internet Explorer, and the Windows logo are registered trademarks of Microsoft Corporation in the United States and/or other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. UNIX is a registered trademark in the United States and other countries licensed exclusively through The Open Group. Intel and Pentium are registered trademarks and MMX, Pentium II Xeon and Pentium III Xeon are trademarks of Intel Corporation in the United States and/or other countries. Other company, product and service names may be trademarks or service marks of others. Special thanks to the following people who contributed information to this effort: Art Eisenhour

3 Introduction Tivoli Workload Schedule for z/os (TWSz) provides variable support. This support allows TWSz predefined and user defined variables to be used in jobs scheduled by TWSz. TWSz will translate these variables prior to submitting the JCL to JES. This allows numerous possibilities to enhance the job scheduling environment and can be a powerful scheduling feature. One particular feature of the TWSz variable support is the dependent variable. Values for these variables are set based on the value of another variable, either pre-defined or user defined. This capability can be used as a scheduling technique to solve many scheduling needs. Many are unaware of dependent variables capabilities; this paper is designed to re-introduce TWSz schedulers to dependent variables and provide brief examples demonstrating their usefulness. Description of the dependent variable As the name implies, a dependent variable s value is set based on a dependency. The dependency is knows as an independent variable. A dependent variable s value is conditional to the value set for an independent variable. For example, if a comment line is needed in the JCL to indicate the day of the week when a job runs, TWS provides as a pre-defined variable CDAY. CDAY is the current day of the week with the values 1-7 representing the days of the week starting with 1 representing Monday and 7 representing Sunday and all others in between, respectively. If the format of the day has to be the full weekday name, a new dependent variable could be created to satisfy this requirement. To do this a dependent variable named DAYOFWK will be created and CDAY will be used as the independent variable. DAYOFWK will be set to the appropriate weekday name based on the numeric value set in CDAY. If CDAY = 1, then DAYOFWK = MONDAY. If CDAY = 2, then DAYOFWK = TUESDAY and so forth. Dependent variables are defined in TWSz variable tables. The following steps document the process of creating the dependent variable DAYOFWK. From the TWSz Main Menu selection option 1 DATABASE (figure 1):

4 Figure 1 From the Maintain Databases menu, select option 9, JCLVAR (Figure 2): Figure 2

5 On the Maintaining JCL variable tables menu, select 2 to Modify (Figure 3): Figure 3 The resulting panel is a filter panel allowing a specific variable table to be selected. By simply pressing enter, a list will be presented. In this example, the enter key will be pressed (Figure 4) causing a list of variable tables to be presented (Figure 5):

6 Figure 4 Select the variable table desired and modify it using the linecmd m (Figure 5) Figure 5

7 Create a new line to add new variable by entering i for insert, and type in the new variable name DAYOFWK. Set any other values as desired. Then select the DAYOFWK variable in the linecmd area to setup the dependencies (Figure 6). Figure 6 On the Modifying a JCL Variable panel issue the DEP command to enter the panel dialog that enables the definitions of dependency (Figure 7).

8 Figure 7 Enter the value CDAY (the predefined variable representing weekdays with integers 1-7) as the Independent Variable in the middle of the panel. At the bottom of the panel, there are up to two row command areas displayed at a time. Each row command area contains two value fields. One represents a value of the Independent Variable and the other represents the associated value for the new Dependent Variable DAYOFWK (Figure 8).

9 Figure 8 As Figure 8 shows, if CDAY = 1, then DAYOFWK will be set to MONDAY. If CDAY = 2, then DAYOFWK will be set to TUESDAY. Using PF7 and PF8 to scroll up and down, respectively, it is possible to add enough rows to include all 7 days of the week. Figure 9 shows the last two rows for Saturday and Sunday.

10 Figure 9 Once this process is completed, using the DAYOFWK variable in the JCL will cause the variable to be substituted with the correct full name of the day of the week. Here is a simple IEFBR14 job that has the &DAYOFWK variable in a comment line. Figure 10 shows the JCL prior to submission. //*%OPC SCAN //* THIS JOB RAN ON &DAYOFWK //VARIABLE JOB (0),'MYTEST',CLASS=A, NOTIFY=????????,REGION=64M,TIME=1440 /*JOBPARM LINES=9999 //STEP1 EXEC PGM=IEFBR14 //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY Figure 10 Figure 11 shows the output of the JCL after TWS translated the variable and it was submitted to JES.

11 //*>OPC SCAN //* THIS JOB RAN ON FRIDAY //VARIABLE JOB (0),'MYTEST',CLASS=A, NOTIFY=????????,REGION=64M,TIME=1440 /*JOBPARM LINES=9999 //STEP1 EXEC PGM=IEFBR14 //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY Figure 11 Summary Dependent variables can be used in numerous TWSz Applications to help handle conditional schedules. One installation had a single line of JCL that needed to change based on a calendar day. Using dependent variables, a default value was set for most days and a dependent value overlaid the default based on a specific calendar day. Making uses of these variables can further enhance your scheduling environment and take advantage of another powerful feature of the TWSz product.