What’s New
Mainframe - Looking at ages of fixes you haven't installed yet
Performance - Drawers, Of Course
Topics - Excel Love It Or Hate It
On the blog
So It Goes...
Episode 33 "These Boots Were Made"
What’s New
Mainframe -
Performance - Open Data Sets, Part 2
Topics - Messing With Digital Electronics
On the blog
So It Goes
This episode is about our After Show. (What is that?) Long show notes can be found here.
We have a special guest joining us for the performance topic, Scott Ballentine.
New news for CustomPac removal date, which has been extended past January 2022. The reason was to accommodate the desired Data Set Merge capability in z/OSMF which customers needed. For the new withdrawl date, it is planned to be announced in 2Q2022.
This topic was looking at some new functions that are only in z/OS V2.5.
There’s a lot of other stuff rolled back to V2.4
This discussion is a summary from a joint presentation on Usage Data and IFAUSAGE
Hope is developers will delight customers by using IFAUSAGE right, and customers will take advantage in the way shown with reporting examples.
This topics is about how to choose a language to use for which purpose. Different languages were discussed for different needs.
Overall lesson: Choose the language that respects the problem at hand.
Marna's blog is here
This episode is about how to be a better z/OS installation specialist, z/OS capture ratios, and a discussion on using Trello. We have a special guest joining us for the performance topic, Miroslava Barahona Rossi. Long show notes are found here .
Performance - Capture Ratio
So It Goes.
This episode is about several of the z/OS V2.5 new functions, which were recently announced, for both the Mainframe and Performance topics. Our Topics topic is on Martin's Open Source tool filterCSV. Full long show notes are here.
We have a guest for Performance: Nick Matsakis, z/OS Development, IBM Poughkeepsie.
Many of the enhancements you'll see in the z/OS V2.5 Preview were provided on earlier z/OS releases via Continuous Delivery PTFs. The APARs are provided in the announce.
If you use FTPS for your IBM software electonic delivery, a change is taking place on April 30, 2021. We strongly recommend you use HTTPS instead, but if you still want to use FTPS see IBM software electronic delivery change - take notice!
So it goes.
Martin was asked about which systems in a System Recovery Boost Speed Boost situation get their GCPs sped up to full speed.
So it goes.
Here are the show notes for Episode 26 "Sounding Board". The show is called this because it relates to our Topics topic, and because we recorded the episode partly in the Pougkeepsie recording studio where Martin sounded zen, and partly at home.
Here are the show notes for Episode 25 “Flit for Purpose”. The show is called this because it relates to our Topic, and also can be related to our Mainframe topic (as a pun for “Fit for Purpose”).
Here are the show notes for Episode 24 “Our Wurst Episode”. The show is called this because we both attended the IBM TechU in Berlin, Germany, and our Topics topic is our trip report.
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 23 “The Preview That We Do”. The show is called this because we talk about the newly previewed z/OS release, V2.4, in the Mainframe section. This is our 24th episode too! How convenient!
Biggest question one may have: what level of HW will z/OS V2.4 IPL on? z/OS V2.4 will run on zEC12/BC12 and higher.
Marna just installed two Nest thermostats, one in each zone (of a three-zone house). Is sharing data with Nest, and presumably whoever owns Nest currently (Google). Instrumentation benefit is having an app in which she can look at what is happening at home, when away, and control it too.
Martin doesn’t have a smart home thermostat, but does have a remote oil tank sensor to determine how much oil is left. This sensor feeds back into a device in the house, and connects to an app on his phone.
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 22 “Great App-spectations”. The show is called this because we talk about app expections in our Topics topic.
Performance: Paging Subsystem Design in an age of Virtual Flash
Performance: Paging Subsystem Design in an age of Virtual Flash
Topics: Anatomy Of A Great App
“App” here means “third party software” but we’ll say app for short
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 21 “Fits and Starts”. The show is called this because we talk about fitness devices, and the Performance topic that had work submitted after a one minute hiatus.
Post-IPL dynamic APF changes are reflected in SMF 90 Subtype 37. A lot of the function is in z/OS V2.2, with these fields in the SMF record:
Function:
Performance: An interesting Db2 DDF case
Central to Martin’s DDF work is some analysis code to process SMF 101 DB2 Accounting Trace.
A customer complained their DDF application stopped dead one evening – for 1 minute. It was an application serviced by a 3-way Datasharing group. The customer sent SMF 101 data from all 3 members for 3 hours around the stoppage, and for 3 hours the previous evening for a presumably “good behaviour”.
Martin plotted application statistics at a one second interval level. It showed a 40-second stoppage the evening they hadn’t complained, making the 1 minute threshold interesting as a number.
Martin “zoomed in” to a much shorter time range . When transactions started again they were elongated, and it that was due to the clustered arrivals in clearing the backlog.
The best theory is something external stopped transactions arriving.
Further he thought there could be “near misses” many times, just short of the 1 minute mark. After transactions started coming again there were spikes in transactions arriving every minute. The speculation is this might be the middle tier doing something on a 1 minute basis: Maybe retries of some sort?
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 20 "Two Is One And One Is None". The show is called this because our Topic topic is trying to figure out how to archive family photos and videos.
Mainframe: zFS Shrink, Only in z/OS V2.3
A system command for reducing the size of a zfs file system. Not be confused with compressing files within a file system. Found on zfsadm shrink. You specify a target size with the size option, gives _final_ size in KB, gets rounded to 8K boundary .
Reminder to use aggrgrow to increase the size of the filesystem. Monitor with SMF 92 subtype 50 for both grow and shrink events. Subtype 59 for # of I/Os and rate, but might occur too often, so use it wisely.
Performance: CPENABLE and HiperDispatch
I/O ends with an Interrupt. Needs to be handled by a processor, and needs to be handled in a timely way. Can be handled with Test Pending Interrupt (TPI). If test true this CP handles pending interrupt. If false then handled by normal interrupt handling. If many TPI successes suggests queue build up. Trade off between timeliness and processor efficiency
There’s a trade off between timeliness and processor efficiency. The CPENABLE parameter’s values manage this trade off. There are two values: if TPI% below first disable a processor from handling I/O interrupts, and if TPI% above second enable a processor to handle them.
Without Hiperdispatch, access to CPU is smeared across online processors, as the LPAR’s weight is evenly spread across its logical processors. Without Hiperdispatch it is recommended that CPENABLE be set to 0,0 which allows all processors to handle interrupts.
Overall this topic shows I/O Interrupt Enablement is a topic worthy of consideration to get timeliness vs efficiency right – particularly in the Hiperdispatch era. Also that the instrumentation really helps.
Talking about personal and family information: photos, audio, and video only. Not writings. Some serious questions:
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 19 "You've lost that syncing feeling". The show is called this because our Topic topic is about losing the Xmarks URL synchronization tool.
Mainframe
Our "Mainframe" topic discusses moving from V4 to V5 zFS, prompted by a user comment that had a very positive experience.
Performance
Our Performance topic is a survey of Licence-Related Instrumentation. Most shops are very conscious of software costs. Martin discusses the instrumentation portion.
Our podcast "Topics" topic is about Marna losing a handy and simple URL sync tool, XMarks. Xmarks used to let you save bookmarks between browsers with other cool capabilities. It was discontinued on May 1, 2018. XMarks was a plug-in to browser, logon, sync, and they were there! With multiple profiles.
Here are some https://techwiser.com/xmarks-alternatives/ ? :
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 future planned removal coming in the release after z/OS V2.3.
ZOSMIGV2R3_NEXT_VSM_USERKEYCOMM..Martin talked about what’s in a data set name and this topic is about getting insight by parsing data set names. His reporting code, which processes SMF 14 (OPEN for read) and SMF 15 (OPEN for write) records, bolds data set qualifiers (or segment names) if they match any of a bunch of criteria. Now, new criteria have been added to investigating data set names.
The new criteria are job step name, dates (in lots of formats), job step program name, “SORT” in the qualifier, and system SMFID.
While the code doesn't see "partner" job names (for instance, where one writes to a data set and the partner reads from the data set), those could be detected using the Life Of A Data Set (LOADS) technique, which we can talk about more one day.
And surely there will be more interesting finds in other customers' data set names. As they are stumbled upon the code can be enhanced to learn these new tricks - as Martin refactored it to make it easier to add new criteria.
Our podcast "Topics" topic is about two cheap and fun pieces of hardware Martin has been playing with: Raspberry Pi and Arduino.
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 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.