Postponing POSIX

You can update to Release 5.0 and take advantage of the new :SETCLOCK command or wildcarded :PURGE, but not use the POSIX extensions.

If most of your users are trapped into applications at logon, they will not notice any difference. More importantly, they cannot create any HFS objects, which means the system manager does not really need to be POSIX knowledgeable.

You can take comfort in knowing that users need to take deliberate action to build a POSIX-named object. Remember that the command :BUILD a still creates the file uppercase "A" in your logon group (as long as you have not changed your CWD). Production jobs and programs will behave the same.

You can limit access to the shell and utilities by adding ACDs to all program files in the HPBIN.SYS group. You can also restrict the use of the .2 shell by adding a lockword.

You can update to Release 5.0 and purge all of the FOS HFS files and the HPBIN.SYS group. This will save you some disk space, but will not prevent a user from creating an HFS object.

You can update to Release 5.0 and buy a commercially available software product that disables the HFS-related features of MPE/iX.