Vous êtes sur la page 1sur 64

z/OS System Management Facility (ZOSMF) & WSC User Experience

2009 System z Expo


October 5 – 9, 2009 – Orlando, FL

Session Title: z/OS System Management


Facility (ZOSMF) & WSC User Experience

Session ID: zZS02

Speaker Name: Bette A Brody

© 2009 IBM Corporation

IBM System z
IBM System z
IBM
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States and/or other countries.
IBM* ServerPac* * Registered trademarks of IBM Corporation
IBM (logo) WebSphere*
RACF* z/OS*
The following are trademarks or registered trademarks of other companies.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or
other countries.
Firefox is a trademark of Mozilla Foundation
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license there from.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Internet Explorer is a trademark of Microsoft Corp
InfiniBand is a trademark and service mark of the InfiniBand Trade Association.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered
trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce.
* All other products may be trademarks or registered trademarks of their respective companies.

Notes:
Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual
throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the
storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the
performance ratios stated here.
IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results
they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions.
This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information
may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area.
All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.
Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot
confirm the performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography.
See url http://www.ibm.com/legal/copytrade.shtml for a list of IBM trademarks.

2 © 2009 IBM Corporation

Expo © 2009 IBM Corporation October 2009


Session ZZS02 1 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z
IBM
Agenda
ƒ Overview
ƒ Packaging
ƒ Installation
ƒ Configuring Websphere Application Server OEM Edition 7.0 for z/OS
ƒ Configuring z/OS Management Facility application
ƒ Washington Systems Center Experience
ƒ Summary
ƒ Appendix

2 © 2009 IBM Corporation

IBM

IBM z/OS Management Facility V1.11


Overview

Slides prepared by Anuja Deedwaniya


© Copyright IBM Corporation 2008
© 2009 IBM Corporation

This is an overview of the end to end setup and configuration for the IBM z/OS Management
Facility V1R11, also called z/OSMF.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 2 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


IBM z/OS Management Facility V1.11 overview
The IBM z/OS Management Facility is a new,
product for z/OS providing support for a
modern, Web-browser based management
console for z/OS.
ƒ Designed for system programmers to easily
manage and administer a mainframe system by
simplifying day to day operations and
administration of a z/OS system.
ƒ More than just a graphical user interface, the
z/OS Management Facility is intelligent,
addressing the needs of a diversified skilled
workforce and maximizing their productivity.
– Automated tasks can help reduce the learning
curve and improve productivity.
– Embedded active user assistance (such as
wizards) guides you through tasks and helps
provide simplified operations.

Announced August 18, 2009 -- Announcement letter: 209-241


General Availability: September 25, 2009
4 © 2009 IBM Corporation

IBM z/OS Management Facility (z/OSMF), a new product, will simplify, optimize and modernize
the z/OS system programmer experience starting with problem data management and TCP/IP
Policy based configuration.

z/OSMF will deliver solutions in a task oriented, Web browser based user interface with
integrated user assistance. And z/OSMF will make the day to day operations and administration
of the mainframe z/OS systems easier to manage for both new and experienced system
programmers. The focus is to help improve system programmer productivity, and make the
functions easier to understand and use.

You may ask why is it Version 1 Release 11 if it is the first release? Why not V1.1? The goal
was to align z/OSMF very closely with z/OS itself. Since for its initial release z/OSMF will be
made available at the same time as z/OS V1.11 we wanted to have the same naming convention.

The focus for z/OSMF is both new and experienced system programmers.
It is important to make system programmers more productive, as quickly as possible with the
least amount of training. You want to automate tasks, reduce the learning curve and overall
accomplish this through a modern task-based, browser based-interface.

The z/OSMF works with a mixed skills workforce -- that is to say it suited for professionals who
are new to z/OS, or already skilled on z/OS. Each professional has its own needs and challenges.
For example a novice system programmer may need to understand the ‘big picture’ and
understand how procedures are done, they need to get documentation on certain procedures and
tasks, and implement them according to the rules of the enterprise. The experienced system
programmer has the knowledge on tasks and procedures, so the goal is to make their functions
and easier, and to get them more productive and contributing more to their business.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 3 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

Looking at the area that system programmers traditionally cover – it’s installation, configuration,
maintenance, disaster recovery, and enabling new functions, problem analysis and determination
– essentially making sure the system is available and running correctly.

Challenges for novice system programmer


Problem analysis and management
Getting the “Big Picture”; Gaining organizational knowledge
Product documentation:
Getting enough of the right kind of experience
Unfamiliar concepts and tools: Tasks that require detailed knowledge of command syntax and
formats:
Gaining the trust of more experienced colleagues

Challenges for experienced system programmer:


Too little time and too many tasks with fewer people – need to be more productive
Aging of the workforce – people retiring
Spanning across many products and platforms

Expo © 2009 IBM Corporation October 2009


Session ZZS02 4 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


IBM z/OS Management Facility V1.11
Focus on System Programming – First release
ƒ Provides infrastructure, services and user interface to perform:
– Configure TCP/IP policy based networking functions
• Communications Server Configuration Assistant
– Links for external Web Applications
– Perform problem data management tasks via the Incident Log
• Simplifies process of sending diagnostic data to IBM
– Manage user access to the z/OSMF product

ƒ z/OSMF is comprised a Web browser interface which


communicates with the z/OSMF application
– Runs on the z/OS host
– No separate client install

ƒ z/OSMF makes use of new enabling technologies


– Common Information Model (CIM)
– Common Event Adapter
– System REXX

5 © 2009 IBM Corporation

z/OSMF is offered by IBM as a separately licensed program product for z/OS. (no charge)
Structurally, z/OSMF comprises a Web browser interface that communicates with the z/OSMF
application running on the z/OS host system. Depending on the system management task to be
performed, z/OSMF interfaces with other z/OS components to offer a simplified interface for
performing tasks. These components make up the environment necessary for using the functions
available in z/OSMF. No separate client install is required. z/OSMF includes the following
software:
• IBM WebSphere® Application Server OEM Edition for z/OS Version 7.0, which provides
a native application server runtime environment for z/OSMF. It is new for z/OS V1R10.
• A set of administration and system management tasks that run on IBM WebSphere
Application Server OEM Edition for z/OS.
• Technologies for serving the Web browser interface, such as JavaScript™ and a Dojo
framework.
Depending on the system management task being performed by the user, z/OSMF makes use of
new enabling technologies on z/OS. For example, the Incident Log task of z/OSMF uses services
provided by the following z/OS components:
• Common Information Model (CIM) server running on the host z/OS system. This
component provides the z/OS data and administrative capability.
• Common event adapter (CEA). This component enables CIM providers to identify,
receive and process selected z/OS events.
• System REXX™ (SYSREXX™). This component provides an infrastructure through
which REXX execs may be run outside the normal TSO/E or batch environments, using a
simple programming interface.

The goal of this architecture is to provide simplified systems management function through a
common, easy-to-use interface.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 5 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


z/OSMF packaging
ƒ z/OSMF V1R11 is comprised of:
– FMID HSMA110 (IBM z/OS Management Facility)
• 5665-S28 (product)
• COMPID 5655S28SM – z/OSMF Core
• COMPID 5655S2805 – z/OSMF Incident Log
• COMPID 5655S28CA – Config Assist
• 5655-S29 (support and service)

– FMID HBBN700 (IBM WebSphere Application Server OEM Edition


for z/OS V7.0)
• COMPID 5655I3512 - WEBS APP SVR OEM

ƒ z/OSMF is not included in the z/OS product (base element or


optional element)

6 © 2009 IBM Corporation

This is a no charge product. Besides ordering 5665-S28 you need to also order 5655-S29 which
is for Support and Service (also no charge). This product is not included in z/OS product.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 6 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Prerequisites
ƒz/OS Management Facility requires z/OS V1 R10 and later
– z/OS V1R10 requires additional service, as defined in the program directory

ƒThe Configuration Assistant for z/OS Communications Server portion of


z/OS Management Facility requires z/OS V1.11 or later.

ƒIncident Log function in z/OS Management Facility requires the following


z/OS components to be configured
– CIM server
– Sysplex Dump Directory
– CEA
– System Rexx
– Logger

ƒClient machine (no client machine install requirements)


– Windows XP® operating system and later
– Supported browsers:
• Mozilla Firefox 3.0.6 (recommended)
• Mozilla Firefox 2
• Internet Explorer® 7
• Internet Explorer 6
7 © 2009 IBM Corporation

z/OSMF is supported on z/OS V1.10 and above. On R10 additional service is required. There is
no client install requirements. The client/ browser machine is a Windows XP® operating system
and supported browsers: Mozilla Firefox 3.0.6 (recommended), Mozilla Firefox 2, Internet
Explorer® 7, Internet Explorer 6.

Note: Additional service required on z/OSV1R10 system is stated in the program directory. The
required Conditional Operational Requisites APARs When Running With z/OS V1.10.0 are:
FMID APAR Function
HPG7750 OA28702 CIM function
HBB7750 OA28275 CEA function
HBB7750 OA27226 Logger function
HBB7750 OA26100 IPCS support
HBB7750 OA26802 REXXLIB support

Expo © 2009 IBM Corporation October 2009


Session ZZS02 7 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


IBM z/OS Management Facility
z/OS application, browser access

Browser z/OS

z/OS
HTTP(s) Management
Facility
application

ƒ z/OS Management Facility is a WEB 2.0 application on z/OS


– Manages z/OS from z/OS
– Browser communicates with z/OSMF via secure connection
8 © 2009 IBM Corporation

This chart explains the structure for z/OSMF and how it fits into the z/OS environment.
z/OSMF is running on the z/OS system on the right hand side and it manages z/OS from z/OS
itself. z/OSMF is an application on z/OS with direct access to z/OS data and information, and it
has a browser interface from the workstation. z/OSMF contains the GUIs and the application
code. Everything is installed on the z/OS server and there are no client side install requirements.

In the middle of the screen is a workstation with a browser and it communicates with z/OSMF via
HTTPS. z/OSMF is a Web 2.0 based solution. It incorporates a browser interface which
communicates with the z/OS system. The browser can be anywhere... in the data center or
around the world. You just need a secure connection.

And on the left is a screen capture of the z/OSMF welcome page once you log into z/OSMF. This
will be covered more in the follow on slides.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 8 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


IBM z/OS Management Facility
The Application Stack

Browser z/OS V1.10 or V1.11 LPAR

App. server z/OS elements

HTTP(s) ƒz/OS MF app ƒ CIM


ƒServlets ƒ System REXX
ƒDOJO/JAVA ƒ RACF
script ƒ and others

