II11919: GETTING THE CONTROL CENTER UP AND RUNNING FOR USE WITH A DB2 UDB FOR OS/390 SUBSYSTEM.

APAR status

• INTRAN

Error description

• 5740xyr00 R610 V6 DB2
  JDB661D, DSNTIJCC, DSNACCMD, DSNACCQC, DSNACCMG, DSNACCAV,
  INSTALLATION, 'CONTROL CENTER', '390 ENABLEMENT', 'STORED
  PROCEDURE', DSNTIJSG
  ================================================================
  IBM DB2 Workstation Control Center provides support to help you
  manage DB2 databases on an array of operating systems in your
  workplace.  A set of stored procedures must be installed at each
  DB2 UDB for OS/390 subsystem that you want to work with using
  Control Center.  390 Enablement provides these stored procedures
  in the form of an SMP/E installable package.  The FMID for the
  390 Enablement feature of DB2 UDB for OS/390 is JDB661D.
  
  IBM provides two sample procedures for you to use to define the
  stored procedures that are needed by the workstation Control
  Center:  DSNTIJCC and DSNTIJSG.  When SMP/E applies the 390
  Enablement installation package, DSNTIJCC is added to the DB2
  target data set SDSNSAMP.  Sample job DSNTIJSG is not shipped
  with 390 Enablement.  It is part of the base feature of DB2 UDB
  for OS/390 and is also a member of data set SDSNSAMP.
  
  Run sample job DSNTIJSG to register and bind DB2 stored
  procedures DSNUTILS and DSNWZP to the DB2 system.  These
  sample procedures are required by Control Center.
  
  After you have run job DSNTIJSG, modify sample procedure
  DSNTIJCC to add a job card for your OS/390 system. Also, tailor
  it for your environment by updating the following strings with
  values that are correct for your installation:
  
  SYSTEM(DSN)
  Replace DSN with the DB2 subsystem identifier
  
  PLAN(DSNTIA!!)
  Replace DSNTIA!! with the DSNTIAD plan name that was bound
  during installation by job SDSNSAMP(DSNTIJTM)
  
  LIBRARY(DSN!!0.RUNLIB.LOAD)
  Replace DSN!!0 with the user-defined prefix that was used during
  installation by DSNTINST CLIST.
  
  LIBRARY(DSN!!0.SDSNDBRM)
  Replace DSN!!0 with the user-defined prefix that was used during
  installation by DSNTINST CLIST.
  
  Finally, run sample procedure DSNTIJCC to register the 390
  Enablement stored procedures to your DB2 subsystem and to bind
  the packages required by these stored procedures to DB2.  This
  is required to activate the 390 Enablement package.
  
  Consult the DB2 for OS/390 Installation Guide, GC26-9008, for
  more information about the jobs that were run when DB2 was
  installed.
  
  To run the 390 Enablement installation job, you must have a user
  ID with authorization to bind the application packages and to
  update the SYSIBM.SYSROUTINES catalog table.  A user ID with
  SYSADM authorization satisfies this requirement.
  
  After you run sample job DSNTIJCC, you must refresh the DB2
  stored procedures address space for the changes to take affect.
  Use the START and STOP PROCEDURE(*.*) DB2 commands to
  refresh the stored procedures address space.
  
  Perform the following Control Center tasks to verify setup of
  the 390 stored procedure environment for Control Center:
  
  *  Select an MVS subsystem and double-click on the buffer pool
  object.  A list of buffer pools for the subsystem should appear
  in the list pane.
  
  *  Select an MVS subsystem and click once on the right mouse
  button.  Choose the 'Locate' choice.  From the Locate window,
  specify object type 'Indexes'  and object state filter of
  'Runstats recommended'.  Select OK.  You should get backa list
  of indexes for which Runstats is recommended.  Select Help for
  more information.
  
  *  Select an MVS subsystem.  Use the right mouse button to
  select 'Display Subsystem Parameters'.  You should get back a
  list of install panels and corresponding parameters and values.
  
  *  Select Catalog Tables object.  Use right mouse button to
  select Query.   Use the dropdown to select 'Without Stospace
  Information'.  Select OK.
  
  *  Expand Databases object.  Expand database DSNDB06.  Select
  Table Spaces object.  Choose any table space and use the right
  mouse button to select 'Report...'.  A valid report summary
  should be returned.
  

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