28.11.2012 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

PIPE SQL<br />

220 <strong>Programming</strong>: <strong>Pipes</strong><br />

are read and discarded; thus errors are not reported when null fields are<br />

selected. Null fields contain blanks or zeros as appropriate to the data field<br />

<strong>for</strong>mat. NOINDICATORS is the default <strong>for</strong> SQL INSERT.<br />

PLAN word<br />

The word specifies the plan to use.<br />

The CNMSJSQL sample contains the plan name <strong>for</strong> your level of the <strong>NetView</strong><br />

program. The plan name is in the <strong>for</strong>m DSISQLnn, where the nn suffix is the<br />

level of <strong>NetView</strong> SQL. This suffix enables you to run different levels on a<br />

single system. For <strong>NetView</strong> Version 1 Release 4, the plan name is DSISQL05.<br />

For Version 1 Release 3, the plan name is DSISQL04.<br />

DIAGN<strong>OS</strong>E<br />

The DIAGN<strong>OS</strong>E options provide additional messages describing the SQL<br />

functions as they are run. The output of DIAGN<strong>OS</strong>E is written to the<br />

secondary output stream in yellow, using a message type of 'apostrophe'<br />

(HDRTYPE). Use this option when debugging applications or at the request of<br />

<strong>IBM</strong> Software Support.<br />

TEST<br />

The TEST option enables you to run the SQL and SQSELECT stages in a<br />

testing mode. DB2 databases are not accessed by the TEST option. Diagnostic<br />

messages are issued to describe the SQL services. For DESCRIBE SELECT and<br />

SELECT requests, a constant set of all DB2 field types is generated. The TEST<br />

mode can be operated without the DSIDB2MT task or DB2 being active. For<br />

example, the command:<br />

PIPE SQL TEST DESCRIBE SELECT anything<br />

Produces a description of all of the fields generated by the test data. The<br />

command:<br />

WINDOW SQSELECT (TEST) anything<br />

Produces a window with a header line and a single record of data under each<br />

column.<br />

Note: The TEST option is best suited <strong>for</strong> understanding the conversion of<br />

internal and external <strong>for</strong>mats, whereas DIAGN<strong>OS</strong>E can be more helpful<br />

when you are testing an application being developed.<br />

SSID<br />

The SSID option enables you to access different DB2 subsystems on the local<br />

system. If the ssidname is not specified, the last subsystem specified <strong>for</strong> your<br />

task is used. If no subsystem was specified <strong>for</strong> the task, the subsystem defined<br />

by the DSIDB2MT task is used, if DSIDB2MT is active. If you specify SSID* ,<br />

the last subsystem name used by the task is reset, making the DSIDB2MT<br />

defined subsystem again the default. If you use multiple DB2 subsystems with<br />

a <strong>NetView</strong> system, consider specifying SSID (either with a name or *) in the<br />

beginning of each procedure used by that task. Another way to organize your<br />

DB2 access is to start one autotask <strong>for</strong> each DB2 subsystem and run requests to<br />

the autotasks using the <strong>NetView</strong> labeled command technique.<br />

Usage Notes<br />

Tables are loaded using SQL INSERT, queried with SQL SELECT, and maintained<br />

with SQL EXECUTE.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!