>X-Authentication-Warning: localhost.localdomain: camber owned process
>Date: Mon, 6 Aug 2001 18:13:46 -0400 (EDT)
>From: Brian Bruns <camber@...>
>To: Terrence Enger <tenger@...>
>Subject: Re: openDRDA, collection name from command line
>Mind if we move this to the list? If not, I'll send my next followup
>there...(procmail does wonders for keeping my life in order ;-)
I shall try to send this response to the list.
>On Mon, 6 Aug 2001, Terrence Enger wrote:
>> Here is a new set of patches (including the patch I sent earlier today).
>Was there supposed to be an attachment?
Duh! This time, I'm gonna try really hard to remember the attachment.
>> I am not allowed to create or rename libraries (collections) on my AS/400.
>> Hence I added the collection name to the url on the command line and to
>I was afraid of this. I'm assuming the default NULLID collection doesn't
>work for you, or are we specifically talking about packages?
>Do you think perhaps a configuration file is necessary such as (samba
> hostname = as400.my.domain.com
> port = 446
> collection = NULLID
> package = OPENDRDA
> CCSID = 500
>I have some code I can import from freetds to do all this. It is
>unfortunate that one needs a collection/package to operate in DB2. We'll
>need the consistancy token here too, which can be queried from the
>database, but it's a chicken and egg thing, we need it to query.
I suppose something like this will have to come eventually. However, I
think the url-like scheme on the command line is pretty neat.
>> Some odds and ends:
>> (*) Thanks for the pointer to OBJDSS. These manuals are *really* hard to
>> understand when you are looking in the wrong place.
>The spec can be a bit unwieldy, I have mine printed in two 3-ring
>binders...its a monster.
Being a cheapskate, I'm printing individual pages. Just one binder so far.
>> (*) Along the same line, on what did you base your definition DRDA_SQLCA?
>> I got back something purporting to be a sqlca, but it differs from both the
>> structure you defined and from the description in my SQL manual.
>SQLCA and SQLDA come from C911 chapter 5. SQLCARD starts on page 175, the
>FD:OCA stuff is a bit hard for me to parse still...it's quite possible the
>code is wrong. Specifically, the endianness of some of the fields makes me
>think i have some field sizes or other details wrong. Maybe your reading
>of it is better than mine.
Thanks. Obviously, I should have printed a few more pages.
>> (*) I changed DRDA.port to unsigned short int.
>I modified this in my tree.
>> (*) I wrote drda_ascii2ebcdic_pad to output a fixed-length ebcdic field
>> with blank padding. My server objects to an embedded null. I have only
>> used the new routine where I have observed an error resulting from the null
>> or where I was changing the code anyway, but you might want to use it more
>> widely, as the calling sequence is a bit shorter.
>> (*) Using ecgs-2.91.66, the two calls to iconv as distributed produce a
>> warning about parameter 2 being passed from an incompatible pointer type.
>> The ugly casts and conversions in my patch prevent the messages during the
>> compile, but I do not understand why this should be necessary.
>> (*) Contrary to the example usage, tester requires a numeric host address.
>> I presume one of us will get around to extending this someday.
>example usage is correct, code is broken ;-)
>> Thanks for your attention,