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
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
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
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
Because it was quick and dirty.
On 7/19/10 3:25 PM, Kris Buelens kris.buel...@gmail.com 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',
*
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
