srmcp now supports performance of SRM transfers in both SRM version 1. protocol and in SRM version 2.1.1 protocol You need to specify --srm_protocol_version=2 option as an argument of srmcp in order to activate version 2.

srmcp product also contains the following SRM version 2.1.1 clients: srmls, srmrm, srmmv, srmkdir and srmrmdir Please run these commands with --help to see usage info.

Added several new command line options: gss_expected_name, globus_tcp_port_range, streams_num, and server_mode. Please find the details in the section called “The SRM Client Suite”.

Added new command srmstage to provide an option to the user to stage files from HSM to dCache and not transfer them to the user right away. This case will be useful if files are not needed right away at user end, but its good to stage them to dcache for faster access later:

Made srmcp script more robust. In previous versions,it is assumed that the Java binary exists and is in the user $PATH. In this current version, script looks for java in various standard locations and under $JAVA_HOME if defined. In case of multiple Java versions found, the most recent version is selected.

Ensure reliable srmcp return codes. The return code is 0 only if all individual file transfers are successful. In case of any failure the return code is 1.