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

Using Tivoli NetView for z/OS SQL Stages for Access to DB2
338 Programming: Pipes
v The SSIDssidname option is supported.
Working with Graphic Character Strings (DBCS)
The SQL stage and the SQSELECT procedure can process graphic (DBCS) fields.
v When issuing an SQL INSERT, the shift-in and shift-out characters must be
included in the data in the VALUES clause.
v When doing an SQL SELECT, the shift-in and shift-out characters are not
returned by SQL.
v The SQSELECT procedure inserts the shift-in and shift-out characters as part of
the output fields so that values are properly displayed.
v The field sizes for graphic characters are counted by DB2 as the number of
DBCS characters, and the amount of space the field uses is 2 * (number of DBCS
characters) bytes.
v A SQL DESCRIBE SELECT request displays the number of DBCS characters in
the Field Length column. The number in the Maximum Field Length column is
the number of bytes in the record for the field. This is twice the number of
DBCS characters plus two bytes if the field has varying length. The shift-in and
shift-out characters are counted in the maximum field length (but they take up
space in the external data format.)
SQSELECT uses a column width equal to the maximum number of bytes the
data required (excluding the 2-byte varying length) plus 2 bytes for the shift-in
and shift-out characters.
Defining the Unit of Work
DB2 commits changes to the database at the end of the unit of work. The unit of
work ends with an explicit COMMIT or by reaching the end of the pipe. Unless
instructed by an option, SQL performs an explicit commit and closes the plan
when processing is complete. Use the option COMMIT when you want the unit of
work to be committed without closing the plan. Use NOCOMMIT in concurrent
SQL stages, and to treat a subsequent SQL stage as the same unit of work.
The unit of work can also be rolled back. That is, the database is restored to the
state before the unit of work began. SQL automatically rolls the unit of work back
when it receives an error code from DB2; use SQL ROLLBACK WORK to perform
an explicit rollback, possibly, in response to a pipeline error condition.
Use NOCLOSE to leave the plan open from one pipe to another on the same Tivoli
NetView for z/OS task. Because the close of the plan takes place when all
concurrent SQL stages have terminated, a NOCLOSE option used in any
concurrent stage of a pipe keeps the plan open when the pipe ends. If you use
NOCLOSE, a subsequent SQL stage can fail if it tries to change the subsystem
name, which is the SSID ssidname parameter on the SQL stage. DB2 enables only
one subsystem at a time per task.
The plan closes when none of the SQL stages specify NOCLOSE. If even one SQL
stage specifies NOCLOSE, the plan remains open.
PIPE SQL COMMIT WORK | CONS
The previous example is an example of committing the unit of work and closing
the active plan.
Note: If a plan is left open and the REXX procedure ends, the plan remains open
until a subsequent pipe closes it or the task ends. A REXX procedure might