Title: | DECmcc user notes file. Does not replace IPMT. |
Notice: | Use IPMT for problems. Newsletter location in note 6187 |
Moderator: | TAEC::BEROUD |
Created: | Mon Aug 21 1989 |
Last Modified: | Wed Jun 04 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 6497 |
Total number of notes: | 27359 |
I have a quick question with the use of the POPLULATE DIRECTIVE. In the Documentation it mentions that you can use wildcard for the ENTITY NAME. ie. MCC> POPULATE DOMAIN domain-identifier SELECT LIST = (NODE4 .dnsdir.*) Can you have a variation of that and wildcard part of the entity name. eg. MCC> POPULATE DOMAIN domain-identifier SELECT LIST = (NODE4 .dnsdir.VAX*) I have issued the command which it accepts OK, but it populates the whole directory and basically ignores the fact that I prefixed it with VAX. The main idea was to select nodes/stations from a particular domain/DNS directory starting with a string and populate it to another domain. Thanks, Niguel Brooks (SNO CSC )
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1852.1 | Not a supported wildcard syntax in V1.1 | TOOK::A_MOORE | Tue Dec 31 1991 14:03 | 9 | |
For DECmcc V1.1 partial wildcard support is for DNS directories only. The wildcard is substituted for the last simple name only. SELECT LIST = (NODE4 .dnsdir.VAX*) is not supported in V1.1. It should have been rejected. Namespace services for V1.2 has expanded the wildcard features. That command works for DNS namespace for EFT T1.2. It is not working for Local MIR namespaces on VMS or Ultrix for EFT T1.2-4. That is QARed. Al |