Upgrade SCO 5.0.2 Host to Enterprise with license Post: 302940519

6 More Discussions You Might Find Interesting

1. IP Networking

QNX host cannot ping SCO host, vice versa

The problem I am facing now is that the QNX host could not ping the SCO host and vice versa. They are in the same domain, ie, 172.20.3.xx. As I am very new to Unix, I guess I must have missed out some important steps. Pls help... Thanx alot

2. UNIX for Dummies Questions & Answers

Upgrade SCO openserver

Hi guys i have a unix server SCO 5.0.4 and i'm trying to install and intel pro 100 and for some reason it wont see it , i tried to install a 3 com card and same thing. I know that if i had 5.0.6 it will see any of those cards.my questions is ( if i upgrade to 5.0.6 i have a computone card...

3. SCO

SCO OpenServer 6.0.0 License for Testing

SCO OpenServer 6.0.0 License is required for testing purpose. If anyone have, please help me at the earliest.

4. Shell Programming and Scripting

to check the Linux upgrade in the host

Hi, how to check when was the linux upgrade has been done to this host. below command show the RHEL version. cat /etc/redhat-release Red Hat Enterprise Linux AS release 3 (Taroon Update 6) i want to know when it was upgraded.. is there any command available for that ? or anywhere we...

5. Shell Programming and Scripting

Updating the license tag in XML file with new license

Hi All, I have a XML file : System.xml in which I want to update the license tag with the new data from file licence.xml. The content of files is in following format: System.xml: <?xml version="1.0"?> <!DOCTYPE Configuration SYSTEM "SystemVariables.dtd"> <usageConfiguration...

6. SCO

Looking to Buy SCO Merge 5.3 License

Xinuos (SCO) discontinued Merge 5.3 on 1.31.16. I'm looking to buy from someone their Merge license. Please contact 1234567@optonline.net

LEARN ABOUT HPUX

rlpstat

rlpstat(1M)															       rlpstat(1M)

NAME

       rlpstat - print status of LP spooler requests on a remote system

SYNOPSIS

       printer] user] [id]...

DESCRIPTION

       reports	the status of the specified jobs or all requests associated with the specified users on the specified printer.	At least one id or
       the name of a printer must be specified.

       For each request submitted (by command -- see lp(1)) reports the request ID, user's name, total size of the request, date of  the  request,
       and, if it is being transferred, the device.

       This command is intended to be used only by the spool system in response to the command and should not be invoked directly (see lpstat(1)).

   Options
       recognizes the following options and command-line arguments:

	      Status is requested on the specified printer.

	      Status is requested on all requests for the user who executed the
			     command  on  the  specified  printer (see the option).  You can repeat the option to specify more users.  The maximum
			     number of users that can be specified is 50.

	      id	     Status is requested on the specified request IDs (as returned by All the request IDs must be for  the  same  printer.
			     The maximum number of request IDs that can be specified is 50.

AUTHOR

       was developed by the University of California, Berkeley, and HP.

FILES

SEE ALSO

       enable(1), lp(1), lpadmin(1M), lpsched(1M), lpstat(1), rcancel(1M), rlp(1M), rlpdaemon(1M).

																       rlpstat(1M)