Skip to content

Releases: ansible-collections/ibm_zos_core

release-v1.13.1

21 May 16:27
9c0fe68
Compare
Choose a tag to compare

Version 1.13.1

Bugfixes

  • zos_data_set

    • Module would fail with TypeError when trying to replace an existing GDG. Fix now allows the replacement of an existing GDG.
    • Module would fail when trying to delete a non-existent Generation Data Group. Fix now provides a successful response with changed=false.

Availability

  • Ansible Automation Platform
  • Galaxy
  • GitHub

Known Issues

  • zos_job_submit - when setting 'location' to 'local' and not specifying the from and to encoding, the modules defaults are not read leaving the file in its original encoding; explicitly set the encodings instead of relying on the default.
  • zos_job_submit - when submitting JCL, the response value returned for byte_count is incorrect.
  • zos_apf - When trying to remove a library that contains the '$' character in the name for an APF(authorized program facility), the operation might fail.
  • zos_copy - Copying from a sequential data set that is in use will result in a false positive and destination data set will be empty. The same is true when type=gdg and source GDS is a sequential data set in use.

Build:
ibm-ibm_zos_core-1.13.0.tar.gz

release-v1.14.0-beta.1

01 May 15:47
a2c1f48
Compare
Choose a tag to compare

Version 1.14.0-beta.1

Minor Changes

  • zos_copy

    • Adds large as a choice for type in dest_data_set.
    • Adds logging of Jinja rendered template content when use_template is true and verbosity level -vvv is used.
    • Adds support for copying in asynchronous mode inside playbooks.
    • Removes the need to allow READ access to MVS.MCSOPER.ZOAU to execute the module by changing how the module checks if a data set is locked.
  • zos_job_output - Add execution_time return value in the modules response.

  • zos_job_query

    • Add execution_time return value in the modules response.
    • Loads correct bytes size value for dds when using zoau 1.3.4 or later
    • System and Subsystem are now retrieved from JES.
  • zos_job_submit

    • Adds logging of Jinja rendered template content when use_template is true and verbosity level -vvv is used.
    • Add execution_time return value in the modules response.
    • Loads correct bytes size value for dds when using zoau 1.3.4 or later.
  • zos_script

    • Adds error message for when remote source does not exist.
    • Adds logging of Jinja rendered template content when use_template is true and verbosity level -vvv is used.
    • Adds support for running local and remote scripts in asynchronous mode inside playbooks.
    • Support automatic removal of carriage return line breaks [CR, CRLF] when copying local files to USS.
  • zos_stat - Adds support to query data sets using their aliases.

  • zos_unarchive - Adds support for unarchiving files in asynchronous mode inside playbooks.

  • zos_zfs_resize - Adds validations for trace destination dataset used for trace verbose.

Bugfixes

  • zos_apf - When trying to add a library into the APF list that was already added, the module would fail. Fix now will not fail the module, and will inform the user that the library is already on the APF list.

  • zos_copy

    • Previously, if the dataset name included special characters such as $, validation would fail when force_lock was false. This has been changed to allow the use of special characters when force_lock option is false. - When asa_text was set to true at the same time as force_lock, a copy would fail saying the destination was already in use. Fix now opens destination data sets up with disposition SHR when force_lock and asa_text are set to true.
    • the carriage return characters were being removed from only first 1024 bytes of a file. Now fixed that issue to support removal of the carriage return characters from the complete file content if the file size is more than 1024 bytes.
  • zos_data_set

    • Module would fail when trying to delete a non-existent Generation Data Group. Fix now provides a successful response with changed=false.
    • Module would fail with TypeError when trying to replace an existing GDG. Fix now allows to replacing a GDG.
  • zos_job_output - When searching for a job name, module performed a '*' (find all), then filtered the results. Fix now asks for specific job name, making the return faster and more precise.

  • zos_job_query - When searching for a job name, module performed a '*' (find all), then filtered the results. Fix now asks for specific job name, making the return faster and more precise.

  • zos_job_submit - When searching for a job name, module performed a '*' (find all), then filtered the results. Fix now asks for specific job name, making the return faster and more precise.

  • zos_mount - Module failed when using persistent option with a data set that contains non UTF-8 characters. Fix now can use a data set with non UTF-8 characters as data_store.

New Modules

  • ibm.ibm_zos_core.zos_stat - Retrieve facts from MVS data sets, USS files, aggregates and generation data groups.

