Modernizing your z/OS system administration with z/OS Management Facility

IBM z/OS Management Facility (z/OS MF) enables you to manage z/OS systems through a web browser interface. This article describes z/OS MF, and shows you how to install, configure, customize, and use it to streamline and simplify your day-to-day z/OS administrative tasks.

Ye Tian (tianybj@cn.ibm.com), Staff Software Engineer, IBM Enterprise Systems and Technology Development team, IBM

Photo of Ye TianYe Tian is aStaff Software Engineer, IBM Enterprise Systems and Technology Development team n Beijing. You can contact Ye at tianybj@cn.ibm.com.



Dan TY Zhang (zhdzhang@cn.ibm.com), Software Engineer, IBM Enterprise Systems and Technology Development team, IBM

Photo of Dan TY ZhangDan TY Zhang is a Software Engineer with the IBM Enterprise Systems and Technology Development team in Beijing. She has one year of experience with the IBM z/OS Management Facility. You can contact Dan at zhdzhang@cn.ibm.com.



07 November 2012

Introduction

IBM® z/OS® Management Facility (z/OS MF) provides a framework for managing z/OS systems across your enterprise through a web browser interface. It helps systems programmers manage and administer mainframe systems more quickly and easily from any location with Internet access. It is especially helpful for young z/OS systems programmers who do not have years of experience with z/OS. In its latest V1R13 release, z/OS MF gives you a single point of control for:

  • Viewing, defining, and updating policies that affect z/OS system behavior
  • Monitoring the performance of z/OS systems across your enterprise
  • Managing z/OS software
  • Performing z/OS data management tasks and troubleshooting data management problems
  • Consolidating your z/OS management tools
Figure 1. Browser-based z/OS MF console
Browser-based z/OS MF console

To start z/OS MF, log in with an authorized user ID. A navigation tree will be displayed on the left of the z/OS MF console, as shown in Figure 2, where you can perform the various z/OS MF tasks.

Figure 2. z/OS MF tasks
z/OS MF tasks

z/OS MF is built on WebSphere Application Server OEM Edition for z/OS (hereafter called WAS OEM). WAS OEM is fenced off from standard Websphere Application Server and only has limited functions, and it is shipped within the z/OS MF product package. Only applications registered for WAS OEM can use its functions, and customers cannot use their normal Websphere Application Server applications with WAS OEM. So far, IBM has offered z/OS MF as a no-charge product.

The information in this article is based on z/OS MF V1R13. There may be some differences in z/OS MF V1R11 and V1R12.

z/OS MF extensible system architecture

z/OSMF complies with industry standards, as shown in Figure 3, and its web interface, Dojo framework, and use of Java provide a high degree of extensibility and customization.

Figure 3. z/OS MF architecture
z/OS MF architecture

z/OS MF divides its components into functional units that you can install and use individually. Each functional unit is a plug-in except for the core functions, which provide the underlying infrastructure and basic services for the plug-ins, such as the web navigation tree, and the access control for performing specific tasks.

Table 1. z/OS MF functions
NumberFMIDFunction description
1HSMA130Core functions
2HSMA131Web ISPF
3HSMA132Resource Monitoring (RM)
4HSMA133Workload Management (WLM)
5HSMA134Software Management (SM)
6HSMA135Incident Log (IL)
7HSMA136Capacity Provisioning (CP)
8HSMA13AConfiguration Assistant (CA)

Every product or subsystem can develop their own providers based on the open-source Common Information Model (CIM) interface to provide information to the end user. CIM is considered the common interface to gather performance and configuration data. z/OS MF can gather data not only from z/OS but also from other platforms such as AIX®, Linux®, and Unix®, as long as CIM is configured properly.

Because z/OS MF uses the Security Access Facility (SAF) interface for access control, you can use IBM Resource Access Control Facility (RACF) or a third-party security product. z/OS MF can manage access control by itself when used in Repository mode, but it is recommended to use SAF mode to manage security because of the increased granularity and expandability. z/OS MF provides other functions such as Submit API and application linking, and will use its flexible and extensible architecture to deliver additional functions in future releases.