Java apps
ƒ Parts of z/OS Management Facility, and Java-
z/OS
CIM
such as the Incident log capability, based server
components use JAVA and CIM CIM client eligible
eligible for zIIP
for zAAP

9 © 2009 IBM Corporation

It requires an application server and a runtime environment. The app server box you see on the
right is really a special version of WebSphere Application Server V7.0 which is pre-configured
and pre-packaged together with zOSMF. It is comes pre-configured so that it is specifically
optimized for zOSMF application serving. It comes packaged together with zOSMF, so there are
additional scripts and documentation to make it easier to set up and config this runtime on z/OS.

Once WebSphere Application Server has been set up and installed, the z/OS Management
Facility application itself is deployed into this runtime and this is where the application serve lets
and GUIs reside. zOSMF uses the DOJO technology for GUIs, which uses Java script and that
helps improve performance overall because the GUI can perform all the graphics rendering in the
browser on the workstation.

This application stack communicates with z/OS components and the components can be
whatever that is applicable for that particular task there are not technical limitations. For this
initial release the tasks and components we have we have added (in alphabetical order) are the
Configuration Assistant for the z/OS Communications server – which performs network
configuration, Links – which is a way for you to list links to documentation, information, and
product information in an easily accessible location. Incident Log is our problem determination
solution, which provides a consociated view of abend-related problems on your system or sysplex
with details behind it and the ability to send the data collected as a result of a problem to a
destination of choice IBM or ISVs. And we also provide some zOSMF administration functions
which enable you to use the tasks in zOSMF.

The applications utilize the dojo framework and Javascript and run on an special version of
WebSphere® Application Server. The applications exploit functions provided by z/OS system
components.

Everything is installed on the z/OS server and there are no client side install requirements.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 9 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Initial Login View

Welcome page when user


first accesses the URL
and has not logged in yet

ƒ To log in you will need a z/OS userID which has been defined and enabled for
z/OSMF (and the WebSphere runtime environment)
10 © 2009 IBM Corporation

Once z/OSMF has been set up and configured and started on a system you point your browser to
the URL for the z/OSMF instance. The URL is basically the host name, the port name and the
context root for z/OSMF. You can see the welcome screen for a guest On the left hand side is the
navigation pane with the login at the top and the large center pane is the work area where the
tasks will open up. To log in a z/OS userID is required which has been defined and enabled for
z/OSMF and the WebSphere runtime environment. Guidance is provided for creating userids and
enabling them for z/OSMF.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 10 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


IBM z/OS Management Facility
Welcome Page

11 © 2009 IBM Corporation

The initial functions include z/OSMF Administration, Incident Log, Configuration Assistant for
z/OS Communication Server and Links

z/OSMF Administration gives the customer a:


• Display welcome page and deployed z/OSMF applications in
Task list
• Provides Authorization services for the administrator
• Allows Dynamic addition of links to non-z/OSMF resources

Under the Problem Determination category on the navigation bar, you will find the Incident
Log task.
This first release will help all system programmers with problem data management tasks,
providing experienced teams with procedural advantages through an incident log summary and
detail views of z/OS dump incidents. The Incident Log provides a consolidated list of SVC Dump
related problems, along with details and diagnostic data captured with each incident. It also
facilitates sending the data for further diagnostics.

Configuration Assistant from Communication Server


Simplified configuration and setup of TCP/IP policy-based networking functions

Another category on the navigation bar is Links which:


• Provides common launch point for accessing resources beyond
the IBM z/OS Management Facility.
• Some links are pre-defined in the product.
• The administrators can define additional links to share commonly
used resources for their installation.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 11 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

So once you’ve logged in , this screen shows you the full scope of what z/OSMF provides in this
first release. And really the first user that logs in as a z/OSMF administrator. So when z/OSMF is
first set up, always the first ID is that of an administrator – that is a requirement for setup. And
the reason for this it allows the first person to get in and to add and enable others.
So this is the welcome screen for a user or an administrator. You’ll notice the navigation pane on
the left is populated with multiple categories with tasks under each category. You have the
configuration category with the Configuration Assistant , the Links category with a bunch of links,
Problem Determination with incident log, and z/OSMF Administration. The main page is now
different and it lists and gives you access to documentation on what you can do with the various
tasks in z/OSMF. On the top right of the screen (it is small) there is and ‘About’ tab which
provides information on the release and service level for z/OSMF.

Welcome page when the user has logged in. This particular navigation panel is displayed when
the z/OSMF administrator logs in. When the user logs in with the administrator’s userid, all tasks
are available to work with.

For all other users, after initial login, the user becomes an ‘Authenticated Guest’ and can access
information about z/OSMF and some permitted tasks.
The z/OSMF administrator must define the user to z/OSMF and assign a role in order for the user
to start working with z/OSMF tasks. Note: By default a z/OSMF user with a ‘user’ role will not see
the z/OSMF Administration category.

z/OSMF Administration category for the administrator:


Authorization services for administrator to add z/OSMF users and roles
Allows the administrator to dynamically add links to non-z/OSMF resources, e.g. ISV products,
commonly used installation Web sites.

Configuration category with Configuration Assistant for z/OS Communication Server


Simplified configuration and setup of TCP/IP policy-based networking functions.

Links category:
Provides common launch point for accessing resources beyond the z/OSMF
Some links are pre-defined in the product.

Problem Determination category with the Incident Log task


The Incident Log provides a consolidated list of SVC Dumps, along with details and diagnostic
data captured with each incident. It also facilitates sending the data for further diagnostics.

One more chart on Links ...


We talked about the Links task under the Administration cat, and what that did was enable an
administrator to define links for the z/OSMF users . The Links Category on the other hand is
where all the links are visible to all users. We do pre-define about 6 links to various IBM sites like
the internet library and the service support center or Shop zSeries and the administrator can
define more links and they will show up here.

Focusing on z/OSMF Administration


The primary purpose of the tasks provided are authorization functions for the administrator or
authorize additional users. These users have the ability to add users (those with valid z/OS
userIDs) and to assign roles to them so these users can get access to different tasks. In this
release we have pre-defined roles and until a user is assigned a role, then they cannot perform
any tasks.

There is a Links task under Administration allowing the administrator to dynamically add links to
non-z/OSMF resources, e.g. ISV products, commonly used installation Web sites. Purpose here
is for the system programmers to work with different products. It’s a handy place to create a
common list for frequently used information and is accessible to the whole team.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 12 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Incident Log – Summary Information

Many fields, set tracking IDs

Context menu with actions

Set the
duration

12 © 2009 IBM Corporation

This is a screenshot of what the incident log task would look like. This is from a test system so you
may see some variations you might not see in a real production system. This shows a combination of
user initiated dumps through the dump command, and some abend dumps which occurred in the
system. You see the dump title and then the time. By default it displays 3 days worth of incidents –
but you can change the duration to whatever you need it to be.

It shows a lot of fields related to that incident ... system, sysplex, z/OS release, component ... and you
see two other fields the problem number and tracking ID – you can set these for individual incidents,
most of the other fields are fixed and are really properties of that incident.

The problem number field – its intent is to enter an meaningful external problem number– maybe an
IBM problem number or an ISV problem number. And you can update it from a number of areas – it
can be an action pull down – you right click an incident, a box appears and you can set the problem
number there, or from another panel.

The intent for tracking ID is to tie a particular incident with your internal tracking system.
Focusing on the dropdown/ popup box, these are the specific actions you can take with any incident.
You can also delete an incident – it will ask you a few things like do you want to allow the next dump
for this particular set of symptoms and it will interface with DAE to allow the next dump. Even without
deleting, you can allow a next dump. When you do delete an incident, ALL information associated wit
that incident is deleted.

You can send the diagnostic data and view the diagnostic details. You can view FTP job status. So if
you send the diagnostic data you can view the FTP status for that submitted job.

If you were to use the actions dropdown from the taskbar at the top, it allows you to do further things,
like work with you tables, filtering, sorting, configuring columns. You can also sort within the table by
clicking on the columns. You can filter using single or multiple filters for more complex sorts.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 13 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

Context Menu brought up when you right click on an incident. You could also select the incident, and
then click on the Actions button to get a similar menu.

IBM System z IBM


Incident Log – Incident Details

Tab shows lists of data


(logrec and error log)

13 © 2009 IBM Corporation

The Diagnostic Details panel displays all available information about the incident including a
reformatted version of the summary data in the Incidents table. If incident is an Abend there will
be additional data listed: Abend code, Load Module, Symptom String
There is another tab showing the list of diagnostic data collected for that incident.

Here is a sample view on diagnostic details taken form the summary information. You see the
details about the dump and you can see two editable fields – this is the problem number and
tracking number which we covered earlier. There is also a second tab – the Diagnostic data tab –
and it will show you the lists of data - the LOGREC and error log captured for this incident. It will
show data sets names in z/OS and it allows to selectively send diagnostic data if required. When
you do send diagnostic data from the incident log panel, it sends ALL of the data associated with
the incident. Here you have to option to only send a subset.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 14 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Incident Log – Send Diagnostic Data

Wizard guides you through the send

14 © 2009 IBM Corporation

The send action is a beautifully guided wizard. It shows the data, allows you to select destination,
associate that with a firewall profile, and allows to you edit the built JCL – specifically the job card
information, because every customer has different requirement for the job card. And once you
edit the job card, it will be persistent from that point on, until you edit it again. Then the complete
JCL is built and away it goes.

The wizard guides you through the steps to send diagnostic data over to either IBM, an ISV, or
any other destination. It prepares (terses) the information needed to send the data to IBM (or
other target) and initiates the ftp action.

You can also later view the status of the FTP job.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 15 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Incident log - Destinations

Pre-loaded with IBM destinations,


or add your own

15 © 2009 IBM Corporation

This is an example of the FTP destinations and IBM has pre-defined four destinations (the top 4
you see there) such as for MVS and Tivoli. You have the ability to add more destinations to IBM
or ISVs or elsewhere. You can set up the destination so that it is anonymous, or if it requires an
ID and password. Not shown here, but in a different window, you can also define firewall profiles
and you can associate a firewall with a particular destination.

The user can define destinations where incident diagnostic data can be sent via FTP. In addition
they can define FTP profiles for firewall definition and associate the two.

When the send action is initiated, the Wizard guides you through the steps to send diagnostic
data over to either IBM, an ISV, or any other destination, prepares (terses) the information
needed to send the data to IBM (or other target) and initiates the FTP action.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 16 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


