Re: Class Notes for a PL/I Course.

In fact, at my former customer's installation, there were very nice
test macros called

AVPUTR (reg1[,reg2])???????? to put register content

AVPUTH operand[,length] ?????? to put hexadecimal content

AVPUTC operand[,length] ?????? to put character content

AVPUTP operand[,length[,scale]] ?????? to put packed content

very nice:
they didn't change any registers
and: they assembled to nothing, if a GBLB symbol named &AVGBTST
was not set (which, IIRC, could also be set using SYSPARM).

This customer started programming in ASSEMBLER in 1972,
in 1980, PL/1 was added and C in 1990. Modules of all three
languages can call each other, and they need not know, in
what language the target module is written.

Of course, the developers wanted the same test support for the
"new" languages, too (test output depending on a compiler switch)
.... no big problem using the PL/1 and C macro processors.

Every module was regularly built in two versions: with and without
this test switch on, and stored on two different datasets
(HLQ.<module>.LOAD and HLQ.<module>.TESTLIB).

And because all calls (in all three languages) were always dynamic
(no static linkage), you could always enable test messages of a
certain module simply by adding its HLQ.<module>.TESTLIB
to the STEPLIB chain.

Kind regards

Bernd



Am 08.10.2019 um 15:12 schrieb 'Bill Turner, WB4ALM' [email protected] 
[H390-MVS]:
>
>
> can you say "a whole bunch of code"...
>
> But then again, I liked Joe Monk's reply.
>
> Often wished that other languages had the equipment of PL/I's "Put data"
> sure was nice when debugging.
>
> /s/ Bill Turner, wb4alm
>
>
>
> On 10/8/19 6:06 AM, kerravon86-/[email protected] [H390-MVS] wrote:
>>
>> ---In [email protected], <tharminc@...> wrote :
>>
>> > Heh - the *real* PUT to use for debugging is
>> > PUT DATA... Now what is the C equivalent of that?
>>
>> First ask what the assembler equivalent is.
>>
>> BFN. Paul.
>>
>
>