II11038: CHANGES TO DB2 R410 INSTALL GUIDE SC26345600 THAT DIDN'T MAKE GA V4.1 PUBS. IN II09154,II09481,II09788,II10228,II10827,II11978

APAR status

• INTRAN

Error description

• 5740xyr00 DB2 R410 V4
  This APAR documents changes to the DB2 Installation Guide
  SC26345600 which did not make Version 4.1 GA pubs.
  continued in II09154,II09481,II09788,II10228,II10827,II11978
  ===============================================================
  Version 4 Book Title: Installation Guide
  Pages: 1-24, 1-25, 1-26, 1-27
  Change Description:
  
    In the section titled data structures in the
    System Planning Concepts chapter, add more specific
    information on table space sizes and correct some
    index sizes.
  1.In the first paragraph under "Table Spaces",
    modify as follows: "A table space is one or more data
    sets in which one or more tables are stored.  A table
    space can consist of a number of VSAM data sets, which
    can together contain up to 64 gigabytes of data...
  
  2.In the section "Partitioned table spaces" modify as
    follows:  "...A partition can be
    1, 2, or 4 gigabytes in length, depending
    on the number of partitions contained in the entire table
    space.  The maximum number of partitions in a partitioned
    table space is 64.  If less than 16 partitions are defined
    on the table space, then its maximum size is 4 gigabytes."
  
  3.In the section "Simple Table Spaces", add the last
    sentence as follows:  "The maximum size of a data set
    in the simple table space is 2 gigabytes.  And so,
    the maximum size of a
    simple table space is 64 gigabytes (2 gigabytes multipled
    by 32 data sets)."
  
  4.In the section "Indexes", modify as follows: "Each index
    occupies its own index space.  A nonpartitioned index
    can contain from 1 to 32 VSAM linear data sets."
  
  5.In the section "Partitioned Indexes" modify as follows:
    "A partitioned index is created on a table in a
    partitioned table space and is divided into
    multiple index spaces.  A partitioned index consists of
    between 1 and 64 partitions, each of which has a one
    to one correspondence to a VSAM data set.
    Each partitioned table space always has one
    table and one partitioned index defined on it.  The
    maximum size of a partitioned index is 1, 2, or 4 GB
    depending on the number of partitions.
    A partitioned index is always a clustering index.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-41, 2-197
  Change Description:
  Change the formula for the Sort Pool Size calculation on
  both pp. 2-41 and 2-197 to following:
  
     16000 x (12 + sort key length + sort data length + 4
     (if ESA hardware sort assist))
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-51, 2-72, 2-224
  
  Change Description:
  Under "Attention" on page 2-51, modify the fourth bullet
  by adding the following cross-reference after the first
  sentence (i.e., after the sentence beginning "Concatenate
  the new...):
  
  For more information on how DB2 uses the command table
  library, see "Connecting DB2I Panels to the ISPF Main
  Panel" on page 2-222.
  
  On page 2-72, modify the description of the target library
  prefix.SDSNSPFT to read:
  
  This is the DB2 ISPF command table library.
  
  On page 2-224, add the following text just before
  Figure 55:
  
  By specifying NEWAPPL(DSNE), you define DSNE as the ISPF
  application name used by DB2I. ISPF uses the name DSNE to
  create the ISPF profile pool member name (DSNEPROF) in the
  TSO_userid.ISPROF data set, which will contain all ISPF
  panel variables defined during DB2I execution.
  
  Using a NEWAPPL name other than DSNE: You may define any
  valid ISPF application name. If you define an application
  name to be something other than DSNE and you plan to use
  DB2 online help, you must create a new command table member
  that corresponds to your application name. You may create a
  new command table name by using the TSO Command Table
  Utility and specifying the Verb as Help and the Action as
  Select Panel(&Helppan) after defining your new ISPF
  application name.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-82
  Change Description:
  Replace the second paragraph under step 2: DSNTIJAE with:
  Do not modify the data definition statements for SDSNCLST,
  SDSNLOAD, or SDSNSAMP.  The SDSNCLST, SDSNLOAD, and SDSNSAMP
  libraries must be defined as partitioned data sets (PDS).
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-85
  Change Description: add this message to table of potential
  SMP/E messages.
  
    IEW0461    DSNCIAR    DFHEI1, DFHEAI0
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-141
  Under description for MAX USER, replace CICS line with:
  
  - Each active CICS transaction that can access DB2.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-162
  
  Replace Acceptable values under SUBSYSTEM NAME on panel
  DSNTIPI with:
    1-4 characters. First must be A-Z, #, $, or @.
    Others must be A-Z, 1-9, #, $, or @.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-182
  
  Replace the last sentence under QUIESCE PERIOD with:
  For more information about the quiesce mode of the Archive
  Log command, see Section 4 (Volume 1) of Adminstration Guide.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-186
  
  Change Description: add to description of DB2 Location Name
  Acceptable characters are A-Z, 0-9, and underscore.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-187
  Change Description: under DDF Threads add:
  If you specify ACTIVE, then the thread remains active. This
  provides the best performance but consumes system resources.
  If your installation must support a large number of
  connections, specify INACTIVE.
  
  In order for a thread to become INACTIVE, the following
  criteria must be met:
  - no held cursors
  - no held cursors have ever been left open during a commit
  - package bound RELEASE(COMMIT)
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-188
  Change Description:
  
  In the "Accept SQL CALL" description, replace the
  sentence "You must specify YES to use stored procedures"
  with the following:
  
  You must specify YES to have the DB2 stored procedures
  JCL procedure created. Specifying YES will allow you to
  use stored procedures and will cause the associated
  sample jobs to be edited. If you specify NO but decide
  later to use stored procedures, you will have to create
  the DB2 stored procedures JCL procedure yourself and
  update the STORPROC parameter in your subsystem parameter
  module with the proper stored procedure name.
  ================================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-217
  
  Modify the first paragraph that begins with "If you have not
  run the SMP/E ACCEPT job (DSNTIJAC)..." to read:
  If you have not run the SMP/E ACCEPT job (DSNTIJAC) for FMID
  HDB6610, you must edit DSNTIJUZ so that the SMP/E temporary
  data set (SMPTLIB) is included in the concatenation for the
  ADSNLOAD DD statement in steps DSNTIZL and DSNTIZQ.
  
  Delete the second paragraph that begins with "If you have not
  run the SMP/E ACCEPT job (DSNTIJAC)... and ends with ...
  CSECTS: DSNFSYSP, DSNJARVP, DSNJLOGP, DSNTSPRM, DSNVDIR1,
  DSNZMSTR, DSN3DIR1   You can ignore these messages."
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-232 and 3-9
  Change Description:
  Change the minimum release of VTAM from Version 3.3 or
  Version 3.4 to Version 3.4.2.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-242
  Change Description:
  Migration step 1: Run link checker on DB2 Version 3 table
  spaces should be listed as optional. Remove DSNDB01.SYSLGRNG
  from the list of table spaces with links or hashes.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-242
  
  Change Description:
  Replace the sentences that begin "When you run this
  utility..." and "Yoc can ignore..." with:
  When you run this utility on segmented table spaces you
  might get message DSN1985I.  The segmented table spaces
  in the catalog and directory are: DSNDB06.SYSPACKAGE,
  DSNDB06.SYSSTR, DSNDB06.SYSSTATS, DSNDB06.SYSDDF,
  DSNDB01.SYSUTILX, and DSNDB01.SPT01. You can usually
  ignore this message, see description of DSN1985I in
  Message and Codes for details.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-258
  
  Change Description:
   Modify change originally recorded in info apar II10827 to
   include the incompatible change for DSN9023I as well as
   DSN9022I.
  
  Add the following to the list of items that might affect
  your DB2 operations after migrating to Version 4:
  
  Changed Format of DSN9022I and DSN9023I Messages from
          START And STOP DB2:
  The completion messages from a START DB2 or
  STOP DB2 command no longer contain the subsystem
  recognition character as part of the message text.
  For example, whereas you previously saw this:
  DSN9022I - DSNYASCP '-START DB2' NORMAL COMPLETION
  In Version 4, you see this:
  DSN9022I - DSNYASCP 'START DB2' NORMAL COMPLETION
  
  Replace "Dump Titles for ABENDs" paragraph in Step 25 with:
    The common dump titles for ABENDs now use the 1-4 character
    subsystem identification (SSID) instead of the subsystem
    recognition character.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-258
  Change Description:
  Restrictions in STOGROUP VOLUMES clause enforced:  The PTF
  for PQ01849 enforces a documented restriction that only a
  single asterisk can be specified in a quoted string in a
  CRESATE STOGROUP or ALTER STOGROUP volume list.  Any
  STOGROUP definitions with mulitple asterisks in a quoted
  string in the VOLUMES clause must be removed using the
  ALTER STOGROUP REMOVE VOLUMES statement before applying this
  PTF.  These illegal definitions cause certain DB2 functions
  to fail.  You will be unable to remove these illegal
  definitions after applying this PTF.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-259
  
  Under CURRENTDATA Option paragraph add this sentence:
  For more information about the CURRENTDATA option, see
  Chapter 4 of Release Guide.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-260
  Change Description:
    Under 'Invoke Utilities Differently' add the following:
  
  Return Code Change for LOAD REPLACE with ENFORCE
    CONSTRAINTS:
  
  Previously, if you loaded a parent table space and enforced
  constraints, the LOAD utility ended with a return code 0,
  even though dependent table spaces were placed in a
  CHECK-pending status. Now, to help alert you to the fact
  that CHECK-pending table spaces exist, the LOAD utility
  ends with a return code 4 and issues message DSNU563I.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-327
  
  Corrected SQL statement in the example:
    SELECT NAME, COLTYPE, LENGTH, SCALE, NULLS, REMARKS, COLNO
           FROM SYSIBM.SYSCOLUMNS
           WHERE TBNAME= 'DEPT' AND TBCREATOR = 'DSN8410'
           ORDER BY COLNO;
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-331
  Change Description:  Add to first bullet under SYSIN
  
  Each SQL statment can be up to 32765 bytes long and be
  continued on multiple records.  However each record must be
  no more than 72 bytes long.
  ============================================================
  continued in II11978
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

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

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

Fix information

Applicable component levels