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

[Charles Wilt <charles.wilt@xxxxxxxxx>]

It didn't.

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

Charles

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

> Thanks Rob
> Apart from the one program in my library - they match
> My question is - why did the signature change?
> I inserted one line of code in the service program
> I didn't think that would have changed the signature
>
> Alan Shore
> Solutions Architect
> IT Supply Chain Execution
>
> [cid:image001.png@01D7CF03.553AB000]
>
> 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 Rob Berendt
> Sent: Monday, November 1, 2021 9:27 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: RE: [EXTERNAL] Re: What could cause a signature violation?
>
> The signature on this:
> DSPPGM PGM(ROUTINES/CHGEML) DETAIL(*SRVPGM)
> should match one of the signatures on this:
> DSPSRVPGM SRVPGM(ROUTINES/SRVPGM) DETAIL(*SIGNATURE)
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to: 7310 Innovation Blvd, Suite 104
> Ft. Wayne, IN 46818
> Ship to: 7310 Innovation Blvd, Dock 9C
> Ft. Wayne, IN 46818
> http://www.dekko.com<http://www.dekko.com>
>
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:
> midrange-l-bounces@xxxxxxxxxxxxxxxxxx>> On Behalf Of Alan Shore via
> MIDRANGE-L
> Sent: Monday, November 1, 2021 9:19 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx
> <mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>
> Cc: Alan Shore <ashore@xxxxxxxx<mailto:ashore@xxxxxxxx>>
> Subject: RE: [EXTERNAL] Re: What could cause a signature violation?
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> Thanks for your reply Rob
> We have the following
> ...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 ...+.
> *************** Beginning of data
> ******************************************
> STRPGMEXP PGMLVL(*CURRENT) SIGNATURE('CRWDTWSTSP')
> /********************************************************************/
> /* *MODULE USPSSP AXSLIB 01/10/19 16:00:00 */
> /********************************************************************/
> EXPORT SYMBOL("GETCTUSERPROFILEBYID")
> EXPORT SYMBOL("GETCTFULFILL")
> EXPORT SYMBOL("GETCTCANCELFULFILL")
> EXPORT SYMBOL("CTREISSUEREWARD")
> EXPORT SYMBOL("CTPURCHASEDTLS")
> EXPORT SYMBOL("CTREISSUEPOINTS")
> ENDPGMEXP
>
> Alan Shore
> Solutions Architect
> IT Supply Chain Execution
>
> [cid:image001.png@01D7CF01.8538D450]
>
> 60 Orville Drive
> Bohemia, NY 11716
> Phone [O] : (631) 200-5019
> Phone [C] : (631) 880-8640
> E-mail : ASHORE@xxxxxxxxxxxxxxxxxxxx<mailto:ASHORE@xxxxxxxxxxxxxxxxxxxx>
>
> 'If you're going through hell, keep going.'
> Winston Churchill
>
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf
> Of Rob Berendt
> Sent: Monday, November 1, 2021 9:15 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx
> <mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>
> Subject: RE: [EXTERNAL] Re: What could cause a signature violation?
>
> In binder language there are maybe a total of four commands. You can
> actually support multiple signatures. Each signature is on the STRPGMEXP
> command. This helps to avoid signature violations
>
> Here is a sample
> STRPGMEXP PGMLVL(*CURRENT) LVLCHK(*YES) SIGNATURE('V20211001')
> EXPORT SYMBOL("ADDDAYS")
> EXPORT SYMBOL("CENTER40")
> ...
> ENDPGMEXP
> STRPGMEXP PGMLVL(*PRV) LVLCHK(*YES) SIGNATURE('V20210825')
> EXPORT SYMBOL("ADDDAYS")
> EXPORT SYMBOL("CENTER40")
> ...
> ENDPGMEXP
> STRPGMEXP PGMLVL(*PRV) LVLCHK(*YES) SIGNATURE('V20200704')
> EXPORT SYMBOL("ADDDAYS")
> EXPORT SYMBOL("CENTER40")
> ...
> ENDPGMEXP
>
> I could have given you a more 'live' example but programmers following me
> decided not to use multiple signatures and trashed it all and just
> recompile everything. If they are using service programs at all.
> If this
> DSPSRVPGM SRVPGM(ROUTINES/SRVPGM) DETAIL(*SIGNATURE)
> Looks like this garbage
> A5AE6D8F472C4062A3B65BB050DA6E4A
> 4A5AE6D8F472C409BC1E294E76E16998
> Then either they aren't using binder language, or they just use
> SIGNATURE(*GEN) instead of assigning a signature.
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to: 7310 Innovation Blvd, Suite 104
> Ft. Wayne, IN 46818
> Ship to: 7310 Innovation Blvd, Dock 9C
> Ft. Wayne, IN 46818
> http://www.dekko.com<http://www.dekko.com><http://www.dekko.com<
> http://www.dekko.com>>
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:
> midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:
> midrange-l-bounces@xxxxxxxxxxxxxxxxxx%
> 3cmailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx>>> On Behalf Of Alan Shore
> via MIDRANGE-L
> Sent: Monday, November 1, 2021 8:59 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx
> <mailto:midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx
> %3cmailto:midrange-l@xxxxxxxxxxxxxxxxxx>>>
> Cc: Alan Shore <ashore@xxxxxxxx<mailto:ashore@xxxxxxxx<mailto:
> ashore@xxxxxxxx%3cmailto:ashore@xxxxxxxx>>>
> Subject: RE: [EXTERNAL] Re: What could cause a signature violation?
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> Thanks John - but what do you mean by "garbage"
>
> Alan Shore
> Solutions Architect
> IT Supply Chain Execution
>
> [cid:image001.png@01D7CEFE.B0EB3AA0]
>
> 60 Orville Drive
> Bohemia, NY 11716
> Phone [O] : (631) 200-5019
> Phone [C] : (631) 880-8640
> E-mail : ASHORE@xxxxxxxxxxxxxxxxxxxx<mailto:ASHORE@xxxxxxxxxxxxxxxxxxxx
> <mailto:ASHORE@xxxxxxxxxxxxxxxxxxxx%3cmailto:ASHORE@xxxxxxxxxxxxxxxxxxxx>>
>
> 'If you're going through hell, keep going.'
> Winston Churchill
>
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf
> Of Jon Paris
> Sent: Monday, November 1, 2021 8:51 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx
> <mailto:midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx
> %3cmailto:midrange-l@xxxxxxxxxxxxxxxxxx>>>
> Subject: [EXTERNAL] Re: What could cause a signature violation?
>
> My best guess is that the binder language wasn't used when the programs
> were created. You can easily check this by resurrecting one of the ones you
> just recompiled and viewing the signature. If it is just "garbage" then
> that is almost certainly the answer.
>
>
> Jon Paris
>
> > On Nov 1, 2021, at 6:44 AM, Alan Shore via MIDRANGE-L <
> midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx<mailto:
> midrange-l@xxxxxxxxxxxxxxxxxx%3cmailto:midrange-l@xxxxxxxxxxxxxxxxxx
> <mailto:midrange-l@xxxxxxxxxxxxxxxxxx%
> 3cmailto:midrange-l@xxxxxxxxxxxxxxxxxx%
> 3cmailto:midrange-l@xxxxxxxxxxxxxxxxxx%
> 3cmailto:midrange-l@xxxxxxxxxxxxxxxxxx>>>> wrote:
> > Hi everyone
> > We are on V7r3
> > We have a service program that has 6 procedures
> > Last Friday, I had to make a change to one of the procedures - and that
> change was to insert one line of code into one procedure
> > Just to populate a field
> > Now - every program that uses those 6 procedures had a Program signature
> violation - MCH4431
> > As this is a relatively new service program - that number of programs
> involved is relatively small
> > So I just recompiled them - yes - I know I could have used UPDPGM
> > They are now working as expected
> > The binding program specifies a signature as well as the 6 procedures -
> in order
> > I am scratching my head as to why a signature violation happened
> > Any one any ideas as to what I can look at?
> >
> > Alan Shore
> > Solutions Architect
> > IT Supply Chain Execution
> >
> > [cid:image003.png@01D7CEEB.EF9450B0]
> >
> > 60 Orville Drive
> > Bohemia, NY 11716
> > Phone [O] : (631) 200-5019
> > Phone [C] : (631) 880-8640
> > E-mail : ASHORE@xxxxxxxxxxxxxxxxxxxx<mailto:ASHORE@xxxxxxxxxxxxxxxxxxxx
> <mailto:ASHORE@xxxxxxxxxxxxxxxxxxxx%3cmailto:ASHORE@xxxxxxxxxxxxxxxxxxxx
> <mailto:ASHORE@xxxxxxxxxxxxxxxxxxxx%3cmailto:ASHORE@xxxxxxxxxxxxxxxxxxxx
> %3cmailto:ASHORE@xxxxxxxxxxxxxxxxxxxx%3cmailto:ASHORE@xxxxxxxxxxxxxxxxxxxx
> > > >
> >
> > 'If you're going through hell, keep going.'
> > Winston Churchill
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:
> MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx%
> 3cmailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:
> MIDRANGE-L@xxxxxxxxxxxxxxxxxx%3cmailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx%
> 3cmailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx%
> 3cmailto: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><
> https://lists.midrange.com/mailman/listinfo/midrange-l<
> https://lists.midrange.com/mailman/listinfo/midrange-l>><
> https://lists.midrange.com/mailman/listinfo/midrange-l<
> https://lists.midrange.com/mailman/listinfo/midrange-l><
> 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<mailto:
> MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx%
> 3cmailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:
> MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx%
> 3cmailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx%
> 3cmailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx%
> 3cmailto: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><
> https://archive.midrange.com/midrange-l<
> https://archive.midrange.com/midrange-l>><
> https://archive.midrange.com/midrange-l<
> https://archive.midrange.com/midrange-l><
> https://archive.midrange.com/midrange-l<
> https://archive.midrange.com/midrange-l>>>.
> > Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:
> support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx%
> 3cmailto:support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx%
> 3cmailto:support@xxxxxxxxxxxxxxxxxxxx%
> 3cmailto:support@xxxxxxxxxxxxxxxxxxxx%
> 3cmailto: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><
> https://amazon.midrange.com<https://amazon.midrange.com>><
> https://amazon.midrange.com<https://amazon.midrange.com><
> https://amazon.midrange.com<https://amazon.midrange.com>>>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:
> MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx%
> 3cmailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:
> MIDRANGE-L@xxxxxxxxxxxxxxxxxx%3cmailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx%
> 3cmailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx%
> 3cmailto: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><
> https://lists.midrange.com/mailman/listinfo/midrange-l<
> https://lists.midrange.com/mailman/listinfo/midrange-l>><
> https://lists.midrange.com/mailman/listinfo/midrange-l<
> https://lists.midrange.com/mailman/listinfo/midrange-l><
> 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<mailto:
> MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx%
> 3cmailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:
> MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx%
> 3cmailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx%
> 3cmailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx%
> 3cmailto: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><
> https://archive.midrange.com/midrange-l<
> https://archive.midrange.com/midrange-l>><
> https://archive.midrange.com/midrange-l<
> https://archive.midrange.com/midrange-l><
> https://archive.midrange.com/midrange-l<
> https://archive.midrange.com/midrange-l>>>.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:
> support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx%
> 3cmailto:support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx%
> 3cmailto:support@xxxxxxxxxxxxxxxxxxxx%
> 3cmailto:support@xxxxxxxxxxxxxxxxxxxx%
> 3cmailto: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><
> https://amazon.midrange.com<https://amazon.midrange.com>><
> https://amazon.midrange.com<https://amazon.midrange.com><
> https://amazon.midrange.com<https://amazon.midrange.com>>>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:
> MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx%
> 3cmailto: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><
> 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<mailto:
> MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx%
> 3cmailto: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><
> https://archive.midrange.com/midrange-l<
> https://archive.midrange.com/midrange-l>>.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:
> support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx%
> 3cmailto: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><
> https://amazon.midrange.com<https://amazon.midrange.com>>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:
> MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx%
> 3cmailto: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><
> 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<mailto:
> MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx%
> 3cmailto: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><
> https://archive.midrange.com/midrange-l<
> https://archive.midrange.com/midrange-l>>.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:
> support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx%
> 3cmailto: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><
> https://amazon.midrange.com<https://amazon.midrange.com>>
> --
> 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>
> --
> 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>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com