z/OSMF Configuration
Configuration Assistant for z/OS Communications Server
ƒ A GUI used to generate configuration files for z/OS Application
Transparent-Transport Layer Security (AT-TLS), IP Security (IPSec),
Network Security Services (NSS), Policy Based Routing (PBR), Quality of
Service (QoS), and Intrusion Detection Services (IDS)
ƒ Originally available as a Microsoft® Windows® web download since z/OS
1.7
– Functions have grown over time
– All functions available with Windows are also provided with z/OSMF
– If you are familiar with the Windows GUI, the Configuration Assistant on z/OSMF is
essentially the same
ƒ Now available with z/OSMF V1.11 on z/OS V1.11
– Configuration files can now be saved to local disk storage accessible to your z/OS
system where the Configuration Assistant is running so FTP (from Windows) is not
required
– Import configuration text files in cases where users have already defined policies and
would like to begin using the Configuration Assistant

16 © 2009 IBM Corporation

The Configuration Assistant reduces configuration complexity by providing a consistent and easily
manageable interface to implement AT-TLS, IPSec, NSS, PBR, QoS, IDS, and DMD. It can
dramatically reduce the amount of time required to generate and maintain policy files for these
disciplines. The Configuration Assistant is intended to replace manual configuration of the policy
disciplines, but it can also incorporate policy data directly from the Policy Agent.

New for V1R11:


ƒ Defense Manager Daemon configuration: The CA has added the ability to configure DMD.
ƒ New System SSL Functions: AT-TLS has been updated to support new SSL functions, and
the CA now includes that configuration.
ƒ Application Setup Tasks: The CA now includes tasks with instructions to assist in
deployment of each supported technology.
ƒ Usability Improvements: Configuration of IPSec and AT-TLS is now easier.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 17 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Configuration Assistant for z/OS Communications Server
As part the IBM z/OS Management Facility V1.11

Create configuration files for any


number of z/OS images with any
number of TCP/IP stacks per image.

Click on "Action" and


select "Configure" to begin
configuring that technology.

Select the
TCP/IP stack
that you want to
configure and
the technology,
such as AT-TLS
or IPSec.

17 © 2009 IBM Corporation

This is a screenshot of what the configuration assistant looks like on z/OSMF. As you can see it
lists all the different technologies that the communications server can create and activate policies
for. The Web-based tool and the z/OS Management Facility function are the same. The benefit
to running the COnfig Assistant to the z/OS Comm Server from z/OSMF is that now you do not
have to download/FTP your network configuration files from z/OS to the Windows workstation
and back again – with z/OSMF you directly on z/OS.

When you enter the Configuration Assistant, this is the Main Perspective. From here you can
create the z/OS Images and TCP/IP stacks for the systems that you want to configure for any of
the supported technologies. Select the TCP/IP stack that you want to configure and the
technology such as IP Sec or AT-TLS. Click on "Action" and select "Configure" to begin
configuring that technology.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 18 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


z/OSMF Help

18 © 2009 IBM Corporation

z/OSMF provides extensive online help information to assist with understanding and performing a
task, troubleshooting problems, entering information, and using all aspects of z/OSMF. Three
types of help are available in z/OSMF: panel-level help, message help, and field-level help. The
help information can be accessed after z/OSM is authenticated.

Panel-level help: provides more details about a panel or dialog box. For example, panel-level
help describes each field or column displayed on a panel and the actions you can initiate from a
panel. To open panel-level help, click the Help link (located in the upper right-hand corner of each
panel) or the Help button (located near the bottom of each dialog box, if help is available). Details
about the panel or dialog box are displayed in a new browser window. The active help topic is
highlighted in the navigation area so you can see where it is located within the hierarchy and
easily navigate to related information.

Message help: provides more details about a message. Message help includes a detailed
explanation of the message, a description of any reason codes listed in the message, and
suggestions for actions you can implement to resolve the issue. To open message help, click the
message ID link that is displayed in the message.

Field-level help: describes the type of data to enter into a field, the format of that data, and
indicates when required information has been omitted. Field-level help is displayed to the right of
the field when an error occurs. Also, a status icon is displayed within the field. After you correct
the errors, the status icon and the message are removed.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 19 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


IBM z/OS Management Facility V1R11
z/OSMF Architecture

Web z/OS LPAR


V1R10 or V1R11
Browser
WAS OEM
z/OSMF Welcome Page
z/OSMF z/OS components
HTTP(s) servlets (CIM, Sysrexx,
DOJO/JAVA Security server,
SCRIPT
CEAS…)

Initial Functions
¾Configuration Assistant
¾Links
¾Incident Log
¾z/OSMF Administration

19 © 2009 IBM Corporation

This chart explains the structure for z/OSMF and how it fits into the z/OS environment.
z/OSMF provides a web browser interface that communicates with the z/OS system with direct
access to z/OS data and information via HTTPs. z/OSMF is hosted on the IBM WebSphere®
Application Server OEM Edition for z/OS that is included with the product. The application server
runtime is special version of WebSphere Application Server V7.0 for use by z/OSMF application.
The z/OSMF applications exploit functions provided by z/OS system components. Everything is
installed on the z/OS server and there are no client side install requirements. End-end
configuration and setup of the application stack is simplified by using the scripts provided with the
product.
Once WebSphere Application Server has been set up and installed, the z/OS Management
Facility application itself is deployed into this runtime and this is where the application serve lets
and GUIs reside. Portions of z/OSMF use the DOJO technology for GUIs, which uses Java script
and that helps improve performance overall because the GUI can perform all the graphics
rendering in the browser on the workstation.

System Programmers invoke the application URL via a supported browser and login using their
z/OS logon id. The main navigator application authenticates and authorizes the user to a set of
tasks which are then loaded into the web browser.

The z/OSMF welcome page is displayed once the user logs in to zOSMF. It will be covered more
in the follow on slides.

For this initial release the tasks and components are the Configuration Assistant for the z/OS
Communications server – which performs network configuration; Links – which is a way to list
links to external websites and products in an easily accessible location; Incident Log - the
problem determination solution, which provides a consolidated view of abend-related problems on
the system or sysplex with details behind it. It also provides the ability to send the data collected

Expo © 2009 IBM Corporation October 2009


Session ZZS02 20 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

as a result of a problem to a destination of choice. Various z/OS facilities are employed to provide
data and interact with the web applications.
The initial functions include z/OSMF Administration, Incident Log, Configuration Assistant for
z/OS Communication Server and Links
z/OSMF Administration gives the customer a:
• Display welcome page and deployed z/OSMF applications in
Task list
• Provides Authorization services for the administrator
• Allows Dynamic addition of links to non-z/OSMF resources
Under the Problem Determination category on the navigation bar, you will find the Incident
Log task.
This first release will help all system programmers with problem data management tasks,
providing experienced teams with procedural advantages through an incident log summary and
detail views of z/OS dump incidents. The Incident Log provides a consolidated list of SVC Dump
related problems, along with details and diagnostic data captured with each incident. It also
facilitates sending the data for further diagnostics. Configuration Assistant from
Communication Server
Simplified configuration and setup of TCP/IP policy-based networking functions
Another category on the navigation bar is Links which:
• Provides common launch point for accessing resources beyond
the IBM z/OS Management Facility.
• Some links are pre-defined in the product.
• The administrators can define additional links to share commonly
used resources for their installation.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 21 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM

IBM z/OS Management Facility V1.11


Installation, Setup and Configuration

Slides prepared by Anuja Deedwaniya


© Copyright IBM Corporation 2008
© 2009 IBM Corporation

This is an overview of the end to end setup and configuration for the IBM z/OS Management
Facility V1R11, also called z/OSMF.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 22 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Installation
Installation scenarios:
ƒ z/OS V1R11 ServerPac
– Provides default customization via post install customization
– Use the WAS OEM Configuration Guide and z/OSMF User’s guide and
Configuration scripts to setup if defaults are not viable
– Provided for both Full System Replace and Software Upgrade installation
paths
ƒ z/OSMF V1R11 CBPDO
– Can be installed on z/OS V1R10 or z/OS V1R11
– Use Program directory to get started
– Use the WAS OEM Configuration Guide and z/OSMF User’s guide and
Configuration scripts to setup
ƒ Setting additional instances (test, service, backup)
– Follow the User’s guide for instructions

21 © 2009 IBM Corporation

z/OSMF can be ordered in a ServerPac which provides a default customization, therefore when
the system is brought up there is an instance of z/OSMF up and running and all you have to do is
point your browser to it. If system supplied defaults are not viable, the best approach is to use
the provided scripts.

z/OSMF can also be ordered in a CBPDO which means z/OS V1.10 customers can order
z/OSMF by itself and get the WAS OEM edition and the z/OSMF application.

z/OS V1.11 customers who did not order z/OSMF with R11 ServerPac can do so at a later date
with CBPDO.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 23 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Installation
V1R11 ServerPac
ƒ The z/OS V1R11 ServerPac with z/OSMF V1R11 will have both the
FMIDs which make up z/OSMF installed in the appropriate directories
ƒ ServerPac provides post-install jobs to create a default instance of
z/OSMF setup end-end with all applications deployed. This includes:
– Allocate and mount z/OSMF product and data file systems
– Install and set up WAS OEM for z/OSMF and deploy z/OSMF applications
– Create ZOSMFAD administrator identity
– Set up z/OS for Incident Log (CIM Server, Sysplex Dump Directory, Logger,
Log streams, System Rexx, Parmlib setup etc).
– Prime z/OSMF data repository with ZOSMFAD userid

ƒ Note: When defaults cannot be taken, the User guide (s) should be
followed to setup the product and use the supplied scripts

22 © 2009 IBM Corporation

z/OS V1.11 ServerPac will include z/OSMF provided it was ordered and selected from the order
checklist. When you order z/OSMF in the z/OS V1.11 ServerPac, not only is z/OSMF installed in
the ServerPac but there are also post-install steps and jobs taking the user through end to end
set up for WAS OEM and z/OSMF to create a default instance. This includes the defaults
provided with z/OSMF. Therefore when z/OS V1.11 is brought up, so is z/OSMF V1.11.

It performs all of the requirements, including allocating and mounting file systems , creating the
administrator identity, setting up all the z/OS requirements, .. in the stack chart that was shown, it
is not just WAS OEM, and z/OSMF application, but it communicates with many components in
z/OS . So it ensures all the components are required are all correctly set up – not only in terms of
component set up with Parmlib members or directories, but also from a security perspective for
permissions and user definitions. The administrator userID is defined at startup, so you are truly
ready to go and use this product.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 24 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Installation
z/OSMF V1R11 CBPDO (on z/OS V1R10 or z/OS V1R11)
The program directory provides sample jobs to lay down both the FMIDs
making up z/OSMF in the appropriate directories
ƒ If you are installing on z/OS V1R10, apply prerequisite service
ƒ Setup z/OS as described in the Planning section of z/OSMF User’s
Guide and the WAS OEM 7.0 Configuration Guide
ƒ Collect all the input as described in the WAS OEM Configuration
Guide
ƒ Collect all the inputs for application setup as described in the z/OSMF
User’s Guide
ƒ Scripts are provided to configure and setup WAS OEM 7.0 and
z/OSMF V1R11, as well as some of the required z/OS setup