z/OS MF installation and configuration

  1. Ensure that the z/OS MF product package is installed on z/OS with SMP/E. Follow and complete the instructions in the installation guide delivered with z/OS MF.
  2. Configure the application server that z/OS MF is running on.
  3. Configure z/OS MF and deploy it into WAS OEM.
  4. Complete the security setup during the configuration of WAS OEM and z/OS MF.
  5. In addition to Steps 1-4, many z/OS system prerequisites should be configured to enable the plug-ins to work, depending on which plug-ins you are setting up. Your Security Administrator and Network Administrator may need to assist with this step.

This article describes the high-level steps for configuring z/OS MF and WAS OEM. For detailed configuration steps, see:

WAS OEM customization

WAS OEM edition provides a script that you can use to customize and set up a WAS OEM instance. Before starting the set up, go to the samples directory under the WAS OEM root path and copy the files wasOEM_env.sh and wasOEMDefault.responseFile to your configuration directory (usually the /etc directory). Review the ENV variables in the script, and modify as shown below:

  • The configuration root directory, which will contain all of the configuration files that you create
  • The configuration name, which the last step uses to create a WAS OEM instance
  • The log directory, which is used to generate the log message when configuring WAS OEM

Then complete the following steps to create a WAS OEM instance. There are two configuration modes -- a Typical mode, and an Advanced mode, which provides more help prompts during customization.

  1. Run the script and answer the help prompts to customize and create the configuration file:
    /usr/lpp/zWebSphereOEM/V7R0/bin/WASOEM.sh -config -responsefile 
    /etc/zWebSphereOEM/V7R0/conf/CONFIG1/responseFile.txt
  2. Review the JCL generated by Step 1 and set up the necessary z/OS system prerequisites, such as logstream, security, and TCP/IP.
  3. Create a WAS OEM instance with the correct configuration name:
    /usr/lpp/zWebSphereOEM/V7R0/bin/WASOEM.sh -create CONFIG1

z/OS MF and WAS OEM security

Running the scripts provided by WAS OEM and z/OS MF generates a set of jobs and scripts that include general commands to set up security. Review and modify these commands according to your specific requirements.

For WAS OEM, run the three jobs generated in the dataset indicated in the RESPOSE file, which is customized when configuring WAS OEM. Ensure that you have SPECIAL role and superuser authority to run these jobs. WAS OEM runs under z/OS Unix Services (OMVS), so there are more complex security steps for OMVS and WAS OEM if you are planning to use the advanced functions. For more information, see the Please refer to WebSphere Application Server information center and the z/OS RACF Security Administrator's Guide.

For z/OS MF, you can use two security modes to manage security. Repository Mode uses a persistence file to store the security setup, which is managed by z/OS MF core, while SAF Mode uses a third party such as RACF to manage security. As with WAS OEM, the configuration of z/OS MF generates a REXX script, which you submit to set up security for z/OS MF. However, on some occasions, you need to review and modify the script according to your requirements, as described below.

It is recommended to use SAF Mode in order to take advantage of RACF. Even if you plan to use Repository Mode, z/OS MF still needs SAF to manage other related profiles for non-z/OS MF classes. A property in the z/OS MF .cfg file indicates the security mode. You may need to convert between the Repository and SAF Modes. The z/OS MF configuration steps will detect and convert the current mode to the mode specified in the .cfg file. A property file (in z/OS MF V1R13 or later) created under the WAS OEM runtime directory is used to specify the current mode and other runtime information.

z/OS MF installation, verification, and execution

z/OS MF inherits the styles of WAS OEM, and provides a set of shell scripts to simplify the setup and provide helpful prompts. You need to complete four major steps in an OMVS or Rlogin session. Izusetup.sh is the script used for configuration. Ensure that the relevant environment variables have been set up properly before running this script. You can use the sample script below in Listing 1 to customize the environment variables -- otherwise they will be set to default values. You can check the current assigned values in the log files of each izusetup step, as shown below in Listing 2.

