It's a Db2 bug, maybe made worse by the way parsing works. The message means that the bind for the plan specified doesn't match the Db2 level being executed. Full employment for Db2 DBAs.
On Thu, Jun 6, 2024 at 9:58 PM Peter Relson <[email protected]> wrote: > <snip> > RUN PROGRAM(DSNTEP2) PLAN(DSNTEP1) LIB('DB2.DBV.SDSNSAMP') > IKJ56712I INVALID KEYWORD, PLAN(DSNTEP1) > </snip> > > I'm surprised that TSO parsing (and given that we see an IKJ message, it > seems that TSO parsing is being used, not necessarily by TSO itself) would > consider a "bad value" (especially when the possible values are not > knowable to a parser) to be an "INVALID KEYWORD" (as opposed to if the user > had coded PLANN(DSNTEP1) it might have complained that PLANN was an invalid > keyword. > > Peter Relson > z/OS Core Technology Design > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
