WAVV Requirement Form[IR1] 

 

Date: 10/9/2000                                           Requirement #:  WAVV200040

Product Name:    IDCAMS      Product Release#: Current

Vendor Name:     IBM

 

Title :                   IDCAMS should do an EOV rather than close on a multivolume restore

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

 

During aan IDCAMS restore with multivolume tapes, IDCAMS issues a close at the end of the first volume if the last file on the first volume does not span to the next volume. Because IDCAMS issues a close, the tape management system does not know what volume to request.

                                                                                            

  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)

 

This would reduce wasted time in researching what tape volume the data file resided on, modifying JCL and operator confusion, as well as after hours programming support.

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

 

Unnecessary costs, production delays and programmer overtime.

  Solution :  (optional desired / undesired elements Note: suggest can limit vendor ability to deliver a solution)

 

IDCAMS should provide an option that would allow the specification that a tape management system is in use, which would consequently change how IDCAMS handles EOV/CLOSE processing.

  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)

 

ASAP

 

Company Name:        State of New Hampshire                                                                  

Author Name:            Don Hooker                             Author Title: Senior Systems Programmer

Author Address:         4 Hazen Dr., Concord, New Hampshire  

Author E-mail:            DHOOKER@admin.state.nh.us

Telephone:                 (603) 271-1535

 


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