RE: Need help with a service program

Unfortunately, even if your CRTSRVPGM default is *SRCFILE, Aldon seems to
override it to *ALL (or there is a global override that I never found). I
had to create an entry for this service program to force it to use *SRCFILE.

My problem was whoever created this program in the beginning did it wrong by
including a binding directory that was not needed. Also per someone else's
recommendation in an earlier email, a service program should have its own
binding directory with just what is needed to build that one service
program. That would also eliminate this problem.

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Englander, Douglas
Sent: Monday, August 15, 2016 1:32 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: Need help with a service program


John,

I have worked with Aldon before. When you change a service program in your
development area by checking it out and compile/create it in DVP, you can
view the signature(s) for the service program (using DSPSRVPGM command) in
that environment after a successful compile. If the signatures in the
development environment match exactly to what is listed in production, then
in most cases (98%+) you will be fine. If you are changing an export and use
*SRCFILE, you should see the new current signature that is created, along
with all of the prior ones [displays 1 and 9 of the DSPSRVPGM command].

As you promote the service program through your other environments, examine
the signatures after every promotion, and you will see if there was a
change. Also, as you promote a service program through the environments,
test one or two programs that reference the changed service program to make
sure you do not get Signature Violation errors.

If you tell Aldon to promote and recompile all related objects, then you
should not receive the Signature Violation. If you do not recompile related
objects, then testing some programs that reference the service program [in
an environment other than Production] allows you to address any Signature
Violations at that time before the final promotion to Production.

Hope this helps.

Doug

--
This is the RPG programming on the IBM i (AS/400 and 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.

Please contact support@xxxxxxxxxxxx for any subscription related questions.