II10141: CHANGES TO DB2 ADMIN. GUIDE VOLUME 1, SC26-4888-00 THAT DID NOT MAKE V3 GA PUBS. CONT: II07478, II07866, 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.
  This information is continued from II07478, II07866, II08170,
  II08225, II08603 and II08789.   5740xyr00 R310 DB2
  ================================================================
  Version 3 Book Title: Administration Guide, Volume 1
  Pages: 2-38, 2-159
  Change Description:
  Change the formula for the Sort Pool Size calculation on
  both pp. 2-38 and 2-216 to the following:
  
     16000 x (12 + sort key length + sort data length + 4
     (if ESA hardware sort assist))
  ============================================================
  Version 3 Book Title:   Administration Guide, Volume 1
  Pages:  2-140
  Change Description:
  
   The paragraph on the subsystem recognition
   characters will be re-written to improve readability.
  ============================================================
  Version 3 Book Title: Administration Guide, Volume 1
  Pages: 2-218
  Change Description:
  
  The following is added to migration step 23 about
  release incompatibilities:
  
  SQLCODE -101
  
  After migrating to DB2 Version 3, 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 3 Book Title: Administration Guide, Volume 1
  Pages: 2-234, 2-235
  
  Change Description:
  On p. 2-234, in the section "Special Considerations for
  COBOL Programs" add the following at the end of the
  first paragraph:
  "Remember that if you are using CICS, the options you need
  to use depend on the CICS environment. To verify that you
  are using the correct options in your CICS environment,
  refer to CICS/ESA Application Programming Guide."
  
  On p. 2-234, modify the two of the table notes in Table 54
  as follows:
    Notes:
     ...
     2) Refers to job DSNTEJ5C only. See the CICS
     ...
     4) Only valid for VS/COBOL II. See the CICS
        documentation for actual options to use.
  
  
  On p. 2-235, remove the following bulleted item (fifth
  down from the top of the page):
   o If you are using the CICS job DSNTEJ5C, add the RES
     option to all occurrences of PARM.COB.
  ============================================================
  Version 3 Book Title: Administration Guide, Volume 1
  Pages:  2-255
  Change Description:
  
            Add the following text after "...change your
            DSNTIAR calls to DSNCIAR calls in DSN8MCxx
            and DSN8MPxx" under the heading "Using CICS
            Storage-Handling Facilities":
  
              Then rerun job DSNTEJ5C or job DSNTEJ5P.
  ============================================================
  Version 3 Book Title: DB2 Administration Guide, Vol. 1
  Pages:  2-304 - 2-305
  Change Description:
  
       The sentence in the 1st paragraph under heading
       Transaction Entries, which says "The RDO group
       specified on installation panel DSNTIPV is loaded
       with the RDO definitions shown in Table 89 on
       page 2-305."
  
       is changed to:
       "The RDO group specified on installation panel
       DSNTIPV is loaded with the RDO definitions, some
       examples of which are shown in Table 89, p.2-305.
       As shown in the table, DSNC is the only DB2-supplied
       transaction that is shipped with DB2.  Please refer
       to the Command and Utility Reference for
       more details on the DSNC subcommands, or the DB2
       commands you can enter directly."
  
  Administration Guide, Vol. 1, p. 2-305, Table 89.
  
       In the second row of the table, add the following
       entries:
  
       DB2 Commands entered directly
       As many as wanted, for example:
  
       CEDA DEFINE TRANSACTION(DISC)
          PROGRAM(DSNyCOM1) GROUP(DB2-group) TWASIZE(1200)
  
       CEDA DEFINE TRANSACTION(DISP)
          PROGRAM(DSNyCOM1) GROUP(DB2-group) TWASIZE(1200)
  
       CEDA DEFINE TRANSACTION(MODI)
          PROGRAM(DSNyCOM1) GROUP(DB2-group) TWASIZE(1200)
  
       CEDA DEFINE TRANSACTION(STOP)
          PROGRAM(DSNyCOM1) GROUP(DB2-group) TWASIZE(1200)
  
       CEDA DEFINE TRANSACTION(STRT)
          PROGRAM(DSNyCOM1) GROUP(DB2-group) TWASIZE(1200)
  
  Administration Guide, Vol. 1, p. 2-305, Table 89.
  
       In the second row of the table, replace
  
       "CEDA DEFINE TRANSACTION(xxxx)
          PROGRAM(DSNyCOM1) GROUP(DB2-group) TWASIZE(1200)"
  
       with the following entry:
  
       "CEDA DEFINE TRANSACTION(-DIS)
          PROGRAM(DSNyCOM1) GROUP(DB2-group) TWASIZE(1200)
  
          or any valid DB2-related command, except -STA DB2,
          using the 4 characters including the dash
          at the beginning.
          See Command & Utility Reference for all the
          valid commands. See also "Providing CICS support
          for DB2 commands for more information."
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 3-55
  Change Description:
  
  Replace this paragraph under Excluding Data Sets:
  
  You must exclude from sharing the bootstrap data set, the
  catalog and directory, and all user data sets that are not
  shared resources.  Also exclude the MVS system catalog.  To
  exclude these VSAM data sets from sharing, add entries to
  your GRS SYSTEMS exclusion resource name list.  Use
  TYPE(GENERIC) entries with QNAME(SYSVSAM) and
  RNAME(data set high level qualifier).
  
  With this paragraph:
  
  You can exclude from sharing the bootstrap data set, the
  catalog and directory, and all user data sets that are not
  shared resources.  Also exclude the MVS system catalog.  To
  exclude these VSAM data sets from sharing, add entries to
  your GRS SYSTEMS exclusion resource name list. Use
  TYPE(GENERIC) entries with QNAME(SYSVSAM) and
  RNAME(data set high level qualifier). If you do not exclude
  the data sets, VSAM and GRS ensures the data is kept safe,
  although performance might be lower.
  ============================================================
  

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