Re: RPG Program as a Stored Procedure

I notice you're mixing system naming and SQL naming

CREATE PROCEDURE V64BPCSUSR.SVLBRTEST

and

specific V64BPCSUSR/SVLBRTEST
...
external name V64BPCSUSR/SVLBRTEST

Idk if that's causing the problem.


On 8/7/2019 3:16 PM, THarteau@xxxxxxxxxxxxxxxxxx wrote:

Hi,
When I add the parentheses, I get the error
Token ( was not valid. Valid tokens: ) ,.
CREATE PROCEDURE V64BPCSUSR.SVLBRTEST
(IN @pTransactionNum float,
IN @pRevisionDate varchar(25),
IN @pNRBDX float,
OUT @pIsOK float,
OUT @pErrorMessage varchar(255),
IN @pEmployeeId varchar(8),
IN @pLogicalDate varchar(10),
IN @pStartDate varchar(10),
IN @pStartTime varchar(8),
IN @pStopDate varchar(10),
IN @pStopTime varchar(8),
IN @pHours float,
IN @pOrderNum float,
IN @pOrderStep float,
IN @pQtyGood dec(9.3),
IN @pQtyScrap dec(9.3),
IN @pScrapCode varchar(10),
IN @pCompltCode varchar(1),
IN @pReworkCode varchar(10),
IN @pDept varchar(4),
IN @pWorkCenter varchar(6),
IN @pMach varchar(10),
IN @pDownCode varchar(10),
IN @pNLaborType varchar(1),
IN @pShift varchar(3),
IN @pIndirect varchar(6),
IN p@Lot varchar(12),
IN @pAttrib1 varchar(15),
IN @pAttrib2 varchar(15),
IN @pAttrib3 varchar(15),
IN @pAttrib4 float,
IN @pAttrib5 float,
IN @pIsBckOt float,
IN @pDownNote varchar(255))
language RPGLE
specific V64BPCSUSR/SVLBRTEST
not deterministic
modifies SQL data
external name V64BPCSUSR/SVLBRTEST
parameter style general

<===================================================>

Terri Harteau
Felker Brothers Corporation
****************
Practice random acts of kindness and senseless acts of beauty
-Anonymous
****************

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus