Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Workspace z/OS
Created by Guest
Created on Apr 12, 2022

NCA: Tailored include/obeyfile should not be limited to LRECL during provisioning

In the z/OSMF Network Configuration Assistance for Cloud configuration; you specify an include and obeyfile for every z/OS image. The 'general' default is a PDSE with FB LRECL 80. The same applied to the 'ezb_cloud_allocate_stack_pdse' workflow as part of the configuration wizard.

When a provisioning template runs which uses network resources (and thus indirectly using and updating the obey/include file), provisioning can fail if one of the VIPA statements exceeds the LRECL of 80 with error:

"EDC5003I Truncation of a record occurred during an I/O operation. (errno2=0xC0440016);"

This is unnecessary because statements can continue on a new line. z/OSMF (or NCA) however demands the line must fit.

An obvious temporary solution is to recreate the PDSE with a larger LRECL, but in our opinion z/OSMF/NCA should honour the dataset LRECL and should continue statements on a new line.

Specific provisioning failed initially because it attempted to fit more then 10 ports on one line and reaching the LRECL of 80.


VIPADYNAMIC
VIPADEFINE 255.255.255.255 xxx.xxx.xxx.xxx
VIPADISTRIBUTE DEFINE DISTM weightedActive OPTLOCAL
xxx.xxx.xxx.xxx PORT 11020 11021 11022 11023 11024 11025 11026 11027 11042 11043
DESTIP xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx
ENDVIPADYNAMIC


z/OSMF or NCA should - if reaching the LRECL of 80 continue on the next line like:


VIPADYNAMIC
VIPADEFINE 255.255.255.255 xxx.xxx.xxx.xxx
VIPADISTRIBUTE DEFINE DISTM weightedActive OPTLOCAL
xxx.xxx.xxx.xxx PORT 11020 11021 11022 11023 11024 11025 11026 11027 11042 11043
11044 11045
DESTIP xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx
ENDVIPADYNAMIC

instead of issuing EDC5003I Truncation.




Idea priority Medium
  • Guest
    Reply
    |
    Oct 5, 2023
    This was delivered in z/OS 3.1