I just wanted to share a little z/OSMF tip with respect to a new feature that I started exploiting frequently with z/OS V2R1. “Resource Monitoring task can link automatically to the Workload Management task for additional data. Thus, when the Resource Monitoring task shows performance data related to a WLM workload, service class, or report class, you can view the corresponding WLM service definition in your z/OSMF session.” For instance I was just taking a look at our Performance Index (PI) numbers in z/OSMF Resource Monitoring... [More]

Following is a quick Capacity Provisioning (CP) for z/OS V2R1 tip but first I should say that I have been very impressed with CP for z/OS. They have been delivering valuable new functionality every z/OS release based on customer feedback and requirements. I will be talking about a couple more in other blog entries. Specifically their support of manually activated capacity as well as defined & group capacity limits – aka Soft or WLM capping. CP for z/OS V2R1 allows the end users to activate/deactivate IFLs, SAPs and ICFs that are... [More]

Tags:  oocod cpm

Prior to z/OS V2R1 Capacity Provisioning (CP) for z/OS component would not manage manually activated On/Off Capacity on Demand (CoD) resources. For instance, let’s say you set up a CP for z/OS policy to manage 100 MSU based on workload conditions. At some point you become aware that soon you are going to require 60 additional MSU to support a peak condition and decide to manually activate those 60 MSU rather than wait for CP for z/OS to recognize the need and activate them for you. CP for z/OS then would only manage the remaining 40 MSU... [More]

Tags:  oocod cpm v2r1

Capacity Provisioning (CP) for z/OS V2R1 can manage Defined Capacity and Group Capacity limits. It can automatically adjust them based on a predefined policy as well as provides the end user with commands to make the adjustments from a z/OS console rather than the Support Element (SE). In this blog entry we will share with you our experiences with this new enhancement. From here on we will refer to Defined Capacity as DC and Group Capacity as GC. Specifically we will talk about: High level introduction to DC and GC concepts Steps we took to... [More]

Tags:  v2r1 softcap wlm oocod groupcapacity definedcapacity cp

zFS Configuration Option: QUIESCE_MESSAGE_DELAY   Message IOEZ00581E appears on the zFS-owning systems that contain at least one zFS aggregate that is quiesced. There is a time delay between when the aggregate is quiesced and when the message appears. Normally, this time delay is about 30 seconds.  When there are no quiesced zFS aggregates on the system, this message is DOMed (removed from the console).  There is a delay between when the last aggregate is unquiesced and when the message is DOMed. This message is handled by a... [More]

Tags:  zfs z/os v2r1

zFS File System Quiesce Execution and Display Experience   The following exercises were performed with zFS PTF UA71136 (APAR OA43249) installed on z/OS V2R1 systems. You can query the setting of the QUIESCE_MESSAGE_DELAY configuration option with the ‘F ZFS,QUERY,SETTINGS’ console command. Here is an excerpt from the display on our Z2 system, where the file systems were mounted.   RO Z2,F ZFS,QUERY,SETTINGS ... QUIESCE_MESSAGE_DELA  30      Seconds to wait after quiesce before IOEZ00581E... [More]

Tags:  v2r1 z/os zfs

zFS File System Quiesce Execution and Display   Prior to z/OS V2R1, the z/OS UNIX displays did not indicate whether a zFS file system was quiesced.   In z/OS V2R1, when a zFS file system is quiesced and it is an RWSHARE or READ-ONLY file system, zFS will handle the quiesce.  If a zFS file system is quiesced and it is a NORWSHARE file system, zFS will inform z/OS UNIX that the file system should be quiesced and z/OS UNIX will handle all aspects of the quiesce including suspending file requests.  If zFS performed the quiesce,... [More]

Tags:  z/os zfs v2r1

z/OS UNIX Temporary File System (TFS) Enhancements   In z/OS V2R1 the Temporary File System (TFS) was enhanced to provide a warning for possible file system full situations, and allow for the TFS to be extended. To assist with early warning of full TFS file systems, TFS provides a FSFULL parameter ( -fsfull ) to indicate a threshold and increments as to when a message ( BPXTF009E , BPXTF010E , BPXTF011I ) is issued concerning the percentage of used space.  This will provide a similar capability as HFS and zFS with their FSFULL mount... [More]

Tags:  unix v2r1 tfs z/os

z/OS UNIX Temporary File System (TFS) Enhancements Experience The following are some tests we performed in our z/OS V2R1 environment.  Our tfs_proc_name is TFS. We defined the TFS PFS in our parmlib member as follows.  Notice that we have the TFS as a colony to allow for modification capability and set the –FSFULL, -ea, and –em parameters.  This sets the global settings and defaults on the system.       SYS1.PARMLIB(BPXPRM00): … FILESYSTYPE TYPE(TFS)... [More]

z/OS UNIX Kernel Storage Monitor and Display   In z/OS V2R1 support was added to monitor usage of kernel storage used for stacks and available below the bar kernel private storage. This involves Health Checks ( USS_KERNEL_PVTSTG_THRESHOLD , USS_KERNEL_PVTSTG_THRESHOLD ) to determine when a shortage of either occurs and the issuing of messages ( BPXH071E , BPXH072E ) to alert operations of the shortage.  There is a new DISPLAY OMVS console command option ( STORAGE|ST and STORAGE|ST,RESET ) to display a list of processes using more than... [More]

