Rank | Ballot Item # | Number of votes | Description |
1 | 5 | 2079 | Remove CPU throttling code on existing affected A-/N-class systems post 10/31/2003. |
2 | 10 | 1694 | Put ALL HP 3000 documentation on the Internet. Note that the CE hardware manuals are not currently available on the Internet. |
3 | 3 | 1595 | Produce a "parking" PowerPatch for 6.5, 7.0 and 7.5 including all General Release patches by 10/31/2003. And make it available via the Internet. Produce a �parking� release of MPE in the 2005-2006 timeframe. |
4 | 7 | 1351 | License ss_config to qualified third parties by end of support. |
5 | 1 | 1301 | Support gigabit LAN connectivity. [There is a migration need for this; also to support network backups.] |
6 | 6 | 1247 | Enable MPE/iX 7.x to boot on 9x7s post 10/31/2003. |
7 | 2 | 1165 | Verify FTP/iX for > 8GB files both ways, fixing any problems discovered. Known problems include slowness when FTPing byestream files. Make sure FTP/iX is industrial strength. |
8 | 4 | 1006 | Make sure MPE can mount any disk up to possibly 1TB and be able to use what we've been advised is the theoretical OS limit of approximately 300MB. |
9 | 36 | 616 | Bundle all of ALLBASE with Image/SQL after HP e3000 end-of-HP-sales: Need 9th of 9 modules, to go over 12 MBytes of user data (everything else is EXACTLY the same between Image/SQL and the full ALLBASE product) |
10 | 9 | 610 | CI functions: the ability to call another script or UDC as a function that would return a value using an enhanced CI RETURN command. [This would allow users and third parties to add CI functionality.] |
11 | 14 | 345 | Better DBUPDATE performance for update of IMAGE SORT Fields (but NOT Search Fields) with CIUPDATE: Compare new value to old, then search for new sort position in �right� direction, instead of always starting at end of chain |
12 | 12 | 315 | IMAGE multi-record / multi-set DBGET, DBPUT, & DBUDPATE (process entire blocks of data instead of just individual records) |
13 | 16 | 285 | Modify DBUPDATE so it honors extended sort requirements if any Field in the extended sort range of a Critical SORT Field is changed, regardless of whether or not the Field being modified is itself �Critical� (CIUPDATE of a critical item ALREADY honors all extended sort criteria, just like DBPUT) |
14 | 30 | 281 | DBSCHEMA: Update so it can be single tool needed to CREATE an IMAGE database: Be able to specify all DBUTIL flags and settings (has not kept up with recent changes). Make it fully SQL-aware. Flag ALLBASE reserved words with WARNing to catch conflicts up front, instead of only later when ATTACH database to DBE |
15 | 11 | 263 | Enhance the CI to include the following functions: VOLINFO(), DEVINFO() and SPOOLINFO(). |
16 | 8 | 223 | Integrate internal system logging with syslogd. |
17 | 13 | 203 | New IMAGE GETUPDATE intrinsic, to retrieve / update record in one call without DBGET (saves overhead; simplifies coding) |
18 | 26 | 190 | Allow tracking files to be associated with a TurboIMAGE database (all associated files; such as schemas, 3rd-party indexes, etc.) |
19 | 35 | 190 | Let TurboIMAGE keys split by IMAGESQL during ATTACH be accessed as a full IMAGE key via SQL at run time (currently no way to do this) |
20 | 22 | 185 | Add new DBINFO modes (probably '5xx') to return all root file flag settings (several flags missing from current mode-list). Avoid need for parse of DBUTIL-FLAGS output. Also include database MPE file name and IMAGE �current list� |
21 | 17 | 184 | Ability to set max IMAGE chain lengths, with unique key option |
22 | 18 | 184 | Allow >16 paths to a DETAIL dataset ( >16 to Master already) |
23 | 28 | 180 | Create a GR patch that would allow running TurboIMAGE version C.10.XX on MPE 6.5. Provides DDX with MPE Large Files (probably PowerPatch 2 or better ONLY, due to need for 128 GB Large Files and Extended High-Water Mark) |
24 | 19 | 154 | Increase IMAGE DBOPEN concurrency. Significant reduction in delay; if many instances of one app launched at the same time |
25 | 24 | 153 | Make the DBQUIESCE intrinsic used by TURBOSTORE user- callable; and provide external documentation for it, including appropriate end-user cautions |
26 | 25 | 148 | Allow default values for FIELDs not specified at DBPUT time, with equivalent in TurboIMAGE to SQL/Server �AUTOINCREMENT� feature |
27 | 29 | 143 | DBUTIL: Non-destructive creator access across groups |
28 | 21 | 140 | Drop the need for IMAGE BlockLength to be a multiple of 256B (saves space) |
29 | 20 | 137 | $CONTROL option to allow >= 2047 items in IMAGE database. Disallowing Remote File Access (RFA) for > 1200 items is O.K. |
30 | 23 | 130 | Allow a single IMAGE character field to be as large as the 2378-Word maximum entry length |
31 | 32 | 122 | Enable / Disable end-user SQL access without Attach / Detach |
32 | 37 | 100 | Allow wild-card ADD USER in IMAGESQL |
33 | 34 | 71 | Do not require IMAGE Maintenance Word in IMAGESQL if none specified in the IMAGE database (potential security issue ??) |
34 | 27 | 63 | Tool �memory area� associated with a TurboIMAGE database (allow logging of tool-specific IMAGE data on structural problems, etc.) |
35 | 33 | 63 | Allow IMAGESQL ATTACH by DBA user without password (requiring password in this case is actually LESS secure, since password is logged in an MPE file) |
36 | 31 | 47 | DBSCHEMA option: Allow symbolic expressions for capacity |
37 | 15 | 7 | Make CIUPDATE default = �ON� in DBUTIL, instead of current �ALLOWED� |
