Re: Package not found

[Michael Ryan <michaelrtr@xxxxxxxxx>]

Ahhhh...very cool. I was talking the default of RDB(*PGM) for CRTSQLPKG,
which in turn was using the CRTSQLRPGI default of RDB(*LOCAL). I see where
specifying the RDB entry would save me having to do the save/restore. This
assumes that RDB directory entry B exists on system A, right?

Thanks...

On Thu, Nov 4, 2010 at 1:17 PM, sjl <sjl_abc@xxxxxxxxxxx> wrote:

> Michael -
>
> You don't necessarily have to save and restore the package.  CRTSQLPKG can
> use the plan information from the program object on the development system
> to create the SQL package on the remote system.
>
> Example:
>
> I have an SQLRPGLE program on System A named COGS.
>
> To create the plan that it needs to use on system B (assuming that my user
> id and password are the same on both systems, and that the RDB name of
> System B is also "B"), I can run this command on system A:
>
> CRTSQLPKG PGM(MYLIB/COGS) RDB(B)
>
> and it will create the SQL package named COGS in MYLIB on system B.
>
> - sjl
>
>
>
> Michael wrote:
>  Sigh...PICNIC error...I needed to CRTSQLPKG on the development system and
>  save/restore the *SQLPKG object to the production system. All is well.
> Maybe
>  I should write this stuff down someplace...
>
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.