Peter,
The clue is
READY
DSN SYSTEM(DB2V)
READY == RUN
PROGRAM(DSNTEP2) PLAN(DSNTEP1) LIB('DB2.DBV.SDSNSAMP')
For some reas
I cannot remember from the beginning of this thread if the OP specified a
STEPLIB pointing to SDSNLOAD. Without that, TSO uses the Linklist and does not
find the DB2 program which controls the RUN command.
I think this is what the OP should have seen in the SYSOUT:
READY
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
> <05791921
יְשַׁקֵּ֖ר
From: IBM Mainframe Discussion List on behalf of
Wayne Driscoll <05791921711d-dmarc-requ...@listserv.ua.edu>
Sent: Thursday, June 6, 2024 9:52 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DSNTEP2 problem
When the DSN command processor successfull
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
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 wrote:
>
> RUN PROGRAM(DSNTEP2) PLAN(DSNTEP1) LIB('DB2.DBV.S
Relson
Sent: Thursday, June 6, 2024 7:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DSNTEP2 problem
RUN PROGRAM(DSNTEP2) PLAN(DSNTEP1) LIB('DB2.DBV.SDSNSAMP')
IKJ56712I INVALID KEYWORD, PLAN(DSNTEP1)
I'm surprised that TSO parsing (and given that we see an IKJ message, it
RUN PROGRAM(DSNTEP2) PLAN(DSNTEP1) LIB('DB2.DBV.SDSNSAMP')
IKJ56712I INVALID KEYWORD, PLAN(DSNTEP1)
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 p
SDSNSAMP is a source library. Look for a load library with a name like
.RUNLIB.LOAD and use that for your LIB parameter.
Hunter Cobb
On 6/5/2024 10:16 AM, wrote:
Thanks!
But now I get this (DSNTEP2 is in DB2.DBV.SDSNSAMP - I checked!):
READY
DSN SYSTEM(DB2V)
DSN
RUN PROGRAM(DSNTEP2) P
>> DSNE117E NOT ABLE TO LOCATE DSNTEP2 IN DSNAME DB2.DBV.SDSNSAMP
Thomas,
Looks like you are pointing to the samp lib. The LOAD module DSNTEP2 is NOT in
the SDSNSAMP library.
Here is my sample DSNTEP2 (pay attention to LIB statement)
//SYSTSIN DD *
DSN SYSTEM(DB2P)
RUN PROGRAM(DSNTEP2)
Sorry all!
Had a moment of dementia - of course I shouldn't used the source lib
With the load lib it worked much better...
Best Regards,
Thomas Berg
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send e
Thanks!
But now I get this (DSNTEP2 is in DB2.DBV.SDSNSAMP - I checked!):
READY
DSN SYSTEM(DB2V)
DSN
RUN PROGRAM(D
If it is this... please raise a doc comment with IBM on the message , and
add this reason to the actions.
Colin
On Wed, 5 Jun 2024 at 16:53, Sri Hari Kolusu wrote:
> >> IKJ56712I INVALID KEYWORD, PLAN(DSNTEP1)
>
> Thomas,
>
> You have an invalid PLAN name. Check with your DBA for the right plan
>> IKJ56712I INVALID KEYWORD, PLAN(DSNTEP1)
Thomas,
You have an invalid PLAN name. Check with your DBA for the right plan name or
if you have authority then check the SYSIBM.SYSPLAN catalog table.
Thanks,
Kolusu
--
I haven't found an appropiate discussionlist for my question (I have been out
of the loop 8 years) so I post it here (Sorry! Please redirect me if you can.)
I'm running DSNTEP2 in batch and using a JCL and command I used before (I
think...) and getting an error message I can't understand. Obvio
15 matches
Mail list logo
