Re: Need help with a service program

Hi John,

I don't think finding the previous signature will help you if you changed
the parameter definitions.
As Buck said earlier, do a DSPPGM on one of the programs that is using the
service program.
Page through until you get to the *SRVPGM screen. It will show you a list
of service programs and the signature of each.
You will see what the signature used to be.
Specifying the old signature on your *PRV line will likely prevent the
signature violation messages but if the parameter definitions were changed,
your program will have problems.



Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (416) 675-9200 ext. 89224
Cell: (416) 317-3144


On 12 August 2016 at 11:55, John R. Smith, Jr. <smith5646midrange@xxxxxxxxx>
wrote:

I follow what you are saying but without rebinding our entire system, how
to
I get it to find the *PRV signature?

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Glenn
Gundermann
Sent: Friday, August 12, 2016 11:51 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
<rpg400-l@xxxxxxxxxxxx>
Subject: Re: Need help with a service program

John,

It looks to me that one or more parameter definitions changed.
Check a compile listing of the old version and compare it to a compile
listing of the new version.
The signature violation between a program and a service program is similar
to how a program gets a level check with a file that has changed.


Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (416) 675-9200 ext. 89224
Cell: (416) 317-3144


On 12 August 2016 at 11:46, John R. Smith, Jr. <
smith5646midrange@xxxxxxxxx>
wrote:

No parm changes, just internal code changes.

Here is the error from the joblog,
Message . . . . : Program signature violation.
Cause . . . . . : The source program LOG03A specifies a signature
X'0000000000E2B8F13A38E3DA45E0F302' which is not supported by service
program CMSRV1. Recovery . . . : The service program interface has
changed. Re-bind source program LOG03A.

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Glenn Gundermann
Sent: Friday, August 12, 2016 11:44 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
<rpg400-l@xxxxxxxxxxxx>
Subject: Re: Need help with a service program

John,

Did you change the number of parameters or the size of any of the
parameters?
What error messages you are getting when you execute the service program?


Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (416) 675-9200 ext. 89224
Cell: (416) 317-3144


On 12 August 2016 at 11:35, John R. Smith, Jr. <
smith5646midrange@xxxxxxxxx>
wrote:

I'm not sure I understand your question. I modified code inside of
function SCGETNVP. I did not add a new function. Does that answer
your question?

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Michael Ryan
Sent: Friday, August 12, 2016 11:25 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
<rpg400-l@xxxxxxxxxxxx>
Subject: Re: Need help with a service program

Buck has the right suggestions. Question: Why is your export
*CURRENT and *PRV the same?

On Fri, Aug 12, 2016 at 11:22 AM, Buck Calabro <kc2hiz@xxxxxxxxx>

wrote:

On 8/12/2016 11:08 AM, John R. Smith, Jr. wrote:

I've done something wrong and have no clue what. We have a
service

program

(CMSRV1) called by many RPGLE programs. I recently migrated a
change to

it

and stuff is blowing up all over with Signature Violations.

In the BND source, we have the following:

-snip-

What piece did I miss?

If you could post the CRTSRVPGM command you used, we'd be able to
pinpoint it. Best guesses:

1) EXPORT(*ALL) instead of *SRCFILE
2) EXPORT(*SRCFILE) with the wrong SRCFILE() specified. Like test
vs production.

Further diagnostics:
Do a DSPSRVPGM to see what the current signature is.
Do a DSPPGM to see what signatures the calling programs expect.

--
--buck