On Wed, Jan 9, 2013 at 12:07 PM, Steve Thompson <sthomp...@us.ibm.com>wrote:
> >>> Sam Siegel posted: > On Wed, Jan 9, 2013 at 11:23 AM, Chris Craddock > <crashlu...@gmail.com>wrote: > > > >> > > >> On 09.01.2013 06:36, Sam Siegel wrote: > > >> > > >>> The Language Environment Vendor Interfaces (SA22-7568-09) mentions > the > > >>> ability to use XL C/C++ in an SRB. This is the full XL C/C++, with > > some > > >>> restrictions, not METAL-C. > > > > Beware that the "some restrictions" can be quite significant in > practice. > > Many of the C/C++ library routines you might expect to use just don't > work > > in that environment. > > > > What about just pure C/C++ code without calling LE library routines or > C-Runtime library routines and assuming that malloc/free and new/delete > eventually invokes the STORAGE OBTAIN/DELETE provided by the substitute > service routines? > <SNIPPAGE> > > If your routines cause any of the proscribed functions to be invoked, your > SRB will be terminated. Things such as an SVC will cause this. > > So unless you know that the compiler generated, and library contained > routines, that will be used for the code you wrote, will not do something > that is prohibited in SRB "mode", give it a whirl. However, I can tell > you that this can be a frustrating proposition where you find something > that was working yesterday, crashes tomorrow because of some unknown or > unseen difference that causes a slightly different code path to be taken > and some kind of I/O (OPEN any one?) gets done. > My intention is to do all I/O on a TCB and provide buffer of data to the SRB to perform some CPU intensive tasks. The processed buffer is then used by the TCB to write output data. There would be no cases where I/O occurs in the C/C++ SRB code. Is there anyway to tell by looking at the binder map, compiler listing, etc. to see if SRB prohibited code (svc, etc.) is generated? Thanks, Sam > > Regards, > Steve Thompson > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
