adelman@TGV.COM (Kenneth Adelman) (02/03/89)
> Rather than STRU VMS, make it STRU {LOCAL|EXOTIC}. If two VMS hosts > were "inter-operating" than either option would work correctly. > That way we don't run out of single character mneumonics for all the > "Open" operating systems coming down the line. Just a STRU EXOTIC isn't enough, because we'd like to be able to send a STRU VMS on client startup. If it is accepted, then we use that mode by default. The problem with STRU EXOTIC is that something else might accept it. I think that "STRU O VMS" is a good idea, where "O" stands for Operating System dependent. There are two reasons for this: 1) It would be a big help to Wollongong not to call the result STRU VMS since they already have software in the field which uses this with a non-standard encapsulation. Calling it something else would give them compatibility between releases. 2) We don't run into the 26 character limit (for those people who only look at the first character). Any objections to this???? Ken