ILE Service Program best practices

All,

We have recently run into the following situation:

Service Program A was made from Module A and contains subprocedures 1 and 2

Service Program B was made from Module B and contains subprocedures 3 and 4

Subprocedure 2 calls subprocedure 3

Subprocedure 4 calls subprocedure 1

No big deal, except we are migrating our code to a development box and
attempting to recreate all of the objects from their source for
Hawkeye (we want the objects on the box to match the source on the
box).

Each service program is dependent upon the other.

We can fake this out by moving the existing objects over as well, but
this raised an interesting question:  How do we keep this from
happening in the future?

The only thing we can think of is to limit service programs to a
single subprocedure, but is this really something we want to do?

How are you guys handling this?

Mike E.