IBM Education Assistance for z/OSMF V2R1 · Material is current as of May 2013 © 2013 IBM Corporation Item: New Release Content Element/Component: z/OS Management Facility IBM Education

© 2013 IBM CorporationMaterial is current as of May 2013

Item: New Release ContentElement/Component: z/OS Management Facility

IBM Education Assistance for z/OSMF V2R1

© 2013 IBM Corporation

Filename: zOS V2R1 zOSMF

Agenda

■ Trademarks■ Overview■ Usage & Invocation■ Interactions & Dependencies■ z/OSMF Browser Support■ Migration & Coexistence Considerations■ Installation■ Presentation Summary■ Appendix

IBM Presentation Template Full Version



Trademarks

■ See url http://www.ibm.com/legal/copytrade.shtml for a list of trademarks.


http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml



Overview

■ Problem Statement / Need Addressed – z/OSMF needs to provide improved configuration experience and a smaller and

faster product package that requires fewer resources. – More functions should be provided to enable the system programmer to

manage the z/OS system better

■ Solution– z/OSMF V2R1 has been rebased on the WebSphere Liberty profile and

delivers a smaller faster product and requires less resources. It is also easier to configure.

– The workflow function has a focus to simplify configuration on z/OS

■ Benefit / Value – z/OSMF can be installed and configured more easily on more systems. – z/OSMF will consume fewer resources and provide more benefit to z/OS clients– The workflow function will provide a basis for future simplification and time to

value




z/OSMF V2R1 welcome panel after login



z/OSMF Software Management

■ The z/OSMF Software Management application (was previously called Software Deployment) extends the Software Deployment task to provide additional actions on instances of SMP/E installed software. It is available on z/OS V1R13 with the PTF UK83841.

■ The Software Management task supports– Deploying a software instance, – Inspection of a software instance to view the product, feature and FMID content, and view the

physical data sets that compose a software instance. – Actions to analyze and report on software instances and products within instances to:

• Identify software products that are approaching, or have reached, end of service support, thus helping customers with upgrade and migration planning.

• Identify missing HIPER and PE fixes, and fixes associated with one or more fix categories to help customers assess the risks and stability of installed software and ensure hardware and software requisites are installed.

• Validate the SMP/E structure and content of a software instance is correct by cross-check SMP/E inventory information with catalog entries, volume residency and data set content.

• Determine if individual fixes are installed and in which software instances.• Compare the service and functional content of two software instances to aid in debugging

or migration planning.

■ In V2R1, Software Management provides Print/Export function for some reports



z/OSMF Workflow

■ Problem being solved:–Configuring a new product or component on z/OS is complex and a

pain point for customers –Customers want consistent, simplified and less error prone way to

configure and perform a set of tasks on z/OS • simplified and managed instructions, interface, tools, wizards, etc.

■ z/OSMF V2R1 provides a workflow framework with a focus to simplify configuration on z/OS or perform a set of tasks on z/OS

■ z/OSMF workflow function will enable bringing together the end-to-end steps for configuration of the selected software

–Provide an programmatic to-do list (aka workflow)–Shorten the time to value

■ Note: the workflow framework will be generic and not confined to configuration only, although that is the initial focus



Use Case Scenario

■ A product decides to participate in z/OSMF workflow■ The product owner defines the metadata file with steps required by their product

– z/OSMF will define and publish the schema for product owners to code to■ The product delivers its metadata file with their product package (SMP/E or non

SMP/E) and documents its location in their program directory (or equivalent)– It is possible that the metadata file is generated as part of some other

configuration steps for that product.■ The product is installed (SMP/E or non SMP/E) on the customer’s z/OS system ■ The customer now wants to configure the product on their z/OS system■ They will follow the product instructions for configuring the product and at some

point in the instructions it will instruct to use the z/OSMF Workflow task to configure the z/OS artifacts

– The customer/system programmer would then need to log in to z/OSMF and open the ‘Workflow task'



Use Case Scenario (contd.)

■ The system programmer logs on to z/OSMF and loads the workflow metadata file for the unit to be configured.

■ In the new Workflow task, the user can define the unit to be configured by identifying the metadata file via Action: CREATE in this new task

–Prompts the user to provide the fully qualified location–Reads in the metadata file(s). Once loaded, it is ready to be used.

The original metadata file(s) is no longer used. If the product provides an update to the metadata file(s), then the z/OSMF user would need to have the Workflow task re-import it to pick up the changes

■ The system programmer can then start by opening a workflow ■ This will start a workflow instance that will allow the user to

view/assign/perform all the steps necessary to configure the given product



Workflow characteristics■ z/OSMF provides an XML schema for products to use to define their

workflow steps in an XML document■ It contains ways to indicate the steps to complete a workflow

– Simple samples are shipped with the product

■ The products would provide this file for the workflow task to import it and then display to the end user for configuring their product

■ There will likely be a set of files that comprise the metadata and the end user will provide the workflow task with a single entity and all other relevant files will be imported automatically.

– Examples of addition files are Job templates, REXX or shell script templates Configuration file

■ Wizards are provided to automate common tasks to aid in configuring z/OS for the given product;

– JCL wizard to update and submit a job– REXX execs and shell scripts supported within generated batch jobs

■ Workflow metadata file packaging – may be USS file or a dataset member



Workflow characteristics■ The XML metadata file contains steps and details;

– Steps may be manual or invoke wizards; – Steps may define dependency on other steps

■ The workflow task provides ability to route tasks among a number of defined users or people assigned to specific roles, such as "system programmer" and "security administrator," to complete setup tasks.

■ The z/OSMF user is notified of assigned workflow steps via the new Notification task ■ The workflow supports wizard-like task sequencing, with tasks presented to

additional users as dependencies are met■ The workflow steps go through various stages until complete;

– The stages may be unassigned, assigned, accepted, not ready, ready, in progress, complete, complete(override), skipped

■ Workflow history is maintained of all activities in the workflow task■ Users can make notes for a workflow instance



z/OSMF workflow – create an instance



z/OSMF configuration - Workflow example

Workflow stepsState of steps

Assigned Notes, history



Workflow JCL wizard

Wizard steps



Workflow history



Enhancements to RESTful Jobs API

■ Recent enhancements to JOBS Submit API–Also available on z/OSMF V1R13 via APAR PM74502

■ Deprecation of non X-IBM- prefixed custom headers■ Access to job JCL■ Submit from data set (including the ability to request a recall of a migrated

data set)■ Submit from z/OS UNIX file■ Secondary JES2 subsystem support for cancel a job, change job class,

and delete a job (cancel a job and purge its output)



Enhancements to RESTful Jobs API

In z/OS V2R1 with z/OSMF V2R1, the z/OS Jobs REST Interface is extended to add support for■ optional asynchronous notification upon job completion,■ passing JCL symbols to a job being submitted, and ■ an optional job correlator that is unique across the JES2 spool.

These extensions are intended to make it easier to reuse existing JCL and detect job completion.



JCL symbolic:

■ The user is able to provide the values in HTTP headers for JCL symbols when submitting a job.

■ This support is JES2 specific.

Example:■ Symbol name MBR with value equal to ABC in HTTP request headers:

PUT https://host:port/zosmf/restjobs/jobs/

Content-Type: applicaton/json

X-IBM-Intrdr-Lrecl: 80

X-IBM-JCL-Symbol-MBR:ABC

■ Part of the codes in JCL something like:

//MYDD DSN=MY.DATASET(&MBR.),DISP=SHR

■ When submit the job to JES, ABC substitutes parameter &MBR as the member name

//MYDD DSN=MY.DATASET(ABC),DISP=SHR



JCL correlator:

■ The user can provide the user portion of the job correlator when submitting a job.

■ The job correlator can be used as an alternative to the jobname/jobid combination for identifying a job.

■ This support is JES2 specific. ■ Example:

–Submit a job with user portion job correlator: –PUT https://host:port/zosmf/restjobs/jobs/ Content-Type:

application/json X-IBM-User-Correlator: @234567890ABCDEF2234567890ABCDE4



Asynchronous Notification for Job completion

■ The user is able to provide a URL when submitting the job. ■ The URL will be sent an HTTP message when the job has completed.■ This support is JES2 specific.■ Example:

