II08941: 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 SC26-4888-00 which did not make Version 3 GA pubs.
  This information is continued in II07478, II07866, II08170,
  II08225, II08603, II08789 & II10141.   5740xyr00 R310 DB2
  ================================================================
  Version 3 Book Title: Administration Guide, Vol I
  Pages: 2-20, 2-143
  Add a pointer from the section on 'DASD Requirements for
  Active Log Data Sets' to 'Determining the Size of the
  Active Logs' in Section 7.  Add the same pointer from
  installation panel DSNTIPL on page 2-143.
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Page: 2-60
  Change Description:
  In the table, change message IEF0461 to IEW0461 for load
  module DSNCIAR.
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-62 and 2-63
  Change Description:
  
  Move the section "Ensure Installation of Proper
  Maintenance" to a new SMP/E step, 14: Install Proper
  Maintenance. Modify the text to read:
  
    Your Version 2 Release 3 subsystem must be at the proper
    maintenance level before you migrate to Version 3. If
    a maintenance tape was shipped with the DB2 tapes, run
    the following jobs: DSNTIJRC to RECEIVE the maintenance,
    DSNTIJAP to APPLY the maintenance, and optionally
    DSNTIJAC to ACCEPT the maintenance.
  
    Refer to the DB2 Program Directory for information
    on the proper maintenance level.
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-75
  Change Description:
  - 44 characters, including periods
  
  With these:
  
  - 44 characters if you use the TSO PROFILE setting NOPREFIX.
  - 42 characters if you use the TSO PROFILE setting PREFIX.
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-108, 2-109
  Change Description:
  The default value for MAX BATCH CONNECT on installation
  panel DSNTIPE is 20, not 40.
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-121
  Change Description:
  
  Change the first sentence under "10. DPROP SUPPORT" to
  indicate subsystem parameters EDPROP and CHGDC are for
  DataPropagator NonRelational.
  
  Replace this sentence:
  
    Specify whether you want to use Data Propagator
    (DPROP) to propagate SQL changes made to tables
    defined with DATA CAPTURE CHANGES.
  
  with this sentence:
  
    Specify whether you want to use DataPropagator
    NonRelational (DPropNR) to propagate SQL changes
    made to tables defined with DATA CAPTURE CHANGES.
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-143
  Change Description:
  
  WRITE THRESHOLD does not affect the amount of data
  lost during abends, if any. The recommendation in
  the revised paragraph comes from the Administration
  Guide.
  
  Change the description of WRITE THRESHOLD from:
  
     The larger the WRITE THRESHOLD value, the less
     often the contents of the output buffer are written
     to the active log. This generally speeds logging;
     however, an increase in the WRITE THRESHOLD can
     increase the amount of DB2 data lost if DB2 abends.
  
  to:
     The larger the WRITE THRESHOLD value, the less
     often the contents of the output buffer are written
     to the active log. We recommend not exceeding
     20% of the total number of buffer pages so that
     DB2 will not have to wait for an available buffer.
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-165
  Change Description:
    Add this entry to Table 45, the DSNZPARM Parameter
    Directory:
     (Name)     (Macro)    (Panel)  (Item)   (Page)
    MAXRBLK    DSN6SPRM    DSNTIPC      4     2-160
  ================================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-171
  Change Description:
  
  Clarify when to use the parameters for DSNYASCP,
  DXRRLM00, and DSNUTILB by replacing the two paragraphs
  before the table with these:
  
    You must ensure that you have the prerequisite
    MVS level installed. Do not overwrite the
    MVS-supplied entries for DB2 and IRLM in the MVS
    program properties tables (PPT).
  
    The program properties table (PPT) must contain
    entries for modules DSNYASCP, DXRRLM00, and
    DSNUTILB. MVS supplies default values for those
    modules.  If you have modified or deleted the
    default values, you must enter the original values
    in the PPT by modifying SYS1.PARMLIB member SCHEDxx.
    Use the following parameters for DSNYASCP, DXRRLM00,
    and DSNUTILB:
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-177, 2-208
  Change Description:
  Add this sentence to the end of the third paragraph
  of Installation Step 5 and the second paragraph of
  Migration Step 12:
  
    The MVS=XA parameter in macro DSN6ENV is no longer used,
    so no changes are necessary.
  ==============================================================
  Version 3 Book Title:  Administration Guide, Vol. 1
  Pages:  2-205
  Change Description:
  
           The 3rd bullet, last line says:
           Issue the commands:
           -DISPLAY DATABASE(DSNDB01) SPACENAM(*) RESTRICT
           -DISPLAY DATABASE(DSNDB06) SPACENAM(*) RESTRICT
  
           These lines will be changed to read:
  
           You can determine existing restrictions by
           issuing this command:
  
           -DISPLAY DATABASE(*) SPACENAM(*) RESTRICT
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-206
  Change Description:
  
  Remove the first sentence of the second paragraph. The
  active log data sets are already VSAM LDS. This is the
  sentence to remove:
  
    If you complied with the naming conventions for the
    DB2 active log data sets, and have kept their input
    parameters current, the migration to VSAM LDS is not
    apparent.
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-216
  Change Description:
  
  Add this passage before the paragraph beginning "If all
  of the local DB2 objects..."
  
   If you want to test DB2 Version 2.3's PL/I ISPF/CAF phone
   application under Version 3, you must BIND the ISPF/CAF
   phone application with the Version 3 plan name by
   changing the BIND command in job DSNTEJ3P step PH03PS03
   to reference PLAN(DSN8SP31) and rerun that job step.
  ============================================================
  Version 3 Book Title: Administration Guide
  Pages: 2-231
  Change Description:
  
  Add this passage after the first sentence on the page:
  
    During verification, run all sample applications under the
    same user ID; this user ID must have SYSADM authority.
    Otherwise, errors may occur.
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-234
  Change Description:
  
  Rename Table 54 to "Options for COB2, COBOL/370, and
  COBOL for MVS & VM".
  
  Add this statement after the table:
  
    If you compile the COBOL sample programs using COBOL
    for MVS & VM Version 1 Release 2 or above, specify the
    option WORD(NOOO). This causes the compiler to use a
    reserved word table without any variables defined in
    the sample applications.
  
  Add COBOL for MVS & VM to the list of acceptable compilers
  in this sentence:
  
    COBOL programs can use the VS COBOL II compiler or the
    IBM SAA AD/Cycle COBOL/370 (COBOL/370) compiler.
  
  The new sentence reads:
  
    COBOL programs can use the VS COBOL II compiler, the
    IBM SAA AD/Cycle COBOL/370 (COBOL/370) compiler, or
    the COBOL for MVS & VM compiler.
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-237
  Change Description:
  Replace the first bullet with this:
  
    Change to compiler module name from EDCCOMP to EDCDCvrm,
    where vrm is the version, release, and modification of
    your C compiler. For example, if you are using Version 1
    Release 2, change EDCCOMP to EDCDC120.
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-256
  Change Description:
  At the end of this paragraph:
    The distributed application using application-directed
    access is executed as part of Phase 6.  The application
    was prepared as part of Phase 3. Before this application
    can be run, you must run job DSNTEJ6 at both the local
    and remote sites.
  Add this sentence:
    Verify that your VTAM APPL statement has the
    SYNCLVL=SYNCPT defined to allow updates at several
    locations.
  ================================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-289
  Both bullets on this page must be done, not
  one or the other.
  Change Description:
  
  Replace the paragraph that begins,"If you have not
  included...." with:
  
    If you have not included the DB2 load libraries
    in your LNKLSTxx, you must add STEPLIB statements
    to your startup procedures and add DSN310.SDSNLOAD
    to the DFSESL DD statement.
  
  Change the second bullet to:
  
    Add the ddname DFSESL DD statement for
    DSN310.SDSNLOAD. All libraries specified on the
    DFSESL DD statement must be APF-authorized. The
    DFSESL DD statement is not required by DB2 DL/I
    batch support. IMS requires that an IMS RESLIB DD
    statement also be referenced by the DFSESL DD
    statement, as in the following:
  
      //DFSESL    DD    DSN=ims_reslib,DISP=SHR
      //          DD    DSN=DSN310.SDSNLOAD,DISP=SHR
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-290
  Change Description:
  
  In the paragraph which begins,"One SSM member can
  be shared...." replace:
  
    Fields are keyword and are delimited by commas.
  
  with:
  
    Fields for IMS Version 4.1 or later are keyword
    or positional and are delimited by commas.
  ============================================================
  Version 3 Book Title: Administration Guide, Vol. I
  Pages: 2-293
  Change Description:
  
  In the last cell of the table, replace the first
  sentence with this one:
  
    Applications scheduled in this region can access
    only external subsystems identified in both SSMs.
  ============================================================
  This APAR is continued in II10141.
  

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