Hi Mark,
[Mark Wong wrote]
> Subject: RE: Does repmcli -b interprets files differently in 7.3.0.29?
>
>
> Hi Steffen,
>
> Hmm... I'm confused. I should have provided an example the
> first time.
> The way I read that in the release notes is that if I were
> using '/' at
> the beginning of a line or an empty line I needed to edit my stored
> procedure. Here's a stored procedure that I've successfully loaded in
> 7.3.0.25:
>
> CREATE DBPROC t1 AS
> SUBTRANS BEGIN;
> SUBTRANS END;;
>
> So the way I understand the change, I don't need to edit anything.
> repmcli says:
>
> Error during execution
> -->-25010
> SQL error -5015 = Missing
> keyword:RETURN,FETCH,CLOSE,WHILE,UPDATE,TRY,SUBTRANS,STOP,SET,
> SELECT,LOCK,INSERT,IF,EXECUTE,DROP,DO,DELETE,DECLARE,CREATE,CO
> NTINUE,CASE,CALL,BEGIN (error position: 50)
>
Well, right. Almost right.
Simply remove the second ('buggy') semicolon at the end of your
dbproc statement and it will run. Promise.
With the new command separator in repmcli
scripts that enables all sql-commands (even those with comments) to
pass through RepMan to the DB we also cleaned up a bit the RepMan
command parser regarding processing DBPROCs. The second semicolon
is a relikt from the past where we used semicolons as command separators
in repmcli scripts. Those semicolons collided with DBPROCs delimiters
and a second semicolon at the end of DBPROC statements was needed to
get DBPROCs through RepMan without cutting off this semicolon.
Thats not longer true for a long time already
but we had some dead code which finally got removed with the new version.
Sorry for any inconvenience.
Regards,
Steffen
--
Steffen Schildberg
SAP DB Team
SAP Labs Berlin
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
