To display a list of slcp command options, enter the sclp command with no arguments, as shown in this example:

# slcp 


<Enter>
slcp: usage
 -d H|h|c|p|x|q|u[,#]|n[,node]|s[,service]
 -b s,device,service[,”id”][,port][,password][,rating]
 -b c,device,service[,node][,port][,password]
 -b h,device[,service][,node][,port]
 -B device|\* Delete touch device binding (\* delete all)
 -c [cpu_rating][,user_limit] Set cpu rating, user limit
 -f Save LAT configuration to /usr/etc/lat/latconfig
 -m sessions Set maximum LAT sessions (0 no limit, 1-255)
 -n [node][,”id”] Set local node name, description
 -g [a|i,]#[,#...]|[,#-#] Set ACL[a] or IDL[i]groups         (default both)
 -G [a|i,]#[,#...]|[,#-#] Clear ACL[a] or IDL[i] groups (default both)
 -Q sequence|\* Delete queue sequence # (\* delete all)
 -r service,rating Set local service rating
 -t seconds Set service announcement timer (10-180 sec)
 -u service,unit Assign unit (minor #) to service
 -U service,unit Remove unit (minor #) from service
 -X Purge unknown, unreachable nodes, services
 -Z [c][n[,node]] Zero host [c] and/or node [n] counters

An slcp command consists of the keyword slcp and a command switch. The switch is a letter preceded by a hyphen (-). For example, this is the slcp command to purge the LAT database of unavailable nodes and services:

slcp -X

Most slcp commands require at least one argument. For example, this slcp command to set the maximum number of sessions on a service node requires a maximum sessions argument:

slcp -m max_sessions 

Some slcp commands take several arguments. The slcp commands with multiple arguments have this syntax:

slcp -switch argument[,argument][,argument][,argument]

When a command contains more than one argument, separate the arguments with a comma (,); include commas as space holders whenever you omit an argument from the arguments list. Do not include spaces between arguments. For example, this command assigns a service rating to a LAT service:

slcp -r IRIS2,250 

By default, the 4DLT installation procedure assigns the IRIX system the host name that appears in the IRIX file /etc/sys_id. You can change the default node name for the IRIX system if you wish. However, if your system is a member of multiple networks, it will be easier to maintain the system if it uses the same name on all networks.

---

Note: Changing the LAT node name on the IRIS host does not affect its name on other networks.

---

To change your IRIS system's LAT node name or desciption, use the slcp -n command:

# slcp -n new_name[,description] 


<Enter>

The arguments to slcp -n have these meanings:

slcp -n lily,“engineering node for testing”

LAT service nodes use their CPU rating as one factor in calculating dynamic service ratings. The slcp -c command lets you assign a fixed CPU rating to an IRIS node to weight its chances of being selected for a service. If you do not assign a CPU rating, a rating is assigned dynamically by 4DLT software.

The slcp -c command also lets you set a limit on the total number of LAT users concurrently using the IRIS system. This option allows you to manage the LAT load on the node by restricting user access (also see “Setting a Maximum on LAT Login Sessions”).

To set the CPU rating and user limit on an IRIS system, use the slcp -c command:

# slcp -c cpu_rating[,user_limit] <Enter>

Arguments to slcp -c have these meanings:

The 4DLT installation process sets the maximum number of LAT login sessions to zero (0). The zero value means there is no limit to the number of LAT sessions the IRIS system will accept. Use the slcp -m command to reset the limit to a value in the range of 1 to 255:

# slcp -m max_sessions 


<Enter>

By default, service nodes multicast service announcements every 60 seconds. To change the multicast interval, use the slcp -t command:

# slcp -t number_of_seconds <Enter>

The argument to the slcp -t command has this meaning:

Service ratings provide terminal servers a gauge for selecting a particular service when multiple hosts are offering the service (see “LAT Service Ratings”). You can assign either a dynamic or static service rating to a login service.

Dynamic ratings are calculated by latd on the provider node each time it broadcasts the service. Static ratings in the range of 0 to 255 are assigned by the LAT administrator. Assigning a higher rating makes the service more likely to be selected by a terminal server; assigning a lower rating makes the service less likely to be selected.

Use the slcp -r command to set a service rating:

# slcp -r service_name,rating 


<Enter>

The arguments to the slcp -r command have these meanings:

The 4DLT installation process creates 256 IRIX devices specifically for LAT services, ttyl and ttyl1 through ttyl255. When a local LAT service is created, a specified LAT device is designated for the service (see “Adding Logins to the latservice File” and “Adding Printers to the latservice File”). When this device is opened, the LAT service is automatically bound to the device for the duration of the session.

You can manually bind a LAT device to a LAT service (for diagnostic purposes, for example) using the slcp -b command. The slcp -b command takes separate arguments for binding to printer services ( -h) and non-printer services ( -c).

---

Note: When you bind to a device, choose one in the middle of the ttyl1 to ttyl255 range (see “How Printing Works” for information on reserved device numbers).

---

slcp -b c,device,service[,node][,port][,password]

# slcp -b c,ttyl162,date

The samples below illustrate records in a LAT services file:

LOGN:Accounting:Login for accounting staff:
PRNT:ttyl124:Colorcopy:*:*:
LOGN:Payroll:13:*:big_$$:
LOGN:Email:-1:Login for electronic mail:

The sample records would establish four services during a 4DLT startup:

To add a login record to the /usr/etc/lat/latservice file, use the svc_setup -l command. The command has this syntax:

# svc_setup -lservice_name [-rrating] [-iidentification] [-apassword]

The arguments to svc_setup -l have these meanings:

When the svc_setup -l command finishes executing, /usr/etc/lat/latservice contains a new record for the login service you added (see “A Sample latservice File” for sample login records). The service will be advertised after you stop and restart the LAT daemon (see “Stopping and Restarting 4DLT” for instructions).

To remove a login record from the /usr/etc/lat/latservice file, use the svc_setup -L command. The command has this syntax:

# svc_setup -L service_name

When the svc_setup -L command finishes executing, the record for the login service that you specified is removed from the latservice file. However, you must stop and restart the LAT daemon to stop advertising this login service (see “Stopping and Restarting 4DLT” for instructions).

To add a printer service record to the /usr/etc/lat/latservice file, use the svc_setup -p command. The command has this syntax:

# svc_setup -pprinter_name -dttylnum -mmodel -sservice [-nnode] [-tport]

The arguments to svc_setup -p have these meanings:

When the svc_setup -p command finishes executing, /usr/etc/lat/latservice contains a new record for the printer service you added (see “A Sample latservice File” for sample printer records). The LAT printer service is available immediately to the IRIX system user; you do not need to stop and restart the LAT daemon.

To remove a print service record from the /usr/etc/lat/latservice file, start the svc_setup utility with the -P option. The command has this syntax:

# svc_setup -Pprinter_name -dttylnum

When the svc_setup -P command finishes executing, the record for the print service that you specified is removed from the latservice file and the printer is no longer available to the IRIS user; you do not need to stop and restart the LAT daemon to remove the service.

The slcp -g command assigns ACL and IDL group codes on an IRIS system. The codes are maintained in the volatile database (they lose their effect when you stop and restart 4DLT). If you assign ACL group codes, incoming service requests will be required to contain a matching group code in order to use the requested service. If you assign IDL group codes, the codes will be forwarded in the IRIS user's request for services and matched with the group codes for the provider node.

The slcp -g command has this syntax:

slcp -g a|i group_code[,group_code]|[start_range-end_range] 

The arguments to the slcp -g command have these meanings:

For example, this command assigns the group codes 7 and 15 to service announcements leaving an IRIS host:

slcp -g a 7,15 

This example assigns a range of group codes, from 8 to 12, to all user requests for service leaving the IRIS system:

slcp -g i 8,12 

Although group codes are not part of the permanent database, you can automate the assignment of ACL and IDL information by specifying them in the IRIS system's /etc/rc2.d/S31lat file (slcp commands are not required). These parameters are read and put into effect each time latd is started from a system reboot.

Use this procedure to reset the default group codes from zero (0) to group codes used on your network. The LAT daemon must be running when you do this procedure, and you must do it as the root user of the IRIS system:

After you complete this procedure, the IRIS system will send out the ACL codes you specified in its service announcements, and it will include the IDL group codes you specified in its connection requests to other LAT nodes.

Some parameters you can change with slcp are also parameters in the permanent database, /usr/etc/lat/latconfig. To record changes you make with slcp in the latconfig file, use this command:

# slcp -f 


<Enter>

When this command completes, any changes you made to settings in the permanent database using slcp commands are recorded in /usr/etc/lat/latconfig.

When the terminal server is unable to establish a connection to a LAT node or service, it marks the node unreachable and the service unknown in the LAT database. Unavailable nodes and services and their status continue to be posted in displays, unless you have specified otherwise (see “Setting Learned Service Parameters”).

By default, 4DLT purges unreachable nodes and unknown services every five hours, removing them from all displays. slcp allows you to purge this information on an as-needed basis.

To purge the LAT database, use this command:

# slcp -X


 <Enter>

If any new information arrives after the database is purged, the new information is entered in the database in the usual manner.