RE: Insert using ODBC/system DSN

[rob@xxxxxxxxx]

Chill buddy.  I brought that up because some people raised the concern 
that simply calling a CL to do the CHGLIBL causes overhead, just because 
CL does.  That's why I suggested the api.  Then in this case, if that is 
all the CL does, then I would think that disposing of it properly would be 
the right solution.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/21/2003 01:37 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     "Midrange Systems Technical Discussion" 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        RE: Insert using ODBC/system DSN


> From: rob@xxxxxxxxx
>
> Why not just call an API that changes the library list?

Are you asking "as opposed to calling a CL program"?  If so, my response 
is
that CL programs are really easy to write and call.  Not everything needs 
to
be turned into a call to an API; there are certain things that CL does
really well, and environment maintenance is one of them.

With the QLICHGLL API, you have to pass values for current library and
product library 1 and 2, as well as the array of libraries and a binary
count.  Even if you're just passing *SAME, it's a point of error, whereas
with the CHGLIBL command, you need only change the library list.

Not only that, it opens the door to expansion down the road.  What if he
also wanted to change priority and timeslice?  Or output queue?  Multiple
API calls might be fine, but an environment setting CL program might be 
just
as nice.  And since this is a one-time call, the overhead of a CL program 
is
not prohibitive.

Joe

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.