WAVV Requirement Form[IR1]

Date: 9/24/2000 Requirement #: WAVV200019

Product Name: S/390 Product Release#: POP Ver. 7

Vendor Name: IBM

Title : TPROT non priviledged

(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)

Every middleware product (not only the core operating system) has the problem of verifying an address. Wheather a given combination of 4 bytes is a valid address is not really relevant to the operating system as long as it is not used. The problem of "hired guns" exists everywhere.

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)

Better parm-checking in everthing (from LE abend handling to MQ parm validation) for S/390 developers. Especially true in MVS where becoming priviledged is near impossible (RACF), but also in VSE. TPROT would save a full path through the programcheck handler, dispatcher and various routines that catch faultly addresses at ProgCheck time (LE dump-routines,VSE-Supervisor, CICS storage handler).

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)

Remove the attribute priviledged instruction from TPROT

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)

Tactical - Fix of an initial design-flaw

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@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]