Mainframe Performance Topics Podcast Episode 18 "What We Won't Have In Common Anymore"”… And then two come along at once.” Unlike Billboards or London Buses, only two here folks. So, we had ideas (and somehow time) to record two episodes almost back to back. So we did. But we have no chance of recording together for a while, sadly. Which is a bit of a shame as we have quite a lot we could talk about. Maybe some of mine will come out in other ways. After all it’s been quite a busy few weeks, bloggingwise. The really neglected medium has been screencasting, but I have an idea for something to do with video. ANd a little time on my hands. Anyhow, I hope you enjoy this episode. Episode 18 “What we won’t have in common anymore”Here are the show notes for Episode 18 “What we won’t have in common anymore”. The show is called this because our Mainframe topic is about some removals in common storage planned for the release after z/OS V2.3. Where we’ve beenThis episode was completed right after Episode 17, so we haven’t been anywhere special:
MainframeOur “Mainframe” topic discusses a future planned removal coming in the release after z/OS V2.3.
PerformanceMartin 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 purpose of bolding in the reporting is to alert the specialist and the customer to significant portions of a data set name. Previously, the only criterion was job name, which most notably show up in temporary data sets. Also previously, the code played formatting games with GDG generations - converting to relative generations - and listed all the generations seen in each running of the job. 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), 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. For example, in the “real life” example in the cited blog post (What’s In A Name? - Revisited) “PR” might very well mean production. and the low level qualifier “T1700” might or might not mean a time. These he considers tenuous parsings right now. TopicsOur podcast “Topics” topic is about two cheap and fun pieces of hardware Martin has been playing with: Raspberry Pi and Arduino
Where We’ll BeMartin will hopefully be in Copenhagen, Denmark visiting a customer. Marna will be at SHARE in Sacramento March 12-16 , and in Cairo IBM TechU April 15-17. On The BlogMartin referenced one blog post from the Performance topic: Contacting UsYou can reach Marna on Twitter as mwalle and by email. You can reach Martin on Twitter as martinpacker and by email. Or you can leave a comment below. |