Make that 3000 release a printer grip
Two very tough days for 3000 customers

Wayback: Security boosts as enhancements

They weren't called enhancements at the time, but 13 years ago this month some security patches to MPE represented internal improvements that no company except HP could deliver to 3000s. Not at that time, anyway. This was the era when the 3000 community knew it needed lab-level work, but its independent support providers had no access to source code.

Just bringing FTP capability up to speed was a little evidence the vendor would continue to work on MPE/iX. For the next few years, at least; HP had halted OpenMPE's dreams to staff up a source code lab by delaying end of support until 2008. The vendor announced a couple more years of its support to 3000 customers.

In doing that, though, HP made an assignment for itself with the support extension, the first of two given to the 3000 before the MPE lab went dark in 2010. That assignment was just like the one facing today's remaining HP 3000 customers: figure out how to extend the lifespan of MPE expertise in a company.

FTP subsequently worked better in 2006 than it had in the years leading up to it. It's not an arbitrary subject. FTP was the focus of a wide-ranging online chat in May. Did you know, for example, that FTP has a timeout command on MPE/iX?

The connection time-out value indicates how long to wait for a message from the remote FTP server before giving up. The allowable range is 0 to 3000. A value from 1 to 3000 indicates a time-out value in seconds. A value of 0 means no time-out (i.e., wait forever). If num-secs is not specified, the current time-out value will be displayed. Otherwise, this command sets the connection time-out to num-secs seconds.

When an FTP job gets stuck, using timeout can help.

MPE/iX engineers and systems managers were working more often in 2006 than they do today. When anybody who uses MPE/iX finds a 3000 expert still available, they need to get in line for available work time. It remains one good reason to have a support resource on contract. A company relying on a 3000 shouldn't be thinking a mailing list or a Slack channel represents a genuine support asset. Even if that FTP tip did arrive via the 3000-L.

The resource of good answers for crucial questions gets ever more rare. The 3000-L mailing list has rarely been so quiet. There are information points out there, but gathering them and starting a discussion is more challenging than ever. File Transfer Protocol is pretty antique technology for data exchange. It turns out to be one of the most current standards the 3000 supports.

Before the boosts, FTP services had lagged behind the rest of the world's FTP for some time. The final patches for MPE/iX 7.5, 7.0 and 6.5 improved FTP in several areas. HP said in 2006 it made SOX compliance easier. It was an era when people cared about SOX and HP still wanted 3000 customers to be able to meet the Sarbanes-Oxley protocols.

The final security enhancements to FTP/iX are in patches FTPHDG9 7.5, FTPHDH0 7.0 and FTPHDH1 6.5. The patches include:

  • deny del, overwrite, rename
  • chroot limiting cd, dir, put, get, mput, mget
  • new enhanced semantics for 'noretrieve'

Patch IDs are:

FTPHDH1(A) for 6.5
FTPHDF5(A) for 7.0 ** note, this patch is for some general FTP fixes
FTPHDH0(A) for 7.0
FTPHDG9(A) for 7.5