Listing 1. Default izu_env.sh
#!/bin/sh
# Default value for the configuration directory
export IZU_CONFIG_DIR=/etc/zosmf
#
# Default value for the logfile directory
export IZU_LOGFILE_DIR=/var/zosmf/configuration/logs
#
# Default value for the product binaries
export IZU_CODE_ROOT=/usr/lpp/zosmf/V1R13
# 
# Setup PATH so the zOS FMF binaries are accessible.
export PATH=.:/usr/lpp/zosmf/V1R13/bin:$PATH
#
# For problems with out of memory starting jvms 
export _BPX_SHAREAS=NO

Step 1. Customize and create a new z/OSMF.cfg file

  1. Command: ./izusetup.sh -file /u/in/R13SRV.cfg -config -fastpath
  2. Input: Sample .cfg file
  3. Output: Customized .cfg file and the generated script file of RACF commands
  4. Authority: Superuser

Step 2. Run the generated RACF commands file to define the z/OS MF related profiles and authorities

  1. Command: go to $IZU_CONFIG_DIR to run the script
  2. Input: None
  3. Output: Profiles are defined to RACF database
  4. Authority: Security administrator with SPECIAL role

Step 3. Prepare the persistence file

The persistence file IZU_DATA_FS_NAME is specified in the .cfg file. It is used by z/OS MF instances to store application data at runtime. The script detects whether the file system is already created and mounted. If it is not, it automatically does all the work according to the properties specified in the .cfg file.

  1. Command: ./izusetup.sh -file /u/in/R13SRV.cfg -prime
  2. Input: New customized .cfg file
  3. Output: Persistence file is primed and formatted, and PARMLIB is updated
  4. Authority: Superuser

Step 4. Deploy and verify z/OS MF.

  1. Command: ./izusetup.sh -file /u/in/R13SRV.cfg -finish
  2. Input: New customized .cfg file
  3. Output: z/OS MF is deployed into WAS OEM
  4. Authority: z/OS MF administrator

z/OS MF configuration log

The option -config'|'-prime'|'-finish represents each individual step to configure a new z/OS MF instance. The option -file specifies the location of the configuration file, and the file name must be prefixed with the full path, The -fastpath option means the you accept all of the values in the .cfg file. To input the new values interactively, run the command without the -fastpath option.

Listing 2 shows a log of the -config step. You should understand each property in the .cfg file in order to customize a z/OS MF instance. The log messages is displayed on the terminal and saved to the directory $IZU_LOGFILE_DIRl. To address several key concerns when setting up the properties, refer to Listing 2 and see if you can answer the following questions:

  1. What kind of persistence file system is being created?
  2. What is the z/OS MF Admin and groups?
  3. What is the setting of WebSphere Application Server?
  4. Where is the RESPONSE file?
  5. Which plug-ins are being configured?
  6. What is the CEA PARMLIB setting?
  7. What WLM, CIM, and Capacity Provisioning RACF groups will z/OS MF users be connected to?
Listing 2. Log of z/OS MF -Config step
IZUG215I: Starting z/OS MF "setup" procedure.
Fri Jun 8 02:50:10 EDT 2012
Version: 1.159.1.9
Delta Date: 5/17/12
Delta Time: 21:39:42

