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
Categories SMP/E
Created by Guest
Created on Apr 29, 2024

Adjust BPXPRM00 FILESYSTYPE for CINET to get a "clean" first IPL after a serverpac

I recently completed a z/OSMF serverpac install.  I attempted the first IPL in the procedures and everything came up except TCPIP.  TCPIP failed with the following message.  

 EZZ4203I Z/OS UNIX - TCP/IP CONNECTION ERROR FOR TCPIP-BPX4SOC,00000003,
FFFFFFFF,00000070,112B00B6      

Upon further research and comparison with a 2.4 system, I noticed that BPXPRM00 had several FILESYSTYPE statements commented out.    See screen snap below

 

 /*FILESYSTYPE TYPE(CINET) ENTRYPOINT(BPXTCINT)                      */
/*NETWORK DOMAINNAME(AF_INET)                                       */
/*        DOMAINNUMBER(2)                                           */
/*        MAXSOCKETS(64000)                                         */
/*        TYPE(CINET)                                               */
/*        INADDRANYPORT(4000)                                       */
/*        INADDRANYCOUNT(2000)                                      */
/*NETWORK DOMAINNAME(AF_INET6) DOMAINNUMBER(19) */   /* For IPv6    */
/*        TYPE(CINET)                           */                    
                                                                      
/*SUBFILESYSTYPE NAME(TCPIP)     */  /* Name of file system         */
/*               TYPE(CINET)     */  /* Type matching Cinet's TYPE  */
/*           ENTRYPOINT(EZBPFINI)*/  /* Entry point of load module  */
/*               DEFAULT         */  /* <- The Default Socket PFS   */
                                                                      
/*SUBFILESYSTYPE NAME(TCPIP2)    */  /* Name of file system         */
/*               TYPE(CINET)     */  /* Type matching Cinet's TYPE  */
/*           ENTRYPOINT(EZBPFINI)*/  /* Entry point of load module  */
         

These statements were not commented out in the BPXPRM00 member from the serverpac install.  They were active.  When I removed these statements TCPIP came up normally and I was able to start address spaces that required TCPIP to be active.   

 Seems these statements would be customized downstream from the first IPL by the customer as needed.   I can see the value having these statements in the BPXPRMxx member as a reference, but they should not inhibit the first IPL in the serverpac workflow.  

 

I am requesting these statements be place between comments with a narrative for their use.  The first IPL after a serverpac install should work successfully without any customization.  Or removal of parameters to make things work.   

Please refer to PMR Case # TS016027141 for more of an explanation.                                                                                                 

Idea priority High
  • Guest
    Reply
    |
    May 8, 2024
    Thank you for your comments. For z/OS 3.1 ServerPac orders, the CINET FILESYSTYPE statements are currently commented out in the supplied BPXPRMxx PARMLIB member. In addition, these statements will be completely removed for future z/OS ServerPac orders.