|
DataMuseum.dkPresents historical artifacts from the history of: DKUUG/EUUG Conference tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about DKUUG/EUUG Conference tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: T i
Length: 3406 (0xd4e) Types: TextFile Names: »isoentities.5«
└─⟦3d0c2be1b⟧ Bits:30001254 ISODE-5.0 Tape └─⟦eba4602b1⟧ »./isode-5.0.tar.Z« └─⟦d3ac74d73⟧ └─⟦this⟧ »isode-5.0/support/isoentities.5«
.TH ISOENTITIES 5 "31 May 1988" .\" $Header: /f/osi/support/RCS/isoentities.5,v 6.0 89/03/18 23:44:45 mrose Rel $ .\" .\" .\" $Log: isoentities.5,v $ .\" Revision 6.0 89/03/18 23:44:45 mrose .\" Release 5.0 .\" .SH NAME .B isoentities \- ISODE entities database .SH DESCRIPTION The \fIisoentities\fR file contains information regarding the known application entity titles (AETs). This file is used by the stub\-directory service in ISODE. .PP Entries are separated by blank lines (or the end\-of\-file). Items are separated by any number of blanks and/or tab characters, though double\-quotes may be used to prevent separation between arguments. The character `#' at the beginning of a line indicates a comment line. .PP There are two formats for an entry. The old format is now described. Note that this format will not be supported in the next release. Therefore it is imperative that the new format be used in order to minimize future problems. .SH "OLD FORMAT" The first two items are the designator (host) and qualifier (service) associated with the AET. The distinguished host \*(lqdefault\*(rq is used for a template entry. Together, these two form the object descriptor definition of the AET. .PP The third item is the object identifier definition of the AET. This is expressed in dot-notation. If no AET is desired, then the string \*(lqNULL\*(rq should be used. .PP The fourth, fifth, and sixth items are the presentation, session, and transport selectors (respectively) for the associated presentation address. If these items start with a hash-mark (`#'), they are interpreted numerically as a decimal short-word quantity; otherwise if these items appear in double\-quotes, they are interpreted as an ascii string, with the usual escape mechanisms for introducing non\-printable characters; otherwise, they are interpreted as an exploded octet string. .PP Any remaining items (if any) form a network address. Following lines (until the first blank line or end\-of\-file) define additional network addresses. .SH "NEW FORMAT" The new format consists of four items. The first three items (designator, qualifier, and AET) remain the same. The fourth item is the entire presentation address expressed using the ISODE string format. Note that since double-quotes are often used in the new string format, it is \fBvery\fR important to quote them correctly in the \fIisoentities\fR file. Usually preceeding the first character of the address with backslash is adequate. .PP In the present release, a blank line should seperate entries. Note that in the next release, the blank line will not be necessary but should be retained for readability. .PP Note that this database is used by the stub-directory service in ISODE. A real directory uses an entirely different mechanism for resolving lookups. The stub-directory mechanism in ISODE transforms the internal AET notion (the object identifiers) into one which appears to have come from a real directory (i.e., application entity information). .SH FILES .nf .ta \w'/usr/etc/isoentities 'u /usr/etc/isoentities ISODE entities database .re .fi .SH "SEE ALSO" isobjects(5), isoservices(5), .br \fIThe ISO Development Environment: User's Manual, Volume 1: Application Services\fR, \*(lqThe ISODE Entities Database\*(rq. .SH AUTHOR Marshall T. Rose, The Wollongong Group .br with design conceptualization by Stephen E. Kille, University College London