1. Understanding System Monitoring Tasks and Roles
Monitoring the z/OS System
55 minutes
Using System Commands and Consoles
45 minutes
Displaying Active Jobs, Tasks and Users
45 minutes
Displaying Device Status
45 minutes
Using Advanced Monitoring Facilities
PowerPoint
System Monitoring Practices and Procedures
40 minutes
Working with SMF
70 minutes
MPF and Message Suppression
Understanding System Monitoring Tasks and Roles
Graphic: Insert your organization’s name in the slide above along with the date and time that the Webinar will begin.
Pre-session activity:
Prior to the session, obtain the demographics of the area that the attendees have come from (i.e. application programmer, operator). This provides you with data that you can present to everyone when you are ready to start. As well as giving you background information on your group it also allows you to tailor some of the presentation specifically to their needs. At the end of the previous PowerPoint presentation, attendees were asked to forward you any questions they may have relating to the content in this pathway. This should also be included in this session.
As attendees come online, make the time to briefly chat with them and ask questions such as: how they have found the Introductory training so far, what their involvement with the system currently is, and what it may entail in the future. This is information you will be able to share with the group when you are ready to start (see next slide).
Presenter/Producer:
Approximately 20 minutes before the Webinar, make sure the welcome slide above is displayed so that when participants log in they know immediately they are in the right place at the right time. You may also want to have rotating slides that display general information such as how they can ask questions throughout the session, what information will be available to them afterwards (e.g. handouts, recording of the session).
Allow a maximum of 3 minutes after the scheduled start time for any late attendees. This provides a general courtesy to those that may have been detained for genuine work related reasons, while not annoying those who have joined promptly and are waiting to begin.
Presenter/Moderator:
Welcomes those that have joined the Webinar and describes general information about the session such as using the webinar features as well as session specific details identifying how long the session will be (30-40 minutes, although you may have a more accurate idea once you have given the presentation a “dry run”), pre-requisites for the session (shown on the right of the welcome slide), interaction that will occur throughout the session (several exercises to keep participants busy) and that there is a 5-10 minute Q & A session at the end.
PowerPoint
Handling SMF and System Messages
z/OS System Operation
60 minutes
Company Name
Date - Time
Webinar
Understanding System Monitoring Tasks and Roles
Copyright © Interskill Learning Pty Ltd 2011 – Commercial in Confidence

2. About You Group Numbers Operators 2 System Analysts 1
Application Programmers 4
Graphics: The group and number details will need to be modified based on the people attending.
Presenter:
This session is all about you (attendees) and obtaining the knowledge you need to perform your workplace tasks. Just so everyone knows a little about each other I have created a breakdown of those attending, and the area they work in (this information can be obtained as mentioned in the pre-session notes from the previous page).
This is a good opportunity to expand on the private conversations you may have had when welcoming people to the session. For example, you may mention that before the session you had an opportunity to chat with a few of you about your induction training and the work you are currently performing. Also mention that this information is important because there are several topics covered where we discuss how it is relevant to you or the area you work in.
These are good icebreaker exercises and usually relaxes the attendees knowing a bit about the other participants.
Copyright © Interskill Learning Pty Ltd 2011 – Commercial in Confidence

3. Understand the consequences of system shutdown and IPL.
Objectives
Understand the consequences of system shutdown and IPL.
Identify system monitoring procedures and practices.
Presenter:
The Datatrain training modules and internal PowerPoint presentations you have undertaken so far have focused on providing you with information describing how important tasks such as system shutdown and startup should be performed and the type of information that is used to gauge the health of your system.
The aim of this session is to involve you in the summarizing of this material describing how it affects you and the organization.
Read and expand on the objectives above.
Copyright © Interskill Learning Pty Ltd 2011 – Commercial in Confidence

4. Clarification of Previous Material
General comments received.
Queries on system shutdown and IPL.
Queries on system monitoring practices.
Presenter:
This section looks at the information that you have forwarded to me during this pathway. The amount of time you spend on this will obviously depend on how much data has been sent to you. The bonus is that because you have received this data prior to the Webinar, you have time to prioritize it and identify approximately how long you need to spend covering it.
I have split this content in two so that we can discuss any concerns or general comments about the pathway learning and the way it is run (for example, learners may feel that only one PowerPoint presentation is required, not two, or that an additional Webinar should be added at the start of the training). The second part deals with information or queries you have sent me over the last ____ days with questions you have about our system shutdown and IPL, and system monitoring practices.
Expand on the items sent (you may also want to identify who sent it to you). Rather than resolving the question yourself you may ask whether any of the attendees can provide it (a good way to interact with them).
Copyright © Interskill Learning Pty Ltd 2011 – Commercial in Confidence

