Hello.  In the past I have queried the list for eof sizes of hpuid files and command.pub.sys files.  We are trying to find out how much our udc files and command files are effecting the performance on our two hp3000's.  After talking to the folks at Beechglen, they had me checking the hpcpumsecs variable after logging on.

I would like to ask folks on the list what their hpcpumsecs variable are set at, right after logging on, so assess how our HP's are in regards to everyone else.

Feel free to offer any other idea for assessing how udc files and command files add overhead to the system.  Our environment is such that over the years, folks have created a bunch of command files and udc's at the system level that have become so engrained that the users actually think they are operating system commands.  I know from past CRUG (Chicago Regional User Group) meetings that udc/command files can be your friend, and can also be abused and add lots of overhead to the system.  We are a very heavy batch environment, and also over 1000 accounts.  During the day, an analyst may need to do a hello command up to 200 times.  Since we just implemented security, it's like they are now counting key strokes.  I know you can go into mpex and do a chlogon to a different group and account without being asked a password again.  We have not assessed how these other command files would work given this method.  We will probably have to assess it at some time, I'm sure we will be asked if there are ways to not have to enter the password so much.  The savvy uses have all ready figured out how to map it to a key combination with minisoft, so if you know their key map, so much for security...

Just wanted to thank you all for your helpful information in the past, and would like to know the values of your hpcpumsecs variable, and any other helpful tidbits for assessing udc/command file good/bad performance.

Thanks.

Mike Baker

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *