I'm not sure what Endevor allows but changing the build process is above my pay
grade.
It's the golden rule: he who has the gold makes the rule. And, yes, there are
legitimate reasons for locking down the build process.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל
"IBM Mainframe Assembler List" wrote on
02/23/2024 03:54:52 PM:
> Simply? In someone else's controlled environment?
That is why I said "simply" (i.e., in quotes). ;-)But, it
would do for testing on a single program source.
Sincerely,
Dave Clark
--
int.ext: 91078
direct:
Simply? In someone else's controlled environment?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
From: IBM Mainframe Assembler List on behalf
of Dave Clark
Sent: Friday, February 23, 2024
"IBM Mainframe Assembler List" wrote on
02/23/2024 12:52:42 PM:
> That works for stand-alone assemblies, but I'm not sure whether the
> CM process can accommodate it.
It doesn't strictly need to. You could "simply" put the following
statement (his) at the beginning of your assembler
On 2/23/24 13:12:16, Seymour J Metz wrote:
Configuation Management using Endevor.
.
Does Endevor let you define your own build processes as,
for example, "make" does (but SMP/E doesn't.)
Are you concerned with suppressing the listing of the
IEABRC macro definition, or of its expansion?
--
Configuation Management using Endevor.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
From: IBM Mainframe Assembler List on behalf
of Martin Trübner
Shmuel
what is "the CM process" ?
Martin
Am 23.02.24 um 18:52 schrieb Seymour J Metz:
That works for stand-alone assemblies, but I'm not sure whether the CM process
can accommodate it.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א
I do not believe the suggestion about putting the COPY statement
within a macro definition will work as desired. Here is an
extraction of the description of the COPY statement as it relates to
macros (Chapter 7. How to specify macro definitions, page 227 of
SC26-4940-09 High Level Assembler for
That works for stand-alone assemblies, but I'm not sure whether the CM process
can accommodate it.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
From: IBM Mainframe Assembler List on
On 2/23/24 10:06:02, Martin Trübner wrote:
There are exits in HLASM that can be used to suppress printing according to you
own rules.
.
This becomes burdensome for anyone intending to publish
assembler source code.
--
gil
There are exits in HLASM that can be used to suppress printing according
to you own rules.
I wrote code to suppress printing of macros and copy-code, if they come
from certain libraries.
the PROCESS/PARM for the HLASM must contain
EXIT(INX(EXNAME),LBX(EXNAME),PRX(EXNAME))
As you can see
"IBM Mainframe Assembler List" wrote on
02/23/2024 11:38:24 AM:
> IEABRC is z/OS, but ASMMSP is part of the HLASM Toolkit. Or is the
> toolkit only for z/OS and z/VM?
HLASM Toolkit is available for z/VSE as a separate product --
which we don't have.
Sincerely,
Dave Clark
--
IEABRC is z/OS, but ASMMSP is part of the HLASM Toolkit. Or is the toolkit only
for z/OS and z/VM?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
From: IBM Mainframe Assembler List on
"IBM Mainframe Assembler List" wrote on
02/23/2024 11:27:00 AM:
> Is there anything in ASMMSP or IEABRC that depends on being in open
code?
I don't have those copybooks (I'm on z/VSE) so someone else will
have to answer that question.
Sincerely,
Dave Clark
--
int.ext: 91078
Is there anything in ASMMSP or IEABRC that depends on being in open code?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
From: IBM Mainframe Assembler List on behalf
of Dave Clark
Sent:
On 2/23/24 07:34:33, Seymour J Metz wrote:
I don't want to use PRINT OFF for the COPY of ASMMSP or IEABRC, but I don't
want to clutter up the listing. Is there an analog of PRINT NOGEN for code in a
COPY?
Make a private copy of ASMMSP or IEABRC. Add PUSH--NOGEN--POP.
I once wrote or
"IBM Mainframe Assembler List" wrote on
02/23/2024 09:34:33 AM:
> I don't want to use PRINT OFF for the COPY of ASMMSP or IEABRC, but
> I don't want to clutter up the listing. Is there an analog of PRINT
> NOGEN for code in a COPY?
It sounds like you want the COPY statement to be
I don't want to use PRINT OFF for the COPY of ASMMSP or IEABRC, but I don't
want to clutter up the listing. Is there an analog of PRINT NOGEN for code in a
COPY?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
Hello list
The entry titled 'Program Alias Names' should not have been posted to this
list. It has been re-posted to IBM-Main.
Peter Morrison
There is an API to the binder described in MVS Program Management:
Advanced Facilities
binder fast data access mentions
MEMBER=member — RX-type address or register (3-12)
3peci®es the name of a structure identifying the member name or alias of
the library member to be
accessed. The structure
Hello List,
The MVS (et al) Binder and program objects have been around for over 30
years.
It is possible to have aliases for program objects (stored in a PDSE) that
are longer than 8 characters.
However, I have not found any facilities to (1) bringing thus-named things
into storage
21 matches
Mail list logo
