Test 935: IBM Tivoli Workload Scheduler for z/OS V8.3 Administration

Planning (21%)

1. Given the naming standards, security policies, and product documentation identify the required TWSz components, so that a design document for TWSz implementation can be submitted for change control. With emphasis on the following steps:
1. Identify the controller, tracker, DataStore, and Server.
2. Verify security & DASD.
3. Determine which TWSz components will be installed on various systems.
4. Identify the dataset and TWSz tasks naming conventions.


2. Given sample exits, customer requirements (dataset triggering), the design document, and product documentation, implement JES and SMF exits, so that functional systems exits: (JES2 exit7 and exit51 or JES3 exit IATUX19, and IATUX29: and IEFUJI, IEFACTRT, IEFU83) can successfully track z/OS and job related tasks. With emphasis on the following steps:
1. Generate exit load modules by customizing and executing sample JCLs.
2. Implement SMF and JES load modules.
3. Update z/OS parmlib and JES.parm.
4. Verify exit install.


3. Given installation media, the design document, and product documentation, configure the TWSz/OS started tasks and verify their functions, so that a TWSz/OS environment is installed and configured. With emphasis on the following steps:
1. Define TWSz subsystems.
2. Setup security environment.
3. Execute the EQQJOBS installation CLIST.
4. Execute the JCL created by EQQJOBS to allocate the TWSz datasets.
5. Create the JCL procedures for TWSz started tasks.
6. Define the initialization statement for started tasks.
7. Setup ISPF environment.
8. Activate inter tasks and inter process communications.
9. Verify TWsz installation.


4. Given the design document and product document, configure the parms so that a working TWSz environment (controller and tracker(s)) is able to submit and track a job successfully on all systems. With emphasis on the following steps:
1. View the parms and design document.
2. Configure parms values to match up with the design document requirements.
3. Set up communication among the tasks.


5. Given the design document and product documentation, configure the parms, so that a working TWSz environment (Data Store, E2E server, JSC server, and PIF/Dialog server) is able to process joblogs for restart and recovery use or aid in the communication between users/jobs and the controller. With emphasis on the following steps:
1. View the parms and design document.
2. Configure parms values to match up with the design document requirements.
3. Set up communication among the tasks.
4. If E2E function is used, configure the EQQPCS05 job for E2E USS security definitions.


6. Given an installed and functional new environment, an existing TWS z/OS environment, the design document and product documentation, perform the required migration actions, so that a scheduling environment is fully functional at the new release level. With emphasis on the following steps:
1. Collect information from existing environment.
2. Verify that new and existing software prerequisites are met.
3. Identify and update local customizations to new release (panel modifications, user exits, PIF programs, parmlib members, and JCL).
4. Migrate the product databases.

Managing the Workload (55%)

1. Given a planning JCL job and a working TWSz environment and, run current plan (CP) and long term plans (LTP),so that a long term plan is created. With emphasis on the following steps:
1. Running the long term plan (LTP) job.
2. Running the current plan (CP) job.


2. Given functional input TWSz databases, JCL, and the existing long term plan, run the current plan (CP) job, so that a current plan is created. With emphasis on the following steps:
1. Run the current plan (CP) job.


3. Given a design document, product documentation, and a functional TWSz environment, define TWSz workstations, so that appropriate workstations are available for scheduling activities. With emphasis on the following steps:
1. Determine which type of workstation is appropriate for a given objective.
2. Create workstation in TWS database.
3. Specify appropriate workstation attributes.


4. Given a design document, product documentation, and a functional TWSz environment, create needed TWSz calendars, so that a functional calendar database is available for scheduling. With emphasis on the following steps:
1. Determine appropriate number of calendars and their attributes.
2. Define needed calendars.


5. Given a design document, product documentation, and a working TWSz environment, create needed TWSz periods, so that a period database is available for scheduling. With emphasis on the following steps:
1. Determine the number and types of user defined periods required.
2. Create user defined periods as needed.


6. Given an anticipated predictable workload, a design document, product documentation, and a working TWSz environment, define required applications, so that populated application description database is created. With emphasis on the following steps:
1. Schedule group jobs into applications.
2. Determine sequence in which jobs must execute.
3. Determine controlling requirements (dataset availability, time requirements, etc.).
4. Create applications.


