IBM Support

II09154: CHANGES TO DB2 R410 INSTALLATION GUIDE SC26-3456-00 THAT DID NOTMAKE V4.1 GA PUBS. CONTINUED IN II09481 & II09788.

Subscribe

You can track all active APARs for this component.

 

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 II09481 & II09788.
    ================================================================
    Version 4 Book Title: Installation Guide
    Pages: 1-37, 2-82, and 2-235
    Change Description:
    p. 1-37 *****************************************
    
    Modify this paragraph:
    
      PDSE data sets must be managed by SMS, and they
      are stored on direct access storage devices.
      For information on conversion and differences
      between PDS and PDSE, see MVS/DFP: Managing
      Non-VSAM Data Sets.
    
    This is the updated paragraph:
    
      PDSE data sets MUST be managed by SMS, and they
      are stored on Direct Access Storage Devices.
      PDSE data sets are NOT allowed in cross memory
      (XM) mode, so see DFSMSdfp: Managing Non-VSAM Data Sets
      for information about how a PDSE differs from a PDS
      dataset  and for conversion instructions.
    p. 2-82 ******************************************
    Change the second paragraph from:
      Do not modify the data definition statements for
      SDSNCLST.  These libraries must be defined as
      partitioned data sets (PDS) because installation
      processing uses a TSO edit subcommand that does
      not support the partitioned data set extended (PDSE)
      format.
    to this:
    
      Do not modify the data definition statements for
      SDSNCLST or SDSNLOAD.  These libraries MUST be defined as
      Partitioned Data Sets (PDS).
    ============================================================
    Version 4 Book Title: Installation Guide
    Page: 2-27
    Change Description:
    
    Add this text under "DASD Requirements for the Archive Log
    Data Sets":
    
    Do not use DFSMS hardware compression for archiving logs to
    DASD.  DB2 uses the basic direct access method (BDAM) to
    access ARCHIVE LOGs residing on DASD.  BDAM does not support
    DFSMS compressed datasets.  Using DFSMS results in log read
    failures when attempting to recover from the archive logs.
    ============================================================
    Version 4 Book Title: Installation Guide
    Pages: 2-37  (chap2 page37)
    Change Description:
    
    The CSA size requirement for each DB2 subsystem is wrong
    in the second paragraph under "Common Service Area".
    Change "76KB" to "40KB". This is the revised passage:
    
      The residual requirement for CSA (below the 16MB line)
      is expected to be less than 40KB for each DB2 subsystem
      and 48KB for each IRLM started.
    ============================================================
    Version 4 Book Title: Installation Guide
    Pages: 2-58, 2-59  (chap2 page58 page59)
    Change Description:
    
    Remove the steps "Update the  EOYINDEX Member" and
    "Update the EOYPARM Member" from "Additional Installation
    Tasks".  These steps are not necessary.
    ============================================================
    Version 4 Book Title: Installation Guide
    Pages: 2-60  (chap2 page60)
    Change Description:
    
    Add this sentence after Table 35. Online Help Reader
    Libraries to be Concatenated:
    
      Concatenate the new DB2 ISPF command table library
      (prefix.SDSNSPFT) in with the ISPTLIB DD statements
      in your TSO logon procedures and in any of the CLISTs
      where they might be allocated.
    ============================================================
    Version 4 Book Title: Installation Guide
    Pages: 2-88 and 2-89  (chap2 page88 page89)
    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 3 subsystem must be at the proper
      maintenance level before you migrate to Version 4. 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.
    
      If your Version 3 subsystem is under MVS/XA, you
      must first upgrade to MVS/ESA. Refer to the DB2 Program
      Directory for information on the proper maintenance
      level.
    ============================================================
    Version 4 Book Title: Installation Guide
    Pages: 2-103
    Change Description:
    
    Under "Valid Data Set Name", replace this bullet:
    - 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 4 Book Title: Installation Guide
    Pages: 2-110
    Change Description:
    
    Add this sentence before the paragraph that begins
    "A change to this parameter..."
    
      The value is sometimes used during IVP processing
      to place output (from COPY TABLESPACE, for example)
      on the device type specified here.
    ============================================================
    Version 4 Book Title: Installation Guide
    Pages: 2-154  (chap2 page154)
    Change Description:
    
    Remove field 15, CURRENT DEGREE, from installation
    panel DSNTIPF.
    ============================================================
    Version 4 Book Title: Installation Guide
    Pages: 2-163
    Change Description:
    
    Replace the description for the field TIME INTERVAL
    with "No longer used."
    ============================================================
    Version 4 Book Title: Installation Guide
    Pages: 2-173, 2-211
    Change Description:
    
    These changes are for Table 55, Allowable Special
    Characters for the Command Prefix.
    - remove the comma (,) from the table
    - add the ampersand (&), which has a hexadecimal
      representation of x'50'. Add this footnote about using
      the ampersand as the command prefix:
        Accept the default command prefix of dash (-) while running
        the CLIST, then edit the job DSNTIJMV to use the ampersand
        (&) as the command prefix in the job.
    Treat the equal (=) x'7e' the same as the ampersand as to edit
    DSNTIJMV after using the default of (-) through the clist.
    This is an ISPF restriction as to the use of the (=) because
    it will take you out of the clist if you use it as a prefix, etc
    
    - add footnote to the apostrophe ('):
        To use the apostrophe ('), you must code two consecutive
        apostrophes in your IEFSSNxx member. For example, the
        entry for subsystem DB2A with a command prefix of 'DB2A
        and a scope of started looks like this:
           DB2A,DSN3INI,'DSN3EPX,''DB2A,S'
    on page 2-211
    Remove the comma from the list of valid command prefix
    characters.  Add the ampersand.
    
    NOTE: If you try to use the comma (,) as your CONCHAR, you
          will receive SSI error MSGDSN3113I and fail.
    ===============================================================
    Version 4 Book Title: Installation Guide
    Pages: 2-210  (chap2 page210)
    Change Description:
    
    Remove the second bullet under "IRLM Requirements".
    In the third bullet, remove references to all formatting
    modules except DXRRLM50.
    
    The IRLM shipped with DB2 Version 4 does not have
    these requirements.
    ============================================================
    Version 4 Book Title: Installation Guide
    Pages: 2-226, 2-227, 2-254, 2-255
    Change Description:
    
    Installation Step 13 and Migration Step 17 should be
    changed to reflect the new subsystem command prefix.
    This example uses the default, -DSN1.
    
    Change "where (-) is the subsystem command prefix you
            defined for DB2...."
    
    To "where (-DSN1) is the...."
    
    In the following lines, change "-" to "-DSN1":
    
      -DSN1 START DB2 PARM(zparmname)
            DSN9022I -DSN1 DSNYASCP 'START DB2' NORMAL COMPLETION
      -DSN1 DISPLAY DATABASE(*) SPACENAM(*) RESTRICT
    =============================================================
    Version 4 Book Title: Installation Guide
    Pages: 2-228, 2-284  (chap2 page228 page284)
    
    Some people have received error ASMA301w RC4 on jobs
    DSNTIJTM and DSNTEJ2A. The error is acceptable.
    
    Change Description:
    
      Update Table 59, DSNTIJTM Return Codes, Step DSNTIAD,
      PROCSTEP ASM to read "0000 or 0004".
    
      Update Table 74, DSNTEJ2A Return Codes, Step PREPUNL,
      PROCSTEP ASM to read "0000 or 0004"
    ============================================================
    Version 4 Book Title: Installation Guide
    Pages: 2-256
    Change Description:
    
    Add to the end of Migration Step 19:
    
      The DB2 catalog now uses SYSLGRNX instead of SYSLGRNG,
      even if you fall back. Run job DSNTIJTD to delete
      SYSLGRNG.
    ============================================================
    Version 4 Book Title: Installation Guide
    Pages: 2-257  (chap2 page257)
    Change Description:
    
    Add this passage before the paragraph beginning "If all
    of the local DB2 objects..."
    
     If you want to test DB2 Version 3's PL/I ISPF/CAF phone
     application under Version 4, you must BIND the ISPF/CAF
     phone application with the Version 4 plan name by
     changing the BIND command in job DSNTEJ3P step PH03PS03
     to reference PLAN(DSN8SP41) and rerun that job step.
    ============================================================
    Version 4 Book Title: Installation Guide
    Pages: 2-267 -- 2-277
    Change Description:
    
    Rename Table 67 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 4 Book Title: Installation Guide
    Pages: 2-280  (chap2 page280)
    Change Description:
    
    Delete the "Special Considerations for Assembler Programs"
    section. The DSNHASMH procedure was replaced by DSNHASM,
    which has the correct module name.
    ============================================================
    Version 4 Book Title: Installation Guide
    Pages: 2-337  (chap2 page337)
    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.
    ============================================================
    Version 4 Book Title: Installation Guide
    Pages: Appendix A. Sample Online Help Installation Jobs
    Change Description:
    
    The JCL in Appendix A. Sample Online Help Installation
    Jobs is no longer accurate.  Please see the DB2 Program
    Directory for current sample JCL.
    ============================================================
    continued in II09481 & II09788.
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • CLOSED FOR DB2INFO
    

APAR Information

  • APAR number

    II09154

  • Reported component name

    PB LIB INFO ITE

  • Reported component ID

    INFOPBLIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1995-12-28

  • Closed date

    1996-03-29

  • Last modified date

    1999-06-08

  • 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

[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
08 June 1999