II11978: CHANGES TO DB2 R410 INSTALL GUIDE SC26345600 THAT DIDN'T MAKE GA V4.1 PUBS. IN II09154,II09481,II09788,II10228,II10827,II11038

APAR status

• INTRAN

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 II09154,II09481,II09788,II10228,II10827,II11038
  ================================================================
  Version 4 Book Title: Installation Guide
  Pages: 2-211
  
  Replace the description of scope and group attach with:
  scope The 1-character scope for the command prefix.  DB2
        registers its command prefix with MVS. When this is
        done,the scope of the command prefix is controlled
        by the value you choose:
  S  Started, and register the prefix with Sysplex scope at DB2
     startup instead of during MVS IPL. This is the default.
  
     Recommendation: Choose S, which allows you to have a
     single IEFSSNxx parmlib member to be used by all MVS
     systems in the Sysplex. It also simplifies the task of
     moving a DB2 from one system to another; you can stop DB2
     on one MVS and start it up on another. There is no need
     to re-IPL the system.
  
  M  MVS system scope, and register the prefix during MVS IPL.
  
  X  Sysplex scope, and register the prefix during MVS IPL.
     This means this DB2 cannot be restarted on another MVS
     without changing the definitions and re-IPLing both MVSs.
  
  For more information about the command prefix facility of MVS,
  see OS/390 MVS Planning: Operations.
  
  group-attach The group attachment name, used for data sharing.
             You can specify this on installation panel DSNTIPK.
  ============================================================
  Version 4 Book Title: Installation Guide
  Page: 2-257
  Replace section Running V3 sample jobs with the following:
  
  Run your Version 3 sample applications on your DB2 Version 4
  subsystem, and then run the Version 4 sample jobs on your
  DB2 Version 4 subsystem.
  
  If all of the local DB2 objects from Version 3 still exist
  (that is, if you have not run job DSNTEJ0), follow the
  procedure below to test migration to Version 4:
  
  If you have already deleted the DB2 sample objects, run phases
  1 through 3 of the Version 3 DSNTEJxx jobs.  Specifically,
  you need to run jobs DSNTEJ1, DSNTEJ1P, DSNTEJ2A, DSNTEJ2C,
  DSNTEJ2D, DSNTEJ2P, DSNTEJ2F, and DSNTEJ3P.  Then follow
  the procedure below:
  
  1. Change the JOBLIB statements to point to the version 4
  SDSNLOAD library.
  
  2. Do not run job DSNTEJ0.
  
  3. Copy the DSN8EAE1 module you  created when you originally
  ran the Version 3 sample jobs to the version 4 SDSNEXIT
  library.  DSN8EAE1 is an EDITPROC used by the employee
  sample table.
  
  4. Execute the RUN statements in step PH01PS02 of job DSNTEJ1P.
  Performing this step runs job DSNTEP2 from Version 3.
  
  5. Test migration of the IVP phase 2 applications from V3:
  a. DSNTEJ2A: Perform all but the first 2 steps of job DSNTEJ2A
     Expect a return code of 4 because table spaces
     DSN8D31U.NEWDEPT and DSN8D31U.NEWPHONE are placed in copy
     pending states.
  b. DSNTEJ2C: Execute only the RUN PROGRAM(DSN8BC3)
     PLAN(DSN8BH31) statement in step PH02CS04.
  c. DSNTEJ2D: Execute only the RUN PROGRAM(DSN8BD3)
     PLAN(DSN8BD31) statement in step PH02DS03.
  d. DSNTEJ2F: Execute only the RUN PROGRAM(DSN8BF3)
     PLAN(DSN8BF31) statement in step PH02FS03.
  e.  DSNTEJ2P: Run only step PH02PS05.
  
  6. Test migration of the IVP phase 3 applications from V3:
  a. Do not run job DSNTEJ3C.
  b. Edit Version 3 SDSNSAMP library member DSNTESA and insert
     the following at the beginning:
         DROP TABLESPACE TEMPSPAC;
  c. Run step 4 of job DSNTEJ3P.  Expect a return code of 8
     because of the rollback processing in this step.
  d. If you want to test the DB2 Version 3 ISPF/CAF applications
     under Version 4, you must place the version 3 SDSNSPFP
     panel library ahead of the Version 4 SDSNSPFP panel
     library in the ISPPLIB concatenation.  This is necessary
     in order for the plans migrated from Version 3 to be used.
     Be sure to remove the Version 3 SDSNSPFP library from your
     ISPPLIB concatenation when you are finished testing the
     Version 3 IVP applications under Version 4.
  
     See the DB2 Version 3 Admin Guide for directions on how to
     start and run the Version 3 ISPF/CAF applications.
  
  7.  Do not run any other Version 3 IVP jobs.
  ============================================================
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

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