Re: Signature violations

Steve Richter wrote on 26/06/2007 21:37:08:

On 6/26/07, Buck <kc2hiz@xxxxxxxxx> wrote:

My original suggestion for you to use hard coded signatures was based

on

my mistaken assumption that you simply didn't like the signature
violation concept. Hard code the sig, no violation :-) Having said
that, lvlchk(*no) is not the same as a hard coded signature because we
have the ability to make an intelligent signature, viz:

strpgmexp pgmlvl(*current) signature('01.00 20070404')

With this mechanism I can clearly define which version of the exports
are bound to a program.

Buck,

maybe I am wrong on this. If I am correct, I think it is important for
people to understand the problems you are exposed to if you
incorrectly use service programs.

*prv signatures dont protect from the problem of reordering of the
exports of the srvpgm. As I understand it, the *PRV and *current
signatures of a srvpgm are the ones that will not signal a signature
violation. But if you insert or remove entries from the binding
source, which causes the export numbers of your exports to change,
your applications are going to fail - despite the fact you dont get a
signature violation.

That's correct Steve. *PRV signatures are pretty much a more specific
lvlchk(*no). That is, you can say "any of the listed signatures are
valid". However, the srvpgm itself still retains only one list of entry
points. I agree that this part of binder language is confusing and
somewhat misleading. That said, there is a simple way to make it easier
... don't use *PRV. IMHO, *PRV signatures are really only useful for
documentation purposes, and there are more straightforward ways of
documenting source.

- Adam

Attention:

The information contained in this message and or attachments is
intended only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon, this
information by persons or entities other than the intended recipient is
prohibited. If you received this message in error, please contact the sender
and
delete the material from any system and destroy any copies. Thank you for your
time and consideration.

Attention:

Le contenu de ce message et(ou) les fichiers ci-joints s?adressent
exclusivement à la personne ou -entité à laquelle ils sont destinés. Ils
peuvent
contenir de l?information confidentielle, protégée et(ou) classifiée. Il est
strictement interdit à toute personne ou entité autre que le(la) destinataire
prévu(e) de ce message d?examiner, de réviser, de retransmettre ou de diffuser
cette information, de prendre une quelconque action en fonction ou sur la base
de celle-ci, ou d?en faire tout autre usage. Si vous avez reçu ce message par
erreur, veuillez communiquer avec l?expéditeur(trice), supprimer ce message et
les fichiers ci-inclus de tout système, et en détruire toutes copies, qu?elles
soient électroniques ou imprimées. Nous vous remercions de votre entière
collaboration.