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 Future consideration
Workspace z/OS
Categories USS
Created by Guest
Created on Mar 2, 2020

USS_PARMLIB_MOUNTS Health Check Refresh After IPL

During a recent IPL a typo in the BPXPRMxx member had the incorrect
name for a zFS file system. As a result, the mount failed with error
message BPXF002I:

BPXF002I FILE SYSTEM OMVS.ASYS.ORESB1.COBOL42 WAS 674
NOT MOUNTED. RETURN CODE = 00000081, REASON CODE = EF096055

Once the system was up, the BPXPRMxx member was updated to correct the
error and the zFS file system was manually mounted. However, the error
had triggered the USS_PARMLIB_MOUNTS Health Check so it was listed in
the Health Check exception list.

In an attempt to clear the exception, the USS_PARMLIB_MOUNTS check was
run but it continued to flag the "missing" file system:

BPXH059I The following file systems are not active:
---------------------------------------------------
File System: OMVS.ASYS.ORESB1.COBOL42
Parmlib Member: BPXPRM3A
Path: /usr/lpp/cobol
Return Code: 00000081
Reason Code: EF096055

Issuing a D OMVS,MF also showed the failed file system so I used the D
OMVS,MF=PURGE command to clear the entry and then re-ran the Health
Check but it still generated an exception.

I also tried issuing a SET OMVS=(3A, 3S) which matches the setting in
the IEASYSxx member but the Health Check still failed.

I opened the PMR listed above and was told that this behavior is the intended design of the USS_PARMLIB_MOUNTS Health Check and that the values checked by the Health Check are those that were specified in the BPXPRMxx members at initialization time. As a result, the only way to clear the exception, is to correct the BPXPRMxx member and IPL.

I am opening this RFE to request that the USS_PARMLIB_MOUNTS Health Check be updated so that it reads the current BPXPRMxx members when validating the mounts and not what was contained in the members at IPL. This will allow a customer to correct the BPXPRMxx member containing the error and then re-run the USS_PARMLIB_MOUNTS Health Check to re-validate the mounts and clear the exception.

Please feel free to contact me if you have any questions or need any additional information.

Idea priority Low
  • Guest
    Reply
    |
    Feb 23, 2021

    .This item is not in our plans but is being kept in our backlog.