IBM Support

OA38553: DOCUMENT TINYDS PARAMETER. USED TO LIMIT THE MAXIMUM NUMBER OF PAGES ALLOCATED FOR THE CNMCANZ0 DATA SPACE (FOR CANZLOG).

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • There is an undocumented parameter that can be used to reduce
    the maximum number of pages allocated for CNMCANZ0 data space.
    The parameter is called TINYDS, and would be specified on the
    INITPARM parameter of the _first_ SUBSYS statement containing
    INITRTN(DSI4LSIT). Example syntax of the statement would be:
     SUBSYS SUBNAME(xxxx) INITRTN(DSI4LSIT) INITPARM('TINYDS')
    This parameter limits the data space size to .5G, or 131072
    (decimal) pages, which is one quarter the size of the full
    data space.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of Tivoli NetView for z/OS V6R1.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: After installing NetView V6R1,          *
    *                      auxiliary storage requirements for the  *
    *                      MASTER address space increases by up to *
    *                      2 GB. This space may not have been      *
    *                      planned for, and could cause aux        *
    *                      storage shortage messages. The storage  *
    *                      is for the main Canzlog data space,     *
    *                      CNMCANZ0, which can grow to a full data *
    *                      space size of 2GB.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Main NetView Canzlog dataspace CNMCANZ0 is allocated with the
    potential to grow to 2GB in size, by default, if the system is
    left running long enough. This can cause auxiliary storage
    problems. There is a value that can be specified on the INITPARM
    parameter of the SUBSYS statement for NETVIEW V6R1 in PARMLIB
    member IEFSSNxx. This value is TINYDS, which will limit the
    maximum size of the data space to .5GB (one fourth of the size
    of a full data space). However, this value is not documented.
    

Problem conclusion

  • The Tivoli NetView for z/OS V6R1 Installation: Getting
    Started manual (GI11-9443-00) should be changed as follows:
     A new usage note should be added to the section entitled
     IEFSSNxx in Chapter 2, Preparing the MVS System, which should
     read as follows:
       o The initialization routine, DSI4LSIT, allocates a data
         space named CNMCANZ0 where MVS and NetView messages are
         stored, and which wraps when it reaches its maximum size.
         This is the main Canzlog data space, and by default is
         allocated with a full data space size of 2GB. To limit the
         size of the data space to .5GB to reduce auxliliary storage
         requirements, specify the following on the first SUBSYS
         statement that contains INITRTN(DSI4LSIT):
            INITPARM('TINYDS')
         Note that the NetView subsystem initialization routine
         ignores any value specified on INITPARM on a SUBSYS
         statement containing INITRTN(DSI4LSIT) that is not the
         first such statement read by MVS. If both TINYDS and
         LOGFORN are needed, specify both values on the same
         INITPARM, with TINYDS before LOGFORN, separated by a comma,
         as follows:
            INITPARM('TINYDS,LOGFORN')
    .
    After changing the Canzlog data space size (IE:TinyDS parm)
    it will not take effect dynamically, it requires a system IPL.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA38553

  • Reported component name

    NETVIEW FOR Z/O

  • Reported component ID

    5697NV600

  • Reported release

    10B

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-01-19

  • Closed date

    2012-02-16

  • Last modified date

    2015-02-09

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

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

Publications Referenced
GI11944300    

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJDU","label":"IBM Z NetView"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10B","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"10B","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
09 February 2015