but when I ran this job against SSMTEP2 I got the following errors:
IEW2278I B352 INVOCATION PARAMETERS - LET,MAP,LIST
IEW2677S 5130 A VALID ENTRY POINT COULD NOT BE DETERMINED.
IEW2230S 0414 MODULE HAS NO TEXT.
IEW2677S 5130 A VALID ENTRY POINT COULD NOT BE DETERMINED.
IEW2008I 0F03 PROCESSING COMPLETED. RETURN CODE = 12.
Joined: 30 Nov 2013 Posts: 917 Location: The Universe
The Binder messages seem to say there was nothing in the data set specified by the SYSLIN DD statement. It might be related to the IEFBR14 step prino already mentioned, or the compile step, You need to check for messages from the PL/I compiler.
IBM1784I S 1313 3527.0 The ENTRY SQLDATA may not be used as a loc
since it does not have the RETURNS attribu
IBM1787I S 1497 3896.0 The ENTRY SQLIND may not be used as a oca
IBM1787I S 1540 3991.0 The ENTRY SQLIND may not be used as a loca
IBM1787I S 1543 3996.0 The ENTRY SQLDATA may not be used as a loc
IBM1787I S 1547 4004.0 The ENTRY SQLIND may not be used as a loca
IBM1787I S 1550 4011.0 The ENTRY SQLDATA may not be used as a loc
IBM1787I S 1550 4011.0 The ENTRY SQLDATA may not be used as a loc
IBM1787I S 1550 4011.0 The ENTRY SQLDATA may not be used as a loc
IBM1787I S 1578 4073.0 The ENTRY SQLDATA may not be used as a loc
Joined: 08 May 2006 Posts: 1204 Location: Dublin, Ireland
... and have you googled IBM1784I and IBM1787I ? Once you have cleared up such errors, your compile might produce some output to be passed to the link-edit step.
Joined: 07 Feb 2009 Posts: 1314 Location: Vilnius, Lithuania
No interest in actually testing this, but adding the SQL pre-processor option to the compiler options might do the trick, and doing a separate pre-compile step is so not required nowadays.