Hidden Value details commands and procedures in MPE that can improve your productivity with HP 3000 systems. Send your tips to email@example.com
Have you done a
reload or restore of the SYS account? It could be something below the
hpstage directory that is causing the problem. Quick solution: Try
issuing the UNINSTALL followed by INITIALIZE. Longer solution: Store
off /SYS/hpstage and everything under it, then restore with the
The last time you
rebooted you did START RECOVERY. (You can verify this with the MISC
command in SYSINFO. PRVXL.TELESUP.) That is why your configuration
file is in BOOTUP.SYS instead of CONFIG.SYS. If the current
configuration is good then go into SYSGEN and type KEEP
CONFIG.SYS. Then you can modify the IO section. Keep the file and
reboot using START NORECOVERY. This will automatically invoke the
default configuration group CONFIG.SYS.
It is a bad idea in
general to run for any length of time under START RECOVERY mode.
These days, the only reason to use START RECOVERY is if you want to
recover scheduled or waiting jobs. Before the native mode spooler,
you had to do a START RECOVERY or else you would lose spoolfiles, but
that is no longer the case.
Try the free utility
CHKTAPE from Allegro? Its at www.allegro.com/software/hp3000/stuff/CHKTAPE.txt.
Use chktape devicenumber. ChkTape must reside in a group.account with
It is possible to
control the starting LDEV for NS-VT and telnet by configuring all
LDEVs up to your selected starting point with nailed LDEVs (bogus DTC
LDEVs as an example) or other configured sysgen devices. It is then
possible to limit the number of inbound NS-VT connections with the
Copyright The 3000 NewsWire. All rights reserved.