z/VM service required for IBM zEnterprise Unified Resource Manager

The IBM zEnterprise Unified Resource Manager (zManager) provides integrated management for the zEnterprise System. The information below provides you with required service to run with IBM zEnterprise Unified Resource Manager and offers some additional tips and resources.
These APARs require:
  • For z/VM 6.1, driver D86 to be at bundle 47z or higher or driver D93 to be at bundle 23z or higher
  • For z/VM 6.2, driver D93 to be at bundle 23z or higher
APAR PTF1
(VM Release) 		Description
VM64822 UM33246
(z/VM 6.1)
NOTE: This PTF should not be combined with other PTFs when ordered. 		Special Corrective service delivery package providing z/VM support for zEnterprise Unified Resource Manager. This package includes requisites back to the 1002 service level, which was delivered on the 6103RSU.

Components affected: CP, CMS(SMAPI), PerfKit, TCP/IP, DirMaint

VM64904 UM33269
(z/VM 6.1) 		Provides additional updates and corrections to both existing SMAPI function and the new/updated function provided in VM64813. This APAR is strongly recommended for all installations that installed VM64813 directly or through VM64822.

Components affected: CMS(SMAPI)

VM64917 UM33302
(z/VM 6.1) 		Provides additional updates and corrections to both existing SMAPI function and the new/updated function provided in VM64813. This APAR is strongly recommended for all installations that installed VM64813 directly or through VM64822.

Components affected: CMS(SMAPI)

VM64956 UM33380
(z/VM 6.1) 		Provides additional updates and corrections to both existing SMAPI function and the new/updated function provided in VM64813. This APAR is strongly recommended for all installations that installed VM64813 directly or through VM64822.

Components affected: CMS(SMAPI)

VM65003 UM33435
(z/VM 6.1) 		Provides additional updates and corrections to both existing SMAPI function and the new/updated function provided in VM64813. This APAR is strongly recommended for all installations that installed VM64813 directly or through VM64822.

Components affected: CMS(SMAPI)

VM64957 UM33373
(z/VM 6.1) 		APAR VM64957 is required to avoid issues restarting the z/VM Management Guest during a concurrent bundle upgrade.

Components affected: CP

VM65054 UM33513
(z/VM 6.1) 		APAR VM65054 is required to avoid instances where SMAPI will leave an ensemble during a restart.

Components affected: CMS(SMAPI)

VM65055 UM33514
(z/VM 6.1)
UM33547
(z/VM 6.2) 		With APAR VM65055, SMAPI administrators of an Ensembled Managed z/VM systems may, under some circumstances, wish to bypass maintenance of the proper ownership and state of Ensemble-owned resources upon a SMAPI restart. In that case, a SMAPI restart without a reset of Ensemble-owned resources may be considered expedient.

Components affected: CMS(SMAPI)

VM65136 UM33655
(z/VM 6.1)
UM33656
(z/VM 6.2) 		APAR VM65136 is required to avoid sychronization concerns between SMAPI and the HMC which may occur When the SMAPI VSMPROXY (SCLP Request Server) is re-IPLed. The ensemble manager is not aware the SMAPI environvment was recycled and therefore no longer receives event notifications from SMAPI.

Components affected: CP

VM65083 VM65151 UM33651
(z/VM 6.2) 		Provides additional updates and corrections to the SMAPI ensemble management support provided with z/VM 6.2. This APAR is strongly recommended for all installations that installed z/VM 6.2 for the purpose of being ensemble managed.

Components affected: CMS(SMAPI)

VM65139 UM33697
(z/VM 6.2) 		Allows the Unified Resource Manager, with driver 93 bundle 28z, to collect improved performance monitoring and network metric statistics from the z/VM hypervisor for Layer 2 networking resources associated with virtual server usage of the intraensemble data network (IEDN).

Components affected: CMS(SMAPI)

VM65162 VM65184 UM33729
(z/VM 6.2) 		Provides additional updates and corrections to the SMAPI ensemble management support, especially support for caching directory entries, provided with z/VM 6.2. LOHCOST routines have been updated to handle exceptionally large user directory entries, and to prevent loading data that would cause the data cache to exceed the storage space available for the cache. This APAR is strongly recommended for all installations that installed z/VM 6.2 for the purpose of being ensemble managed.

Components affected: CMS(SMAPI)

VM65271 UM33972
(z/VM 6.2) 		Provides a new tool for SMAPI called SMSTATUS EXEC. SMSTATUS makes it easy to capture data about the SMAPI environment for submission to IBM when a problem in the SMAPI environment is suspected. Instructions for the setup and use of SMSTATUS are documented in Appendix F of the z/VM 6.2.0 Systems Management Application Programming publication (SC24-6234-04).

z/VM 6.2 Publications

Components affected: CMS(SMAPI)