5. Consequences of a system shutdown
System shutdown scenarios
Scenario 1:
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Quisque accumsan pellentesque sollicitudin. Mauris vel leo elit, at viverra elit. Pellentesque blandit sagittis enim nec sollicitudin. Vestibulum mollis odio quis risus euismod vel cursus augue vestibulum. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus.
Graphic: You may want to include some screen shots here depending on the scenarios you have chosen.
Pre-Webinar requirement:
The screen here shows a single scenarios but the number you present depends on your requirements. Ideas for scenarios could include: - where the system seems to have stopped (but is actually just waiting for a WTO response) and ask them what action they would take first (this tests how they should not jump to any conclusions and to follow the correct procedures).
where the systems programmer has contacted you asking to perform a standard shutdown of system ____ (this tests that they know what to do under normal system shutdown situations).
where a system shutdown has started but ___ product is preventing the process from completing (this tests what action they would take when there are problems).
Before running this Webinar you should confirm with the relevant people that the correct actions are identified for the scenarios you will be presenting. This may include notification, escalation and problem logging procedures.
Presenter:
This is an opportunity for you to interact with me and describe the types of tasks that you, or the area you work in, would be involved in with the scenarios described here. I will allow you 5 minutes to forward me these details and we will then discuss as a group.
The start of this Webinar should have instructed the user on the method used to forward this information to you. The learner response time period (five minutes) is a guide only but is purposefully short to put them under the pressures that they might experience as part of these scenarios.
As learners forward responses, you may want to play out the scenario as it relates to those responses. For example, in the last scenario above, person 1 says that they would cancel the job causing problems…you could respond by saying that the job still won’t complete. Meanwhile person 2 has responded by saying they would contact the owner of the product for action to be taken…and you might say that they can not be contacted, or that they have indicated that the job needs to be forced….so there could be numerous outcomes depending on the action they take.
Copyright © Interskill Learning Pty Ltd 2011 – Commercial in Confidence

6. Consequences of a system shutdown – Your Response
Discuss responses from different people
Presenter:
You will need to cover as many people as possible with their responses and compare it to the information you gathered pre-Webinar. By working your way through all areas, all learners obtain an appreciation of what needs to be achieved in these circumstances.
You may also want to describe any recent system shutdown problems and the action that was taken.
Copyright © Interskill Learning Pty Ltd 2011 – Commercial in Confidence

7. Consequences of a system IPL
System start-up scenarios
Scenario 1:
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Quisque accumsan pellentesque sollicitudin. Mauris vel leo elit, at viverra elit. Pellentesque blandit sagittis enim nec sollicitudin. Vestibulum mollis odio quis risus euismod vel cursus augue vestibulum. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus.
Scenario 2:
Graphics: You may want to include some screen shots here depending on the scenarios you have chosen.
Pre-Webinar requirement :
The screen here shows two scenarios but the number you present depends on your requirements. Ideas for scenarios could include: - where a problem has occurred and a vital system has abended. Ask them what action they would take first (this tests whether they are aware of the processes…depending on the system they may try to bring it up immediately or may need to escalate the situation).
where the systems programmer has contacted you asking for specific IPL parameters to be used as part of the IPL (this tests that they know how to define default parameters).
where during an IPL, the system requires an operator response (this tests what action they would take when something out of the ordinary, but not necessarily a problem, occurs).
where during an IPL, the system freezes (this tests their response when there is a problem).
Before running this Webinar you should confirm with the relevant people that the correct actions are identified for the scenarios you will be presenting. This may include notification, escalation, problem logging procedures, commands used to obtain additional information, identifying who has the authority to request that an IPL be taken and who is allowed to perform an IPL, and how items are to be started normally if IPL automation fails.
Presenter:
This is an opportunity for you to interact with me and describe the types of tasks that you, or the area you work in, would be involved in with the scenarios described here. I will allow you 5 minutes to forward me these details and we will then discuss as a group.
The start of this Webinar should have instructed the user on the method used to forward this information to you. The learner response time period (five minutes) is a guide only but is purposefully short to put them under the pressures that they might experience as part of these scenarios.
As learners forward responses, you may want to play out the scenario as it relates to those responses. For example, in the last scenario above, person 1 says that they would just start the IPL process over again…you could respond by saying that the IPL freezes again. Meanwhile person 2 has responded by saying they would contact the system programmer for action to be taken…and you might say that they have informed you to use different load parameters. When they do this several warning messages are produced….so there could be numerous outcomes depending on the action they take.
Copyright © Interskill Learning Pty Ltd 2011 – Commercial in Confidence