Tags:  kernelstoragemonitordispl... v2r1 z/os unix

RACF V2R1 new feature testing. This topic describes our experiences with a few of the changes that were introduced to our RACF environment with V2R1. RACF Protection of job classes . We tested the ability to protect the use of job classes through RACF profiles.  This ability is new with RACF V2R1, although in previous releases you could protect job classes with the use of exits.  We tested with a job class that was 8 characters long since this is also new with the z/OS V2R1 platform.  This test was performed on both a JES2 and a... [More]

Tags:  racf zpet v2r1

zFS Version 1.5 Aggregate and Extended (v5) Directory Experience Part4 Convert a Version 1.4 Aggregate and a v4 Directory Using zfsadm convert -path We used the zfsadm convert –path on a mounted version 1.4 aggregate to convert a directory to an extended (v5) directory.  This converted the aggregate to a version 1.5 aggregate and converted the directory indicated in the -path to an extended (v5) directory. We mounted a version 1.4 aggregate. $ mount -t zfs -f OMVSSPN.PET3.ZFS.FS /pet3 Using zfsadm fileinfo , we see that the directory... [More]

Tags:  version1.5 lcst/e zpet z/os v5 zfs v2r1

  zFS Version 1.5 Aggregate and Extended (v5) Directory Experience Part3 Convert a zFS Version 1.5 Aggregate to a Version 1.4 Aggregate You can convert a version 1.5 aggregate to a version 1.4 aggregate by using the IOEFSUTL utility.  Since, the aggregate will be a version 1.4 and can not contain extended (v5) directories, all extended (v5) directories will be converted to v4 directories.  The file system needs to be unmounted and the convert needs to be executed on a z/OS V2R1 system .   Note: The zFS IOEFSUTL utility with... [More]

Tags:  zpet version1.5 lcst/e z/os v2r1 v5 zfs

zFS Version 1.5 Aggregate and Extended (v5) Directory  Experience Part2 Convert a zFS Version 1.4 Aggregate to a Version 1.5 Aggregate You can convert a zFS version 1.4 aggregate to a version 1.5 aggregate with the online zfsadm convert command on z/OS V2R1.  The aggregate can contain v4 and extended (v5) directories.  All new directories will be extended (v5) directories.  The v4 directories can be converted later using various convert commands and parameters .   Note: Online conversion of an aggregate to version 1.5... [More]

zFS Version 1.5 Aggregate and Extended (v5) Directory Experience Part1    Convert a Mounted zFS Version 1.4 Aggregate to a zFS Version 1.5 Aggregate Using the –converttov5 Configuration Option We determined that the OMVSSPN.VER15.ZFS file system was a candidate for extended (v5) directories.   Using the method of having the zFS configuration –converttov5 option ON to update the attributes of a mounted file system, we gave the file system the converttov5 parameter.  We ensured that no other file systems were... [More]

Tags:  zpet zfs v5 v2r1 z/os lcst/e version1.5

zFS Version 1.5 Aggregate and Extended (v5) Directory Beginning in z/OS V2R1, zFS supports a new version aggregate, the version 1.5 aggregate .  Version 1.5 aggregates support extended (v5) directories .  Extended (v5) directories provide the following benefits:   They can support larger directories with performance. They store names more efficiently than v4 directories. When names are removed from extended (v5) directories, the space is reclaimed, when possible, unlike v4 directories where space is not reclaimed until the... [More]

Tags:  lcst/e z/os v2r1 v5 zfs zpet version1.5

With z/OS V2R1, RMF Monitor III Data Gatherer (RMFGAT) can partially offload work to zIIP processors. zIIP exploitation helps customers reduce their total cost of ownership (TCO).   The RMFGAT zIIP exploitation is ON by default and can be turned OFF/ON dynamically by means of the ZIIPUSE/NOZIIPUSE parameter. F RMF,F III,ZIIPUSE                 switches ON zIIP Usage F RMF,F III,NOZIIPUSE            switches... [More]

Tags:  rmf ziip

The objective of this is to exploit IMS CQS and log stream primary storage usage/management/notification enhancements to reduce log stream exploiter outages from primary storage full conditions. This blog will also provide more detailed data on log stream offload processing to assist customers in this tuning.   The system logger and IMS CQS (Common Queue Services) teams provided tuning advice to support an IMS CQS client to facilitate the use of a very large CF list structure (order of magnitude in gigabytes vs. megabytes). The use of a... [More]

z/OS UNIX Provide JWT support for shell environment In z/OS V2R1, z/OS UNIX provides a new parmlib setting and a new environment variable that installations and applications can use to set a time out value for when inactive terminal users will be logged off.   The new BPXPRMxx statement is called PWT. The options on this statement provide the ability to indicate if the SMFPRMxx JWT/TWT/SWT value is to be honored or not. The parmlib option will affect all processes in waits for tty reads/writes. The new environment variable is a kernel... [More]

Tags:  zpet timeout jwt v2r1 shell lcst/e