VM65217 UM33870
(z/VM 6.2) 		Provides updates to the output from the SMAPI configuration checker, DMSWSCHK EXEC, to match published SMAPI documentation. does not match the documentation in the SMAPI book. These updates provide more meaningful and accurate messages when the checker is run. The changes also clean up some discrepancies between the output of the configuration checker and what is documented in the z/VM 6.2.0 Systems Management Application Programming publication (SC24-6234-04).

z/VM 6.2 Publications

Components affected: CMS(SMAPI)

VM65231 UM33798
(z/VM 6.2) 		Corrects a timeout condition on the Manage Virtual Switch panel when attempting to manage PORTBASED VSwitches

Components affected: CP

VM65290 UM34320
(z/VM 6.2) 		The following API's return additional/incorrect output which does not match the API's documentation:
  • VIRTUAL_NETWORK_VLAN_QUERY_STATS
  • VIRTUAL_NETWORK_VSWITCH_QUERY_EXTENDED
  • VIRTUAL_NETWORK_VSWITCH_QUERY_STATS
The returned output from the APIs contain extra, undocumented values, which include null terminators and embedded binary zeroes, between output parameters.

Warning: Installations using the Unified Resource Manager for integrated systems management of z/VM must apply bundle 81z for driver D93 (z196 / z114) and bundle 18 for driver D15 (zEC12 / zBC12) before applying the PTF for VM65290.

Applying the PTF for APAR VM65290 before the specific bundle is available will cause incorrect results, and possible failures, to occur while managing z/VM through the Unified Resource Manager.

Components affected: CMS (SMAPI)

VM65291 UM33911
(z/VM 6.2) 		Corrects the handling within SMAPI when the Unified Resource Manager has requested the deletion of a managed virtual server.

Components affected: CMS (SMAPI)

VM65323 UM33979
(z/VM 6.2) 		Corrects handling of _DM API requests to route the work to the directory manager while the directory caching database (LOHCOST) is initalizing.

Components affected: CMS (SMAPI)

VM65374 UM34477
(z/VM 6.2) 		Installations using the Unified Resource Manager for integrated systems management of z/VM should apply z/VM 6.2 APAR VM65374 prior to applying bundle 25 for driver D15 (zEC12 / zBC12). The combination of z/VM APAR and firmware bundle allows a cloned z/VM image to properly join an ensemble. The z/VM APAR alerts the operator of the need for an IPL when a cloned image attempts to join an ensemble. This operator notification will not occur when applying the firmware bundle prior to the z/VM APAR.

Components affected: CMS (SMAPI)


1 When using IBM Shopz order using the PTF number.

What is IBM zEnterprise Unified Resource Manager?

End-to-end management of the heterogeneous environment of a zEnterprise System is provided by the IBM zEnterprise Unified Resource Manager. The resources of a zEnterprise System ensemble are managed and virtualized as a single pool of resources. Virtual server lifecycle management enables directed and dynamic virtual server provisioning from a single, uniform point of control. Virtual server management functions permit virtual servers to be created and deleted, and allow real and virtual networking resources to be managed by the Unified Resource Manager. Enhancements to z/VM allow full participation for life cycle management from the Unified Resource Manager

Where to find configuration information

Consult these z/VM publications for configuration information:

  • z/VM CP Planning and Administration (SC24-6178), Chapter 16
  • z/VM Systems Management Application Programming (SC24-6234)
  • Installations using DirMaint as your directory manager, please be sure to follow the steps in Appendix B of the z/VM DirMaint Tailoring and Administration Guide (SC24-6190) 'DirMaint Support for Systems Management APIs'
See the z/VM Library for these publication PDFs and information center.

Required changes to configuration of z/VM networking and System Management API servers

Configuration is required within z/VM networking support and the Systems Management API (SMAPI) servers as described in the aforementioned two publications. Pay special attention to updates required for user directories and within updated sample PROFILE EXECs.

  • Sample directories for all the SMAPI servers have updates required for the ensemble environment. Please ensure to incorporate these changes to the production SMAPI servers already in use.
  • An updated sample PROFILE EXEC (VSMREQIN SAMPPROF) has been supplied for the SMAPI request servers (VSMREQIN, VSMREQI6, VSMREQIM, VSMREQIU and VSMPROXY). And an updated sample PROFILE EXEC (VSMWORK1 SAMPPROF) has been supplied for the SMAPI worker servers (VSMGUARD, VSMWORK1, VSMWORK2, VSMWORK3, etc).

    To take advantage of the changes made to these two EXECS, the PROFILE EXEC on each SMAPI request and worker server MUST be updated with the changed code. If local modifications have not been made to either the PROFILE EXEC on the SMAPI request servers or the PROFILE EXEC on the SMAPI worker servers, the PROFILE EXEC on each request server's 191 A-disk can simply be replaced with the new VSMREQIN SAMPPROF file by copying VSMREQIN SAMPPROF as PROFILE EXEC. Also, the PROFILE EXEC on each worker server's 191 A-disk can simply be replaced with the new VSMWORK1 SAMPPROF file by copying VSMWORK1 SAMPPROF as PROFILE EXEC. If local modifications have been made to the PROFILE EXEC on either the SMAPI request or worker servers, those local modifications will need to be reworked.

