Hi Charles
I agree
The problem is with how the object is promoted into production and the way the implementer parameters are set
For the moment, I have left things as they are as all the programs have all been re-compiled and are working
The next change to this service program will require a re-compile of all the same programs or UPDPGM for all of them
At least I know what the cause was - and for that - thanks to all who replied
Alan Shore
Solutions Architect
IT Supply Chain Execution
[cid:image001.png@01D7CF2C.C5D7BDC0]
60 Orville Drive
Bohemia, NY 11716
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
E-mail : ASHORE@xxxxxxxxxxxxxxxxxxxx
'If you're going through hell, keep going.'
Winston Churchill
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Monday, November 1, 2021 2:24 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [EXTERNAL] What could cause a signature violation?
Except the current signature IS garbage
The service program has a signature of
Current export signature . . . . . . . . . . . . :
E855C017596794C8F164E37656A0C4BE
That translates to ("Y.{<POC>..mH1.T...D."
The prior *SRVPGM signature was the hex value for "CRWDTWSTSP"
Message . . . . : Program signature violation.
Cause . . . . . : The source program TSTPRCHDTL specifies a signature
X'C3D9E6C4E3E6E2E3E2D7404040404040' which is not supported by service
Charles
On Mon, Nov 1, 2021 at 11:25 AM Peter Dow <petercdow@xxxxxxxxx<mailto:petercdow@xxxxxxxxx>> wrote:
Except that is not garbage, it is the hex translation of "CRWDTWSTSP".
On 11/1/2021 7:17 AM, Jon Paris wrote:
Well that is a perfect example of what I meant by a "garbage" signature.
The program was apparently created when the service program had a
signature of "CRWDTWSTSP" - which looks as if it is probably correct. But
the service program has apparently been re-created without binder source
and now has a signature that is clearly generated garbage - it translates
(or rather doesn't) as "Y.{<POC>..mH1.T...D."
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l<
https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/midrange-l<
https://archive.midrange.com/midrange-l>.
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com<
https://amazon.midrange.com>
midrange.com
