IBM Workload Automation Training & Education

Transcription

1 1 Automated Systems And Planning IBM Workload Automation Training & Education driving user innovation in workload automation since 1988

2 Mission: To provide a world class organization that promotes knowledge, idea sharing, and creates an atmosphere where our membership can leverage learned best-of-breed practices to better manage their enterprise automation systems.

3 Unsurpassed User Network & Programs ASAP Membership is comprised of Fortune 500 corporations, government agencies, universities and medium to large organizations. ASAP University: Annual Workload Scheduler training and educational symposium comprised of 60+ technical courses presented by subject matter experts including IBM L2 support team, IBM L3 development team, expert users; scheduling labs; Workload Scheduler certification testing; networking with IBM business partners. ASAP Executive Council: Executive meeting with Marco Morucci & the development and project management teams to discuss strategic workload automation priorities. ASAP User Network: ASAP maintains an active user community through its user and Linked-In. See the ASAP Calendar, ASAP University, Membership tabs and social media links at twsuser.org for additional information about ASAP s programs and services. 3

4 Parameters, Variables and Variable Tables How easy it is to use variables and variable tables? In this session, you learn how you can reuse your scheduling definitions by leveraging variables.

5 Override the variable value in the run cycle The same variable can be present in different variable tables. The variables are searched in the following order: 1. In the run cycle. 2. In the job stream. 3. In the workstation. 4. In the default variable table. Use variable tables for working hours Use variable tables for holidays

6 Override the variable value in the workstation The same variable can be present in different variable tables. The variables are searched in the following order: 1. In the run cycle. 2. In the job stream. 3. In the workstation. 4. In the default variable table. Use variable tables for Rome Use variable tables for New York City

7 Parameters, Variables and Variable Tables We have 4 different tables defined on our production system. I will show you one way we use them.

8 Parameters, Variables and Variable Tables When we get requests to run ad-hoc jobs with different files it is easier to plug in the variable. We receive a request to run the following: SSBN TASC_TO_RR with file filename This is asking us to pick a file from the vendor TASC and put the file on our secure terminal server. So we change the variable and then submit the job stream. This is the script we run in the job; /xfer/bin/sendfiles.pl tascget outbound/^filefromtasc^ ^FILEFROMT ASC^

9 Parameters, Variables and Variable Tables So suppose you want a job to run with the same value 95% of the time but a different value the other 5%? This is where Variable Tables are useful. On the next slide you will see how we have the same variable name in different tables but different values. Below is how we submit the different table.

10 Parameters, Variables and Variable Tables

11 Override the variable value in the workstation And what if I want to run the same job for two different customers on the same workstation? Define one pool for each of your customers referencing the same agent Pool for customer1 Pool for customer2

12 Variables resolved by the agent And what if a pool has several agents and I want to set a variable according to the agent that runs the job? Use variables resolved by the agent! Set the variable with the parm command Use the variable in Job B with the following syntax ${job.joba.variablename}

13 Variable resolution By default, variables are resolved when the job is added to the plan If a job is changing a value of a variable the other jobs of the same job stream cannot see this change. A new mechanism is added to change this behavior and resolve the variable when the job starts

14 Variable resolution at runtime Flag Job B to resolve the variables at runtime In Job A change the variable value with composer (or with the restul API) Use the variable in Job B with the following syntax ${variablename} Job A Job B

15 Reference job properties variables Job A exports a variable. Some job types automatically export some variables (i.e. File Transfer). Scripts can export a variable with the jobprop command. Automatic Resolution Use the variable in Job B with the following syntax ${job.joba.variablename} These variables are visible within the job stream. Job A Job Properties Job B

16 Reference job log in a variable Job A writes to stdout (this is always exported) Job B gets the stdout of Job A as a property in the job definition Automatic Resolution Use the variable in Job B with the following syntax ${job.joba.stdlist} Job A Job output Job B

17 Reference job log in standard in Job A writes to stdout (this is always exported) Job B gets the stdout of Job A as stdin Use the variable in Job B with the following syntax ${job.joba.stduri} Job A Job output Job Input Job B

18 Another place to use variables is Event Rules

19 How do you rate the value of this webinar? Let us know. Complete the evaluation. How was the webinar? How will you use what you learned? Share your insights with users between sessions on the ASAP User Forum at ASAPUniversity.org Facebook #ASAPWAIA ASAP University

20 Mark Your Calendar 2 nd Thursday d/committee Meeting 1 PM CT / 2 PM ET 2 nd Tuesday Planning Team Meeting 1 PM CT / 2 PM ET 3 rd Tuesday z/committee Meeting 8 AM CT / 9 AM ET 3 rd Wednesday ASAP University Webinar 10 AM CT / 11 AM ET See ASAP Calendar at for meeting agendas and webinar details ASAP University

21 May 7 May 11, 2017 Westchester Renaissance Hotel West Harrison, NY ASAP University