×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I know that I have had errors when a package did not exist. I have had
SQLRPGLE programs which failed when distributed to production until I also
restored the sql package along with them.
And there was some discussion on the list from someone having issues with
their change management software. Apparently when you call MYSQLRPGLE
program, and it does an imbedded CONNECT TO to access a remote database it
needs an sql package on the remote system and the package wasn't there.
From that link at
http://www-01.ibm.com/support/docview.wss?uid=nas8N1019633
<snip>
Only extended dynamic SQL packages are automatically re-created by the
application. It is important that you do not delete IBM-supplied SQL
packages: packages in QSYS, packages whose names start with Q, and DRDA
packages. If you are unsure about whether a specific SQL package is used
by DRDA, use the PRTSQLINF command and look at the first page of the
report. DRDA packages will contain an RDB keyword entry identifying the
relational database for DRDA.
</snip>
We have a utility called SCNMSGF. I used it to scan QCPFMSG and QSQLMSG.
While there are ?4? sql package messages in QCPFMSG there are a plethora
in QSQLMSG. Of course, the scan would not find a generic message which
says 'object &1, type &2 was not found in &3'.
Rob Berendt
midrange.com