IZUG091I: Environment variable "IZU_CODE_ROOT" 
is set to the value "/usr/lpp/zosmf/V1R13".
IZUG091I: Environment variable "IZU_LOGFILE_DIR" 
is set to the value "/var/zosmf/configuration/logs".
IZUG091I: Environment variable "IZU_CONFIG_DIR" 
is set to the value "/etc/zosmf".
IZUG091I: Environment variable "_BPX_SHAREAS" 
is set to the value "YES".
IZUG091I: Environment variable "PATH" 
is set to the value ".:/bin:.".
IZUG093I: The directory "/tmp/izutmp" will be used for storing temporary files.
Script caller: IBMUSER
Script command: ./izusetup.sh -file /u/in/R13SRV.cfg -config -fastpath
IZUG146I: Invoking script 
"/usr/lpp/zosmf/V1R13/bin/izuconfig.sh -config /u/in/R13SRV.cfg -fastpath".
IZUG215I: Starting z/OS MF "configuration" procedure.
Fri Jun 8 02:50:13 EDT 2012
Version: 1.44.2.3
Delta Date: 5/8/12
Delta Time: 16:46:43
IZUG237I: Enter the name of the file to save the configuration data 
(must be .cfg extension), or press Enter to save as file "/u/in/R13SRV.cfg":
IZUG243I: Accepted input: /u/in/R13SRV.cfg
IZUG145I: Enter the mount point for the z/OS MF data file system, 
or press Enter to accept the default "/var/zosmf/data":
IZUG243I: Accepted input: /var/zosmf/data
IZUG234I: File system "IZU.SIZUDATZ.DATA" is already mounted at mount point 
"/var/zosmf/data". Do you want to use the existing file system 
as the z/OS MF data file system (Y|N)?
IZUG232I: Specified z/OS MF data file system with name "IZU.SIZUDATZ.DATA" was accepted.
IZUG062I: What security mode do you want to use? To use SAF mode, enter S. 
To use Repository mode, enter R:
IZUG243I: Accepted input: REPOSITORY
IZUG073I: If you have AUTOUID enabled, RACF can assign unused UIDs for your user ids. 
Do you want RACF to automatically assign UIDs to user ids created by z/OS MF? 
For yes, enter Y. For no, enter N. Or press Enter to accept the default "Y":
IZUG243I: Accepted input: Y
IZUG071I: If you have AUTOGID enabled, RACF can assign unused GIDs for your group ids. 
Do you want RACF to automatically assign GIDs to groups created by z/OS MF? 
For yes, enter Y. For no, enter N. Or press Enter to accept the default "Y":
IZUG243I: Accepted input: Y
IZUG274I: Enter z/OS MF administrator group name, or press Enter to accept "IZUADMIN":
IZUG243I: Accepted input: IZUADMIN
IZUG069I: Configuration property "IZU_ADMIN_GROUP_GID" is set to the value "AUTOGID".
IZUG274I: Enter z/OS MF user group name, or press Enter to accept "IZUUSER":
IZUG243I: Accepted input: IZUUSER
IZUG069I: Configuration property "IZU_USERS_GROUP_GID" is set to the value "AUTOGID".
IZUG256I: Enter z/OS MF administrator user ID or press Enter to accept default "ZOSMFAD":
uid=9001(ZOSMFAD) gid=9003(IZUADMIN) groups=6321(CEAGP),9008(CPOCTRL),
9007(CPOQUERY),9400(WLMGRP),2500(WSCFG1)
IZUG257W: User "ZOSMFAD" already exists.
IZUG243I: Accepted input: ZOSMFAD
IZUG069I: Configuration property "IZU_ADMIN_UID" is set to the value "AUTOUID".
IZUG256I: Enter the z/OS MF administrator home directory, 
or press Enter to accept the default "/u/zosmfad":
IZUG243I: Accepted input: /u/zosmfad
IZUG256I: Enter the z/OS MF administrator shell program name, 
or press Enter to accept the default "/bin/sh":
IZUG243I: Accepted input: /bin/sh
IZUG256I: Enter the z/OS MF administrator logon procedure name, 
or press Enter to accept the default "OMVS0803":
IZUG243I: Accepted input: OMVS0803
IZUG256I: Enter the z/OS MF administrator account number, 
or press Enter to accept the default "123123":
IZUG243I: Accepted input: 123123
IZUG153I: Enter the directory path and name of the WebSphere Application Server 
configuration file, or press enter to accept 
"/u/zWebSphereOEM/V7R0/conf/CONFIG1/CONFIG1.responseFile":
IZUG243I: Accepted input: /u/zWebSphereOEM/V7R0/conf/CONFIG1/CONFIG1.responseFile
IZUG154I: WebSphere Application Server configuration values have been read.
IZUG340I: Variable substitution entry "IZU_APPSERVER_ROOT" 
is being updated with value "/u/wasoemcfg".
IZUG340I: Variable substitution entry "IZU_APPSERVER_GROUP" 
is being updated with value "WSCFG1".
IZUG340I: Variable substitution entry "IZU_WAS_PROFILE_PREFIX" 
is being updated with value "BBNBASE".
IZUG340I: Variable substitution entry "IZU_CLUSTER_TRANSITION_NAME" 
is being updated with value "BBNC001".
IZUG340I: Variable substitution entry "IZU_CELL_SHORT_NAME" 
is being updated with value "BBNBASE".
IZUG340I: Variable substitution entry "IZU_CONTROL_USERID" 
is being updated with value "WSCRU1".
IZUG340I: Variable substitution entry "IZU_SERVANT_USERID" 
is being updated with value "WSSRU1".
IZUG340I: Variable substitution entry "IZU_ORB_PORT" 
is being updated with value "32203".
IZUG340I: Variable substitution entry "IZU_HTTP_SSL_PORT" 
is being updated with value "32208".
IZUG340I: Variable substitution entry "IZU_APPSERVER_HOSTNAME" 
is being updated with value "ssresys.pok.ibm.com".
IZUG270I: Enter the path of the root WBEM directory, 
or press Enter to accept the default "/usr/lpp/wbem":
IZUG243I: Accepted input: /usr/lpp/wbem