Availability

  • Galaxy
  • GitHub

Known Issues

  • zos_copy - Copying from a sequential data set that is in use will result in a false positive and destination data set will be empty. The same is true when type=gdg and source GDS is a sequential data set in use.

ibm-ibm_zos_core-1.14.0-beta.1.tar.gz

release-v1.13.0

31 Mar 18:13
e7ffe6d
Compare
Choose a tag to compare

Version 1.13.0

Minor Changes

  • zos_copy

    • Added new option autoescape to template_parameters, allowing users to disable autoescaping of common XML/HTML characters when working with Jinja templates.
    • Adds error message when a PDS/E source member does not exist or is not cataloged.
  • zos_job_submit

    • Add deploy and forget capability. Now when wait_time_s is 0, the module will submit the job and will not wait to get the job details or content, returning only the job id.
    • Added new option autoescape to template_parameters, allowing users to disable autoescaping of common XML/HTML characters when working with Jinja templates.
    • Added support to run zos_job_submit tasks in async mode inside playbooks.
  • zos_mvs_raw - Added max_rc option. Now when the user sets max_rc, the module tolerates the failure if the return code is smaller than the max_rc specified, however, return value changed will be False if the program return code is not 0.

  • zos_script - Added new option autoescape to template_parameters, allowing users to disable autoescaping of common XML/HTML characters when working with Jinja templates.

Bugfixes

  • zos_copy

    • Improve module zos_copy error handling when the user does not have universal access authority set to UACC(READ) for SAF Profile 'MVS.MCSOPER.ZOAU' and SAF Class OPERCMDS. The module now handles the exception and returns an informative message.
    • Previously, if the dataset name included special characters such as $, validation would fail when force_lock was false. This has been changed to allow the use of special characters when force_lock option is false.
    • Previously, if the dataset name included special characters such as $ and asa_text option is true, the module would fail. Fix now allows the use of special characters in the data set name when asa_text option is true.
    • When asa_text was set to true at the same time as force_lock, a copy would fail saying the destination was already in use. Fix now opens destination data sets up with disposition SHR when force_lock and asa_text are set to true.
  • zos_fetch - Some relative paths were not accepted as a parameter e.g. C(files/fetched_file). Change now allows the user to use different types of relative paths as a parameter.

  • zos_find

    • Module would not find VSAM data and index resource types. Fix now finds the data and index resource types.
    • Module would not find a VSAM cluster resource type if it was in use with DISP=OLD. Fix now finds the VSAM cluster.
  • zos_job_query - Module was not returning values for system and subsystem. Fix now returns these values.

  • zos_mvs_raw

    • If a program failed with a non-zero return code and verbose was false, the module would succeed. Whereas, if the program failed and verbose was true the module would fail. Fix now has a consistent behavior and fails in both cases.
    • Module would not populate stderr return value. Fix now populates stderr in return values.
    • Module would obfuscate the return code from the program when failing returning 8 instead. Fix now returns the proper return code from the program.
    • Module would return the stderr content in stdout when verbose was true and return code was 0. Fix now does not replace stdout content with stderr.
    • Option tmp_hlq was not being used as HLQ when creating backup data sets. Fix now uses tmp_hlq as HLQ for backup data sets.
  • zos_script - When the user trying to run a remote script had execute permissions but wasn't owner of the file, the module would fail while trying to change permissions on it. Fix now ensures the module first checks if the user can execute the script and only try to change permissions when necessary.

New Modules

  • ibm.ibm_zos_core.zos_zfs_resize - Resize a zfs data set.

Availability

  • Ansible Automation Platform
  • Galaxy
  • GitHub

Known Issues

  • zos_job_submit - when setting 'location' to 'local' and not specifying the from and to encoding, the modules defaults are not read leaving the file in its original encoding; explicitly set the encodings instead of relying on the default.
  • zos_job_submit - when submitting JCL, the response value returned for byte_count is incorrect.
  • zos_apf - When trying to remove a library that contains the '$' character in the name for an APF(authorized program facility), the operation might fail.
  • zos_copy - Copying from a sequential data set that is in use will result in a false positive and destination data set will be empty. The same is true when type=gdg and source GDS is a sequential data set in use.

Release v1.13.0 Build
ibm-ibm_zos_core-1.13.0.tar.gz

release-v1.12.1

