As the programs runs, the need to create the SQLPKG on the remote arises. Rather than use the profile that is running the process as the RDB user ID, it is retrieving the move coordinator profile that created the program to create the SQLPKG. Because this profile does not exist on the remote machine, the package creation fails. Which causes the process to fail.

-snip-

MSG ID SEV RECORD TEXT
SQL0204 30 THE_MOVE_COORDINATOR in QSYS type *USRPRF not found.
SQL5056 SQL package creation for module PROGRAM_NAME failed.
Package name was to be PROGRAM_NAME in QTEMP at REMOTE_SYSTEM.

Not sure how to proceed. While it appears that the SQL0204 error is the killer, I can't even find SQL5056 on IBM's website. I expect that I'll have to ask IBM about it, but thought I would share this with you all.

DSPMSGD SQL5056 QSQLMSG basically gives you exactly what you've shown
here. Since it seems undesirable to create a profile for the
coordinator, how about putting a CRTSQLPKG in the deployment script to
avoid the automatic package creation?

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].