1 delete Use the delete command to delete an entity or an instance of an entity. As with create, most entities support the delete command; however, some entities are deleted automatically by software, and so do not support the delete command. For example, entities that correspond to communications links are usually deleted dynamically as these links are closed. You cannot delete an entity if it has child entities; you must delete all child entities before you can delete the parent entity. It is usually, though not always, the case that you must disable an entity before you can delete it. 2 alias_(OpenVMS) Deletes the alias module. delete [node node-id] alias 3 Exception_Messages o module enabled Disable the alias entity before trying to delete it. 3 port delete [node node-id] alias port port-name NOTE Disable routing before manually deleting an alias port. Example: delete alias port dec:.lkg.bulean 4 Exception_messages o cannot delete the entity while it is enabled Disable the alias port entity before trying to delete it. 2 csma-cd delete [node node-id] csma-cd 3 Exception_Messages o has children (Tru64 UNIX) Cannot delete while subentities exist. o cannot delete while subentities exist (OpenVMS) Cannot delete while csma station subentities exist. 3 station delete [node node-id] csma-cd station station-name Example: delete csma station csmacd-1 4 Exception_Messages o station in use (Tru64 UNIX) Attempt to delete the csma-cd station entity failed because there is at least one active port still associated with this station. You must wait until the ports go away to delete this station. o wrong state The csma-cd station must be disabled before deletion. 2 ddcmp_(OpenVMS_VAX) delete [node node-id] ddcmp 3 link delete [node node-id] ddcmp link link-name Example: delete ddcmp link ddcmp-0 4 Exception_Messages o Cannot delete while subentities exist. Cannot delete the link until its logical station subentities have been disabled and deleted. o wrong state The link must be disabled before deletion. 4 logical_station delete [node node-id] ddcmp link link-name - logical station station-name Example: delete ddcmp link ddcmp-0 logical station ddcmp-0 5 Exception_Messages o wrong state The logical station must be disabled before deletion. 2 device delete [node node-id] device 3 Exception_Messages o has children Cannot delete while subentities exist. 3 unit delete [node node-id] device unit simple-name 2 dns 3 clerk delete [node node-id] dns clerk Deletes the DECdns clerk on the specified node. You must disable a clerk before you delete it (see the disable command). You can also enter this command through the dns$control utility. You must have the NET$MANAGE rights identifier (OpenVMS systems) or superuser privileges (Tru64 Unix systems). 4 known_namespace delete [node node-id] dns clerk - known namespace namespace-ident Removes a namespace from a specified clerk's list of known namespaces. The namespace-identifier is required. You can use one of the following: name The name of the namespace. The name argument may be different from the nickname if the nickname is ambiguous. nscts The value of the namespace creation timestamp (NSCTS) assigned to the specified namespace when it was created. The format is 14 pairs of hex digits (xx-xx). You must have the NET$MANAGE rights identifier (OpenVMS systems) or superuser privileges (Tru64 Unix systems). NOTE You are not permitted to delete the known namespace that is currently the default namespace (that is, the one shown by show dns clerk default namespace). The following command removes the namespace with the name jns from the clerk's list of known namespaces. delete dns clerk known namespace jns 4 manual_nameserver delete [node node-id] dns clerk - manual nameserver name Removes the knowledge of a server that exists across a WAN from the local clerk's cache. You can also enter this command through the dns$control utility. You must have the NET$MANAGE rights identifier (OpenVMS systems) or superuser privileges (Tru64 Unix systems). The following command removes knowledge of server nrl from the clerk cache on node .mfg.umbriel: delete node .mfg.umbriel dns clerk manual nameserver nrl 3 server delete [node node-id] dns server Deletes the DECdns server on the specified node and reclaims all server resources except clearinghouses, which remain. You must disable a server before you can delete it. You can also enter this command through the dns$control utility. You must have the NET$MANAGE rights identifier (OpenVMS systems) or superuser privileges (Tru64 Unix systems). The following command deletes the DECdns server from node .mfg.polaris: delete node .mfg.polaris dns server 4 clearinghouse delete [node node-id] dns server clearinghouse clearinghouse-name Deletes a clearinghouse on the specified node. You must disable a clearinghouse before you can delete it. You can also enter this command through the dns$control utility. This command also automatically deletes all read-only replicas from the clearinghouse when executed. DECdns does not permit you to delete a clearinghouse that contains a master replica. You must have delete access to the directories in the clearinghouse as well as to the clearinghouse. You must have the NET$MANAGE rights identifier (OpenVMS systems) or superuser privileges (Tru64 Unix systems). The following command deletes a clearinghouse named .sales.ny_ch from the node .sales.orion. delete node .sales.orion dns server clearinghouse .sales.ny_ch 2 dtss delete [node node-id] dtss 2 event_dispatcher 3 outbound_stream delete [node node-id] event dispatcher - outbound stream simple-name Example: delete event dispatcher outbound stream local_stream 4 Exception_Messages o wrong state The operation failed because the entity was not in an off state. 3 relay delete [node node-id] event dispatcher relay 4 Exception_Messages o entity has children Cannot delete while subentities exist. o wrong state The relay must be disabled before deletion. 3 sink delete [node node-id] event dispatcher sink simple-name Example: delete event dispatcher sink local_sink 4 Exception_Messages o has children Cannot delete while subentities exist. o wrong state The sink must be disabled before deletion. 2 fddi delete [node node-id] fddi 3 Exception_Messages o has children Cannot delete while subentities exist. FDDI Stations must be disabled and deleted before the FDDI module can be deleted. 3 station delete [node node-id] fddi station station-name Example: delete fddi station fddi-1 4 Exception_Messages o wrong state The station must be disabled before deletion. 2 frame_(OpenVMS) delete [node node-id] frame 3 link delete [node node-id] frame link frame-link-id Example: delete frame link frame-0 2 hdlc delete [node node-id] hdlc 3 link delete [node node-id] hdlc link link-name Example: delete hdlc link hdlc-0 4 Exception_Messages o wrong state The logical station must be disabled before deletion. o has children Cannot delete while subentities exist. The Logical Station subentities must be disabled and deleted before this link can be deleted. o link enabled The link is still enabled. Disable the link and reissue the delete command. 4 logical_station delete [node node-id] hdlc link link-name - logical station logical-station-name Example: delete hdlc link hdlc-0 logical station hdlc-0 2 lapb delete [node node-id] lapb 3 link delete [node node-id] lapb link simple-name Example: delete lapb link link-0 2 llc2 delete [node node-id] llc2 3 sap delete [node node-id] llc2 sap simple-name Example: delete llc2 sap sap-0 4 link delete [node node-id] llc2 sap simple-name - link simple-name Example: delete llc2 sap sap-0 link dte-1 2 modem_connect delete [node node-id] modem connect 3 Exception_Messages o has children The modem connect entity has subentities. You must delete these subentities before you can delete the modem connect entity. 3 line delete [node node-id] modem connect line line-name Example: delete modem connect line DSY-0-0 2 mop delete [node node-id] mop 3 Exception_Messages o has children Cannot delete while subentities exist. MOP Client Circuits and Clients must be deleted before the MOP Module can be deleted. 3 circuit delete [node node-id] mop circuit circuit-name Example: delete mop circuit csmacd-1 4 Exception_Messages o has children Cannot delete while MOP Circuit Operation or Station subentities exist. 3 client delete [node node-id] mop client client-name Example: delete mop client lamchp 2 nsp delete [node node-id] nsp 3 Exception_Messages o Wrong State You cannot delete the entity while it is enabled. 2 osak Deletes an OSAK entity and reclaims the resources associated with it. The entity must be in the NotAvailable state before it can be deleted. delete [node node-id] osak 3 Exception_Messages o subentity exists Cannot delete while subentities exist. o wrong state The osak entity is in the wrong state for the command you have tried to use on it. The text accompanying the exception message specifies which command has failed. 3 application_(OpenVMS) delete [node node-id] osak application "presentation address" Example: delete osak application "'0001'H/'0001'H/'0004'H/NS+21,CLNS" 4 Exception_Messages o wrong state Disable the osak application before trying to delete it. 4 invocation_(OpenVMS) delete [node node-id] osak - application "presentation address" - invocation invocation-identifier Example: delete osak application "'0001'H/'0001'H/'0004'H/NS+21,CLNS" - invocation [AP_Invocation = -1, AE_Invocation = -1] 5 Exception_Messages o wrong state You cannot delete an osak application invocation entity when it still has open ports. 2 osi_transport delete [node node-id] osi transport 3 Exception_Messages o wrong state Disable the osi transport entity before trying to delete it. 3 application_(OpenVMS) delete [node node-id] osi transport application application-name Example: delete osi transport application osit$ivp 3 template delete [node node-id] osi transport template template-id Example: delete osi transport template osit$rfc1006 4 Exception_Messages o cannot delete default template Attempt to delete the osi transport template entity failed because the template named Default cannot be deleted. 2 routing delete [node node-id] routing 3 Exception_Messages o wrong state Routing module cannot be deleted when it is enabled. o has children Cannot delete while subentities exist. 3 circuit delete [node node-id] routing circuit circuit-name Example: delete routing circuit csmacd-1 4 adjacency delete [node node-id] routing circuit circuit-name - adjacency adjacency-name Example: delete routing circuit csmacd-1 adjacency RTG$0001 5 Exception_Messages o deletion not permitted An attempt has been made to delete an automatic adjacency, or an adjacency on a circuit that is not a dynamically assigned X.25 circuit. 4 reachable_address delete [node node-id] routing circuit circuit-name - reachable address simple-name Example: delete routing circuit csmacd-1 reachable address to-bulean 3 egp_group delete [node node-id] routing egp group group-name 4 egp_neighbor delete [node node-id] routing egp group group-name - egp neighbor neighbor-name 3 permitted_neighbor delete [node node-id] routing permitted neighbor neighbor-name 2 session_control Supported only on Tru64 UNIX: delete [node node-id] session control 3 Exception_Messages o wrong state Disable the session control entity before trying to delete it. 3 application delete [node node-id] session control - application application-name Example: delete session control application SMISERVER 3 backtranslation_softlink Removes a backtranslation softlink subentity from the session control database on the specified node. delete [node node-id] session control - backtranslation softlink softlinkname Note that this command does NOT remove the softlink from the DECdns namespace, which may be done using the DNS$CONTROL. The softlink must be removed from the DECdns namespace in order to prevent other nodes from using this backtranslation. In other words, until the softlink is corrected in the DECdns namespace, other nodes may use this backtranslation softlink, thus associating this address with the wrong target node. Example: delete session control backtranslation softlink - ! Represents DEC:.DNA_BACKTRANSLATION.%X49.%X0004.%XAA0004007413 ! DECnet ! address 24.36 delete session control backtranslation softlink - ! On OpenVMS only, DEC:.DNA_BACKTRANSLATION.%XA1725E3E ! deletes the ! softlink for ! IP address ! 161.114.94.62 3 port delete [node node id] session control port port-name Example: delete session control port SCL$PORT$1202002C 3 proxy_(Tru64_UNIX) delete [node node-id] session control proxy name Name is a simple name assigned to a particular entity instance. The name is the management identifier for the proxy database entry and is kept unique among the entries in this database maintained by Session Control. 3 tower_maintenance delete [node node-id] session control tower maintenance fullname Example: delete session control tower maintenance DEC:.LKG.FALSE 3 transport_service delete [node node-id] session control - transport service transport-name Examples: delete session control transport service OSI delete session control transport service NSP 4 Exception_Message o wrong state (Tru64 UNIX) This entity cannot be deleted while there are connections using this transport. 2 token_ring_(Tru64_UNIX) delete [node node-id] token ring 3 Exception_Messages o has children Cannot delete while subentities exist. 3 station delete [node node-id] token ring station station-name 4 Exception_Messages o wrong state Failure to delete the token ring station entity because the station must be disabled before deletion. 4 FA_map delete [node node-id] token ring station station-name - FA map famap-id 4 source_route delete [node node-id] token ring station station-name - source route sourceroute-id 2 x25_access delete [node node-id] x25 access 3 application delete [node node-id] x25 access application application-name Example: delete x25 access application X25_MAIL 3 dte_class delete [node node-id] x25 access dte class class-name Example: delete x25 access dte class REMOTE-CLASS-0 4 Exception_Messages o inbound DTE class The DTE Class is referenced by an enabled DTE. 3 filter delete [node node-id] x25 access filter filter-name Example: delete x25 access filter X29 3 reachable_address delete [node node-id] x25 access reachable address address-name Example: delete x25 access reachable address x121 3 security_dte_class delete [node node-id] x25 access security dte class class-name 4 remote_dte delete [node node-id] x25 access - security dte class class-name - remote dte dte-name 3 security_filter delete [node node-id] x25 access - security filter filter-name Example: delete x25 access security filter APPL_APPLICATION_0 3 template delete [node node-id] x25 access template template-name Example: delete x25 access template TEMPLATE-0 2 x25_client_(OpenVMS) delete [node node-id] x25 client 2 x25_protocol delete [node node-id] x25 protocol 3 dte delete [node node-id] x25 protocol dte dte-name Example: delete x25 protocol dte dte-0 4 pvc delete [node node-id] x25 protocol - dte dte-name pvc pvc-name Example: delete x25 protocol dte dte-0 pvc PVC-0 3 group delete [node node-id] x25 protocol group group-name Example: delete x25 protocol group GROUP-0 4 Exception_Messages o referenced dte enabled One or more of the DTEs referenced by this group is still enabled. 2 x25_relay_(Alpha) delete [node node-id] x25 relay 3 client delete [node node-id] x25 relay client client-name 4 Exception_Messages o has active connections One or more active connections exist on this client. 3 pvc delete [node node-id] x25 relay pvc pvc-name 2 x25_server delete [node node-id] x25 server 3 client delete [node node-id] x25 server client simple-name 3 security_nodes delete [node node-id] x25 server - security nodes simple-name 2 xot_(OpenVMS_Alpha) Deletes the X.25 Over TCP/IP (XOT) module. delete [node node-id] xot Before the XOT module can be deleted, all of its associated SAPs and LINKs must be disabled and deleted. Example: show xot sap * state ! To find all SAPs and their states show xot sap sap-0 link * state ! To find all links for a SAP disable xot sap sap-0 link link-0 ! All links must be disabled/deleted delete xot sap sap-0 link link-0 disable xot sap sap-0 ! All SAPs must be disabled/deleted delete xot sap sap-0 delete xot ! Before XOT itself can be deleted 3 Exception_Messages o has children The XOT module cannot be deleted when it has active subentities. 3 sap Deletes a disabled Service Access Point (SAP) entity. Sap-name is a simple name that uniquely identifies a particular SAP instance. delete [node node-id] xot sap sap-name Before a SAP can be deleted, all of its associated LINK entities must be disabled and deleted. Example: show xot sap * - local ip addr, state ! Identifies the sap to delete. show xot sap sap-0 link * ! There can be no link subentities disable xot sap sap-0 ! and SAP must be disabled delete xot sap sap-0 ! before the SAP can be deleted. 4 link Deletes a previously disabled LINK entity, which represents a remote system with which XOT is allowed to communicate. The sap-name and link-name are simple names which uniquely identify particular SAP and LINK instances. delete [node node-id] xot sap sap-name link link-name Example: show xot sap sap-0 link * - ! Finds link to delete. remote ip address, state disable xot sap sap-0 link link-0 ! LINK must be disabled delete xot sap sap-0 link link-0 ! before deletion. 5 Exception_messages o wrong state The XOT SAP LINK entity must be disabled before it can be deleted. 4 Exception_Messages o wrong state The XOT SAP entity must be disabled before it can be deleted. o has children The XOT SAP entity cannot be deleted when it has LINK subentities.