RE: RE: Trials and tribulations of QMHSNDPM (Was: No Subroutines ...)

Rory;

I used to be in the no C-specs in copybooks, but I have modified that a
little. With IBM APIs, and many of our home built APIs, you end up with
initialization, cleanup, calling, and D-specs and you use them all over the
place. Using minimal code in the C-spec copybooks to initialize call and
cleanup the API variables you can then call the API with 4 /Includes. You
have all of the functionality of the API at your disposal, when you need it.
Personally I don't like wrappers, you may be making it simple to use, but
you are also loosing functionality IMO.

Duane Christen

-----Original Message-----
From: Hewitt, Rory [mailto:rory.hewitt@xxxxxx]
Sent: Thursday, July 28, 2005 11:48 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: RE: Trials and tribulations of QMHSNDPM (Was: No
Subroutines...)


Duane,

>>Use copybooks. 

Like many shops, mine is happy (relatively) with D-specs being copied
in, but not C-specs. Something about being able to see all the 'code'...
Not my choice.

Now what would be even better would be able to include a single copybook
which could include multiple specs (at least D- and C-specs) and have
the compiler sort them out and place them in the appropriate place. I
have a precompiler which includes processing to do this, but even so,
it's not ideal...

Rory