HP-UX

Just checked, depending of how it was installed OnlineJFS may not show up with the given command, only when you try... If You have a GUI then as root try to launch sam:
sam & go to disks and filesystems, choose logical volumes, and click on lvol9 then in the top menubar choose Action-> Increase size and int the new window enter 500

What happens?

I know how to interrupt the Autoboot, and change the Mode Configuration from 'OEM' to 'USER'. I don't know what X11 is, or how to check it. And the third sentence you've got me completely lost

X11 is the unix graphical environment (windowing system...).
I have no idea what a 743 looks like only that it used similar boards and CPU as 712/715 that I had long ago... (but never migrated to 10.20 and left them in 9.5...)
So I should ask more: What kind of terminal are you working on...

Addendum:
What I wanted to know is can you execute the above, and if so what happend (did the system complain or did it do what was asked ( LVM extension...)

If you dont have GUI (yes pretty colors X system...) then we are to do all in command line from the console as root...

Okay I've tried to increase the size using sam, but it requires the services to be stopped, and the guys here will only allow me to try that on Monday.
Check out this link for the 743 board: Agilent / HP 743 - In Stock, We Buy Sell Repair, Price Quote

OK so you have seen what you can do then... If you had OnlineJFS it would have done the job...
Did you use sam in graphic mode or was it a vague txt gui?

I will explain a bit more:
You could have from command line as root extended the logical volume:

Code:

lvextend -L 500 /dev/vg00/lvol9

but to increase the filesystem's size you are to have nobody using it in order to unmount it, only problem is many things use /var especially all the logging systems in /var/adm so the only chance it to go single user ( boot and no filesystem mounted or just /...) mount what you need : / , /stand should be there, /usr for the commands but you cannot use sam anymore because sam uses /var...
Either you go savage way like init s
then

Code:

umount /var 
#or 
umount /dev/vg00/lvol9
# then extend the filesystem:
extendfs /dev/vg00/rlvol9   # Very important the "r" for raw device
# then lazy way to mount all:
mount -a
#now save the configuration:
vgcfgbackup vg00

I think I havent forgotten anything, but its difficult to imagine like the in front of a PC what you are to do on a box ..

Reboot or check behaviour :

Code:

init 2
init 3

Dont think you use 4 ( but I do... so check in /etc/inittab : the init default value...)

Looks good, will try it out. At which point would I specify the size 500? Or should I use

Code:

 
lvextend -L 500 /dev/vg00/lvol9

lvextend add physical extents (imagine pseudo disk blocks...) -L is to give the new size in MB...
here it can be done with sam but sam will complain because sam automatcally after will try to extend the filsystem which it can not...
Dont remember what happens after, mind you you can try... it wont brake anything...
It may show the logical volume size with the new size... in which case that part is done...
You can type the command now also...

you can give a new size to extendfs but I find it silly since what ever space you leave you cannot use it... only to extend the existing... not giving a size will make extendfs use all it finds... but remember umount first then usr raw device!
Good luck!

Looked at you link... Is this mounted in a rack? how is the disk connected? behind on the scsi 68pin? what is it used for?