II10827: CHANGES TO DB2 R410 INSTALL GUIDE SC26345600 THAT DID NOT MAKE V4.1 GA PUBS. CONT.IN II09154, II09481, II09788,II10228,II11038

APAR status

• Closed as canceled.

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, II11038.
  ===============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-42, 2-43
  Change Description:
  
  Within Chapter 2-2 in the section on "Calculating the EDM Pool
  Space Needed for Plans" modify the 3rd paragraph as follows:
  
   The average plan size changes in proportion to the increase
   in the number and complexity of SQL statements.  Plan size
   is also affected by the complexity of the access path for
   SQL statements.
  
   Add the following information in 2 paragraphs after the
   information on the ACQUIRE option of the BIND command:
  
   The RELEASE option of the BIND command can also affect the
   plan size.  RELEASE(DEALLOCATE) can result in a larger plan
   size than RELEASE(COMMIT), thus affecting the amount of EDM
   pool storage that the plan consumes.  RELEASE(DEALLOCATE)
   causes items to remain stored with the plan to enhance
   performance.
  
   The increase in plan size is determined by the number of
   database objects (databases, table spaces, and tables)
   actually used by the plan.  In CICS and IMS environments,
   thread reuse tends to increase the number of database
   objects used by the plan when the RELEASE(DEALLOCATE) BIND
   option is used.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-108
  Change Description:
  
  In the description of items 3-9 (Volume Serial),
  add the following to the 1st paragraph:
  
  Each volume serial number must identify a volume that is
  accessible to MVS for dynamic allocation of the data set,
  and all identified volumes must be of the same device type
  and have adequate free space.  See Section 2 (Volume 1) of
  Administration Guide for more information on managing data
  sets.  Refer to Chapter 2-2, "Estimating DB2 Storage Needs"
  for information on estimate space.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-167
  Change Description:
      Under the description of item 7, Message Identifier,
      the changes are marked with ">>".
  
  7. MEMBER IDENTIFIER
  DSNZPARM:             none
  Default:                 1
  Acceptable values:   1-248
  Update: edit IRLM start procedure
  
  Specify an ID number that uniquely names this IRLM member
  >> within an IRLM data sharing group.  We recommend that
  you correlate the IRLM member ID with the DB2 member name.
  For example, for DB2 member DSN1, specify an IRLM member
  ID of 1.
  
  >> Note that this IRLM ID does not relate directly to the
  >> limit of IRLM members that can be in the data sharing
  >> group. That limit is determined by the current hardware
  >> limits (currently 32).  If you edit the "irlmproc"
  >> directly, you can specify a value from 1-255.  See DB2
  >> Command Reference for the "irlmproc command" information.
  
  This option is used only for DB2 data sharing.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-173
  Change Description:
   A footnote is added to the special characters
   table that states the following:
  
   3. To use the equal sign (=), accept the default
      command prefix, then edit job DSNTIJMV and
      replace the dash (-) with the equal sign as the
      first character of the command prefix.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-187, 3-7, 3-10
  Change Description:
  
  p.2-187:
  Under installation panel DSNTIPR, the description for
  field 8 DB2 GENERIC LUNAME, add this sentence after the
  1st sentence:
  
  Specify a generic LUNAME to identify this DB2 subsystem
  or data sharing group in a network.
  >>You can only use a generic LU name if
  >>DB2 is running as part of an MVS Sysplex.
  
  p.3-7, under introduction to step 2:
  >>If you use at least VTAM version 4 release 2 and the MVS
  >>system on which DB2 is running is part of an MVS sysplex,
  >>you can choose a generic LU name to define a DB2 group to
  remote locations.
  
  p.3-10 within step 2 in the bullet about generic names:
  If you use VTAM Version 4 Release 2,
  >>and the MVS
  >>system on which DB2 is running is part of an MVS sysplex,
  you can use a "generic"
  8-character name to represent a group of VTAM LU names.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-216 & 2-248
  Change Description:
  
  Change Installation Step 4, last sentence to:
  
  If DSNTIJID fails or abends,
  run job DSNTIJDE, then rerun DSNTIJIN and DSNTIJID.
  
  Change Migration Step 9, last sentence to:
  
  If DSNTIJID fails or abends, delete all datasets created by
  DSNTIJIN, then rerun DSNTIJIN and DSNTIJID.
  ============================================================
  Version 4 Book Title: Installation Guide
  Page: 2-241
  Change Description:
  
  In "Migrating the DB2 Subsystem," under "Utilities,"
  replace the last sentence of the second paragraph with this:
  
  "See Section 2 of Utility Guide and Reference for
  information about buffers for input and output data
  sets in online utilities."
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages:  2-242
  Change Description:
   Within Migration Step 1, and following the sentence,
   "This ensures that the table space pages are physically
   correct and the catalog table spaces are clustered."
  
   Modify the next sentence as follows:
  
   When you run this utility on some of the
   catalog table spaces, like
   DSNDB06.SYSPKAGE, you might get message
   DSN1985I because those spaces are segmented.
   You can ignore this message.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-256
  Change Description:
  
  The second sentence in the following paragraph, under
  Migration Step 19 is deleted.
  
  We recommend that you check the integrity of your DB2
  Version 4 catalog by following, in any order, these steps.
  ****the following is deleted***************
  >>Ensure you have stopped the catalog table spaces or
  >>DB2 before proceeding.
  ============================================================
  Version 4 Book Title:  Installation Guide
  Pages: 2-258
  
    Add the following to the list of items that might affect
    your DB2 operations after migrating to Version 4:
  
    Changed format of DSN9022I Message from START and STOP DB2:
    The completion message, DSN9022I, from a START DB2 or
    STOP DB2 command no longer contains 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
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-259
  Change Description:
  
  The following is added to migration step 23 about
  release incompatibilities:
  
  SQLCODE -101
  
  After migrating to DB2 Version 4, it is possible to receive
  SQLCODE -101 on long or complicated SQL statements that
  previously executed successfully.  This is possible because
  SQL statements and DB2 internal structures are buffered in
  the same local storage, and release changes in the internal
  structures can result in less storage available for the SQL
  statements.
  
  Re-write the offending SQL statements by using correlated
  references, or by breaking up UNIONs.
  ============================================================
  Version 4 Book Title: Installation Guide
  Pages:  2-284
  Change Description:
    This note is added to the paragraph prior to the table on
    DSNTEJ2A return codes:
  
  Note that the output from Job DSNTEJ2A shown in "table DSNTEJ2A
  RETURN CODES"   assumes that you are using IBM High Level
  Assembler/MVS Version 1 Release 2. With Version 2, you can get
  a return code of 4 at procstep ASM along with warning and
  informational messages from the Assembler.  These warnings
  relate to changes in the assembler default options and can be
  ignored. Job DSNTEJ2A runs as expected.
  ============================================================
  Version 4 Book Title:  Installation Guide
  Pages: 2-365, 2-368, 2-369
  Change Description:
  
  The defaults for STRWT and STANDBY are corrected
  in the DSNCRCT TYPE=INIT macro parameters as follows:
  
  The default for STANDBY in the syntax diagram is SQLCODE.
  The default for STRTWT is AUTO.  In the note under the
  syntax diagram the sentence is changed: "The STANDBY keyword
  and the AUTO option of STRTWT are valid for CICS TRANSACTION
  SERVER 1.1 and above.  STRTWT=YES is the default for CICS
  Version 4 and earlier."
  
  In the description of STANDBY, SQLCODE is highlighted
  as the default.  The 2nd sentence under the general
  description is changed to:"This keyword is valid for
  CICS Transaction Server 1.1 and above."
  
  The Default is SQLCODE.
  
  Under the STRTWT description, AUTO is highlighted as
  the default. Under the YES parameter, the description is
  changed as follows:
  
     Directs the attachment facility to wait...At that time,
     the initialization of the CICS attach completes.
     However, the attachment facility can be terminated by
     the DSNC STOP command while it is waiting for DB2.
  
     Under the AUTO parameter description, the last
     sentence is changed as:  "This keyword is valid for
     CICS Transaction Server 1.1 and above."
  
     The default is AUTO.
   ============================================================
  Version 4 Book Title:  Installation Guide
  Pages: 2-367
  
  Change Description:
    Add as a last line under explanations for
    parameters PLANI and PURGEC in the chapter
    on CICS.  This sentence is already added for
    parameter TXIDSO from an earlier forum append.
  
  "This parmeter is only valid for CICS 4 and subsequent
  releases."
  ============================================================
  continued in II11038.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• CLOSE FOR INTERNET VIEWING
  

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