Innsbruck z/OS and Storage Conference - Day 1
MartinPacker 11000094DH Comment (1) Visits (3903)
Here's a summary of MY first day at the z/OS and Storage conference in Innsbruck. I'll be reporting from a PERSONAL point of view (using Notepad to capture thoughts). Hopefully some of these items will be of some use to you. I admit this is all a bit raw.
Already I've run into several UK customers and a lot of developer friends (and fellow presenters I've known a long time).
Session Z01: What's New In z/OS? Speaker: Garry Geokdjian
This was an introductory session to z/OS R.6. It also touched on R.7. As a performance person it's hard to keep up with the more minor details of each release. So this was a good chance to fill in the gaps.
Garry previewed the "New Face of z/OS" initiative which proposes a Web User Interface which is consistent across
tasks. These tasks would be automated and simplified tasks and would have integrated user assistance.
z/OS Load Balancing Advisor is a new feature in R.7 Improved Dynamic Virtual IP Addressing in R.4 and R.6. Can
rename LPAR without IPL in R.6 (z890 and z990 required.)
There is a PTF to R.4 to change CPU speed of z800 and z890 without an IPL.
In R.6 you can reserve LPARs with a "*" for the LPAR Name.
A 32-way z/OS image previewed as a PTF for z/OS R.6 for later in 2005.
64-bit Java 2 1.4.1 was made available September 2004.
IBM Communication Controller for Linux (CCL) for zSeries 1.1 emulates a 3745 Comms Controller, so you can run ( most
of) NCP under Linux. Already available - but this is an announcement I'd not spotted.
Initial z/OS support for Enterprise Workload Manager (EWLM) was made available December 2004. This today provides
reporting of business performance objectives and breaks down response times across the whole environment. In the
future it will provide workload balancing recommendations.
From R.7 the root File System will be zFS.
z/OS Load Balancing Advisor will use SASP protocol to provide routing recommendations to a SASP-compliant router to help with load balancing.
IBM HealthChecker for z/OS and Sysplex has been very successful and will be incorporated into R.7. Additional checks will be added.
XRC+ makes System Logger more attractive in GDPS environment.
Statement of Direction for The VSAM Connector for z/OS, a JDBC connector for VSAM.
Session TSS06: VSAM RLS Overview, Speaker: Terri Menendez
With RLS, SHAREOPTIONS(2,x) allow some level of sharing between RLS (can read/write) and non-RLS (for read).
SMSVSAM address space is RLS. Control blocks and buffer pools are in a dataspace.
To use RLS you have to have a CF even for single-system operation. RLS uses cache structures and a lock structure
(IGWLOCK00). The default lock structure sizing is generous. The cache structures might be a little small. SMS assigns data sets to Cache Sets, each of which is associated with a CF cache structure.
RLS Development has put a very great deal of effort into Reliability Availability and Serviceability (RAS). Much of
this has come out through APARs.
RLS does lock detection and can supply a bad return code to the caller in the event of a deadlock.
D SMS,SMSVSAM is a useful operator command for displaying the status of the RLS infrastructure.
Catalog calls SMSVSAM to delete a data set, because there might be retained locks associated with the data set. Likewise DFSMSdss.
Automation between CICS and VSAM RLS. eg F cicsname,CEMT SET DSN(
sharing the data set. (It was news to me you could do a CEMT by modiFying the CICS address space.)
Session G04 zSeries Processors Migration Considerations, Speaker: Parwez Hamid
ESCON channels cannot be spanned across LCSS's. FICON can but needs the same CHPID for each LCSS.
z990 I/O Configuration "Plan Ahead" can be used to install additional cages when installing the z990 - to avoid
outages when upgrading the I/O configuration later on.
I'm reminded that the Bimodal Accomodation Offering is not available for z/OS R.5 and subsequent releases.
z/OS R.4 z990 Exploitation code supports more than 1 LCSS, more than 15 LPARs and 2-digit LPAR IDs. WSC Flash 10236
Parwez reminded us of the the good reasons why LSPR comparisons between eg 9672 and z990/z890 are not directly
z990 GA3 allows conversions of engines to Unassigned and between types.
Adding another z990 book (perhaps for more memory) and POR'ing is quite likely to cause PR/SM to re-evaluate which
physical engines to use and hence it's pretty likely some engines on the new book will be used.
z990 GA3 is required for dynamic LPAR renaming (mentioned above).
If going to CF Level 14 use the CFSIZER tool to determine if you need more CF storage - it's quite likely you
Session ZP03: Much Ado About CPU, Speaker: Me :-)
I feel I rushed this a little - but it WAS the first time I'd delivered the material. There were a couple of
questions. One related to not being able to treat multiple clusters as one. I think the customer has multiple
parallel sysplexes which touched the one machine and therefore more than one cluster. IRD will not manage between
clusters. The other question was a comment that for bureaux the need is to limit an LPAR's CPU consumption. My only
answer to that is that LPAR design needs to take that carefully into account.