Difficult but not impossible. Check the library list of the QZRCSRVS
jobs. (They should all be the same.) See if you have two service
programs. If so, do they both have the same signature? Hold all of the
QZRCSRVS jobs except one you put into debug.
**Warning** This can impact production if you use these jobs for many
application / users.
Second approach is to start your service job on one of the QZRCSRVS job,
put the called program into debug and set a break point just before the
procedure execution. Change the run priority of the serviced job to a
low number such as 15. This should make this job get the next request.
It will only break if it is going to call the procedure you want to
check otherwise it will run without a hitch.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Thursday, March 06, 2008 9:08 AM
To: Midrange Systems Technical Discussion
Subject: Re: Service program signature violation puzzler
Chris Bipes wrote:
Can you check the program stack in the QZRCSRVS program? Verify the
Library List as well and check for copies of the program / service
programs.
That's pretty difficult ... the job goes active and immediately
terminates. None of my code is ever running.
Odd thing is, this particular version of the code has been running for a
few weeks without problems.
midrange.com
