Re: Microfocus & Oracle data types

From: James J. Gavan (jjgavan_at_shaw.ca)
Date: 08/13/04

  • Next message: Jeff York: "Re: Conversion Problem"
    Date: Fri, 13 Aug 2004 04:11:21 GMT
    
    

    Simon Tobias wrote:

    >Hi Jimmy.
    >
    >I'm not sure that I suggested using any particular compiler directives to
    >resolve the issue -- purely making use of functionality available with
    >OpenESQL, which ships with Net Express and Server Express. SQLWARNx is part
    >of our standard SQLCA copybook structure, and is automatically populated
    >where necessary.
    >
    >
    >
    Yes I read that too quickly and *assumed* a directive was being set

    ><shameless plug>
    >
    ></shameless plug>
    >
    >
    >
    No problem as a developer using the product I really like the product -
    so plugs are in order :-)

    >I am concerned regarding your experiences with the MF Answer Exchange
    >though -- if you're not getting satisfactory responses, please email me
    >off-list with details, and I'll endeavour to follow up internally.
    >
    >
    >
    That stumped me. Believe me I *really* can complain when necessary. So
    I had to read my previous message to get what you thought I was
    complaining about. As an example I was cautioning about use of
    Directives. To solve the problem there was no quick fix. Not knowing
    precisely where it was occurring would have necessitated me sending a
    HUGE zipfile for the project (OO) for somebody to sort out. Assuming
    somebody would take on the challenge without saying 'This is gonna cost
    money....", they would have rebuilt the project with their tools. Still
    probably wouldn't have worked. If the recipient was real smart he might
    have thought of doing a global search :-

    .... another plug here :-)

    on the project source looking to see if I had any '$set.......". Bingo
    ! From memory - he would find I used only one (no SQL being used in
    those days and I don't even use any of the $sets.... for OO - it works
    fine without them.).

    so he would see "$set compress.....", include the DLL and find that it
    runs smoothly. In a very polite and diplomatic way he would write me -
    literal translation - "Make sure you include the compress.DLL - you
    silly bugger !". Someone might find it fairly easily, but I think you
    would agree, initially it might be a long shot.

    Absolutely no problems with Answer Exchange. It's even better than its
    predecessor M/F CompuServe Forum which Alan monitored and good old
    stalwart Patrick was part of, and still is. Funnily enough a Colin
    Ransom/Ranshaw (?) today posted he had a 'funny' with SQL using V 3.0
    (No ! Don't tell him to upgrade - $$$$$$ !). I referred to the fact that
    you had helped resolve Michael's problem here in c.l.c. and suggested he
    use all the features of ESQL , setting up a dummy Table, generating
    queries and perhaps running them in ESQL test mode. I think his problem
    might be a little quirky. I should have suggested to him - take his
    problem step-by-step ( having firstly generated the copyfile), then
    copy/paste each step (Query), into a small COBOL program against a
    series of perform PARAGRAPHS. From memory the problem is occurring at
    arm's length over a network.

    Now if you want to know about complaining - I think we are back in 1985
    or thereabouts and I had switched from RM/COBOL to MS COBOL (not their
    'badged' version of M/F COBOL - but the immediate predecessor). Can't
    even remember my justification for the switch from RM to MS. Anyway I
    had a problem but can't remember details. So I phoned M/S Tech Support-
    they had a Canadian Office in either Quebec or Toronto. Nice young man
    took my query - but even from the first telephone call ( and this *was*
    my dime - no 1-800s in those days), it was clearly apparent that I knew
    more about COBOL than he did. In fact I'm not even sure he knew anything
    about COBOL. But I suppose on the basis he had taken a course at college
    that's how he got his job. He would look into it.

    Few weeks pass - I phone again "I'm still looking into it". I suggest I
    snail-mail him a diskette with the offending source.

    Few weeks pass - I phone again. "Sorry. Haven't received your diskette".

    Boy ! I'm really pissed off by now. I think on the problem; , what's the
    name of that man in Washington State who started this Microsoft thing.
    Ah yes. Bill Gates. (Didn't realize that even back then he had enough
    greenbacks to completely paper over Mount St. Helens and stop it blowing
    its top). Screw it ! I'll phone and ask to speak to him direct. I know
    he's the boss of a *small* company - still he's got to be concerned.
    Truly - I get his secretary - who plays it real cool and ensures me the
    message will be passed on. Boom ! Within the hour on comes a bright-eyed
    and bushy-tailed troubleshooter. "What's the problem. Details please. OK
    leave it to me".. Gets back about half an hour later, obviously having
    checked out the Canadian office. "OK send a copy of your diskette to
    Beyonce Knowles here in Belliingham, (I WISH !). She will sort it out
    and phone you back".

    She did within one day of probably receiving the diskette and for full
    measure offered to send me a couple of diskettes with sample programs.
    One source I recall was taking a print heading routine, centering for
    when it was printed on the page. Regrettably, I assume the young guy in
    Canada probably got the boot and I doubt his manager was left as a very
    happy camper either.

    If yer gonna complain - do it big time !

    I just reflected - that was human-to-human talking. Ignoring the size of
    MS now - or any other company - would we get the same sort of action
    with our modern dispassionate e-mail approach ?

    Mind you ignoring COBOL - on reflection I think my time would have been
    better spent, armed with huge bags, traipsing around the slopes of St.
    Helens, collecting Bill's greenbacks.

    Jimmy, Calgary AB


  • Next message: Jeff York: "Re: Conversion Problem"

    Relevant Pages

    • Re: Microsoft Cobol 5.0 Help Needed
      ... Original MF Cobol compilers (CIS Cobol of 1978 and its predecessor ... error is the byte offset of the failure, not a source code line number. ... With OPT"0" the COPYLIST REF directives will give the offsets of the ... int code _before_ the generator has turned this into machine code. ...
      (comp.lang.cobol)
    • Re: Microsoft Cobol 5.0 Help Needed
      ... Original MF Cobol compilers (CIS Cobol of 1978 and its predecessor ... error is the byte offset of the failure, not a source code line number. ... With OPT"0" the COPYLIST REF directives will give the offsets of the ... int code _before_ the generator has turned this into machine code. ...
      (comp.lang.cobol)
    • Re: Deploying over IIS and VB
      ... >> The COBOL needs to be OO and wrapped as a standard COM server. ... it when the VB .DLL is being called or when the COBOL .DLL is being ... If you are using embedded SQL statements in your program, ... also have the correct SQL directives turned on for compilation. ...
      (comp.lang.cobol)
    • Re: M/F Personal Cobol 2.0 for Dos problem running under windows XP
      ... 'Elements of OO COBOL", ... which may or may not have included that diskette. ... Installation instructions and are you aware of the significance of ADIS ...
      (comp.lang.cobol)
    • Re: Deploying over IIS and VB
      ... >> have to go the OO Cobol route. ... > also have the correct SQL directives turned on for compilation. ... I belive that the Cobol.dll compiles fine as the Oracle Precompiler ...
      (comp.lang.cobol)