| 134 | |
| 135 | === Controlling Retries done by WMS === |
| 136 | |
| 137 | After the job has been submitted to WMS, WMS goes through several phases until final submission of the job to the CE. For various reasons, errors can occured at each stage and a user can control the number of retries WMS must do through 2 JDL attributes: |
| 138 | * `RetryCount`: defines the maximum number the WMS try to process a job in case of an error occured inside the WMS. Default is site specific and there is a maximum defined on the WMS itself. |
| 139 | * `ShallowRetryCount`: defines the maximum number the WMS try to submit a job to the selected CE in case of an error occured on the CE. Default is site specific and there is a maximum defined on the WMS itself. |
| 140 | |
| 141 | Until the maximum attempt has been reached the job never reached the state 'Done'. |
| 142 | |
| 143 | ''Note: when debugging jobs, it is often desirable to set `RetryCount` and `ShallowRetryCount` to 0 to get a quick feedback in case of errors.'' |
| 144 | |
| 145 | === Some Other Useful JDL Attributes === |
| 146 | |
| 147 | JDL files accept many [http://server11.infn.it/workload-grid/docs/DataGrid-01-NOT-0101-0_6-Note.pdf different attributes]. In addition to those already described, a few other useful attributes are: |