IZUG162I: Select the plug-ins to be configured. 
Multiple plug-ins can be selected by separating plug-ins with a comma.
IZUG163I: Select "0" to configure ALL plug-ins.
IZUG163I: Select "1" to configure Incident Log.
IZUG163I: Select "2" to configure Configuration Assistant.
IZUG163I: Select "3" to configure Workload Management.
IZUG163I: Select "4" to configure Resource Monitoring.
IZUG163I: Select "5" to configure Capacity Provisioning.
IZUG163I: Select "6" to configure Software Deployment.
IZUG163I: Select "7" to configure ISPF.
IZUG164I: Which plug-ins do you want to configure?
IZUG165I: You have selected to configure Incident Log.
IZUG165I: You have selected to configure Configuration Assistant.
IZUG165I: You have selected to configure Workload Management.
IZUG165I: You have selected to configure Resource Monitoring.
IZUG165I: You have selected to configure Capacity Provisioning.
IZUG165I: You have selected to configure Software Deployment.
IZUG165I: You have selected to configure ISPF.

Version: 1.26.1.2
Delta Date: 5/8/12
Delta Time: 16:47:02

IZUG272I: Do you want to enable the common event adapter (CEA) component and update 
related parmlib options for using the Incident Log task? 
For yes, enter Y. For no, enter N. Or press Enter to accept the default "Y":
IZUG243I: Accepted input: Y
IZUG059I: Specify the CEA high level qualifier (HLQ) to use for log snapshot data sets. 
The HLQ can be 1-4 characters.
IZUG243I: Accepted input: CEA
IZUG277I: Enter the "country" code, or press Enter to accept the default "000":
IZUG243I: Accepted input: 000
IZUG277I: Enter the "branch" code, or press Enter to accept the default "999":
IZUG243I: Accepted input: 999
IZUG280I: Do you want to accept storage value "VOLSER(AUXPK1)"? (Y|N)?
IZUG243I: Accepted input: "VOLSER(AUXPK1)"

IZUG284I: Enter name of source data set for your existing CEAPRM00 parmlib member. 
Specify the fully qualified data set name, 
or press Enter to accept the default "CIMSSRE.R13ONLY.PARMLIB":
IZUG114I: Command  listds 'CIMSSRE.R13ONLY.PARMLIB'  was passed to script izutso.rexx.
IZUG112I: Script izutso.rexx returned with reason code  0 .
IZUG243I: Accepted input: CIMSSRE.R13ONLY.PARMLIB

IZUG064I: Enter the name of the target data set to be used for saving 
updated "CEAPRM00" parmlib member. Specify the fully qualified data set name, 
or press Enter to accept the default: "CIMSSRE.R13ONLY.PARMLIB":
IZUG114I: Command  listds 'CIMSSRE.R13ONLY.PARMLIB'  was passed to script izutso.rexx.
IZUG112I: Script izutso.rexx returned with reason code  0 .
IZUG243I: Accepted input: CIMSSRE.R13ONLY.PARMLIB