28 Feb 16:21
0580ffd
Compare
Choose a tag to compare

Version 1.12.1

Bugfixes

  • zos_copy

    • Previously, if the dataset name included special characters such as $ and asa_text option is true, the module would fail. Fix now allows the use of special characters in the data set name when asa_text option is true.
    • Previously, if the dataset name included special characters such as $, validation would fail when force_lock was false. This has been changed to allow the use of special characters when force_lock option is false.
    • When asa_text was set to true at the same time as force_lock, a copy would fail saying the destination was already in use. Fix now opens destination data sets up with disposition SHR when force_lock and asa_text are set to true.

Availability

  • Automation Hub
  • Galaxy
  • GitHub

Requirements

The IBM z/OS core collection has several dependencies, please review the z/OS core support matrix to understand both the
control node and z/OS managed node dependencies.

Known Issues

  • zos_job_submit - when setting 'location' to 'local' and not specifying the from and to encoding, the modules defaults are not read leaving the file in its original encoding; explicitly set the encodings instead of relying on the default.
  • zos_job_submit - when submitting JCL, the response value returned for byte_count is incorrect.
  • zos_apf - When trying to remove a library that contains the '$' character in the name for an APF(authorized program facility), the operation will fail.

ibm-ibm_zos_core-1.12.1.tar.gz

release-v1.13.0-beta.1

05 Feb 22:33
3bb4331
Compare
Choose a tag to compare

Version 1.13.0-beta.1

Minor Changes

  • zos_copy

    • Added new option autoescape to template_parameters, allowing users to disable autoescaping of common XML/HTML characters when working with Jinja templates.
    • Adds error message when a PDS/E source member does not exist or is not cataloged.
  • zos_job_submit

    • Add deploy and forget capability. Now when wait_time_s is 0, the module will submit the job and will not wait to get the job details or content, returning only the job id.
    • Added new option autoescape to template_parameters, allowing users to disable autoescaping of common XML/HTML characters when working with Jinja templates.
    • Added support to run zos_job_submit tasks in async mode inside playbooks.
  • zos_mvs_raw - Added max_rc option. Now when the user sets max_rc, the module tolerates the failure if the return code is smaller than the max_rc specified, however, return value changed will be False if the program return code is not 0.

  • zos_script - Added new option autoescape to template_parameters, allowing users to disable autoescaping of common XML/HTML characters when working with Jinja templates.

Bugfixes

  • zos_copy - Improve module zos_copy error handling when the user does not have universal access authority set to UACC(READ) for SAF Profile 'MVS.MCSOPER.ZOAU' and SAF Class OPERCMDS. The module now handles the exception and returns an informative message.

  • zos_fetch - Some relative paths were not accepted as a parameter e.g.files/fetched_file. Change now allows the user to use different types of relative paths as a parameter.

  • zos_find

    • Module would not find VSAM data and index resource types. Fix now finds the data and index resource types.
    • Module would not find a VSAM cluster resource type if it was in use with DISP=OLD. Fix now finds the VSAM cluster.
  • zos_job_query - Module was not returning values for system and subsystem. Fix now returns these values.

  • zos_mvs_raw

    • If a program failed with a non-zero return code and verbose was false, the module would succeed. Whereas, if the program failed and verbose was true the module would fail. Fix now has a consistent behavior and fails in both cases.
    • Module would not populate stderr return value. Fix now populates stderr in return values.
    • Module would obfuscate the return code from the program when failing returning 8 instead. Fix now returns the proper return code from the program.
    • Module would return the stderr content in stdout when verbose was true and return code was 0. Fix now does not replace stdout content with stderr.
    • Option tmp_hlq was not being used as HLQ when creating backup data sets. Fix now uses tmp_hlq as HLQ for backup data sets.
  • zos_script - When the user trying to run a remote script had execute permissions but wasn't owner of the file, the module would fail while trying to change permissions on it. Fix now ensures the module first checks if the user can execute the script and only try to change permissions when necessary.

New Modules

  • ibm.ibm_zos_core.zos_zfs_resize - Resize a zfs data set.

Availability

  • Galaxy
  • GitHub

Requirements

The IBM z/OS core collection has several dependencies, please review the z/OS core support matrix to understand both the
control node and z/OS managed node dependencies.

