Re: New standard for networking help
Because it will give the wrong results! "split 1 after / ,/" will result in an error. "split 1 after string / ,/" is probably what you meant, but it really isn't what you want. "split 1 after string / ,/ | chop 8" will result in getting only the first two ids of a line that can contain up to 5 of them.. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Neale Ferguson Sent: Monday, July 19, 2010 1:28 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: New standard for networking help Because it was quick and dirty. On 7/19/10 3:25 PM, "Kris Buelens" wrote: Sorry to be nitpicking on this good idea: * why expose to errors by not using ADDRESS COMMAND? * why throwing away any userid starting with "VSM". Take this instead * 'PIPE CP Q NAMES', * '|StrNfind /VSM_-/', * '|SPLIT 1 after /,/', * '|CHOP 8', '|Stem name.'
Re: New standard for networking help
Because it was quick and dirty. On 7/19/10 3:25 PM, "Kris Buelens" wrote: Sorry to be nitpicking on this good idea: * why expose to errors by not using ADDRESS COMMAND? * why throwing away any userid starting with "VSM". Take this instead * 'PIPE CP Q NAMES', * '|StrNfind /VSM_-/', * '|SPLIT 1 after /,/', * '|CHOP 8', '|Stem name.'
Re: New standard for networking help
Sorry to be nitpicking on this good idea: - why expose to errors by not using ADDRESS COMMAND? - why throwing away any userid starting with "VSM". Take this instead 'PIPE CP Q NAMES', '|StrNfind /VSM_-/', '|SPLIT 1 after /,/', '|CHOP 8', '|Stem name.' 2010/7/19 Neale Ferguson > Here¹s an EXEC I use to do initial data gathering. I had updated it but > have > lost the latest copy. Anyway it¹s a start: > > /* */ > CP.1 = 'Q ALL' > CP.2 = 'Q CPLEVEL' > CP.3 = 'Q SRM' > CP.4 = 'Q ALLOC' > CP.5 = 'Q ALLOC PAGE' > CP.6 = 'Q ALLOC SPOOL' > CP.7 = 'Q ALLOC TDISK' > CP.8 = 'Q MDC' > CP.9 = 'Q VDISK' > CP.10 = 'Q FRAME' > CP.11 = 'IND' > CP.12 = 'IND Q' > CP.13 = 'Q VSWITCH ALL DETAILS' > CP.0 = 13 > > User.1 = 'Q SHARE' > User.2 = 'Q QUICKDSP' > User.3 = 'IND USER' > User.0 = 3 > > 'PIPE cms ERASE VM REPORT' > > 'PIPE (end ? name GETUSER)', > '| cp Q N', > '| split', > '| strip', > '| nfind VSM' ||, > '| spec 1.8 1', > '| strip', > '| stem Name.' > > do I_CP = 1 to CP.0 > 'PIPE (name GETCP end ?)', > '| cp' CP.I_CP, > '| literal' CP.I_CP, > '| append literal ' > '| >> VM REPORT A' > end > > do I_User = 1 to User.0 > do I_Name = 1 to Name.0 > 'PIPE (name GETUSER end ?)', > '| cp' User.I_User Name.I_Name, > '| literal' User.I_user Name.I_Name, > '| append literal ', > '| >> VM REPORT A' > end > end > > 'PIPE (name GETSTSI)', > '| cms EXEC STSI', > '| literal STSI', > '| append literal ', > '| >> VM REPORT A' > > exit > > On 7/19/10 10:19 AM, "David Boyes" wrote: > > >> The point was not the format, but that the information was organized, > >> complete, and easy to read. > >> > >> Alan Altmark > >> z/VM Development > >> IBM Endicott > > > > I think you missed the intent of the suggestion. Often we see that people > > don't know what information might be useful to solve a problem. If there > is > > some key information that makes solving problems easier, then having a > > guideline often helps people collect the right stuff to get the problem > solved > > the first time around. Others have suggested a automated way; that's > cool, but > > you have to define what you (IBM) need before you can automate anything. > Then > > the REXX and Pipe fiends will take over and find a way to collect it. 8-) > > > > Returning to the report in question, if that's the paradigm that you find > > useful, gut it of customer details, and let's see it. If nothing else, it > will > > make a good example of what kind of things need to be collected. > > > > -- db > > > -- Kris Buelens, IBM Belgium, VM customer support
Re: New standard for networking help
Here¹s an EXEC I use to do initial data gathering. I had updated it but have lost the latest copy. Anyway it¹s a start: /* */ CP.1 = 'Q ALL' CP.2 = 'Q CPLEVEL' CP.3 = 'Q SRM' CP.4 = 'Q ALLOC' CP.5 = 'Q ALLOC PAGE' CP.6 = 'Q ALLOC SPOOL' CP.7 = 'Q ALLOC TDISK' CP.8 = 'Q MDC' CP.9 = 'Q VDISK' CP.10 = 'Q FRAME' CP.11 = 'IND' CP.12 = 'IND Q' CP.13 = 'Q VSWITCH ALL DETAILS' CP.0 = 13 User.1 = 'Q SHARE' User.2 = 'Q QUICKDSP' User.3 = 'IND USER' User.0 = 3 'PIPE cms ERASE VM REPORT' 'PIPE (end ? name GETUSER)', '| cp Q N', '| split', '| strip', '| nfind VSM' ||, '| spec 1.8 1', '| strip', '| stem Name.' do I_CP = 1 to CP.0 'PIPE (name GETCP end ?)', '| cp' CP.I_CP, '| literal' CP.I_CP, '| append literal ' '| >> VM REPORT A' end do I_User = 1 to User.0 do I_Name = 1 to Name.0 'PIPE (name GETUSER end ?)', '| cp' User.I_User Name.I_Name, '| literal' User.I_user Name.I_Name, '| append literal ', '| >> VM REPORT A' end end 'PIPE (name GETSTSI)', '| cms EXEC STSI', '| literal STSI', '| append literal ', '| >> VM REPORT A' exit On 7/19/10 10:19 AM, "David Boyes" wrote: >> The point was not the format, but that the information was organized, >> complete, and easy to read. >> >> Alan Altmark >> z/VM Development >> IBM Endicott > > I think you missed the intent of the suggestion. Often we see that people > don't know what information might be useful to solve a problem. If there is > some key information that makes solving problems easier, then having a > guideline often helps people collect the right stuff to get the problem solved > the first time around. Others have suggested a automated way; that's cool, but > you have to define what you (IBM) need before you can automate anything. Then > the REXX and Pipe fiends will take over and find a way to collect it. 8-) > > Returning to the report in question, if that's the paradigm that you find > useful, gut it of customer details, and let's see it. If nothing else, it will > make a good example of what kind of things need to be collected. > > -- db >
Re: New standard for networking help
> The point was not the format, but that the information was organized, > complete, and easy to read. > > Alan Altmark > z/VM Development > IBM Endicott I think you missed the intent of the suggestion. Often we see that people don't know what information might be useful to solve a problem. If there is some key information that makes solving problems easier, then having a guideline often helps people collect the right stuff to get the problem solved the first time around. Others have suggested a automated way; that's cool, but you have to define what you (IBM) need before you can automate anything. Then the REXX and Pipe fiends will take over and find a way to collect it. 8-) Returning to the report in question, if that's the paradigm that you find useful, gut it of customer details, and let's see it. If nothing else, it will make a good example of what kind of things need to be collected. -- db
Perfkit: history data files
Hi, Perfkit, through panel 32, doesn't give the opportunity to use packed history files. Don't you think it could be interesting to allow perfkit t o have this function ? Alain Benveniste