IZUG066I: Enter the name of the source data set for the IEADMCZM parmlib member. 
Specify the fully qualified data set name, 
or press Enter to accept the default "CIMSSRE.R13ONLY.PARMLIB":
IZUG114I: Command  listds 'CIMSSRE.R13ONLY.PARMLIB'  was passed to script izutso.rexx.
IZUG112I: Script izutso.rexx returned with reason code  0 .
IZUG243I: Accepted input: CIMSSRE.R13ONLY.PARMLIB

IZUG064I: Enter the name of the target data set to be used for saving 
updated "IEADMCZM" parmlib member. Specify the fully qualified data set name, 
or press Enter to accept the default: "CIMSSRE.R13ONLY.PARMLIB":
IZUG114I: Command  listds 'CIMSSRE.R13ONLY.PARMLIB'  was passed to script izutso.rexx.
IZUG112I: Script izutso.rexx returned with reason code  0 .
IZUG243I: Accepted input: CIMSSRE.R13ONLY.PARMLIB
IZUG275I: Enter the member name suffix to use for the "CEAPRM" parmlib member, 
or press Enter to accept the default "99":
IZUG243I: Accepted input: 99
IZUG114I: Command  listds 'CIMSSRE.R13ONLY.PARMLIB(CEAPRM99)'  
was passed to script izutso.rexx.
IZUG112I: Script izutso.rexx returned with reason code  0 .

IZUG199W: File "CIMSSRE.R13ONLY.PARMLIB(CEAPRM99)" already exists.

IZUG114I: Command  listds 'CIMSSRE.R13ONLY.PARMLIB(IEADMCZM)'  
was passed to script izutso.rexx.
IZUG112I: Script izutso.rexx returned with reason code  0 .
IZUG275I: Enter the member name suffix to use for the "IEADMC" parmlib member, 
or press Enter to accept the default "ZM":
IZUG243I: Accepted input: ZM
IZUG114I: Command  listds 'CIMSSRE.R13ONLY.PARMLIB(IEADMCZM)'  
was passed to script izutso.rexx.
IZUG112I: Script izutso.rexx returned with reason code  0 .

IZUG199W: File "CIMSSRE.R13ONLY.PARMLIB(IEADMCZM)" already exists.
IZUG166I: No configuration prompts are required for the plug-in Configuration Assistant.

Version: 1.13.1.1
Delta Date: 5/8/12
Delta Time: 16:47:05

IZUG047I: Enter existing Workload Management group name that is used to authorize users 
to the Workload Management resources. Press Enter to accept the default "WLMGRP", 
or enter "NO.KNOWN.VALUE" if no group exists.
IZUG243I: Accepted input: WLMGRP

IZUG166I: No configuration prompts are required for the plug-in Resource Monitoring.

Version: 1.4.1.1
Delta Date: 5/8/12
Delta Time: 16:46:59

IZUG047I: Enter existing Capacity Provisioning query group name that is used 
to authorize users to the Capacity Provisioning resources. 
Press Enter to accept default "CPOQUERY", or enter "NO.KNOWN.VALUE" if no group exists.
IZUG243I: Accepted input: CPOQUERY
IZUG047I: Enter the existing Capacity Provisioning control group name that is used 
to authorize users to the Capacity Provisioning resources. 
Press Enter to accept default "CPOCTRL", or enter "NO.KNOWN.VALUE" if no group exists.
IZUG243I: Accepted input: CPOCTRL

IZUG166I: No configuration prompts are required for the plug-in Software Deployment.
IZUG166I: No configuration prompts are required for the plug-in ISPF.

Version: 1.14.1.1
Delta Date: 5/8/12
Delta Time: 16:46:57

IZUG047I: Enter the existing Common Information Model admin group name that is used 
to authorize users to the Common Information Model resources. 
Press Enter to accept default "CFZADMGP", or enter "NO.KNOWN.VALUE" if no group exists.
IZUG243I: Accepted input: CFZADMGP
IZUG047I: Enter the existing Common Information Model user group name that is used 
to authorize users to the Common Information Model resources. 
Press Enter to accept default "CFZUSRGP", or enter "NO.KNOWN.VALUE" if no group exists.
IZUG243I: Accepted input: CFZUSRGP

