SRM-LS-STATUS: BeStMan SRM-Client Tools User's Guide

srm-ls-status checks the status of previously submitted srm-ls request with the returned request token.

Usage

-authid <string>	Authorization ID to be used in SRM for the request
-conf <path>	Path to the configuration file. Command line options will override the options from conf file
-connectiontimeout <int>	enforces http connection timeout in the given seconds. Default=1800
-count <int>	Specifies count in case there are too many listing Default=0
-debug	Specifies debugging output Default=false
-delegation <true¶false>	Force proxy delegation. When not provided, srm-ls-status makes no delegation by default. When -delegation is provided, it overrides the automatic handling and forces the user choice.
-help	Show the help message
-log <path>	Specifies path to log file Default=./srmclient-event-date-random.log
-offset <int>	Specifies offset in case there are too many listing Default=0
-proxyfile <path>	Path to user grid proxy
-quiet	Suppress output in the console. This option writes the output to the log file. Default=false
-renewproxy	Enables automatic proxy renewal upon expiration Works only when -usercert and -userkey are provided Prompts for the pass phrase Default=false
-requesttoken <string>	Request token from the successful results from srm-ls
-serviceurl <endpoint>	Full web service endpoint Required when source url or target url does not contain web service endpoint information
-sethttptimeout <int>	set client-side http connection timeout in the given seconds. Default=600
-usercert <path>	Path to user grid certificate
-userkey <path>	Path to user grid certificate key

srm-ls-status makes no proxy delegation by default. A user can override the automatic handling by providing an option “-delegation” (or “-delegation true”) to force the delegation, and “-delegation false” to force no delegation. “-debug” option would show how the delegation is done on the output.

This command retrieves the status of the previously requested LS request. Click here for the sample output.

srm-ls-status LS_TOKEN_1234 -serviceurl srm://bestman.lbl.gov:8443/srm/v2/server

When a large LS status is expected to be returned, the srm-ls-status may not handle status information into the memory. It is mostlikely because the memory size of the java virtual machine. In such case, you can increase the size of the virtual machine in srm-ls-status by -Xmx###M, where # is the amount of memory which you want to allocate in megabytes. E.g. java –Xmx512M
For memory conscious jobs, “-lite” option is provided to use less memory to handle the user request. The option the passes -Xms32M to the virtual machine.