In the MVS3.8J section; if you don’t play with that move along.<\/p>\n
The Oops was the number macro library I posted on the website in the mvs38j section yesterday was buggy; the main issue was there was a character 2 where there should have been a character 0, in assembler when addressing memory that’s a big oops. It works now :-).<\/p>\n
Now the main post, “where is the damn command code”.<\/p>\n
I see another few months (or years) of frustration ahead poking through the mvs3.8j source code for me.<\/p>\n
In z\/OS I believe you can use the MPF list to define new console commands; shame MPF doesn’t exist for mvs3.8j. <\/p>\n
All I want to do is add a new display command available at the console, ie : D xxx. <\/p>\n
So all I have to do is find the OS source code routine that handles console commands and insert\/zap the new command so it runs the command instead of saying invalid display command.<\/p>\n
All I have to do… I could search all the source PDS files to see what members contain the string “D” but that will not get me anywhere; I assume they all will.<\/p>\n
I guess todo next weekend will be to find what module issues the “command invalid” error message, and over the next few months try and identify every module that calls that one.<\/p>\n
Just because it irritates me.
\nThe command I wanted to emulate was simply “D SMF”. As a temporary workaround I am using “S DSMF” and have also discovered that CMD1 can return the same info with #CS. But why settle for workarounds.<\/p>\n
I may never find the OS code I need to modify; but it will keep me amused (or frustrated) for a few months anyway; until I find it or give up.<\/p>\n","protected":false},"excerpt":{"rendered":"
In the MVS3.8J section; if you don’t play with that move along. The Oops was the number macro library I posted on the website in the mvs38j section yesterday was buggy; the main issue was there was a character 2 … Continue reading