IZUG224I: The configuration data was saved in file "/u/in/R13SRV.cfg".
IZUG146I: Invoking script "/usr/lpp/zosmf/V1R13/bin/izuracf.sh".
IZUG215I: Starting z/OS MF "RACF processing" procedure.

Fri Jun 8 02:50:42 EDT 2012

Version: 1.42.1.3
Delta Date: 5/17/12
Delta Time: 21:06:38

IZUG049I: z/OS MF configuration has detected SAF to REPOSITORY authorization mode switch.
IZUG034I: The z/OS MF configuration process has created a set of sample security execs 
for your reference in directory "/etc/zosmf".
IZUG033I: Examine each of the output execs and determine which exec is appropriate 
for your environment. Run one exec only.  The output execs are: 
"/etc/zosmf/R13SRV.cfg.rexx", "/etc/zosmf/R13SRV.cfg.convertFromSAFtoREP.rexx"

IZUG095I: The Common Information Model (CIM) server must be configured and started 
before proceeding with configuration.
IZUG210I: The script "/usr/lpp/zosmf/V1R13/bin/izuracf.sh" has completed.
IZUG210I: The script "./izusetup.sh" has completed.

When you complete Steps 1-4 above, the message IZUG349I will be displayed to indicate how to start the z/OS MF console. Then, start the WAS OEM procedure to start WAS OEM and z/OS MF. The message IZUG400I will be displayed in SYSLOG to indicate that z/OS MF is initialized and ready to use.

Listing 3. Successful messages
IZUG349I: 
The "z/OSMF Welcome panel" can be accessed at "https://xxxx.pok.ibm.com:32208/zosmf" 
after the application server is started on your system. BPXM023I (WSSRU1) 
IZUG400I: 
The z/OS MF Web application services are initialized in REPOSITORY Authorization Mode.

z/OS MF plug-ins

Besides Steps 1-4 above, you can add each plug-in individually as long as the z/OS MF core has been configured. Specify the option -add within each izusetup step, and then follow Steps 1-4 steps again. A brief summary of the settings for each z/OS MF plug-in is listed below. For more details, see the z/OS MF information center and the online help on the z/OS MF console.

Capacity Provisioning (CP)

Provides a browser-based UI to manage your domain configurations and policies, and to request various reports of the status of the CP Manager. To configure the CP plug-in, check the following items:

  1. Ensure that the CP plug-in is selected in .cfg when doing -config.
  2. Consult your administrator regarding the user groups with Query and Control roles for the CPM subsystem. Ensure that the Admin of z/OS MF is connected to them in Step 2 above.
  3. Enable the PTKTDATA class on both sides when there is secure sign-on to a remote server.
  4. If you add this plug-in individually, ensure that the generated RACF commands are submitted as in Step 2 above to define the profiles in class ZMFAPLA and permit the appropriate user groups:
    Prefix.ZOSMF.CAPACITY_PROVISIONING.CAPACITY_PROVISIONING.VIEW
    Prefix.ZOSMF.CAPACITY_PROVISIONING.CAPACITY_PROVISIONING.EDIT.**

Configuration Assistant (CA)

Provides a GUI, wizards, and online help to create configuration files for any number of z/OS images with any number of TCP/IP stacks per image. to configure the CA plug-in, check the following items:

  1. Ensure that the CA plug-in is selected in .cfg when doing -config.
  2. Optional: Move the existing backing store file for the Windows® version into z/OS MF.
  3. If you add this plug-in individually, ensure that the generated RACF commands are submitted as in Step 2 above to define the profiles in class ZMFAPLA and permit the appropriate user groups:
    Prefix.ZOSMF.CONFIGURATION_ASSISTANT.**

Incident Log (IL)

