Explanation
A client issued an FTP subcommand that required
access to a local MVS™ data set
name. The local MVS data set
name is being held by one or more jobs.
This message might
be issued as a sequence of EZZ9819I messages that identify some of
the jobs that are holding the MVS data
set.
If FTP is unable to identify the job that is holding
the data set, the
as_id,
jobname,
access_mode,
and
q_name values are UNKNOWN. The following conditions
that can cause FTP to be unable to identify the job.
- The data set 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.
See the IPSF or ISPF/PDF information
in z/OS MVS Planning: Global Resource Serialization for information about how MVS serializes the use of resources.
In
the message text:
- type
- The type of access that FTP was attempting to obtain. Possible
values are:
- EXCLUSIVE
- FTP requires exclusive use of the MVS data
set.
- SHARED
- FTP requires shared use of the MVS data
set.
- ds_name
- The name of the local MVS data
set that is being held by another job.
- as_id
- The address space identifier of the job that is holding the local MVS data set. If FTP is unable to
identify the job that is holding the data set, the as_id value
is UNKNOWN.
- jobname
- The job that is holding the local MVS data
set. If FTP is unable to identify the job that is holding the data
set, the jobname value is UNKNOWN.
- access_mode
- 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.
- q_name
- The name of the queue used by z/OS® to
control access to MVS data set.
If FTP is unable to identify the job that is holding the data set,
the q_name value is UNKNOWN. The following are
the most likely queue names.
- SPFEDIT
- The queue is used by FTP when access to a member of an MVS partitioned data set is required.
- SYSDSN
- The queue is used by z/OS when
access to an MVS data set is
required.
System action
The FTP client continues to try to access the
local MVS data set.
Operator response
System programmer response
Perform the following steps:
- Use the information in the EZA9819I and EZA9820I messages to determine
which job or jobs are holding the MVS data
set and resolve the contention.
- Purge or cancel the job that is causing the MVS data set contention, if appropriate.
User response
If you need immediate access to the MVS data set, contact the system programmer
and provide the sequence of EZA9819I and EZA9820I messages.
Problem determination
Source
z/OS Communications
Server TCP/IP: FTP
Module
Routing code
Descriptor code
Automation
Not applicable for automation.
Example
EZA1459I NAME (9.42.104.19:USER1):
user1
EZA1701I >>> USER user1
331 Send password please.
EZA1789I PASSWORD:
EZA1701I >>> PASS
230 USER1 is logged on. Working directory is "USER1.".
EZA1460I Command:
get 'user.example' 'user1.testfile'
EZA9819I FTP unable to obtain SHARED use of USER1.TESTFILE which is held by:
005C MYJOB EXCLUSIVE ON SYSDSN
EZA9820I Data set access will be retried in 1 minute intervals - 1 attempts remaining
EZA9819I FTP unable to obtain SHARED use of USER1.TESTFILE which is held by:
005C MYJOB EXCLUSIVE ON SYSDSN
EZA2562W Allocation of USER1.TESTFILE failed (error code 0210 info code 0000 S99ER
SN 00000000)
EZA2799W The data set is allocated to another job and is unavailable.
EZA1460I Command: