|
>From: David Gibbs [mailto:dgibbs@mks.com] >Sent: Friday, March 15, 2002 9:15 AM > ... >Most of the code in SVCPGM-A takes a bit of data and decides to call a >routine that's in either SVCPGM-B1 or SVCPGM-B2. > >SVCPGM-A also has generic routines that are called by both SVCPGM-B1 and >SVCPGM-B2. > >Problem is: I have routines in SVCPGM-B1 and SVCPGM-B2 that want to call the >generic routines in SVCPGM-A. Unfortunately, I can't get any of the service >programs to compile first because the routines they are calling don't exist >in the other service programs yet. > >So, I can't compile SVCPGM-B1 because it calls routines in SVCPGM-A (which >hasn't been created yet), and I can't compile SVCPGM-A, because it calls >routines in SVCPGM-B1. David, create SVCPGM-A with OPTION(*UNRSLVREF), then create B1 and B2. Then re-create SVCPGM-A without that option. Barbara Morris
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.