(Originally posted 2017-07-07.)
Boy has this one been a “slow train coming” but I’m glad it’s out now. And it was fun making it. Especially the piece with Frank and Jeff.
It’s a long listen; As always I’m comfortable with long podcast episodes.
Episode 14 “In The Long Run” Show Notes
Here are the show notes for Episode 14 “In the Long Run”. The show is called this because the episode ran longer than usual, and it is of fitting length if you have a very long commute.
Martin has two new blog posts about DDF (DB2’s Distributed Data Facility), following up on Episode 13 where he talked about recent DDF analysis enhancements:
(Follow Up is of course an invention of John Siracusa.) 🙂
Where we’ve been
Martin has been to London (to the UK GSE zCMPA User Group) to present his ever-updated DDF presentation, and had more fun with it.
Marna has been to the Systems University in Orlando, Florida (May 22, 2017 week).
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:
Whether to start z/OSMF or not. (Starting is the default). You control this via IZUPRMxx parmlib members (which in new news can be shared via PI82068).
If you don’t start z/OSMF and have its functions available to system(s), then you not be able to use certain functions (notably in z/OS V2.3: JES3 Notification).
If you don’t want to start z/OSMF on a certain system, you can connect to another z/OSMF system in the same sysplex, and that requires specification on which group that would be.
The number of z/OSMF servers in a sysplex hasn’t changed, still as it was before V2.3.
z/OSMF server starting on an LPAR with good zIIP capacity, and memory (minimum of 4GB) is a starting consideration.
Strong recommendation: start z/OSMF now on your V2.1 or V2.2 system so that there are fewer work items to do (a couple of security profiles, new procs, parmlib updates only).
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
Resources: CPU, memory, and path
Structures: their role to applications, and how responsiveness responds to work load is interesting
This is the subject of another blog post: Some Parallel Sysplex Questions, Part 2 – XCF
Resources: Paths, buffers, and transport groups
Groups: again, knowing the application types, with the theme of managing traffic down when possible
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.
Terminal Talk (TT) has enviable technology for recording, and came about from Frank and Jeff taking long car rides to Pennsylvania.
Planning for the TT podcast consists mostly on engaging guests, and not necessarily following an outline.
Length is a big consideration: TT is intended to be of a work-commute length.
Editing is done with Audacity, just like our MPT podcast. TT records mono. MPT does stereo. Martin uses the Audacity waveform visualisation when editing; Hence the terms “um fish” and “so so birds”. 🙂
We had great fun talking to Frank and Jeff; Martin left some of the laughs in the final edit. And we’re sure a lot of you will enjoy Terminal Talk, having listened to all their episodes so far.
Marna and Martin discussed three customer requirements:
Where We’ll Be
Marna will be at SHARE in Providence, RI, 7–11 August 2017 and [IBM Systems Symposium, 15–17 August 2017 in Melbourne, AU)[https://www.regonline.co.uk/registration/Checkin.aspx?EventID=1939263]
Martin will be going nowhere for a while.
On The Blog
Martin has published six blog posts recently. The two not already mentioned are:
Marna has not blogged since our last podcast episode.
Or you can leave a comment below.