Allow a SQL stored procedure to use 3 part naming without having to create a custom *SQLPKG on each target.

I created a sql stored procedure which looks like the following:

CREATE PROCEDURE rob.PROPAGATE_QLNKOMT()
         LANGUAGE SQL MODIFIES SQL DATA
        SET OPTION DATFMT = *ISO

P1 : BEGIN
DECLARE OMIT_LIST CHARACTER VARYING ( 32000 ) ;

SELECT FSXCMD INTO OMIT_LIST
FROM QUSRBRM . QA1AFS
WHERE FSNAME = 'QLNKOMT'
;
UPDATE GDI . QUSRBRM . QA1AFS
SET FSXCMD = OMIT_LIST
WHERE FSNAME = 'QLNKOMT' ;
UPDATE DOMTEST . QUSRBRM . QA1AFS
SET FSXCMD = OMIT_LIST
WHERE FSNAME = 'QLNKOMT' ;

...

END P1 
;

The first time I run it, each system used in the 3 part naming ends up with a *SQLPKG in the library rob.

Now, I modify the stored procedure, drop it and recreate it.  When I call it the run fails with 

Cause . . . . . : Package PROPA00001 in ROB on application server GDIHQ cannot be run with the current application program because either the application program has been recompiled without rebuilding the package or the package has been restored from a back level version. Recovery . . . : Rebuild the package by using the CRTSQLPKG command or by using a CRTSQLxxx command specifying the correct relational database. Otherwise, restore the package from a version which matches the application program being run.

If I just run a 3 part statement outside of a stored procedure it doesn't create a sql package on the remote system does it?  Why should it need to just because I ran it from within a stored procedure?

It makes it tough to have to go to each target and blast the sql package.