As advertised yesterday, here is a complete re-post
of the 1997 SIGIMAGE Enhancement Ballot. See
separate message for accompanying Enhancement
Proposals (expanded enhancement descriptions).
Again, for all those that missed it first time around;
or just didn't get around to it yet; this is the *last
chance* to have your vote count in deciding what new
enhancements HP will implement next in Image/SQL.
See instructions at end of ballot for sending it in. Note
that at this late date email response is encouraged.
Return to:
[log in to unmask]
thanks,
Ken Sletten
SIGIMAGE Chair
===================================
**************************************
**** SIGIMAGE ****
**** 97 Enhancement Ballot ****
**************************************
This ballot lists only SIGIMAGE enhancement requests
that have been reviewed by the SIG and/or the SIGIMAGE
Executive Committee (SIEC), that have not been formally
committed to by Hewlett-Packard. Additional details are
provided in the accompanying "1997 Enhancement Proposals"
handout. Enhancements that have been implemented or are
scheduled for near-term delivery have been moved to the
"Now/Soon Available" list.
This is a weighted ballot. You have up to $100 to spend on
enhancements that are most important to you. You may
spend the $100 on just one enhancement, or divide it up in
increments as small as $1. Vote against an enhancement by
prefacing the amount with a minus sign. HOWEVER, note
that the absolute total of the dollars you spend must still be
<= $100, regardless of the sign.
Each individual may send in only ONE 1997 enhancement
ballot, regardless of how you receive and return it (by hard-
copy, e-mail, web site, or fax). To provide a method of
verifying the one-person, one-ballot rule, all ballots must
include at least the <name> AND <phone number or e-mail
address> of the person submitting the ballot. Ballots that
lack legible entries for this minimum information or that
spend more than $100 will be disqualified.
Enhancements on this ballot are grouped into six categories:
Enhancements to Support Direct ODBC Access, those to
Support SQL Access, IMAGESQL Utility Enhancements,
Vendor Needs, QUERY Enhancements, and General
Enhancements. Within each category, enhancements that
were on the 1996 ballot are listed in the order they were
ranked in '96. Note that if the first two enhancements
(Direct ODBC Access) would meet ALL your SQL needs,
you may not want to vote for enhancements to the
IMAGESQL utility (numbered 16 through 24), since their
intent is to improve functionality and simplify tasks when
ATTACHing an IMAGE database to an ALLBASE DBE.
Enhancement requests that have already been classified as
requiring a Small, Medium, or Large amount of work to
implement are followed by (S), (M), or (L). Those that
are new for 1997 are followed by "[97]". Because this
ballot has expanded for 1997, note that there are TWO
SIDES or SHEETS of paper that must be returned if
sending hardcopy....
**************************************
**** SIGIMAGE ****
**** 97 Enhancement Ballot ****
**************************************
Enhancements to Support Direct ODBC Access to
HP 3000 Data:
____ 1. Provide 16/32-bit ODBC client access directly to
TurboIMAGE, without having to go through
Allbase/SQL: [97].
____ 2. Provide 16/32-bit ODBC client access directly to
MPE and KSAM files, without having to go
through Allbase/SQL.
Image/SQL Enhancements to Support SQL Access:
____ 3. Ability to ATTACH MPE and KSAM files to a
DBE (full integration with Allbase/SQL): (L).
____ 4. Ability to add/drop Image datasets, indexes, and
items (DDL): (L).
____ 5. Support SQL NULL item functionality in
Image/SQL: (L).
____ 6. Provide IMAGE read-only DBLOCK mode
(repeatable read): (L).
____ 7. Multi-record/multi-set DBGET, DBPUT,
DBUDPATE: (M).
____ 8. Support SQL SAVEPOINT in Image/SQL: (M).
____ 9. Ability to better inform the SQL Query Optimizer
about the most efficient retrieval path to use in
accessing IMAGE data.
____ 10. Allow default values for FIELDS not specified
at DBPUT time.
____ 11. Allow one transaction to span both ALLBASE
and IMAGE: (L).
____ 12. Allow ODBC access TO clients FROM Image/SQL.
____ 13. Make DBSCHEMA fully SQL-aware.
____ 14. Allow renaming of an IMAGE table through SQL.
____ 15. Easier access to Image and Allbase from POSIX
programs: [97].
Enhancements to the IMAGESQL Utility Program:
____ 16. Provide ability to retain and reuse attach
parameters across a DETACH / re-ATTACH of
an Image/SQL database to a DBE.
____ 17. Improve DBA functions for managing authorization
ID's.
____ 18. Provide ability to enable/disable SQL access
without having to ATTACH / DETACH an Image
database to / from a DBE.
____ 19. Allow DBA user to ATTACH IMAGE database
without password.
____ 20. Do not require exclusive DBE access for all
IMAGESQL functions.
____ 21. Provide IMAGESQL option to NOT attach
IMAGE Auto Masters.
____ 22. Allow wild-card ADD USER in IMAGESQL.
____ 23. ATTACH command to register IMAGE Master-Detail
referential integrity constraints in a DBE: [97].
____ 24. ATTACH command option to load ODBCVIEWs: [97].
TurboIMAGE Vendor Enhancement Needs:
____ 25. Provide a user-accessible DBQUIESCE
intrinsic: (L).
____ 26. A Measurement Interface for performance
data: (M).
____ 27. Allow tracking files to be associated with a
database: (M).
____ 28. Tool "memory area" file(s) associated with
a database: (M).
Enhancements to TurboIMAGE QUERY:
____ 29. Ability to do FIND FIELDA = FIELDB.
____ 30. Provide a MULTIFIND update / delete function.
____ 31. Ability to access DBCONTROL and DBINFO: (S).
____ 32. Allow DBGET using IMAGE record number.
____ 33. Support IMAGE dynamic transactions: (S).
____ 34. SHOW INDEX command to show all OMNIDEX Indexes.
General Enhancements to IMAGE:
____ 35. Provide Date/time datatypes in Image/SQL.
____ 36. Image/SQL support for Binary Large Objects
(BLOBS).
____ 37. GETUPDATE to update record(s) without prior
DBGET: (M).
____ 38. Ability to specify all DBUTIL flags and settings
in DBSCHEMA.
____ 39. Non-destructive creator access across groups
in DBUTIL.
____ 40. Increase limits in TurboIMAGE internal structures.
____ 41. DCE compatibility for IMAGE (Security, directory
services, etc.).
____ 42. Performance improvements for DBUPDATEs
of Sort Fields.
____ 43. Global files (avoid max files per process limit
+ better performance)
____ 44. DBINFO mode to return fully-qualified IMAGE
database name.
____ 45. Have DBUTIL ignore database file equations
(can't use anyway).
____ 46. Ability to set maximum chain lengths in IMAGE.
____ 47. DBUTIL option to require confirmation for
PURGE and ERASE after displaying fully
qualified database name: [97].
____ 48. Extend FTP/iX command set to include a
DBMGET, that takes root file input and insures
complete copy of an IMAGE database: [97].
Name: _______________________________________
Phone: ________________________________ and / or:
e-mail: _______________________________________
Company: ____________________________________
Send this so it ARRIVES on or before Mon 20
January 1997:
Fax to Interex at: 408-747-0947,
Attn: SIGIMAGE Ballot
or mail to: Interex - SIGIMAGE Ballot
P.O. Box 3439
Sunnyvale, CA 94088-3439 USA
or send e-mail to: [log in to unmask]
(with ONLY "SIGIMAGE Ballot" in title).
_______________________________________________
|
