WAVV Requirement Form
Date: 3/4/2002 Requirement #: WAVV200241
Title: (Paraphrase problem in a single
statement)Easier determination if file
is Librarian
Detailed
Problem Description: (Description of what you want changed - 400 character entry limit)
The only method to determine
if a DLBL is a Librarian file is to issue LIBRM OPEN or
LBRACCES MF=ADDLIB and check the return code. If the DLBL is VSAM, this could also produce a 42xxI error
message on the console; if scanning labels this can flood the console. A simple call (either LIBRM or INLC/LBR
macro) with a return code, and no console message if issued against a VSAM
file, is desired.
Priority: (Select one: Urgent
- High - Medium - Low)
Medium
Requested
Completion Date: (When? Examples: 3 months, 1 year,
Next Release) Next release
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?)
Customers have complained about the plethora of
messages issued when our Entire System Server product scans labels at
initialization and there are many VSAM files defined.
Solution: (Optional)(Desired/undesired elements Note: Making a suggestion may limit a
vendors ability to deliver a solution)
The preferred
solution is a simple API passing a DLBL and a return code stating either yes or
no, and possibliy whether VSAM or non-VSAM.
An alternative
solution is the ability to surpress any console messages by flipping a bit in
the LACB and LIBRDCB blocks.
Impact: (Optional) (How
will your company’s business be affected if a solution is not delivered?)
No fiscal impact, however perception of the
product by customers is affected by the current operation.
Company Name: Software AG
Author Name: Ray
Mullins Author
Title: Sr. R&D Specialist
Author
Address: 1016 Wendy Ave, Big Bear City, CA 92314
Author E-mail: ray.mullins@softwareag-usa.com
Telephone:
(909) 584-7004