When a problem occurs on a z/OS system, the IL can help you diagnose and fix the problem, or else report it to IBM or an ISV. The IL is a problem data management solution that can help you with the time-consuming task of gathering the relevant diagnostic data and sending it to a support team. To configure the IL plug-in, check the following items:

  1. Ensure that the IL plug-in is selected in .cfg when doing -config.
  2. Ensure that CIM is configured.
  3. Ensure that CEA is configured.
  4. Ensure that SYSREXX is configured.
  5. Ensure that OPERLOG and LOGREC are configured.
  6. Set up the automatic allocation of dump dataset.
  7. Set up the sysplex dump directory.
  8. Set up DAE.
  9. If you add this plug-in individually, ensure that the generated RACF commands are submitted as in Step 2 above to define the profiles in class ZMFAPLA and permit the appropriate user groups:
    Prefix.ZOSMF.INCIDENT_LOG.**

Resource Monitoring (RM)

Provides a web-based UI to monitor the performance of z/OS sysplexes, AIX system complexes on System p®, Linux system complexes on System z® and System x®, and Linux images on System z and System x. With the RM task, you can monitor most of the metrics of the Resource Measurement Facility (RMF) Monitor III. To configure the RM plug-in, check the following items:

  1. Ensure that the RM plug-in is selected in .cfg when doing -config.
  2. Ensure that the RMF Distributed Data Server is configured.
  3. Enable the PTKTDATA class on both sides when there is secure sign-on to a remote server.
  4. If you add this plug-in individually, ensure that the generated RACF commands are submitted as in Step 2 above to define the profiles in class ZMFAPLA and permit the appropriate user groups:
    Prefix.ZOSMF.RESOURCE_MONITORING.**

Workload Management (WLM)

Provides a browser-based UI to manage z/OS Workload Manager service definitions and provide guidelines for it to use when allocating resources. To configure the WLM plug-in, check the following items:

  1. Ensure that the WLM plug-in is selected in .cfg when doing -config.
  2. Consult the WLM Administrator. Ensure that the Admin of z/OS MF is connected to them in Step 2 above and has the access authority to WLM policy.
  3. If you add this plug-in individually, ensure that the generated RACF commands are submitted as in Step 2 above to define the profiles in class ZMFAPLA and permit the appropriate user groups:
    Prefix.ZOSMF.WORKLOAD_MANAGEMENT.WORKLOAD_MANAGEMENT.VIEW
    Prefix.ZOSMF.WORKLOAD_MANAGEMENT.WORKLOAD_MANAGEMENT.MODIFY
    Prefix.ZOSMF.WORKLOAD_MANAGEMENT.WORKLOAD_MANAGEMENT.INSTALL

Software Management (SM)

Previously named the Deployment task, SM contains the software deployment functions to make cloning of SMP/E installed software simpler and safer. To configure the SM plug-in, check the following items::

  1. Ensure that the SM plug-in is selected in .cfg when doing -config.
  2. Enable sharing of digital certificates to allow deployment task work with other systems or sysplexes.
  3. If you add this plug-in individually, ensure that the generated RACF commands are submitted as in Step 2 above to define the profiles in class ZMFAPLA and permit the appropriate user groups:
    Prefix.ZOSMF.SOFTWARE_DEPLOYMENT.**
    Prefix.ZOSMF.SOFTWARE_DEPLOYMENT.DATA.**
    Prefix.ZOSMF.SOFTWARE_DEPLOYMENT.SOFTWARE_MANAGEMENT.PRODUCT_INFO_FILE.*

Web ISPF

Provides a browser-based UI with the same functionality as z/OS ISPF for the experienced ISPF user. To configure the ISPF plug-in, check the following items::

  1. Ensure that the ISPF plug-in is selected in .cfg when doing -config.
  2. Ensure that CEA is configured.
  3. If you add this plug-in individually, ensure that the generated RACF commands are submitted as in Step 2 above to define the profiles in class ZMFAPLA and permit the appropriate user groups:
    Prefix.ZOSMF.ISPF.**

For more information on the RACF commands, see the z/OS MF Configuration Guide in the z/OS MF information center for each of the ZMFAPLA profiles mentioned above.

Resources

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into WebSphere on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=845179
ArticleTitle=Modernizing your z/OS system administration with z/OS Management Facility
publish-date=11072012