#zos

  • martinpacker: ... Main issue: The code assumed only pair of sections. Not sure what we gain by going further but I'm sure it'll be fun. #zOS R10 forces me

  • martinpacker: @plhatfield56 #zOS Technical conference only - like @mwalle and @tetterrogers do.

  • martinpacker: @mwalle Hello Marna! Glad @meraltemel persuaded you to dip your toe in the water. :-) Folks, Marna's a friend from #zOS Development.

  • martinpacker: Wondering if a shift of job emphasis to encompass #zOS / #mainframe Asset Management mightn't use my talents well. This IN ADDITION to Perf.

  • martinpacker: According to #IBMMAIN you can put a hyphen in a #zOS data set name. I suspect, though, there is potential for unpleasantness when you do ...

  • martinpacker: @plhatfield56 Which #zOS R.10 enhancements take your fancy then?

  • martinpacker: Looking up how to do commenting in #zOS #IEBCOPY. And will probably take "the scenic route" to see if it buys me unforeseen capabilities.

  • martinpacker: @martinpacker I've said before #mainframes should report (their nice LOW) power usage via #RMF (the measurement component of #zOS).

  • martinpacker: Fiddling with my #LPAR charts: Now each one shows which LPAR *THIS* #zOS system is. Often LPAR names and #zOS SMFIDs aren't the same.

  • martinpacker: @meraltemel I'd say yes but the effect may be very minor: As these LPARs won't load anything other than a Wait State PSW. Unlike #zOS idling

  • martinpacker: Recommendation to people with little budget for #zOS performance tools: Try the #RMF Spreadsheet Reporter.

  • martinpacker: The dreaded "my processor lost some cooling and so slowed down and we didn't notice" thread has recurred on #IBMMAIN. Note sent to #zOS Devt

  • martinpacker: @tdotrob Welcome to the UK! BTW does "Websphere Security" in your title relate at all to #RACF on #zOS?

  • martinpacker: A nice (tho' I say so myself) fixup for my #CouplingFacility charts is the path types connecting this #zOS image to that CF appear as a note

  • martinpacker: Nanotut: Pre #zOS "Changed" #CouplingFacility reqs were caused by subchannel shortages. Mechanism still exists.

  • martinpacker: Back to the discussion on dumping and memory on #zOS with my current major customer. Similar to another big cust in Jan / Feb of this year.

  • MichaelDag: @martinpacker Noted!!! Thanks, do you know about the #REXX Compiler for #zOS too?

  • martinpacker: @MichaelDag OK. If you need friendly faces for #MQ and #zOS you'll find them here.

  • martinpacker: #Nanotut: Mainframes manage engines in diff't pools - 5 at present. Also #zOS has 3 engine types doing different things. Types map 2 pools

  • martinpacker: In #RMF #SMF Type 70 the #zOS engine type is different in general from the #PR/SM Pool Number. Just designed a fix to expose Pool Number.