–Submit a job with notification URL: –PUT https://host:port/zosmf/restjobs/jobs/Content-Type:

application/jsonX-IBM-Notification-URL: http://alps4223.pok.ibm.com:32207/UberTestUnsecured/job-complete

■ Job Completed JSON Object received

{"abend-code":null,"owner":"ZOSMFAD","class":"A","jobname":"SUBAPI01","jobid":"JOB00089","job-correlator":"J0000089SY1.....C9E2C342.......:","completion-type":1,"completion-code":0,"retcode":"CC 0000"}



Enhancements to Incident Log

■ The z/OSMF Incident Log application allows you to modify its default JCL to meet the needs of your organization (It is available on z/OS V1R13 with the PTF UK83842)

■ The z/OSMF Incident Log application is extended to use enhanced FTP.DATA Support in V2R1 PDUU.

■ PDUU Enhancement in V2R1 expands the TARGET_SYS parameter to accept up to 256 characters. This new function is intended to support this PDUU enhancement in V2R1.

■ In addition, the supported HLQ length of diagnostic data is extended to 8 characters.



Enhancements to Resource monitoring and Workload Management

■ The z/OSMF Resource Monitoring application is linked to the z/OSMF Workload Management application in context, and the z/OSMF Workload Management application is linked to the z/OSMF Resource Monitoring application.

■ The System Status task is linked to the Workload Management task such that the active service definition, active service policy, or WLM status can be opened and viewed. The Workload Management task is linked to Resource Monitoring dashboards such that while viewing the active service definition or service policy, resource monitoring dashboards with performance metrics for service classes, workloads, and report classes can be opened and viewed.

■ This function is available on z/OSMF V1R13 With PTF UK83833 and PTF UK83836.

■ In V2R1, z/OSMF Resource Monitoring is enhanced to monitor the performance of Windows on System x.

■ In V2R1, z/OSMF Workload Management is enhanced to support new function level of service definition for z/OS WLM



View performance of Active policy



View active service definition



Enhancements to Capacity Provisioning

■ The z/OSMF Capacity Provisioning application is enhanced to allow you to create, edit, and activate domain configurations and capacity provisioning policies.(Available on V1R13 with PTF UK83852)

– With these new functions z/OSMF Capacity Provisioning supports all the functions available in the Microsoft Windows-based Capacity Provisioning Control Center (CPCC).

■ In V2R1, it requires the z/OSMF Capacity Provisioning task for managing the z/OS Capacity Provisioning Manager (CPM)

■ z/OSMF V2R1 Capacity Provisioning also supports the latest enhancements in the Capacity Provisioning Manager

• Defined Capacity and Group Capacity management capabilities• Can be increased and decreased via z/OSMF based on your

schedules or the workload running on your system. • Allows you to define additional scopes and limits to reflect your

business needs for additional Defined Capacity or Group Capacity.



Enhancements to Configuration Assistant for z/OS Communications Server

■ This function is redesigned for new and improved web user experience and performance

■ Redesigned panels provide a new look and feel that tightly integrates with z/OSMF and other plug-ins

■ Improved performance due to execution of more function in the browser rather than on the host

■ With V2R1, Windows download will no longer be provided, users must migrate to z/OSMF

■ New function provided in support of V2R1 z/OS Communications Server Policy-Based Networking

– AT-TLS support of TLS V1.2– Policy-based Routing (PBR) support for IPv6



V2R1 Configuration Assistant



Other recent enhancements

■ The z/OSMF ISPF application is enhanced to get the completion status of long running commands, without any user intervention (PTF UK83828)

■ With PTF UK83825 on z/OSMF V1R13, the Systems and FTP Servers tasks are available under z/OSMF Settings.

– The Systems task allows you to define the settings required for z/OSMF to access other systems in your installation and to define the HTTP proxy settings for z/OSMF to use when establishing an HTTPS connection to another system.

– The FTP Servers task allows you to define the settings required for z/OSMF to access the FTP servers that are running on internal or external systems and to define the settings for z/OSMF to use when transferring files between systems.

