When I ported the PCRE to classic z/OS (PDS, PDSE and all) I've found to my
chagrin that IEBUPDTE does not support vb libraries, only good ol' fb 80. I
had to write a 'crude' Rexx process (ADDMEM) that mimic some of the IEBUPDTE
functionality (./ ADD NAME=...). It also allowed me to do some character
manipulation in the process. Ze'ev Atlas
From: John McKown <[email protected]>
To: [email protected]
Sent: Monday, March 23, 2015 3:02 PM
Subject: Re: HLASM Syntax (was (Regular Expressions followup))
On Mon, Mar 23, 2015 at 1:57 PM, John Ehrman <[email protected]> wrote:
> John McKown would like...
>
> The only enhancement that I, personally, would like would be for "free
> format" input into HLASM with _no_ line limits. Mainly because I keep
> my HLASM source in a UNIX file and, depending on "things", I use the
> "as" UNIX command to assemble it. I'm a bit of a UNIX partisan for
> "interactives". Being forced to use column alignment when I use a
> non-ISPF editor is a royal bother. Hum, it would also be nice if the
> tab character were a white space character outside of literals.
>
> HLASM used to ship an input exit (ASMAXINV) that accepts variable-length
> input records. Check the Programmer's Guide.
Oh, I use FLOWASM for this functionality. However, I would prefer to
not need an "add on" because I sometime contribute to the CBT tape and
would prefer to not have FLOWASM as a prerequisite to compiling my
code. Of course, I could always implement the FLOWASM functionality as
an M4 macro <gag><puke>.
>
> Making the tab character a white space should be easy, but might require
> an option of some sort.
>
> John Ehrman
--
If you sent twitter messages while exploring, are you on a textpedition?
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