23 © 2009 IBM Corporation

In case of a CBPDO the documentation provided must be used. It has a planning section which
identifies all the components and what functions need to be set up along with samples and
scripts. The planning section also puts together everything you will need to complete the set up
end to end so you can collect the information required ahead of time..... because very often it is
not just one person with all the information, .... you need the networking person to give you some
information, the security person needs to give you more information, the system programmer
needs to provide information on the data sets and volumes.

There are scripts guiding you through the setup, with information you have collected as part of the
planning exercise.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 25 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Installation
For all scenarios:
ƒ Verify z/OSMF has been properly setup and configured
– Script is provided to verify that all the z/OS setup was completed successfully
ƒ Verify the Client environment
– A client environment checking tool has been provided to check the browser
settings. The URL to access is documented in the IBM z/OS Management Facility
User's Guide
ƒ Start z/OSMF
– Starting WAS OEM will also start z/OSMF
Note: At the completion of above setup, the administrator - ZOSFMAD
user can access all tasks on the UI.
ƒ To add additional users,
– The administrator, ZOSMFAD, needs to add and assign those users the
appropriate roles on the UI under Administration category.
– Use the sample scripts to generate and submit the RACF commands needed to
connect user to Core (includes Configuration Assistant) and/or Incident Log.
• Note: You will need the z/OSMF config file as input

25 © 2009 IBM Corporation

Scripts are provided to ensure the set up is correct and complete for the flow to work with so there is
verification for basic z/OSMF setup and for the incident log which has the biggest amount of setup
requirements. This is set up correctly all the way down to where the dumps are taken, where I’ts
visible as an incident, all the way up to the delete.

A client check is provided as well. It is invoked through a URL and it will actually check the browser
environment. Not only giving a detailed report of the browser setting, but also point out any setting not
correct for z/OSMF to run and how to fix it.

Once all the verifications are completed, WAS OEM and z/OSMF may be started. Once the
administrator is set up by default, additional scripts are provided to add additional users. They
encompass everything required to define additional users, end to end, authorization they may require
so you can easily enable more users.

Starting WAS OEM:


In UNIX®
$IZU_APPSERVER_ROOT/AppServer/bin/startServer.sh $APPSERVER_NAME

Where by default:
APPSERVER_ROOT = /u/wasoegcfg
APPSERVER_NAME= server1 and can be found in:
$IZU_APPSERVER_ROOT/AppServer/profiles/default/config/cells/*/nodes/*/servers

On MVS Console
START appserver_proc_name,JOBNAME=server_short_name,
ENV=cell_short_name.node_short_name.server_short_name
For example:

START BBN7ACR,JOBNAME=BBNS001,ENV=BBNBASE.BBNNODE.BBNS001

Expo © 2009 IBM Corporation October 2009


Session ZZS02 26 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z
IBM System z
IBM
z/OSMF Configuration and setup detailed flow
ƒ Configuring WAS OEM

ƒ Configuring z/OSMF

ƒ Creating new users for z/OSMF

ƒ Setting up Sysplex Dump Directory – (backup foil)

27 © 2009 IBM Corporation

Now we will go into more detail on customizing WAS OEM and z/OSMF.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 27 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


WAS OEM v7 Configuration – Overview
ƒ Pre-requisites for WAS OEM
– Some z/OS components and PARMLIB members need to be setup prior to configuring WAS OEM
ƒ WAS OEM configuration is achieved in 3 phases
– Step A – Config - Invoke WASOEM.sh in config mode:
• Specific configuration and customization settings are collected as you respond to a series of
interactive prompts.
• A new version of the response file is generated that reflects your responses to the prompts.
• Unless you specify the -nooverride parameter, the new response file is then updated with any
information that you provided in the override response file.
• Three security jobs are created for you to run to set up the security env
– Step B – Security Customization - Submit Security Customization Jobs
• BBOSBRAK
• BBOSBRAM
• BBOCBRAK
– Step C – Create Instance - Invoke WASOEM.sh in create mode:
• The helper script createWASOEMHFS.sh is invoked to create an instance of IBM
WebSphere Application Server OEM Edition for z/OS
• The WAS admin script updateConfigWASOEM.py is invoked to modify the
configuration settings for this IBM WebSphere Application Server OEM Edition for
z/OS instance.
27 © 2009 IBM Corporation

Expo © 2009 IBM Corporation October 2009


Session ZZS02 28 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Install Step A:
Running WASOEM.sh in config mode
ƒ Syntax :
WASOEM.sh -config
Where :
• Required parameters
-config = indication this is the configuration phase of install
• Optional parameters
-showmsgprefix = indicates that message prefixes should display on the
console.
-noclear = indicates that the screen should not be cleared between
prompts.
-fastpath = indicates that you want to use the variable values that are
already specified in the response file, and/or in the override response file.
When you specify this parameter, you are not prompted for new values for
the response file variables during the configuration process.
-nooverride = indicates that you do not want to use the variable values that
are specified in the override response file.
-v = additional detail included in the log file and displayed on the console.
-responsefile = specifies the fully-qualified name of the response file that
29 you want WASOEM.sh to use as its input file. © 2009 IBM Corporation

IBM System z IBM


Install Step A:
Running WASOEM.sh in config mode (cont)
ƒ If you do not specify a filename to save the configuration into, it will be saved
in /etc/zWebSphereOEM/V7R0/conf/
ƒ Make sure when this is run, you also have access to:
– load module plexname
– createWASOEMHFS.sh
– modifyWASOEM.py
ƒ These are located in the same dir as WASOEM.sh
(/usr/lpp/zWebSphereOEM/V7R0/bin). The PATH should also be setup so these
scripts can be referenced.
ƒ This, and all other shell scripts must run in either an OMVS, telnet or rlogin
session. It cannot be run from under ISHELL.
ƒ This shell script invokes WAS install technology in the form of the zpmt.sh
install tool. This script accepts the responseFile after it has been tailored and
produces 3 security jobs which are submitted in the next step

30 © 2009 IBM Corporation

Expo © 2009 IBM Corporation October 2009


Session ZZS02 29 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Install Step B:
Running the Security Customization Jobs
ƒ The newly created customization jobs are located in the $zTargetHLQ.CNTL library.
– Ex: if the default.Responsefile contained a setting of
$zTargetHLQ=BBN.V7R0.CONFIG1.ZPMTJOBS Then the security customization
jobs would be found in the library BBN.V7R0.CONFIG1.ZPMTJOBS.CNTL
ƒ The security customization jobs must be submitted in the following order:
– BBOSBRAK
• creates the Administrator ID ${zAdminUserid} without a password, or password
phrase. This is the ID used to log onto the WAS Admin EUI
– BBOSBRAM
• creates the various home directories for IBM WebSphere Application Server
OEM Edition for z/OS.
– BBOCBRAK
• creates the following RACF users and profiles that are required by the IBM
WebSphere Application Server OEM Edition for z/OS node.

31 © 2009 IBM Corporation

IBM System z IBM


Install Step C:
Running WASOEM.sh in create mode
ƒ Syntax :
WASOEM.sh -create <configuration_name>
Where :
• Required parameters
-create = indication that this is the instance creation phase of install
• Optional parameters
-showmsgprefix = indicates that message prefixes should display on the
console.
-noclear = indicates that the screen should not be cleared between
prompts.
-v = additional detail included in the log file and displayed on the console
-nocustom = indicates that you do not want to run the customization
portion of the WASOEM script.

32 © 2009 IBM Corporation

Expo © 2009 IBM Corporation October 2009


Session ZZS02 30 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


z/OSMF Configuration Overview
Action to perform Script invocation Peformed by

“Step 1: Create the initial configuration” izusetup.sh –config filename [-system sysname] Superuser

“Step 2: Configure security for the core functions” izusetup.sh –racfcore configfilename Superuser

“Step 3: Configure security for the Incident Log” izusetup.sh –racfincidentlog configfilename Superuser

“Step 4: Verify the RACF security setup” izusetup.sh –file configfilename –verify racf Superuser

“Step 5: Prime the z/OSMF data file system” izusetup.sh –file configfilename -prime Superuser

“Step 6: Complete the setup for core functions” izusetup.sh –file configfilename –core z/OSMF administrator

“Step 7: Complete the setup for the Incident Log” izusetup.sh –file configfilename –application log z/OSMF administrator

“Step 8: Verify the previous actions” izusetup.sh –file configfilename –verify [all | core | log] z/OSMF administrator

“Step 9: Verify the z/OSMF configuration” At the end of the z/OSMF configuration process, you can verify the z/OSMF administrator
success of your configuration changes by opening your browser
to the z/OSMF Welcome task.

33 © 2009 IBM Corporation

The table describes the steps to configuring z/OSMF. The first column describes the 9 steps to
configuring z/OSMF. The second column contains the commands used to invoke the script to
perform the action. The third column identifies the user required to perform the action.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 31 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z
IBM System z
IBM
Step 1: Create the initial z/OSMF configuration
izusetup.sh –config filename [-system sysname]

Submitted from SUPERUSER ID izuconfig.sh

•Prompt user for z/OSMF configuration data


•Requires completed planning worksheet

izusetup.sh •Create mount point for z/OSMF data file system

•Allocate and mount z/OSMF data file system

•Save configuration data to configuration file

../defaults/izudflt.cfg
configfilename.cfg

Remember this
file name

33 © 2009 IBM Corporation

This is the first step in the configuration for z/OSMF. It creates the configuration file needed for
the remainder of the steps in the configuration. The installer is prompt for values that will be
saved to a caller specified configuration file. The planning worksheet MUST be completed prior to
this step. This step also allocates and mounts the z/OSMF data file system (if it doesn’t already
exist). It creates the logs directory on the data file system that is used to store the run time logs
for z/OSMF.

Some highlights for this step:


• Requires superuser authority with a UID of 0 to run this script.
• Provides option to setup Incident Log
• Provides option to setup CIM
• Default saved configuration file format is izudflt-$(date +"%m%d%y")_$(date
+"%H%M%S").cfg and is saved in $IZU_CONFIG_DIR (/etc/zosmf)
• User specified configuration file can also be provided to prime the prompts with default
values
• In creating the z/OSMF data file system both zFS and HFS file systems are supported