■ Usability: Additional filter capabilities are designed to improve ease of use for the user. The z/OSMF table filtering support has been enhanced to allow for AND/OR filtering as well as case sensitive filtering for more granular filtering capabilities (PTF UK83825)



z/OSMF WAS Liberty support

■ Evolution of z/OS Management Facility configuration■ New and simplified z/OSMF V2R1

–Packaging–Configuration –Performance –Security



z/OSMF configuration evolution

■ z/OSMF V1R11– z/OSMF includes WebSphere OEM and z/OSMF apps– Separate setup required for each, with similar steps– CIM server setup included, and non-optimal– Phase 1 fixpack included many changes – collapsed 11 distinct script invocations to 3

with the same script.

■ z/OSMF V1R12– Separated CIM setup, only emitted CIM security setup if requested– Improved CIM setup instructions – Added new plug-ins, all plug-in setup now optional– Security setup enhanced, simplified

■ z/OSMF V1R13– Added new plugins– Security updates – authorization modes, roles, groups

■ z/OSMF V2R1 – Eliminate WebSphere OEM package and separate setup– Single stream configuration, 1 setup only– Improved performance, reduced resources



Package ■ New product package 5610-A01

–WAS OEM is now removed from z/OSMF (HBBN700)–z/OSMF product package is much smaller in size –WAS Liberty Profile is part of z/OSMF package

■ File systems:–Product file system

• /usr/lpp/zosmf/V2R1–Data file system

• /var/zosmf/data■ Other directories:

–Configuration file system by default wil be in /etc/zosmf–Logfiles by default in /var/zosmf/configuration/logs–Data file system mount point by default will be /var/zosmf/data

■ Recommended size – is documented in Program Directory for product file system and in Configuration Guide for data file system



Simplified Configuration ■ z/OSMF setup to no longer require two separate configurations for

runtime(WASOEM) and application(z/OSMF); it is reduced to one ■ Fewer overall prompts and variables■ JAVA 1.7 64 bit SR3 is required (pre-req)

■ Configuring z/OSMF–Option 1

• Configure z/OSMF core• Perform pre-req setup for all/selected plugins (optionally using workflow)• Add all/selected plugins as required or as ready

–Option 2• Complete pre-req setup for all/selected plugins • Configure z/OSMF which includes core and all/selected plugins



Simplified Configuration

■ z/OSMF configuration is collapsed, with fewer steps:1)izusetup.sh –file izuconfig1.cfg –config2)Security setup

● Verify security setup3)izusetup.sh –file izuconfig1.cfg –finish

■ No longer require separate deployment of applications■ Support default TCPIP Port for HTTP communication

• http port 80 and https port 443• Note: https port preserved on migration, http port default set to 80

■ z/OSMF intends to exploit the z/OSMF workflow for z/OSMF configuration. V2R1 delivers stage 1 of the configuration workflow. This workflow covers the pre-requisite z/OS system setup for the plugins. The steps are mainly manual steps.



z/OSMF improved service and performance

■ Simplified service; follow the normal z/OS model; –Perform normal SMPE receive/apply and restart z/OSMF to pick up

new service. –Separate step not required for activation (i.e. No izusetup.sh –file

izuconfig1.cfg –service step)

■ Improved performance –Faster configuration since there is no longer any deployment of apps

nor data movement–Faster startup (few seconds instead of minutes)–Reduced memory requirement

• Package footprint reduced to 1/3 of previous release• Memory requirement reduced to half of previous release



z/OSMF V2R1 Security

■ Only support SAF authorization mode–Requires ZMFAPLA class be enabled

■ Removed separate z/OSMF administrator id (default was ZOSMFAD)–Since V2R1 only supports SAF authorization mode, this ID is not

longer needed–Still require that an id be authorized to z/OSMF during configuration

■ Add–z/OSMF server started task id (Used for STARTED definitions)–z/OSMF unauthenticated user id (Similar to the id WAS OEM had)–Include setup of the necessary certificates and keyring for SSL–Create a Certificate Authority(CA) by default, and server cert (self-

signed)• Optionally can choose not to create a CA

– Useful for multiple z/OSMFs in the enterprise– Hardware crypto support is built in



z/OSMF release migration

