×
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.
First, I apologize, I have sent a number of messages back to the list
regarding my issues with SQLPKGs. The messages have been rejected by
midrange.com - primarily because they were sent through my google
account instead of my usual mail account.
My question is for those who use Thunderbird.
Why am I able to submit my original message via Thunderbird as
paultherrien@xxxxxxxxxxxxxxxxxx, but when replying to postings on
midrange.com via Thunderbird thunderbird is using my google account?
Obviously it is a configuration issue, but annoying.
So to Vern...
Vern,
Thanks for the info. I am getting that same idea - that I need to
create the SQLPKG on the remote system from the client that will access it.
I know I read somewhere that the signature of the SQLPKG contains
information from the database where the SQL originated, but I cannot
find that info today.
I've been going through the database documentation in the info center
and not finding specific info.
Paul
and to Jack Kingsley:
I am using SQL Connect statement to connect to remote server.
And to everyone in general...
I went into the target system using System i Navigator to look at the
SQLPKG and noticed that the SQL packages do show you a column called
'Program Location' which does show you the name of the system where the
SQLPKG creation originated from.
So I am guessing that the source system for the SQLPKG is integral in
identifying the SQLPKG at execution time.
I asked an associate of mine about this situation and he suggested a
separate library for each client machine on the target machine for the
SQLPKGs.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.