RE: Service Program Error

Chris,
It sounds like your UPDPGM added the changed module objects to the PGM
itself, in order to do that, it would have had to have been there already.
So I'm assuming the new objects have DBGVIEW(*LIST) in them, which would
cause them to at least double in size.

Does the new module you created (which you referred to as a "program", I'm
assuming this reference is out of habit) have the NOMAIN keyword on the
Header spec? If not and you expect it to go into a service program, then you
have a bad design. 

Whenever you change a source member, in this case a procedure, and
recompile, you can use UPDSRVPGM to update the service program in which it
was originally stored. If no changes to the source member in the way of
adding new procedures or changing the order, then you shouldn't have any
other issues. 

>From what you suggested, I'm guessing you changed the location of the
procedure in the source code. That is it was previously subprocedure number
5 (for example) in the source, but now it is number 4, or 1 or something
like that.  That will cause the kind of issue you're observing.

-Bob

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Chris_Bougher@xxxxxxxxxxxxx
Sent: Thursday, May 20, 2004 7:08 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Service Program Error

I have a set of programs that use a service program. When they were first
implemented everything worked fine. One of the programs needed to be
changed a week later and after the change was made and the program put into
production everything started to break. The call stack was like this:

OPM Program in activation group default called
ILE Program in activation group ILE used
Srv Program in activation group SRVPGM

The error was coming from the service program and from a procedure that
shouldn't have even been called.

The fix after many hours of agonizing was to use UPDPGM command on the ILE
program. This worked but also increased the size of the program object
almost double. My question now is what happened to the bindings? Why did
the program increase in size after UPDPGM? Why did a procedure that was not
even called bomb?

Not the OPN and SRVPGM were not changed. and the change to the ILE program
did not involve any calls to the service program.

Thanks
Chris Bougher



_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.