Date:         Mon, 11 Mar 1996 21:09:58 GMT
Reply-To:     REXX Programming discussion list <REXXLIST@UGA.CC.UGA.EDU>
Sender:       REXX Programming discussion list <REXXLIST@UGA.CC.UGA.EDU>
From:         John Gillett <jgillett@CIX.COMPULINK.CO.UK>
Organization: GSA Ltd.
Subject:      Re: Creating OS/2 Rexx Dll

> Is there some special magic I should be doing when creating the
> dll that I'm not? Does the def file need anything special in it?
>
> Replies or pointers to more information would be appreciated.
>
>
Use an interactive symbolic debugger and you will see what's happening in
your program.   I used OS/2 CSet and found the debugger,IPMD, easy to
use.  One trick to remember, however.  The debugger requires the name of
a .EXE.  So IPMD to debug CMD.EXE.  At the appropriate point tell IPMD to
interrupt on loading your DLL.   When you RUN you will get to a command
line.  Start you REXX test program.  Have trace on you like.  When the
DLL is loaded IPMD takes over.  You can now set breakpoints in your C
source code.
 
Sounds dificult but once you've done it a few times you will be amazed at
how fast you move forwards.
 
You may find this hard to believe but writing a SOM module is actually
easier - and you get free binding to OREXX, C, SmallTalk etc..  SOM is
easier because SOM takes care of the parameter mapping for you.  You
really write a whole lot less C code.
 
Good luck - and either way you do the job, you need a source code
debugger.  Makes all the difference.
 
 
John
**************************************************************
* Gillett, Sheen & assocs Ltd. (Computer-enhanced Telephony) *
* tel.+44 (0)1962 877227,             fax:+44 (0)1962 866945 *
* internet: jgillett@cix.compulink.co.uk    CIS: 100015,2610 *
**************************************************************