Expo © 2009 IBM Corporation October 2009


Session ZZS02 32 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


configfilename.cfg

IZU_ADMIN_NAME ZOSMFAD
../defaults/izudflt.cfg
IZU_ADMIN_PROC OMVS0802
IZU_ADMIN_ACCOUNT MVS420
IZU_ADMIN_NAME ZOSMFAD
IZU_ADMIN_REGION 2096128
IZU_ADMIN_PROC OMVS0802
IZU_ADMIN_UID 9001
IZU_ADMIN_ACCOUNT MVS420
IZU_ADMIN_GROUP SYS1
IZU_ADMIN_REGION 2096128
IZU_ADMIN_HOME /u/zosmfad
IZU_ADMIN_UID 9001
IZU_ADMIN_PROGRAM /bin/sh
IZU_ADMIN_GROUP SYS1
IZU_WAS_PROFILE_PREFIX BBNBASE
IZU_ADMIN_HOME /u
IZU_CLUSTER_TRANSITION_NAME BBNC001
IZU_ADMIN_PROGRAM /bin/sh
IZU_APPSERVER_GROUP WSCFG1
IZU_WAS_PROFILE_PREFIX BBNBASE
IZU_APPSERVER_ROOT /u/wasoemcfg
IZU_CLUSTER_TRANSITION_NAME BBNC001
IZU_CELL_SHORT_NAME BBNBASE
IZU_APPSERVER_GROUP WSCFG1
IZU_CONTROL_USERID WSCRU1
IZU_APPSERVER_ROOT /zWebSphereOEM/V7R0/config1
IZU_SERVANT_USERID WSSRU1
IZU_CELL_SHORT_NAME BBNBASE
IZU_WBEM_ROOT /ict/wbem
IZU_CONTROL_USERID WSCRU1
IZU_DATA_FS_NAME IZU.SIZUDATA
IZU_SERVANT_USERID WSSRU1
IZU_CODE_ROOT /usr/lpp/zosmf/V1R11
IZU_WBEM_ROOT /usr/lpp/wbem
IZU_DATA_DIR /SY1/var/zosmf
IZU_DATA_FS_NAME IZU.SIZUDATA
IZU_CONFIG_DIR /etc/zosmf
IZU_CODE_ROOT /usr/lpp/zosmf/V1R11
IZU_CIM_GROUP_NAME CIMGP
IZU_DATA_DIR /var/zosmf
IZU_CIM_GROUP_ID 5321
IZU_CONFIG_DIR /etc/zosmf
IZU_CEA_UID 9002
IZU_CIM_GROUP_NAME CIMGP
IZU_CEA_GROUP_NAME CEAGP
IZU_CIM_GROUP_ID 5321
IZU_CEA_GROUP_ID 6321
IZU_CEA_UID 9002
IZU_CEA_PARM_NAME ZM
IZU_CEA_GROUP_NAME CEAGP
IZU_IEA_PARM_NAME ZM
IZU_CEA_GROUP_ID 6321
IZU_PARMLIB HDENNIS.ZOS17.PARMLIB
IZU_CEA_PARM_NAME 01
IZU_PARMLIB_SOURCE CEAID.PUIAM.JCL2
IZU_IEA_PARM_NAME ZM
IZU_INCIDENT_LOG Y
IZU_PARMLIB SYS1.PARMLIB
IZU_CIM_SETUP N
IZU_PARMLIB_SOURCE SYS1.PARMLIB
IZU_SYSNAME_PREFIX SY1
IZU_INCIDENT_LOG Y
IZU_DATA_FS_TYPE ZFS
IZU_CIM_SETUP N
IZU_COUNTRY_CODE 000
IZU_BRANCH_CODE 999
IZU_STORAGE_VALUE "VOLSER(PEVDM3)"

36 © 2009 IBM Corporation

The left represents the current default configuration file. It contains the properties and default
values provided for the configuration.

The right shows an example of a file that is created after completing Step 1.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 33 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Step 2: Configure security for the core functions
izusetup.sh –racfcore configfilename.cfg

Submitted from SUPERUSER ID

izuracfcore.sh

•Create rexx script containing RACF commands to:


izusetup.sh
•Create z/OSMF Administrator

•Connect / Permit z/OSMF Administrator to Core

configfilename.cfg

izuracfbase.template
../etc/zosmf/izuracfbase.rexx

37 © 2009 IBM Corporation

This step creates a rexx script which contains the RACF commands to configure security for the
core functions.

izuracfcore.sh is invoked with the configuration file. The values in the configuration file are
applied to template file, izuracfbase.template, to create a rexx script which contains the RACF
commands for the core functions.

The rexx script contains RACF commands used to create the z/OSMF administrator and to
connect/permit it to core functions.

The script is to be reviewed/modified and executed by the security administrator.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 34 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Step 3: Configure security for the Incident Log
izusetup.sh –racfincidentlog configfilename.cfg
Submitted from SUPERUSER ID

izuracfincidentlog.sh

•Create rexx script containing RACF commands to:

izusetup.sh •Create CIM and CEA groups

•Connect z/OSMF Administrator to CIM and CEA groups

•Connect / Permit z/OSMF Administrator to Incident Log

configfilename.cfg

izuracfincidentlog.template ../etc/zosmf/izuracfincidentlog.rexx

38 © 2009 IBM Corporation

This step creates a rexx script which contains the RACF commands to configure security for the
Incident Log.

izuracfincidentlog.sh is invoked with the configuration file. The values in the configuration file are
applied to template file, izuracfincidentlog.template, to create a rexx script which contains the
RACF commands for the Incident Log functions.

The rexx script contains RACF commands used to create CIM and CEA groups. The z/OSMF
administrator is connected/permitted to CIM and CEA groups required for Incident Log.

The script is to be reviewed/modified and executed by the security administrator. If another


security product is used instead, the commands can be substituted appropriately.

For cases where CIM is already configured, no CIM group is created. Instead the z/OSMF
administrator is permitted to the existing CIM RACF classes. More information on this subject is
provided later on.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 35 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z
IBM System z
IBM
z/OSMF Configuration with pre-existing CIM setup

ƒ If CIM server is already setup and operational, then it is assumed the


– CIM administrator has been created
– CIM RACF setup has been completed

ƒ In order for z/OSMF to also use the CIM server, the scripts will perform the
required steps as follows
– In step 1, create configuration, only needs to know the name of the existing CIM
administrator, and will bypass all other prompts relating to CIM.
– In Step 3, configuring security for the Incident Log, no CIM RACF setup will take
place. It is assumed that this has already been completed.
– Instead, the z/OSMF administrator will be permitted to the CIM/Incident Log RACF
classes.
– In Step 7, completing the setup for Incident Log, the scripts to handle the CIM
configuration will not be called. The CIM server is expected to be running for this
case. The configuration will verify that the CIM server is running and will only
perform the PARMLIB updates

37 © 2009 IBM Corporation

If the CIM environment has already been setup on the target system, the setup scripts will take it
into account. No special action has to be taken, other than provide the name of the currently
setup CIM administrator.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 36 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Step 4: Verify the RACF security setup
izusetup.sh –file configfilename.cfg –verify racf

Submitted from IBMUSER (SUPERUSER)

izuracfverify.sh
izusetup.sh •Verifies RACF configuration

izuracfverify.report
configfilename.cfg

39 © 2009 IBM Corporation

Verifies the RACF settings for z/OSMF. A report file (izuracfverify.report) is created. It contains
the sequence of RACF commands that were issued to validate the setup. If an error occurs the
error can be found within this file.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 37 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Step 5: Prime the z/OSMF data file system
izusetup.sh –file configfilename.cfg -prime
Submitted from SUPERUSER ID

izuprime.sh

•Primes the repository for z/OSMF


izusetup.sh
•Prime user repository

•Prime role repository

configfilename.cfg

40 © 2009 IBM Corporation

Primes the z/OSMF data file system with the user and role repository. This persistent data for
z/OSMF.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 38 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Step 6: Complete the setup for core functions
izusetup.sh –file configfilename.cfg -core
Submitted from z/OSMF Administrator ID

izuadmin.sh

•z/OSMF WAS administration


izusetup.sh
•Deploy z/OSMF

•Configure WAS OEM for z/OSMF

configfilename.cfg

41 © 2009 IBM Corporation

Performs the required WAS administration for z/OSMF. These are the tasks handled by this step:

Deploy the application ear to the application server.


# Create the application scope shared library.
# Create the global scope shared library.
# Add a reference to the application scope library
# from the application classloader.
# Add a reference to the global scope library
# from the application server global classloader.
# Updates the server region LIBPATH.
# Create an environment property in the application servers
# servant process for the IZU data directory.
# Set the required settings in the application server.
# The settings will be set as follows:
# . The application server is set to run in 64 bit mode.
# . Administrative security is enabled.
# . Application security is enabled.
# . Java 2 security is disabled.
# . Authenticate only when the URI is protected is enabled.
# . Use available authentication data when an unprotected
# URI is accessed is enabled.
# . Sync to OS Thread is enabled.
# . LTPA timeout set to the value specified in izuadmin.env.
# The default in izuadmin.env is 490 minutes.
# The izuadmin.env is obtained from /etc/zosmf/izuadmin.env
# if it exists or from the defaults directory in the IZU
# code directory if /etc/zosmf/izuadmin.env does not exist.
# . LTPA cache timeout set to the value specified in
# izuadmin.env.
# The default in izuadmin.env is 2940 seconds (490 minutes).
# . Session timeout set to the value specified in izuadmin.env.
# The default in izuadmin.env is 495 minutes.
# The value must be greater than the LTPA timeout.
# . Adds a log/trace specification to the server.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 39 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Step 7: Complete the setup for the Incident Log
izusetup.sh –file configfilename.cfg –application log

Submitted from z/OSMF Administrator ID

Configuring Incident Log


izucimconfig.sh

izusetup.sh •Setup .profile for z/OSMF Admin with CIM environment variables
•Validates the cimserver.env file matches the z/OSMF configuration
•Starts CIM server
•Run cimivp to validate CIM setup
•Verifies IVP providers are registered with CIM (if not it will register them)

configfilename.cfg izuincidentlogconfig.sh

•Create CEAPRMxx parmlib member


•Create IEADMCxx parmlib member
•Activate CEAPRMxx parmlib member

42 © 2009 IBM Corporation

Configuring CIM
• Verifies values in /etc/wbem/cimserver.env file matches the configuration
• Updates z/OSMF administrator’s .profile with CIM environment variables
• Starts the CIM server
• Validate CIM server setup
• Verifies IVP Providers are registered with CIM (if not registered, it will register them)

Configuring Incident Log