8. Consequences of a system IPL – Your Response
Discuss responses from different people
Presenter:
You will need to cover as many people as possible with their responses and compare it to the information you gathered pre-Webinar. By working your way through all areas, all learners obtain an appreciation of what needs to be achieved in these circumstances.
You may also want to describe in recent IPL problems or issues and the action that was taken.
Copyright © Interskill Learning Pty Ltd 2011 – Commercial in Confidence

9. System monitoring procedures and practices
Commands used to obtain additional information
Scenario 1:
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Quisque accumsan pellentesque sollicitudin. Mauris vel leo elit, at viverra elit. Pellentesque blandit sagittis enim nec sollicitudin. Vestibulum mollis odio quis risus euismod vel cursus augue vestibulum. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus.
Scenario 2:
Graphics: You may want to include some screen shots here (i.e. error messages) depending on the scenarios you have chosen.
Pre-Webinar requirement :
Before running this Webinar you should obtain real life situations from aspects mentioned above and the action that was taken (which may have been correct or incorrect). Add the scenario(s) into the spaces above. Scenarios could include the following:
The system seems to be running slowly (this tests the types of commands to display system activity or whether there might be any outstanding WTO messages they need to respond to).
The system is running extremely slow immediately following an IPL(this tests whether they can obtain information about the IPL parameters).
Error or warning messages are displayed for a device (tape, DASD) and they need to display the status of that component (this tests whether they can obtain this information and interpret it). When the user enters the correct command, a number of different statuses could be supplied (i.e. offline, not readied, boxed)
Error messages indicate that a channel path is not online/faulty. Get them to display channel configuration information (this tests whether they know the command to display this information and can interpret what is displayed).
Presenter:
The internal PowerPoint presentations associated with the system monitoring pathway have discussed various commands that our organization uses to obtain system information. This section provides you with some scenarios (some that have actually occurred and some fictional) and invites you to discuss the methods you would use to handle the situation. You have a total of five minutes to forward me details on how you think the situation above was/or should be, handled. We will then discuss your findings, the action that was taken and any consequences it had.
The start of this Webinar should have instructed the user on the method used to forward this information to you. The learner response time period (five minutes) is a guide only but is purposefully short to put them under the pressures that they might experience as part of these scenarios.
As learners forward responses, you may want to play out the scenario as it relates to those responses. For example, in the first scenario above, person 1 says that they would use a command to display system activity…you could respond by saying that the standard applications are currently running. Meanwhile person 2 has responded by saying they would display whether there were any outstanding messages…and you might say that there is and ask them how they might respond to that message.….so there could be numerous outcomes depending on the action they take.
Copyright © Interskill Learning Pty Ltd 2011 – Commercial in Confidence

