The Storage Resource Manager Interface Specification Version 2.2 24 May 2008 Collaboration Web: http://sdm.lbl.gov/srm-wg Document Location: http://sdm.lbl.gov/srm-wg/doc/SRM.v2.2.html Editors: Alex Sim Lawrence Berkeley National Laboratory Arie Shoshani Lawrence Berkeley National Laboratory Authors/Contributors: Paolo Badino Olof Barring Jean-Philippe Baud Flavia Donno Maarten Litmaath European Organization for Nuclear Research (CERN), Switzerland Timur Perelmutov Don Petravick Fermi National Accelerator Laboratory (FNAL), USA Ezio Corso Luca Magnoni International Centre for Theoretical Physics (ICTO), Italy Istituto Nazionale di Fisica Nucleare (INFN), Italy Junmin Gu Lawrence Berkeley National Laboratory (LBNL), USA De Witt Jens Jensen Rutherford Appleton Laboratory (RAL), England Michael Haddox-Schatz Bryan Hess Andy Kowalski Chip Watson Thomas Jefferson National Accelerator Facility USA of Contents
The requested file with the SURL is being used by other clients. SRM_FILE_UNAVAILABLE the requested file with the SURL is temporarily unavailable. SRM_FAILURE file request is failed. any other request failure. Explanation needs to be filled for details. srmStatusOfChangeSpaceForFilesRequest This function is used to check the status of the previous request to srmChangeSpaceForFiles, when asynchronous operation was necessary in the SRM. Request token must have been provided in response to the srmChangeSpaceForFiles. Parameters In: string authorizationID, string requestToken Out: TReturnStatus returnStatus, int estimatedProcessingTime, TSURLReturnStatus [] arrayOfFileStatuses Notes on the Behavior When space transition is completed successfully, SRM_SUCCESS must be returned for each SURL. If changing space is not completed, estimateProcessingTimemay be returned when known. If all files are still in the queue and none of the files are completed in changing space, the returned status code must be SRM_REQUEST_QUEUED. If some files are queued, and some files are completed in changing space, SRM_REQUEST_INPROGRESS must be returned as the return status code. Each file must have its own status code. If the target space is only large enough to transfer a subset of the files, the request will continue taking place until the target space cannot hold any more files, and the request must be failed. The status of the request must return an error of SRM_EXCEED_ALLOCATION in such case. Return Status Code For request level return status, SRM_SUCCESS All file requests are successfully completed. All SURLs have new targetSpaceToken. SRM_PARTIAL_SUCCESS All requests are completed. Some SURL requests have new targetSpaceToken, and some SURL requests are failed to have new targetSpaceToken. Details are on the status. SRM_ REQUEST_QUEUED Request submission is successful and the entire request is still on the queue. SRM_ REQUEST_INPROGRESS Some files are still queued, and some files are completed in space transition.
All requests are successfully completed. All source SURLs are copied into the target destination successfully. SRM_PARTIAL_SUCCESS All requests are completed. Some file request is successfully copied into the target destination, and some file request is failed. Details are on the files status. SRM_AUTHENTICATION_FAILURE SRM fails to authenticate the client SRM_AUTHORIZATION_FAILURE client is not authorized to submit the request Client is not authorized to copy into the space that client provided with targetSpaceToken or targetFileRetentionPolicyInfo SRM_INVALID_REQUEST If both parameters targetSpaceToken and TRetentionPolicyInfo are provided, then their types must match exactly. targetSpaceToken does not to an existing known space in the SRM. SRM_SPACE_LIFETIME_EXPIRED space associated with the targetSpaceToken is expired. SRM_EXCEED_ALLOCATION space associated with the targetSpaceToken is not enough to hold all requested SURLs. SRM_NO_USER_SPACE user space is not enough to hold all requested SURLs. SRM_NO_FREE_SPACE SRM is not enough to hold all requested SURLs for free. SRM_INTERNAL_ERROR SRM has an internal transient and client may try again. SRM_NOT_SUPPORTED SRM does not support the input parameters. For example, client requestsdesiredFileStorageType that is not supported by the SRM. targetFileRetentionPolicyInfo does not refer to a supported retention policy in the SRM. Directory operation is not supported in the SRM. Recursive directory operation is not supported in the SRM. A specified input parameter is not supported in the SRM. function is not supported in the SRM. SRM_FAILURE all files requests are failed. any other request failure. Explanation needs to be filled for details. For file level return status, SRM_SUCCESS successful request completion for the file. The sourceSURL is copied into the target destination targetSURL successfully, and lifetime on the targetSURL is started. SRM_REQUEST_QUEUED file request is on the SRM_REQUEST_INPROGRESS file request is being served. SRM_FILE_LOST the request file (sourceSURL) is permanently lost.