On Tue, 1 Nov 2016 16:07:59 -0500, Janet Graff <janet.gr...@yahoo.com> wrote:
> DSN SYSTEM(DBAG)
>
>DSN
>
> BIND PACKAGE(DB2ZP) MEMBER(ZPDB2) ACT(REP) ISO(CS) CURRENTDATA(YES)
> ENCODING(EBCDIC)
>DSN
>
> BIND PLAN(DB2ZP) PKLIST(DB2ZP.*) ACT(REP) ISO(CS) CURRENTDATA(YES)
> ENCODING(EBCDIC)
I don't think you need to bind your plan over and over. The way you specify the
package list, new versions of the package will be picked up. But that is not
the problem...
>DSN
>
> RUN PROGRAM(DSNTIAD) PLAN(DSNTIA10) LIB('DSNA10.DBAG.RUNLIB.LOAD')
>
>DSN
>
> END
>
>READY
>
>END
>
> DSNTIAD - SAMPLE DYNAMIC SQL PROGRAM 2.0
>
> DROP TABLE JIG.TESTDB2
>DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION
>
> CREATE TABLE JIG.TESTDB2
> (MYAUTO CHAR(16) FIELDPROC VSHFPX01 ('CRYPTID=@WAGA@MYAUTO'),
> MYCCN CHAR(16) FIELDPROC VSHFPX01 ('CRYPTID=@WAGA@MYCCN'),
> MYSSN CHAR(11) FIELDPROC VSHFPX01 ('CRYPTID=@WAGA@MYSSN'),
> MYSST CHAR(16) FIELDPROC VSHFPX01 ('CRYPTID=@WAGA@MYSST'))
> IN VOLTTEST.VOLTTAB
>DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION
>
> DROP TABLE JIG.TESTDB22
>DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION
>
> CREATE TABLE JIG.TESTDB22
> (MYAUTO CHAR(16),
> MYCCN CHAR(16),
> MYSSN CHAR(11),
> MYSST CHAR(16))
> IN VOLTTEST.VOLTTAB
>DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION
>
I am not getting the DROP/CREATE table part here... Are these the tables that
are used in your program? Because if they are, then dropping them will
invalidate all packages accessing them. And re-creating the tables will *not*
rebind your packages. After all, even if they have the same name, your tables
will be different, new objects. And any program that uses the invalidated
packages will fail...
Cheers,
Jantje.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