■ There will be a migration support for upgrading z/OSMF from prior releases – the administrator would need to run a series of scripts.

1)Migrate the configuration and optionally the override file● izumigrate.sh

2)Establish the new configuration file and resolves any new references added in V2R1 like the z/os security administrator role or references for Liberty.

● izusetup.sh –config

3)In V2R1, a new setup for Liberty security is required. In addition, we’ll remove the Repository authorization mode Everyone will need to be in SAF mode.

4)Complete all configuration actions● izusetup.sh –finish



Interactions & Dependencies

■ Software Dependencies–z/OS V2R1–JAVA 1.7 64 bit SR3

■ Hardware Dependencies–None

■ Exploiters–None

■ Clients Supported –Windows XP, Windows 7 (32 bit and 64 bit)




z/OSMF V2.1 Browser support

■ A new integrated help system Knowledge Center Local Edition 1.0.0 is introduced to replace IEHS (IBM User Interface Help System based on Eclipse) in z/OSMF V2R1.

■ Following browsers and platforms are supported in z/OSMF V2R1:

Windows XP 32 bit

Windows 7 32 bit Windows 7 64 bit

Firefox ESR 17.0.x Yes Yes Yes

Internet Explorer 8.x

Yes Yes Yes

Internet Explorer 8.x (x64)

No No Yes


No Yes Yes


No No Yes

Windows XP 32 bit

Windows 7 32 bit Windows 7 64 bit

Firefox ESR 17.0.x Yes Yes Yes


Yes Yes Yes


No No Yes


No Yes Yes


No No Yes



Migration & Coexistence Considerations

■ Migration involves only those actions required to make the new system behave as the old one did.

–z/OSMF provides the scripts and instructions to migrate from a previous release.

–SAF mode is required for V2R1 and scripts are provided help convert from Repository mode to SAF mode.

– Note: If migrating from z/OSMF V1R13, the conversion to SAF mode can be performed in V1R13 also, prior to migration to z/OSMF V2R1

■ Coexistence applies to lower-level systems which coexist (share resources) with latest z/OS systems.

– In z/OSMF coexistence implies ability to Switch back to a lower z/OSMF release and also switch back to z/OSMF V2R1. This would typically be done after or during migration from lower release of z/OSMF.

– Software Management: can work with mix of V1R13 and V2R1 systems■ No Coexistence APARs identified




Installation

■ z/OSMF can be ordered with the z/OS V2R1 ServerPac or by itself in the product ServerPac.

■ Product id is 5610-A01■ ServerPac supplies installation jobs for the z/OSMF Core function using a

supplied override default file.–Plugins can be added later following the instructions in the z/OSMF

Configuration guide.■ ServerPac includes the security setup which includes new support in the

(RACFTGT and RACFDRV) jobs and support of the new WAS 8.5 level (Liberty) which will now be part of the z/OSMF install and not be a separate install.




Presentation Summary

■ z/OSMF V2R1 delivers an improved product package ■ Product package is smaller, faster and easier to configure

–It included the WebSphere 8.5 liberty profile instead of WASOEM.■ z/OSMF V2R1 includes enhancements to z/OSMF V1R13 as well as new

workflow and notifications framework to enable better end to end tasks management

–Watch for enhancements in capability and increased exploitation of Workflow going forward




Appendix: z/OSMF product packageProduct ID: 5610-A01

S&S 5655-S29

FMID COMPID Component Name

HSMA210 5655S28SM z/OSMF Core Functions

HSMA210 5655S28RJ z/OSMF RESTJOBS

HSMA210 5655S28WL WebSphere Liberty Profile

HSMA210 5655S28TS z/OSMF TSO REST Services

HSMA211 5655S2801 z/OSMF ISPF

HSMA212 5655S2802 z/OSMF Resource Monitoring

HSMA213 5655S2803 z/OSMF WLM

HSMA214 5655S2804 z/OSMF Software Deployment

HSMA215 5655S2805 z/OSMF Incident Log

HSMA216 5655S2806 z/OSMF Capacity Provisioning

HSMA217 5655S2807 z/OSMF Workflow

HSMA21A 5655S28CA z/OSMF Configuration Assistant



