'sfunny how things go 'round.
In September I was unhappy with my ISP and I asked
for advice on alternatives. Which I got, and I'm
now down to two contenders. (Thanks to those who
passed on suggestions and personal experiences.)
But, before I actually move my website, I decided
it was time for a
> -Original Message-
> From: IBM Mainframe Assembler List
> [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Paul Gilmartin
> Sent: 18 November 2011 16:37
> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
> Subject: Re: Conditional assembly for COBOL?
>
>
>
> On Nov 17, 2011, at 14:35, Bernd Oppol
>The PPONLY option causes the preprocessed code to be sent
>to SYS010 without invoking the compiler.
Correction: Make that SYSUT10, not SYS010
OK, just answer me one question.
If you have to use REXX anyway, why not use it for everything?
You guys are making this harder than it really is because of your bias
toward Assembler. (Of course, this is the Assembler List.)
I keep seeing this code and that code to perform the pre-process. Usin
M4 does look like an excellent choice, as far as capabilities go. But
John's point is exactly what I was thinking: How do I run M4 against my
PDS input? If someone can point me to some JCL to accomplish this, I will
probably head in that direction.
The next closest option looks like the C prepro
> -Original Message-
> From: IBM Mainframe Assembler List
> [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Paul Gilmartin
> Or use existing art:
>
> http://en.wikipedia.org/wiki/M4_%28computer_language%29
>
> -- gil
Oh, that's just __nasty__. m4 is complicated. And, in z/OS, is
On Nov 17, 2011, at 14:35, Bernd Oppolzer wrote:
> The PL/1 preprocessor is IMHO the most powerful tool to do such things,
> but maybe you don't have it, if you have no PL/1 licensed.
>
> The ASSEMBLER macro processor will not work, because you cannot
> extract the result and send it to the COBOL
All
Correction. The line counts shown in prior message were total bytes not
lines. The structured conditional macro assembler version of ZSTRMAC.MLC
was exactly 1,000 lines. The bootstrap version in HLASM basic conditional
macro assembler with all the AGO's and macro statement labels is 1,933.
Original Message From: "Tom Marchant"
An alternate method could be to direct SYSPUNCH to a temporary data set,
which is then used as input to a later Cobol compile step. John's method
has the benefit of greater flexibility to, for example, include additional
steps such as other pre-compilers or
All
The z390 Portable Macro Assembler offers an easy solution using extensions
to the AREAD and PUNCH statements to allow specifying DDNAME to read
and/or write multiple text files. These extensions allow you to use
conditional assembler to code utilities that read and write multiple text
files t
I am out of the office until 11/21/2011.
I will be out of the office. If you needed to contact me call me on my cell
phone and email me too.
Note: This is an automated response to your message "Re: Conditional
assembly for COBOL?" sent on 11/18/2011 9:22:51 AM.
This is the only notification yo
On Thu, 17 Nov 2011 17:15:17 -0500, John Gilmore wrote:
>My practice is 1) to generate the output I need using PUNCH and REPRO
>(for invariant text) and 2) direct SYSPUNCH output to the internal
>reader.
>
>This scheme requires that this SYSPUNCH output include the appropriate
>JCL, as is always t
12 matches
Mail list logo
