DB2 V7 z/os - Transferring Runstats info

Jeff Wolters

DB2 V7 z/os - Transferring Runstats info

December 4, 2007 10:03 AM

Does anyone know how or a utility that can be used, to run SQL
input,
that is larger than 80 bytes?

I'm trying to move statistics from one DB2 subsystem to another
(prod to
test). I have the four SQL queries from the Administration Guide
Vol 2
(see below). I've tried using SPUFI, DSNTEP2 & DSNTIAD,
CA-Unicenter
DB2 products(Platinum),
But all have limitations on the length of the input. (And I didn't
see
any parameters to override the length).
The SQL to build the SQL, to do the updates, creates update
statements
that are
Almost 180 bytes long.

IDUG is pleased to announce a series of upgrades to the DB2-L
discussion listserv that are being implemented to improve
reliability and the overall user experience of DB2-L. These changes
are coming on November 30th. Details at http://www.idug.org

David Seibert

In SPUFI and DSNTEP2, you can use continuation:
You don't need any special continuation character. Just put the
name in
quotes and run it all the way to col. 72 and resume in col. 1.
Subsequent testing shows you don't even need quotes.
CREATE PROCEDURE

"SPWITHREALLYLONGNAME
The contents of this e-mail are intended for the named addressee
only. It contains information that may be confidential. Unless you
are the named addressee or an authorized designee, you may not copy
or use it, or disclose it to anyone else. If you received it in
error please notify us immediately and then destroy it.

Does anyone know how or a utility that can be used, to run SQL
input,
that is larger than 80 bytes?

I'm trying to move statistics from one DB2 subsystem to another
(prod to
test). I have the four SQL queries from the Administration Guide
Vol 2
(see below). I've tried using SPUFI, DSNTEP2 & DSNTIAD,
CA-Unicenter
DB2 products(Platinum),

But all have limitations on the length of the input. (And I didn't
see
any parameters to override the length).
The SQL to build the SQL, to do the updates, creates update
statements
that are
Almost 180 bytes long.

IDUG is pleased to announce a series of upgrades to the DB2-L
discussion listserv that are being implemented to improve
reliability and the overall user experience of DB2-L. These changes
are coming on November 30th. Details at http://www.idug.org

Steen Rasmussen

Dave - I believe his INPUT dataset has a RECL greater than 80 byte
which
is the problem - I'm currently looking into how ISQL or Batch
Processor
can deal with this - is this a correct assumption Jeff ?

You don't need any special continuation character. Just put the
name in
quotes and run it all the way to col. 72 and resume in col. 1.
Subsequent testing shows you don't even need quotes.

CREATE PROCEDURE
"SPWITHREALLYLONGNAME

IMPORTANT NOTICE:

IDUG is pleased to announce a series of upgrades to the DB2-L
discussion
listserv that are being implemented to improve reliability and
the
overall user experience of DB2-L. These changes are coming on
November
30th. Details at http://www.idug.org

IDUG is pleased to announce a series of upgrades to the DB2-L
discussion listserv that are being implemented to improve
reliability and the overall user experience of DB2-L. These changes
are coming on November 30th. Details at http://www.idug.org