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 reply is sent
as part of a sequence of replies that identify some of the jobs that
are holding the MVS data set.
This reply can be suppressed by enabling the REPLYSECURITYLEVEL configuration
option.
If FTP is unable to determine which job is holding
the resource, the
asid,
jobname,
accessmode,
and
qname values will be UNKNOWN. Some of the conditions
that can cause FTP to be unable to determine which job is holding
the resource are:
- The resource is being held by a job that is running on another
processor.
- The device on which the data set resides prohibits access to the MVS data set.
In the reply text:
- type
- The type of access that FTP was attempting to obtain. Possible
values are:
- EXCLUSIVE
- FTP requires the exclusive use of the MVS data
set.
- SHARED
- FTP requires the shared use of the MVS data
set.
- dsname
- The name of the MVS data
set being held by another job.
- asid
- The address space identifier of the job holding the MVS data set. If FTP cannot identify the job
that is holding the data set, the asid value is
UNKNOWN.
- jobname
- The job name associated with an address space identifier (ASID)
that is holding the MVS data
set. If FTP cannot identify the job that is holding the data set,
the jobname value is UNKNOWN.
- accessmode
- The way the MVS data set
is being held. Possible values are:
- EXCLUSIVE
- A job is accessing the data set exclusively.
- SHARED
- A job is accessing the data in shared mode.
- UNKNOWN
- FTP is unable to identify the job that is holding the data set.
- qname
- The name of the queue used by the enqueue operation. Possible
values are:
- SPFEDIT
- The queue used by ISPF EDIT, FTP, and other processes when access
to a member of an MVS partitioned
data set is required.
- SYSDSN
- The queue used by z/OS® when
access to an MVS data set is
required.
- UNKNOWN
- FTP cannot identify the job that is holding the data set.
See ISPF or ISPF/PDF in z/OS MVS Planning: Global Resource Serialization for information about how MVS serializes the use of resources and the
use of SPFEDIT.
Example
ftp> get 'USER1.FTPDATA' testing
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 Sending data set USER1.FTPDATA
250 Transfer completed successfully.
System action
The FTP server continues
to try to access the local MVS data
set.
User response
If you need immediate access
to the MVS data set, contact
the system programmer for the FTP server 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 configuration statement 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: Health Checker