Z Open Automation Utilities

Showing 35

Create tape datasets from Python API to ZOAU

In zOS there are two types of hardware datasets, the datasets that exist on Direct Access Devices (DISKs) and datasets that exist on TAPES. Data in datasets can be too large to be housed on DISKs, so the datasets are put on Tapes so that they don'...

9 months ago in Z Open Automation Utilities 0 Future consideration

7 VOTE

ZOAU zIIP eligibility

We're using Python on Z and ansible-collections/ibm_zos_core with zoau under the hood for increasingly large portions of our z/OS CI workload.While Python, in which ibm_zos_core written, is zIIP eligible, we suspect that zoau's modules are not (ou...

about 2 months ago in Z Open Automation Utilities 0 Submitted

6 VOTE

ZOAU interface with SDSF

Just as with REXX one can use the SDSF REXX API to access any/all information from SDSF so should ZOAU be able to do the same. There is so much information available via SDSF that could be useful to the ZOAU user.

2 months ago in Z Open Automation Utilities 0 Needs more information

11 VOTE

Add support to zoautil_py.datasets & zoautil_py.zoau_io to be given a DD as parameter

Add support to zoautil_py.datasets & zoautil_py.zoau_io to be given a DD as parameter, instead of having to hardcode the dataset name: In the JCL: //DDIN DD DSN=XXXX.YYYY.ZZZZ,DISP=SHR In the Python code: datasets.read('//DDIN') instead of: da...

4 months ago in Z Open Automation Utilities 0 Needs more information

9 VOTE

Improvement for the zos_copy / ibm_zos_core collections module (based on ZOAU’s dcp utility)

For our Ansible-based deployment solution, we use the zos_copy module from the ibm_zos_core collection (version 1.8.0). We note the absence of ISPF statistics on our PDS and this is particularly penalizing for our PARMLIBs. The objective of this p...

4 months ago in Z Open Automation Utilities 1 Future consideration

3 VOTE

z/OS Ansible Collection zos_operator: add a wrapper for the opercmd 'console' parameter

The 'console' parameter for the opercmd shell command and python API allow us to specify a suffix for the EMCS console name that is generated. I need this functionality to be exposed in the zos_operator module.

about 1 month ago in Z Open Automation Utilities 1 Under review

4 VOTE

dinfo command should not require a volume parameter as all our datasets are catalogued

The dinfo command should not require a volume parameter as all our datasets are catalogued. Should be able to issue this command: dinfo -u @02858.t.cntl …instead of this one: dls -l @02858.t.cntl | awk '{print $1, $NF}' | xargs dinfo -u to list: @...

2 months ago in Z Open Automation Utilities 0 Submitted

5 VOTE

Add LIKE capability to dtouch

Add a new optional parameter to dtouch shell command (and corresponding Python API) called --like (or maybe --model) which takes the name of an existing dataset. This argument would override (and could be specified completely in lieu of) other all...

3 months ago in Z Open Automation Utilities 0 Future consideration

2 VOTE

Provide ENQ / DEQ services

We are migrating Rexx code to Python, some of our Rexx code calls a Module that issues ENQ / DEQ to serialize some processing against other ZOS processes running. We would like to issue an ENQ/DEQ from Python through a ZOAU function.

about 1 month ago in Z Open Automation Utilities 0 Submitted

3 VOTE

dls should list all dataset types (including VSAM) by default (not just non-VSAM/GDGs) along with including the VSAM dataset type when using -T

dls should list all dataset types (including VSAM) by default (not just non-VSAM/GDGs) along with including the VSAM dataset type when using -T dls xxxxxxxx.** dls will only list all VSAM datasets using the -t option, but the dls man page does not...

2 months ago in Z Open Automation Utilities 0 Planned for future release

Shape the future of IBM!

Search existing ideas

Post your ideas

Specific links you will want to bookmark for future use