Ed,
I am also a proponent of structured programming. Here is just one small
bit of a my ATLS program on z/VSE.
MAIN_LINE SECTION START
PERFORM INITILIZATION_LOGIC
PERFORM READ_CONTROL_CARDS
PERFORM CONNECT_TO_STACK
PERFORM CONNECT_TO_OCEXIT
PERFORM OPEN_CTL
PERFORM INIT_GSK
PERFORM READ_CONTROL_CARDS
PERFORM WAIT_MASTER_ECB
PERFORM DISCONNECT_FROM_OCEXIT
PERFORM DISCONNECT_FROM_STACK
ML_EXIT SECTION EXIT
The SECTION and PERFORM macros are my own. Just part of a group of about
10 macros that let me write 'mostly' structured programs.
Each section has it's own limited addressability. A branch outside of a
perform section will not even assemble. (Error exit routines are in the
base section of the program to allow easy branch exiting upon critical
errors.) restricted usings " USING (MAIN_LINE,X0080),R9 " are really
nice to prevent errors.
Tony Thigpen
-----Original Message -----
From: Ed Jaffe
Sent: 12/04/2013 05:45 PM
On 12/4/2013 1:37 PM, Tony Harminc wrote:
Well, sure, but all the ugly generated labels and such are there when
you have to read the listing rather than the source. And there are
times when you have the offset where something program checked, and
the source just won't do.
We use FLOWASM. Therefore, most listings we read look like what's
pictured on slide 56 of this SHARE presentation:
ftp://phoenixsoftware.com/pub/demo/Structured_Assembler.pdf
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/
