Date: 9/24/2000 Requirement #: WAVV200018
Title : New instructions to use
indirect indexes
(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)
On other platforms I am use
to the concept of indirect addresses.
This is also used (but not named) in S/390. Addresslists are used everywhere. To load an address from a list,
you now need at least 2 instructions.
With 3 new instructions this could be reduced to just 1: LRX load regular (4byte address) indirect,
LSX load short (3byte address) LLX (load long 4byte address + 4byte ALET).
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)
Less error-prone coding for all developers in
S/390 Assembler
Date
: (When?
ASAP, 6 months, one year from now, etc)
ASAP
Impact : (How? How will your company’s business be
affected if a solution is not
delivered.)
None
Solution : (optional desired / undesired elements Note: suggest can limit vendor ability to deliver a solution)
LSX addresses
with B/DDD field an address that points to a 3 byte address, LRX addresses with
B/DDD field an address that points to a 4 byte address and LLX addresses with
B/DDD field an address that points to an address/ALET pair. All rules regarding addresses should apply
to both addresses (the B/DDD and the pointed to one).
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)
Suggestion
Company Name: Pi-Systemprogrammierungs-GmbH
Author Name: Martin
Trubner Author Title: Sysprog
Author
Address: D-63225 Langen Paul-Ehrlich-Str 46
Author E-mail: Martin@pi-sysprog.de
Telephone: (49) 171 850 7132
·
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]