WAVV
Requirement Form
Date: 9/8/2004 Requirement #: WAVV200504
Title: (Paraphrase problem in a
single statement)Log all console messages
also to SYSLST.
Detailed
Problem Description: (Description of what you want changed - 400 character entry limit)
Not all DB2/VSE console
messages get logged to SYSLST. Some things only display on the console.
Priority: (Select one: Urgent
- High - Medium - Low)
Medium
Requested
Completion Date: (When? Examples: 3 months, 1 year,
Next Release) ASAP
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?)
It is extremely hard to trouble-shoot DB2/VSE
problems when you have to look in 2 places for important messages -- the
console and SYSLST.
Solution: (Optional)(Desired/undesired elements Note: Making a suggestion may limit a
vendors ability to deliver a solution)
Any message that gets displayed on the console
should also get logged to SYSLST.
Impact: (Optional) (How
will your company’s business be affected if a solution is not delivered?)
Will make it easier to trouble-shoot DB2/VSE
problems by having all important messages in one place (SYSLST). This will also
help DB2 technical support personnel as they *always* request to see both the
SYSLST and the console log.
Company Name: Computer
Credit, Inc.
Author Name: Michael
Rosinger Author Title: Systems Programmer/DBA
Author
Address: 640 West Fourth Street, Winston-Salem, NC 27101
Author E-mail: mrosinger@cciws.com
Telephone: (336) 761-1524