WAVV
Requirement Form
Date: 4/23/2003 Requirement #: WAVV200323
Title: (Paraphrase problem in a
single statement)Have AUTOxxx select next
avail LST/PUN entries using std Power rules
Detailed
Problem Description: (Description of what you want changed - 400 character entry limit)
CSI has told me that AUTOxxx
selects entries from the VSE/Power queue based on the earliest creation
time. So increasing the priority of any
entry does not cause AUTOFTP to process the entry any sooner. We need a way to prioritize reports being
sent out. We would like AUTOFTP to use
the VSE/Power priority and the standard VSE/Power rules to select which report
to process next.
Priority: (Select one: Urgent
- High - Medium - Low)
High
Requested
Completion Date: (When? Examples: 3 months, 1 year,
Next Release) 3 mos
Requirement
Type: (Select one:
Acceptability - Compatibility/Migration - Ease of Use - Feature/Function - Performance - Reliability/Availability/Serviceability
- Packaging - Interoperability)
Performance
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?)
To get prioritized reports sent out first.
Solution: (Optional)(Desired/undesired elements Note: Making a suggestion may limit a
vendors ability to deliver a solution)
Code AUTOxxx to used standard GENERIC GET
PWRSPL macros to process next available queue entries.
Impact: (Optional) (How
will your company’s business be affected if a solution is not delivered?)
We would have to define alternate AUTOxxx
events using different classes for different priority reports which will waste
VSE/Power classes that we can't afford.
Company Name: Bisys
Author Name: Pat
Bowman Author Title: Director Mainframe Tech Suppor
Author
Address: 11 Greenway Plaza - suite 300
Houston, TX 77046
Author E-mail: pat.bowman@bisys.com
Telephone:
(713) 965-1458