RE: Removing or replacing *inzsr with Dspecs

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Schutte
Subject: Re: Removing or replacing *inzsr with Dspecs

But that's about as far as I would go with sub procedures in a main line program. If there's other code that I feel like should be in a sub-procedure that's imported through a module or service program. Judging by the comment you made about being out of the game for a while, this might be a little too for this thread

...

If Wilson is in learning mode, converting subroutines to subprocedures can be a good exercise for him for getting used to them. Such conversions are good for that.

I like the idea for general maintenance where it doesn't detract from your timelines. Some subroutines use variables defined only for their purpose, or re-use work fields defined globally. To practice at first, do it with a few of them.

Alan













--------------------------------------------------------------------------------
Confidentiality Notice: This email may contain confidential information or information covered under the Privacy Act, 5 USC 552(a), and/or the Health Insurance Portability and Accountability Act (PL 104-191) and its various implementing regulations and must be protected in accordance with those provisions. It contains information that is legally privileged, confidential or otherwise protected from use or disclosure. This e-mail message, including any attachments, is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. You, the recipient, are obligated to maintain it in a safe, secure and confidential manner. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Thank you.
--------------------------------------------------------------------------------