Known Issues

  • zos_job_submit - when setting 'location' to 'local' and not specifying the from and to encoding, the modules defaults are not read leaving the file in its original encoding; explicitly set the encodings instead of relying on the default.
  • zos_job_submit - when submitting JCL, the response value returned for byte_count is incorrect.
  • zos_apf - When trying to remove a library that contains the '$' character in the name for an APF(authorized program facility), the operation will fail.

release-v1.12.0

09 Dec 16:20
c032672
Compare
Choose a tag to compare

Version 1.12.0

Minor Changes

  • zos_backup_restore - default behavior for module option hlq changed. When option operation is set to restore and the hlq is not provided, the original high level qualifiers in a backup will be used for a restore.

  • zos_job_output - has added the address space type for a job returned as content_type in the module response.

  • zos_job_query - has added the address space type for a job returned as content_type in the module response.

  • zos_job_submit - has added the address space type for a job returned as content_type in the module response.

  • zos_mvs_raw - updates the stdout and stderr when an unknown, unrecognized, or unrepresentable characters with the 'replacement character' (�), found in the Unicode standard at code point U+FFFD.

  • zos_operator - has added the option case_sensitive, allowing the module to control the commands case.

  • zos_script - updates the stdout and stderr when an unknown, unrecognized, or unrepresentable characters with the 'replacement character' (�), found in the Unicode standard at code point U+FFFD.

  • zos_tso_command - updates the stdout and stderr when an unknown, unrecognized, or unrepresentable characters with the 'replacement character' (�), found in the Unicode standard at code point U+FFFD.

Bugfixes

  • zos_apf - module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.

  • zos_archive - module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.

  • zos_backup_restore - when a recoverable error was encountered and recover = True, the module would fail. The change now allows the module to recover.

  • zos_blockinfile

    • when the modules marker_begin and marker_end were set to the same value, the module would not delete the block. Now the module requires the marker_begin and marker_end to have different values.
    • module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option..
  • zos_copy

    • module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.
    • module would fail if the user did not have Universal Access Authority for SAF Profile MVS.MCSOPER.ZOAU and SAF Class OPERCMDS. Now the module handles the exception and returns an informative message.
    • module would ignore the value set for remote_tmp in the Ansible configuration file. Now the module uses the value of remote_tmp or the default value ~/.ansible/tmp if none is given.
  • zos_data_set - module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.

  • zos_encode - module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.

  • zos_fetch - module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.

  • zos_find

    • Module would not find VSAM data and index resource types. Fix now finds the data and index resource types.
    • Module would not find a VSAM cluster resource type if it was in use with DISP=OLD. Fix now finds the VSAM cluster.
  • zos_job_output - module would raise an invalid argument error for a user ID that contained @, $, or #. Now the module supports RACF user naming conventions.

  • zos_job_query

    • module did not return values for properties system and subsystem. Now the module returns these values.
    • module would raise an invalid argument error for a user ID that contained @, $, or #. Now the module supports RACF user naming conventions.
  • zos_lineinfile - module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.

  • zos_mount - module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.

  • zos_mvs_raw

    • Module sub-option base64 for return_content did not retrieve DD output as Base64. Now the module returns Base64 encoded contents for the DD.
    • Module would return the stderr content in stdout when verbose was true and return code was 0. Fix now does not replace stdout content with stderr.
    • Module would obfuscate the return code from the program when failing returning 8 instead. Fix now returns the proper return code from the program.
    • If a program failed with a non-zero return code and verbose was false, the module would succeed (false positive). Fix now fails the module for all instances where a program has a non-zero return code.
  • zos_script - module would only read the first command line argument if more than one was used. Now the module passes all arguments to the remote command.

  • zos_unarchive - module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.

Availability

  • Automation Hub
  • Galaxy
  • GitHub

Requirements

The IBM z/OS core collection has several dependencies, please review the z/OS core support matrix_ to understand both the
control node and z/OS managed node dependencies.

Known Issues

  • zos_job_submit - when setting 'location' to 'local' and not specifying the from and to encoding, the modules defaults are not read leaving the file in its original encoding; explicitly set the encodings instead of relying on the default.
  • zos_job_submit - when submitting JCL, the response value returned for byte_count is incorrect.
  • zos_apf - When trying to remove a library that contains the '$' character in the name for an APF(authorized program facility), the operation will fail.

release-v1.11.1

25 Nov 16:06
74c3df5
Compare
Choose a tag to compare

Version 1.11.1

