SIB 2004 224 Responses
Strategic Issues: These items contain issues that are of a policy or business decision nature and include some open issues from the SIB 2003. There are 30 votes available for these.
1 Description: Remove CPU throttling code in all affected HP3000 systems. 1090
2 Description:Put all internal MPE/iX and HP3000 system documentation on the Internet. 1108
3 Description: Build and make available by 11/1/2006 to all HP3000 sites, regardless of their current HP support status, an MPE/iX parking release for 6.5 and 7.5 versions of the operating system. This would include a full SUBSYS tape of all MPE/iX products to be distributed for the cost of media and distribution expenses.A final PowerPatch release for these versions would be made available via the normal channels. The PowerPatch releases will be available by 6/1/2005 to allow time for users to install the PowerPatch and verify no major issues are present. 1039
4 Description: License ss_config to HP approved third party support vendors. 854
5 Description: Enable MPE/iX version 7.5 to boot on 9x7 systems. 358
6 Description: Allow the conversion of used HP9000 computers, with "twin" HP3000 counterparts, to increase the size of the used HP3000 equipment "pool". 572
7 Description: By the second half of 2004, announce the decision for whether the MPE/iX source code will be licensed to one or more third parties. 1132
8 Description: Allow SCSI disk drive firmware level updating immediately. Suitable disk drives can be obtained on the open market to replace failed drives. They don _ t have the HP supplied firmware or the firmware level is not current. A new procedure needs to be supplied for all users, regardless of HP support status, to update the firmware, downloaded from the ITRC, on an MPE/iX machine. 590
Tactical Issues: These items contain issues that will require an R&D effort and include some open issues from the SIB 2003.
1 Description: Enhance MPE/iX to allow applications to send SCSI commands directly to SCSI devices (most likely to be implemented via POSIX ioctl() function). A primary goal will be to allow a "one I/O at a time" connection to most SCSI device types -- even types previously not supported by MPE/iX. NOTE: Devices will be limited those able to connect to existing HPe3000 Host Bus Adaptor cards (e.g. Parallel SCSI buses. For 9xx: SE and FW SCSI. For A/N-Class: HVD and LVD SCSI). Support of newer HBAs and connection protocols (e.g. 10Gbit FC, iSCSI, etc) will not be considered as part of this item. 872
2 Description: Support gigabit LAN connectivity. 1351
3 Description: Enable FWSCSI card firmware level reporting and update immediately. ODE/MAPPER doesn _ t show the firmware level on FWSCSI and MFIO cards. This needs to be fixed. The suplicen password for FWSCSIPB in SYSDIAG or STM is needed to get the level information and update the firmware, if needed. A new procedure needs to be supplied for all users, regardless of HP support status, to update the firmware, downloaded from the ITRC, on an MPE/iX machine. 1021
4 Description: Add ability to the SHOWJOB command to see all jobs in a job queue: SHOWJOB JOB=@J;JOBQ=MYQUEUE. Enhance the existing SHOWJOB command so that it can filter output based on a user specified job queue name. Today, the ;JOBQ parameter alters the SHOWJOB display to report the job queue name for all reported jobs. When JOBQ=name is specified the existing job queue SHOWJOB format will be used. The job queue name can be wildcarded. 804
5 Description: Create a new CI variable such that POSIX's UMASK feature is available to MPE processes. This would allow existing MPE applications to create files with security defined by the UMASK setting rather than using conventional MPE default security. Children processes would inherit the UMASK setting, so once it is set, all child processes have the same value controlling default permissions on all new files they create. The UMASK influence is easily overridden by specifying the security for the file directly, or by altering it after the file has been created, or by setting UMASK back to it's initial value (which actually is interpreted as "undefined"). 330
6 Description: Network printing to work with non-HP printers by adding a pcl_supported = false option in NPCONFIG.PUB.SYS. If this option is paired with pjl_supported = false, the spooler would just dump the ASCII data to the printer and strip any PCL sequences from the beginning of the spool file. No device status checking and reporting, failure recovery, imbedded PCL sequences, or handling of CCTL information would be done. The customer would be responsible for ending each of the spool files with a form feed command to flush the last page. HEADON would not be supported. 1424
7 Description: DEVINFO CI functions. Similar to FINFO and JINFO, provide a CI function which provides information for a device, based on LDEV # or device name. This function could get the desired info from AIFDEVCLASSGET and/or AIFDEVICEGET. 393
8 Description: VOLINFO CI functions. Similar to FINFO and JINFO, provide a CI function which provides information for a device, based on LDEV # or device name. This function could get the desired info from HPVOLINFO. 345
9 Description: SPOOLINFO CI functions. Similar to FINFO and JINFO, provide a CI function which provides information for a spoolfile, based on spoolfile # or spoolfile name. 637
10 Description: Local CI variables. Enhance the CI to support variables whose scope is local to the script or UDC in which they are defined. These variables would be deleted after the creating script/UDC ends. A local variable of the same name as a job/session variable would be found first. SHOWVAR may need to distinguish between local and job/session variables of the same name. The HPCIPUTVAR and HPCIGETVAR intrinsics may need to be enhanced to support this feature. 660
11 Description: System level CI variables. Enhance the CI to support variables whose scope is global to the entire system, not just a job or session as today. There will need to be restrictions on who can modify and delete system variables (maybe on who can create them too?). A global variable of the same name as a job/session variable will be found first to prevent them from being masked out. SHOWVAR may need to distinguish between system and job/session variables of the same name. The HPCIPUTVAR and HPCIGETVAR intrinsics may need to be enhanced to support this feature. 902
12 Description: ACDs for root, accounts, and MPE group directories. Today the root directory, all accounts and all MPE groups do not support ACDs. This means the shell chmod command cannot operate on these directories, and system managers cannot restrict who can see (traverse) the contents of these directories. Thus, LISTF @.@.@ is able to display every file on a system, which could be controlled if this enhancement was implemented. 369
13 Description: Inheritable access permissions passed down from a directory to its files. Similar to the POSIX CMASK but more flexible. Allow each directory (including root, accounts and MPE groups) to define a default permissions setting which, as a default, is applied to all objects created below this directory. 287
14 Description: Inheritable volume class passed down from a directory to its files. Enhance all directories, including MPE accounts and groups, to define a default volumeclass where all objects created below this directory, by default, are placed in that volume. If this is too large an effort or too risky, at least allow this enhancement for MPE groups. 217
15 Description: Make future I&I open source products (Apache, Samba, Sendmail, etc...) include the source trees and build scripts used to create the binary releases starting with the current releases. 979
16 Description: Keep Java for MPE up-to-date with the most current version available. 886
17 Description: Add a filecode for Perl scripts and enhance the CI (and COMMAND/HPCICOMMAND) to automatically run perl scripts if they have a perl filecode or if their HFS name ends in ".pl". 403
18 Description: Request that MPE's FTP server be enabled to support 'ftpusers' (users not allowed access to the FTP server) and 'ftpaccess' (files not allowed to be retrieved), like FTP on UNIX. The addition of these files would allow a system manager more granular control of an MPE system. These features would be valuable now and in the future (for homesteaders). 1349
What most accurately reflects what your site is planning to do (choose one):
1. Migrate off the HP 3000 (this includes replacing your applications). 73
2. Homestead for as long as possible. 99
3. Don't know yet. 39