Tips from Abroad: Printing Container Login Scripts in NetWare 5, Using ? and Echo On Commands in NCF files, and Making DS Tunable Parameters Persistent
Articles and Tips: tip
01 Sep 2000
Looks at printing container login scripts, using ? and Echo On commands in NCF files, making DS tunable parameters persistent, gathering NLM property information from Windows NT workstations, verifying server-assigned IP addresses, and installation tips for the CodeWarrior PDK.
Novell UK Ltd.
Printing Container Login Scripts
You can use the following NLIST command to get a copy of the container login scripts. To do this, perform the following:
NLIST "ORGANIZATIONAL UNIT" unitname SHOW "LOGIN SCRIPT"
Replace unitname with the name of the Organizational Unit for which you want the login script. Be sure to set your context above the Organizational Unit whose login script you want to print. You can use the Greater Than sign ( > ) to redirect the output to a text file.
Prompts in NCF Files
You can use the DOS "?" and "echo on" commands in the AUTOEXEC.NCF file, or in any .NCF file, to create user prompts.
The "Echo On" command performs as it does under DOS; that is, it will print the results of the commands to the server console screen.
Much more interesting is the "?" command, which creates a Yes/No prompt. Users can press <Enter> to accept the default answer of Yes (Y), or they can change the prompt to N for No. The ? command gives you 10 seconds to respond to the stated command. If you do not react in that time frame, the command will be carried out. For example, the command
? load ne2000 ....
presents the following at the server console prompt:
load ne2000 ? Y
After 10 seconds, if the user hasn't typed "N", the command will load the ne2000 driver.
Making DS Tunable Parameters Persistent
Tunable DS parameters, such as those that are displayable through commands like "Set dstrace=*p", should be persistent in NetWare 5. For example, suppose you want to change the size of the SMI Cache Setting and you want the new cache setting to stay at that value after the server reboots. When you modify those settings, they are supposed to be written to the SYS:\_NETWARE\_NDSDB.INI file.
However, I've seen several NetWare 5.1/NDS 8 server installations where the _NDSDB.INI file exists as a directory rather than a file, so the parameters you are seeking to make persistent never get properly saved. The solution to this problem is to remove that directory (by using SENLM.NLM) and then set the DS parameter again. This time the _NDSDB.INI file should then be created, holding the persistent DS parameters.
* Originally published in Novell AppNotes
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.