Appendix: Publications

■ IBM z/OS Management Facility Configuration Guide Version 2 Release 1 – SA38-0657

■ IBM z/OS Management Facility Programming Version 2 Release 1 – SA32-1066

■ Program Directory for IBM z/OS Management Facility V2.1.0 –GI11-9847



Appendix: Sample configuration file (refer to product documentation for latest copy)

■ Here is sample of configuration file.■ IZU_CONFIG_FILE_VERSION=2.1.0■ IZU_DATA_DIR=/var/zosmf/data■ IZU_DATA_FS_NAME=IZU.SIZUDATA■ IZU_DATA_FS_TYPE=ZFS■ IZU_DATA_FS_VOLUME='*'■ IZU_DATA_FS_SIZE=200■ IZU_AUTOUID_OVERRIDE=NO.DEFAULT.VALUE■ IZU_AUTOGID_OVERRIDE=NO.DEFAULT.VALUE■ IZU_ADMIN_GROUP_NAME=IZUADMIN■ IZU_ADMIN_GROUP_GID=9003■ IZU_USERS_GROUP_NAME=IZUUSER■ IZU_USERS_GROUP_GID=9004■ IZU_HTTP_SSL_PORT=443■ IZU_HTTP_PORT=80■ IZU_APPSERVER_HOSTNAME=@HOSTNAME■ IZU_CIM_ADMIN_GROUP_NAME=CFZADMGP■ IZU_CIM_USER_GROUP_NAME=CFZUSRGP■ IZU_ZOS_SECURITY_ADMIN_GROUP_NAME=IZUSECAD■ IZU_ZOS_SECURITY_ADMIN_GROUP_GID=9006■ IZU_CA_CONFIGURE=NO.DEFAULT.VALUE■ IZU_CP_CONFIGURE=NO.DEFAULT.VALUE■ IZU_CP_QUERY_GROUP_NAME=CPOQUERY■ IZU_CP_CONTROL_GROUP_NAME=CPOCTRL■ IZU_DM_CONFIGURE=NO.DEFAULT.VALUE■ IZU_IL_CONFIGURE=NO.DEFAULT.VALUE■ IZU_IL_CEA_CONFIGURE=Y

■ IZU_CEA_HLQ='CEA'■ IZU_COUNTRY_CODE=NO.DEFAULT.VALUE■ IZU_BRANCH_CODE=NO.DEFAULT.VALUE■ IZU_STORAGE_VALUE=NO.DEFAULT.VALUE■ IZU_CEAPRM_SOURCE_PARMLIB=SYS1.PARMLIB■ IZU_CEAPRM_TARGET_PARMLIB=SYS1.PARMLIB■ IZU_IEADMC_SOURCE_PARMLIB=SYS1.SAMPLIB■ IZU_IEADMC_TARGET_PARMLIB=SYS1.PARMLIB■ IZU_CEA_PARM_NAME=01■ IZU_IEA_PARM_NAME=ZM■ IZU_WISPF_CONFIGURE=NO.DEFAULT.VALUE■ IZU_RMF_CONFIGURE=NO.DEFAULT.VALUE■ IZU_WLM_CONFIGURE=NO.DEFAULT.VALUE■ IZU_WLM_GROUP_NAME=WLMGRP■ IZU_STARTED_TASK_USERID_NAME=IZUSVR■ IZU_STARTED_TASK_USERID_UID=9010■ IZU_STARTED_TASK_HOME=/u/izusvr■ IZU_STARTED_TASK_PROGRAM=/bin/sh■ IZU_SAF_PROFILE_PREFIX=IZUDFLT■ IZU_DEFAULT_CERTAUTH=Y■ IZU_UNAUTHENTICATED_NAME=IZUGUEST■ IZU_UNAUTHENTICATED_UID=9011■ IZU_UNAUTHENTICATED_GROUP_NAME=IZUUNGRP■ IZU_UNAUTHENTICATED_GROUP_GID=9012

Documents

IBM Education Assistance for z/OSMF V2R1 · Material is current as of May 2013 © 2013 IBM Corporation Item: New Release Content Element/Component: z/OS Management Facility IBM Education