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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQLRPGLE

Status
Not open for further replies.

debdas

MIS
Feb 12, 2003
35
IN
I have one CL program named : T1
and another on SQLRPGLE : S1

and I am calling T1 program from S1

sample program

C CALL T1
C .......
C/EXEC SQL
C DELETE .....
C/END-SQL
C SETON LR

I have compiled T1 with option 14 and seperatly it is running and I have compiled S1 through CRTSQLRPGI OBJ(DASTEST/S1) SRCFILE(DASTEST/DASTESTSRC) COMMIT(*NONE)

while compiling it is showing NO ERRORS

But, while running the program it is showing error "Error occurred while calling program or procedure dastest/T1 (C G D F)"
if pressed "D" it shows

"Application error. MCH3401 unmonitored by DO2 at statement 0000000073, inst"


CAN ANYONE TELL ME OUT WHERE I AM DOING MISTAKE
NB: ALL PROGRAMS ARE ON THE SAME LIBRARY
 
Unless T1 is defined with the program name as a named constant or as a variable which has an initial value, surround the name with single quotes.


"When once you have tasted flight, you will forever walk the Earth with your eyes turned skyward, for here you have been, and there you will always long to return."

--Leonardo da Vinci

 
I am sorry to give single quotes, pl include that. I think I am doing mistake while compilation as I have not included T1 program while CRTSQLRPGI or any other mistake ...

Pl point me out ...

 
MCH3401 means "Cannot resolve to object &3. Type and Subtype &1 Authority &4".

Next time you run it and get the error message, press F1 on the message and see what the second-level text says. Also, look for the preceding messages in the job log, they might give you a clue as to what the problem is.


"When once you have tasted flight, you will forever walk the Earth with your eyes turned skyward, for here you have been, and there you will always long to return."

--Leonardo da Vinci

 
When it comes to errors. F1 and F10 are your friends. On the error message press F1, then F10. The first message rarely gives enough information.

iSeriesCodePoet
IBM iSeries (AS/400) Programmer
[pc2]
Want to have all your bookmarks in one spot?
 
Thanks to all, it was a silly mistake. The mistake was on call statement 'T1' program was written in lower case.

Thanks once again for your kind reply

Debabrata das
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top