Re: Wanted:MAIL.MAI structure definition

On Tue, 06 Jun 2006 13:20:41 -0700, Hoff Hoffman <hoff-remove-this@xxxxxx> wrote:

Tom Linden wrote:

I understand that the layout is subject to change, but why couldn't the definition be included in starlet. Just curious.

Before any further discussion here: I am aware of no plans to make the MAIL definitions externally visible -- the recommended approach for most operations involves the use the MAIL calling interface, and the use of the available itemcodes and structures associated with that interface.

OpenVMS source code facilities (and most layered products, for that matter) that weren't intending or intended to share their data structure definitions outside the facility tend to have them located locally; within the OpenVMS facility. If you have to reach into the facility directories within an OpenVMS build, you tend to realize you're using an unpublished and volatile interface, after all.

Nothing technically prevents relocating the definitions, but this would obviously also include a requirement to recode and rebuild the facility -- and the folks maintaining the facility would also have to accept some number of folks "locking into" the definitions, too. The reloocation is easily feasible. Convincing various of the engineers involved around the need to open the API is the challenge.

FWIW, STARLET is the "published" area. LIB is the "volatile" area; the area where the system- and version and semi-documented definitions tend to reside.

In this particular corruption case, I'd still focus on figuring out where the problem is lurking -- an approach based on having to re-verify the mail files for corruptions seems to be somewhat less than optimal. (And if it's MAIL that's involved, the obvious approach would include fixing the error, and (if needed) the addition of the necessary repair tool(s) into one of the MAIL facilities within OpenVMS itself.)

As I said, it was just curiosity. If there is not a compelling reason to
keep something proprietary, then starlet it. There, I created a new verb..

.

Relevant Pages

  • Re: Wanted:MAIL.MAI structure definition
    ... the MAIL definitions externally visible -- the recommended approach for most operations involves the use the MAIL calling interface, and the use of the available itemcodes and structures associated with that interface. ... OpenVMS source code facilities that weren't intending or intended to share their data structure definitions outside the facility tend to have them located locally; ... STARLET is the "published" area. ...
    (comp.os.vms)
  • Re: Yet another OO question...
    ... So an architect may design a house, and a builderwill implement the design and build any number of individual houses of the same plan. ... Think of a interface as a contract. ... Create a different class for each facility that implements the Facility interface. ... add a new venue to your venues list. ...
    (comp.lang.java.programmer)
  • Re: COBOL Transactions?
    ... need to do, here is how I would normally do it, what is the facility ... under VMS that does this?" ... OpenVMS does work with tapes, and if it's a working SCSI drive then ... While we're here, though, are you sure that your dirt cheap Alpha was ...
    (comp.os.vms)
  • Re: Interaction between ipfw, IPSEC and natd
    ... > Just sort of thinking out loud here, would some kind of daemon (or ... > interface, like pipsecd does, but use the kernel's IPSec facility to ... I think so - but I don't see why a daemon whould be necessary. ...
    (FreeBSD-Security)
  • Re: Comments concerning TR 24731
    ... you make far more radical changes to the language. ... any such facility should include some interoperability ... interface. ...
    (comp.std.c)