7. Given the requirements for accurate capacity planning (Service Level Agreement, etc), the design document, product documentation, and a working TWSz environment, , set LIMIT FOR FEEDBACK and SMOOTHING options in the TWSz initialization parameters and in the APPLICATION DESCRIPTION DATABASE, so that the planned durations of scheduled work will be correctly adjusted to reflect actual experience. With emphasis on the following steps:
1. Determine required GLOBAL settings of related initialization parameters.
2. Determine which, if any jobs are to be exceptions to the global settings.
3. Set operation-level over-rides for exception jobs.


8. Given the requirements for scheduling on demand workload in response to data set creation, the design document, product documentation, and a working TWSz environment, configure TWSz environment so that the required dataset triggering is implemented. With emphasis on the following steps:
1. Identify triggering data sets, and their associated TWSz Applications.
2. Create needed definitions in ETT database.
3. Define all SPECIAL RESOURCES which are to be ETT TRIGGERS in SR database.
4. Code needed EQQLSENT macros and run sample job EQQLSJCL to create EQQDSLST member of the EQQJCLIB.
5. Issue needed TWSz modify commands to load EQQDSLST to TRACKER subsystem(s).


9. Given the requirements for scheduling on demand workload in response to a job or special resource trigger, the design document, product documentation, and a working TWSz environment, configure TWSz environment, so that the required event triggered tracking is implemented. With emphasis on the following steps:
1. Identify triggering events, and their associated TWSz Applications.
2. Create needed definitions in ETT database.
3. Define any SPECIAL RESOURCES which are to be ETT TRIGGERS in SR database.


10. Given JCL for scheduled jobs, user requirements for dynamic JCL customization, the design document, product documentation, and a working TWSz environment, implement TWSz JCL variables, so that a JCL Library is configured to minimize manual updates at run time. With emphasis on the following steps:
1. Determine whether TWS-supplied predefined JCL variables are adequate.
2. Create user-defined variable tables and populate them if predefined variables are not adequate.
3. nsert variables and JCL TAILORING DIRECTIVES in JCL.


11. Given the JCL Library, requirements for automatic recovery when scheduled jobs end unsuccessfully with predictable errors, the design document, product documentation, and a working TWSz environment, insert auto recovery directives into JCL as needed to meet requirements, so that the JCL LIBRARY configured to reduce manual intervention for predictable recovery actions. With emphasis on the following steps:
1. Insert auto recovery directives into JCL as needed to meet customer requirements.


12. Given the requirements for controlling the flow of scheduled work, the design document, product documentation, and a working TWSz environment, use special resources , so scheduled work flow proceeds as desired with minimal manual intervention. With emphasis on the following steps:
1. Define needed special resources.
2. Associate resources with operations in the AD database.
3. Add needed operations or job steps to control status of defined resources.
4. Monitor reported status of resources using the TWSz user interfaces.
5. Perform cleanup of special resources as needed.


13. Given user requirements for control of TWSz activity using z/OS batch jobs and/or TSO commands (outside the ISPF dialog and GUI interfaces), the design document, product documentation, and a working TWSz environment, implement TWSz utilities, so that the user requirements are met. With emphasis on the following steps:
1. Recognize the need for external dependencies based on user job flow requirements.
2. Determine between which operations the dependencies are to be defined.
3. Understand the differences between Application and Operation Input Arrival Times and their significance for External Dependency resolution.
4. Define needed external dependencies, taking into account relative INPUT ARRIVAL TIMES of predecessor and successor application and operation input arrival times.


14. Given an operational or environmental exception, the design document, product documentation, and a working TWSz environment, use appropriate service functions, so that the exception is effectively handled. With emphasis on the following steps:
1. Understand how to activate or deactivate job submission for the mainframe or E2E, or both.
2. Identify when it is appropriate to refresh the TWSz in-core security profiles, and the result of that action.
3. Understand how and when to activate or deactivate ETT processing.
4. Understand how and when to activate or deactivate AUTOMATIC JOB RECOVERY (AJR).
5. Understand the consequences of REFRESHING THE CURRENT PLAN, and when that action might be appropriate.
6. Know how to recover from an unintentional CP REFRESH.
7. Create a TWSz APAR TAPE. Know how to setup and run the EQQAPAR sample jobstream.

Optional Functions: Restart and Cleanup (8%)

1. Given a working TWSz Restart and Cleanup environment (RCL) including Data Store(s), standards for restartability of scheduled jobs, design and product documentation, implement RCL functionality, so that jobs can be restarted from the selected restart point. With emphasis on the following steps:
1. Explain the relationship among the Restart and Cleanup command, the JES joblog and the Data Store.
2. Code the RCL-related initialization parameters in the CONTROLLER and DATASTORE parmlib members.
3. Determine which customer datasets must be protected from accidental deletion.
4. Determine which jobs, jobsteps, and datasets are to be exempted from RCL processing and implement the exemptions.
5. Code the DSTUTIL init statement to effect the desired retention and cleanup of datastore contents.
6. Define specified desired cleanup options for each MVS job in the ADdatabase.


2. Given a working TWSz environment with installed End-to-End (E2E) code, installed Fault Tolerant Agents (FTAs), design document, and product documentation, configure and use End to End, so that jobs are successfully scheduled and tracked on distributed platforms using TWSz E2E. With emphasis on the following steps:
1. Identify distributed machines and design the topology for the distributed environment where work will be scheduled.
2. Code the needed Topology and code the associate DOMREC AND CPUREC init statements and create Fault Tolerant Agent (FTA) workstations.
3. Code the E2E-related initialization parameters in the CONTROLLER and E2E Server parmlib members.
4. Establish connectivity between the TWSz CONTROLLER LPAR and the distributed systems.
5. Make certain the eqqUID user, and all users in the eqqGID group all have valid OMVS segments and are not SuperUser (UIDO).
6. Determine the use of centralized or non centralized scripts.
7. Code the required parmlib and JCL changes to enable E2E scheduling.
8. Create applications scheduling work on FTA workstations.
9. Schedule and run E2E scripts on FTA workstations.

Problem Determination and Performance Tuning (16%)

1. Given installation backup software and procedures, the design document, product documentation, and a working TWSz environment, maintain TWSz data sets, so that recovery potential is optimized. With emphasis on the following steps:
1. Implement proper dataset backup strategy.
2. Implement proper placement of datasets.
3. Demonstrate knowledge of correct backup and recovery for each TWSz dataset.
4. Demonstrate disaster recovery of TWSz to a specific time frame.


2. Given perceived Job tracking problem, design and product documentation, and a working TWSz environment, diagnose and correct Job Tracking problem, so that jobs are tracked correctly.
1. Run the EQQAUDIT utility against problem jobs.
2. Review the EQQAUDIT report.
3. Verify the job tracking environment using the EQQAUDIT report and product documentation.
4. Implement appropriate action to correct condition which caused loss of job tracking events.


3. Given a reported loop in CURRENT PLAN Dependency Resolution, design and product documentation, and a working TWSz environment, correct the issues causing the loop, so that a current plan can be created. With emphasis on the following steps:
1. Review EQQMLOG for failing EQQDNTOP, EQQDRTOP, or EQQDTTOP job step.
2. Review the EQQLOOP dataset for the failing plan job.
3. Implement corrective action for reported problem as is documented in the product manuals.


4. Given a reported TWSz performance problem, design and product documentation, and a working TWSz environment, collect and analyze documentation and take corrective actions, so that performance problem is resolved. With emphasis on the following steps:
1. Capture a console dump of the affected address space while the process is occurring.
2. Review EQQMLOG of problem task(s).
3. Run and review EQQAUDIT.
4. Use the documented MVS MODIFY commands to activate STATMSG collection, JCLDGB trace or VSAM I/O TRACE as needed if the problem is in the TWSz Controller.
5. Review additional data written to EQQMLOG by diagnostic functions activated by the MODIFY command.
6. If source of problem is not obvious, use standard z/OS performance tools to isolate problem address space and TCB.