Category Archives: SCO OpenServer

Unlock Terminals in SCO Admin

To unlock a terminal in SCO Admin, following the instructions below:

Login:  root     Password:  superXXX

At the # prompt, type  scoadmin  –>  Use the down arrow key to highlight System  –>  Use the down arrow key to highlight Terminal Manager  –>  Use the right arrow key to highlight Unlock

Type the name of the terminal you wish to unlock – i.e.   ttyp0

You can continue with the same process using the terminal types  ttyp1, ttyp2, ttyp3,  etc.

Once the process is complete. press the ESC key to end

Use the right arrow key to highlight Quit  –>  Press the Enter key and select Yes  –>  Press the TAB  key to File  –>  Press the Enter key to Exit  –>  Select x to go back to the # prompt and press CTRL_D key to return to the login



SCO Unix Samba Password

If  your operating system is SCO Unix and you want a user to have access to the Share, Export, etc. folders on the TOP server,  the command to change the Samba password is:

Login:  root

Password:  ask system supervisor

At the command prompt, type

#  smbpasswd   username   (same login name that is used to login to TOP)

New SMB password:

Retype new SMB password:

#  exit

SCO Unix User Password

If  your operating system is SCO Unix, the command to change the user password is:

Login:  root

Password:  ask system supervisor

At the command prompt, type

#  passwd   username   (same login name that is used to login to TOP)

You can choose whether you pick a password
or have the system create one for you:

1. Pick a password
2. Pronounceable password will be generated for you

Enter New password: choice (default is 1):  Select 1.  Pick a password

Please enter new password:

Re-enter password:

#  exit






Using the WHO Command

Whether your server is running SCO Unix or Red Hat Linux, to see the user names that are logged into your system you can use the who command. Follow the simple procedure below:

Login:  root

Password: XXXXXX (ask system supervisor)

Type in who at the # prompt:

#  who

The name of each user and the number of times they are logged in will display on your screen. To return to your login prompt, type

# exit


How to Cancel User Processes

There are times when a user is working in Total Order Plus and for whatever reason finds themselves being kicked out of TOP. When this happens, there are files left open that will prohibit you from logging back in and returning to your original input.  This can also cause ‘Error 0 – File Device/Record Busy or Inaccessible’ message.

Instead of trying to track which files were open, it is easier to cancel the user processes which will allow the user to enter the same application and close any open files associated with that user.

To cancel an active user process on your system, you must enter the following commands:

Login: root
Password: xxxxxx (ask system supervisor)

Type in the who command to see what users are logged in:
# who

You can view a list of all active users with their TTY, Date and Time of login and the process they are running.


On Red Hat Linux servers, it will also display the IP address of each user.

To view a list of all active processes:
# ps -a

You will be able to see the PID number, the TTY, Time of login and the active process for each user.

To view a list of active processes for just one specific user:

# ps -t ttyxx

The processes for each user is listed on the screen. You must decide what PID number
you want to cancel and what process to cancel for that tty. There are usually multiple
processes running for one user. The process to cancel for Total Order Plus will always
be the Business Basic process (Pro5). You will need that process identification number (PID).

With this information you can enter this command:
# kill  -9  11049 (PID number for BBx)

The system will display a prompt telling you the print job has been cancelled.

To return to the login prompt, type:
# exit

SCO Unix Shutdown Command

Prior to issuing the shutdown command, you must determine if all users have exited back to the SCO login prompt. Just because a workstation has been turned off, it doesn’t necessarily mean that they have logged off properly. To start the system shutdown, enter the following commands:

Login: root

Password: xxxxxx (ask system supervisor)

# who

The system should only display one user being logged in and that should be root. You can re-enter the who command until you see that everyone has logged off properly. When you are ready to continue, issue this command:

# shutdown -g0

Shutdown automatically executes the sync and haltsys command and can allow 0 to 15 minutes before the shutdown takes place, allowing users to complete the work they are doing prior to issuing the shutdown command. The example above (-g0) is for 0 minutes.

The shutdown is complete when you see this prompt:

** Safe To Power Off **


** Press Any Key to Re-Boot **

Press the Enter key to reboot. When the server comes back up, a message like below displays:


Press the Enter key to continue. If the Enter key isn’t pushed after a short period of time, the boot process will automatically continue.

Type CTRL+D keys to proceed with normal startup (or give root password for system maintenance).

Press the Enter key at the system date and time display.

