Closed ddimatos closed 3 months ago
Relates to issue #1254
This error message doesn't come from zos_copy but rather from zos_data_set. The issue comes from a call to DataSet.delete_member()
which only zos_data_set uses. You can see the task Create a MEMBER
is the one failing in your playbook.
Recreating the scenario but skipping the initial zos_data_set tasks gives me the correct error message.
Is there an existing issue for this?
Are the dependencies a supported version?
IBM Z Open Automation Utilities
v1.2.5
IBM Enterprise Python
v3.11.x
IBM z/OS Ansible core Version
v1.8.0-beta.1
ansible-version
latest
z/OS version
None
Ansible module
zos_copy
Bug description
When the playbook tasks the member TEST1, I then went into ISPF and edited the PDSE and ran again (obtain lock), in this second run, I expected a message that would tell me the data set has a lock on it and to use force_lock if an operation need to be done on a data set held by a long running process. Instead what I received while not invalid, It feels out of sequence. Maybe I should be told first that force_lock needs to be enabled?
I expected:
Playbook verbosity output.
No response
Ansible configuration.
No response
Contents of the inventory
No response
Contents of
group_vars
orhost_vars
No response