Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.os2.programmer.misc > #1494

Re: VisproRexx odbc

Show all headers | View raw

comp.lang.rexx: they are, rare exceptions excluded, using their own 
Windows-based interpreter (ooRexx), including the ::REQUIRES and their
selfish language derivate of ORexx. comp.lang.oorexx would be a better
newsgroup, but instead they'll assume that ooRexx is the standard in 
comp.lang.rexx.

 > I'm using classic rexx

That's a safe choice, at least for now. In general often ORexx may be 
better, but ORexx could also introduce new errors (related to checking
code first based on the ANSI standard, or e.g. due to running out of 
shared memory). VisPro/REXX should work with your CRexx, albeit it may
require an older version of the OS.

Check your rcs, make sure that the DLL can be found in the LIBPATH, 
and perhaps first make sure that you can RxFuncAdd and use any simple 
version. RxFuncAdd individual functions first, to avoid the risk that 
a generic Load-function doesn't load all functions. As such it's 
possible to RxFuncAdd and use a VRODBCDR.DLL function. My error REX40 
is returned by it, unlike your REX43-error. I can reproduce a 
REX43-error by e.g. using a DLL name which doesn't exist at all.

 > SQLGetFunctions

What is "SQLGetFunctions"? Did you RxFuncAdd it, or is this an 
internal error message? 

 > SQLProcedures

EXEHDR:

  12    1  00000c04  SQLPROCEDURES      exported, shared data

I cannot RxFuncAdd and use a function called "SQLPRODECURES". 
RxFuncAdd returns 1, and calling it adds a SYS3175-entry to 
x:\POPUPLOG.OS2.

I'm not using VisPro/REXX (yet), I don't have your code, I'm not using
ODBC nor SQL, and I don't have your database. Hence the general 
suggestions and remarks in comp.lang.rexx, like checking the rc.

Is it possible for you to share whatever (database, your code, steps 
required to execute it) is needed to reproduce your error, excluding 
VisPro/REXX v3.1.1 itself?

It may be a bug, but REX43 suggests that it cannot find a function 
which CRexx should be able to find and use. If there's a bug, then you
still should be able to reproduce my REX40 with an invalid number of 
arguments.

And did you give my REX40 one-liner a try with CRexx? If so, then did 
you give it a try with VisPro/REXX? If VisPro/REXX still can load 
exyternal DLL functions, then it should be reproducable too.


--

Back to comp.os.os2.programmer.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

VisproRexx odbc per@raiko.no - 2015-10-22 06:06 -0700
  Re: VisproRexx odbc per@raiko.no - 2015-11-20 06:09 -0800
  Re: VisproRexx odbc per@raiko.no - 2015-11-20 07:43 -0800
    Re: VisproRexx odbc "A.D. Fundum" <what.ever@neverm.ind> - 2015-11-21 11:13 +0100
      Re: VisproRexx odbc per@raiko.no - 2015-11-21 11:01 -0800
        Re: VisproRexx odbc "A.D. Fundum" <what.ever@neverm.ind> - 2015-11-23 08:46 +0100
          Re: VisproRexx odbc PJ <per@raiko.no> - 2015-11-24 13:04 -0800
            Re: VisproRexx odbc "A.D. Fundum" <what.ever@neverm.ind> - 2015-11-25 19:04 +0100
              Re: VisproRexx odbc PJ <per@raiko.no> - 2015-11-25 11:12 -0800
                Re: VisproRexx odbc "A.D. Fundum" <what.ever@neverm.ind> - 2015-12-03 12:36 +0100
                Re: VisproRexx odbc PJ <per@raiko.no> - 2015-12-03 06:45 -0800
  Re: VisproRexx odbc "A.D. Fundum" <what.ever@neverm.ind> - 2015-12-05 17:28 +0100

csiph-web