Charles, I'm nearly certain that it doesn't do a SVC99 when you are using fopen with a DDNAME
But it does seem to do a OPEN/BLDL/POINT....STOW/CLOSE for each fopen() / fclose() using //DD:MYDD(MEM) IMO, there are a couple of important missing things: 1) There isn't a way to update (or get) the PDS directory user data when processing the member with fopen()/fclose(). 2) You would really like to be able to do this: fopen(//DD:MYDD(MEM1), ...) freopen(//DD:MYDD(MEM2), ....) so that the freopen() caused a STOW (if opened update) and a BLDL/POINT, and avoided the cost of a complete OPEN/CLOSE path. I don't think that it does that. So, for my money, better BPAM support would be nice. Kirk Wolf Dovetailed Technologies http://dovetail.com On Mon, Apr 30, 2012 at 11:45 AM, Charles Mills <charl...@mcn.org> wrote: > Does anyone *know* whether a C/C++ Language Environment fopen() of a > filename of the form DD:ddname(member) use an OPEN of ddname followed by a > BLDL or FIND for member (the way any reasonable programmer would) or does > it > do a whole new DYNALLOC for dsname(member)? (Seems like a dumb question, > but > FTP does it that way, so stranger things have happened.) > > My *interpretation* of the allocation messages - I don't see allocate and > de-allocate messages for a SYSnnnnn that appears to be for member - leads > me > to believe that C/C++ LE does it right. But I could be reading it wrong. > Does anyone *know*? > > Thanks, > Charles > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
