WAVV
Requirement Form
Date: 6/11/2005 Requirement #: WAVV200601
Title: (Paraphrase problem in a
single statement)AIX Duplicate Key Feedback
Detailed
Problem Description: (Description of what you want changed - 400 character entry limit)
Currently, VSAM feedback for
a duplicate key does not provide differentiation between the primary key being
duplicate and an alternate key being duplicate. It would be beneficial, particularly when inserting a record into
a file, to know if failure is the primary key or an alternate key. Alternate key duplication can frequently be
mitigated at the application level.
Priority: (Select one: Urgent
- High - Medium - Low)
medium
Requested
Completion Date: (When? Examples: 3 months, 1 year,
Next Release) next release
Requirement
Type: (Select one:
Acceptability - Compatibility/Migration - Ease of Use - Feature/Function - Performance - Reliability/Availability/Serviceability
- Packaging - Interoperability)
Ease of Use
Business
Justification: (Why? Non-technical
business case description. Do not reword Detailed Problem
Description from above. What are the benefits to be gained by your
company, and the vendor and others?
Quantify: run time, dollars, manpower, etc. Why should the vendor do this for the customer?)
This would simplify insertion logic in many
programs and frequently avoid a preliminary read only to detect duplicate
primary keys. Although there is a
circumvention (defining the AIX with NONUNIQUEKEY but with a record size only
permitting a single key) it's a bit confusing to explain and to implement
properly.
Solution: (Optional)(Desired/undesired elements Note: Making a suggestion may limit a
vendors ability to deliver a solution)
Impact: (Optional) (How
will your company’s business be affected if a solution is not delivered?)
Company Name:
Author Name: Kevin
Corkery Author Title: Systems Consultant
Author
Address: 64 Acadia Drive, Voorhees,
NJ 08043
Author E-mail: kcorkery@comcast.net
Telephone: (856) 424-5185