10. System monitoring procedures and practices
Using SMF
Scenario 1:
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Quisque accumsan pellentesque sollicitudin. Mauris vel leo elit, at viverra elit. Pellentesque blandit sagittis enim nec sollicitudin. Vestibulum mollis odio quis risus euismod vel cursus augue vestibulum. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus.
Scenario 2:
Graphics: You may want to include some screen shots here (i.e. error messages) depending on the scenarios you have chosen.
Pre-Webinar requirement :
Before running this Webinar you should obtain real life situations from aspects mentioned above and the action that was taken (which may have been correct or incorrect). Add the scenario(s) into the spaces above (as this is a small topic, you may only require one scenario).
Scenarios could include the following:
An I/O error occurs when the system is writing to one of the SMF data sets (tests whether the user can display the status of these data sets).
System programmer asks whether SMF is recording to a log stream or data set.
Error message indicates that SMF is unable to store/create any more records (tests whether the user knows who to contact, or the action to take when there is a problem).
Presenter:
The “Handling SMF and system messages” PowerPoint presentation discussed various commands that can be used to display and control SMF. This section provides you with some scenarios (some that have actually occurred and some fictional) and invites you to discuss the methods you would use to handle the situation. You have a total of five minutes to forward me details on how you think the situation above was/or should be, handled. We will then discuss your findings, the action that was taken and any consequences it had.
The start of this Webinar should have instructed the user on the method used to forward this information to you. The learner response time period (five minutes) is a guide only but is purposefully short to put them under the pressures that they might experience as part of these scenarios.
As learners forward responses, you may want to play out the scenario as it relates to those responses. For example, in the last scenario above, person 1 says that they would use a command to display the status of SMF…you could respond by saying that the command shows that all SMF data sets are full. Meanwhile person 2 has responded by saying they would contact the owner first…and you might say that they have asked you what the status of SMF is. So there could be numerous outcomes depending on the action they take.
Copyright © Interskill Learning Pty Ltd 2011 – Commercial in Confidence

11. System monitoring procedures and practices
Handling system messages
Scenario 1:
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Quisque accumsan pellentesque sollicitudin. Mauris vel leo elit, at viverra elit. Pellentesque blandit sagittis enim nec sollicitudin. Vestibulum mollis odio quis risus euismod vel cursus augue vestibulum. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus.
Scenario 2:
Graphics: You may want to include some screen shots here depending on the scenarios you have chosen.
Pre-Webinar requirement :
Before running this Webinar you should obtain real life situations from aspects mentioned above and the action that was taken (which may have been correct or incorrect). Add the scenario(s) into the spaces above (as this is a small topic, you may only require one scenario). Scenarios could include the following:
There is a need to track messages following a system problem but some messages you expected to see do not seem to have been created. Ask users what action they would take (tests whether users know how to display messages that might be suppressed).
You have recently upgraded your z/OS version and messages you thought were supposed to be suppressed are appearing.
It has been determined that an incorrect MPFLSTxx member is being referenced (tests whether users know how to use the T MPF command).
There is a sudden influx of system console messages that prevents the console from displaying more important messages (tests whether the user knows how to identify whether message flood automation is turned on).
Presenter:
The “Handling SMF and system messages” PowerPoint presentation discussed how system messages could be suppressed and how message flood automation can occur. This section provides you with some scenarios (some that have actually occurred and some fictional) and invites you to discuss the methods you would use to handle the situation. You have a total of five minutes to forward me details on how you think the situation above was/or should be, handled. We will then discuss your findings, the action that was taken and any consequences it had.
The start of this Webinar should have instructed the user on the method used to forward this information to you. The learner response time period (five minutes) is a guide only but is purposefully short to put them under the pressures that they might experience as part of these scenarios.
As learners forward responses, you may want to play out the scenario as it relates to those responses.
Copyright © Interskill Learning Pty Ltd 2011 – Commercial in Confidence

12. System shutdown and IPL
Summary
System shutdown and IPL
Using SMF
Handling system messages
Presenter:
Being the last item in this learning pathway, hopefully it has helped pull together many aspects relating to your role in relation to the monitoring of the system. You may want to expand the points above.
Copyright © Interskill Learning Pty Ltd 2011 – Commercial in Confidence

13. Monitoring the z/OS System
55 minutes
Using System Commands and Consoles
45 minutes
Displaying Active Jobs, Tasks and Users
45 minutes
Displaying Device Status
45 minutes
Using Advanced Monitoring Facilities
PowerPoint
System Monitoring Practices and Procedures
40 minutes
Working with SMF
70 minutes
MPF and Message Suppression
Questions
Presenter:
An opportunity for you to respond to any questions that learners want to ask (5-10 minutes).
Complete the webinar by:
Thanking them for attending.
Outlining what their next step in the training process is.
Mentioning that the webinar will be made available to them for replaying if they require. An will be sent informing them of the details.
Mention that the HR team may send them a survey to complete.
PowerPoint
Handling SMF and System Messages
z/OS System Operation
60 minutes
Webinar
Understanding System Monitoring Tasks and Roles
Copyright © Interskill Learning Pty Ltd 2011 – Commercial in Confidence