Yes, this is what I meant. I have heard some very good techniques here for
keeping binding under control, but so far for me, the 1 module/1 pgm
approach has been easy to keep straight. Don't call Java or C here.
One thing we did, don't know if everyone does this or not, is create a
service program that can call all the old programs we used to use call/parm
for - part number searches etc. It acts like a container. We call the
procedure and the svc pgm does the call/parm of the old programs. Seems to
work great. Poor mans cleanup and keeps the service pgms a reasonable
size. Any serious downside to this?
Jim
Hi Peter
Is it possible that Jim meant multiple service programs, and not
including the modules?
Vern
***********************************************************************
The information transmitted is intended solely for the individual or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or
other use of or taking action in reliance upon this information by
persons or entities other than the intended recipient is prohibited.
If you have received this email in error please contact the sender and
delete the material from any computer. As a recipient of this email,
you are responsible for screening its contents and the contents of any
attachments for the presence of viruses. No liability is accepted for
any damages caused by any virus transmitted by this email.
