{big snip}...

With *no* tools at your disposal your options are limited, other than
the free Glance trial mentioned by Bill Lancaster.  But...

A very general indicator is do issue a ":showq;active" and count the
number of processes in the ready queue.  This is a fairly reliable
indicator of CPU demand.  Similarly the posix shell 'w' command gives
you a 'load avg' value, which is the number of processes in the ready
queue.

If you have lots of scroll memory (for 100 users), :showproc;job=@ can
give some indication.  Bad signs are MMBLK states, BLKCB states, or
processes with an inordinately high value of CPU.

Watch the access LEDs on your disks.  If your system volume set drives
are getting lots of activity, combined with MMBLK (sp?) processes above,
you might be memory starved.  If you have no private volumes, this
observation will be skewed.

Going to network connections has a varying effect.  Using NS/VT will
increase memory demands (more processes, more virtual memory) while
going telnet increases CPU demands.

It is very difficult to advise you without *any* measurement tools.

Best of luck...

Jeff Kell <[log in to unmask]>