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

APAR status

• Closed as canceled.

Error description

• This APAR documents changes to the DB2 Administration Guide
  Volume 1 SC26-4888-00 which did not make Version 3 GA pubs.
  This information is continued from II07478, II07866 & II08170.
  This info. is continued in II08603.
  5740xyr00 R310
  ================================================================
  Version 3 Book Title: DB2 Administration Guide, Volume I
  Pages: 2-56
  Change Description:
  Add the following paragraph before 'Sharing SMP/E Data
  Sets with IMS'.
    Sharing SMP/E Data Sets with CICS:
  
    The CICS - DB2 attachment facility feature (JCI4106)
    on the CICS Version 4 product tape contains some macros
    with the same name as macros on the DB2 tape.  To
    prevent existing modules with the same names from
    being overwritten, do not install CICS/ESA V4 into the
    same target and distribution zones as DB2.
  ===============================================================
  Version 3 Book Title: Admin Guide, Vol. I
  Pages: 2-126
  Change Description:
  Additional information about the Coded Character Set.
  Replace the paragraph beginning with 'Warning:'
  with the following text:
     WARNINGS:
    If MIXED DATA = YES, you must specify one
  of the EBCDIC Mixed Data CCSIDs listed in
  table 231 on page X-173.  An error occurs
  if you do not specify a CCSID or if the CCSID
  you specify is not listed in table 231.
    If you specify a CCSID that does not appear
  as a value of SYSSTRINGS.OUTCCSID, an error
  occurs when SYSSTRINGS is accessed by DB2 to
  determine if a conversion is provided.  The CCSID
  is probably incorrect and is probably not a
  valid EBCDIC SBCS CCSID.  If it is correct,
  conversions can be provided by adding rows to
  SYSSTRINGS as explained in Appendix G on page
  X-176.
    If you specify a CCSID that appears as a value
  of SYSSTRINGS.OUTCCSID, but the CCSID is incorrect,
  data can be corrupted.  For example, assume
  the coded character set used at your site is 37,
  but you implicitly or explicitly specify 500 as
  the system CCSID.  If DB2 receives data on the
  wire with a CCSID of 500, the data can be corrupted
  because character conversion does not occur.
  Conversely, if DB2 receives data on the wire with a
  CCSID other than 500 and a conversion is provided
  from that CCSID to 500, the data can be corrupted
  because character conversion does occur.  In both
  cases, the corruption is usually limited to certain
  special characters such as brackets and braces.
    If you specify an incorrect CCSID, you can correct
  it by altering this parameter, but the alteration
  has no effect on bound SQL statements.  Bound statements
  that reference input string variables include the
  CCSID of these variables.  This CCSID is the system
  CCSID of the local DB2 at the time the statements
  were bound.  Thus, if the system CCSID is corrected
  after programs were bound, the change does not correct
  the CCSID of their input variables.  The only way to
  correct the CCSID of these variables is to rebind
  the programs.  This requirement is limited to programs
  that were bound to application servers other than the
  local DB2.  There is no need to rebind local applications
  after you change the system CCSID because the bound form
  of their SQL statements indicates that character
  conversion does not occur.
  ===============================================================
  Version 3 Book Title: DB2 Administration Guide Vol. I
  Pages: 2-178, 2-208
  Change Description:
  Add the following paragraph after the paragraph that
  begins,"If you added a STEPLIB statement to the DB2...."
    If you are assembling the DB2 macro DSN6ARVP with DBCS
  Assembler H option, add the Assembler H option NODBCS to
  steps DSNTIZA and DSNTIZP in job DSNTIJUZ.  Otherwise,
  you will receive MSGIEV202 and MSGIEV205 because the
  assembler will interpret the characters in columns 71 and
  72 as extended continuations.
  ===============================================================
  Version 3 Book Title: DB2 Admin. Guide, Vol. 1
  Pages: 2-188
  Change Description:
  
  Add the following paragraph after the first paragraph under
  'Installation Step 14: Define Temporary Work Files: DSNTITM':
  
  If you use a product that uses a semicolon as a delimiter:
  The CLIST adds SQL statements to job DSNTIJSG, but products
  that use a semicolon as a delimiting character cause
  semicolons to be removed from the installation CLIST before
  it is executed.  To correct the problem, replace the
  semicolons at the end of each SQL statement in job DSNTIJSG
  before you run the job.
  ================================================================
  Version 3 Book Title: DB2 Admin. Vol.1
  Pages: 2-234
  Change Description:
  
  In Table 54. modify RESIDENT and add NORESIDENT as follows:
  
      NORESIDENT (4)
  
      RESIDENT (6)
  
            Add the following footnote to the table:
  
  (6) Use with VS/COBOL II for CICS sample applications.
  ================================================================
  Version 3 Book Title: DB2 Admin. Guide, Vol. 1
  Pages: 2-331
  Replace the information under 'TXID=(transaction-ID)'
  with the following:
  
  Specify the transaction identification, or identifications
  for this entry.  For 'transaction ID', substitute the
  transaction identification/s found the CSD transaction
  definition.  The way you code this option depends
  on how many transactions you have and on whether:
  (1) you have different plans for each transaction;
  (2) you want to use dynamic plan allocation;
  (3) you want separate statistics for each transaction.
  
  1. If you have several transactions that use the same
     plan, you can code a list of transaction IDs, to
     be indexed to the same RCT entry.  Code your entry
     as in this example:
  
        DSNCRCT TYPE=ENTRY,TXID=(TXI1,TXI2,TXIn),PLAN=(PLNA)
  
     You cannot code more than one plan per entry.  To
     specify a different plan for each transaction,
     you must code a separate DSNCRCT entry for each plan,
     as follows:
  
        DSNCRCT TYPE=ENTRY,TXID=(TXI1),PLAN=(PLNA)
        DSNCRCT TYPE=ENTRY,TXID=(TXI2),PLAN=(PLNB)
        DSNCRCT TYPE=ENTRY,TXID=(TXIn),PLAN=(PLNC)
  
  2. With dynamic plan selection, DB2 selects a plan based
     on the DBRM of the first SQL statement, or based on a
     user-defined exit routine for dynamic plan selection.
     You can use the PLNEXIT and PLNPGME parameters to
     specify a user-defined exit routine.
  
     To use dynamic plan selection for your transactions,
     code one or more transactions per entry,
     and optionally add pointers to the PLNEXIT and
     PLNPGME parameters, as follows:
  
        DSNCRCT TYPE=ENTRY,TXID=(TXI1,TXI2,TXIn),PLNEXIT=YES
  
      or
  
        DSNCRCT TYPE=ENTRY,TXID=(TXI1),PLNEXIT=YES
        DSNCRCT TYPE=ENTRY,TXID=(TXI2),PLNEXIT=YES
        DSNCRCT TYPE=ENTRY,TXID=(TXI3),PLNEXIT=YES
  
  3. If you want separate CICS attachment facility statistics
     for each transaction, you must code a separate entry
     for each transaction, as in this example:
  
        DSNCRCT TYPE=ENTRY,TXID=(TXI1)
        DSNCRCT TYPE=ENTRY,TXID=(TXI2)
        DSNCRCT TYPE=ENTRY,TXID=(TXIn)
  ================================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-235
  Change Description:
  Change the fifth bullet under job DSNTEJ2C from:
    If you are using the CICS job DSNTEJ5C, add the
    RES option to all occurrences of PARM.COB.
  to:
    If you are using the CICS job DSNTEJ5C, add the
    RES and RENT options to all occurrences of PARM.COB.
  ================================================================
  Version 3 Book Title: Admin Guide, Volume I
  Pages: 2-298
  Change Description:
  Insert the following paragraph at the end of the
  section 'Adding CICS Routines to DB2 Load Modules':
    Once you have run DSNTIJSU for installation or
  migration, you should not have to run it again,
  even when applying maintenance to the CICS
  attachment facility modules.  If you get unresolved
  external references for DFHEAI or DFHEAI0 applications
  of a PTF, there may be a problem with your target
  library.  DSNTIJSU generally resolves external
  references for DFHEAI and DFHEAI0 in the CICS
  attachment facility load modules.
  ===============================================================
  Version 3 Book Title: DB2 Admin. Guide, Vol. 1
  Pages: 3-17
  Change Description:
  
  In Figure 88, change the MODEENT statements so that the
  continuing lines begin in column 16.  For example,
  
  DB2MODES MODETAB
  IBMDB2LM MODEENT LOGMODE=IBMDB2LM,   DB2 DEFAULT MODE...
                 TYPE=0,             NEGOTIABLE BIND...
                 SSNDPAC=X'02',     SECONDARY SEND...
                 SRCVPAC=X'00',     SECONDARY RECEIVE...
  ================================================================
  Version 3 Book Title: DB2 Admin. Guide, Vol. 1
  Pages: 3-39, 3-40
  Change Description:
  
  In Figure 94, change the APPL statements so that the
  continuing lines begin in column 16.  For example,
  
  DB1APPL  APPL   APPC=YES,...
                 ATNLOSS=ALL,...
                 AUTH=(ACQ),...
                 AUTOSES=1,...
  ================================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-11, 2-47, 2-171, 2-199
  
  Change Description:
  
  2-11   --------------------------------------------
  
  In the second paragraph under SMP/E Steps Summary,
  replace the last two sentences with:
  
    Use Information/Access or the ServiceLink facility
    of IBMLink to check the most current information
    about DB2 and other products.  Contact the IBM Support
    Center if you do not have access to IBMLink.
  
  2-47   --------------------------------------------
  
  Replace the last paragraph with:
  
    Before installing DB2, use Information/Access or the
    ServiceLink facility of IBMLink to check for PSP updates
    to the information contained in both the Program
    Directory and this book.  Refer to the Program Directory
    for PSP keyword specifications.  Be sure that you apply
    all necessary corrective service to your DB2 system before
    migrating to Version 3.  It is also a good idea to check
    monthly for PSP updates.  This way, you get the
    most current information about DB2.  Contact the IBM
    Support Center if you do not have access to IBMLink.
  
  2-171  --------------------------------------------
  
  Replace the third paragraph under Chapter 2-5.
  Installing the DB2 Subsystem with:
  
    Before proceeding with the installation steps, refer to
    the IBM DATABASE 2 Program Directory shipped with the
    product for keyword specifications for Preventive Service
    Planning (PSP).  Use Information/Access or the
    Service/Link facility of IBMLink to check the most
    current information about DB2 and other products.  Contact
    the IBM Support Center if you do not have access to
    IBMLink.
  
  2-199  --------------------------------------------
  
  Replace the last two sentences of the warning with:
  
    Check Information/Access or the ServiceLink facility of
    IBMLink for PSP information before you migrate and
    monthly for access to the most current information about
    DB2.  Contact the IBM Support Center if you do not have
    access to IBMLink.
  ================================================================
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• CLOSED 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