Out of curiosity, does that means that the CSFDLL functions do not create a linkage stack entry before calling the true routines/
On Fri, 12 Jan 2024 14:23:54 +0000 Eric D Rossman <[email protected]> wrote: :>There is no documentation because this is not a supported interface. It has been suggested in passing but has never been put forward as an official requirement. :>All LE-capable applications have access to the CSFDLLxx (where xx is 31,3X,64) libraries and the csfbext.h C/C++ header to call directly :>All non-LE applications have the CSN* and CSN*6 (plus CSF*/CSF*6) assembler stubs. :>Eric Rossman :>ICSF Architect :>-----Original Message----- :>From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Binyamin Dissen :>Sent: Friday, January 12, 2024 3:26 AM :>To: [email protected] :>Subject: [EXTERNAL] Direct branch entry to ICSF routines :>I have been looking but I have not yet found the explicit doc that shows how to call ICSF routines via the CSFCCVT. :>Looking at a few of the stub routines I see that they create a linkage stack entry and then call the real routine via CSFCCVT but the labels in the CSFCCVT are not obviously related to the name of the stub routine. :>I am expecting to find something like for the name/token routines, where the stub can be used but the direct entry is also documented. :>Further research shows that the several routine that I am interested all branch to the same EP, but the stub loads a different value into R0. Don't ask me why there aren't a list of equated values for the various functions and a parameter with the function code. At any rate, high level language routines cannot set R0 but assembler routines certainly can. -- Binyamin Dissen <[email protected]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
