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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Updating the config file and issuing F REFRESH works as long as the config file is in zFS or an MVS PDS or PDSE. Making it work for other MVS dataset types would not be cost-justified. This will be closed.
This item is not in our plans but is being kept in our backlog.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - z Systems Software
Product - z/OS Communications Server
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Enterprise Networking
Product - z/OS Communications Server
We have disp=shr already.
//STDENV DD DSN=SYS3.TCPIP.&SYSPLEX..TCPPARMS(SMTPEV),DISP=SHR
//CONFIG DD DSN=SYS3.TCPIP.&SYSPLEX..TCPPARMS(SMTPCF),DISP=SHR
Maybe i didn't explain this issue. SMTP has an inclusive right to the tcpparms which stops us from compressing it or moving to another volume.
SYS3.TCPIP.SP0Z.TCPPARMS
SYS3.TCPIP.SP0Z.TCPPARMS
JOB NAME ENQ TYPE
-------- ---------
SMTP SHARED
Hello, To share the dataset, you will need to specify a disp=shr. This is the approach recommended by our z/OS Communications server applications. In fact, we think that files will be shared, so we support system symbols. Is there a problem in your organization with using disp=shr?