Workload Automation

Contents Workload Scheduler for z/OS after 9.3 (2016)

Workload Scheduler for z/OS after 9.3 - 2016

Intelligent Digital transformation requires modern automation Modern Agile Intelligent Hybrid

IBM Workload Scheduler for z/OS after v9.3 2Q 3Q 4Q 1Q 2Q 3Q 4Q 2015 2016 IWSz 9.3 SPEs SPEs SPEs SPEs SPEs SPEs Predict Connect Automate Zero downtime for z-Centric agents upgrade Easier management of operations time-zone New support for d-Driven agents NOP and MH in operations defs Modern New application dependencies Agile Insightful audit Insightful audit Insightful audit Enhanced security

Modern Workload Automation

The need for modern workload automation IT Leaders need to simplify operations and reduce total cost of ownership Everything is getting more complex and I’m alone here I need the product to more easily fit with complex scenarios

Timeline of features for modern automation Application dependencies (PI62520, PI62521) Timeline of features for modern automation NOP and MH in operation definition (PI57310) Easier management of operations time-zone (PI47506) New support for d-Driven agents (PI47613 ) End-to-end Zero downtime for z-Centric agent upgrade (IWSd v9.4) End-to-end 2Q 3Q 4Q 1Q 2Q 3Q 4Q 2015 2016

Features for modern automation - Details Easier timezone management for time-dependent operations New «/F subsys, RFRUX14T» modify command to reload exit 14 criteria table with no recycle New support for d-Driven agents D-Driven agents can now run in a JES3 environment The controller calls EQQUX014 when a time dependent operation becomes ready in a z/OS® environment. The exit returns an offset, expressed in minutes, to be added to the operation start time. The result is used by the Workstation Analyzer task, to decide whether the operation can be started.

Zero downtime for z-Centric agent upgrade - Details Value Solution Planning the maintenance of your agents no longer means negotiating rare idle time windows Perform the upgrade of the agents without need to stop the submission

NOP and MH options in operation definition - Details Value Solution Dynamic schedules, with variable applications, allow easier mapping of various scenarios Depending on when they run, applications can have different scheduling rules The following settings can be specified in the “Time Specification” section of operation definition: NOP Manual Hold Critical job indicator When a NOP operation is ready to be started, IBM Workload Scheduler for z/OS immediately sets it to C status. The operation is not submitted and successor operations are eligible to start. Manually Hold options at operation level in the Application Description (AD) data base. These settings, together with the Critical Job Indicator, can also be specified in the "Time Specifications" section of the operation definition in the Application Description (AD) data base. PI57310

NOP, MH and CRIT for a Time Dependent job Automatic Option Time & Run Cycle Options This will be the demo scenario. We have two RCG, the 1° one containing all Mondays, the 2° one containing all the other days. By default the job is not critical (see left screen). The right screen says that the job is added to CP already NOped only on Monday, while all the other days is added to CP already manually held and eligible for Critical Path. Except Monday: Initially NOped in CP Only Monday: Initially Manually Held and in Critical Path Default: No Critical Path

New application dependencies - Details Value Solution More flexible definition of workflows Eliminate possible dummy jobs, specifically created to link applications Now, you can specify operations/applications dependencies as follows: An operation depends on another operation An operation depends on an application An application depends on another application An application depends on an operation of another application

New application dependencies - Scenario After implementing application dependencies operations 1, 2 and 255 have been replaced by deps on other applications Operations 1, 2 and 255 are used as place holder for dependencies to other applications Appl XYZ Appl XYZ 1 NETZ 2 NETZ Dep on ABC Dep on DEF 10 NN91 10 NN91 20 NN91 20 NN91 21 NN91 22 NN91 21 NN91 22 NN91 255 NETZ Dep on GHI

Agile Workload Automation

The need for superior control and audit IT Leaders need to confidently extend the product access to Developers I need to give workload automation access to developers, for everyone’s benefit.. With Developers entering WA, I need to manage the Wild West!

Timeline of features for superior audit and control Enhanced security: Finer-grained security access level (PI57531) Insightful audit (PI48075): Insightful audit (PI48133): Insightful audit (PI54662): 2Q 3Q 4Q 1Q 2Q 3Q 4Q 2015 2016

Insightful Audit - Details Value Solution Being ready to track detailed auditing info for any changes to scheduling objects: When Who How What Additional CP-related auditing information (JT logs): Manually completed occurrences Automatic completion of internal completed predecessors Job name added Old status added to operation records Possibility to filter Auditing info New DB-related auditing information (new set of JT-like sequential datasets: EQQDB*)

Enhanced Security - Details Value Solution More granularity in security access help guarantee product stability Secure actions, in addition to data Security access can now be controlled at any level, from object level down to action level

Enhanced Security - Details Occurrence Commands RG Remove from group DG Delete group CG Complete group C Complete an occurrence W Set waiting R Rerun Define actions as sub-resources in AUTHDEF statement Use RACF commands to provide/deny access to users Fixed resource Subresource & RACF resource name Description CP CP.ADD Add workload (occurrences or operations)   CP.MODIFY Modify attributes CP.DELETE Delete workload (occurrences or operations) CP.COMMANDx Line commands CP.ADDOPER Add operations CP.DELOPER Delete operations CP.MODOPER Modify operations CP.ADDDEP Add dependencies CP.DELDEP Delete dependencies CP.MODDEP Modify dependencies CP.MODOPSTAT Modify operation status Operation Commands J Edit JCL (J command resource) MH, MR Manual Hold, Manual Release (MR, MH command resources) NP, UN NOP,UN NOP (NP, UN command resources) K Kill (K command resource) EX Execute (EX command resource) JR/FJR JT, Fast path JR (JR command resource) SR/FSR SR, Fast path SR (SR command resource) SC/FSC SC, Fast path SC (SC command resource) SJR Simple Job Restart Execute (SJR command resource) R Reset Status (MODOPSTAT resource) BIND Bind operation (BND command resources) N Set NEXT logical status (MODOPSTAT resource) N-x Set specific status (MODOPSTAT resource) AUTHDEF COMMAND1(J,ARC,…) SUBRESOURCES(CP.ADDOPER, CP.COMMAND1) RACF Commands RDEF IBMOPC CP.ADDOPER PERMIT CP.ADDOPER ID(JASON) ACCESS(UPDATE) CLASS(IBMOPC)

Enhanced Security - Scenarios Tim, the System Administrator 1 2 Tim can now authorize Jason, the Scheduler, to add operations to the Current Plan. In the same time, he can prevent him from adding new occurrences. Tim can secure a set of commands, creating new User Profiles. He can authorize Jane to perform a recovery action He can authorize Jason to Complete and Rerun an existing occurrence, but prevent him from adding new occurrences Jane, the Application Developer Jason, the scheduler

Enhanced Security - Scenarios 2 1 Define the CP.COMMANDx subresources in the AUTHDEF AUTHDEF CLASSNAME(IBMOPC) COMMAND1(ARC) COMMAND2(C,R) SUBRESOURCES(CP.COMMAND1,CP.COMMAND2) Define to RACF RDEF IBMOPC CP.COMMAND1 RDEF IBMOPC CP.COMMAND2 Give Jane update access to CP.COMMAND1 PERMIT CP.COMMAND1 ID(JANE) ACCESS(UPDATE) CLASS(IBMOPC) Give Jason update access to CP.COMMAND2 PERMIT CP.COMMAND2 ID(JASON) ACCESS(UPDATE) CLASS(IBMOPC) Define the CP.ADD and CP.ADDOPER subresources in the AUTHDEF SUBRESOURCES(CP.ADD,CPADDOPER) (AUTHDEF statement) Define them to RACF and give universal NONE access by default RDEF IBMOPC CP.ADD RDEF IBMOPC CP.ADDOPER Give user Jason update access to the CP.ADDOPER resource PERMIT CP.ADDOPER ID(JASON) ACCESS(UPDATE) CLASS(IBMOPC)

Thank you