On 25/10/2013 1:51 PM, Rob Schramm wrote:
With a JDBC driver and a bit of JAVA code..you could use the COBOL/JAVA
procedure BCDBATCH to help tie the two together. Did a quick scan and
there appear to be at least few JDBC drivers.
I'm scratching my head as to why a JDBC driver is useful with a NoSQL
data base which has a very specific API.
Why not just use the MongoDB Java API? Does JDBC provide some kind of
value add?
Rob
Rob Schramm
Senior Systems Consultant
Imperium Group
On Fri, Oct 25, 2013 at 1:18 AM, David Crayford <[email protected]> wrote:
On 25/10/2013 12:28 PM, Tony Harminc wrote:
On 24 October 2013 23:49, Ze'ev Atlas <[email protected]> wrote:
About a previous post, the endianess should not be a big issue to deal
with once the two sides of the protocol are well defined. The EBCDIC issue
is a make or break issue. MongoDB works decidedly with UTDF-8 and I need
COBOL to natively view a string as UTF-8. Does the current incarnation of
COBOL (and perhaps PL/I) have a native UTF-8 string type. If not, then I
will abandon the whole project.
I'm doubtless blowing (or something) into the wind again, but this
sounds like a place for UTF-EBCDIC. Which is easily translated to and
from UTF-8 if that's what goes on the wire. (I'm assuming your UTDF-8
was just a typo.) Presumably it would be a good start if COBOL could
see and manipulate the subset of UTF-EBCDIC that is EBCDIC strings
that would live as UTF-8 in the database. Then when COBOL learns to
handle UTF-EBCDIC, it could handle the complete UNICODE set.
The wire protocol is binary. The UTF-8 requirement for strings in the BSON
spec http://bsonspec.org/#/**specification<http://bsonspec.org/#/specification>
.
I really like the look of BSON. It's like google protocol buffers but more
flexible. XML is the pleated khakis of the document markup world.
http://www.unicode.org/**reports/tr16/<http://www.unicode.org/reports/tr16/>
Tony H.
------------------------------**------------------------------**
----------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
------------------------------**------------------------------**----------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