Bugfixes

  • zos_mvs_raw

    • If a program failed with a non-zero return code and verbose was false, the module would succeed. Whereas, if the program failed and verbose was true the module would fail(false positive). Fix now has a consistent behavior and fails in both cases.
    • Module would obfuscate the return code from the program when failing returning 8 instead. Fix now returns the proper return code from the program.
    • Module would return the stderr content in stdout when verbose was true and return code was 0. Fix now does not replace stdout content with stderr.

Availability

  • Automation Hub
  • Galaxy
  • GitHub

Requirements

The IBM z/OS core collection has several dependencies, please review the z/OS core support matrix_ to understand both the
control node and z/OS managed node dependencies.

Known Issues

  • zos_job_submit - when setting 'location' to 'local' and not specifying the from and to encoding, the modules defaults are not read leaving the file in its original encoding; explicitly set the encodings instead of relying on the default.
  • zos_job_submit - when submitting JCL, the response value returned for byte_count is incorrect.
  • zos_apf - When trying to remove a library that contains the '$' character in the name from APF(authorized program facility), operation will fail.

release-v1.9.4

21 Nov 16:09
Compare
Choose a tag to compare

Version 1.9.4

Bugfixes

  • zos_mvs_raw - If verbose was true, even if the program return code was 0, the module would fail. Fix now ensures the module fails on non-zero return code only.

Availability

  • Automation Hub
  • Galaxy
  • GitHub

Requirements

The IBM z/OS core collection has several dependencies, please review the z/OS core support matrix to understand both the
controller and z/OS managed node dependencies.

Known Issues

  • zos_job_submit - when setting 'location' to 'LOCAL' and not specifying the from and to encoding, the modules defaults are not read leaving the file in its original encoding; explicitly set the encodings instead of relying on the default.

  • zos_job_submit - when submitting JCL, the response value returned for byte_count is incorrect.

  • zos_job_submit, zos_job_output, zos_operator_action_query - encounters UTF-8 decoding errors when interacting with results that contain non-printable UTF-8 characters in the response. This has been addressed in this release and corrected with ZOAU version 1.2.5.6 or later.

    • If the appropriate level of ZOAU can not be installed, some options are to:

      • Specify that the ASA assembler option be enabled to instruct the assembler to use ANSI control characters instead of machine code control characters.
      • Ignore module errors by using ignore_errors:true for a specific playbook task.
      • If the error is resulting from a batch job, add ignore_errors:true to the task and capture the output into a registered variable to extract the
        job ID with a regular expression. Then use zos_job_output to display the DD without the non-printable character such as the DD JESMSGLG.
      • If the error is the result of a batch job, set option return_output to false so that no DDs are read which could contain the non-printable UTF-8 characters.
  • zos_data_set - An undocumented option size was defined in module zos_data_set, this has been removed to satisfy collection certification, use the intended and documented space_primary option.

  • In the past, choices could be defined in either lower or upper case. Now, only the case that is identified in the docs can be set, this is so that the collection can continue to maintain certified status.

release-v1.12.0-beta.1

29 Oct 05:44
2b87759
Compare
Choose a tag to compare
Pre-release

Version 1.12.0-beta.1

Minor Changes

  • zos_backup_restore - default behavior for module option hlq changed. When option operation is set to restore and the hlq is not provided, the original high level qualifiers in a backup will be used for a restore.

  • zos_job_output - has added the address space type for a job returned as content_type in the module response.

  • zos_job_query - has added the address space type for a job returned as content_type in the module response.

  • zos_job_submit - has added the address space type for a job returned as content_type in the module response.

  • zos_mvs_raw - updates the stdout and stderr when an unknown, unrecognized, or unrepresentable characters with the 'replacement character' (�), found in the Unicode standard at code point U+FFFD.

  • zos_operator - has added the option case_sensitive, allowing the module to control the commands case.

  • zos_script - updates the stdout and stderr when an unknown, unrecognized, or unrepresentable characters with the 'replacement character' (�), found in the Unicode standard at code point U+FFFD.

  • zos_tso_command - updates the stdout and stderr when an unknown, unrecognized, or unrepresentable characters with the 'replacement character' (�), found in the Unicode standard at code point U+FFFD.

