IBM Tivoli NetView for z/OS Programming: Pipes - IBM notice

Using Tivoli NetView for z/OS SQL Stages for Access to DB2
334 Programming: Pipes
SUBSYSTEM=DB2
The SUBSYSTEM definition identifies which DB2 is the Tivoli NetView for z/OS
default. The DB2ACESS definition sets which DB2 interface is used for the Tivoli
NetView for z/OS program unless the DB2SEC statement in the CNMSTYLE
member is set to RRS or CAF. In either case, the setting is applied the first time
either definition is processed, and the interface is not changed while the Tivoli
NetView for z/OS program is running.
v The Tivoli NetView for z/OS SQL stage must be defined to DB2. The Tivoli
NetView for z/OS SQL stage is defined once in a process called binding the
plan. Sample CNMSJSQL contains a sample installation job to perform this
process. In the following sample job, the name of the library on the SYSUT2 JCL
statement must match the name specified in the BIND statement in the second
step of the job. The sample uses the name USER2.DBRMLIB, which you can
modify to suit your system:
//SYSUT2 DD DSN=USER2.DBRMLIB(DSISQLDO),DISP=SHR
The following sample shows the BIND statement:
BIND PACKAGE(DSISQL04) MEM (DSISQLDO) ACT(REF) -
ISOLATION(CS) LIB(’USER2.DBRMLIB’) OWNER(USER2)
BIND PACKAGE(DSISQL14) MEM(DSISQLDP) ACT(REF) -
ISOLATION(CS) LIB(’USER2.DBRMLIB’) OWNER(USER2)
BIND PLAN(DSISQL04) ACT(REF) -
PKLIST(DB2L01.DSISQL04.DSISQLDO,DB2l01.DSISQL14.DS
ISQLDP) ISOLATION(CS) OWNER(USER2)
DSISQL04, DSISQLDO and DSISQLDP are Tivoli NetView for z/OS names that do not
change. Change IBMUSER to a value suitable to your installation to identify the
Tivoli NetView for z/OS system that is using SQL. In general, the Tivoli
NetView for z/OS plan name is DSISQLnn where nn is changed because of
service or future releases. The CNMSJSQL sample is reshipped when a change to
the DSISQLDO and DSISQLDP programs causes the plan to be incompatible.
To run CNMSJSQL, the job user ID must have BINDADD privilege.
v The Tivoli NetView for z/OS job must access DB2 load libraries. Sample
CNMSJ009 contains comments, in the STEPLIB DD statements, to help you
modify your production procedure.
v If you use Distributed Relational Database Access (DRDA ® ), ensure that all other
systems know about Tivoli NetView for z/OS SQL stages. Unload the plan from
the system where you have installed Tivoli NetView for z/OS SQL stages and
bind it to the other systems.
v You must be registered as a DB2 user to query a table. Contact your database
administrator to determine whether you are registered. When you have connect
authority, you can query tables.
v To create tables, you must have a TABLESPACE or write privileges to a space
owned by another user. Your database administrator can allocate space.
v You can define the level of DB2 access with the DB2SEC statement in the
CNMSTYLE member.
If DB2SEC is set to RRS, the Tivoli NetView for z/OS program loads the RRS
interfaces and you have operator-level security checking. You can then access
multiple DB2 subsystems on your system.
If DB2SEC is set to CAF, the Tivoli NetView for z/OS program loads the CAF
interfaces. You do not have operator level security, but you can continue to
access multiple DB2 subsystems on your system.
When the RRS or CAF interfaces are loaded, tasks can access DB2 directly
without needing the DSIDB2MT task. DSIDB2MT must remain active for tasks
that access the DB2 subsystem that DSIDB2MT accesses. When starting the