Date: 9/18/2000 Requirement #: WAVV200030
Title : Add support for Tokens to
VSE
(Short description of what you want the
product changed to - include keywords like function, short product name)
Statement of
the Problem : (What? Detailed description of what you want
changed, 400 char.limit)
Currently, the only way to
share system getvis areas are to set up pointers in either SDL phases or via
the PRODID hooks. There needs to be a better approch. MVS currently supports
what are called "Tokens" simular to what would help VSE.
As envisioned, tokens could be defined with a scope
of either system, partition, task.
Benefit : (Why? Non-technical business
case description, i.e a business case. Do not reword problem statement above. How do you to justify the needed change? Wwill itrequest
benefit the submitter’s your company, and the vendor
and others? Business case
and benefits to users and vendor which can to
justify the needed change?. Quantify: run time, dollars, manpower, etc. Also, wWhy
should is it important
for vendor to want to do this for their
customer?s)
Date : (When? ASAP, 6 months, one year from now, etc)
1 year
Impact : (How? How will your company’s business be
affected if a solution is not
delivered.)
Continue using the other methods to 'cheats'.
Solution : (optional desired / undesired elements Note: suggest can limit vendor ability to deliver a solution)
Each token entry needs to only supply a minimal
amount of data. Each entry could be limited to maybe only 64 bytes. Maybe an
extention to the XPCC functionality.
Classification : (Suggestion=Nice Idea, Long
Range=Future, Tactical=ASAP, or Acceptability=I won’t buy the product
or will drop the product if solution not provided)
Future
Company Name: Thigpen
Enterprises, Inc.
Author Name: Tony
Thigpen Author Title:
Author
Address: 102 Brandiwood Court, DeBary, FL 32713
Author E-mail: tony@vse2pdf.com
Telephone: (407) 474-0770
·
Please
be precise and short.
·
The
Benefit section is extremely important – please make a business case.
·
Proofread
- recheck accuracy of contact information before saving.
·
File
as unique name-WRvviinn, where vv=vendor initials, ii=your initial, ‘nn’ to number each requirement.
Ex.: Wribwm01 ib=IBM, wm=wayne mery
·
Submit
your labeled diskette (with your full name) to the requirements coordinator, a
black shirt WAVV manager, the registration desk or copy it to the root drive of
a registration or workroom PC.
* [IR1]