Bugfixes

  • zos_apf - module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.

  • zos_archive - module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.

  • zos_backup_restore - when a recoverable error was encountered and recover = True, the module would fail. The change now allows the module to recover.

  • zos_blockinfile

    • when the modules marker_begin and marker_end were set to the same value, the module would not delete the block. Now the module requires the marker_begin and marker_end to have different values.
    • module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option..
  • zos_copy

    • module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.
    • module would fail if the user did not have Universal Access Authority for SAF Profile MVS.MCSOPER.ZOAU and SAF Class OPERCMDS. Now the module handles the exception and returns an informative message.
    • module would ignore the value set for remote_tmp in the Ansible configuration file. Now the module uses the value of remote_tmp or the default value ~/.ansible/tmp if none is given.
  • zos_data_set - module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.

  • zos_encode - module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.

  • zos_fetch - module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.

  • zos_job_output - module would raise an invalid argument error for a user ID that contained @, $, or #. Now the module supports RACF user naming conventions.

  • zos_job_query

    • module did not return values for properties system and subsystem. Now the module returns these values.
    • module would raise an invalid argument error for a user ID that contained @, $, or #. Now the module supports RACF user naming conventions.
  • zos_lineinfile - module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.

  • zos_mount - module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.

  • zos_mvs_raw - module sub-option base64 for return_content did not retrieve DD output as Base64. Now the module returns Base64 encoded contents for the DD.

  • zos_script - module would only read the first command line argument if more than one was used. Now the module passes all arguments to the remote command.

  • zos_unarchive - module option tmp_hlq was previously ignored and default values were used. Now the module uses the value set in the option.

Availability

  • Galaxy
  • GitHub

Requirements

The IBM z/OS core collection has several dependencies, please review the z/OS core support matrix_ to understand both the
control node and z/OS managed node dependencies.

Known Issues

  • zos_job_submit - when setting 'location' to 'local' and not specifying the from and to encoding, the modules defaults are not read leaving the file in its original encoding; explicitly set the encodings instead of relying on the default.
  • zos_job_submit - when submitting JCL, the response value returned for byte_count is incorrect.
  • zos_apf - When trying to remove a library that contains the '$' character in the name for an APF(authorized program facility), the operation will fail.

release-v1.9.3

28 Oct 20:46
3bd152d
Compare
Choose a tag to compare

Version 1.9.3

Bugfixes

  • zos_job_query - Module was not returning values for system and subsystem. Fix now returns these values.

  • zos_mvs_raw

    • If a program failed with a non-zero return code and verbose was false, the module would succeed. Whereas, if the program failed and verbose was true the module would fail. Fix now has a consistent behavior and fails in both cases.
    • Module would obfuscate the return code from the program when failing returning 8 instead. Fix now returns the proper return code from the program.

Availability

  • Automation Hub
  • Galaxy
  • GitHub

Requirements

The IBM z/OS core collection has several dependencies, please review the z/OS core support matrix to understand both the
controller and z/OS managed node dependencies.

Known Issues

  • zos_job_submit - when setting 'location' to 'LOCAL' and not specifying the from and to encoding, the modules defaults are not read leaving the file in its original encoding; explicitly set the encodings instead of relying on the default.

  • zos_job_submit - when submitting JCL, the response value returned for byte_count is incorrect.

  • zos_job_submit, zos_job_output, zos_operator_action_query - encounters UTF-8 decoding errors when interacting with results that contain non-printable UTF-8 characters in the response. This has been addressed in this release and corrected with ZOAU version 1.2.5.6 or later.

    • If the appropriate level of ZOAU can not be installed, some options are to:

      • Specify that the ASA assembler option be enabled to instruct the assembler to use ANSI control characters instead of machine code control characters.
      • Ignore module errors by using ignore_errors:true for a specific playbook task.
      • If the error is resulting from a batch job, add ignore_errors:true to the task and capture the output into a registered variable to extract the
        job ID with a regular expression. Then use zos_job_output to display the DD without the non-printable character such as the DD JESMSGLG.
      • If the error is the result of a batch job, set option return_output to false so that no DDs are read which could contain the non-printable UTF-8 characters.
  • zos_data_set - An undocumented option size was defined in module zos_data_set, this has been removed to satisfy collection certification, use the intended and documented space_primary option.

  • In the past, choices could be defined in either lower or upper case. Now, only the case that is identified in the docs can be set, this is so that the collection can continue to maintain certified status.

ibm-ibm_zos_core-1.9.3.tar.gz