TSO is then running the TSO Run command rather than a DB2 command - taking
“PROGRAM(DSN2)” - which it expect to be a DSN - to be a PDS member and
objecting to the PLAN parameter which is not a valid parameter for the TSO
command.
Keith
> On 6 Jun 2024, at 14:52, Wayne Driscoll
> <000005791921711d-dmarc-requ...@listserv.ua.edu> wrote:
>
> When the DSN command processor successfully starts up, the command prompt
> will be DSN, not READY. this implies that the DSN command wasn't found or
> some other error occurred.
> READY
> DSN SYSTEM(DSN1)
> DSN
> -DIS THREAD(*)
> DSNV401I -DSN1 DISPLAY THREAD REPORT FOLLOWS -
> DSNV402I -DSN1 ACTIVE THREADS -
>
> Note "DSN" not "READY" after the DSN command was processed.
>
>> On Thu, Jun 6, 2024 at 7:47 AM Attila Fogarasi <
>> 000005b6fee9abb7-dmarc-requ...@listserv.ua.edu> wrote:
>>
>> 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 <rel...@us.ibm.com> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>>
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>
>
>
> --
> Wayne Driscoll
> Software Engineer | Mainframe Software Division
> Broadcom Software
>
> *Office: *630-300-1931* Mobile:* 630-247-1632
> wayne.drisc...@broadcom.com
>
> --
> This electronic communication and the information and any files transmitted
> with it, or attached to it, are confidential and are intended solely for
> the use of the individual or entity to whom it is addressed and may contain
> information that is confidential, legally privileged, protected by privacy
> laws, or otherwise restricted from disclosure to anyone else. If you are
> not the intended recipient or the person responsible for delivering the
> e-mail to the intended recipient, you are hereby notified that any use,
> copying, distributing, dissemination, forwarding, printing, or copying of
> this e-mail is strictly prohibited. If you received this e-mail in error,
> please return the e-mail to the sender, delete it from your computer, and
> destroy any printed copy of it.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
