As does IBM XLC. Supports fopen("//DD:ddname(member)", r);
But I suspect it allocates to the member as Shmuel alludes; it does not use
allocate/OPEN/FIND.
I just did a Find on <BPAM> in the XLC P/G and got zero hits. (For <QSAM> I got
15.)
There is no exposure of DESERV or anything like that (although I suspect the
old "read the directory BLKSIZE=256 and parse it yourself" would work just fine
written in C or C++).
I get 230 hits on member but of course member has a C++-specific overload.
(By xSAM I meant "BSAM or QSAM.")
Charles
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Paul Gilmartin
Sent: Sunday, March 29, 2020 1:35 PM
To: [email protected]
Subject: Re: strange python announcement
On Sun, 29 Mar 2020 19:52:50 +0000, Seymour J Metz wrote:
>xSAM? I don't know of any language on z/OS* other than HLASM that supports
>BPAM.
>
I believe that SAS/C (ISV) support{s|ed} a construct such as fopen(
"DD:"ddname"("member")", ... );
presumably employing BPAM.
And early in the development of the QSAM/BSAM interface to allocated
HFS files the facility was referred to as xSAM. The name was deprecate
as an overload.
>At this point, if I invest the time to master** a new language, I'd be looking
>at Java, Ruby or Rust rather than Python.
>
>* Assembler E, F, XF, H and H V2 don't count; they're not supported. It
>might, however
> be fun to see if thy will still run.
>
>** I mean a lot more than just Hello world
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