The system will automatically return each workstation to their SCO login prompt.

ALT+CTRL+F1 keys will return the screen to the normal SCO Unix scosysv character login prompt on the server. ALT+CTRL+F3 can be used as a secondary login.


If the system is shutdown incorrectly or loses power while users have data files open, there is a probability of damage being done to records within any given file, causing corrupt file integrity. You must either run a restore procedure from a backup processed before the shutdown or run file rebuild programs to try and correct the errors.


How To Access Your Backup Server

Customers with backup file servers need to make sure their automatic nightly backup is working properly. Weather, electrical outages or spikes, etc. can all affect the main file server and at the same time the backup server. Without checking on the situation at least once a week, there is no guarantee that you data is being transferred.

We recommend that you do a shutdown on the two file servers at least once a month. There is a certain procedure you need to use to shutdown both servers and in this order:

Shutdown the main file server and leave it at the ‘Press Any Key to Reboot’ message  ->   Shutdown the backup server,  ->  Reboot the backup server  ->  Reboot  the main server

To toggle back and forth between the two servers follow these instructions:

Press the Scroll Lock key twice  ->  Press the Up Arrow key to access the backup server login. The message SCO OpenServer Release (top2) will display on the backup server as the login prompt so you know you are on the correct server. You can login as root to do the shutdown from the # prompt.

Press the Scroll Lock key twice -> Press the Down Arrow key to return to the main server.


To see if the data on the backup server is current with the main server, you can login on the backup server and look at invoice history or the date on the Order Entry Menu.

Another way to access the backup server is to login on the main server as root. At the # prompt, enter telnet to get to the backup server login.


Create RecoverEDGE Bootable Media

When BackupEDGE software is installed on your file server for nightly backup procedures, a bootable RecoverEdge DVD is created to be used in case a restore is ever necessary. The media contains the system configuration, printer designations, etc.

Periodically, updates are available from Microlite’s website whenever a new version of the software is released. Once an upgrade is downloaded and upgraded, you need to make a new RecoverEDGE DVD to update the information. It is a good idea to label the DVD with the date it was generated and the label ‘Bootable RecoverEdge Media’.

You receive a nightly backup summary printout. When it is necessary to make new media, you will see this message on the printout ‘RecoverEDGE Media is Out Of Date’. It only takes a few minutes to create the media compared to hours of time that would be needed to configure a new operating system.

Following are the instructions needed to create a RecoverEDGE DVD:

Insert a new DVD disc in the file server
Login to the file server as root -> Type edgemenu at the # prompt
Select Setup on the menu -> Select Make RecoverEDGE Media
Select Boot Media Type (i.e. dvd0, optical0) -> Select Make Media -> Select Continue

Medium Generation Status will display as the media is generated -> Follow the prompts on the screen

Select OK after ‘Bootable Medium Created Successfully’ message is displayed. Make sure to label the DVD ‘BackupEdge Bootable Media’ along with the date. Keep in a safe place.

SCO Unix Print Device Commands

There is a SCO Unix command  lpstat  -t  that will list all of the system print devices. If there are too many devices or print jobs to completely display on the screen, use the command  lpstat  -t |more.

Each print device has a device name and an individual IP address for each one. Each device will show it is accepting requests and whether or not the device is idle , enabled or currently executing a print job.

TOP_PRINTER_MENUThe Total Order Plus printer menu will have the print device name before the description of each printer so you can cross reference the two print device names.

Login as root and enter the system password.

#  lpstat -t |more

If a print device shows disabled, you will be able to see the device name i.e.  ps01 disabled. If there are numerous print jobs listed for the disabled print device, you will need to cancel all of them prior to executing the enable command.

# cancel  -a  ps01

# enable ps01


There are reasons why a print device might be disabled. If a user takes a printer offline during a print job, if a printer is turned off to try and cancel a print job or CUPS (Common UNIX Printing System) will disable a printer if it doesn’t respond after a certain amount of time.

If you want to cancel an individual print job, enter this command:

# cancel ps01-1234  (1234 being the number of the print job)

If you see Network host ‘’  is busy, it usually means the device is not connected to the network. You can execute the following command to test the connection:

# ping

If the device is connected, you will see the data packets that are transmitted and received.

PING 56 data bytes
64 bytes from ( icmp_seq=0 ttl=60 time=150 ms
64 bytes from ( icmp_seq=1 ttl=60 time=101 ms

— ping statistics —
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 101/125/150 ms