• Copies SYS1.SAMPLIB(IEADMCZM) into specified PARMLIB dataset.
• Suffix used for IEADMC is based on value in configuration file.
• Copies CEAPRM from source dataset into specified PARMLIB dataset.
• CEAPRM member is updated with data from configuration file:Branch, Country
Code, Storage
• Suffix used CEAPMRxx is based on value in configuration file.
• Calls IBMzOS_PDW_IVP (method SetCEAMember) to activate the CEA member on the
system.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 40 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Step 8: Verify the setup
izusetup.sh –file configfilename.cfg –verify all

Submitted from z/OSMF Administrator ID

izuadmin.sh
•Verifies WAS configuration for z/OSMF

izusetup.sh
izuincidentlogverify.sh
•Verifies CIM server is started
•Verifies IVP Providers are registered
•Creates test incident
•Calls IVP providers and collect data to create report file
configfilename.cfg

izuincidentlogreport.template ../etc/zosmf/izuincidentlogverify.report

43 © 2009 IBM Corporation

Verifies the configuration for both core and Incident Log functions.

The core verification validates the WAS configuration for z/OSMF.

The Incident Log verification validates Incident Log configuration for z/OSMF. This includes:
1) Verifying all the z/OS dependencies (CEA, Sysrexx, Logger, etc.)
2) Creating a test dump on the target system and running a series of Incident Log
operations against it to verify function.
3) Creating a test report which details the results of the verification

The core verification can be invoked independently with the following command:izusetup.sh –file
configfilename.cfg –verify core

The Inicdent Log verification can be invoked independently with the following command:
izusetup.sh –file configfilename.cfg –verify log

Expo © 2009 IBM Corporation October 2009


Session ZZS02 41 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


izuincidentlogverify.report
Incident Log Verification Report
------------------------------------------ SLIP OperLog time : 3600
Sysplex Dump Directory : SUCCESS SLIP LOGREC time : 3600
CEA : SUCCESS SLIP LOGRECSUMMARY time : 86400
System Rexx : SUCCESS DUMP OperLog time : 3600
DUMP LOGREC time : 3600
Diagnostic Information DUMP LOGRECSUMMARY time : 86400
------------------------------ ABEND OperLog time : 3600
SVCDump : SUCCESS ABEND LOGREC time : 3600
ABEND LOGRECSUMMARY time : 86400
Operations Log : SUCCESS
Error Log : SUCCESS
Incident Log Logstreams
Error Log Summary : SUCCESS
--------------------------------
Incident Log Operations System Logger : TRUE
------------------------------- OperLog set to Logstream : TRUE
Prepare Dump Request : SUCCESS Logrec set to Logstream : TRUE
Prepare Operations Log Request : SUCCESS Primary Logger CDS : "CIMPROV.LOGR001"
Prepare Error Log Request :SUCCESS Alternate Logger CDS : "CIMPROV.LOGR002"
Prepare Error Log Summary Request : SUCCESS Number of LSR for Primary CDS : 60
Set PMR Request : SUCCESS CEA OperLog Logstream : ""
Set Tracking Request : SUCCESS CEA Logrec Logstream : ""

CEA Parmlib Member Sysplex Dump Directory


----------------------------- --------------------------------
SnapShot : TRUE Name : "MVSSPT.SYSPLEX.DMPDIR"
Size : 112
Branch : 999
On shared volume : TRUE
Country : 000
Full : FALSE
Storage Value : PEVDM3
IPCS initialized : TRUE
HLQ : CEA

continue Æ

44 © 2009 IBM Corporation

An example of the Incident Log verification report.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 42 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z
IBM System z
IBM
Configuration Log Files
ƒ Format: script_$(date +"%m%d%y")_$(date +"%H%M%S").log

ƒ Configuration logs are written to $IZU_CONFIG_DIR ( by default: /etc/zosmf)

ƒ For most scripts, if $IZU_CONFIG_DIR is not available logs are written to


/tmp.

Message File

ƒ $IZU_CODE_ROOT/bin/IZUGDeploy.properties

ƒ z/OSMF configuration messages are IZUG100 to IZUG399

44 © 2009 IBM Corporation

Log files for z/OSMF configuration are given the following naming convention. The “script” prefix
identifies the name of the script that has been invoked. It is followed by a timestamp and ending
with a “log” extension.

For example, below are the logs for scripts izuadmin.sh and izuprime.sh respectively:
izuadmin_040309_153552.log
izuprime_052209_134047.log

The logs are written to $IZU_CONFIG_DIR (/etc/zosmf). If this directory does not exist the logs
are written to $TMPDIR. If $TMPDIR is not set then it is written to /tmp.

File IZUGDeploy.properties contain the z/OSMF configuration message definitions. This file is
located in $IZU_CODE_ROOT/bin.

The z/OSMF configuration messages are ranged from IZUG100I to IZUG379I.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 43 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z
IBM System z
IBM
Step 9: Verify the z/OSMF configuration
ƒ Start WAS OEM:
– START BBN7ACR,JOBNAME=BBNS001,ENV=BBNBASE,BBNNODE,BBNS001

ƒ Point your browser to: https://hostname:port/zosmf/

To log in you will need a z/OS userID defined and enabled for z/OSMF (and the
WebSphere runtime environment) - Guidance is provided.
45 © 2009 IBM Corporation

This is the final step to the z/OSMF configuration. Ensure CIM server is started (if previosuly set-
up)

This shows the Welcome page when user first accesses the URL and has not logged in yet

Once z/OSMF has been set up and configured and started on a z/OS system, a z/OS user can
access z/OSMF via a browser session. The URL is the host name, the port name and the context
route for z/OSMF. The user initially accesses z/OSMF as a ‘GUEST’ until they login. On the left
hand site is the navigation pane with the login at the top and the large center pane is where the
tasks will open up. At this point you can log in with a valid z/OS user ID that has been defined
and enabled for z/OSMF and the WebSphere OEM runtime environment.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 44 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Adding users to z/OSMF
ƒ Adds an existing user to z/OSMF

ƒ The z/OSMF administrator needs to add the user to z/OSMF via the Users
task

ƒ Two scripts are provided:


– izuaddloguser.sh: adds user to both Core and Incident Log
– izuaddcoreuser.sh: adds user to Core only

ƒ The configuration file name is required as input.


– If scripts are invoked without configuration file the caller will be prompted
for required values.

47 © 2009 IBM Corporation

After completing the configuration for z/OSMF two scripts are provided to allow existing users to
be added to z/OSMF.

The scripts can be invoked with the configuration file used for the z/OSMF configuration or (if
omitted) prompts will be displayed for the properties required to add the users.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 45 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


izuaddloguser.sh –file configfilename.cfg –username zmausr1

izuaddloguser.sh
configfilename.cfg
•Create rexx script containing RACF commands to:

•Add existing user to Incident Log and Core

If no cfg file will prompt for:


1) z/OSMF Admin ID
2) CIM Admin ID
3) CEA group
4) AppServer Servant User ID
5) SAF Profile Prefix
izuaddloguser.template ../etc/zosmf/izuaddloguser_zmausr1.rexx

48 © 2009 IBM Corporation

Adding a user to the Incident Log functions can be done using the izuaddloguser.sh script. Using
a template file, values are applied to the template file to create a RACF rexx script containing the
RACF commands to add the specified user to the Incident Log and core functions. In this
example, the output rexx script will be named izuaddloguser_zmausr1.rexx.

This script can be passed in the configuration file used for the z/OSMF configuration. Or, if the
file is omitted, the caller will be prompted for the values required.

The required values are:


• z/OSMF Admin ID
• CIM Admin ID
• CEA group
• AppServer Servant User ID
• SAF Profile Prefix

Expo © 2009 IBM Corporation October 2009


Session ZZS02 46 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


izuaddcoreuser.sh –file configfilename.cfg –username zmausr1

izuaddcoreuser.sh

configfilename.cfg •Create rexx script containing RACF commands to:

•Add existing user to Core

If no cfg file will prompt for:


1) AppServer Servant User ID
2) SAF Profile Prefix

izuaddcoreuser.template
../etc/zosmf/izuaddcoreuser_zmausr1.rexx

49 © 2009 IBM Corporation

Adding a user to the core functions can be done using the izuaddcoreuser.sh script. Using a
template file, values are applied to the template file to create a RACF rexx script containing the
RACF commands to add the specified user to the core functions. In this example, the output rexx
script will be named izuaddcoreuser_zmausr1.rexx.

This script can be passed in the configuration file used for the z/OSMF configuration. Or, if the
file is omitted, the caller will be prompted for the values required.

The required values are:


• AppServer Servant User ID
• SAF Profile Prefix

Expo © 2009 IBM Corporation October 2009


Session ZZS02 47 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Client side environment checking tool

Browser links to z/OS


Management Facility checks
the browser settings

51 © 2009 IBM Corporation

Separate URL to access the tool (documented in the User’s Guide). Checker collects the client
setup data and indicates any issues for the specific browser being used.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 48 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z
IBM System z
IBM
Additional Information
Program Directory for z/OS Management Facility GI11-2886-00

IBM z/OS Management Facility License Information GC52-1263-00

IBM z/OS Management Facility User's Guide SA38-0652-01


APAR PK93289 and PTF UK50610 reflect this level
IBM WebSphere® Application Server OEM Edition GA32-0631-00
for z/OS Configuration Guide, Version 7.0

IBM WebSphere Application Server OEM Edition for z/OS V7.0 PDF – Web
Quickstart Guide download

z/OS Hot Topics, Issue 21: Simplify PDF – Web


download

z/OS Management Facility Web Page


http://www.ibm.com/systems/z/os/zos/zosmf/

IBM z/OS Management Facility education modules in IBM Education


Assistant
50 © 2009 IBM Corporation

Program Directory: This Program Directory is intended for the system programmer responsible
for program installation and maintenance. It contains information concerning the material and
procedures associated with the installation of IBM z/OS Management Facility. This publication
refers to IBM z/OS Management Facility as z/OS Management Facility. This includes IBM
WebSphere Application Server OEM Edition for z/OS, which will be referred to as WebSphere
Application Server OEM Edition for z/OS.

IBM z/OS Management Facility V1R11.0 User's Guide: This document provides information to
help you set up, configure, and use IBM® z/OS® Management Facility (z/OSMF). This document
also provides information for troubleshooting problems related to the use of z/OSMF.

IBM WebSphere Application Server OEM Edition for z/OS Configuration Guide: Describes
the prerequisite steps for configuring the application server runtime environment for z/OSMF. This
work must be completed before using the procedures described in the IBM z/OS Management
Facility User's Guide.

