Page 3  


Configuring 9x7 Systems to use a Remote Console
(continued from previous page)

Which Verison of MPE is Right?
(continued from page 1)
Current bit rate is 2400 bits/sec. Select the new bit rate:

<enter> (9600)

Current Protocol is Bell. Select the new protocol:

1 <enter> (North America uses BELL)

New system identification: HP957SX <enter> (Your system
model number)

CM> ER <enter>

Remote CS command: Disabled, Select the new setting
(E=enabled, D=disabled): E <enter>

Current mode: Multiple, Select the new setting (S=single,
M=multiple): M <enter>

New password: TEST <enter> (Always enable a password to
avoid any annoying beeping)

CM> UR <enter>

Remote Console answer mode is now unlocked. This function
enables DTR to the modem so the modem will autoanswer.

That’s it! To disable the remote console to allow session mode,
use the ‘DR’ command. To lockout the modem but keep it in
remote console mode use ‘LR’ lock remote command. To return
to the system prompt, type: CM> CO <enter>

It is strongly recommended you use the same Baud Rate for
both Remote Console and Session modes.
6.0 – Includes Y2K and additional functionality (such as 9GB disk support) that had been available as patches for 5.5. It’s the last release that supports the older models of the PA-RISC family. HP support for 6.0 has ended.

6.5 - Does not support the older PA-RISC 3000s, the HP-IB interface, or HP FiberLink disk interface. 6.5 (and later) releases will be “supported” by HP through the end of 2006. 6.5 Introduced support for “large” files (>4GB), User-Defined Job Queues, and increased many maximum configuration limits. Users with limited CPU and Memory may see a small performance decrease between 6.0 and 6.5 and later releases. 6.5 is the last release that will run on the 9x7 series 3000s.

7.0 – MPE/iX 7.0 was initially the “N-Class” release. Major functionality was missing before the Express 1 update. 7.0 does not support the 9x7 server family.

7.5 – MPE/iX 7.5 is the current (and last) major MPE/iX release. Much of the functionality included in 7.5 is for the high-end N-Class (and A-Class) systems. Support for the PA-8700 3000’s and Native Fiber Channel disk interfaces is included. Most systems that run 7.5 do so because of hardware requirements.

Will there be another release? It’s highly unlikely. Any new functionality is likely to be released via patches to the remaining supported MPE versions.

Performing an MPE/iX operating system upgrade is generally painless, whether done with or without help. Also be sure to check with all your third party software providers about compatibility before considering an upgrade.

Resource 3000 offers operating System support for all of the above versions of MPE/iX, regardless of their support status by HP. Contact us for more information.


The Problem with Big Disk

MPE/iX was designed to be a finely-tuned transaction processing machine. But, as good as it is, MPE isn’t perfect. With the availability of bigger, cheaper disks, most people don’t think much about disk fragmentation or contiguous disk space until it’s too late. The system may mysteriously fail, or, users start complaining about response time, or you can’t update the OS. Time to look at disk fragmentation.

There are four types of fragmentation found on HP 3000 MPE/iX systems: file fragmentation, disk fragmentation, system fragmentation and database internal fragmentation. This article focuses on disk fragmentation, which occurs when the free space on a disk drive is spread throughout the disk in many small pieces. This can have performance as well as management implications.

OS updates and the MPE Transaction Manager (XM) require quite a bit of contiguous space on LDEV 1. Although you may have plenty of disk space available, it may not be contiguous.

What can you do about fragmentation?

Fragmentation normally isn’t harmful, but as mentioned, it can slow your system and actually cause serious problems if contiguous free space

on LDEV 1 gets dangerously low. First, purge all your old log files. They accumulate like dust in the corner. Then, reduce the fragmentation. The easiest way to do this is with a utility, such as De-Frag/X, designed specifically to reduce disk and file fragmentation. In case you don’t have one of these utilities (and why not?), you can use the CONTIGVOL command of VOLUTIL, first introduced with MPE/iX 5.0.

CONTIGVOL is designed to resolve the problem of disk fragmentation, and does nothing for file fragmentation, system fragmentation, or database fragmentation. You use the command to create contiguous space on LDEV 1.
However, you may run into a problem: If you run CONTIGVOL and receive an error message “Warning: Contigvol - Inverse Extent Tbl Full, Internal resource limit,” it simply means that you’ve run into a minor inconvenience. CONTIGVOL only handles 40,000 extents at a time. You can run it as often as necessary to get
your contiguous space. The message is simply a warning that an internal table is full.

The bottom line: MPE is great, but not perfect. You still have to manage your disks, regardless of their apparent infinite capacity.
   Resource 3000 - NEWS - Issue No. 2 - MAY 2005