IBM Support

PI94515: IBM SYSTEM STORAGE VTF MAINFRAME(VTFM) HVT092E. F TASKNAME,DISPLAY=TSP AND HVTUREP VOLUME COUNT NOT CONSISTENT.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When running HVTUREP the volume count shows value greater than
    400,000, for example:
    
    HVT202I ENTRIES  IN VDB  =   458999
    
    When issuing F taskname,DISPLAY=TSP it shows:
    
    HVT433I TAPES= 400001
    
    Following error message is issued:
    
    HVT092E MAXIMUM NUMBER OF 00400000 ALLOWED VIRTUAL TAPES
            EXCEEDED
    
    Current design is to limit 400K volumes, during VTFM server
    initialization or when updating the VDB-in-Storage table, VTFM
    detected that the number of virtual tapes in the VDB exceeds its
    internal buffer designed to store them.  However, the code is
    not consistent and could cause overflow in the VTF region.
    
    With this apar, code will be changed to allow definition of
    greater than 400K volumes and to ensure that the region does not
    overflow.
    

Local fix

  • Until this issue has been fixed, it is advisable to reduce the
    number of scratches so that it does not exceed 400K.
    
    As the message states, following action should be taken to
    reduce the number of volumes so that it does not exceed 400K:
    
    HVT092E:
    
    ...
    ...
    
    Operator action
    
    If some of the virtual tapes in the VDB are not in use, remove
    them using the HVTUTAP utility in the HVTUTAP member in the
    SAMPLIB library.
    
    ...
    ...
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All VTF Mainframe Release 3.0.0 users.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: HVT092E message count is inconsistent   *
    *                      with the HVTUREP report showing more    *
    *                      tapes.                                  *
    ****************************************************************
    * RECOMMENDATION: Install the latest PTF associated with this  *
    *                 APAR.                                        *
    ****************************************************************
    The virtual tapes entries residing in the VDB are periodically
    loaded by the VTFM server into its private storage in what is
    called VDB-In-Storage. That copy of virtual tapes list is used
    to locate eligible scratch tapes and to inform the dynamic
    reallocation feature of the existence of specific virtual
    tapes.
    
    While the VDB-In-Storage buffer is limited to 400,000 entries,
    no limit is imposed by other VTFM components that can add new
    virtual tapes to the VDB. Following that condition and in case
    where more than 400,000 virtual tapes are added to the VDB by
    VTFM components like HVTUTAP or HVTURCV utilities, new virtual
    tapes ad hoc mounts, etc.., the following issues are expected:
    1. During VDB-In-Storage load process, HVT092E message is
       issued indicating that only 400,000 virtual tapes were
       loaded.
    2. Virtual tapes over the 400,000 limit are not considered to
       be scratch-eligible and are not mounted on requests for
       scratch tapes mounts.
    3. The HVT433I and HVT434I messages (result of F server,D=TSP
       command) don't display any count larger than 400,000.
    4. The HVTUREP utility report includes all virtual tapes from
       the VDB and the count reported by its HVT202I message
       obviously exceeds the limit loaded to the VDB-In-Storage and
       reported by the HVT092E message.
    
    The fix reworks the various VTFM components compatibility
    issues and:
    1. Increases the number of handled virtual tapes to 1,000,000.
    2. Fixes all VTFM components to limit the number of virtual
       tapes to 1,000,000.
    
    Note: After the fix apply, the following components will
          experience an increase in their virtual storage use:
          1. The VTFM server by 15MB.
          2. The VTFM Dialog by 7MB.
    

Problem conclusion

  • Additional keywords: VTFM/K
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI94515

  • Reported component name

    SYS STOR VTF MA

  • Reported component ID

    5655V4300

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-03-01

  • Closed date

    2018-03-08

  • Last modified date

    2018-04-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UI54330

Modules/Macros

  • HVTIBF   HVTINI   HVTLVD   HVTMNT   HVTTAPF
    HVTTP01  HVTTV05  HVTUJRC  HVTURCV  HVTUTAP  HVTVAM   HVTVLP
    HVTVLR   HVTVLT
    

Fix information

  • Fixed component name

    SYS STOR VTF MA

  • Fixed component ID

    5655V4300

Applicable component levels

  • R300 PSY UI54330

       UP18/03/09 P F803

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"300","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 April 2018