IBM WebSphere Application Server OEM Edition for z/OS V7.0 Quickstart Guide: This
document is intended for users of the IBM® WebSphere® Application Server OEM Edition for
z/OS® product. It should be used in conjunction with the IBM WebSphere Application Server
OEM Edition for z/OS Configuration Guide, GA32-0631, and the documentation provided with the
z/OS system application for deploying on a IBM WebSphere Application Server OEM Edition for
z/OS server instance. This document provides:
• A high-level description of the IBM WebSphere Application Server OEM Edition for z/OS
product
• Two quickstart procedures providing guidance through the IBM WebSphere Applicatio
Server OEM Edition for z/OS configuration and server instance creation processes.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 49 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

• An appendix containing three worksheets to help you plan for the IBM WebSphere
Application Server OEM Edition for z/OS configuration and server instance creation
processes.

There are also articles about the z/OS Management Facility in z/OS Hot Topics, Issue 21:
• z/OS Simplifies Your Life — An introduction to z/OSMF
• What's in your (incident) log? An introduction to the z/OSMF Incident Log
• Setting up Operlog and Logrec for z/OSMF Incident Log
• Removing the Mystery on using System Logger for z/OSMF

IBM

IBM z/OS Management Facility V1.11


Washington Systems Center User Experience

Slides prepared by Bette A Brody


© Copyright IBM Corporation 2008
© 2009 IBM Corporation

Expo © 2009 IBM Corporation October 2009


Session ZZS02 50 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


WSC User Experience - Background
ƒ Participated in Beta and ESP
– z/OS R10 for Beta
• Limited functionality
• We took all defaults
• Testing found some problems and dislikes
• Results:
• Documentation improvements and requirements submitted
• Initial problems were fixed prior to ESP

– z/OS R11 for ESP


• Overrode defaults for some values in the configuration file
• Results:
• Improved documentation
• Problems resolved by General Availability
• Functions working as designed

ƒ Focus for this presentation is ESP level

ƒ 4-way Parallel Sysplex


– z9 and z10

ƒ Very current on PTF service


54 © 2009 IBM Corporation

IBM System z IBM


Planning
ƒ Extremely important to READ the documentation prior to running any
scripts/jobs for WAS OEM and z/OSMF
– z/OSMF User’s Guide: use -01 level
– Ensure APAR PK93289 (PTF UK50610) is installed

ƒ Use the WAS OEM Quickstart Guide when configuring WASOEM


– WAS OEM can coexist in the same environment as full function WebSphere

ƒ If required functions are already set-up (example: DAE, System Logger, etc)
verify PARMLIB members all have the correct parameters set as required for
z/OSMF

ƒ IBM WebSphere® Application Server OEM Edition for z/OS Version 7.0 must be
configured prior to starting z/OSMF configuration.
– There are several z/OS requirements to be met

55 © 2009 IBM Corporation

Expo © 2009 IBM Corporation October 2009


Session ZZS02 51 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


WAS OEM
ƒ We installed several times (different users wanted the experience)
ƒ We used the Quickstart Guide for the second install (37 pages)
– Excellent document
– Contains z/OS system preparation checklist
• Used to verify setup tasks for z/OS are completed
– Contains WASOEM.sh shell script prompt response worksheet
• Used to plan your responses during the configuration process
• Identifies description, prompt from script and default values
• may override default values
– Contains Post-installation task checklist
– Know what DASD volumes you want to use
• WebSphere Application server
• File system (zFS or HFS) < WSC used zFS>
• Configuration file
– Provides an advanced quickstart procedure for those who have a deep
understanding of WebSphere Application server for z/OS

56 © 2009 IBM Corporation

IBM System z IBM


WAS OEM Configuration steps
ƒ We did fill out the worksheets ahead of time
ƒ Caution: If overriding defaults do not make any typing errors
1. Configuration steps:
– Initial invocation: run WASOEM.sh –config
– Creates folder & files in /etc/zWebSphereOEM/V7R0/conf/
– Edit Response file and re-issue WASOEM.sh:
WASOEM.sh –config –responsefile <path>/CONFIGxx.RespFile
2. Security Set-up step: run 3 Jobs
3. Server Creation step: WASOEM.sh –create CONFIGxx
– Uses User prompts & following response file:
/etc/zWebSphereOEM/V7R0/conf/CONFIGxx/zpmt/responseFile.txt
– Should create Intermediate symbolic link to WAS OEM Product zFS was_smpe -
>/usr/lpp/zWebSphereOEM/V7R0/???
– Creates Cell run-time Configuration ZFS
(default = BBN.V7R0.CONFIG1.ZFS at /zWebSphereOEM/V7R0/config1
– Log files in /var/zWebSphereOEM/V7R0/logs/

57 © 2009 IBM Corporation

Expo © 2009 IBM Corporation October 2009


Session ZZS02 52 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


WSC Sample xxx.cfg file for WASOEM.sh
# Status = HSMA110
IZU_ADMIN_NAME ZOSMFAD
IZU_ADMIN_PROC IKJACCNT
IZU_ADMIN_ACCOUNT D999
IZU_ADMIN_REGION 2096128
IZU_ADMIN_UID 19
IZU_ADMIN_GROUP SYS1
IZU_ADMIN_HOME /u/zosmfad
IZU_ADMIN_PROGRAM /bin/sh
IZU_WAS_PROFILE_PREFIX Z7BASEB
IZU_CLUSTER_TRANSITION_NAME Z7SR01
IZU_APPSERVER_GROUP Z7CFG
IZU_APPSERVER_ROOT /zWebSphereOEM/z7baseb/z7nodeb
IZU_CELL_SHORT_NAME z7baseb
IZU_CONTROL_USERID Z7ACRU
IZU_SERVANT_USERID Z7ASRU
IZU_WBEM_ROOT /usr/lpp/wbem
IZU_DATA_FS_NAME ZMFUSS.SIZDATB.ZFS
IZU_CODE_ROOT /usr/lpp/zosmf/V1R11
IZU_DATA_DIR /var/zosmf
IZU_CONFIG_DIR /etc/zosmf
IZU_CIM_GROUP_NAME CIMGP
IZU_CIM_GROUP_ID 11
IZU_CEA_UID 20
IZU_CEA_GROUP_NAME CEAGP
IZU_CEA_GROUP_ID 12
IZU_CEA_PARM_NAME 01
IZU_IEA_PARM_NAME ZM
IZU_PARMLIB SYS1.PARMLIB
IZU_PARMLIB_SOURCE SYS1.PARMLIB
IZU_INCIDENT_LOG Y
IZU_CIM_SETUP Y
IZU_SYSNAME_PREFIX SYSB
IZU_DATA_FS_TYPE ZFS
IZU_COUNTRY_CODE 000
IZU_BRANCH_CODE 487
IZU_STORAGE_VALUE "VOLSER(ZOSDM1,ZOSDM2,ZOSDM3,ZOSDM4)"
IZU_CIM_ADMIN_NAME ZOSMFAD
58 © 2009 IBM Corporation

IBM System z IBM


Validating WAS OEM
ƒ Start the WASOEM server
Z7ACRB,JOBNAME=Z7SR01B,ENV=Z7BASEB.Z7NODEB.Z7SR01B
– You will need to substitute your server name

ƒ From a Web Browser, log into the Integrated Solutions Console (ISC):
(Administrative console)
https://host_name:admin_secure_port/ibm/console
– Take note this is a secure http

ƒ Take a back-up of the HFS/zFS filesystem


– DFDSS

ƒ Shutdown the WASOEM Server


– Needs to be shutdown before configuring z/OSMF

59 © 2009 IBM Corporation

Expo © 2009 IBM Corporation October 2009


Session ZZS02 53 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Configuring z/OSMF – getting started
ƒ Review z/OS Set-up actions for Incident Log task
– Table 1in the z/OSMF User’s Guide – Chapter 2
> OPERLOG > CEA
> LOGREC Log stream > System REXX
> Automatic dump allocation > RRS
> DAE > Sysplex dump directory

ƒ Use the Planning worksheets for core functions and incident log
– Tables 2 & 3 in the z/OSMF User’s Guide – Chapter 2
• Provides task, description and default value
• Column for your value >>> write it down

ƒ Most tasks require superuser authority


– Table 4 in the z/OSMF User’s Guide – Chapter 3 identifies which steps require
superuser authority

60 © 2009 IBM Corporation

IBM System z IBM


Configuring z/OSMF - Steps 1–7
1. Create Initial config: izusetup –config (Several User Prompts)
• Creates xxx.cfg Configuration File in /etc/zosmf/xxx.cfg file.
2. Configure Security for Core: izusetup –racfcore /etc/zosmf/xxx.cfg
• Creates RACF commands in /etc/zosmf/izuracfbase.rexx - Run it
• In the -1 level of z/OSMF User’s Guide this is a separate step
3. Configure security for Incident Log: izusetup –racfincident xxx.cfg
• Creates RACF commands in /etc/zosmf/izuracfincidentlog.rexx - Run it
• In the -1 level of z/OSMF User’s Guide this is a separate step
• (Re-) Start CIM Server (MVS command) : /S CFZCIM
4. Verify RACF security setup: izusetup –file /etc/zosmf/xxx.cfg –verify racf
• Creates izuracfverify.report - Review it
5. Prime z/OSMF data file system: izusetup –file /etc/zosmf/xxx.cfg –prime
• Creates Registry & Data directory for z/OSMF in /var/zosmf/
Switch to zosmf administrator’s ID (above scripts run as SuperUser.)
6. Complete setup core functions: izusetup –file /etc/zosmf/xxx.cfg –core
• Deploys Core functions & Registers z/OSMF with WAS OEM & Updates config.
7. Complete Incident Log: izusetup –file /etc/zosmf/xxx.cfg –application log
• Also updates CIM server and CEA server members in PARMLIB.
61 © 2009 IBM Corporation

Expo © 2009 IBM Corporation October 2009


Session ZZS02 54 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z
IBM System z
IBM
Validating your z/OSMF server
ƒ Start the WAS OEM server:
S Z7ACRB,JOBNAME=Z7SR01B,ENV=Z7BASEB.Z7NODEB.Z7SR01B

ƒ Start the CIM Server:


S CFZCIM

ƒ From a Web Browser, log into z/OSMF:


https://host:port /zosmf
first time login using the z/OSMF Administrator userid. Default is
ZOSMFAD

ƒ Environment Checker:
https://host:port/zosmf/IzuUICommon/environment.jsp

60 © 2009 IBM Corporation

IBM System z IBM


Using z/OSMF
Login to https://host:port /zosmf

63 © 2009 IBM Corporation

Expo © 2009 IBM Corporation October 2009


Session ZZS02 55 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


z/OSMF Environment Checker
https://host:port/zosmf/IzuUICommon/environment.jsp

64 © 2009 IBM Corporation

IBM System z IBM


Adding z/OSMF Users
ƒ First, add users with izuaddcoreuser.sh and izuaddloguser.sh
scripts and rexx EXECs which added users & EJBROLE profiles
ƒ Then go to z/OSMF Admin >> Users >> Actions >> New… and specify
UserID, Name and specify “z/OSMF AdministratorUser” or “z/OSMF User”

65 © 2009 IBM Corporation

Expo © 2009 IBM Corporation October 2009


Session ZZS02 56 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


z/OSMF Incident Log
ƒ Use Filters to select by date, System, Problem #, etc.

Actions:
ƒ Setting the tracking ID
ƒ Setting the problem number
ƒ Deleting incidents
ƒ Sending all of the diagnostic data
ƒ Viewing diagnostic details
ƒ Displaying the status of all of the FTP jobs
ƒ Allowing the next dump **
ƒ Displaying the FTP Destinations panel
ƒ Displaying the FTP Profiles panel

66 © 2009 IBM Corporation

IBM System z IBM


z/OSMF Configuration Assistant
(First, transfer existing backing store files?)

67 © 2009 IBM Corporation

Expo © 2009 IBM Corporation October 2009


Session ZZS02 57 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Trouble-Shooting
ƒ WAS OEM Logs
– JES Spool (SYSPRINT, SYSOUT)

ƒ Tracing (MVS modify command – dynamic)


– F <server_name>,tracejava='com.ibm.zosmf.*=all=enabled‘

ƒ Stop Tracing (MVS modify command – dynamic)


– F <server_name>,traceinit

ƒ z/OSMF Logs – see JES logs (SYSPRINT)

ƒ Wsadmin logs (from izusetup.sh)


– wsadmin.traceout file in <profile_root>/logs

ƒ z/OSMF Help

68 © 2009 IBM Corporation

IBM System z
IBM System z
IBM
Summary
¾ IBM z/OS Management Facility (z/OSMF) V1R11 is a new product for z/OS
customers

¾ z/OSMF will make the day to day operations and administration of the
mainframe z/OS systems easier to manage for both new and experienced
system programmers

¾ z/OSMF delivers solutions in a task oriented, Web browser based user


interface

¾ The initial functions in z/OSMF 1.11 include z/OSMF Administration,


Incident Log, Configuration Assistant for z/OS Communication Server
and Links

¾ More to come…..

67 © 2009 IBM Corporation

In Summary, z/OSMF is a new product for z/OS customers that will make the day to day management of
z/OS system easier for both new and experience system programmers. It is task oriented, browser based
solution. The initial functions are problem data management and TCP/IP policy management.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 58 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM

Backup Foils

69 © 2009 IBM Corporation

IBM System z IBM


z/OSMF Problem Determination
ƒ Pain Points
– Need to troubleshoot a live system, recover from an apparent failure.
– Need to reduce risk to the business, reduce risk of re-occurrence.
– Complexity of performing the task (number of steps, jargon).
– Data collection very time-consuming
– Significant skill level needed to analyze problems, interact with IBM and
ISVs to obtain additional diagnostic info (setting SLIP traps, traces, etc.)
ƒ Initial focus on Problem Determination capability - Incident Log :
– Troubleshoot your system easier, faster
– The incident log and underlying z/OS diagnostic data gathering greatly
improves the tasks related to:
• Identifying system-detected problems (those related to SVC dumps
taken by the system)
• Collecting diagnostic materials related to a problem and sending
materials to IBM or another company's support area
• Telling the system to take the next dump for a previously-recognized
70 problem © 2009 IBM Corporation

Focusing on Problem Determination, System programmers often spend a lot of time collecting
and managing the right information and documentation, When a problem is encountered on a

Expo © 2009 IBM Corporation October 2009


Session ZZS02 59 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

z/OS system today, the system programmer has to take many manual and time consuming steps
to collect diagnostic data like dumps and appropriate excerpts from logs and then send those
materials elsewhere, such as to IBM or ISV support, via FTP. Getting a consolidated list of the
abend related problems across a sysplex, that the system programmer can work with, is also a
challenging task right now.
The incident Log task delivers on improving first failure data capture and problem data
management. When an abend dump and user initiated SVC dump is taken, the system also
collects and creates snapshots of additional data from the system and ties them all together into
what we call incidents. DAE interface is also simplified, so that you can enable the next dump for
specific incident string.

The new problem management task in the z/OS Management Facility provides simple interfaces
to get a consolidated list of problems in the sysplex, related to SVC dumps, the properties and the
diagnostic data captured and saved with each SVC dump. It also provides easy to use interface
to facilitate sending the diagnostic data for further diagnosis. This will require less time and skills
to manage the problems and diagnostic data in a sysplex.

IBM System z IBM


z/OSMF Problem Determination – Incident log
Benefits
Without z/OSMF** With z/OSMF**
Recognizing a system- Requires 5 to 7 manual steps, plus skill on effective use of IPCS to Display in 1 click. Greatly reduced skill required
detected (dumped) problem extract data from each of the dumps. As little as 5 seconds
occurred Up to 5-6 minutes

Collecting and sending Requires 7 to 15 manual steps, plus skill to locate the right log files, build Send the material in 8 clicks:
diagnostic data and run JCL jobs, rename the output datasets, and use an ftp job to send ƒSelect the incident materials
the different data sets to the target destination. ƒSpecify the FTP destination information
ƒIndicate send the material
Up to 20 minutes
Up to 30 minutes for sysplex components ƒCheck whether the information was FTP’d successfully
As little as 30 seconds

Allow new dump to be taken Requires 7 to 12 manual steps, plus skill on effective use of IPCS to Make the update happen in 3 mouse clicks
for the same symptom locate the dump data set, obtain the symptom string, get into the IPCS
DAE display, locate the matching symptom string (could be non-trivial)
and indicate TakeNext on the IPCS display As little as 10 seconds
Up to 15 minutes

** Based on IBM laboratory results, your results may vary


73 © 2009 IBM Corporation

Here are examples of z/OS Management Facility ease of use. Many of the time taking and
complex tasks are simplified so they can be accomplished in less time with just a few clicks and
also require less system knowledge.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 60 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Setting up System Logger log streams
1. Define and start OPERLOG in a system logger log stream.
Define a coupling facility (CF) structure
Activate the operations log (OPERLOG) through the VARY HARDCPY
command.
2. Define and start the LOGREC data set in a system logger log stream.
Define a CF structure
Activate it through the SETLOGRC command.
3. Create log streams for CEA.
Create OPERLOG and LOGREC model log streams for the common event
adaptor (CEA) component.
4. Define a couple data set for system logger.
Define a couple data set for the system logger component (or update your
existing LOGR data set) with a large enough log stream records (LSR) value
to allow sufficient space for managing the DASDONLY log streams that will be
created for capturing diagnostic log snapshots.

71 © 2009 IBM Corporation

Expo © 2009 IBM Corporation October 2009


Session ZZS02 61 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Other z/OS setup
1. Start auto-dump.
Start automatic SVC dump data set allocation (auto-dump).
2. Start DAE.
– Start dump analysis and elimination (DAE) to ensure that duplicate SVC dump are
suppressed.
– Ensure PARMLIB member is set properly – must have sysplex wide scope (starting
and stopping)
3. Ensure SYSREXX and CEA are active.
Verify that the System REXX (SYSREXX) and CEA components are active. To
do so, verify that the AXR and CEA address spaces are active.
4. Ensure SYS1.MIGLIB is APF-authorized.
The SYS1.MIGLIB data set requires APF authorization to allow AMATERSE to
be called by SYSREXX execs, which are authorized.

72 © 2009 IBM Corporation

Expo © 2009 IBM Corporation October 2009


Session ZZS02 62 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z IBM


Setting up Sysplex Dump Directory
ƒ If Sysplex dump directory is not setup, follow the steps below to Allocate and
activate Sysplex Dump Directory (SYS1.DDIR) on user specified volume.
– This value is stored in the BLSCUSER member in PARMLIB

ƒ Syntax: izusetupsddir.sh –volume VOLUME –cim /usr/lpp/wbem


• CIM server must be configured and running
• It uses the Incident Log IVP CIM Providers to activate the Sysplex Dump Directory.
• The volume specified must be allocated prior to calling the script.
• On the –cim argument, must specify the path to IZU_WBEM_ROOT
• Export IZU_WBEM_ROOT
– Calls izusetupsddir.rexx:
• Calls BLSCDDIR to format a Sysplex Dump Directory (SYS1.DDIR) on volume ZOSMF.

– Calls IBMzOS_SysplexDumpDirectory Provider (ActivateSDDIR) to activate the


SDDIR
• S BLSJPRMI
• C DUMPSERV
ƒ The recommended data set size is 60 cylinders, enough to hold approx 15,000 directory
records.

74 © 2009 IBM Corporation

Incident Log requires multiple z/OS dependencies to be setup prior to the z/OSMF configuration.
One of these dependencies is the Sysplex Dump Directory. A script is provided to help in
formatting and setting up a Sysplex Dump Directory.

The name of the Sysplex Dump Directory is SYS1.DDIR. This value is stored in the BLSCUSER
member in PARMLIB.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 63 Orlando
z/OS System Management Facility (ZOSMF) & WSC User Experience

IBM System z
IBM System z
IBM
Installation
ƒ Setting up additional instance for z/OSMF
– Install and setup WAS OEM. Note each WAS setup needs unique values
(i.e. server, cell, etc)
– Collect all the inputs as described in Planning section of z/OSMF User’s
Guide (At completion of ServerPac there is a config file, izudflt-
serverpac.cfg, with most inputs that can be read in also)
– Invoke setup scripts to configure and setup z/OSMF

Note: z/OSMF is designed to be installed using the scripts provided.

74 © 2009 IBM Corporation

There is additional information provided on how you would set up additional instances of z/OSMF
for backup. Right now z/OSMF does not have hot backup or hot failover at this point . You will
have to ensure there is another z/OSMF instance set up that is configured appropriately but not
started at the same time ... but can be started later as part of the same repository, so you don’t
have to go through and define it all over again.

You might also want to set up another instance for a test system. Not only do we provide scripts
to do the set up, the setup is broken into 3-4 pieces for flexibility. You can set up the z/OSMF
main application, there is separate script to set up the incident log, the security for each task is
also broken into a separate script so you can review first – because the sysprog setting up
z/OSMF is usually not the one set up for security.

Expo © 2009 IBM Corporation October 2009


Session ZZS02 64 Orlando