Command  Home
Scalable Graphic

Soft - is your software and documentation
Asset - is something that must be protected
Management - is what we do
Enterprise - is the capability
Computing - is the power
Services - are what we provide


A.    Process one or more shipping orders on the local host and send the associated packets or files to remote sites.

B.    TCP/IP connection

To transmit a file, shipping_server uses UDP to contact the albd_server process on the receiving host, and albd_server invokes shipping_server in receive mode on the receiving host. If you are sending packets through a firewall (that is, the CLEARCASE_MIN_PORT and CLEARCASE_MAX_PORT environment variables are set), shipping_server tries to use TCP to contact the remote albd_server. If that connection fails, shipping_server uses UDP. For more information read about using store-and-forward through a firewall in the "Choosing a transport method" chapter of IBM Rational ClearCase MultiSite Administrator's Guide. On Linux and the UNIX system, shipping_server forks one subprocess for each packet that it sends. As many as 10 shipping_server subprocesses, each trying to send a single packet, can be started for each invocation of shipping_server. The same number of subprocesses are forked on the receiving machine. As a subprocess finishes, another can be started, but only 10 can run simultaneously. After a TCP connection is established between the two shipping_server processes, they transfer the file. The receiving shipping_server selects a storage bay using the configuration settings in the shipping.conf file (Linux and the UNIX system) or MultiSite Control Panel (Windows). If a storage class is assigned multiple storage bays, available disk space determines the selection of a bay.

On Linux and the UNIX system, the packet file is created with the same owner and group as the storage bay directory, and its access mode is taken from the directory's read and write permissions. (The execute permission and special permissions, if any, are ignored.)

On Windows, the packet file inherits permissions from the Windows ACL on the storage bay directory.

Colon characters in packet names

If a packet name contains a colon ( : ), shipping_server changes the colon to a period ( . ) during processing. This change allows packets to be delivered to Windows machines, which do not allow colons in file names.

Handling of file name conflicts

You can use the mkorder and shipping_server commands to transmit nonpacket files if the files are in the same directory as their associated shipping orders. If a file with the same name already exists on the receiving host, the new file is renamed to filename_1 (if you send another file with the same name, it is renamed to filename_2, and so on).

Setting a timeout period for unreachable hosts

You can set a timeout period during which the shipping server will not try to send packets to hosts that it previously identified as unreachable. For more information, see the shipping.conf (Linux and the UNIX system) or MultiSite Control Panel (Windows) reference page.


On Linux and the UNIX system, shipping_server writes records of all packets sent and received, along with all errors, to file /var/adm/rational/clearcase/log/shipping_server_log.

On Windows, shipping_server writes records of all packets sent and received, notification messages, log messages, and all errors to the Windows Event Viewer. You can use the cleartool getlog shipping command to view shipping_server messages from the Event Viewer.

C.    Restrictions

Identities: You must have write and execute permissions on the directory containing the shipping order. On Linux and the UNIX system, you must own the data file or be root.

Locks: No locks apply.

Mastership: No mastership restrictions.

Other: The shipping order and the data file it specifies must be located in the same directory.

D.    One or more pathnames of files or directories. Each file you specify is processed if it contains a valid shipping order. For each directory you specify, shipping_server processes some (if you use –sclass) or all shipping orders stored in that directory.

E.    Processes shipping orders located in some (if you use –sclass) or all storage and return bays defined in the shipping.conf file on Linux and the UNIX system or the MultiSite Control Panel on Windows.  Note: shipping_server processes only shipping orders whose file names start with the characters sh_o_. If you create shipping orders, name them according to this convention, or omit the –poll option and specify the shipping order pathnames.  On Linux and the UNIX system, only shipping order files that you own are processed. However, when root runs this program, shipping order files are processed regardless of ownership.

Table of Contents

Table of Contents. 1

How do I use the cleartool ln command.. 1

1.       to list link to a previously deleted directory.. 1

2.       to create a VOB hard link (build.c) as another name for element (samecs.c) 2

3.       to create a VOB symbolic link (build.c) pointing to an element (samecs.c) 2

4.       to create a group of hard links in the build directory for all .h files in the current working directory. 3

5.       to create a VOB symbolic link in the checked-in directory version \vobs_hw@@\main\3 that points to hello.c in the current working directory. 3


How do I use the MultiSite shipping_server command

Note: <no output means command succeeded or did not find any shipping orders>

1.   to process all shipping orders in all MultiSite storage bays on the local host:


/opt/rational/clearcase/rhat_x86/etc/shipping_server  -poll


2.   to process a particular shipping order on the local host:




3.   to process all shipping ordersin the storage bays of a specified storage class:


/opt/rational/clearcase/rhat_x86/etc/shipping_server –poll –sclass daily


4.   to process all shipping order files in a specified directory.

/opt/rational/clearcase/rhat_x86/etc/shipping_server var/adm/rational/clearcase/shipping/ms_ship/outgoing


This website is published "as is". There is no warranty of any kind (express or implied) as to the operation of our site, the accuracy of the information or the services or products referred to on it. All warranties are excluded as far as permitted at law. Neither we nor any third party will be liable for any losses or damage that may result from use of the website or as a consequence of any inaccuracies in, or any omissions from, the information which it contains.