Re: Cyclical reference in service programs?

["Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>]

Hello David,

You have a DESIGN problem.  Fix that first.  Either:

        1. Move the the generic functions into a separate service program
and compile that first.
        2. Combine the three service programs into one. Since they are
tightly coupled anyway by the inter-dependencies you can't use one without
the other.
        3. Move the generic functions into a separate service program.
Combine the remaning functions into another service program.

My preference would be for option 3.

This sort of change will require you to rebuild the programs that use the
service programs because the interface has changed.  However, it is better
to fix the design issue sooner rather than later.  It will just get worse.

There is an option on the CRTSRVPGM command called *UNRSLVREF that will
let you create the first dependent service program and ignore the missing
references.  It will not run in this state but once it exists you can
build the other dependent service programs and recreate the first service
program ommitting the *UNRSLVREF keyword.  However, relying on this
function is sloppy.

Regards,
Simon Coulter.

--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists
   http://www.flybynight.com.au/

   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------