|
It might be coincidental. I read the text on SQL7022. You may have
multiple CONNECTs. Perhaps you already have a connection going from a
previous SET CONNECT? If that is the case then you probably are in the
second condition of the help
DSPMSGD SQL7022 QSQLMSG
1. Display message text
Message . . . . : User &1 not the same as current user &2.
Cause . . . . . : One of the following occurred.
-- User &1 was specified in a CONNECT statement that specified the
local
relational database name. The user specified is not the same as the
current
job user &2.
-- User &1 was specified in a CONNECT statement and a connection using
&2
already exists to the specified relational database using connection
method
*DUW.
Recovery . . . : If connecting to the local relational database, change
the
statement so the user specified on the CONNECT is the same as the
current
job user ID.
If connecting to a remote relational database, either use the SET
CONNECTION statement to use the existing connection or end the current
connection and issue the CONNECT statement with the new user id.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.