Special notice for users of z/VM SSL servers

This is a warning of a disruptive change for those using the z/VM SSL servers: All z/VM customers who have configured the z/VM SSL server for use in a production environment take note.

APAR PK97437, included in this package, requires a disruptive system configuration change. For details, please read the z/VM Red Alert PDF on this topic.

Action is required BEFORE placing this service into production. ONLY customers running a production SSL server are affected by this requirement.

Warning on Cloning z/VM Images

The following warning is in regards to Cloning (Copying) or the IPLing in Multiple LPARs of a z/VM System that is Being Managed by the IBM zEnterprise Unified Resource Manager.

A z/VM system that is being managed by the IBM zEnterprise Unified Resource Manager must not be cloned (copied) or IPLed in multiple LPARs. Doing so will cause resource and communication conflicts which will result in communication failures and other unpredictable results within the ensemble complex. To safely clone a z/VM system or to IPL a z/VM image in different LPARs, you must do so only with a z/VM system that is not managed by the IBM zEnterprise Unified Resource Manager.

SMAPI Configuration Information

  • The default virtual storage size for the VSMPROXY and VSMREQIU user IDs is 128MB. Depending on the size and volume of the virtual server directories to be managed by the Unified Resource Manager, the default virtual storage size may need to be increased to 256MB or 512MB.
  • Ensure your backup policy includes all files in SFS directory: VMSYS:VSMWORK1.DATA
  • The minimum virtual storage size for the z/VM 6.2 LOHCOST and ZVMLXAPP user IDs must be 1GB when running with diver D15 on a zEnterprise EC12 or BC12.

ZVMLXAPP Directory Information

Please ensure to use EBCDIC code page 924 when updating the SCP data contained within the 'LOADDEV Directory Control Statement' of the ZVMLXAPP user directory. Square brackets must be coded in hex as x'AD' and x'BD'.

For example: 

404040D3 D6C1C4C4 C5E540E2 C3D7407D C07F9799 96868993
       L  O A D D  E V   S  C P   '  " " p r  o f i l
85A27F7A 40AD7FA9 E5D460D4
 e s " :   " " z  V M - M
C77FBD6B 7F9585A3 A6969992 C3819984 A27F7A40 ADC07FD6
 G " " ,  " n e t  w o r k  C a r d  s " :    " " " O
E2C17D6B 7D
 S A ' ,  '
7F7A407F 8193937F 6B7F9389 9592D396 838193C9 D7E5F67F
 " :   "  a l l "  , " l i  n k L o  c a l I  P V 6 "
7A4095A4 939340D0 BD40D07D
  :  n u  l l   "  "   " '

Installations with ensemble managed z/VM 6.1 images must ensure the LOADDEV user directory statement for ZVMLXAPP has been configured correctly before attempting a Concurrent Driver Upgrade from D86 to D93.

Process for Migrating Management of z/VM During a CPC Upgrade

Last Updated: March 1, 2013

The high-level steps that have to be executed when migrating 'ensemble-managed' z/VM systems during a CPC Upgrade or Replace can be found here. The instructions are applicable when migrating the Unified Resource Manager environment to an IBM zEnterprise 196, 114, or EC12.

Scripts which may be helpful to perform some of the tasks when migrating 'ensemble-managed' z/VM systems during a CPC Upgrade or Replace, or when migrating z/VM systems to non-managed, can be found here.

Extending zBX Connectivity Options to Layer-2

Customer experience with the IBM zEnterprise BladeCenter Extension (zBX) has led IBM to depart from its original requirement to exclusively support Layer-3 connectivity between the external data network and the intraensemble data network (IEDN) top-of-rack (TOR) switches in the zBX. With this change, a z/VM Virtual Switch can be used to provide a Layer 2 connection through the IEDN TOR switch using an OSD, thus extending IEDN connectivity to z/VM guests without requiring an OSX and without requiring z/VM to participate in an Ensemble.

A Redpaper is now available, illustrating a set of pre-tested configuration examples in support of both Layer-2 and Layer-3 connectivity. The Redpaper, IBM zEnterprise BladeCenter Extension: Network Connectivity Options (REDP-5036) includes a description of limitations and trade-offs when deploying Layer-2 versus Layer-3 connectivity.

Migrating from zManager to Native z/VM Management

The management of z/VM environments in zManager is now stabilized as part of the evolution of the IBM cloud strategy and adoption of OpenStack, as announced with z/VM 6.3. Accordingly, zManager does not provide systems management support for z/VM V6.3. Therefore, a package has been made available on the z/VM downloads web site. This package will help to consolidate a set of configuration commands generated by the z/VM SMAPI infrastructure in support of a System z Unified Resource Manager (zManager) management environment for z/VM. It is intended to support a migration from zManager to native z/VM management and should be used in conjunction with the documentation included with the package. The steps outlined in this package should be followed by any z/VM installation with guest access to the IEDN before migrating to z/VM 6.3.