Skip to content

[Bug] [module_utils] data_set_exists() does not allow for tmp_hlq  #912

@ddimatos

Description

@ddimatos

Is there an existing issue for this?

  • There are no existing issues.

Are the dependencies a supported version?

  • The dependencies are supported.

IBM Z Open Automation Utilities

v1.2.3

IBM Enterprise Python

v3.9.x

IBM z/OS Ansible core Version

v1.7.0-beta.1

ansible-version

v2.15.x

z/OS version

v2.5

Ansible module

No response

Bug description

When looking over discussion #834 I noticed that the module_utils method data_set_exists() invokes mvscmd and passes commands for it to execute. When mvsmcd/mvscmdauth is invoked where no data sets are provided, mvscmd/mvscmdauth will place the command into a temporary data set on behalf of the caller (ansible). This poses a problem for users who's HLQ are limited.

We currently support tmp_hlq, likely it was overlooked that we needed to pass tmp_hlq when ever mvscmd is used without us passing data sets.

This issue should also perform a quick scan of all code that invokes mvscmd or mvscmdauth to determine if tmp_hlq needs to be passed to the function.

Testing:
This is likely outside the scope of this task (we might need a new issue for this), ideally we should dynamically create a user (omvs segement) with limited privileges that is not permitted to create a HLQ to test this code.

Playbook verbosity output.

No response

Ansible configuration.

No response

Contents of the inventory

No response

Contents of group_vars or host_vars

No response

Metadata

Metadata

Assignees

Labels

BugSomething isn't working as designed.In PlanIssue has been accepted and put into a planned release

Type

No type

Projects

Status

✅ Done

Relationships

None yet

Development

No branches or pull requests

Issue actions