Re: QZDASOINIT library list - JDBC

I worked with this server job few years ago in my previous company. I'm trying
to recall my memory.

When you connect to host by Client function, it will involved number of Servers.
(please refers to IBM manual Series Access for Windows: Administration Version 5
Release 4 Page 28).


Let's just consider the database server.

QZDASRVSD is the daemon program
QZDASOINIT is the Server program


When you connect to the database server, the daemon program will "create" a
Server program for this connection. Actually, it is socket programming. Your
can refer Scott Klement's website
(http://www.scottklement.com/rpg/socktut/tutorial.html) for details.

The QZDASOINIT is the server program for your connection. The connection
properties will be the key control for your library list. I only used java.
Thus, I can only provide you the information by IBM toolbox. Please refers to
IBM manual IBM toolbox for Java V5R4 page 313. I remember it was working if I
use *LIBL and System naming. As the connection used my User Id to signon, the
library list is based on user profile.


For me, there is a problem. If the server job has message waiting, you won't
know it because the message is by the job QZDASOINIT. Our operators said they
had no resources to monitor this kind of messages. Thus, I have to do some job
to override the message to my message queue. I made use the "Current User" to
do something. I forgot the details..... I was few years ago.....

Anyway, hope it help.

Kevin








________________________________
From: Alex Pinsky <apinsky@xxxxxxxxxxxxxxx>
To: Java Programming on and around the IBM i <java400-l@xxxxxxxxxxxx>
Sent: Wed, April 27, 2011 1:05:21 PM
Subject: RE: QZDASOINIT library list - JDBC

This is how it works in our environment

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On
Behalf Of Charles Wilt
Sent: Wednesday, April 27, 2011 12:48 PM
To: Java Programming on and around the IBM i
Subject: Re: QZDASOINIT library list - JDBC

James & Alan,

System naming is being used...so you're saying the LIBL is being set from the
JOBD of the connecting profile?

Charles

On Wed, Apr 27, 2011 at 11:51 AM, Alex Pinsky <apinsky@xxxxxxxxxxxxxxx> wrote:

In this case it is taken from job description that is assigned to the
user profile that is used to open connections in data source
definitions XML

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of James Perkins
Sent: Wednesday, April 27, 2011 11:46 AM
To: Java Programming on and around the IBM i
Subject: Re: QZDASOINIT library list - JDBC

I've noticed that if you set naming=*system, then library list seems
to be set correctly.
--
James R. Perkins


On Wed, Apr 27, 2011 at 05:57, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

All,

I'm trying to understand how the library list is being set for a
QZDASOINIT job servicing a JDBC connection.

The JDBC connection specifies
libraries=*libl

Which as I understand it means use the default LIBL for the server
job. I would expect to see just the libraries specified in the
QSYSLIBL and QUSRLIBL system values.

However, when I look at an active job, I see that the LIBL isn't what
I'd expect. It looks as if the library list is being taken from the
JOBD specified on the user profile used to connect.

I don't recall it working like that. Is my memory going, or am I
missing something that resetting the LIBL of the QZDASOINIT job?

Thanks,
Charles
--
This is the Java Programming on and around the IBM i (JAVA400-L)
mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take
a

moment to review the archives at
http://archive.midrange.com/java400-l.

--
This is the Java Programming on and around the IBM i (JAVA400-L)
mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/java400-l.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CONFIDENTIALITY NOTE: The information contained in this email or fax
is intended only for the use of the individual or entity to whom it is
addressed. If you are not the intended recipient, you are hereby
notified that any disclosure, copying, distribution, printing or other
use of, or any action taken in reliance upon, the contents of this email or fax
and the information contained therein is strictly prohibited.
Before opening or using attachments, check them for viruses and
defects. Our liability to you for viruses or defects associated with
any email or fax is strictly limited to resupplying any affected
attachments. If you have received this communication in error, please
immediately notify the sender by telephone at (646) 264-6217 and delete the
original message.
Thank you.

--
This is the Java Programming on and around the IBM i (JAVA400-L)
mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/java400-l.

--
This is the Java Programming on and around the IBM i (JAVA400-L) mailing list To
post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a moment to
review the archives at http://archive.midrange.com/java400-l.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CONFIDENTIALITY NOTE: The information contained in this email or fax is intended
only for the use of the individual or entity to whom it is addressed. If you are
not
the intended recipient, you are hereby notified that any disclosure, copying,
distribution, printing or other use of, or any action taken in reliance upon,
the
contents of this email or fax and the information contained therein is strictly
prohibited.
Before opening or using attachments, check them for viruses and defects. Our
liability
to you for viruses or defects associated with any email or fax is strictly
limited to resupplying
any affected attachments. If you have received this communication in error,
please immediately
notify the sender by telephone at (646) 264-6217 and delete the original
message.
Thank you.