
Sign up to save your podcasts
Or


Our "Mainframe" topic discusses the addition of a new parmlib member for RACF, IRRPRMxx.
Martin talked about whether 2 LPARs (on 2 CECs) or 4 LPARs (on 2 CECs) is better.
Our podcast "Topics" topic is a follow up and a short discussion on what to do if your wifi isn't performing as you wish.
You can reach Marna on Twitter as mwalle and by email.
You can reach Martin on Twitter as martinpacker and by email and blogs at blog.
Our "Mainframe" topic discusses a new z/OS V2.3 function, Coupling Facility Encryption, with Mark Brooks,
Mark explained that CF Encryption means that the customer's data is encrypted by XCF
z/OS sysprog needs to set it up by:
List and Cache structures contain customer sensitive data, the XCF control
Tooling:
For more information, see the z/OS Setting Up a Sysplex.
Martin talked about MSU-related CPU fields for doing software pricing analysis. Some of these fields are used by SCRT in support of the new Mobile function. Most notably the fields cover:
Container Pricing is another pricing model, ....., and maybe another topic on that later.
The overall idea: Be aware of the new fields that you will be analysing. These fields are available at two levels:
Our podcast "Topics" topic is about adding chapter markers to the MP3 file for podcast apps. This
You can reach Marna on Twitter as mwalle and by email.
You can reach Martin on Twitter as martinpacker and by email and blogs at blog.
Here are the show notes for Episode 15 "Waits and Measures". The show is called this because our Performance topic is about LPAR weights, and because this episode was after a seasonal hiatus.
Our "Mainframe" topic discusses a small new function in z/OS UNIX V2.3: automatic unmount of the version "root" file system in a shared file system environment. Our guest was Barry Lichtenstein, the developer of the function, and he told us all about it:
Martin talked about Weights and Online Engines in LPARs, and Martin again looking at customer information.
Our podcast "Topics" topic was "Video Killed the Radio Star?" and about screencasting. Martin has been trying to post screencasts to YouTube. Here's one.
You can reach Marna on Twitter as mwalle and by email.
You can reach Martin on Twitter as martinpacker and by email and blogs at blog.
Here are the show notes for Episode 14 "In the Long Run". The show is called this because the episode ran much longer than usual, and it is of fitting length if you have a very long commute.
Our "Mainframe" topic is the first in a series of deep dives into z/OS V2.3. Part 1 is on z/OSMF Autostart.
This is the most important migration action in z/OS V2.3, and requires special consideration by every customer IPLing z/OS V2.3. Things that you'll need to consider are:
In our "Performance" topic Martin talked about two Parallel Sysplex items that he's been pondering extensively recently. He's been using RMF data (taken from SMF type 74 subtype 2 and 4).
This is the subject of a blog post: Some Parallel Sysplex Questions, Part 1 - Coupling Facility
This is the subject of another blog post: Some Parallel Sysplex Questions, Part 2 - XCF
Our "Topics" topic is subtitled "Podcast meets Podcast" with the newest mainframe podcast we know: Terminal Talk.
Frank De Gilio and Jeff Bisti are the hosts, and concentrate on a wider introductory perspective than our MPT podcast does.
We had great fun talking to Frank and Jeff; Martin left some of the laughs in the final edit.
You can reach Marna on Twitter as mwalle and by email.
You can reach Martin on Twitter as martinpacker and by email and blogs at blog.
Here are the show notes for Episode 13 "We'll Always Have Paris". The show is called this because both Marna and Martin reminisce about lovely times in the City of Light. Marna just got back from Paris with her son (the one that built his own gaming computer). They discuss what they like to do there.
Our "Mainframe" topic discusses what has been a popular item since more people have finished migrating to z/OS V2.2: GDGEs. Generation Data Group Extended (GDGEs) were introduced in z/OS V2.2, and should only be used after fully migrated to that release everywhere. "Old" GDGs allow >255 generations. GDGEs allow up to 999, but with a very different internal structure. GDGEs are externally usable transparently.
There is no straightforward conversion way in DFSMS. Steve Branch (alias name of "Mr. Catalog") and Marna had a six step JCL job to convert (which used IDCAMS ALTERs), and would work if the generations were SMS-managed, which was the initial use case. Several options were discussed.
Martin talked about a presentation he's been keeping updated, Even More Fun With DDF. The original presentation covered:
The updated presentation has an analysis is done using RMF and SMF 30, and SMF 101 DB2 Accounting Trace, using special code written by Martin.
You can reach Marna on Twitter as mwalle and by email.
You can reach Martin on Twitter as martinpacker and by email and blogs at blog.
Here are the show notes for Episode 12 "Baker's Dozen". The show is called "Baker's Dozen" because it is the thirteenth episode, after starting at Episode #0.
Our "Mainframe" topic discussed some fun small enhancements Marna has enjoyed from GRS.
Now, you can get all your "monitoring" into SMF records for both ENQ/DEQs and global generic queue scans. And you don't need to use the cumbersome ISGAUDIT anymore.
Martin talked about coupling facility structure performance, especially as it concerns DB2 lock and cache structures. Having a lot of structures isn't a problem, as long as you are looking at how "busy" the coupling facility is - both CPU- and memory-wise. Sorting in descending order the structures by a metric you want is an important and easy way to figure out which structures to pay attention to.
Balance this with the number of DB2 structures to manage - perhaps hundreds! Some advice was given as to what were the most important metrics to concentrate on.
Looking at "false contentions" and "XES contention" for lock structures is important, and may indicate that these structures need to be larger. Especially if the number of false contentions is high, relative to the lock structure requests. For cache structures, there are different metrics. You may have gotten a large number of structures because you are using DB2 data sharing. Look at names and types for a clue as to where they came from.
Our podcast "Topics" topic is how the audio for this podcast gets produced. If you are interested in audio editing, here are some items that recording this podcast has uncovered:
You can reach Marna on Twitter as mwalle and by email.
You can reach Martin on Twitter as martinpacker and by email and blogs at blog.
Here are the show notes for Episode 11 "XI-Ting". The show is called "XI-Ting" because, well, it is episode #11 and we had one shot at the Roman numeral to use and took it.
Our "Mainframe" topic was Marna's experience in trying out the z/OSMF Workflow Editor. The z/OSMF Workflow Editor is a new function in z/OSMF to create your own Workflow, or change an existing Workflow. The Workflow Editor is available on z/OSMF V2.1 in PTF UI43814 and on z/OSMF V2.2 in PTF UI42847.
Martin had a special guest for a conversation on zHyperLinks, Anna Shugol, IBM Mainframe Technical Specialist. Martin and Anna talked about a Statement of Direction that was released at the beginning of 2017.
This topic is very important because it is an innovative new IBM I/O and Storage technology to improve performance for DB2-centric applications. This is designed to provide dramatic improvements in I/O latency, and change the I/O paradigm. It complements existing technology, such as Hiper Performance FICON and using large DB2 buffer pools. zHyperlinks is intended to provide short distance (150 meters between the CEC and the storage unit) point-to-point improvements, which are expected to support 8GBs (gigabytes per second) with new protocols.
Our podcast "Topics" topic has been sub-titled "Some Assembly Required" ; Not the HLASM that mainframers might think that relates to, but actually something in the same vein. Marna's 14-yr old son who is interested in hardware has just built his first personal computer. Marna and Martin talk about how that first computer has a lot in common with a mainframe.
You can reach Marna on Twitter as mwalle and by email.
You can reach Martin on Twitter as martinpacker and by email and blogs at blog.
Here are the show notes for Episode 10 "234U". The show is called "234U" because:
Our "Mainframe" topic was a highlight of some of the newly previewed z/OS V2.3 enhancements! We will surely talk a lot about z/OS V2.3 in podcasts to come.
First, it is important to know that z/OS V2.3 will only IPL on an zEC12, zBC12 and higher. Prepare now if you need to.
Here's a brief list of the items planned for V2.3 (which is planned to GA on September 29, 2017)
Martin had an esteemed guest for our "Performance" topic, Elpida Tzortzatos, Distinquished Engineer from z/OS Development.
Martin and Elpida chatted about several important recent advances made in the area of z/OS memory management.
Review of UIC (Unreferenced Interval Count), which is how long in seconds
When more memory support was added (128G to 4TB) it was again reduced to not do any UIC updates, other metrics are used to judge contention instead.
RMF reports high impact, medium impact, and low impact frames evicted today, for a performance judgement.
Customers should be looking at average available memory, and minimum too. Make sure your AFQ can handle workload spikes and SVC dumps. Here is a WSC paper about that.
Large frames (1MB and 2GB page sizes): the Dynamic Address Translation (DAT) is on the critical performance path
Use the LFAREA specification for 1MB and 2GB frame usage.
You can reach Marna on Twitter as mwalle and by email.
You can reach Martin on Twitter as martinpacker and by email and blogs at blog.
Here are the show notes for Episode 9 "Back in Black". The show is called "Back in Black" because:
Continuous Delivery Follow-up Announcements
Our "Mainframe" topic was an interview with John Eells, z/OS System Test and lead on the Software Installation Strategy.
This topic is very important for z/OS system programmers to understand. IBM and ISVs have been working on a common install method, that handles both SMP/E and non-SMP/E. This would go beyond laying down code, and would eventually hook seamlessly into doing configuration tasks (via z/OSMF Workflow). It would even be able to package software, if you wanted to, and all delivered within the base z/OS operating system.
The common install method would be provided through z/OSMF's Software Management plug-in, so make sure you are setting up and becoming familiar with z/OSMF now. John and Marna also talked about some of the wishlist items we'd like to see in this solution.
Our "Performance" topic was about some about additions and changes to Martin's Parallel Sysplex Performance presentation that he's been presenting over the years. Somehow this presentation never seems to get any shorter.
This presentation has several sections: Structure-Level CPU, Matching CF and PR/SM views of CPU, Structure Duplexing, XCF traffic, CF link information, and CF Thin Interrupts.
The new parts and changes he has made in this presentation are:
and
Ahoy! In our "Topics" section we discuss voice-activated assistants that have been hitting the market for a while now.
Martin has a good amount of experience in Siri from Apple and Alexa (Amazon) Echo and Dot. A third one is Google Home.
Martin talks about the various pros and cons on each.
You can reach Marna on Twitter as mwalle and by email.
You can reach Martin on Twitter as martinpacker and by email and blogs at blog.
Here are the show notes for Episode 8 "Queue Me Up". The show is called "Queue Me Up" because:
We had some follow up:
Our "Mainframe" topic was a discussion on z/OS upgrade timing considerations.
z/OS R13 is now out of service since end of September 2016, five years of regular service support since GA. There are three consecutive releases of coexistence (with releases planned on coming out every two years).
This "discrepancy" between five years of service and and six years (three times two) of coexistence has been quite interesting and deserves some thought. Marna talks about some considerations, and it might be that the "n-2" model should be reconsidered to be a "n-1" model for some customers.
Our "Performance" topic was an extension of this blog post of Martin's: Right On Queue.
Martin talks about Coupling Facility list structures, and how they are different from lock and cache structures. He also covers some considerations and causes for how they might get filled up. (Think of the analogy of a pipe getting blocked as one case.)
Sizing is important and he uses SMF 74-4 and RMF Monitor III. A good rule of thumb is that your structure's maximum size should be in the range of 50% to 100% of the current size. More than double puts you at risk of having a list structure full of control blocks and little data. You also need to monitor how much of the current size is actually in use.
In our "Topics" section we discussed a travel app called Waze. It's a crowd-sourcing app you can use to get real-time travel estimates and routes. It also alerts you about such items as accidents, debris, police cars, etc, which other users have reported. This app is particularly useful even if you have to put up with a very small amount of advertising.
You can reach Marna on Twitter as mwalle and by email.
You can reach Martin on Twitter as martinpacker and by email and blogs at blog.
From the publisher's feed