Re: [EXTERNAL] Re: What could cause a signature violation?

I'd call Implementer support...

Unless David jumps in :)

I don't know how Implementer works, but IIRC with Aldon, you had two
choices,
1) Recreate on promotion
2) Move object without recreate

So I could see how it might happen with option 2, assuming the developer
created it wrong from RDI or something.

Charles

On Mon, Nov 1, 2021 at 8:02 AM Alan Shore via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Thanks for your reply Charles
That's scary as we use Implementer to promote into production

Alan Shore
Solutions Architect
IT Supply Chain Execution

[cid:image001.png@01D7CF07.90777EB0]

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 10:01 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [EXTERNAL] Re: What could cause a signature violation?

It didn't.

Whoever recreated the *SRVPGM used export(*ALL) instead of using the binder
source, which resulted in a generated signature.

Charles