SQL CLI

Hello list,

Currently I'm doing some research on using the SQL CLI. I wrote a few
serviceprograms to hide database work, and used the CLI functions in it.
I want to extend this concept. The routines in which I want to use the
CLI are serviceroutines wich will run in the Activation Group of the
caller.

I'm not sure where to place the SQLAllocEnv, SQLAllocConnect and
SQLConnect calls for the allocation of environment and connection
handles. 
The manual says "there can be only one active environment at any one
time per application." 
And for the connection: "iSeries does not support multiple simultaneous
connections to the same data source in a single job."

So it looks that I have to let the calling program do the allocation of
the handles and the database connection. But I don't want the calling
program to know anything about the underlaying database handling. 
I thought about a trap-door routine in the serviceroutines which prepare
a connection if it was not established. But then the problem arises what
to do when leaving the calling program. It does not free connection and
handles automaticly since a database connection is scoped to the job.

Are there people who have expererience with the use of the SQL CLI in
such situation? 

Thanks in advance,
Arco Simonse
pgmr

DISCLAIMER:
This message contains information that may be privileged or
confidential and is the property of C.Meijer B.V. It is intended only for the 
person to whom it is addressed. If you are not the intended recipient, you are 
not authorized to read, print, retain, copy,disseminate, distribute, or use 
this message or any part thereof. If you
receive this message in error, please notify the sender immediately and delete 
all copies of this message. 

This footnote also confirms that this email message has been swept by the 
presence of computer viruses