Nebraska packages a small set of extensions to the dCache SRM clients.  These allow the user to use SRM much in the same manner as FTS.

Installation

To install the clients, first install the latest dCache SRM client from DESY.  Currently, the link is:

rpm -i http://www.dcache.org/downloads/1.8.0/dcache-srmclient-1.8.0-4.noarch.rpm

One should always make sure to keep on top of the latest patch releases.  Next, check out the dCacheNebraska code:

svn co svn://t2.unl.edu/brian/dCacheNebraska

There are no prepackaged tarballs currently available.  Next, set the DCACHENEBRASKA_HOME environment variable and PATH:

export DCACHENEBRASKA_HOME=$PWD/dCacheNebraska
export PATH=$PATH:$DCACHENEBRASKA_HOME/scripts

This should put srm-transfer-list, srm-transfer-submit, and srm-transfer-cancel in your path.

Usage

srm-transfer-submit

srm-transfer-submit submits a transfer; make sure to use the -2 flag:

$ srm-transfer-submit -srm_protocol_version=2 srm://srm.unl.edu:8443/srm/managerv2?SFN=/pnfs/unl.edu/data4/testfile.unl.brian srm://srm.unl.edu:8443/srm/managerv2?SFN=/pnfs/unl.edu/data4/testfile.unl.brian_client_test
-2147232098

The syntax is:

srm-transfer-submit -2 <from SURL> <to SURL>

It should return quickly; the only output with debug turned off is the request ID.

srm-transfer-status

srm-transfer-status looks up the status of a particular transfer:

$srm-transfer-status -2 srm://srm.unl.edu:8443/srm/managerv2 -2147244134
SRM_SUCCESS

The syntax is:

srm-transfer-status -2 <SRM endpoint> <request ID>

srm-transfer-list

srm-transfer-list looks up all the request IDs for your DN.  It does not print out the state of these transfers!

srm-transfer-list -2 srm://srm.unl.edu:8443/srm/managerv2
Request token=-2147232194 Created=null
Request token=-2147232168 Created=null
Request token=-2147232227 Created=null
Request token=-2147232384 Created=null
Request token=-2147232166 Created=null
Request token=-2147232200 Created=null
Request token=-2147232206 Created=null
Request token=-2147232455 Created=null
Request token=-2147232367 Created=null
Request token=-2147232128 Created=null
Request token=-2147232390 Created=null
Request token=-2147232192 Created=null
Request token=-2147232219 Created=null
Request token=-2147232457 Created=null

The syntax is:

srm-transfer-list -2 <SRM endpoint>

Note that this is not necessarily the same thing as glite-transfer-list -- there's no status information (it's not built into the SRM protocol).  If status information is needed, I recommend writing a wrapper script around srm-transfer-list and srm-transfer-status.

srm-transfer-cancel

srm-transfer-cancel aborts a given transfer.

$ srm-transfer-cancel -2 srm://srm.unl.edu:8443/srm/managerv2 -2147244134

(there is no output in case of success; just check the exit code).
The syntax is:

srm-transfer-cancel -2 <SRM endpoint> <request ID>

SRM Status Codes

Status Code Table

Status Code	Interpretation
SRM_SUCCESS	File transfer has completed successfully.
SRM_REQUEST_QUEUED	File transfer has been accepted and is sitting in the queue.
SRM_REQUEST_INPROGRESS	File transfer has been accepted and is running.
SRM_PARTIAL_SUCCESS	All files have been completed.  At least one of the files have completed successfully, but not all are done.
SRM_AUTHENTICATION_FAILURE SRM_AUTHORIZATION_FAILURE	There was a problem with authZ/authN; usually this happens during the initial submission.  Fatal error.
SRM_INVALID_REQUEST	The request ID was incorrect, or the request does not belong to this user.  Fatal error.
SRM_SPACE_LIFETIME_EXPIRED SRM_EXCEED_ALLOCATION SRM_NO_USER_SPACE SRM_NO_FREE_SPACE	There was a problem with the space reservation or reserving space on the site for this transfer; the transfer will not succeed.
SRM_INTERNAL_ERROR	There was an unknown problem in the server, possibly transient.  Try again later.
SRM_NOT_SUPPORTED	The SRM server does not support srmCopy mode (most implementations do; only DPM currently does not support this), and the tools listed on this page will not work with the site
SRM_FAILURE	All files in the request have failed.

Status Code Comments

Explicitly, the following states are all final states after a file transfer was attempted:

• SRM_SUCESS
• SRM_PARTIAL_SUCCESS
• SRM_FAILURE

The following are permanent failures which occur prior to data transfers:

• SRM_AUTHENTICATION_FAILURE
• SRM_AUTHORIZATION_FAILURE
• SRM_INVALID_REQUEST
• SRM_SPACE_LIFETIME_EXPIRED
• SRM_EXCEED_ALLOCATION
• SRM_NO_USER_SPACE
• SRM_NO_FREE_SPACE
• SRM_NOT_SUPPORTED

The following is a transient error state (try again later):

• SRM_INTERNAL_ERROR