Re: Security Routines - bind by copy? (wasRE: Questionabout serviceprograms)

David Gibbs wrote:

True. But can't I just do an updpgm with a new module to replace yours?
I guess the argument is that I'd need to know the signature which is
easier to know for a srvpgm than an embedded module.

Assuming the service program is not explicitly qualified in the program (i.e., using library list), putting a new service program higher on the library list is trivial and the easiest thing to do, imo.

Ah, good old SYSnnn (numeric designation removed to protect the guilty). You wrote a four-line version of this program, put it higher in your library list, and suddenly BPCS had no licensing. But you didn't hear it from me...

Doing an UPDPGM could work assuming you had the authority. This, however, would probably leave incriminating tracks.

At the least it would change the last modified date, no? I guess you could make your own version, put it higher in the library list, and then delete it when you were done. But as Walden points out, it's hard to know how to write that module. Not impossible, but also not something the average i programmer is going to know how to do. That's why I bind by copy.

Joe