System Software Library Distributed Name Service (DNS) Management Operations Manual Product Version DNS D00 Release ID C20/D00 Edition Print Date Part Number Abstract February 1992 31258 This manual describes the interactive Distributed Name Service (DNS) interface, DNSCOM, used to maintain the names of objects controlled by Tandem and other systems. It is intended for those who devise and implement the naming strategy used in a network.
Document History Edition Part Number Product Version Release ID Print Date First Edition 31258 DNS D00 C20/D00 February 1992 New editions incorporate any updates issued since the previous edition. Examples Export Statement Copyright Examples and sample programs are for illustration only and may not be suited for your particular purpose.
Contents About This Manual xv Notation Conventions Section 1 xix Introducing Distributed Name Service The Need for Better Name Management The DNS Solution Users of DNS 1-4 1-5 Ways to Use DNS Programmatically Interfaces to the DNS Database 1-5 1-7 DNS Architecture 1-9 DNS Files Loaded by Install DNS Configurations 1-10 Section 2 1-2 1-9 Introducing DNS Names Command Object Keywords Subsystem Names 2-2 Subsystem Managers 2-2 Subsystem-Object Names DNS Type Names 2-1 2-3 2-3 DNS Object
Contents Updating the DNS Database Changing DNS File Names 3-7 3-8 DNS File and Database Security 3-9 Changing DNS Ownership 3-10 Security Through Operating Modes Security Through Safeguard 3-11 Backing up the DNS Configuration Recreating a Configuration File 3-11 3-12 3-12 Updating Definitions on Unavailable Nodes 3-12 Error Recovery Reloading the DNS Database Section 4 3-13 Building and Modifying the DNS Database Selecting a Naming Strategy 4-1 Introduction to Defining DNS Names 4-3 Name Dep
Contents Section 5 How DNS Exports the Name Database The Name Manager 5-1 Naming the Name Manager to Support Exporting TMF and the Name Manager 5-2 5-1 The Name Exporter 5-2 Naming the Name Exporter to Support Exporting TMF and the Name Exporter 5-2 5-2 The Queue File 5-3 DNS Database Replication 5-3 The Export Process 5-3 Time-Staged Replication 5-5 Type Mismatch and Hold Queues 5-7 How DNS Avoids Name Duplication and Incompatibility 5-7 Important Considerations About Database Distribution 5-8 Dist
Contents When to Use the AT, IN, ON, UNDER, and USING Phrases 6-13 Making Inquiries With the Wild-Card Symbol 6-14 Accessing Another Configuration for a Single Command 6-15 Working With Lists in Commands 6-16 Combining the RESET Command With the ALTER or ADD Commands 6-17 Directing Output With the OUT Command 6-18 Ambiguous Names (Error 1034) Section 7 6-18 The DNSCOM Commands Overview of DNSCOM Commands 7-1 Important Notes About Individual Commands 7-8 Notes About ADD Commands 7-8 Notes About ALTER C
Contents ALTER SSMANAGER ALTER SSOBJECT ALTER SSTYPE ASSUME CLOSE 7-65 7-67 7-69 7-70 CMDSYS 7-71 CMDVOL COPY * 7-63 7-72 7-73 COPY ALIAS 7-74 COPY COMPOSITE COPY GROUP 7-76 7-78 COPY MEMBERS DELETE ALIAS 7-79 7-80 DELETE ALIASTYPE 7-82 DELETE COMPOSITE 7-83 DELETE COMPOSITETYPE DELETE DNSDOMAIN DELETE GROUP DELETE SS 7-90 DELETE SSOBJECT DELETE SSTYPE 7-94 7-96 ENABLE EXPORT 7-97 EXIT 7-99 FC 7-91 7-92 DISABLE EXPORT 7-98 7-87 7-88 DELETE SSMANAGER ENV 7-85 7-100 HE
Contents INFO DNS 7-113 INFO DNSDOMAIN INFO DNSFILE 7-115 7-117 INFO DNSPROCESS INFO GROUP 7-121 INFO MEMBERS INFO SS 7-119 7-124 7-126 INFO SSMANAGER INFO SSOBJECT INFO SSTYPE 7-130 7-133 INITIALIZE DNS LIST * 7-128 7-135 7-137 LIST ALIAS 7-138 LIST ALIASTYPE 7-140 LIST COMPOSITE 7-141 LIST COMPOSITETYPE LIST DNS 7-145 LIST DNSDOMAIN LIST DNSFILE LIST GROUP 7-152 7-153 LIST SSMANAGER LIST SSOBJECT LIST SSTYPE NAMESYS 7-159 7-160 7-162 OBEYVOL x 7-155 7-161 OBEYSYS OUT
Contents RESELECT 7-166 RESET ALIAS 7-167 RESET ALIASTYPE 7-168 RESET COMPOSITE 7-169 RESET COMPOSITETYPE RESET DNS 7-171 RESET DNSDOMAIN RESET DNSFILE 7-172 7-173 RESET DNSPROCESS RESET GROUP RESET SS 7-174 7-175 7-176 RESET SSMANAGER RESET SSOBJECT RESET SSTYPE RESTORE * 7-177 7-178 7-179 7-180 RESTORE ALIAS 7-181 RESTORE COMPOSITE RESTORE GROUP 7-186 7-187 SET ALIAS 7-188 SET ALIASTYPE 7-191 SET COMPOSITE 7-194 SET COMPOSITETYPE SET DNS 7-197 7-200 SET DNSDOMAIN SET D
Contents SHOW ALIAS 7-221 SHOW ALIASTYPE 7-222 SHOW COMPOSITE 7-223 SHOW COMPOSITETYPE SHOW DNS 7-225 SHOW DNSDOMAIN SHOW DNSFILE SHOW GROUP 7-230 SHOW SSOBJECT SHOW SSTYPE START DNS 7-232 7-233 7-235 STATUS EXPORT STOP DNS 7-231 7-234 STATUS DNS 7-237 7-239 7-241 VOLUME 7-242 Appendix A Configuration File Verification Appendix B DNSCOM Error Messages Appendix C Reserved Words Glossary Glossary–1 Index xii 7-228 7-229 SHOW SSMANAGER SYSTEM 7-226 7-227 SHOW DNSPROCESS S
Contents Figures Figure 1-1. Objects and Their Names Figure 1-2. Retrieving a Subsystem-Object Name Figure 1-3. Retrieving an Alias Figure 1-4. Application Interfaces With DNS Figure 1-5. Components of DNS Figure 2-1. An ATM Is a Composite Object Figure 2-2. Sample Domains Figure 3-1. Using DNSCOM to Initialize DNS Figure 4-1. Group Hierarchy Example Figure 4-2. DNS Name Dependencies and Relationships Figure 4-3. Dependencies and Relationships of SS Names Figure 4-4.
Contents Tables Table 3-1. xiv DNS Database File Names 3-8 Table 4-1. Dependencies for Defining Names Table 4-2. DNS Name Parts Table 6-1. Attributes of Command Objects Table 6-2. Default Values for Special Attributes Table 7-1. Update Commands 7-2 Table 7-2. Inquiry Commands 7-4 Table 7-3. Operational Commands Table 7-4.
About This Manual The Distributed Name Service (DNS) Management Operations Manual provides subsystem-specific information about object management using the Tandem DNS subsystem. The interactive DNS interface, DNSCOM, allows users to send commands to modify, control, and monitor the DNS name database. The manual serves as both a reference manual to the DNSCOM commands as well as an aid to the first-time user of DNS, including introductory information, usage guidelines, and examples.
About This Manual Sections 5 through 7 provide reference information and overview information about DNSCOM as follows: How DNS exports (distributes) the DNS database (Section 5) Descriptions of DNS keywords and interfaces (Section 6) Various ways to enter DNSCOM commands (Section 6) Individual descriptions of the DNSCOM commands (Section 7) Appendix A lists the steps DNSCOM takes to verify a configuration file. Appendix B lists the DNSCOM error messages. Appendix C lists the DNS reserved words.
About This Manual DSMS System Management Guide explains the procedures for installing and configuring Distributed Systems Management Solutions. It also contains reference information used to extend DSMS. User’s Guide to the DSNM Commands contains instructions for using Distributed Systems Network Management (DSNM) commands to perform network management tasks. It also contains information about using NetCommand.
About This Manual xviii 31258 Tandem Computers Incorporated
Notation Conventions The following list summarizes the conventions for syntax presentation and other elements in this manual. Notation Meaning UPPERCASE LETTERS Uppercase letters represent keywords and reserved words; enter these items exactly as shown. Lowercase italic letters represent variable items that you supply. Brackets enclose optional syntax items. A group of vertically aligned items enclosed in brackets represents a list of selections from which you can choose one or none.
1 Introducing the Distributed Name Service The Distributed Name Service (DNS) subsystem operates in a Tandem NonStop system or an Expand network. To operate, DNS depends on the presence of the Guardian 90 operating system and the Transaction Monitoring Facility (TMF) on your system. DNS is part of the set of Tandem system management products known collectively as Distributed Systems Management (DSM).
Introducing Distributed Name Service The Need for Better Name Management Briefly, DNS provides facilities that: Maintain names of objects controlled by Tandem systems and other types of systems Provide alternative names (aliases) for objects Translate an alias to a subsystem-object names, allowing command interpreters to accept meaningful names Translate subsystem-object names to aliases, allowing event processing applications to report meaningful names to operators Organize objects into groups Provide a s
Introducing Distributed Name Service The Need for Better Name Management To appreciate the need for a good naming system, consider the following situations. The Guardian names of certain objects change fairly often. For instance, terminal names change as new communications lines are added and existing terminals are moved to these lines. Disk files are routinely moved from one physical volume to another, again requiring new names.
Introducing Distributed Name Service The DNS Solution The DNS Solution DNS is the Tandem solution to problems involved in managing object names in a distributed network. With DNS, you and other users can: Record and retrieve information about specific objects. For example, for a given object, you can record the name of the subsystem to which the object is defined, the name of the management process that controls the object, the object type, and other information.
Introducing Distributed Name Service Ways to Use DNS Programmatically Users of DNS If you are a system manager or system operator, you typically communicate with DNS through DNSCOM, the DNS interactive interface. This interface allows you to create the DNS database, control the DNS processes, and perform inquiry and update operations against the DNS name database. For example, you might ask DNS to break down a group into the individual objects that compose it and to display the names of those objects.
Introducing Distributed Name Service Ways to Use DNS Programmatically Figure 1-2. Retrieving a Subsystem-Object Name (Network Control Node) 2 STATUS LINE46 Network management application sends alias to DNS. LINE467 NMA 1 DNS \A.$LINE4 (SNAX line) User enters status command. 4 Network management application sends command with subsystem-object name to Subsystem Control Point. 3 DNS returns subsystem-object name used by operating system. STATUS \A.
Introducing Distributed Name Service Interfaces to the DNS Database Retrieving an alias. An application might obtain a subsystem-object name from an event message, pass that name to DNS, and retrieve from DNS an alias to use in reporting the event to users at terminals, as shown in Figure 1-3. Figure 1-3. Retrieving an Alias 2 Event Collector Management application sends subsystem object name to DNS. $TAPE1 Event Distributor 1 Event distributor reports event to user application.
Introducing Distributed Name Service Interfaces to the DNS Database DNS processes report events to the Event Management Service (EMS) primary collector ($0); applications can retrieve these event messages by using an EMS consumer distributor. You can find more details about EMS in the Event Management Service (EMS) Manual. Figure 1-4.
Introducing Distributed Name Service DNS Architecture DNS Architecture DNS consists of processes, configurations, and various files. Below is an overview of the major elements of the DNS subsystem. DNS Files Loaded by Install DNS is placed on your system by Install, as discussed in Section 3, “DNS Management and Operations.” During the REPSUBSYS phase, Install loads the following files: DNSCOM ($SYSTEM.SYSTEM.DNSCOM).
Introducing Distributed Name Service DNS Architecture LOAD ($altvol.ZDNS.LOAD). The load file is a command file that may be read by DNSCOM to initially load the DNS database with the definitions of some commonly used Tandem subsystems and their object types. DBDDLS ($altvol.ZDNS.DBDDLS). This is a Data Definition Language (DDL) source file that describes the DNS database. DNS Configurations Each DNS database is associated with a DNS configuration created with the INITIALIZE DNS command.
Introducing Distributed Name Service DNS Architecture Figure 1-5. Components of DNS Local Node Remote Nodes DNSCOM ••• DNS Database Files DNSCOM DNS Name Manager Management Application Queue File Management Application Name Exporter \A.name manager ••• DNS Configuration File \Z.
2 Introducing DNS Names This section describes the DNS names that compose the DNS name database. DNS names are defined and assigned to the objects that compose your systems, subsystems, and networks. For the most part, this is done with the DNSCOM commands. The concepts defined in this section should establish a basic understanding of the names that DNS manages. This section does not provide step-by-step procedures for creating and maintaining the DNS database.
Introduction to DNS Names Subsystem Names Subsystem Names In a Tandem computer system, a subsystem is defined as a program or set of processes that manages a cohesive set of objects. Examples of Tandem supplied subsystems are the File Utility Program (FUP), the Pathway transaction processing system, and the Spooler. A subsystem name identifies a Tandem subsystem, a subsystem you write, or a subsystem that you buy from an independent software vendor.
Introduction to DNS Names DNS Type Names Subsystem-Object An object is any entity controlled by a subsystem, often referred to as a subsystem Names object. Most objects are integrated parts of computer systems and networks such as terminals, lines, printers, and workstations. Objects are also pieces of information such as personal names, addresses, and phone numbers.
Introduction to DNS Names DNS Object Names When creating DNS type and name definitions, first you create a type definition, then you create an object or alias definition and include an existing type name in the definition of the object or alias. By linking the object or alias with its respective type, you assign the object or alias to a category that classifies it. In the example below, the subsystem-object name TERM26 is added to the DNS database.
Introduction to DNS Names DNS Object Names Figure 2-1. An ATM Is a Composite Object Components of the Composite PATHWAY SNAX SNAXHLS \B.$PM \B.ZNET \B.$HLS9 TERM-006 (Terminal) $LINE4.#LU3 (Logical Unit) #LINE4.LU3 (Session) Composite Object ATM-44 Composite Name S8121-007 Domains Within a network, all or part of the DNS database can be replicated (duplicated) on different nodes; only alias, composite, and group names can be replicated.
Introduction to DNS Names DNS Object Names Figure 2-2. Sample Domains DOMAIN1 \A \B DOMAIN2 \C \E Legend DOMAIN1 includes nodes A, B, and C. DOMAIN2 includes nodes C and E. S8121-008 By specifying the domain of a name, you permit or restrict the visibility and use of that name on other nodes. Operators and applications on any node in the domain can use the name or obtain information about it from local DNS processes. Domains can be automatically assigned when defining alias and object names.
3 DNS Management and Operations This section discusses how to install DNS and how to initialize, start, and stop DNS configurations. This section also contains system management duties, such as defining a network node, changing a DNS file name, and securing your DNS database. Most DNS management operations are done using DNSCOM commands. After you initialize and start your DNS configuration, proceed to Section 4, “Building and Modifying the DNS Database,” to create your name database.
DNS Management and Operations DNS Configuration Files and Associated Processes The DNS Database and AUTOLOAD The AUTOLOAD utility available from the DSNM applications simplifies the creation of your DNS name database. AUTOLOAD creates OBEY files (command files) for use with DNSCOM. These OBEY files can contain commands to add subsystem objects to the database, delete subsystem objects from the database, or create groups, and other tasks.
DNS Management and Operations Initializing and Starting DNS Configurations Installing DNS DNS arrives at your site on a site update tape (SUT). The product files on the SUT are grouped into a distribution subvolume (DSV) whose name appears on the last portion of the packing list. This DSV includes six files (listed below) and a softdoc file.
DNS Management and Operations Initializing and Starting DNS Configurations 2. Select the name of the DNS configuration file by entering the SELECT DNSCONF command. Include volume and subvolume name with the configuration file name, as shown in Figure 3-1. The warning statement in this step is nothing to worry about; the DNS configuration is initialized in step 8 below. Then select the definition operating mode by entering the SELECT DEFINITION ON command.
DNS Management and Operations Initializing and Starting DNS Configurations Figure 3-1. Using DNSCOM to Initialize DNS 1 2 3 4 5 6 7 9 10 11 ••• 8 54> DNSCOM DNSCOM - T9635D00 - (15DEC91) SYSTEM \ANKARA COPYRIGHT TANDEM COMPUTERS INCORPORATED 1987, 1991 DNSCOM_ SELECT DNSCONF $ENGIN2.DNS.CONFIG WARNING 1063 - DNS Configuration has not been Initialized Configuration File is $ENGIN2.DNS.CONFIG DNSCOM_ SELECT DEFINITION ON DNSCOM_ VOLUME $ENGIN2.
DNS Management and Operations Initializing and Starting DNS Configurations 7. Now it is time to specify the execution priorities for the DNS name manager process, the exporter process, and the CPUs on which these processes are to run. At this point, you may also indicate the volume on which the name manager’s swap file is created. To perform these tasks, use the SET DNSPROCESS command as shown in the figure. The values you specify in this step take effect in step 8.
DNS Management and Operations Updating the DNS Database Stopping a DNS When it is necessary to shut your system down for altering a DNS configuration, for Configuration system maintenance, or installing a new system generation, the DNSCOM STOP command lets you stop any running DNS name manager. Also, when you need additional system resources that DNS is using, you can stop a DNS configuration that you don’t need to be active.
DNS Management and Operations Changing DNS File Names If you like, you can also assign aliases and add the new objects to existing groups. Likewise, when you add or delete an object programmatically, your management application should update the DNS database. Changing DNS File The DNS database is composed of 16 files that each serve a particular function within Names DNS. At initialization, DNS creates these files and assigns them predefined (default) names.
DNS Management and Operations DNS File and Database Security If the default file names do not meet the requirements of the naming conventions used at your site, you can easily change them. To do this, use the following command for each file name you wish to change. This must be done before you enter the INITIALIZE DNS command: SET logical file, FILE file name In the following example, DNS-NAME-FILE is changed to DNSNAME, and DNSALPHA-FILE is changed to $DATA.
DNS Management and Operations DNS File and Database Security A user or an application with execute authority can execute commands that change the state or configurations of DNS. With execute authority, you can start and stop a DNS configuration and change the attributes of DNS files and processes. A user or an application with definition authority can add, alter and delete the definitions of subsystem-object types, alias types, composite types, and subsystems.
DNS Management and Operations DNS File and Database Security Security Through Operating Modes In addition to the DNS owner and security attribute, DNSCOM has another feature that protects against accidental changes to the database. You can run DNSCOM in one of two modes: user mode or definition mode. In user mode with write authority, you can add, alter, or delete the definitions of domains, objects, managers, aliases, composites, and groups.
DNS Management and Operations Backing up the DNS Configuration Backing up the DNS To back up your DNS configuration files, do one of the following steps right after Configuration initializing a DNS configuration: Use the SYSGEN program to copy the DNS configuration files to your system image tape. Back up the DNS configuration file onto magnetic tape with the BACKUP program described in the BACKUP/RESTORE section of the Guardian 90 Operating System Utilities Reference Manual.
DNS Management and Operations Error Recovery: Reloading the DNS Database If you want the copied name definition reflected throughout the system, you must directly alter the definition node’s version when that node becomes available, just as you would globally change a name definition under normal circumstances. See “Selecting a Naming Strategy” and “Uniqueness of Names: Parts of a DNS Name” in Section 4 for more information on the definition node.
4 Building and Modifying the DNS Database This section discusses creating DNS names that compose the DNS database. Altering and deleting DNS name definitions from the database is also discussed in this section. The majority of this section focuses on creating the initial database definitions. Once the name definitions exist in the database, they can be altered or deleted. In general, the concepts and methods involved in creating DNS name definitions also apply to altering definitions.
Building and Modifying the DNS Database Selecting a Naming Strategy When processing an update command, DNS always accesses the definition node for all names involved in the command. This rule prevents the problems that would otherwise occur if persons at two different nodes simultaneously tried to update their local copies of the DNS database.
Building and Modifying the DNS Database Introduction to Defining DNS Names Figure 4-1. Group Hierarchy Example OREGON_ATMS PORTLAND_ATMS MEDFORD_ATMS SALEM_ATMS EUGENE_ATMS NORTHWEST_ATMS PORT_NORTHEAST_ATMS PNE_ATM1 PNE_ATM2 PNE_ATM3 030 Introduction to When you define an object, type, alias, group, or other name to DNS, you define its Defining DNS Names attributes, assign it a name, and add the definition to the DNS database.
Building and Modifying the DNS Database Introduction to Defining DNS Names Creating some name definitions is dependent on the preexistence of other definitions, as listed in Table 4-1. Definitions of some names are building blocks for other definitions. Because of the multitude of name relationships and dependencies, it is important that you understand them before creating the DNS database. Table 4-1.
Building and Modifying the DNS Database Introduction to Defining DNS Names Figure 4-2 displays all DNS name relationships except for domains. Domains have no name dependencies. They can be included in any name definition except subsystem names. To see a single name’s relationship to other names, see the individual definition discussions under “How to Define DNS Names” later in this section. Figure 4-2.
Building and Modifying the DNS Database Introduction to Defining DNS Names The ASSUME Command: a Useful Aid DNSCOM provides a keystroke saving option—the ASSUME command. When you use the ASSUME command, DNS remembers the object name you specified in a command line until you issue another ASSUME command.
Building and Modifying the DNS Database Introduction to Defining DNS Names The example below displays how to add an alias type in one command line. Its result is the same as the example used in the previous subsection. The ampersand (&) is part of your input when you carry a long command line to the next line on a screen. Using the ampersand is described more in Section 6 under “Entering a Command on More Than One Line.
Building and Modifying the DNS Database Introduction to Defining DNS Names Uniqueness of Names: Parts of a DNS Name Each DNS name consists of two parts; and no two DNS names can have identical first part and second parts. For instance, the names CIRCUIT ON \MEMPHIS and CIRCUIT ON \DALLAS are unique names. DNS automatically adds the second part when you add a DNS object. The definition node is the node where the original name was defined and where the definition resides.
Building and Modifying the DNS Database How to Define DNS Names Specifying Aliases in SSOBJECT and SSMANAGER Definitions Using DNSCOM, you can specify aliases when defining an SSOBJECT or SSMANAGER name. As a convenience of DNSCOM, it performs an ADD ALIAS command for each alias in the specified alias list within each SSOBJECT or SSMANAGER definition you build. This automatic adding of aliases is done when DNS processes the ADD SSOBJECT or ADD SSMANAGER command.
Building and Modifying the DNS Database How to Define DNS Names Figure 4-3. Dependencies and Relationships of SS Names SS SSMANAGER SSTYPE Legend In an order-restricted relationship, a solid arrow line is used, and the dependent name appears below the required name. Relationships shown with dashed arrow lines are not order-restricted. The name from which an arrow originates is specified in the definition of the name at the arrowhead.
Building and Modifying the DNS Database How to Define DNS Names Figure 4-4. Dependencies and Relationships of SSTYPE Names SS SSTYPE DNSDOMAIN ALIASTYPE SSOBJECT COMPOSITETYPE Legend In an order-restricted relationship, a solid arrow line is used, and the dependent name appears below the required name. Relationships shown with dashed arrow lines are not order-restricted. The name from which an arrow originates is specified in the definition of the name at the arrowhead.
Building and Modifying the DNS Database How to Define DNS Names EXTERNAL Attribute for SSTYPE Definitions The EXTERNAL attribute used for an SSTYPE definition can play a useful part in the definitions of names associated with an SSTYPE. If the EXTERNAL attribute is set to ON in an SSTYPE definition, subsystem-object names of this type are automatically added as aliases.
Building and Modifying the DNS Database How to Define DNS Names When you add a manager definition, you specify the following: The manager name A list of subsystems the manager controls Additionally, you can give the manager one or more aliases and specify the default domain for aliases of this manager. Figure 4-5 displays the relationships and dependencies of SSMANAGER name definitions. Figure 4-5.
Building and Modifying the DNS Database How to Define DNS Names Managers usually manage only one subsystem. For example, a Pathmon process manages Pathway, and $SSCP manages SNAX/XF. The example below shows how to add a subsystem manager. User input is displayed in boldface type; system output is displayed in regular type. DNSCOM_SET SSMANAGER SUBSYSTEMS SNAX DNSCOM_ADD SSMANAGER $SSCP SSMANAGER \BLUE.
Building and Modifying the DNS Database How to Define DNS Names Figure 4-6. Dependencies and Relationships of COMPOSITETYPE Names SSTYPE DNSDOMAIN SSOBJECT COMPOSITETYPE COMPOSITE Legend In an order-restricted relationship, a solid arrow line is used, and the dependent name appears below the required name. Relationships shown with dashed arrow lines are not order-restricted. The name from which an arrow originates is specified in the definition of the name at the arrowhead.
Building and Modifying the DNS Database How to Define DNS Names Figure 4-7.
Building and Modifying the DNS Database How to Define DNS Names See Figure 4-8 for the following explanation. Before defining the composite object(s) displayed in Figure 4-8, the system manager must have defined a composite type called ATM and specified that all associated ATMs must consist of a Pathway terminal, a SNAX/XF LU, and an HLS thread.
Building and Modifying the DNS Database How to Define DNS Names The commands for defining the composite object ATM44 are shown below. User input is displayed in boldface type. DNSCOM_ASSUME COMPOSITE DNSCOM_SET TYPE ATM DNSCOM_SET COMPONENTS TERM-006 UNDER \NY.$PM DNSCOM_SET COMPONENTS $LINE4.#LU5 UNDER \NY.$SSCP DNSCOM_SET COMPONENTS #LINE4.LU5 UNDER \NY.
Building and Modifying the DNS Database How to Define DNS Names Figure 4-9. Dependencies and Relationships of ALIASTYPE Names SSTYPE DNSDOMAIN ALIASTYPE ALIAS Legend In an order-restricted relationship, a solid arrow line is used, and the dependent name appears below the required name. Relationships shown with dashed arrow lines are not order-restricted. The name from which an arrow originates is specified in the definition of the name at the arrowhead.
Building and Modifying the DNS Database How to Define DNS Names When you add an alias type definition, you specify the following: The alias type name An owner (usually your company name) A type number, which must be unique among type numbers defined by the owner Optional list of subsystem-object types for objects that can have this type of alias You can also specify the default domain for definitions of aliases of a type.
Building and Modifying the DNS Database How to Define DNS Names Figure 4-10. Dependencies and Relationships of SSOBJECT Names SSMANAGER SSTYPE * IF DNSDOMAIN SSOBJECT ‡ OR ALIAS COMPOSITE Legend * Relationship between SSMANAGER and SSOBJECT exists only if SSTYPE definition associated with SSOBJECT has HASMANAGER attribute set to ON. ‡ ALIAS’s REFERENT may be either SSMANAGER or SSOBJECT.
Building and Modifying the DNS Database How to Define DNS Names Examples of subsystem-object names are the following: A subsystem-object name that Pathmon \NY.$PM uses for a particular terminal might be TERM-006. A subsystem-object name that SNAX/XF process \NY.$SSCP uses for a logical unit might be $LINE4.#LU3. A subsystem-object name that the Guardian 90 operating system uses for a file might be \NY.$ACCT.PAYROLL.EMP. For the objects shown in Figure 4-11, subsystem-object names appear in parentheses.
Building and Modifying the DNS Database How to Define DNS Names The sample session below shows where subsystem objects (LUs) are added, including aliases. INFO commands are used to show the attributes of the subsystem objects. User input is displayed in boldface type. DNSCOM_ASSUME SSOBJECT Default Name Type is SSOBJECT DNSCOM_SET TYPE LU DNSCOM_SET SSMANAGER $SSCP DNSCOM_SHOW SSOBJECT ALIASES None DOMAIN LOCAL EXTERNAL OFF MANAGER $SSCP TYPE LU IN SNAX DNSCOM_ADD $LS.
Building and Modifying the DNS Database How to Define DNS Names The next example shows how to add subsystem objects that are terminals. SHOW and INFO commands display attributes before and after adding the terminal. No aliases are added in this example. User input is displayed in boldface type. DNSCOM_ASSUME TERM DNSCOM_RESET DNSCOM_SET MANAGER $ATMM DNSCOM_SHOW SSOBJECT ALIASES None DOMAIN LOCAL EXTERNAL ON MANAGER $ATMM TYPE TERM IN PATHWAY DNSCOM_ADD LA-TERM SSOBJECT LA-TERM UNDER \BLUE.
Building and Modifying the DNS Database How to Define DNS Names Specific Characteristics for SSOBJECT Names Names selected for subsystem-object names and their attributes must have the following characteristics: The subsystem-object name can be any sequence of characters from the following: ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz 0123456789#$`@[\]^{|}~./-_ The subsystem-object name cannot be more than 162 characters long.
Building and Modifying the DNS Database How to Define DNS Names DNS ensures that every alias corresponds to a particular subsystem-object name or manager and, thus, to a particular object managed by a subsystem. This correspondence permits a management application to accept an alias in a command and to use DNS to translate the alias into the correct subsystem-object name; this process is known as name resolution. Below is an example of name resolution.
Building and Modifying the DNS Database How to Define DNS Names Figure 4-13 displays the dependencies and relationships of alias name definitions. Figure 4-13. Dependencies and Relationships of ALIAS Names SSMANAGER DNSDOMAIN ALIASTYPE SSOBJECT ‡ OR ALIAS GROUP Legend ‡ ALIAS REFERENT may be either SSMANAGER or SSOBJECT. In an order-restricted relationship, a solid arrow line is used, and the dependent name appears below the required name.
Building and Modifying the DNS Database How to Define DNS Names Be no more than 32 characters long Be unique in the DNS database on which they are defined Defining Composite-Object Names While simple objects are managed by one subsystem only, a composite object (COMPOSITE) is managed by multiple subsystems. The entities controlling the composite objects are called components. Before you can define a composite object, you must define a composite type, as described in “Defining Composite Type Names.
Building and Modifying the DNS Database How to Define DNS Names Optionally, you can specify a domain in the composite-object definition. If you do not specify a domain, the composite object inherits a default domain from its composite type definition, as described in “DOMAIN Attribute for SSTYPE Definitions,” earlier in this section. In the composite-object definition, you can also specify the groups to which the composite object is to belong.
Building and Modifying the DNS Database How to Define DNS Names Defining Groups A group is the name for a set of related DNS object names whose members can be aliases, composites, or other groups. Groups are most often used to define sets of objects on which the same operation must be performed, or objects all of which are affected by the same actions. For example, a group could contain the names of lines from which a certain quality of service is required.
Building and Modifying the DNS Database How to Define DNS Names Objects in a particular group need not be of the same type. Figure 4-16 displays the relationships of GROUP name definitions. Group names are not dependent on the preexistence of any names. Figure 4-16. Relationships of GROUP Names DNSDOMAIN ALIAS COMPOSITE GROUP Legend GROUP can specify its members, or members can specify its group.
Building and Modifying the DNS Database How to Define DNS Names The DOMAIN attribute of group definition specifies a DNS domain that determines the systems on which the group’s definition is replicated. If a group has a domain specified, it may not contain other groups as members. The domain of any group containing other groups must be LOCAL. (LOCAL is the DNSCOM keyword used to indicate that a names should not be replicated to any other node.
Building and Modifying the DNS Database How to Define DNS Names DNSCOM_INFO GROUP CAL, EXPLODE CAL DOMAIN LOCAL MEMBERS SCAL : GROUP BURBANK : COMPOSITE (ATM) LA : COMPOSITE (ATM) SF : COMPOSITE (ATM) DNSCOM_ Specific Characteristics for GROUP Names Specific characteristics for group definitions are the same as those listed under “Specific Characteristics for ALIAS Names.” Defining Domains As defined in Section 2, a domain is a collective name for a set of network nodes.
Building and Modifying the DNS Database How to Define DNS Names Figure 4-18 displays the relationships of DOMAIN name definitions in the DNS subsystem. Figure 4-18. Relationships of DOMAIN Names SSOBJECT SSMANAGER ALIASTYPE SSTYPE DNSDOMAIN ALIAS COMPOSITETYPE GROUP COMPOSITE Legend Dashed arrow lines represent optional relationships. S8121-029 DOMAIN is an attribute of most names. For certain names, default domains may be automatically inherited if not explicitly specified.
Building and Modifying the DNS Database Creating a Sample Database Creating a Sample Database Below is a listing of the DNSCOM commands to create a small DNS database. This is a sample listing of DNSCOM commands; use it as an aid when creating your database. Your site requires a unique naming convention to suit your needs. 1. The following commands create domains named NEWYORK, MIDWEST, and NETWORK_CONTROL.
Building and Modifying the DNS Database Creating a Sample Database 5. The following commands create composite types named SNA-TERMINAL and X25-TERMINAL. SET SET SET SET ADD COMPOSITETYPE COMPOSITETYPE COMPOSITETYPE COMPOSITETYPE COMPOSITETYPE OWNER JoyCo TYPENUM 1 COMPONENTS (LU, TERM) DOMAIN NETWORK_CONTROL SNA-TERMINAL ADD COMPOSITETYPE X25-TERMINAL, OWNER JOYCO, TYPENUM 2, & DOMAIN NETWORK_CONTROL, COMPONENTS (SU IN X25AM, TERM) 6.
Building and Modifying the DNS Database Creating a Sample Database SET SSOBJECT TYPE TERM IN PATHWAY SET SSOBJECT MANAGER $RDS SET SSOBJECT EXTERNAL OFF ADD ADD ADD ADD ADD ADD ADD 8. SSOBJECT SSOBJECT SSOBJECT SSOBJECT SSOBJECT SSOBJECT SSOBJECT TERM1 TERM2 TERM3 TERM4 TERM5 TERM6 TERM7 The following commands create aliases named TEST_SYSTEM and NCC_TERM. SET ALIAS REFERENT $TEST SET ALIAS DOMAIN LOCAL ADD ALIAS TEST_SYSTEM ADD ALIAS NCC_TERM, REFERENT $LINE1.#LU7, DOMAIN NETWORK 9.
Building and Modifying the DNS Database Deleting DNS Names Deleting DNS Names Obviously, name definitions can only be deleted after they have been added to the DNS database. There are some considerations to be aware of when deleting DNS names, such as which names can be deleted in user mode and which require definition mode. See the individual DELETE command descriptions in Section 7 for the considerations of a specific DELETE command, which appear after the command syntax description.
5 How DNS Exports the Name Database Exporting name definitions involves the local name manager and name exporter, and the name managers on another system. The local name manager and name exporter communicate through the Guardian 90 file system. The name exporter acts as the requester, and the name manager acts as the server. In addition to this interprocessor communications (IPC) interface, the two processes communicate through a file called the queue file.
How DNS Exports the Name Database The Name Exporter TMF and the Name Manager The name manager is a TMF server; DNSCOM and the user applications are requesters, regarded as clients of the name manager. The name manager receives TMF transactions through $RECEIVE. Consequently, the NMA (or DNSCOM) has control over TMF transactions. The DNS database is TMF-protected; therefore, each update to the database must occur under a TMF transaction.
How DNS Exports the Name Database DNS Database Replication The Queue File The queue file assists the communication between the name manager and name exporter. The queue file is composed of four logical files: the primary queue, secondary queue, hold queue, and export control file. The primary queue serves as a place for the name manager to store export requests until acted upon by the name exporter.
How DNS Exports the Name Database DNS Database Replication Figure 5-1. The Export Process 1. The operator or an application adds or changes a definition. 2. The DNS name manager updates the local database and adds an item to the queue of names to export from \A. DNSCOM ADD or ALTER DNS Name Manager DNS Database Names to Export from \A Management Application 3. The name manager tells the name exporter that there are names to export. DNS Name Exporter 5.
How DNS Exports the Name Database DNS Database Replication The Queue Manager The name manager makes no attempt to determine which systems are to be involved in the update. That task is delegated to the part of the name exporter known as the queue manager. The queue manager’s main processing loop is as follows: 1. Begin a TMF transaction. 2. Read the primary queue with lock. 3. If a request is found, analyze the request to determine the systems to which it needs to be sent.
How DNS Exports the Name Database DNS Database Replication Figure 5-2. Time-Staged Replication 1 Node A Node B Node A Node B Node B fails. 9:00 a.m. 2 User tries to update a name definition replicated on Node B. 3 DNS updates name definition on Node A, but queues update request for Node B. 4 Node B is restored. 10:00 a.m. 5 DNS updates name definition on Node B. S8121-027 Situations might arise where a name’s definition node is unavailable and a change to that name’s definition is required.
How DNS Exports the Name Database DNS Database Replication Although you can request updates to a name from any node where DNS is installed, DNS actually accomplishes and propagates the updates through the definition node for that name. Names preferably should be defined on the nodes where the objects physically exist, although DNS does not enforce this. For more information about the COPY command, see “Updating Definitions on Unavailable Nodes” in Section 3 and the COPY command description in Section 7.
How DNS Exports the Name Database Distribution Strategy of Network Control Nodes Important Considerations About Database Distribution The fact that only one node can export or update the definition of a name has one important implication: if the definition node becomes unavailable, other nodes can no longer receive new definitions or updates from the definition node.
How DNS Exports the Name Database Distribution Strategy of Network Control Nodes Figure 5-3. Distribution With Two Network Control Nodes \A \B \D \E DNS Name Manager DNS Name Manager DNS Name Manager DNS Name Manager DNS Name Exporter DNS Name Exporter DNS Name Exporter DNS Name Exporter The name exporter is responsible for remote copies and updates. The name database on \E is replicated on \F. The name database on \D is partially replicated on \F.
How DNS Exports the Name Database Distribution Strategy of Network Control Nodes In this example, although each NCN has a complete copy of the DNS database for all nodes under its control, an NCN cannot change the information in its database that was defined on the remote nodes. Only a definition node can change its names. Operators on an NCN can still control the objects and their names on remote definition nodes. However, the name manager at the remote node performs the update.
6 Using DNSCOM As a system manager or operator, you use the DNS interactive interface to create a DNS database, maintain and query a DNS database, and manage the operation of DNS. You accomplish these tasks with the DNSCOM commands. This section includes an overview of DNSCOM and tips for using the DNSCOM commands. Section 7 presents all the DNSCOM commands in alphabetical order with syntax descriptions and examples.
Using DNSCOM Keywords Used in Commands The functions available through the DNSCOM commands, except the basic commands, are also available through SPI. SPI is the programmatic interface to DNS and is discussed in the Distributed Name Service (DNS) Management Programming Manual. The remainder of this section includes specific information about the various ways to enter and use the DNSCOM commands.
Using DNSCOM Keywords Used in Commands Table 6-1.
Using DNSCOM Keywords Used in Commands Table 6-1.
Using DNSCOM Working With Different DNS Configurations Table 6-2.
Using DNSCOM Working With Different DNS Configurations If neither a system name nor number is passed, DNSCOM attempts to open the name manager on the system where DNSCOM is running. When a START DNS command is processed by DNSCOM, DNSCOM attempts to open the DNS configuration on a system determined as follows: If the AT \system parameter is included in the START DNS command, DNSCOM attempts to open the configuration file on that system. Otherwise, DNSCOM attempts to open the $SYSTEM.SYSTEM.
Using DNSCOM Working With Different DNS Configurations Initial OPEN With a Default Configuration File If DNSCOM cannot find a definition for the =_DNS_CONFIG parameter, that is, one is not present, the initial DNSCOM open remains as described previously in “Specifying a System Name and Configuration File” earlier in this section.
Using DNSCOM Working With Different DNS Configurations In the following example, DNS attempts to open the process on \REMOTE specified by DNS-MANAGER PROCESSNAME in \REMOTE.$DATA.MYDNS.DNSCONF: ALTER DEFINE =_DNS_CONFIG, FILE \REMOTE.$DATA.DNSCONF DNSCOM DNSCOM - T9635D00 (15DEC91) SYSTEM \ABC COPYRIGHT TANDEM COMPUTERS INCORPORATED 1987, 1991 Current Configuration File is \REMOTE.$DATA.MYDNS.
Using DNSCOM Working With Different DNS Configurations To avoid having to include the name of the name manager each time that DNSCOM is run, as well as to handle the case where the desired configuration is not in the running state, DNSCOM looks for DEFINE =_DNS_CONFIG. If this define mapping statement is present, the default configuration for that execution of DNSCOM becomes the one whose configuration file is mapped by =_DNS_CONFIG.
Using DNSCOM DNSCOM Interfaces and Operating Modes This is done by including the AT { \system | name manager } parameter in the command line. See Section 7 for the command syntax for directing commands to alternate systems or configurations. The name manager that executes a command is called the command name manager. The command name manager can be either the current name manager or another name manager.
Using DNSCOM DNSCOM Interfaces and Operating Modes Using a Command File A command file is useful in situations where you expect the same sequence of commands to be used numerous times. Command files permit you to type the full form of the commands only once, and later initiate execution of a command file with a single command (abbreviated if desired). You not only save time but also reduce the possibilities of typing errors.
Using DNSCOM Options for Entering DNSCOM Commands See the individual command descriptions for OBEY, OBEYSYS, and OBEYVOL in Section 7, and refer to the Guardian 90 Operating System User's Guide for more information on command files. DNSCOM Commands and Operating Modes DNSCOM operates in either of two modes: user or definition. User mode is the default mode of operation; definition mode is available to you only if your security authorization includes definition authority.
Using DNSCOM Options for Entering DNSCOM Commands Terminating a DNSCOM Command or Session If you use the BREAK key while a DNSCOM command is in progress, DNSCOM terminates the command and returns a new prompt. Any update that may be in progress is canceled. To terminate a DNSCOM session, use the EXIT command. CRTL-Y also terminates a DNSCOM session. Entering Multiple Commands on a Single Line To enter more than one DNSCOM command on the same line, separate each command with a semicolon (;).
Using DNSCOM Options for Entering DNSCOM Commands IN specifies the subsystem that defines a subsystem-object type. In the following examples, SNAX and Pathway subsystem names are used. LINE IN SNAX TERM IN PATHWAY IN also specifies the name of a group. In the following examples, SAN-FRANCISCO and SEATTLE are group names. * IN SAN-FRANCISCO ALIAS * IN SEATTLE ON specifies the definition node of a DNS object (alias, composite, or group). In the following examples, \NY and \SANFRAN are system names.
Using DNSCOM Options for Entering DNSCOM Commands 4) To get information about all of a particular type of DNS object defined on a particular node. Examples are: INFO ALIAS * ON \NCN INFO GROUP * ON \NCN 5) To get information about all of the members of a group, for example: INFO * IN SAN_FRANCISCO 6) To get information about all instances of an alias type or composite type. Examples are: INFO CIRCUIT * INFO SNA-TERMINAL * 7) To get information about all SSTYPES defined by a particular subsystem.
Using DNSCOM Options for Entering DNSCOM Commands Working With Lists in Commands Where lists of elements are allowed in DNSCOM commands, they can take one of the following two forms: { element } { ( element [ , element ] ... ) } Thus when you specify a single list element as shown in the first form above, parentheses are not necessary. If you specify multiple elements, they must be enclosed in parentheses and separated by commas, shown in the second form.
Using DNSCOM Options for Entering DNSCOM Commands If you use neither the plus sign nor the minus sign in an ADD, ALTER, or SET command, the list-valued attribute is set to contain the elements listed. For example: DNSCOM_SHOW MEMBERS GROUP MEMBERS B D E F DNSCOM_SET MEMBERS (I, J) DNSCOM_SHOW MEMBERS GROUP MEMBERS I J Instead of keeping track of what to delete and add, you can use the RESET command to first clear the contents of the list and then use the ADD command to create the list.
Using DNSCOM Ambiguous Names (Error 1034) DNSCOM generates a warning message in response to any request to add an element to a list if that element is already on the list. Similarly, it generates a warning message in response to a request to delete an element that is not on the specified list. Directing Output With the OUT Command The OUT command directs all output other than operator prompts to a specified destination. Usually, the destination is a disk file or printer.
Using DNSCOM Ambiguous Names (Error 1034) DNSCOM_ ALTER LINE4,REFERENT \A.$SPARE1 ERROR 1034 - Ambiguous Name - LINE4 DNSCOM_ INFO LINE4 LINE4 ON \A : ALIAS COPIED DOMAIN ALL-NCNS ON \A OWNER XYZCO REFERENT \A.$LINE4 : SSOBJECT (LINE IN SNAX) TYPE COMM-LINE TYPENUM 1 LINE4 ON \C : ALIAS COPIED DOMAIN ALL-NCNS ON \C OWNER XYZCO REFERENT \C.
7 The DNSCOM Commands This section presents detailed information about all the DNSCOM commands, including complete command syntax, command description, special considerations, and examples. In the examples in this section, user input appears in boldface type, and DNSCOM output appears in normal type. Some DNSCOM commands initialize, open, and close DNS configurations and processes. Other commands add, alter, or delete the name definitions in the DNS name database.
The DNSCOM Commands Overview of DNSCOM Commands Table 7-1. Update Commands (Page 1 of 2) Command Function Performed ADD ALIAS Adds new alias, defining domain where alias is replicated, groups to which it belongs, corresponding subsystem object or manager process, and alias type. Adds new alias type, defining default domain for instances of the type, corresponding subsystem-object types, owner, and numeric type code.
The DNSCOM Commands Overview of DNSCOM Commands Table 7-1. Update Commands (Page 2 of 2) Command Function Performed ALTER SSOBJECT ALTER SSTYPE COPY * COPY ALIAS COPY COMPOSITE COPY GROUP COPY MEMBERS DELETE ALIAS DELETE ALIASTYPE DELETE COMPOSITE DELETE COMPOSITETYPE DELETE DNSDOMAIN DELETE GROUP DELETE SS DELETE SSMANAGER DELETE SSOBJECT DELETE SSTYPE Changes existing definitions of subsystem-object names. Changes existing definitions of subsystem-object types.
The DNSCOM Commands Overview of DNSCOM Commands Table 7-2. Inquiry Commands Command Function Performed INFO * INFO ALIAS INFO ALIASTYPE INFO COMPOSITE INFO COMPOSITETYPE INFO DNS INFO DNSDOMAIN INFO DNSFILE INFO DNSPROCESS INFO GROUP INFO MEMBERS INFO SS INFO SSMANAGER INFO SSOBJECT INFO SSTYPE LIST * LIST ALIAS LIST ALIASTYPE LIST COMPOSITE LIST COMPOSITETYPE LIST DNS LIST DNSDOMAIN LIST DNSFILE Displays information about one or more names. Displays information about one or more aliases.
The DNSCOM Commands Overview of DNSCOM Commands Table 7-3. Operational Commands Command Function Performed CLOSE DISABLE EXPORT ENABLE EXPORT INITIALIZE DNS OPEN START DNS STATUS EXPORT STATUS DNS STOP DNS Closes current name manager. Disables exports to nodes. Enables exports to system(s). Installs DNS on node and initializes DNS configuration files. Opens (begins communication with) name manager process. Executes a DNS configuration on specified node.
The DNSCOM Commands Overview of DNSCOM Commands Table 7-4. Basic Commands (Page 2 of 3) Command Function Performed RESET COMPOSITE RESET COMPOSITETYPE RESET DNS RESET DNSDOMAIN RESET DNSFILE RESET DNSPROCESS RESET GROUP RESET SS RESET SSMANAGER RESET SSOBJECT RESET SSTYPE SELECT SET ALIAS Restores default values of composite attributes. Restores default values to the composite type attributes. Restores DNS attributes to their default values. Restores default values of domain attributes.
The DNSCOM Commands Overview of DNSCOM Commands Table 7-4. Basic Commands (Page 3 of 3) Command Function Performed SHOW ALIASTYPE Displays current creation values for alias type attributes, as established by SET ALIASTYPE command. Displays current creation values for composite object attributes, as established by SET COMPOSITE command. Displays current creation values for composite-object type attributes, as established by SET COMPOSITETYPE command.
The DNSCOM Commands Important Notes about Individual Commands Important Notes About General notes that apply to the ADD, ALTER, and INFO commands are discussed Individual Commands below. Notes About ADD Commands ADD commands define new names to DNS. The new name is added on the local system only unless the name has a domain. If the name has a domain, it is added to those systems in the domain. This applies to alias, composite, and group names, since only these names may be replicated to other systems.
The DNSCOM Commands Important Notes about Individual Commands Notes About INFO Commands (OBEYFORM Considerations) Most of the INFO commands have an optional OBEYFORM parameter. This parameter controls the displayed output of the INFO commands so the syntax of the SET or ALTER command is displayed correctly. Using OBEYFORM allows you to obtain a copy of the commands needed to duplicate the definition of a currently defined name or set of names.
The DNSCOM Commands Important Notes about Individual Commands Wild-Card Symbol” in Section 6 for using the INFO command with the wild-card symbol. DNSCOM_INFO TCP1, OBEYFORM ==ASSUME ALIAS ==RESET ==SET DOMAIN LOCAL ==ALTER %G1 ON \WEST, MEMBERS + %TCP1 ON \WEST ==SET REFERENT %TCP1 UNDER \WEST.$PM ==ADD %TCP1 ASSUME SSOBJECT RESET ==SET ALIASES + %TCP1 (DOMAIN LOCAL) SET DOMAIN LOCAL SET EXTERNAL ON SET MANAGER \WEST.
The DNSCOM Commands Important Notes about Individual Commands reserved words in future DNS releases). The use of the percent sign to avoid syntax errors was discussed earlier in this section under “Keywords Used in Commands.” Appendix C lists the reserved DNS words.
The DNSCOM Commands ADD ALIAS ADD ALIAS The ADD ALIAS command defines a new alias for a subsystem object or manager. The object or manager must have been previously defined by the ADD SSOBJECT or ADD SSMANAGER command. For more information about using the ADD command, see “Notes About ADD Commands” at the beginning of this section. ADD [ ALIAS ] alias [ LIKE an alias [ ON \system-1 ] [ at-part ] ] [ , parameter ] ...
The DNSCOM Commands ADD ALIAS parameter is one of the following: DOMAIN { domain | LOCAL } domain is the name of a domain. The definition of alias is replicated on the systems in the specified domain. If not specified, the domain is inherited from the specified alias type if the alias is typed, or from the referent if the alias is not typed. LOCAL indicates that the definition of the alias being added is not replicated.
The DNSCOM Commands ADD ALIAS another alias is an alias. When specified, the referent creation value is set to the REFERENT of this alias. manager name is the name of a subsystem manager previously defined through use of the ADD SSMANAGER command. RESET DOMAIN indicates that the domain for alias is to revert to its default value. If the alias is typed, the domain is the domain for the specified alias type; otherwise, the domain of alias is the domain of its referent.
The DNSCOM Commands ADD ALIAS Considerations When adding an alias, a referent must be specified, either by the ADD ALIAS command or the SET ALIAS command. The referent must have been previously defined through use of the ADD SSOBJECT or ADD SSMANAGER command. If a typed alias is being added, and the referent already has an alias of the specified type, an error message is generated, and the alias is not added.
The DNSCOM Commands ADD ALIASTYPE ADD ALIASTYPE The ADD ALIASTYPE command defines a new alias type. This command may be used only in definition mode. For more information about using the ADD command, see “Notes About ADD Commands” at the beginning of this section. ADD [ ALIASTYPE ] alias type [LIKE an alias type [ at-part ] ] [ , parameter ] ... where at-part is: AT { \system | name manager } ALIASTYPE may be omitted if the default object is ALIASTYPE.
The DNSCOM Commands ADD ALIASTYPE RESET DOMAIN indicates that, by default, aliases of the type being added will not have their definitions replicated. RESET SSTYPES [ * ] indicates that the alias type being added is not restricted to objects of particular types. SSTYPES [ + | - ] ssobject-type list + indicates that the subsystem-object types listed should be added to those already specified in preceding SET ALIASTYPE SSTYPES commands.
The DNSCOM Commands ADD ALIASTYPE * is the default and indicates (like RESET SSTYPES above) that the alias type being added is not restricted to objects of particular types. OWNER owner owner is an owner name that specifies the company that defines the alias type. This is a required parameter. TYPENUM integer integer must be a unique, nonzero value between -9999 and 9999 within owner with regard to alias types. This is a required parameter.
The DNSCOM Commands ADD COMPOSITE ADD COMPOSITE The ADD COMPOSITE command adds a composite object to the DNS database. For more information about using the ADD command, see “Notes About ADD Commands” at the beginning of this section. ADD [ COMPOSITE ] composite [LIKE a composite [ ON \system-1 ] [ at-part ] ] [ , parameter ] ... where at-part is: AT { \system-2 | name manager } COMPOSITE may be omitted if the default object is COMPOSITE. composite is the name of the composite being added.
The DNSCOM Commands ADD COMPOSITE parameter is one of the following: [ COMPONENT ] component type [ IN subsystem ] { ssobject name [ UNDER manager ] } { alias } component type is the name of a previously created subsystem-object type. subsystem is the name of a subsystem defining ssobject type. This must be specified if the type of composite being added requires the same subsystem-object type from two different subsystems. (See “Considerations.
The DNSCOM Commands ADD COMPOSITE indicates that composite should not be added to the listed groups, even if those groups have been specified in previous SET COMPOSITE commands. If neither + nor - appears, composite is added to the groups listed. group list is the name(s) of at least one group defined on the local system. Multiple group names are separated by commas (,) and must be enclosed in parentheses.
The DNSCOM Commands ADD COMPOSITE Each composite object is associated with from two to eight subsystem objects. A particular subsystem object may be a component of more than one composite object. When specifying a component for a composite object, the IN subsystem parameter need only be included if the type of composite being added requires the same subsystem-object type from two different subsystems.
The DNSCOM Commands ADD COMPOSITETYPE ADD The ADD COMPOSITETYPE command is used to describe composite types. This COMPOSITETYPE command may be used only in definition mode. For more information about using the ADD command, see “Notes About ADD Commands” at the beginning of this section. ADD [ COMPOSITETYPE ] composite type [ LIKE a composite type [ at-part ] ] [ , parameter ] ... where at-part is: AT { \system | name manager } COMPOSITETYPE may be omitted if the default object is COMPOSITETYPE.
The DNSCOM Commands ADD COMPOSITETYPE indicates that the subsystem-objects listed in composite list should be deleted from those previously specified in SET COMPOSITETYPE COMPONENTS commands. If neither + nor - appears, the types in component list replace those previously specified. This is a required parameter. component list is defined as { ssobject type [ in-part ] } { ( ssobject type [ in-part ] [ , ssobject type [ in-part ] ] ...
The DNSCOM Commands ADD COMPOSITETYPE OWNER owner owner is an owner name that specifies the company that defines the composite type. RESET DOMAIN indicates that the default domain for instances of the composite type is to be set to empty. TYPENUM integer integer must be a unique, nonzero value between -9999 and 9999 within owner with regard to composite types.
The DNSCOM Commands ADD DNSDOMAIN ADD DNSDOMAIN The ADD DNSDOMAIN command defines a new domain to DNS. For more information about using the ADD command, see “Notes About ADD Commands” at the beginning of this section. ADD [ DNSDOMAIN ] domain [ LIKE a domain [ at-part ] ] [ , SYSTEMS [ + | - ] system list ] where at-part is: AT { \system | name manager } DNSDOMAIN may be omitted if the default object is DNSDOMAIN. domain is the name of the domain to be added.
The DNSCOM Commands ADD DNSDOMAIN system list is defined as: { \system | ( \system [ , \system ] ... ) } \system is a Guardian 90 system name. A particular name may only appear once in a system list. Examples ADD DNSDOMAIN NETWORK, SYSTEMS ( \NORWES1, & \NORWES2, \NORWES3 ) ADD DNSDOMAIN NETWORK LIKE NETWORK AT \MEMPHIS.$RDSN Considerations A domain need not contain any systems; systems are specified either by using the SET DNSDOMAIN command or the ADD DNSDOMAIN command.
The DNSCOM Commands ADD GROUP ADD GROUP The ADD GROUP command is used to define a new group to DNS. For more information about using the ADD command, see “Notes About ADD Commands” at the beginning of this section. ADD [ GROUP ] group name [ , parameter ] ... GROUP may be omitted if the default object is GROUP. group name is the name of the group being defined.
The DNSCOM Commands ADD GROUP MEMBERS [ + | - ] { name [ ON \system ] } { ( name [ ON \system ] [ , name [ ON \system ] ... ) } + indicates that the listed names are to be added to those specified in previous SET GROUP commands. If a group has groups as members, its domain must be LOCAL. indicates that the listed names are to be deleted from those specified in previous SET GROUP commands. If neither + nor - appears, the members of group name are to be exactly those listed.
The DNSCOM Commands ADD GROUP Considerations Groups need not have any members when they are originally defined using the ADD GROUP command. You can add a group to be included in a parent group either by specifying the GROUPS attribute in the ADD GROUP command, as defined above, or by altering the parent group to include the other.
The DNSCOM Commands ADD SS ADD SS The ADD SS command is used to define a subsystem to DNS. This command may be used only in definition mode. For more information about using the ADD command, see “Notes About ADD Commands” at the beginning of this section. ADD [ SS ] subsystem [ LIKE a subsystem [ at-part ] ] [ , parameter ] ... where at-part is: AT { \system | name manager } SS may be omitted if the default object is SS. subsystem is the name of the subsystem being added.
The DNSCOM Commands ADD SS Examples ADD SS TMF, OWNER TANDEM, SSNUM 10 ADD SS RDS LIKE RDS AT $RDNS 7–32 31258 Tandem Computers Incorporated
The DNSCOM Commands ADD SSMANAGER ADD SSMANAGER The ADD SSMANAGER command defines a subsystem manager to DNS. For more information about using the ADD command, see “Notes About ADD Commands” at the beginning of this section. ADD [ SSMANAGER ] manager [ LIKE a manager [ at-part ] ] [ , parameter ] ... where at-part is: AT { \system | name manager } SSMANAGER may be omitted if the default object is SSMANAGER. manager is the name of the manager being added.
The DNSCOM Commands ADD SSMANAGER indicates that the listed aliases should be deleted from those specified in previous SET SSMANAGER ALIASES commands. If neither + nor - appears, the listed alias specifications replace those currently existing for the manager. alias-spec is defined as: alias [ ( { DOMAIN domain } [ , DOMAIN domain ] ) ] { TYPE alias type } [ , TYPE alias type ] alias is an alias for the manager. domain is the name of a DNS domain.
The DNSCOM Commands ADD SSMANAGER SUBSYSTEMS [ + | - ] { subsystem } { ( subsystem [ , subsystem ]...) } + indicates that the listed subsystems are to be added to those specified in a previous SET SSMANAGER command. indicates that the listed subsystems are to be deleted from those specified in a previous SET SSMANAGER command. If neither + nor - appears, the manager is assumed to support objects defined by only those subsystems listed. subsystem is the name of a subsystem.
The DNSCOM Commands ADD SSOBJECT ADD SSOBJECT The ADD SSOBJECT command defines a subsystem object (ssobject) and, optionally, one or more aliases. For more information about using the ADD command, see “Notes About ADD Commands” at the beginning of this section. ADD [ SSOBJECT ] ssobject [ LIKE an ssobject [ UNDER manager ] [ at-part ] ] [ , parameter ] ... where at-part is: AT { \system | name manager } SSOBJECT may be omitted if the default object is SSOBJECT.
The DNSCOM Commands ADD SSOBJECT + indicates that the listed alias specifications should be added to those specified in previous SET SSOBJECT ALIASES command. indicates that the listed aliases should be deleted from those specified in previous SET SSOBJECT ALIASES commands. If neither + nor - appears, the listed alias specifications replace any that were previously specified.
The DNSCOM Commands ADD SSOBJECT EXTERNAL { ON | OFF } ON indicates that ssobject is added as an untyped alias that refers to the object being defined. OFF indicates that ssobject is not added as an alias. MANAGER { manager | alias } manager is the name of the manager for ssobject. alias is an alias for the manager of ssobject. RESET ALIASES [ * ] no aliases are created in processing the ADD SSOBJECT command except if EXTERNAL ON is specified, in which the single alias ssobject is created.
The DNSCOM Commands ADD SSOBJECT Example ADD SSOBJECT $LINE4.#TERM22, TYPE LU, ALIASES TERM22 See “Creating a Sample Database” in Section 4 for more examples of adding subsystem object s. Considerations When defining a subsystem object, the TYPE attribute must have a creation value established either by using SET SSOBJECT commands or as parameters to the ADD SSOBJECT command. If the specified subsystem-object type is defined with HASMANAGER ON, then MANAGER must have a creation value similarly established.
The DNSCOM Commands ADD SSTYPE ADD SSTYPE The ADD SSTYPE command defines a subsystem-object type. This command may be used only in definition mode. For more information about using the ADD command, see “Notes About ADD Commands” at the beginning of this section. ADD [ SSTYPE ] ssobject type [ LIKE an ssobject type [ IN subsystem ] [ at-part ] ] [ , parameter ] ... where at-part is: AT { \system | name manager } SSTYPE may be omitted if the default object is SSTYPE.
The DNSCOM Commands ADD SSTYPE parameter is one of the following: DOMAIN { domain | LOCAL } domain is the name of a domain. When specified, becomes the default domain for untyped aliases that refer to instances of the type being defined. LOCAL Indicates that the default domain for instances of the subsystem-object type is empty; that is, the definitions of untyped aliases that refer to instances of the type are not replicated.
The DNSCOM Commands ADD SSTYPE DEVICENAME Indicates that objects of this type must have valid Guardian 90 logical device names. When adding a subsystem object of this type using the ADD SSOBJECT command, DNSCOM expands the name using the specifications from the most recent NAMESYS command. DISKFILENAME Indicates that subsystem-object names of this type must be valid Guardian 90 disk file names.
The DNSCOM Commands ADD SSTYPE SUBDEVICENAME SUBDEVICENAME-1 SUBDEVICENAME-2 Indicates that objects of this type must have valid Guardian 90 subdevice names. Where SUBDEVICENAME is specified, one or two levels of subdevice name may be specified. Where SUBDEVICENAME-1 is specified, only a single level of subdevice name is allowed (such as $X.#Y). Where SUBDEVICENAME-2 is specified, two levels of subdevice name are required (such as $X.#Y.Z).
The DNSCOM Commands ADD SSTYPE SUBSYSTEM subsystem subsystem is the name of the subsystem that defines the object type being added. TYPENUM integer integer is a nonzero integer between -9999 and 9999 that identifies the type within the subsystem. Example ADD SSTYPE TCP, SUBSYSTEM PATHWAY, FORMAT PATHWAYNAME & TYPENUM 5, HASMANAGER ON See “Creating a Sample Database” in Section 4 for more examples of adding subsystem-object types.
The DNSCOM Commands ALLOW ALLOW The ALLOW command specifies the maximum number of warnings or errors that may occur during execution of an OBEY file or an IN file. If either value is exceeded, DNSCOM halts execution of the OBEY file or IN file. The syntax of the ALLOW command is as follows: ALLOW [ ALL ] [ ERRORS ] [ NO ] [ WARNINGS ] [ count ] count is an integer specifying the number of errors or warnings permitted during the execution of an IN file or command file.
The DNSCOM Commands ALTER ALIAS ALTER ALIAS Aliases are altered using the following syntax: ALTER [ ALIAS ] alias [ ON \system-1 ] [ at-part ], parameter [ , parameter ] ... where at-part is: AT { \system-2 | name manager } ALIAS can be omitted if alias is unique in the command name manager’s database or if ON system is specified. alias is an alias name. \system-1 is a Guardian 90 system name that specifies the definition node for alias.
The DNSCOM Commands ALTER ALIAS REFERENT { ssobject name [ UNDER manager ] } { another alias } { manager name } ssobject name is the name that the subsystem uses to refer to the object. manager is the name of the object’s manager, or an alias for the object’s manager. This may be omitted if ssobject name is unique on the local node or if ssobject name has no manager. another alias is an alias. When specified, the REFERENT of alias is changed to the referent of another alias.
The DNSCOM Commands ALTER ALIASTYPE ALTER ALIASTYPE Alias types are altered using the ALIASTYPE command. This command may be used only in definition mode. ALTER [ ALIASTYPE ] alias type [ at-part ] , parameter [ , parameter ] ... where at-part is: AT { \system | name manager } ALIASTYPE may be omitted if alias type is unique in the command name manager’s database. alias type is the name of the alias type to be altered. { \system | name manager } is a system or name manager where alias type is defined.
The DNSCOM Commands ALTER ALIASTYPE SSTYPES [ + | - ] ssobject-type list + indicates that the subsystem-object types in ssobject-type list are to be added to those allowable for instances of the alias type. causes each subsystem-object type in ssobject-type list to be deleted from those for which aliases of type alias type are allowed.
The DNSCOM Commands ALTER COMPOSITE ALTER COMPOSITE Composite objects are altered using the following syntax: ALTER [ COMPOSITE ] composite [ ON \system-1 ] [ at-part ] , parameter [ , parameter ] ... where at-part is: AT { \system-2 | name manager } COMPOSITE may be omitted if composite is unique in the command name manager’s database or if ON system is specified. composite is the name of the composite object to be altered.
The DNSCOM Commands ALTER COMPOSITE subsystem is the name of a subsystem defining ssobject type. This must be specified if the type of composite being altered requires the same subsystem-object type from two different subsystems. ssobject name is the name that the subsystem uses to refer to the object. manager is the name of the object’s manager, or an alias for the object’s manager. This may be omitted if ssobject name is unique on the local node or if the object does not have a manager.
The DNSCOM Commands ALTER COMPOSITETYPE ALTER COMPOSITETYPE Composite types are altered using the ALTER COMPOSITETYPE command. This command may be used only in definition mode. ALTER [ COMPOSITETYPE ] composite type [ at-part ] , parameter [ , parameter ] ... where at-part is: AT { \system | name manager } COMPOSITETYPE may be omitted if composite type is unique in the command name manager’s database. composite type is the name of a composite type defined.
The DNSCOM Commands ALTER DNS ALTER DNS A DNS configuration is changed using the following syntax: ALTER DNS [ AT { \system | config file } ] , parameter [ , parameter ] ... \system is the name of the system. The name of the configuration file to be altered is derived by applying this system to the name of the current configuration file. config file is the name of a DNS configuration file previously created using the INITIALIZE DNS command.
The DNSCOM Commands ALTER DNS MAXEXPORTS exports is an integer in the range 1 through 31; the default value is 31. This parameter specifies the maximum number of active export tasks permitted by the name exporter. SECURITY "security flags" security flags is a four-character string with each character selected from the list O, U, G, C, A, N and -. Enclose the character string in double quotation marks (“). Examples ALTER DNS, DNSOWNER SUPER.OPS, SECURITY "AGOG" ALTER DNS AT \NEWYORK.$DNS.RDSDNS.
The DNSCOM Commands ALTER DNSDOMAIN ALTER DNSDOMAIN Domains are altered using the following syntax: ALTER [ DNSDOMAIN ] domain , [ at-part ] parameter [ , parameter ] ... where at-part is: AT { \system | name manager } DNSDOMAIN may be omitted if domain is unique in the command name manager’s database. domain is the name of a domain on the local system. { \system | name manager } is a system or name manager where domain is defined. If omitted, the current name manager is assumed.
The DNSCOM Commands ALTER DNSDOMAIN Example ALTER NETWORK, SYSTEMS + \NEW Considerations When a system is added to a domain, any aliases, composites or groups that have their DNSDOMAIN value equal to the name of the altered domain have their definitions replicated on the added system. When a system is deleted from a domain, any aliases, composites or groups that have their DNSDOMAIN value equal to the name of the altered domain have their definitions removed from the deleted system.
The DNSCOM Commands ALTER DNSFILE ALTER DNSFILE DNS database files are altered using the following syntax: ALTER [ DNSFILE ] DNS file [ AT { \system | config file } ] , FILENAME file name DNS file is one of the following: DNS-ALPHA-FILE DNS-BILL-FILE DNS-COPY-FILE DNS-DOMAIN-FILE DNS-FAST-FILE DNS-FAST-GROUP-FILE DNS-GROUP-FILE DNS-MANAGER-FILE DNS-MAP-FILE DNS-MEMBER-FILE DNS-NAME-FILE DNS-QUEUE-FILE DNS-RFAST-FILE DNS-RMAP-FILE DNS-RNAME-FILE DNS-TYPES-FILE \system is the name of a system.
The DNSCOM Commands ALTER DNSFILE Examples ALTER DNS-NAME-FILE, FILENAME $NEWVOL.NAMES.DRCTRY ALTER DNS-NAME-FILE, FILENAME $DATA2.RDSDNS.DNSNAMES ALTER DNS-TYPES-FILE AT \MEMPHIS.$DNS.RDSDNS.DNSCONFIG, & FILENAME \MEMPHIS.$SPOOL.DNSRDS.DNSTYPES Considerations To issue this command, the DNS configuration must be in the stopped state. The ALTER DNSFILE command does not change the name of the physical database file; it simply updates the DNS configuration file. To rename a DNS database file, you must: 1.
The DNSCOM Commands ALTER DNSPROCESS ALTER DNSPROCESS DNS processes are altered using the following syntax: ALTER [ DNSPROCESS ] { DNS-EXPORTER } { DNS-MANAGER } [ AT { \system | config file } ] , parameter [ , parameter ] ... \system is the name of a system. The name of the configuration file to be altered is derived by applying this system to the name of the current configuration file. config file is the name of a DNS configuration file previously created using the INITIALIZE DNS command.
The DNSCOM Commands ALTER DNSPROCESS PROGRAM program program is the name of an object file to be executed in creating the process. SWAPVOL $volume volume is the name of the disk volume where the process’s swap files are to be created. Examples ALTER DNS-MANAGER, CPUS (3,2), SWAPVOL $FALL ALTER DNS-MANAGER, PRIORITY 180 ALTER DNS-EXPORTER, PRIORITY 150 ALTER DNSPROCESS DNS-EXPORTER AT TEST.DNSCONFIG, CPUS (3,2) Considerations To issue this command, DNS must be in the stopped state.
The DNSCOM Commands ALTER GROUP ALTER GROUP Groups are altered using the following syntax: ALTER [ GROUP ] group [ ON \system-1 ] [ at-part ] , parameter [ , parameter ] ... where at-part is: AT { \system-2 | name manager } GROUP may be omitted if group is unique in the command name manager’s database, or if ON \system-1 is specified. group is the name of the group being defined. \system-1 a Guardian 90 system name that specifies the definition node for group.
The DNSCOM Commands ALTER GROUP MEMBERS [ + | - ] { name [ ON \system-1 ] } { ( name [ ON \system-1 ] [ , name [ ON \system-1 ] ... ) } + Indicates that each of the names that follow are to be added as members of group. Indicates that each of the names that follow are to be deleted as members of group. If neither + nor - appears, the names listed replace the current group membership list. name is a DNS object name. \system-1 is a Guardian 90 system name that indicates the definition node for name.
The DNSCOM Commands ALTER SSMANAGER ALTER SSMANAGER Subsystem managers are altered using the following syntax: ALTER [ SSMANAGER ] manager [ at-part ] , parameter [ , parameter ] ... where at-part is: AT { \system | name manager } SSMANAGER may be omitted if manager is unique in the command name manager’s database. manager is the name of the manager to be altered. { \system | name manager } is a system or name manager where manager is defined. If omitted, the current name manager is assumed.
The DNSCOM Commands ALTER SSMANAGER Indicates that the manager is no longer to control objects defined by each subsystem listed. If neither + nor - appears, the subsystems replace those currently specified. subsystem is the name of a subsystem.
The DNSCOM Commands ALTER SSOBJECT ALTER SSOBJECT Subsystem object definitions are altered using the following syntax: ALTER [ SSOBJECT ] ssobject [ UNDER manager ] [ at-part ] , parameter [ , parameter ] ... where at-part is: AT { \system | name manager } SSOBJECT may be omitted if ssobject is unique in the command name manager’s database, if UNDER is included. ssobject is the ssobject for the object to be altered. manager is the manager that controls the object.
The DNSCOM Commands ALTER SSOBJECT LOCAL specifies that the default domain for untyped aliases that refer to the object being altered is empty. Does not affect any existing aliases. EXTERNAL { ON | OFF } If OFF is specified, indicates that ssobject is no longer to be treated as an alias. If ON is specified, indicates that ssobject is to be treated as an alias for the object. ssobject must conform to the rules for aliases and must be unique in the command name manager’s database. Examples ALTER $LINE4.
The DNSCOM Commands ALTER SSTYPE ALTER SSTYPE Subsystem-object types are altered using the ALTER SSTYPE command. This command may be used only in definition mode. ALTER [ SSTYPE ] ssobject type [ IN subsystem ] [ at-part ] , parameter [ , parameter ] ... where at-part is: AT { \system | name manager } SSTYPE may be omitted if ssobject type is unique in the command name manager’s database, or if IN subsystem is specified. ssobject type is the name of a subsystem-object type defined on the local system.
The DNSCOM Commands ALTER SSTYPE DUPLICATES [ NOT ] ALLOWED If NOT is specified, subsequent ADD SSOBJECT commands that specify this type will require that the ssobject name be unique over all managers defined in the command name manager’s database. If NOT is omitted, subsequent ADD SSOBJECT commands that specify this type will require that the ssobject name be unique only within the specified manager. FORMAT ANY removes any previous name FORMAT restrictions for instances of the type.
The DNSCOM Commands ASSUME ASSUME The ASSUME command is used to specify a default command object for subsequent SET, SHOW, RESET, and ADD commands. ASSUME [ name type|alias type|composite type|ssobject type ] name type is one of the following: ALIAS ALIASTYPE ( definition mode only ) COMPOSITE COMPOSITETYPE ( " " ") DNS ( " " ") DNSFILE ( " " ") DNSPROCESS ( " " ") DNSDOMAIN GROUP SS ( " " ") SSMANAGER SSOBJECT SSTYPE ( " " ") alias type is the name of an alias type.
The DNSCOM Commands CLOSE CLOSE The CLOSE command causes DNSCOM to close its current name manager. CLOSE Example DNSCOM_CLOSE Name Manager \VIEW.
The DNSCOM Commands CMDSYS CMDSYS CMDSYS sets the default system name for file references; otherwise, the default system is the system currently in use. This command does not affect references to OBEY (command) files. CMDSYS [ \system ] \system is a Guardian 90 system name. Examples CMDSYS CMDSYS \TOKYO Considerations If the CMDSYS command is not issued, file references are expanded according to the default settings in effect when DNSCOM was started.
The DNSCOM Commands CMDVOL CMDVOL The CMDVOL command sets the default volume and subvolume names for future file references. The command does not affect references to OBEY (command) files. CMDVOL [ $volume ] [ [ $volume.] subvolume ] volume is a Guardian 90 volume name. subvolume is a Guardian 90 subvolume name. Examples CMDVOL CMDVOL MYDNS CMDVOL $DATA CMDVOL $DATA.MYDNS Considerations If the CMDVOL command is not issued, the default settings in effect when DNSCOM was started are used.
The DNSCOM Commands COPY * COPY * The COPY * command is used to create a locally owned copy of all aliases, composites, and groups that has been replicated from other systems. ON \system-1 [ at-part ] COPY * where at-part is: AT { \system-2 | name manager } \system-1 is a Guardian 90 system name. This is specified if you only want to copy names imported from a particular node. { \system-2 | name manager } is a system or name manager where the command is to be executed.
The DNSCOM Commands COPY ALIAS COPY ALIAS The COPY ALIAS command is used to create locally owned copies of aliases that have been replicated from other systems. COPY { [ ALIAS ] alias } [ at-part ] { ALIAS * [ ON \system-1 ] [ IN group ] } { alias type * [ ON \system-1 ] [ IN group ] } where at-part is: AT { \system-2 | name manager } ALIAS may be omitted if the default object is ALIAS. alias is the name of an alias to be copied.
The DNSCOM Commands COPY ALIAS Examples COPY ALIAS * ON \CHICAGO COPY 32KDF0032A COPY ALIAS * IN KNOXVILLE AT \NEWYORK COPY CIRCUIT * Consideration See the considerations listed under the COPY * command.
The DNSCOM Commands COPY COMPOSITE COPY COMPOSITE The COPY COMPOSITE command is used to create locally owned copies of composites that have been replicated from other systems. COPY { [ COMPOSITE ] composite } { COMPOSITE * [ ON \system-1 ] [ IN group ] } { composite type * [ ON \system-1 ] [ IN group ] } [ at-part ] where at-part is: AT { \system-2 | name manager } COMPOSITE may be omitted if the default object is COMPOSITE. composite is the name of a composite object to be copied.
The DNSCOM Commands COPY COMPOSITE Examples COPY COMPOSITE * ON \CHICAGO COPY RDS_T2 COPY COMPOSITE * IN KNOXVILLE AT \NEWYORK COPY X25-TERMINAL * Consideration See the considerations listed under the COPY * command.
The DNSCOM Commands COPY GROUP COPY GROUP The COPY GROUP command is used to create a locally owned copy of groups that have been replicated from other systems. COPY { [ GROUP ] group } [ at-part ] { GROUP * [ ON \system-1 ] [ IN group ] } where at-part is: AT { \system-2 | name manager } GROUP may be omitted if the default object is GROUP. group is the name of a group to be copied. GROUP * means all groups in the command name manager’s database (or within some other specified group) are to be copied.
The DNSCOM Commands COPY MEMBERS COPY MEMBERS The COPY MEMBERS command is used to create locally owned copies of members of groups that have been replicated from other systems. COPY [ MEMBERS ] * [ ON \system-1 ] IN group [ at-part ] where at-part is: AT { \system-2 | name manager } MEMBERS may be omitted if the default object is MEMBERS. \system-1 is a Guardian 90 system name. This is specified if you only want to copy names imported from a particular node.
The DNSCOM Commands DELETE ALIAS DELETE ALIAS The DELETE ALIAS command purges alias names and their definitions from the DNS database. Only aliases previously added on the local system may be deleted. DELETE { [ ALIAS ] alias } [ at-part ] [ ! ] { ALIAS * [ IN group ] } { alias type * [ IN group ] } where at-part is: AT { \system | name manager } ALIAS may be omitted if alias is unique in the command name manager’s database, or if ON system is specified. alias is the name of an alias to be deleted.
The DNSCOM Commands DELETE ALIAS Examples DELETE TEST_SYSTEM ! DELETE ALIAS * IN MEMPHIS DELETE CIRCUIT * AT \TESTSYS Considerations Deleting an alias does not delete its referent. When an alias is deleted, it is automatically removed from all groups of which it was a member.
The DNSCOM Commands DELETE ALIASTYPE DELETE ALIASTYPE The DELETE ALIASTYPE command purges alias type names and their definitions from the DNS database. This command may be used only in definition mode. DELETE { [ ALIASTYPE ] alias type } [ at-part ] [ ! ] { ALIASTYPE * } where at-part is: AT { \system | name manager } ALIASTYPE may be omitted if alias type is unique in the command name manager’s database. alias type is the name of an alias type to be deleted.
The DNSCOM Commands DELETE COMPOSITE DELETE COMPOSITE The DELETE COMPOSITE command purges composite names and their definitions from the DNS database. DELETE { [ COMPOSITE ] composite } [ at-part ] [ ! ] { COMPOSITE * [ IN group ] } { composite type * [ IN group ] } where at-part is: AT { \system | name manager } COMPOSITE may be omitted if composite is unique in the command name manager’s database. composite is the name of a composite object to be deleted.
The DNSCOM Commands DELETE COMPOSITE Examples DELETE RDS_T6 ! DELETE COMPOSITE * IN MEMPHIS DELETE X25-TERMINAL * AT \TESTSYS Considerations Deleting a composite does not delete the underlying subsystem objects. When a composite is deleted, it is automatically removed from all groups of which it was a member.
The DNSCOM Commands DELETE COMPOSITETYPE DELETE COMPOSITETYPE The DELETE COMPOSITETYPE command purges composite type names and their definitions from the DNS database. This command may be used only in definition mode. DELETE { [ COMPOSITETYPE ] composite type } [ at-part ] [ ! ] { COMPOSITETYPE * } where at-part is: AT { \system | name manager } COMPOSITETYPE may be omitted if composite type is unique in the command name manager’s database. composite type is the name of a composite type to be deleted.
The DNSCOM Commands DELETE COMPOSITETYPE Examples DELETE X25-TERMINAL AT \TESTSYS DELETE COMPOSITETYPE * ! Consideration If a composite type name is being deleted and any instances of the composite type exist on the local system, DNSCOM issues a warning message and the composite type is not deleted. Composite types may only be deleted in definition mode.
The DNSCOM Commands DELETE DNSDOMAIN DELETE DNSDOMAIN The DELETE DNSDOMAIN command purges DNS domains and their definitions from the DNS database. DELETE { [ DNSDOMAIN ] domain } [ at-part ] [ ! ] { DNSDOMAIN * } where at-part is: AT { \system | name manager } DNSDOMAIN may be omitted if domain is unique in the command name manager’s database. domain is the name of a domain to be deleted. DNSDOMAIN * means all domains in the command name manager’s database are to be included for deletion.
The DNSCOM Commands DELETE GROUP DELETE GROUP The DELETE GROUP command purges group names and their definitions from the DNS database. DELETE { [ GROUP ] group } [ at-part ] [ ! ] { GROUP * [ IN group-2 ] } where at-part is: AT { \system | name manager } GROUP may be omitted if group is unique in the command name manager’s database. group is the name of a group to be deleted.
The DNSCOM Commands DELETE GROUP Considerations Deleting a group does not delete the members of the group. A deleted group is automatically removed from all groups of which it was a member.
The DNSCOM Commands DELETE SS DELETE SS The DELETE SS command purges subsystem names and their definitions from the DNS database. This command may be used only in definition mode. DELETE { [ SS ] subsystem | SS * } [ at-part ] [ ! ] where at-part is: AT { \system | name manager } SS may be omitted if subsystem is unique in the command name manager’s database. subsystem is the name of a subsystem to be deleted.
The DNSCOM Commands DELETE SSMANAGER DELETE SSMANAGER The DELETE SSMANAGER command purges subsystem-manager names and their definitions from the DNS database. Any aliases for the manager are also deleted. A subsystem-manager name cannot be deleted if there are subsystem objects that have that name specified as their manager.
The DNSCOM Commands DELETE SSOBJECT DELETE SSOBJECT The DELETE SSOBJECT command purges subsystem-object names and their definitions from the DNS database.
The DNSCOM Commands DELETE SSOBJECT of ssobject type defined by any subsystem are included; in this case, the name of the subsystem-object type is included (in parentheses) for deletion, following the name of the subsystem object. { \system | name manager } is a system or name manager where the command is to be executed. If omitted, the current name manager is assumed. ! If present, DNSCOM does not prompt for confirmation before deleting each name. If omitted, DNSCOM prompts for confirmation.
The DNSCOM Commands DELETE SSTYPE DELETE SSTYPE The DELETE SSTYPE command purges subsystem-object type names and their definitions from the DNS database. This command may be used only in definition mode. DELETE { [ SSTYPE ] ssobject type [ in-part ] } { SSTYPE * [ IN subsystem ] } [ at-part ] [ ! ] where in-part is: IN { subsystem | * } and at-part is: AT { \system | name manager } SSTYPE may be omitted if ssobject type is unique in the command name manager’s database or if IN subsystem is specified.
The DNSCOM Commands DELETE SSTYPE ! If present, DNSCOM does not prompt for confirmation before deleting each name. If omitted, DNSCOM prompts for confirmation. At each prompt, you have the following options: retain the subsystem-object type name, delete the subsystemobject type name, delete all remaining subsystem-object type names specified by the delete expression, or abort the command.
The DNSCOM Commands DISABLE EXPORT DISABLE EXPORT The DISABLE EXPORT command disables exports to one or more nodes. DISABLE EXPORT { system list | * } [ at-part ] where at-part is: AT { \system | name manager } system list is defined as: { \system | ( \system [ , \system ] ... ) } \system is a Guardian 90 system name. A particular name may only appear once in a system list. * indicates that export to all systems should be disabled.
The DNSCOM Commands ENABLE EXPORT ENABLE EXPORT The ENABLE EXPORT command enables export to one or more systems. This command also causes the exporter to attempt reprocessing of all entries currently in the hold queue for the specified system. ENABLE EXPORT { system list | * } [ at-part ] where at-part is: AT { \system | name manager } system list is defined as: { \system | ( \system [ , \system ] ... ) } \system is a Guardian 90 system name. A particular name may only appear once in a system list.
The DNSCOM Commands ENV ENV The ENV command displays the current configuration file, the current manager name, and the current DNSCOM defaults. A question mark (?) entered at a DNSCOM_ prompt is equivalent to ENV. ENV The ENV display has the following format: Configuration file is $FALL.MYDNS.
The DNSCOM Commands EXIT EXIT The EXIT command stops DNSCOM. { E | EXIT } Examples EXIT E Consideration When entered from a terminal or in a command file passed to DNSCOM in a TACL RUN command, or in an OBEY file, the EXIT command stops DNSCOM.
The DNSCOM Commands FC FC The FC command provides the ability to edit or repeat a command line. This is the standard Tandem FC command as implemented by the FIXSTRING procedure. FC Example Refer to the Guardian 90 Operating System User’s Guide for details about the FC command, including many examples.
The DNSCOM Commands HELP HELP The HELP command displays the syntax of DNSCOM commands. If you include the command name and object name in the syntax, DNSCOM responds with the complete syntax for the specified command and the list of attributes for the specified object name, including the current settings of the attributes. HELP [ command name [ object name ] ] [ symbol name ] [ error-warning number ] command name is the name of a DNSCOM command whose syntax is to be displayed.
The DNSCOM Commands HELP DNSCOM_HELP SET ALIASTYPE SET [ ALIASTYPE ] [ LIKE alias type ] [ , parameter ] ... [ parameter ] where parameter is one of the following: { domain | LOCAL } owner { [ + | - ] sstype list } { * } TYPENUM nonzero integer { -9999:9999 } DOMAIN OWNER SSTYPE The keyword ALIASTYPE may be omitted if the default name type is ALIASTYPE. This command is only available in DEFINITION MODE. Consideration If parameters are omitted, the names of all DNSCOM commands are displayed.
The DNSCOM Commands INFO * INFO * The INFO * command returns information about all names in a configuration’s database. The displayed information is similar to that presented by the individual INFO commands for these DNS objects: INFO ALIAS, INFO COMPOSITE, and INFO GROUP. INFO [ / OUT file name / ] * [ ON \system-1 ] [ at-part ] [ [ , option ] ... ] [ , OBEYFORM ] where at-part is: AT { \system-2 | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed.
The DNSCOM Commands INFO * EXPLODE requests an expanded display of the subsumed groups. GROUPS requests a display of all groups of which each object is a part. MEMBERS requests a display of the names of the members of group names. SSTYPES requests a display of all ssobject types of each alias type. OBEYFORM controls the format of the display information. DNSCOM displays each attribute as a syntactically correct SET or ALTER command.
The DNSCOM Commands INFO ALIAS INFO ALIAS The INFO ALIAS command displays information about an alias or set of aliases. The information includes the domain and referent of each alias. If the alias is typed, the type is listed along with the type’s owner and number. If the alias is a member of any groups, the group names are listed if the GROUPS parameter is specified.
The DNSCOM Commands INFO ALIAS alias type * means that all aliases of the specified type in the command name manager’s database (or in the specified group or group-on-system) are to be included for display. GROUPS means that the names of groups of which the alias is a member are to be displayed. DETAIL is the same as GROUPS. OBEYFORM controls the format of the display information. DNSCOM displays each attribute as a syntactically correct SET or ALTER command.
The DNSCOM Commands INFO ALIASTYPE INFO ALIASTYPE The INFO ALIASTYPE command displays information about an alias type or set of alias types. The information includes the owner, the type number, the domain, and (optionally) subsystem-object types. INFO [ / OUT file name / ] { [ ALIASTYPE ] alias type } { ALIASTYPE * } [ at-part ] [ [ , { SSTYPES | DETAIL } ] ...
The DNSCOM Commands INFO ALIASTYPE OBEYFORM controls the format of the display information. DNSCOM displays each attribute as a syntactically correct SET or ALTER command. This allows you to obtain a copy of the commands needed to duplicate a currently defined name or set of names. See the subsection “Notes About INFO Commands (OBEYFORM Considerations)” at the beginning of this section for additional information about OBEYFORM, including examples.
The DNSCOM Commands INFO COMPOSITE INFO COMPOSITE The INFO COMPOSITE command displays information about a composite object or set of composite objects. The information includes the composite type, the domain, and the components. Also shown are the owner and type number of the associated composite type. If GROUPS is specified, the groups of which each composite is a member are also displayed.
The DNSCOM Commands INFO COMPOSITE composite type * means that all composites of the specified type on the local system (or in the specified group or group-on-system) are to be included for display. { \system-2 | name manager } indicates a system or name manager to where the command is to be directed. If omitted, the current name manager is assumed. \system-2 is a Guardian 90 system name. It designates a node other than the current system for processing the command.
The DNSCOM Commands INFO COMPOSITETYPE INFO COMPOSITETYPE The INFO COMPOSITETYPE command displays information about a composite type or set of composite types. The information includes the domain, components, owner, and type number of the type. INFO [ / OUT file name/ ] { [ COMPOSITETYPE ] composite type } { COMPOSITETYPE * } [ at-part ] [ , OBEYFORM ] where at-part is: AT { \system | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed.
The DNSCOM Commands INFO COMPOSITETYPE See the subsection “Notes About INFO Commands (OBEYFORM Considerations)” at the beginning of this section for additional information about OBEYFORM, including examples.
The DNSCOM Commands INFO DNS INFO DNS The INFO DNS command displays the current values of the DNS attributes and the currently installed version number of DNS. INFO [ / OUT file name / ] DNS [ at-part ] [ USING config file ] [ , OBEYFORM ] where at-part is: AT { \system | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed. If omitted, the list is written to the current DNSCOM OUT file.
The DNSCOM Commands INFO DNS INFO DNS USING $DATA.TEST.
The DNSCOM Commands INFO DNSDOMAIN INFO DNSDOMAIN The INFO DNSDOMAIN command displays information about a DNS domain or set of DNS domains. The information consists of the system names that make up the domain. INFO [ / OUT file name/ ] { [ DNSDOMAIN ] domain } [ at-part ] { DNSDOMAIN * } [ , OBEYFORM ] where at-part is: AT { \system | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed. If omitted, the list is written to the current DNSCOM OUT file.
The DNSCOM Commands INFO DNSDOMAIN See the subsection “Notes About INFO Commands (OBEYFORM Considerations)” at the beginning of this section for additional information about OBEYFORM, including examples.
The DNSCOM Commands INFO DNSFILE INFO DNSFILE The INFO DNSFILE command displays the Guardian 90 file name for a DNS logical file or set of DNS logical files. INFO [ / OUT file name/ ] { [ DNSFILE ] DNS file | DNSFILE * } [ at-part ] [ , OBEYFORM ] [ USING config file ] where at-part is: AT { \system | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed. If omitted, the list is written to the current DNSCOM OUT file.
The DNSCOM Commands INFO DNSFILE See the subsection “Notes About INFO Commands (OBEYFORM Considerations)” at the beginning of this section for additional information about OBEYFORM, including examples. Examples INFO DNS-NAME-FILE INFO DNS-RNAME-FILE AT \TOKYO INFO DNS-TYPES-FILE USING $DATA.TEST.DNSCONF INFO /OUT FILES/DNSFILE *, OBEYFORM DNSCOM_INFO DNS-NAME-FILE AT \WEST DNS-NAME-FILE AT \WEST: DNSFILE FILENAME $DATA.NAMES.
The DNSCOM Commands INFO DNSPROCESS INFO DNSPROCESS The INFO DNSPROCESS command displays information about a DNS process or set of DNS processes. The information consists of the CPUs where the process is to run, the name of the event log, the execution priority, the program file name, and the swap volume name.
The DNSCOM Commands INFO DNSPROCESS OBEYFORM controls the format of the display information. DNSCOM displays each attribute as a syntactically correct SET or ALTER command. This allows you to obtain a copy of the commands needed to duplicate a currently defined name or set of names. See the subsection “Notes About INFO Commands (OBEYFORM Considerations)” at the beginning of this section for additional information about OBEYFORM, including examples. Examples INFO DNS-EXPORTER AT \TOKYO.
The DNSCOM Commands INFO GROUP INFO GROUP The INFO GROUP command displays information about a group or set of groups. The information includes the domain (if any) of the group. If the keyword MEMBERS is specified, information about the members of the group is also displayed. You can selectively request display of the names of subsumed groups by using the optional keyword GROUPS.
The DNSCOM Commands INFO GROUP group is the name of a group. When specified, only groups that are members of this higher-level group are included for display. { \system-2 | name manager } indicates a system or name manager to where the command is to be directed. If omitted, the current name manager is assumed. \system-2 is a Guardian 90 system name. It designates a node other than the current system for processing the command. name manager designates a configuration other than the current one.
The DNSCOM Commands INFO GROUP Examples INFO TENNESSEE INFO GROUP * IN TENNESSEE AT \MEMPHIS, EXPLODE INFO /OUT GROUPS/GROUP *, OBEYFORM DNSCOM_INFO SOUTH-BAY SOUTH-BAY ON \SFO : GROUP DOMAIN NETWORK DNSCOM_INFO SOUTH-BAY, MEMBERS SOUTH-BAY : GROUP DOMAIN NETWORK MEMBERS SOUTH-BAY-LINES : GROUP SOUTH-BAY-TERMS : GROUP 31258 Tandem Computers Incorporated 7–123
The DNSCOM Commands INFO MEMBERS INFO MEMBERS The INFO MEMBERS command displays information about the members of a specified group or set of groups. The information displayed is the same as what would be displayed for the INFO command corresponding to the type of member. For example, for an alias, the information displayed by this command is the same as that for an INFO ALIAS command. INFO [ / OUT file name / ] [ MEMBERS ] * IN group [ at-part ] [ [ , option ] ...
The DNSCOM Commands INFO MEMBERS GROUPS requests a display of all groups of which each member is a part. MEMBERS requests a display of the names of the members of the subsumed groups, in addition to group names. OBEYFORM controls the format of the display information. DNSCOM displays each attribute as a syntactically correct SET or ALTER command. This allows you to obtain a copy of the commands needed to duplicate a currently defined name or set of names.
The DNSCOM Commands INFO SS INFO SS The INFO SS command displays information about a subsystem or set of subsystems. The information consists of the owner and number of the subsystem. INFO [ / OUT file name / ] { [ SS ] subsystem | SS * } [ at-part ] [ , OBEYFORM ] where at-part is: AT { \system | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed. If omitted, the list is written to the current DNSCOM OUT file.
The DNSCOM Commands INFO SS Examples INFO SS PATHWAY AT \TOKYO INFO X25AM INFO /OUT SSES/SS *, OBEYFORM DNSCOM_INFO PATHWAY PATHWAY : SUBSYSTEM OWNER TANDEM SSNUM 8 31258 Tandem Computers Incorporated 7–127
The DNSCOM Commands INFO SSMANAGER INFO SSMANAGER The INFO SSMANAGER command displays information about a subsystem manager or set of subsystem managers. The information consists of the names of subsystems managed by the specified managers, the domain (if any), and (optionally) any aliases for the managers.
The DNSCOM Commands INFO SSMANAGER Examples INFO $RDS INFO $PM AT \NEWYORK INFO /OUT SSMGRS/SSMANAGER *, OBEYFORM DNSCOM_INFO $PM, ALIASES $PM : SSMANAGER ALIASES PATHMON DOMAIN LOCAL SUBSYSTEMS PATHWAY 31258 Tandem Computers Incorporated 7–129
The DNSCOM Commands INFO SSOBJECT INFO SSOBJECT The INFO SSOBJECT command displays information about a subsystem object or set of subsystem objects. The information includes the name of the subsystem manager, subsystem-object type, domain (if any), external indicator, owner, subsystem number, and type number of the subsystem-object type. If you include the ALIASES keyword, any aliases for the object are displayed.
The DNSCOM Commands INFO SSOBJECT SSOBJECT * means all subsystem objects in the command name manager’s database. If qualified by the name of a subsystem manager or an alias for a subsystem manager, only subsystem objects controlled by the specified manager are included in the display. If no subsystem manager is specified, or if UNDER * is specified, subsystem objects controlled by all managers on the local system are included.
The DNSCOM Commands INFO SSOBJECT OBEYFORM controls the format of the display information. DNSCOM displays each attribute as a syntactically correct SET or ALTER command. This allows you to obtain a copy of the commands needed to duplicate a currently defined name or set of names. See the subsection “Notes About INFO Commands (OBEYFORM Considerations)” at the beginning of this section for additional information about OBEYFORM, including examples. Examples INFO SSOBJECT TERM1 INFO $LINE1.
The DNSCOM Commands INFO SSTYPE INFO SSTYPE The INFO SSTYPE command displays information about a subsystem-object type or a set of subsystem-object types. The information consists of the domain (if any), duplicates indicator, external indicator, HASMANAGER indicator, format, and type number. In addition, the OWNER and SSNUM attributes inherited from the subsystem are displayed.
The DNSCOM Commands INFO SSTYPE { \system | name manager } indicates a system or name manager to where the command is to be directed. If omitted, the current name manager is assumed. \system is a Guardian 90 system name. It designates a node other than the current system for processing the command. name manager designates a configuration other than the current one. OBEYFORM controls the format of the display information. DNSCOM displays each attribute as a syntactically correct SET or ALTER command.
The DNSCOM Commands INITIALIZE DNS INITIALIZE DNS The INITIALIZE DNS command initializes a DNS configuration. Section 3 explains the initialization procedure. INITIALIZE [ DNS ] [ AT \system ] [!] [ , DNSCONFONLY ] [ DNSCONF file name ] DNS may be omitted if the default object is DNS. \system is the name of the system where DNS is to be initialized. If omitted, the system specified by the last CMDVOL command is assumed. file name must be the name of a disk file (the file need not exist).
The DNSCOM Commands INITIALIZE DNS If ! is omitted, and the specified or default DNS configuration file exists, the following message is issued: FILE CREATE ERROR - file name - record already exists If ! is included and the specified or default DNS configuration file exists, DNSCOM attempts to purge the file. If unsuccessful, an error message is generated. This is the case if the user executing the command is not the current DNS owner or local SUPER.SUPER user or does not have purge authority for the file.
The DNSCOM Commands LIST * LIST * The LIST * command provides a list of all names in a configuration’s database. If an alias or composite is typed, the type is give in parentheses immediately following the DNS object name. LIST [ / OUT file name / ] * [ ON \system-1 ] [ at-part ] where at-part is: AT { \system-2 | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed. If omitted, the list is written to the current DNSCOM OUT file.
The DNSCOM Commands LIST ALIAS LIST ALIAS The LIST ALIAS command provides a list of a specific set of alias names. If a listed alias is typed, the alias type is given in parentheses immediately following the alias name.
The DNSCOM Commands LIST ALIAS alias type * means that all aliases of the specified type in the command name manager’s database (or in the specified group or group-on-system) are to be included for listing. The list output does not include the alias type name. { \system-2 | name manager } indicates a system or name manager where the command is to be executed. If omitted, the current name manager is assumed. \system-2 is a Guardian 90 system name.
The DNSCOM Commands LIST ALIASTYPE LIST ALIASTYPE The LIST ALIASTYPE command provides a list of a specific set of alias type names. LIST [ / OUT file name / ] { [ ALIASTYPE ] alias type } { ALIASTYPE * } [ at-part ] where at-part is: AT { \system | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed. If omitted, the list is written to the current DNSCOM OUT file. ALIASTYPE restricts listed information to only the alias type having the name alias type.
The DNSCOM Commands LIST COMPOSITE LIST COMPOSITE The LIST COMPOSITE command provides a list of a specific set of composite names. If a composite is typed, the composite type is listed in parentheses following the composite name.
The DNSCOM Commands LIST COMPOSITE composite type * means that all composites of the specified type in the command name manager’s database (or in the specified group or group-on-system) are to be included for listing. { \system-2 | name manager } indicates a system or name manager where the command is to be executed. If omitted, the current name manager is assumed. \system-2 is a Guardian 90 system name. It designates a node other than the current system for processing the command.
The DNSCOM Commands LIST COMPOSITETYPE LIST The LIST COMPOSITETYPE command provides a list of a specific set of composite COMPOSITETYPE type names. LIST [ / OUT file name/ ] { [ COMPOSITETYPE ] composite type } { COMPOSITETYPE * } [ at-part ] where at-part is: AT { \system | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed. If omitted, the list is written to the current DNSCOM OUT file.
The DNSCOM Commands LIST COMPOSITETYPE Examples LIST X25-TERMINAL LIST COMPOSITETYPE * DNSCOM_LIST ATM ATM : COMPOSITETYPE 7–144 31258 Tandem Computers Incorporated
The DNSCOM Commands LIST DNS LIST DNS The LIST DNS command is used to determine if a particular DNS configuration exists. If the configuration does not exist, an error message is generated. LIST [ / OUT file name / ] DNS [ at-part ] [ USING config file ] where at-part is: AT { \system | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed. If omitted, the list is written to the current DNSCOM OUT file. DNS may be omitted if the default object is DNS.
The DNSCOM Commands LIST DNSDOMAIN LIST DNSDOMAIN The LIST DNSDOMAIN command provides a list of a specified set of DNS domain names. LIST [ / OUT file name/ ] { [ DNSDOMAIN ] domain } [ at-part ] { DNSDOMAIN * } where at-part is: AT { \system | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed. If omitted, the list is written to the current DNSCOM OUT file. DNSDOMAIN restricts listed information to only the domain having the name domain.
The DNSCOM Commands LIST DNSFILE LIST DNSFILE The LIST DNSFILE command provides a list of Guardian 90 file names for a specific set of DNS logical file names. LIST [ / OUT file name / ] { [ DNSFILE ] dns file } { DNSFILE * } [ at-part ] [ USING config file ] where at-part is: AT { \system | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed. If omitted, the list is written to the current DNSCOM OUT file.
The DNSCOM Commands LIST DNSFILE Examples LIST DNS-NAME-FILE LIST DNS-RNAME-FILE AT \TOKYO LIST DNS-TYPES-FILE USING $DATA.TEST.
The DNSCOM Commands LIST DNSPROCESS LIST DNSPROCESS The LIST DNSPROCESS provides a list of DNS processes existing on the local system or some other specified system. LIST [ / OUT file name / ] { [ DNSPROCESS ] dns process } { DNSPROCESS * } [ at-part ] [ USING config file ] where at-part is: AT { \system | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed. If omitted, the list is written to the current DNSCOM OUT file.
The DNSCOM Commands LIST GROUP LIST GROUP The LIST GROUP command provides a list of a specified set of group names. LIST [ / OUT file name / ] { [ GROUP ] group } [ at-part ] { GROUP * [ ON \system-1 ] [ IN group ] } where at-part is: AT { \system-2 | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed. If omitted, the list is written to the current DNSCOM OUT file. GROUP restricts listed information to only the group having the name group.
The DNSCOM Commands LIST GROUP \system-2 is a Guardian 90 system name. It designates a node other than the current system for processing the command. name manager designates a configuration other than the current one.
The DNSCOM Commands LIST MEMBERS LIST MEMBERS The LIST MEMBERS command provides a list of the members of a specified group. If you include the keyword EXPLODE, the list also shows the same information for all subsumed groups. LIST [ / OUT file name / ] [ MEMBERS ] * IN group [ at-part ] [ , EXPLODE ] where at-part is: AT { \system | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed. If omitted, the list is written to the current DNSCOM OUT file.
The DNSCOM Commands LIST SS LIST SS The LIST SS command provides a list of subsystems on the local system. LIST [ / OUT file name / ] { [ SS ] subsystem } [ at-part ] { SS * } where at-part is: AT { \system | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed. If omitted, the list is written to the current DNSCOM OUT file. SS restricts listed information to only the subsystem having the name subsystem.
The DNSCOM Commands LIST SSMANAGER LIST SSMANAGER The LIST SSMANAGER command provides a list of subsystem managers on the local system. LIST [ /OUT file name/ ] { [ SSMANAGER ] manager } [ at-part ] { SSMANAGER * } where at-part is: AT { \system | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed. If omitted, the list is written to the current DNSCOM OUT file. SSMANAGER restricts listed information to only the subsystem manager having the name manager.
The DNSCOM Commands LIST SSOBJECT LIST SSOBJECT The LIST SSOBJECT command provides a list of names of subsystem objects on the local system. If an object is typed, the name of the subsystem-object type is given in parentheses following the object name. A particular subsystem, subsystem manager, and/or subsystem type may be specified.
The DNSCOM Commands LIST SSOBJECT manager, only subsystem objects controlled by the specified manager are included in the listing. If no subsystem manager is specified, or if UNDER * is specified, subsystem objects controlled by all managers on the local system are included, regardless of type. ssobject type means that subsystem objects of the specified type are to be included for listing. This selection of objects may be restricted by the optional IN subsystem and UNDER manager parameters.
The DNSCOM Commands LIST SSTYPE LIST SSTYPE The LIST SSTYPE command provides a list of names of subsystem-object types defined on the local system. A particular subsystem may be specified. LIST [ / OUT file name / ] { [ SSTYPE ] ssobject type [ in-part ] } [ at-part ] { SSTYPE * [ IN subsystem ] } where in-part is: IN { subsystem | * } and at-part is: AT { \system | name manager } file name is a Guardian 90 file name to which the list output may optionally be directed.
The DNSCOM Commands LIST SSTYPE Examples LIST LINE IN SNAX LIST LINE IN * AT $RDNS LIST * IN PATHWAY LIST SSTYPE * DNSCOM_LIST TCP TCP IN PATHWAY : SSTYPE 7–158 31258 Tandem Computers Incorporated
The DNSCOM Commands NAMESYS NAMESYS The NAMESYS command sets the default system name for name references. NAMESYS [ \system ] \system is a Guardian 90 system name. Examples NAMESYS NAMESYS \NEWYORK NAMESYS \DALLAS Considerations If the NAMESYS command is not issued, name references for subsystem managers and subsystem objects are expanded using the system name of the current name manager. If the system name is not included in the command, the default is the system where DNSCOM is running.
The DNSCOM Commands NAMEVOL NAMEVOL The NAMEVOL command sets the default volume and subvolume names for future SSMANAGER and SSOBJECT references. NAMEVOL [ $volume ] [ [ $volume.] subvolume ] volume is a Guardian 90 volume name. subvolume is a Guardian 90 subvolume name. Examples NAMEVOL $DATA2.RRRDNS NAMEVOL MYDNS NAMEVOL $SIAM Considerations If the NAMEVOL command is not issued, the default settings in effect when DNSCOM was started are used.
The DNSCOM Commands OBEY OBEY The OBEY command causes commands to be read from a specified file. { OBEY | O } file name file name is a Guardian 90 file name, specifying a file that contains one or more valid DNSCOM commands. Examples OBEY ZDNS.LOAD O \TESTSYS.$DATA.NEWDNS.DEFS Considerations If the file name system, volume, or subvolume is not supplied, DNSCOM uses the defaults supplied by the OBEYSYS and OBEYVOL commands or by the SYSTEM and VOLUME commands.
The DNSCOM Commands OBEYSYS OBEYSYS The OBEYSYS command sets the default system name for OBEY file name expansion. OBEYSYS [ \system ] \system is a Guardian 90 system name. Examples OBEYSYS OBEYSYS \TESTSYS Considerations If the OBEYSYS command is not issued, the default settings in effect when DNSCOM was started are used. If the system is omitted, the default is set for local name expansion.
The DNSCOM Commands OBEYVOL OBEYVOL The OBEYVOL command sets the default volume and subvolume names for OBEY file name expansion. OBEYVOL [ $volume ] [ [ $volume. ] subvolume ] volume is a Guardian 90 volume name. subvolume is a Guardian 90 subvolume name. Examples OBEYVOL OBEYVOL DNSDEFS OBEYVOL $DATA.NEWDNS Considerations If the OBEYVOL command is not issued, the default settings in effect when DNSCOM was started are used.
The DNSCOM Commands OPEN OPEN The OPEN command requests DNSCOM to establish communication with a DNS name manager. If communications cannot be established, an error message is generated and the current name manager is unchanged. Section 6 also provides information about opening name managers in “Switching DNS Configurations.” The OPEN command may also be used to change DNS configurations and to alter the NAMESYS setting to the name manager’s system name.
The DNSCOM Commands OUT OUT The OUT command directs all output other than operator prompts to a specified destination. { OUT file name } { / OUT file name / } file name is a Guardian 90 file identifier that specifies the new output destination. It can specify a disk file, a device (such as a printer), or a process (such as the spooler). If omitted, the output is directed to the original DNSCOM OUT file.
The DNSCOM Commands RESELECT RESELECT The RESELECT command restores default settings to options previously set using the SELECT command. RESELECT [ DEFINITION | DNSCONF ] DEFINITION if specified, DEFINITION mode is reset. DNSCONF If DNSCONF is specified or if no options are specified, DNSCOM reverts to the default configuration file.
The DNSCOM Commands RESET ALIAS RESET ALIAS The RESET ALIAS command restores the alias creation values to their defaults. RESET [ ALIAS ] [ parameter [ , parameter ] ... ] ALIAS may be omitted if the default object is ALIAS. parameter is one of the following: DOMAIN indicates that aliases subsequently defined through the ADD ALIAS command will have their domain inherited from the alias type if one is specified; otherwise, the domain is inherited from the referent of the alias.
The DNSCOM Commands RESET ALIASTYPE RESET ALIASTYPE The RESET ALIASTYPE command restores default values to the ALIASTYPE attributes. This command may be used only in definition mode. RESET [ ALIASTYPE ] [ parameter [ , parameter ] ... ] ALIASTYPE may be omitted if the default object is ALIASTYPE. parameter is one of the following: DOMAIN removes any previous DOMAIN specification. OWNER removes any previous owner specification.
The DNSCOM Commands RESET COMPOSITE RESET COMPOSITE The RESET COMPOSITE command restores default values of COMPOSITE attributes. If no parameters are supplied, all attributes are reset. RESET [ COMPOSITE ] [ parameter [ , parameter ] ... ] COMPOSITE may be omitted if the default object is COMPOSITE. parameter is one of the following: [ COMPONENT ] ssobject type [ IN { subsystem | * } ] COMPONENT may be omitted.
The DNSCOM Commands RESET COMPOSITETYPE RESET COMPOSITETYPE The RESET COMPOSITETYPE command restores default values to the COMPOSITETYPE attributes. The command is available only in definition mode. If no parameters are supplied, all attributes are reset. RESET [ COMPOSITETYPE ] [ parameter [ , parameter ] ... ] COMPOSITETYPE may be omitted if the default object is COMPOSITETYPE. parameter is one of the following: COMPONENTS [ * ] removes any previous COMPONENTS specifications.
The DNSCOM Commands RESET DNS RESET DNS The RESET DNS command restores DNS attributes to their default values. This command overrides previous SET DNS commands and is available only in definition mode. If no parameters are supplied, all attributes are reset. RESET [ DNS ] [ parameter [ , parameter ] ... ] DNS may be omitted if the default object is DNS.
The DNSCOM Commands RESET DNSDOMAIN RESET DNSDOMAIN The RESET DNSDOMAIN command restores the default values of domain attributes. RESET [ DNSDOMAIN ] [ SYSTEMS [ * ] ] DNSDOMAIN may be omitted if the default object is DNSDOMAIN. SYSTEMS [ * ] Removes any previous SYSTEMS specification.
The DNSCOM Commands RESET DNSFILE RESET DNSFILE The RESET DNSFILE command restores DNS database file attributes to their default values. This command is available only in definition mode. The default DNSFILE file names are listed in Table 6-2 in Section 6.
The DNSCOM Commands RESET DNSPROCESS RESET DNSPROCESS The RESET DNSPROCESS command restores DNS process attributes to their default values. This command is available only in definition mode. If no parameters are supplied, all attributes are reset. RESET [ DNSPROCESS ] { DNS-EXPORTER } { DNS-MANAGER } { * } [ parameter [ , parameter ] ... ] DNSPROCESS may be omitted if the default object is DNSPROCESS. * indicates that all DNS processes on the local system are to be reset.
The DNSCOM Commands RESET GROUP RESET GROUP The RESET GROUP command restores the default values of GROUP attributes. If no parameters are supplied, all attributes are reset. RESET [ GROUP ] [ parameter [ , parameter ] ... ] GROUP may be omitted if the default object is GROUP. parameter is one of the following: DOMAIN indicates that group names subsequently defined through the ADD GROUP command will not have their definitions replicated on other systems.
The DNSCOM Commands RESET SS RESET SS The RESET SS command restores subsystem attributes to their default values. This command may be used only in definition mode. If no parameters are supplied, all attributes are reset. RESET [ SS ] [ parameter [ , parameter ] ] SS may be omitted if the default object is SS. parameter is one of the following: OWNER removes any previous owner specification. Subsequent ADD SS commands must contain an OWNER parameter as this is a required attribute.
The DNSCOM Commands RESET SSMANAGER RESET SSMANAGER The RESET SSMANAGER command restores the default values of subsystemmanager attributes. If no parameters are supplied, all attributes are reset. RESET [ SSMANAGER ] [ parameter [ , parameter ] ... ] SSMANAGER may be omitted if the default object is SSMANAGER. parameter is one of the following: ALIASES [ * ] removes any previously specified aliases. DOMAIN removes any previous domain specification.
The DNSCOM Commands RESET SSOBJECT RESET SSOBJECT The RESET SSOBJECT command restores the values of subsystem-object attributes. If no parameters are supplied, all attributes are reset. RESET [ SSOBJECT ] [ parameter [ , parameter ] ... ] SSOBJECT may be omitted if the current default is SSOBJECT. parameter is one of the following: DOMAIN indicates that untyped aliases for objects subsequently defined through the ADD SSOBJECT command will have their domain inherited from their subsystem-object type.
The DNSCOM Commands RESET SSTYPE RESET SSTYPE The RESET SSTYPE command restores subsystem-object type attributes to their default values. This command may be used only in definition mode. If no parameters are supplied, all attributes are reset. RESET [ SSTYPE ] [ parameter [ , parameter ] ... ] SSTYPE may be omitted if the default object is SSTYPE. parameter is one of the following: DOMAIN removes any previous domain specification. DUPLICATES sets the value of DUPLICATES to ALLOWED.
The DNSCOM Commands RESTORE * RESTORE * The RESTORE * command is used to delete a locally owned copy of all aliases, composites, and groups that have been created by the COPY command. RESTORE * ON \system-1 [ at-part ] where at-part is: AT { \system-2 | name manager } \system-1 is a Guardian 90 system name. { \system-2 | name manager } indicates a system or name manager to where the command is to be directed. If omitted, the current name manager is assumed. \system-2 is a Guardian 90 system name.
The DNSCOM Commands RESTORE ALIAS RESTORE ALIAS The RESTORE ALIAS command is used to delete locally owned copies of aliases that have been created by the COPY command. RESTORE { [ ALIAS ] alias [ ON \system-1 ] } { ALIAS * [ ON \system-1 ] [ IN group ] } { alias type * [ ON \system-1 ] [ IN group ] } [ at-part ] where at-part is: AT { \system-2 | name manager } ALIAS may be omitted if alias is unique in the command name manager’s database, or if ON system is specified.
The DNSCOM Commands RESTORE ALIAS Examples RESTORE ALIAS * ON \CHICAGO RESTORE 32KDF0032A RESTORE ALIAS * IN KNOXVILLE AT \NEWYORK RESTORE CIRCUIT * Consideration See the considerations listed under the RESTORE * command.
The DNSCOM Commands RESTORE COMPOSITE RESTORE The RESTORE COMPOSITE command is used to delete locally owned copies of COMPOSITE composites that have been created by the COPY command.
The DNSCOM Commands RESTORE COMPOSITE Examples RESTORE COMPOSITE * ON \CHICAGO RESTORE RDS_T2 RESTORE COMPOSITE * IN KNOXVILLE AT \NEWYORK RESTORE X25-TERMINAL * Consideration See the considerations listed under the RESTORE * command.
The DNSCOM Commands RESTORE GROUP RESTORE GROUP The RESTORE GROUP command is used to delete a locally owned copy of groups that has been created by the COPY GROUP command. RESTORE { [ GROUP ] group [ ON \system-1 ] } [ at-part ] { GROUP * [ ON \system-1 ] [ IN group ] } where at-part is: AT { \system-2 | name manager } GROUP may be omitted if group is unique in the command name manager’s database, or if ON system is specified. group is the name of a group to be restored.
The DNSCOM Commands RESTORE MEMBERS RESTORE MEMBERS The RESTORE MEMBERS command is used to delete locally owned copies of members of groups that have been created by the COPY MEMBERS command. RESTORE [ MEMBERS ] * [ ON \system-1 ] IN group [ at-part ] where at-part is: AT { \system-2 | name manager } MEMBERS may be omitted. The required IN group parameter signals DNSCOM that this is a RESTORE MEMBERS command. \system-1 is a Guardian 90 system name.
The DNSCOM Commands SELECT SELECT The SELECT command is used to enter or exit definition mode and allows you to change the current configuration file. SELECT { DEFINITION { ON | OFF } } { DNSCONF config file } ON sets the DNS definition mode to DEFINITION ON. You must have DEFINITION authority in the current configuration or the command returns an error message. OFF sets the DNS definition mode to DEFINITION OFF, which is the default value.
The DNSCOM Commands SET ALIAS SET ALIAS The SET ALIAS command establishes new creation values for aliases for use by subsequent ADD ALIAS commands. SET [ ALIAS ] [ LIKE an alias [ ON \system-1 ] [ at-part ] ] [ parameter ] [ , parameter ] ... where at-part is: AT { \system-2 | name manager } ALIAS may be omitted if the default object is ALIAS. an alias is an alias. When specified, all attributes have their creation values equal to those defined for an alias. \system-1 is a Guardian 90 system name.
The DNSCOM Commands SET ALIAS LOCAL indicates that subsequently added aliases will not have their definitions replicated. GROUPS [ + | - ] group list + indicates that the listed groups are to be added to those specified in previous SET ALIAS commands. indicates that the listed groups are to be deleted from those previously specified. If neither + nor - appears, alias is added to the groups listed. group list is the names of a groups defined on the local system.
The DNSCOM Commands SET ALIAS TYPE alias type alias type is the name of an alias type. When the ALIAS TYPE is set, the default value of the ALIAS DOMAIN attribute is set to the value of the DOMAIN attribute for alias type. Example SET ALIAS LIKE 36KDF0032A See “Creating a Sample Database” in Section 4 for more examples.
The DNSCOM Commands SET ALIASTYPE SET ALIASTYPE The SET ALIASTYPE command establishes creation values for alias type attributes to be used in subsequent ADD ALIASTYPE commands. This command may be used only in definition mode. SET [ ALIASTYPE ] [ LIKE an alias type [ at-part ] ] [ parameter ] [ , parameter ] ... where at-part is: AT { \system | name manager } ALIASTYPE may be omitted if the default object is ALIASTYPE. an alias type is the name of some other alias type.
The DNSCOM Commands SET ALIASTYPE causes each subsystem-object type in ssobject-type list to be deleted from those for which aliases of type alias type are allowed. If omitted, the types in ssobject-type list are to replace the current list. ssobject-type list is defined as { ssobject type [ in-part ] } { ( ssobject type [ in-part ] [ , ssobject type [ in-part ] ] ... ) } where in-part is: IN { subsystem | * } ssobject type is the name of a subsystem-object type.
The DNSCOM Commands SET ALIASTYPE Examples SET ALIASTYPE TYPENUM 3 SET ALIASTYPE LIKE CIRCUIT AT \MEMPHIS See “Creating a Sample Database” in Section 4 for more examples.
The DNSCOM Commands SET COMPOSITE SET COMPOSITE The SET COMPOSITE command establishes new creation values for composite attributes for use by subsequent ADD COMPOSITE commands. SET [ COMPOSITE ] [ LIKE a composite [ ON \system-1 ] [ at-part ] ] [ parameter ] [ , parameter ] ... where at-part is: AT { \system-2 | name manager } COMPOSITE may be omitted if the default object is COMPOSITE. a composite is the name of a composite.
The DNSCOM Commands SET COMPOSITE subsystem is the name of a subsystem defining ssobject type. This must be specified if more than one subsystem defines ssobject type, unless * is specified. alias an alias that refers to the component object. ssobject is the name that the subsystem uses to refer to the component object. manager the name of the object’s manager, or an alias for the object’s manager. This may be omitted if ssobject is unique on the local node.
The DNSCOM Commands SET COMPOSITE TYPE composite type composite type is the name of the type of composite to be subsequently added. When the COMPOSITETYPE is set: The default value of the COMPOSITE DOMAIN attribute is set to the value of the DOMAIN attribute for composite type. Any previously entered SET COMPOSITE COMPONENT specifications are reviewed, and for each component that is invalid for composite type, a warning message is issued.
The DNSCOM Commands SET COMPOSITETYPE SET COMPOSITETYPE The SET COMPOSITETYPE command establishes creation values for composite type attributes for use by subsequent ADD COMPOSITETYPE commands. This command may be used only in definition mode. SET [ COMPOSITETYPE ] [ LIKE a composite type [ at-part ] ] [ , parameter] ... [ parameter ] where at-part is: AT { \system | name manager } COMPOSITETYPE may be omitted if the default object is COMPOSITETYPE. a composite type is the name of a composite type.
The DNSCOM Commands SET COMPOSITETYPE indicates that the listed types are to be deleted from those previously specified. If neither + nor - appears, the types in component list replace those previously specified. ssobject type is the name of a subsystem-object type. subsystem is the name of a subsystem defining ssobject type. This must be specified if more than one subsystem defines ssobject type, unless * is specified.
The DNSCOM Commands SET COMPOSITETYPE Examples SET COMPOSITETYPE LIKE SNA-TERMINAL AT \MEMPHIS SET COMPOSITETYPE DOMAIN NETWORK33 See “Creating a Sample Database” in Section 4 for more examples.
The DNSCOM Commands SET DNS SET DNS The SET DNS command establishes creation values for DNS attributes for use in a subsequent INITIALIZE DNS command. This command is available only in definition mode. SET DNS parameter [ , parameter ] ... DNS may be omitted if the default object is DNS. parameter is one of the following: ALLOWEXPORTS { ON | OFF } If ON is chosen, the name exporter is started when the configuration is started.
The DNSCOM Commands SET DNS MAXDOMAINS domains domains specifies the maximum number of domains that can be defined on a node. It is an integer in the range 0 through 255. MAXEXPORTS exports exports is an integer in the range 1 through 31; the default value is 31. This parameter specifies the maximum number of active export tasks that are permitted by the name exporter. MAXMANAGERS managers managers specifies the maximum number of subsystem managers that can be defined on a node.
The DNSCOM Commands SET DNSDOMAIN SET DNSDOMAIN The SET DNSDOMAIN command establishes the list of systems to be associated with domains subsequently added with the ADD DNSDOMAIN command. SET [ DNSDOMAIN ] [ LIKE a domain [ at-part ] , ] SYSTEMS [ + | - ] system list where at-part is: AT { \system | name manager } DNSDOMAIN may be omitted if the default object is DNSDOMAIN. a domain is the name of a DOMAIN.
The DNSCOM Commands SET DNSDOMAIN system list is as defined as: { \system } { ( \system [ , \system ] ... ) } \system is a Guardian 90 system name. The system must be defined to the network but does not need to be currently accessible. Example SET DNSDOMAIN LIKE NETWORK AT \MEMPHIS See “Creating a Sample Database” in Section 4 for more examples.
The DNSCOM Commands SET DNSFILE SET DNSFILE The SET DNSFILE command establishes creation values for DNS database file names.
The DNSCOM Commands SET DNSPROCESS SET DNSPROCESS The SET DNSPROCESS command establishes initialization values for DNS process attributes to be used in a subsequent INITIALIZE DNS command. This command is available only in definition mode. SET [ DNSPROCESS ] { DNS-EXPORTER | DNS-MANAGER } parameter [ , parameter ] ... DNSPROCESS may be omitted if the default object is DNSPROCESS.
The DNSCOM Commands SET DNSPROCESS Examples SET DNS-MANAGER PRIORITY 160 SET DNS-MANAGER PROCESSNAME $RDNS SET DNS-EXPORTER PRIORITY 100 Consideration If the program volume or subvolume are omitted, DNSCOM uses the defaults supplied by the CMDVOL command.
The DNSCOM Commands SET GROUP SET GROUP The SET GROUP command establishes new creation values for groups for use by subsequent ADD GROUP commands. SET [ GROUP ] parameter [ , parameter ] ... GROUP may be omitted if the default object is GROUP. parameter is one of the following: DOMAIN { domain | LOCAL } domain is the name of a DOMAIN on the current name manager’s system. This causes groups subsequently added to have their definitions replicated on the systems specified for the domain.
The DNSCOM Commands SET GROUP MEMBERS [ + | - ] { name [ ON \system-1 ] } { ( name [ ON \system-1 ] [ , name [ ON \system-1 ] ... ) } + indicates that the listed names are to be added to those specified in previous SET GROUP commands. indicates that the listed names are to be deleted from those specified in previous SET GROUP commands. If neither + nor - appears, the members of group name are to be exactly those listed. name is a DNS object name.
The DNSCOM Commands SET SS SET SS The SET SS command establishes creation values for use by subsequent ADD SS commands. This command may be used only in definition mode. SET [ SS ] [ LIKE a subsystem [ at-part ] ] [ , parameter ]... [ parameter ] where at-part is: AT { \system | name manager } SS may be omitted if the default object is SS. a subsystem is the name of another subsystem. It sets OWNER and SSNUM creation values equal to those defined for a subsystem.
The DNSCOM Commands SET SS Examples SET SS LIKE RDS AT $TTW22 SET SS LIKE RDS AT \MEMPHIS See “Creating a Sample Database” in Section 4 for more examples.
The DNSCOM Commands SET SSMANAGER SET SSMANAGER The SET SSMANAGER command establishes new creation values for managers for use by subsequent ADD SSMANAGER commands. SET [ SSMANAGER ] [ LIKE a manager [ at-part ] ] [ parameter ] [ , parameter ] ... where at-part is: AT { \system | name manager } SSMANAGER may be omitted if the default object is SSMANAGER. a manager is the name of or an alias for an existing manager.
The DNSCOM Commands SET SSMANAGER alias-spec alias [ ( { DOMAIN domain } [ , DOMAIN domain ] ) ] { TYPE alias type } [ , TYPE alias type ] alias is an alias for the manager. domain is the name of a DNS domain. If omitted, the domain of alias is inherited from alias type, if specified. If alias type is not specified, the domain of the alias defaults to the value of the DOMAIN attribute for the manager. alias type is the name of an alias type. If omitted, alias is to be an untyped alias.
The DNSCOM Commands SET SSMANAGER subsystem is the name of a subsystem. Examples SET SSMANAGER ALIASES TSSW_ALL SET SSMANAGER LIKE $PM AT $RDNS See “Creating a Sample Database” in Section 4 for more examples.
The DNSCOM Commands SET SSOBJECT SET SSOBJECT The SET SSOBJECT command establishes new creation values for subsystem-object attributes for use by subsequent ADD SSOBJECT commands. SET [ SSOBJECT ] [ LIKE an ssobject [ UNDER manager ] [ at-part ] ] [ parameter ] [ , parameter ] ... where at-part is: AT { \system | name manager } SSOBJECT may be omitted if the default object is SSOBJECT. an ssobject is the name of an existing subsystem object.
The DNSCOM Commands SET SSOBJECT indicates that the listed alias specifications are to be deleted from those specified in a previous SET SSOBJECT command. If neither + nor - appears, the listed alias specifications replace those currently existing for the object. alias-spec alias [ ( { DOMAIN domain } [ , DOMAIN domain ] ) ] { TYPE alias type } [ , TYPE alias type ] alias is an alias for the manager. domain is the name of a DNS domain.
The DNSCOM Commands SET SSOBJECT EXTERNAL { ON | OFF } If ON is specified, subsystem-object names subsequently added are also added as untyped aliases. If OFF is specified, subsystem-object names subsequently added are not added as aliases. If not explicitly set, the value of EXTERNAL for the type of subsystem object being added is assumed. MANAGER manager manager is the name of a manager or an alias for a manager.
The DNSCOM Commands SET SSTYPE SET SSTYPE The SET SSTYPE command establishes creation values for use by subsequent ADD SSTYPE commands. This command may be used only in definition mode. SET [ SSTYPE ] [ LIKE an ssobject type [ IN subsystem ] [ at-part ] ] [ parameter ] [ , parameter ] ... where at-part is: AT { \system | name manager } SSTYPE may be omitted if the default object is SSTYPE. an ssobject type is the name of an subsystem-object type.
The DNSCOM Commands SET SSTYPE LOCAL If specified, the default domain for instances of the types is empty; that is, the definitions of untyped aliases that refer to objects of these types are not replicated. DUPLICATES [ NOT ] ALLOWED If NOT is specified, subsystem-object names of this type must be unique irrespective of manager. If NOT is omitted, subsystem-object names of this type must only be unique within manager. This is the default setting.
The DNSCOM Commands SET SSTYPE DEVICENAME indicates that objects of this type must have valid Guardian 90 logical device names. When adding a subsystem object of the type using the ADD SSOBJECT command, DNSCOM expands the name using the specifications from the most recent NAMESYS command. DNSNAME indicates that objects of this type must have valid DNS object names.
The DNSCOM Commands SET SSTYPE SUBDEVICENAME SUBDEVICENAME-1 SUBDEVICENAME-2 indicates that objects of this type must have valid Guardian 90 subdevice names. Where SUBDEVICENAME is specified, one or two levels of subdevice name may be specified. Where SUBDEVICENAME-1 is specified, only a single level of subdevice name is allowed (such as $X.#Y). Where SUBDEVICENAME-2 is specified, two levels of subdevice name are required (such as $X.#Y.Z).
The DNSCOM Commands SHOW ALIAS SHOW ALIAS The SHOW ALIAS command displays the alias creation values that have been established by the SET ALIAS command. SHOW [ ALIAS ] [ parameter [ , parameter ] ... ] ALIAS may be omitted if the default object is ALIAS. parameter is one of the following: DOMAIN GROUPS REFERENT TYPE If no parameters are supplied, the values of the attributes listed above are displayed. Default values for DNS attributes are listed in Table 6-1 in Section 6.
The DNSCOM Commands SHOW ALIASTYPE SHOW ALIASTYPE The SHOW ALIASTYPE command displays the creation values of alias type attributes established by previous SET ALIASTYPE commands. SHOW [ ALIASTYPE ] [ parameter [ , parameter ] ... ] ALIASTYPE may be omitted if the default object is ALIASTYPE. parameter is one of the following: DOMAIN OWNER SSTYPES TYPENUM If no parameters are supplied, the values of the attributes listed above are displayed.
The DNSCOM Commands SHOW COMPOSITE SHOW COMPOSITE The SHOW COMPOSITE command displays the composite creation attributes that have been established by the SET COMPOSITE command. SHOW [ COMPOSITE ] [ parameter [ , parameter ] ... ] COMPOSITE may be omitted if the default object is COMPOSITE. parameter is one of the following: [ COMPONENT ] ssobject type [ IN { subsystem | * } ] COMPONENT * DOMAIN GROUPS TYPE ssobject type is the name of a subsystem-object type.
The DNSCOM Commands SHOW COMPOSITETYPE SHOW COMPOSITETYPE The SHOW COMPOSITETYPE command displays the creation values of composite type attributes established by previous SET COMPOSITETYPE commands. SHOW [ COMPOSITETYPE ] [ parameter [ , parameter ] ... ] COMPOSITETYPE may be omitted if the default object is COMPOSITETYPE. parameter is one of the following: COMPONENTS [ * ] DOMAIN OWNER TYPENUM If no parameters are supplied, the values of the attributes listed above are displayed.
The DNSCOM Commands SHOW DNS SHOW DNS The SHOW DNS command displays the initialization values of DNS attributes. SHOW [ DNS ] [ parameter [ , parameter ] ... ] DNS may be omitted if the default object is DNS. parameter is one of the following: ALLOWEXPORTS ALLOWIMPORTS DNSOWNER EXPORTDELAY MAXDOMAINS MAXEXPORTS MAXMANAGERS MAXNAMES MAXTYPES SECURITY If no parameters are supplied, the values of the attributes listed above are displayed.
The DNSCOM Commands SHOW DNSDOMAIN SHOW DNSDOMAIN The SHOW DNSDOMAIN command displays the systems that are to be included in a domain defined by a subsequent ADD DNSDOMAIN command. SHOW [ DNSDOMAIN ] [ SYSTEMS ] DNSDOMAIN may be omitted if the default object is DNSDOMAIN. SYSTEMS is included for compatibility with future DNS releases.
The DNSCOM Commands SHOW DNSFILE SHOW DNSFILE The SHOW DNSFILE command displays creation values of DNS database file names.
The DNSCOM Commands SHOW DNSPROCESS SHOW DNSPROCESS The SHOW DNSPROCESS command displays the creation values of DNS process attributes. SHOW [ DNSPROCESS ] { DNS-EXPORTER } { DNS-MANAGER } { * } [ parameter [ , parameter ] ... ] DNSPROCESS may be omitted if the default object is DNSPROCESS. parameter is one of the following: CPUS PRIORITY PROCESSNAME PROGRAM SWAPVOL If no parameters are supplied, the values of the attributes listed above are displayed.
The DNSCOM Commands SHOW GROUP SHOW GROUP The SHOW GROUP command displays the group name creation attributes that have been established by the SET GROUP command. SHOW [ GROUP ] [ parameter [ , parameter ] ... ] GROUP may be omitted if the default object is GROUP. parameter is one of the following: DOMAIN GROUPS [ * ] MEMBERS [ * ] If no parameters are supplied, the values of the attributes listed above are displayed. Default values for DNS attributes are listed in Table 6-1 in Section 6.
The DNSCOM Commands SHOW SS SHOW SS The SHOW SS command displays the subsystem creation attributes that have been established by the SET SS command. SHOW [ SS ] [ parameter [ , parameter ] ... ] SS may be omitted if the default object is SS. parameter is one of the following: OWNER SSNUM If no parameters are supplied, the values of the attributes listed above are displayed. Default values for DNS attributes are listed in Table 6-1 in Section 6.
The DNSCOM Commands SHOW SSMANAGER SHOW SSMANAGER The SHOW SSMANAGER command displays the manager creation attributes that have been established by the SET SSMANAGER command. SHOW [ SSMANAGER ] [ parameter [ , parameter ] ... ] SSMANAGER may be omitted if the default object is SSMANAGER. parameter is one of the following: ALIASES [ * ] DOMAIN SUBSYSTEMS [ * ] If no parameters are supplied, the values of the attributes listed above are displayed.
The DNSCOM Commands SHOW SSOBJECT SHOW SSOBJECT The SHOW SSOBJECT command displays the subsystem-object creation attributes that have been established by the SET SSOBJECT command. SHOW [ SSOBJECT ] [ parameter [ , parameter ] ... ] SSOBJECT may be omitted if the default object is SSOBJECT. parameter is one of the following: ALIASES [ * ] DOMAIN EXTERNAL MANAGER TYPE If no parameters are supplied, the values of the attributes listed above are displayed.
The DNSCOM Commands SHOW SSTYPE SHOW SSTYPE The SHOW SSTYPE command displays creation values of subsystem-object type attributes established by previous SET SSTYPE commands. SHOW [ SSTYPE ] [ parameter [ , parameter ] ... ] SSTYPE may be omitted if the default object is SSTYPE. parameter is one of the following: DOMAIN DUPLICATES EXTERNAL FORMAT SUBSYSTEM TYPENUM If no parameters are supplied, the values of the attributes listed above are displayed.
The DNSCOM Commands START DNS START DNS The START DNS command creates the DNS processes. START [ DNS ] [ ON \system ] [ USING config file ] DNS may be omitted if the default object is DNS. \system is a Guardian 90 system name. When specified, indicates the node where DNS is to be started. The name of the configuration file used to start DNS is formed by applying \system to the current configuration file. If omitted, the system specified by the last CMDSYS or SYSTEM command is assumed.
The DNSCOM Commands STATUS DNS STATUS DNS The STATUS DNS command displays the status of a DNS configuration. STATUS [ DNS ] [ at-part ] [ , DETAIL ] where at-part is: AT { \system | name manager } DNS may be omitted if the default object is DNS. \system is a Guardian 90 system name. If included, specifies the system for which DNS status is desired. If omitted, the local (OPEN) system is assumed. If no system is currently open, the system specified by the last CMDSYS command is assumed.
The DNSCOM Commands STATUS DNS If DNS is running and DETAIL is included, the display is similar to the following: DNS status at 08:11:43 , 16 Nov 1992 SYSTEM \NOREAST State: RUNNING Process $ZDNS Type Manager Primary Backup Openers 3,029 10,096 \NOREAST.12,132 \NOREAST.$Z0 \NOREAST.
The DNSCOM Commands STATUS EXPORT STATUS EXPORT The STATUS EXPORT command allows the user to obtain information about the state of the export mechanism. STATUS { [ EXPORT ] \system } [ at-part ] { EXPORT } where at-part is: AT { \system | name manager } \system is the name of a system in the Expand network. If specified, only status for the named system is displayed. If omitted, status information for all systems for which the local system has control records is displayed.
The DNSCOM Commands STATUS EXPORT Line 3 gives the Initialization Time Stamp (ITS) for \NUCOMM and indicates that: There are entries in the \NUCOMM secondary queue (Queued = Yes). \NUCOMM is enabled for export at \VIEW (Enabled = Yes). There is currently running EXPORT task for \NUCOMM (Active = Yes). There are current no entries in the \NUCOMM Hold queue (Hold = NO). Line 4 gives the ITS for \COMM and indicates that: There are no entries in the \CARSON secondary queue (Queued = No).
The DNSCOM Commands STOP DNS STOP DNS The STOP DNS command stops a DNS configuration. STOP [ DNS ] [ at-part ] [ ! ] [ , WAIT { ON | OFF } ] where at-part is: AT { \system | name manager } DNS may be omitted if the default object is DNS. { \system | name manager } is a system or name manager where the command is to be executed. If omitted, the current name manager is assumed. \system is a Guardian 90 system name. It designates a node other than the current system for processing the command.
The DNSCOM Commands STOP DNS Considerations If WAIT ON is specified, DNSCOM periodically produces a STATUS DNS, DETAIL display until DNS is stopped. If a STOP DNS command is issued while a START DNS command is in progress, DNSCOM displays an error message and ignores the STOP request.
The DNSCOM Commands SYSTEM SYSTEM The SYSTEM command sets the default system for expansion of any file names. SYSTEM [ \system ] \system is a Guardian 90 system name. If the SYSTEM command is not issued, the default settings in effect when DNSCOM was started are used. If the system name is omitted, the default is set for local file name expansion. Note that this is not the same as specifying the local system name.
The DNSCOM Commands VOLUME VOLUME The VOLUME command sets the default volume and subvolume names for subsequent file references. VOLUME [ $volume ] [ [ $volume.] subvolume ] volume is a Guardian 90 volume name. subvolume is a Guardian 90 subvolume name. Examples VOLUME VOLUME $DATA.RDSDNS VOLUME MYDNS VOLUME $SMOKE Considerations If the VOLUME command is not issued, the default settings in effect when DNSCOM was started are used.
Appendix A Configuration File Verification DNSCOM performs the following checks on a configuration file: 1. The file name must be in the format of a disk file; partial names are expanded using the current CMDSYS and CMDVOL settings. 2. If the file does not exist (FILEINFO returns FENOTFOUND [11]), a warning message is issued and no further tests are made. The file still becomes the current configuration file. 3. The user must have READ access to the file. 4.
Appendix B DNSCOM Error Messages This appendix describes the error and warning messages issued by DNSCOM. Error 1 ERROR 1 - Name Manager Does Not Support this Command The current name manager is at a lower release level than the DNSCOM being used and does not support the command just issued. Error 2 ERROR 2 - Name Already Has an Alias of Type aliastype An attempt to add a typed ALIAS failed because the specified REFERENT already has an ALIAS of the type indicated by aliastype.
DNSCOM Error Messages Error 8 ERROR 8 - Illegal Combination of Attribute Values The current command is rejected because it would have resulted in an illegal combination of attribute values. Error 9 ERROR 9 - Illegal Number of Components The current ADD COMPOSITETYPE command failed because more COMPONENTS were specified than the name manager allows.
DNSCOM Error Messages Error 14 ERROR 14 - Name in use - name The current DELETE command failed because references to the name exist in the DNS database. Possible references are dependent on the type of name as follows: ALIAS The ALIAS was created as a result of its REFERENT being defined with EXTERNAL ON; such aliases may be deleted by altering the REFERENT to EXTERNAL OFF. ALIASTYPE, COMPOSITETYPE aliases or composites of the type exist in the database.
DNSCOM Error Messages Error 18 ERROR 18 - DNSCOM/DNSMGR Error - Invalid File Number The current command is rejected because DNSCOM passed an illegal value in a ZDNS-DDL-FILENO field. This problem should be reported to your Tandem representative. Error 19 ERROR 19 - Name Manager doesn't support format code - number The current ADD or ALTER command is rejected because the name manager doesn’t recognize the FORMAT represented by number.
DNSCOM Error Messages Error 24 ERROR 24 - Database I/O Error FILE ERROR file name error text The current command failed because an I/O error occurred on the specified file. Error 25 ERROR 25 - Last SUBSYSTEM in SSMANAGER May Not be Deleted The current ALTER SSMANAGER command is rejected because it would have resulted in the manager having an empty subsystem list. Warning 26 WARNING 26 - Last System Deleted from DNSDOMAIN domain The indicated domain is empty.
DNSCOM Error Messages Error 35 ERROR 35 - Required Parameter Not Supplied - parameter The current ADD command is rejected because the required indicated parameter was not previously set with the SET command. Error 36 ERROR 36 - DNSCOM/DNSMGR Error - Routing Error The current command is rejected because DNSCOM passed an SSID other than ZDNSVAL-SSID in an SPI buffer header. This error should be reported to your Tandem representative.
DNSCOM Error Messages Error 42 ERROR 42 - DNSCOM/DNSMGR Incompatibility - Buffer Size Error The version of the name manager requires a larger response buffer than that supplied by DNSCOM. Error 44 ERROR 44 - Name Manager Buffer Allocation Failure The name manager is unable to allocate a buffer from one of its internal pools.
DNSCOM Error Messages Warning 49 WARNING 49 - Duplicate SSTYPE - name In response to a SET ALIASTYPE command, the indicated name is already in the subsystem-object types list. In response to an ALTER ALIASTYPE command, the indicated name is already on the subsystem-object types list for the specified alias type. Warning 50 WARNING 50 - Duplicates Subsystem - name In response to a SET SSMANAGER command, the indicated name is already in the subsystems list.
DNSCOM Error Messages Warning 54 WARNING 54 - Not Previously Copied - name Returned in response to a RESTORE command where the indicated name has not been previously copied using the COPY command. Warning 55 WARNING 55 - SSTYPE Not Found - name In response to a SET ALIASTYPE command, indicates that a request to delete an SSTYPE from the current SSTYPES list failed because the indicated SSTYPE is not on the list.
DNSCOM Error Messages Error 59 ERROR 59 - Active Definition May Not be Restricted This error is returned in the following cases: When an ALTER SSTYPE command attempts to change the FORMAT of the SSTYPE to a value other than ANY, and there are ssobjects defined with that SSTYPE. When an ALTER ALIASTYPE command attempts to change an alias type’s SSTYPES list from “*” to a specific list and there are aliases defined with that alias type.
DNSCOM Error Messages Error 65 ERROR 65 - Parameter(s) Not Supported by Name Manager The current command failed because it contained one or more parameters not supported by the version of name manager to which the request was sent. Error 66 ERROR 66 - DNSCOM/DNSMGR Error - DNSMGR SSGET Status - status This error indicates that the current request failed because the name manager received an unexpected status from the SSGET procedure.
DNSCOM Error Messages Error 71 ERROR 71 - Illegal logical file - file name The current command failed because the DNSCOM or the name manager discovered that the indicated logical file (for example, DNS-ALPHA-FILE or DNS-NAME-FILE) failed one of the following checks: The file code is not 850. The file is not key-sequenced. The key offset of the file is not 0. The file has the wrong key length. The file has the wrong record length.
DNSCOM Error Messages Error 1001 ERROR 1001 - Token Too Long A token in a DNSCOM command exceeded 162 characters in length. Error 1002 ERROR 1002 - Illegal Syntax The command did not follow the rules for valid DNSCOM commands. Error 1003 ERROR 1003 - Illegal File Name DNSCOM did not find a valid Guardian 90 file name when expected.
DNSCOM Error Messages Error 1007 ERROR 1007 - Unable to Apply Default System to this File Name - file name The indicated file name has an eight-character device name (including $) and hence cannot be placed in network format. Error 1008 ERROR 1008 - Wrong Name Type - name While name exists in the DNS database, it has the wrong type to be used as it was in the current command.
DNSCOM Error Messages Error 1014 ERROR 1014 - Illegal Subvolume Name A subvolume name is not found where DNSCOM expected one. Error 1015 ERROR 1015 - Must be Disk File DNSCOM was expecting the name of a disk file but the indicated name has the format of a nondisk file. Error 1016 ERROR 1016 - Only Volume Name Allowed DNSCOM was expecting the name of a disk volume but the indicated name has the format of a file name.
DNSCOM Error Messages Error 1022 ERROR 1022 - Unable to Access $SYSTEM.SYSTEM.USERID DNSCOM was unable to access $SYSTEM.SYSTEM.USERID to verify a user name. Error 1023 ERROR 1023 - Unknown Userid The indicated user name is not defined on DNSCOM’s system. Error 1024 ERROR 1024 - Volume Name Required A volume name was not found where expected. Error 1025 ERROR 1025 - OBEYs Nested Too Deeply OBEY commands were nested to a level greater than four.
DNSCOM Error Messages Error 1029 ERROR 1029 - Process isn't a DNS Name Manager - process name This error is returned because the one of the following applies to the indicated process: It does not accept WRITEREAD requests. It returned a malformed SPI buffer in response to a GETVERSION SPI command. It returned an SPI buffer owned by a subsystem other than DNS.
DNSCOM Error Messages Error 1036 ERROR 1036 - Must be DNSCOM Reserved Word. Parameters in the HELP command that are not enclosed in angle brackets (< >) must be DNSCOM keywords. Error 1037 ERROR 1037 - Value Illegal in ALTER Command The indicated value, while valid in an ADD or SET command, may not be used in an ALTER command. Warning 1038 WARNING 1038 - Duplicate SSTYPE Replaced - sstype name This warning is returned in response to a SET or ADD ALIASTYPE command.
DNSCOM Error Messages Error 1042 ERROR 1042 - Name Manager Not Started, PROCESS_CREATE_ Error error:detail The indicated error is returned by the PROCESS_CREATE_ procedure; error is the value returned by PROCESS_CREATE_; and detail is the value returned in the error-detail parameter. Refer to the System Procedure Errors and Messages Manual for more information about system procedure errors.
DNSCOM Error Messages Error 1050 ERROR 1050 - Use DELETE ALIAS Command to Reset Aliases Returned in response to an ALTER command that requests RESET ALIASES. The DELETE ALIAS command must be used to delete aliases of a manager or subsystem object. Warning 1051 WARNING 1051 - Component Not Found This warning is returned in response to a request to a RESET COMPOSITE COMPONENT where the named COMPONENT was not previously set with a SET command.
DNSCOM Error Messages Error 1057 ERROR 1057 - Invalid Owner DNSCOM did not find a valid owner name where expected. Warning 1058 WARNING 1058 - No Name(s) Found to COPY This warning is returned in response to a COPY command where no names matching the request are found that could be copied. Warning 1059 WARNING 1059 - No Name(s) Found to DELETE This warning is returned in response to a DELETE command where no names matching the request are found that could be deleted.
DNSCOM Error Messages Warning 1065 WARNING 1065 - Current Name Manager has been Closed - name A command causes the current manager name to change, and DNSCOM currently has a name manager open with the old name. Error 1066 ERROR 1066 - Configuration File is Corrupt - file name The indicated DNS configuration file is incomplete or damaged. You should purge the file and create a new one with an INITIALIZE DNS, DNSCONFONLY command.
DNSCOM Error Messages Error 1072 ERROR 1072 - Missing Logical File Name DNSCOM expected a logical file name (for example, DNS-ALPHA-FILE or DNSNAME-FILE) or the asterisk (*). Error 1073 ERROR 1073 - Missing Logical Process Name DNSCOM expected DNS-MANAGER, DNS-EXPORTER, or the asterisk (*). Warning 1074 WARNING 1074 - No Name(s) Found This warning is returned in response to an INFO or LIST command where no names matching the request are found.
Appendix C Reserved Words The following words are reserved in DNS and may not be used as names. However, you can use any of these names if you precede the name with a percent sign (%).
Reserved Words DNS-MAP-FILE DNS-MEMBER-FILE DNS-NAME-FILE DNS-QUEUE-FILE DNS-RFAST-FILE DNS-RMAP-FILE DNS-RNAME-FILE DNS-TYPES-FILE DNSCONF DNSCONFONLY DNSDOMAIN DNSFILE DNSNAME DNSOWNER DNSPROCESS DOMAIN DUPLICATES E ENABLE ENV ERRORS EVENTLOG EXIT EXPLODE EXPORT EXPORTDELAY EXTERNAL FILENAME FORMAT FULLNAMES GROUP GROUPS HASMANAGER HELP IN INFO INITIALIZE INSPECT LIKE LIST LOCAL MANAGER MAXDOMAINS MAXMANAGERS MAXNAMES MAXTYPES MEMBERS C–2 31258 Tandem Computers Incorporated
Reserved Words NAMESYS NAMEVOL NO NOT O OBEY OBEYFORM OBEYSYS OBEYVOL OFF ON OPEN OUT OWNER PATHWAYNAME PRINTL PRINTQ PRIORITY PROCESSNAME PROCESSQUALIFIER PROGRAM PURGEQ REFERENT RESELECT RESET RESTORE SAVEABEND SECURITY SELECT SET SHOW SS SSMANAGER SSNUM SSOBJECT SSTYPE SSTYPES START STATUS STOP SUBDEVICENAME SUBDEVICENAME-1 SUBDEVICENAME-2 SUBSYSTEM SUBSYSTEMS SWAPVOL SYSTEM 31258 Tandem Computers Incorporated C–3
Reserved Words SYSTEMNAME SYSTEMS TYPE TYPENUM UNDER USING VOLUME WAIT WARNINGS C–4 31258 Tandem Computers Incorporated
Glossary This glossary defines technical terms that are used in this manual. Some of these terms are also defined in the Distributed Systems Management (DSM) Management Programming Manual. alias. Any name that the user can enter to identify an object. In the context of DNS, every alias corresponds to a particular subsystem-object name recognized by some subsystem or by the Guardian 90 operating system.
Glossary command name manager. The DNS name manager executing an issued command. If the AT paramerer is specified after the object of a command, the command name manager becomes the name manager specified in that AT paramerer. If no AT paramerer is specified, the command name manager is the current name manager. composite. A name for one object that has different aspects controlled by different subsystems. A user defines composite objects to DNS.
Glossary context-sensitive server. A server that retains information about previous processing. For instance, in performing a command on a list of objects, a context-sensitive server might retain, between reply messages, the name of the object it last processed. Context-sensitive servers limit or complicate the requester’s ability to interrupt or abandon the continuation of a series of replies. continuation. The packaging of a response in multiple reply messages.
Glossary system and network objects, facts about their relationships, and instructions for replicating name definitions on remote nodes. The completed database, which you update as needed to reflect configuration changes, is an online resource to operators and management applications. The subsystem includes both an interactive text interface (DNSCOM) and a programmatic command interface based on SPI. Distributed Systems Management (DSM).
Glossary domain name. A name assigned by a user to identify a domain to DNS. DSM. See Distributed Systems Management. DSMA. See Distributed Systems Management Application. DSMS. See Distributed Systems Management Solutions. DSNM. See Distributed Systems Network Management. empty list or variable. A list that has no members, or a variable that has no content. EMS. See Event Management Service. error. A condition that causes a command or other operation to fail. Compare warning. error number.
Glossary exporter process. A DNS process that manages the time-staged replication of name definitions on remote nodes. This process is not a NonStop process pair. format. The organization (relative or absolute positions of elements) in a symbolic representation. In DNS, the attribute of a subsystem-object type that describes the constraints on names for objects of that type. File Utility Program (FUP). The Tandem interactive utility that lets you perform a variety of operations on files. FUP.
Glossary management interface. An interactive or programmatic interface through which one can manage a subsystem and its objects. In some subsystems, a specific process is dedicated to the management interface; in other subsystems, the process that provides the management interface also performs other functions. management process. The process through which an application issues commands to a subsystem.
Glossary node. an individual Tandem computer system within a network of such systems. (Each system consists of two or more processor modules, an interprocessor bus, an input/output channel, and two or more device controllers.) null value. A value indicating that a program has made no explicit assignment to a variable or field.
Glossary Control Process (TCP) and user-written SCREEN-COBOL program units, and servers grouped into server classes to perform the requested processing. ViewPoint is a Pathway application. programmatic command. A command issued by a program, rather than by a human operator. programmatic interface. A means for a program to communicate with another program.
Glossary SCP. See Subsystem Control Point. session. The period during which two entities can exchange data. In the context of a management application, the period during which an application can issue commands to a subsystem. In the context of a command interpreter, the period during which a user can issue commands to the command interpreter. simple object. An object that is managed by a single subsystem. SNA. See Systems Network Architecture. SNAX Extended Facility (SNAX/XF).
Glossary Subsystem Control Facility (SCF). An interactive interface for configuring, controlling, and collecting information from Tandem data communications subsystems. Subsystem Control Point (SCP). The management process for all Tandem datacommunications subsystems. There can be several instances of this process. Applications using SPI send all commands for data-communications subsystems to an instance of this process, which in turn sends them on to the manager processes of the target subsystems.
Glossary subsystem-object type. The owner.subsystem number.subsystem-object type number grouping always provides a unique identifier for the subsystem-object type that is independent of the subsystem-object type name assigned by a particular user. Developers of management applications should always use the owner.subsystem number.
Glossary type. See alias type, subsystem-object type, and composite type. type number. See alias type number, subsystem-object type number, and composite type number. type name. See alias type name, subsystem-object type name, and composite type name. typed alias. An alias with a type attribute, used in an application where it is required to distinguish between multiple aliases for the same object. untyped alias.
Index A Accessing other nodes AT phrase 6-15 entering commands 6-15 INFO command 6-15 LIST command 6-15 STATUS command 6-15 STOP command 6-15 ADD ALIAS command, DNSCOM 4-26 ADD ALIASTYPE command, DNSCOM 7-15 ADD command DNSCOM 4-6, 4-7, 6-17, 7-8 general notes 7-8 LIKE phrase 7-8 listed elements 6-17 purpose 7-8 with the LIKE phrase 4-7 with the SET command 4-6 ADD command, DNSCOM 5-3 ADD COMPOSITE command, DNSCOM 7-18 ADD COMPOSITETYPE command, DNSCOM 7-22 ADD DNSDOMAIN command, DNSCOM 7-25 ADD GROUP comma
Index Alias benefits for having 4-25/26 defined 2-4 defining 4-25/28 guidelines for selecting 4-2 referent 4-26 specifying in manager definitions 4-9 specifying in object definitions 4-9 translation 4-26 typed 2-4, 4-18 untyped 2-4, 4-19 Alias definition dependencies 4-26 what to specify 4-26 Alias lists adding alias types 4-9 adding domains 4-9 manager definitions 4-9 object definitions 4-9 Alias type 4-19 defined 2-3 defined in alias list 4-9 defining 4-18/20 name 4-18 Alias type definition dependencies
Index ALTER ALIAS command, DNSCOM 4-26, 7-45 ALTER ALIASTYPE command, DNSCOM 7-47 ALTER command AT phrase 7-8 DNSCOM 4-6, 4-7, 6-15, 6-16, 6-17, 7-8, 7-9 general notes 7-8 listed elements 6-16 OBEYFORM parameter 7-9 other managers 6-15 with the LIKE phrase 4-7 ALTER command, similar to ADD command 4-1 ALTER COMPOSITE command, DNSCOM 7-49 ALTER COMPOSITETYPE command, DNSCOM 7-51 ALTER DNS command, DNSCOM 3-9, 3-10, 5-3, 7-52 ALTER DNSDOMAIN command, DNSCOM 7-54 ALTER DNSFILE command, DNSCOM 7-56 ALTER DNSPR
Index Attributes ALIASES 6-4, 6-5 ALL ERRORS 6-11 ALLOWEXPORTS 5-2, 6-2 ALLOWIMPORTS 6-2 COMPONENT 6-4 COMPONENTS 6-2 CPUS 6-2, 6-5 defining 4-6 DNSCONFONLY 3-12 DNSOWNER 6-2 DOMAIN 4-12, 4-32, 4-34, 6-2, 6-4, 6-5 DUPLICATES 4-11, 6-2 EXPORTDELAY 6-2 EXTERNAL 4-12, 6-2, 6-4 FILENAME 6-2, 6-5 FORMAT 4-11/25, 6-2 group 4-30 GROUPS 6-4, 6-17 HASMANAGER 4-8, 6-2, 6-4 MANAGER 6-2, 6-4 MAXDOMAINS 6-2 MAXEXPORTS 6-2 MAXMANAGERS 6-2 MAXNAMES 6-2 MAXTYPES 6-2 MEMBERS 4-31, 6-4 optional 6-2 OWNER 4-10, 6-2 PRIORITY
Index Authority, operating modes 3-11 AUTOLOAD, DSNM 3-2 B Backing up configuration file 3-12 Backslash character (\), subsystem-object names 4-25 Banner display, DNSCOM 6-10 Basic DNSCOM commands 6-1 BEGINTRANSACTION procedure 5-2 BILL database file 3-8 BREAK key, using in DNSCOM 6-13 Breakdown, name 1-5 C Case-insensitive names in DNSCOM 4-8 Case-sensitive, OWNER 4-8 Changing current configuration 6-8/9 Changing current name manager 6-8/9 AT phrase 6-8 Changing default configuration 6-9 OPEN command 6-9
Index Command processing AT phrase 6-9 remote system 6-9 Command types, DNSCOM basic 6-1 inquiry 6-1 operational 6-1 update 6-1 Commands, DNSCOM ADD 4-6, 4-7, 5-3, 6-17, 7-8 ADD ALIAS 4-26 ADD ALIASTYPE 7-15 ADD COMPOSITE 7-18 ADD COMPOSITETYPE 7-22 ADD DNSDOMAIN 7-25 ADD GROUP 7-27 ADD SS 4-9, 4-13, 7-30 ADD SSMANAGER 4-9, 7-32 ADD SSOBJECT 4-9, 7-35 ADD SSTYPE 4-10, 4-11, 7-39 ALLOW 7-44 ALTER 4-6, 4-7, 6-15, 6-16, 6-17, 7-8, 7-9 ALTER ALIAS 4-26, 7-45 ALTER ALIASTYPE 7-47 ALTER COMPOSITE 7-49 ALTER COMP
Index COPY GROUP 7-77 COPY MEMBERS 7-78 DELETE 4-38, 6-15 DELETE ALIAS 7-79 DELETE ALIASTYPE 7-81 DELETE COMPOSITE 7-82 DELETE COMPOSITETYPE 7-84 DELETE DNS 5-3 DELETE DNSDOMAIN 7-86 DELETE GROUP 7-87 DELETE SS 7-89 DELETE SSMANAGER 7-90 DELETE SSOBJECT 7-91 DELETE SSTYPE 7-93 DISABLE EXPORT 7-95 ENABLE EXPORT 5-7, 7-96 ENV 7-97 EXIT 6-11, 7-98 FC 7-99 HELP 7-100 INFO 3-13, 4-32, 6-14/15, 6-18, 7-10 INFO * 7-102 INFO ALIAS 7-104 INFO ALIASTYPE 7-106 INFO COMPOSITE 7-108 INFO COMPOSITETYPE 7-110 INFO DNS 7-
Index LIST COMPOSITE 7-140 LIST COMPOSITETYPE 7-142 LIST DNS 7-144 LIST DNSDOMAIN 7-145 LIST DNSFILE 7-146 LIST DNSPROCESS 7-148 LIST GROUP 7-149 LIST MEMBERS 7-151 LIST SS 7-152 LIST SSMANAGER 7-153 LIST SSOBJECT 7-154 LIST SSTYPE 7-156 NAMESYS 6-19, 7-158 NAMEVOL 7-159 OBEY 6-11, 7-160 OBEY LOAD 3-6 OBEYSYS 7-161 OBEYVOL 3-6, 7-162 OPEN 6-8, 6-9, 7-163 OUT 6-18, 7-164 RESELECT 7-165 RESET 6-17 RESET ALIAS 7-166 RESET ALIASTYPE 7-167 RESET COMPOSITE 7-168 RESET COMPOSITETYPE 7-169 RESET DNS 7-170 RESET DN
Index sample database 4-35/37 SELECT 6-9, 7-186 SELECT DEFINITION 3-4, 3-11 SELECT DNSCONF 3-4 SET 3-8, 4-6, 4-7, 6-17, 7-8, 7-9 SET ALIAS 7-187 SET ALIASTYPE 7-190 SET COMPOSITE 7-193 SET COMPOSITETYPE 7-196 SET DNS 3-4, 7-199 SET DNSDOMAIN 7-201 SET DNSFILE 7-203 SET DNSOWNER 3-9 SET DNSPROCESS 3-5, 7-204 SET GROUP 7-206 SET SS 7-208 SET SSMANAGER 7-210 SET SSOBJECT 7-213 SET SSTYPE 7-216 SHOW 4-6 SHOW ALIAS 7-220 SHOW ALIASTYPE 7-221 SHOW COMPOSITE 7-222 SHOW COMPOSITETYPE 7-223 SHOW DNS 7-224 SHOW DNSD
Index Comment line characters (==) 6-11, 7-8, 7-9 Comments on command line 6-11 Communication line name, example of 1-3 Component 4-28 of composite type 2-3, 4-14 COMPONENT attribute, default 6-4 COMPONENTS attribute, default 6-3 Composite object, defining 4-28/29 Composite object definition, what to specify 4-28 Composite object, defined 2-4 Composite type component of 2-3, 4-14 defining 4-14/18 DOMAIN attribute 4-12 instances of 4-17 name 4-14 Composite type definition dependencies 4-14 what to specify 4
Index Configurations DNS files 3-2 DNS processes 3-2 multiple 3-2 name exporter 3-2 name manager 3-2 Continuation character (&) 6-13 in command file 6-11 Continued line, entering commands 6-13 Copied name definition 3-12 COPY * command, DNSCOM 7-72 COPY ALIAS command, DNSCOM 7-73 COPY command, other managers 6-15 COPY command, DNSCOM 3-12, 5-7, 5-8, 6-15 COPY COMPOSITE command, DNSCOM 7-75 COPY database file 3-8 COPY GROUP command, DNSCOM 7-77 COPY MEMBERS command, DNSCOM 7-78 Copying definitions using OBE
Index D Database and network control node 5-10 and remote nodes 5-10 security 3-9/11 Database, DNS 1-5 Database files default names 3-8 described 1-10 Database replication 5-3 Database, reloading 3-13 Database, sample 4-35/37 DBDDLS DSV file 3-3 Default configuration 3-2 Default configuration file 6-6 initial open 6-7 Default configuration file, changing 6-6 Default name manager 6-7 DEFAULTS attribute 6-6 DEFINE =_DNS_CONFIG 6-6, 6-7, 6-9 DEFINE =_DNS_CONFIG map 6-6 Defining alias type, specific characteri
Index Definition authority 3-10 Definition mode available operations 6-12 defined 6-12 security 3-11 Definition node 5-1, 5-7, 5-10 accessing 4-2 domain name 4-33 unavailable 3-12 Definition node, local definitions 4-1 Definitions blank spaces 4-8 length 4-8 DELETE ALIAS command, DNSCOM 7-79 DELETE ALIASTYPE command, DNSCOM 7-81 DELETE command DNSCOM 4-38 6-15 other managers 6-15 DELETE COMPOSITE command, DNSCOM 7-82 DELETE COMPOSITETYPE command, DNSCOM 7-84 DELETE DNS command, DNSCOM 5-3 DELETE DNSDOMAIN
Index DNS Expand network 1-1 initializing 3-3/6 interactive interface 6-1 NonStop subsystem 1-1 programmatic interface 6-2 purpose 1-2 DNS architecture, described 1-9 DNS components 1-11 DNS configurations database files 1-10 name exporter 1-10 name manager 1-10 queue file 1-10 DNS database 1-5 DNS dependencies Guardian 3-1 TMF 3-1 DNS files DBDDLS 1-9 DNSCOM 1-9 DNSEXP 1-9 DNSHELP 1-9 DNSMGR 1-9 LOAD 1-9 ownership 3-6 security 3-6 DNS names, deleting 4-38 DNS owner, security 3-10 DNS uses assigning aliase
Index DNSCOM command 3-3 DNSCOM command types 6-1/2 DNSCOM commands basic 7-5 inquiry 7-4 management operations 3-1 operational 7-5 sample database 4-35/37 update 7-1 DNSCOM DSV file 3-3 DNSCONF 3-2, 6-6, 6-7 DNSCONFONLY attribute 3-12 DNSDOMAIN name, no dependencies 4-4 DNSEXP DSV file 3-3 DNSHELP DSV file 3-3 DNSMGR DSV file 3-3 DNSOWNER attribute, default 6-3 Dollar sign ($), subsystem-object names 4-25 Domain 2-5, 2-6 defined 2-5 defined in alias lists 4-9 defining 4-33/34 examples 2-5 nodes in 2-5 rep
Index DSNM, updating the DNS database 3-7 DSV files, DNSCOM 3-3 DUPLICATES attribute 4-11 DUPLICATES attribute, default 6-3 Duplicates, avoiding 5-7 E Efficient name distribution, strategy 4-1 Efficient name distribution,strategy ENABLE EXPORT command, DNSCOM 5-7, 7-96 ENDTRANSACTION procedure 5-2 Enform database query 1-5 name reports 1-8 Entering commands accessing other nodes 6-15 AT phrase 6-13, 6-15 combining RESET and ADD commands 6-17 combining RESET and ALTER commands 6-17 Directing output with the
Index EXIT command command file 6-11 EXIT command, DNSCOM 6-11, 7-98 Export process 5-3 Export control file 5-3 Export controller 5-5 EXPORTDELAY attribute, default 6-3 Exporter, name 5-10 Exporting names 5-1 $SYSTEM 5-8 strategy 5-8/10 Exporting node 5-1, 5-7 EXTERNAL attribute default 6-3, 6-4 subsystem-object type definition 4-12 EXTERNAL ON, and OBEYFORM 7-9 F FAST database file 3-8 FAST-GROUP database file 3-8 FC command 7-99 editing DNSCOM commands 6-12 limitations 6-13 FENOTFOUND message A-1 File na
Index G Group defined 2-6 defining 4-30/33 DOMAIN attribute 4-32 member objects of 4-30 MEMBERS attribute 4-31 replication of 4-30 GROUP name, no dependencies 4-4 Group attributes 4-30 GROUP database file 3-8 Group definition dependencies 4-30 what to specify 4-30 Group names, example 1-3 Group names, examples 4-30 Groups hierarchy 4-2, 4-32 nested 4-2, 4-32 GROUPS attribute default 6-4 listed elements 6-17 Guardian DNS dependency 3-1 file names 1-2 H HASMANAGER attribute 4-8, 6-4 default 6-3 in DNSCOM 7-3
Index INFO command accessing other nodes 6-15 DNSCOM 7-10 error 1034 6-18 wildcard symbol (*) 6-14/15 INFO command, DNSCOM 3-13, 4-32, 6-14/15, 6-18 INFO command, general notes 7-9/10 INFO COMPOSITE command, DNSCOM 7-108 INFO COMPOSITETYPE command, DNSCOM 7-110 INFO DNS command, DNSCOM 7-112 INFO DNSDOMAIN command, DNSCOM 7-114 INFO DNSFILE command, DNSCOM 7-116 INFO DNSPROCESS command, DNSCOM 7-118 INFO GROUP command, DNSCOM 7-120 INFO MEMBERS command, DNSCOM 7-123 INFO SS command, DNSCOM 7-125 INFO SSMAN
Index K Key length, configuration file A-1 Key offset, configuration file A-1 Keywords attributes 6-2 command objects 2-1, 6-2 in commands 6-2/5 L Length, of name definitions 4-8 Library procedures 1-8 LIKE phrase ADD command 4-7, 7-8 ALTER command 4-7 copying existing definitions 4-7 creating similar definitions 4-7 general form 7-8 overriding attributes 4-7 overriding set values 7-8 saving time 4-7 SET command 4-7 LIST * command, DNSCOM 7-136 LIST ALIAS command, DNSCOM 7-137 LIST ALIASTYPE command, DNSCO
Index Listed elements ADD command 6-17 adding members 6-16 ALTER command 6-16 deleting members 6-16 entering commands 6-16/17 GROUPS attribute 6-17 RESET command 6-17 SET command 6-17 LOAD DSV file 3-3 LOAD file (ZDNS) 3-6 local definition 4-1 Local system, defined 6-9 Logical file defaults 6-5 Long command line, ampersand (&) 4-7 M Management applications 1-5 Management interface, defined 2-2 Management operations, DNSCOM commands 3-1 Manager, defining 4-12/14 MANAGER attribute, default 6-3, 6-4 MANAGER d
Index MEMBER database file 3-8 Member objects of group 4-30 Members adding 6-16 deleting 6-16 nested 4-2 MEMBERS attribute default 6-4 of a group 4-31 Mode of DNSCOM, operating 6-12 Multiple commands, entering on one line 6-13 Multiple configuration supports 3-2 Multiple domain names, allowed 4-33 N Name alias 2-4 alias type 2-3, 4-18 ambiguous 6-18 composite 2-4 composite type 2-3, 4-14 copied definition 3-12 domain 2-5, 4-33 exporting 5-1 groups 2-6 manager process 2-2 parts of 4-8 replicating 2-6, 5-5 r
Index NAME database file 3-8 Name definition copied 3-12 restored 3-12 Name domain 5-7 Name exporter 3-2, 5-7, 5-10 and the queue file 5-3 and TMF 5-2 configuration file 6-9 defined 5-2 process priority 3-6 replicating names 2-5 Name exporter process, described 1-10 Name manager 3-2 and the queue file 5-3 configuration file 6-9 current 6-7 default 6-7 defined 5-1 OPEN command 6-8 opening 6-7 process priority 3-6 replicating names 2-5 Name manager process, described 1-10 Name resolution 4-26 Names avoiding
Index Node definition 5-1, 5-7, 5-10 exporting 5-1, 5-7 importing 5-1, 5-7 network control 5-1, 5-8/10 Nodes, in domain 2-5 O OBEY command, DNSCOM 6-11, 7-160 OBEY LOAD command, DNSCOM 3-6 OBEYFORM considerations 7-9/10 OBEYFORM parameter ALTER command 7-9 altering name definitions 7-9 and ALTER GROUP 7-9 and SSMANAGER names 7-9 and SSOBJECT names 7-9 and the EXTERNAL ON parameter 7-9 creating name definitions 7-9 purpose 7-9 SET command 7-9 OBEYFORM, copying definitions, examples 7-9 OBEYSYS command, DNSC
Index Objects of commands 6-2 in DNSCOM 2-1 ON as part of a name 4-8 ON phrase, entering commands 6-14 Open default configuration 6-7 initial 3-2 name manager 6-5 specified configuration 6-8 OPEN command changing configuration 6-9 DNSCOM 6-8, 6-9, 7-163 name manager 6-8 Opening name manager 6-7 Operating mode authority 3-11 changing 3-11 definition 3-11, 6-12 selecting 3-4 user 3-11, 6-12 Operational DNSCOM commands 6-1 Operational states of DNS 3-7 Operations with other managers ALTER command 6-15 COPY co
Index P Parameters AT 6-9, 7-8 EXTERNAL ON 7-9 LIKE 7-8 OBEYFORM 7-9 =_DNS_CONFIG 6-9 Parts of DNS name 4-8 actual 4-8 ON 4-8 Percent sign preceding DNS names 7-10, C-1 Planning, for defining DNS names 4-1/2 Primary queue 5-3, 5-5 PRIORITY attribute 6-3 default 6-5 Priority of processes name exporter 3-6 name manager 3-6 Procedure FNAME32COLLAPSE 1-8 FNAME32EXPAND 1-8 FNAME32TOFNAME 1-8 FNAMETOFNAME32 1-8 Process priority name exporter 3-6 name manager 3-6 Processing command files 6-11 PROCESSNAME attribut
Index R RDF (Remote Database Disaster Facility) 5-8 Reacting to system failures 3-12 Read authority 3-9 Recreating a configuration file 3-12 Referent, alias 4-26 REFERENT attribute, default 6-3, 6-4 Reloading DNS database, INFO command 3-13 Remote Database Disaster Facility (RDF) 5-8 Remote system and database 5-10 command processing 6-9 configuration file 6-9 Replicatable definitions 5-8 Replicating names 2-5/6, 5-5 local node 2-5 name exporter 2-5 name manager 2-5 Replicating names, DNS database 5-3 Repl
Index RESET SSMANAGER command, DNSCOM 7-176 RESET SSOBJECT command, DNSCOM 7-177 RESET SSTYPE command, DNSCOM 7-178 Resolution, name 4-26 REST DNSFILE command, DNSCOM 3-4 RESTORE * command, DNSCOM 7-179 RESTORE ALIAS command, DNSCOM 7-180 RESTORE command DNSCOM 6-15 other managers 6-15 RESTORE command, DNSCOM 3-12, 5-7, 5-8 RESTORE COMPOSITE command, DNSCOM 7-182 RESTORE GROUP command, DNSCOM 7-184 RESTORE MEMBERS command, DNSCOM 7-185 Restored name definition 3-12 RFAST database file 3-8 RMAP database fil
Index SECURITY attribute default 6-3 Security attribute 3-9 Security of DNS files in DNSCOM 7-53, 7-135 SELECT command, changing configuration 6-9 SELECT command, DNSCOM 6-9, 7-186 SELECT DEFINITION command, DNSCOM 3-4, 3-11 SELECT DEFINITION command,operating modes 3-11 SELECT DNSCONF command, DNSCOM 3-4 SET ALIAS command, DNSCOM 7-187 SET ALIASTYPE command, DNSCOM 7-190 SET command changing DNS file names, 8 defining attributes 4-6 DNSCOM 3-8, 4-6, 4-7, 6-17, 7-8, 7-9 listed elements 6-17 OBEYFORM parame
Index SHOW GROUP command, DNSCOM 7-228 SHOW SS command, DNSCOM 7-229 SHOW SSMANAGER command, DNSCOM 7-230 SHOW SSOBJECT command, DNSCOM 7-231 SHOW SSTYPE command, DNSCOM 7-232 Similar definitions, LIKE phrase 4-7 Site update tape (SUT) 3-1 SNAX/XF subsystem 1-1 Spaces, in definitions 4-8 SPI subsystem name definition 4-9 SPI (Subsystem Programmatic Interface) 1-5, 5-1 subsystem name definition 4-9 SPI commands 1-7 SSMANAGER names and OBEYFORM 7-9 SSNUM attribute 4-10 default 6-3 SSOBJECT names and OBEYFORM
Index Strategy, defining DNS names 4-1/2 Strategy, distributing names 5-8/10 Strategy, exporting names 5-8/10 Subsystem defining 4-9, 4-10 Subsystem definition, dependencies 4-9 Subsystem manager names 4-14 Subsystem name, defined 2-2 Subsystem names 2-2, 4-10 Subsystem number, subsystem name definition 4-9 Subsystem object 1-1, 2-3 defining 4-20/25 Subsystem Programmatic Interface 5-1 subsystem name definition 4-9 Subsystem Programmatic Interface (SPI) 1-5 Subsystem-controlled object 1-1 Subsystem-object
Index T TACL macros 1-5 TACLCSTM file, =_DNS_CONFIG 6-6, 6-9 TACLLOCL file, =_DNS_CONFIG 6-6, 6-9 Temporary copies of DNS names 5-10 Terminating DNSCOM command, CRTL-Y 6-13 Terminating DNSCOM session, CRTL-Y 6-13 Terminating, command files 6-11 Time savers, in command file 6-11 Time-staged replication 5-7 TMF 5-2 and the export controller 5-5 and the name exporter 5-2 and the queue manager 5-5 backing up files 3-12 BEGINTRANSACTION 5-2 configuration 3-1 DNS dependency 3-1 TMFCOM 3-12 Translating an alias 4
Index U Unavailable nodes, updating definitions 3-12 UNDER phrase, entering commands 6-14 Uniqueness of names 4-8 Untyped alias 2-4, 4-19 multiple 4-19 Update DNSCOM commands 6-1 Updating definitions, unavailable nodes 3-12 Updating the database 3-7 User mod available operations 6-12 User mode security 3-11 Users, defined 1-5 USING phrase, entering commands 6-14 V VOLUME command, DNSCOM 3-4, 7-241 W Warning messages, DNSCOM A-1 Wildcard symbol (*) entering commands 6-14/15 INFO command 6-14/15 Write author
