II07866: CHANGES TO DB2 ADMINISTRATION GUIDE VOLUME 1, SC26-4888-00 THAT DID NOT MAKE V3 GA PUBS. CONT. OF II07478, II08170, II08225, ETC

APAR status

• Closed as canceled.

Error description

• This APAR documents changes to the DB2 Administration Guide
  Volume 1 SC26488800 which did not make Version 3 GA pubs.
  Continuation of Info. APAR II07478.  Continued in II08170,
  II08225, II08603.    5740xyr00 R310
  ================================================================
  Version 3 Book Title: DB2 Admin. Guide, Vol. 1
  Pages: 2-30
  Change Description:
  
  Replace the formula for calculating virtual storage for
  DSNDBM1 with:
         dictionary size (number of entries) x 16 bytes
  ================================================================
  Version 3 Book Title:  DB2 Admin. Guide, Vol. 1
  Pages: 2-76
  Change Description:
  
  Remove the following sentence from the first paragraph under
  '5.SUFFIX':
  
  'If there is a suffix, the prefix and suffix together cannot
     exceed 17 characters.'
  ================================================================
  Version 3 Book Title: DB2 Admin. Guide, Vol. 1
  Pages: 2-80
  Change Description:
  
  Remove paragraph that begins with:
  'We recommend that you do not modify this data set name ...'
  ================================================================
  Version 3 Book Title: DB2 Admin. Guide, Vol. 1
  Pages: 2-186
  Change Description:
  
  Under 'Installation Step 10:  Connect IMS to DB2 (Optional)',
  change the second bulleted item to:
  
  o Define DB2 to IMS
  
  Under 'Installation Step 11:  Connect CICS to DB2
  (Optional)', change the second bulleted item to:
  
  o Define DB2 to CICS using the RCT
  ================================================================
  Book Title:  DB2 Admin. Guide, Vol. 1
  Page Number:  2-200
  Change Description:
  
  In the second paragraph, after 'This ensures that the table
  space pages are physically correct and the catalog table
  spaces are clustered.', add:
  
  'When you run this utility on DSNDB06.SYSPKAGE, you get
  message DSN1985I because SYSKAGE is a segmented table
  space.  You can ignore this message.'
  ================================================================
  Admin. Guide Vol. 1 SC26-4888-00
  page 2-200
  The last line in paragraph 3 is incorrect it should read as
  follows.  Contact your IBM services representative if either of
  these queries returns a COUNT greater than 0 (zero).  The
  message number issued is msgDSNE610i.
  ===============================================================
  Admin. Guide Vol. 1 SC28-4888-0
  page 2-201
  At end of page.  The last sentence in the last paragraph
  should read:  Executing queries on mirror copies can
  dramatically reduce contention on the catalog, especially for
  those catalog tables that are very large, and can improve
  performance because of the extra indexes that you can define
  for the mirror copy.
  
  Following the previous sentence add this sentence: If any
  PLANs have been bound with empty DBRM members queries 31 and
  33 will return rows indicating an entry in DB2 catalog table
  SYSIBM.SYSPLAN but no related entry in catalog tables
  SYSIBM.SYSDBRM or SYSIBM.SYSSTMT.
  ===============================================================
  Version 3 Book Title: DB2 Admin. Guide, Vol. 1
  Pages: 2-204 and 2-205
  Change Description:
  
  Change the last sentence of the 5'th paragraph
  on page 2-204 to:
  'For the DB2 subcommands that permit LISTS of plan
  names, package names, DBRMs, and ENABLE and DISABLE
  statements, DB2I provides ISPF tables to contain all
  the user-specified variables for these subcommand
  keywords.'
  
  Change the third member name in the first column of
  Table 50 on page 2-204 from 'DSNDBRMS' to 'DSNPLPKN'.
  
  Add the following paragraph under the ALLOC statement
  at the top of page 2-205:
  'If you do not allocate the DSNSPFT data set and
  connect it to ISPF, DB2I allocates a temporary data
  set for the ISPF table library members at DB2I startup.
  DB2I deletes this temporary data set when the ISPF session
  is terminated.'
  ================================================================
  Admin. Guide Vol. 1  SC26-4888-00
  page 2-206
  Add the following sentence to the end of Migration Step 8:
  Define Non-VSAM Data Sets: DSNTIJIN.  Because these datasets
  are in use frequently, do NOT migrate them with DFSMShsm.
  ===============================================================
  Book Title:  DB2 Admin. Guide, Vol. 1
  Page Number: 2-213
  Change Description:
  
  Replace the paragraph that begins with 'Because this is the
  first time DB2 Version 3 is started . . . ' with the following:
  If you used buffer pools other than BP0 for your DB2
  Version 2 Release 3 subsystem, you get a message that the
  buffer pool you specified is invalid.  You can ignore this
  message because your buffer pools are defined when you
  run job DSNTIJTM.
  ================================================================
  Admin. Guide Vol. 1 SC26-4888-00
  page 2-215
  Under Migration Step 20: Prepare Dynamic SQL Program: DSNTIJTM
  replace the second paragraph with the following:
  'DSNTIJTM creates as many temporary table spaces
  as you specified on panel DSNTIPD.  The default is 1 4K
  table space and 1 32K table space.  You can also edit
  DSNTIJTM to include more table spaces.  When this is done,
  the DSNTIJTM job restarts the DSNDB07 database.'
  ===============================================================
  Version 3 Book Title: DB2 Admin. Guide, Vol. 1
  Pages: 2-216
  Change Description:
  
  Replace the second paragraph under 'Migration Step 22' with
  the following:
  
  'Modify the instructions in this documentation as follows:
   o Change all Version 2 Release 3 references to Version 3.
   o Delete table space SYSIBM.SYSUTIL
   o Include the new Version 3 catalog table spaces that need
     to be copied:  SYSIBM.SYSUTILX and SYSIBM.SYSSTATS.'
  ================================================================
  Version 3 Book Title: DB2 Admin. Guide, Vol. 1
  Pages: 2-219
  Change Description:
  
  Replace the heading 'Clean Up Catalog Visisbility Objects'
  with 'Clean Up Objects' and add the following information:
  
  'DB2 Version 3 no longer uses the SYSUTIL VSAM dataset. You
  can delete SYSUTIL after you are sure you will not fall back
  to Version 2 Release 3.'
  ================================================================
  Admin. Guide Vol. 1 SC26-4888-00
  page 2-220
  Under Other Operational Considerations sub-topic For
  Distributed Data the second sentence regarding the RACF router
  is incorrect and should be deleted.
  ===============================================================
  Version 3 Book Title: DB2 Admin. Guide, Vol. 1
  Pages: 2-242
  Change Description:
  
  Add this sentence to the first paragraph under
  'Job DSNTEJ2D':
  
  'Note that you must have sequence numbering on to run this
  job from an ISPF edit session.'
  ===============================================================
  Book Title:  DB2 Admin. Guide, Vol. 1
  Page Number: 2-244
  Change Description:
  
  Change the first sentence of '5.' to:
  
  'Enter the library name prefix.NEW.SDSNSAMP(DSNTESA) as
  input on line 1, the DATA SET NAME parameter.'
  ================================================================
  DB2 Admin. Guide Volume 1
  page 2-290
  Add the following to the end of the fifth paragraph:
  The following examples show how to define fields for IMS
  Version 4.1.  Fields are keyword, and are delimited by commas.
  For previous releases of IMS, fields are positional.  For more
  information, see the 'IMS Customization Guide: System' from
  the appropreate release.
  ===============================================================
  Version 3 Book Title:  DB2 Admin. Guide, Vol. 1
  Pages: 2-297, 2-298
  Change Description:
  
  Change the first sentence in the last paragraph on page
  2-297 to:
  
  'If you specified CICS Version 3 Release 1 Modification 1
  or later and left fields 7-10 blank on panel installation
  panel DSNTIPV, the LOADCSD step of DSNTIJSU is commented
  out, using the "//" job termination characters.'
  
  Add the following after the first sentence on page 2-298:
  
  'If you specified CICS Version 2 Release 2 Modification 2
  on panel DSNTIPV, the DEFINE statements in the LOADCSD
  step are deleted.  These statements are not supported
  in that release of CICS.'
  ================================================================
  Book Title: DB2 Administration Guide, Vol 1
  Page Number: 2-310
  
  Change Description:
  
  In Table 87 'Optional CICS Program List Table (PLT) Entries for
  DB2', change 'Final quiesce stage shutdown program' to 'First
  quiesce stage shutdown program'.
  ===============================================================
  Book Title: DB2 Administration Guide, Vol 1
  Page Number: 2-329
  
  Change Description:
  
  Replace the first sentence under 'TOKENE=NO|YES' with
  this: 'Specifies whether the facility will produce a
  DB2 accounting record for every CICS transaction, even
  those transactions that are reusing threads.'
  
  Add the following sentence to the end of the first
  under 'TOKENE=NO|YES':  'You might receive more than one
  DB2 accounting record for a CICS transaction that has
  multiple DB2 units of recovery, but you can correlate the
  CICS and DB2 records with the matching LU6.2 tokens.'
  ===============================================================
  Version 3 Book Title: DB2 Admin. Guide, Vol. 1
  Pages: 3-5
  Change Description:
  
  Replace the last sentence on the page with:
  'Again, this is not visible to you, but information about
  these protocols is in 'SNA LU 6.2. Peer Protocols
  Reference'.'
  ===============================================================
  Version 3 Book Title: DB2 Admin. Guide, Vol. 1
  Pages: 3-21
  Change Description:
  
  Replace the last sentence in the second bulleted item with:
  'You do not to populate this table for systems that use
  only application-directed access and make only requests
  of your local DB2.'
  ===============================================================
  Version 3 Book Title: DB2 Administration Guide
  Pages: 3-57
  
  Change Description:
  
  In Section 3-2, "Sharing Read-only Data,"
  add to the section "Create DB2 Storage Groups" under "Create
  DB2 objects to be shared," after the paragraph that starts
  "When creating objects on the owning DB2 subsystem".
  
  When you create the DB2 storage group, specify the serial
  numbers of the volumes that will be needed for the table
  space or index.  When a data set is defined in the shared
  read-only environment, all volume serial numbers from the
  DB2 storage group are stored in the VSAM catalog to be
  used for data set extension.
  
  If you are using SMS to manage your data sets, use an
  asterisk to specify each volume that you expect to use.
  For example, if you anticipate needing three volumes to
  extend the data set, list three asterisks in the VOLUMES
  clause of your CREATE STOGROUP statement:
  
     CREATE STOGROUP stogroupname (VOLUMES('*','*','*') ...
  
  For each asterisk, SMS uses a volume from the storage group
  that you defined for SMS.
  
  If you do not list enough volumes, data set extension fails.
  In that case, you can alter the storage group to contain
  more volumes, using the ALTER STOGROUP statement.
  New volumes added to a DB2 storage group are not available
  to a data set until you do one of the following:
   o  Issue a CREATE TABLESPACE or CREATE INDEX statement
   o  Run the LOAD REPLACE, REORG, or RECOVER utility.
  ================================================================
  This Info. APAR is continued in II08170 and II08225.
  

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