V5R3 CALL stored procedure behavior

[qsrvbas@xxxxxxxxxxxx (Tom Liotta)]

I could've sworn that the last time I looked into this, a program object needed 
to be defined to DB2 as a stored procedure _only_ if parm values were to be 
returned. I.e., if all parms were IN only, then you could CALL a program as if 
it had been declared as a stored procedure.

But the V5R3 InfoCenter says that:

"A static CALL statement without a corresponding CREATE PROCEDURE statement is 
processed with the following rules:

    * All host variable arguments are treated as INOUT type parameters.
    * The CALL type is GENERAL (no indicator argument is passed).
    * The program to call is determined based on the procedure name specified 
on the CALL, and, if necessary, the naming convention.
    * The language of the program to call is determined based on information 
retrieved from the system about the program."

That's from Database-> Programming-> SQL programming-> Routines-> Stored 
procedures-> Using embedded CALL statement where no procedure definition exists.

Ummm... so in V5R3, pretty much every program object is open for a remote (or 
local only?) SQL CALL assuming authority is appropriate and you treat all parms 
as INOUT?

There are some obvious snags, but..... huh??? How long has this been so?

Tom Liotta