125: Data set `dsname` is not available

Explanation

The FTP server received an FTP command that required access to an MVS™ data set name that is being held by one or more jobs. This is the closing reply for a sequence of 125- replies. The sequence identifies the jobs that are holding the MVS data set, and the number of MVS data set access attempts that remain. The FTP server attempted to access an MVS data set in approximately 1-minute intervals for the amount of time specified in the DSWAITTIME statement in the FTP server FTP.DATA file. The contention for the MVS data set could not be resolved and the command is rejected.

In the reply text:

dsname: The name of the MVS data set that is not available because it is held by other jobs.

Example

get 'user1.ftpdata' testfile
 EZA1701I >>> PORT 127,0,0,1,4,5
 200 Port request OK.
 EZA1701I >>> RETR 'user1.ftpdata'
200 Port request OK. 
125-FTP Server unable to obtain SHARED use of USER1.FTPDATA which is held by: 005C MYJOB EXCLUSIVE SYSDSN
125-Data set access will be retried in 1 minute intervals - 1 attempts remaining
125 Data set USER1.FTPDATA is not available
450 Data set USER1.FTPDATA is allocated to another job and is unavailable for RETR command.
EZA1460I Command:

System action

The file transfer fails and processing continues.

User response

Do one of the following actions:

Use the STAT command to determine the DSWAITTIME value for this session from the FTP server perspective. Use the SITE command to change the DSWAITTIME value and try the file transfer again. For example, from the z/OS® FTP client, issue the following subcommand to set the total time to wait for the MVS data set to become available to 10 minutes:
```
SITE DSWAITTIME=10
```
See the information about using the STAT subcommand and SIte subcommand in z/OS Communications Server: IP User's Guide and Commands and the DSWAITTIME statement in z/OS Communications Server: IP Configuration Reference.
Transfer the file when the MVS data set is available.
If you need immediate access to the MVS data set, contact the system programmer and provide the sequence of 125- replies

System programmer response

Perform the following actions:

Use the information in the 125- replies to determine which job or jobs are holding the MVS data set and resolve the contention.
Purge or cancel the job causing the MVS data set contention, if appropriate.
Modify the DSWAITTIME in your FTP.DATA file based on your end-user requirements, and recycle the FTP server for the change to take effect for new FTP sessions.

Problem determination

None.

Source

z/OS Communications Server TCP/IP: FTP

125: Data set dsname is not available