Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

-927 calling STORED PROCEDURE in MVS

Status
Not open for further replies.

bpat

MIS
Apr 25, 2003
3
US
I get a -927 on the Mainframe (MVS) when running a stored procedure. Any ideas ? I've read the message in Messages and Codes and have SDSNLOAD in my iSPLLIB in the CLIST I'm usning to call the Main program. The DSNSPAS has a SDSNLOAD library in it's JCL also.
 
Can you post the clist that you use to call the main program?
Marc
 
Here is the Clist that I use to call TSTCAP3. TSTCAP3 is a PLI program that calls the Stored Procedure which is another PLI Program. The clist didn't paste onto this message board very well for whatever reason but here it is.

CONTROL MSG CONLIST NOFLUSH NOPROMPT SYMLIST
SET PRE = &STR(TP)
SET PREF = &STR(&PRE..&USR)
FREE DD(SYSOUT) FREE DD(SYSPRINT) ALLOC DD(SYSOUT) DA(*)
IF &SYSDSN('TP.CJ18.TSTCAPRC.SYSPRINT')=OK THEN +
DELETE 'TP.CJ18.TSTCAPRC.SYSPRINT'
ALLOC DD (SYSPRINT) DS('TP.CJ18.TSTCAPRC.SYSPRINT') NEW RECFM(F B) +
LRECL(134) BLKSIZE(5896) SP(300 300) TR
ISPEXEC LIBDEF ISPLLIB DATASET ID -
('SYSH.SPC.TESTLIB' 'CJ18.V7.SDSNLOAD.STPR')
DSN SYSTEM(DSN)
RUN PROGRAM(TSTCAP3) PLAN(TSTCAP3)
END
FREE DD(SYSOUT)
FREE DD(SYSPRINT)
 
Can't see anything wrong with the CLIST. Only thing that occurs to me is to check that your DB2 sub system is called DSN as specfified in the SYSTEM statement.
Marc
 
thanks marc,
Yea the DB2 subsystem is called DSN.
I defined the STORED PROCEDURE with a COLLID and I have the plan TSTCAP3 defined with that COLLID and Bound both the main program and the STORED PROCEDURE program using that COLLID.
 
I think that you only get a -927 if the connection to DB2 has not been established. From looking at your CLIST you have the SYMLIST CONLIST parms coded on the CONTROL statement which should give you some output. Have a look at this output and see if anything there jumps out at you. The other thing to check is to see if your DB2 subsystem is actually up and running. Try typing in the DSN command in native TSO and see if that gives any error. Also try running another program under DSN that you know works.

Sorry I can't be of more help.
Marc
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top