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.

Add a new idea Subscribe
Status Future consideration
Workspace z/OS
Categories SMP/E
Created by Guest
Created on Jul 12, 2022

RELATED IDEAS

Enhance zosmf SMP Features

I have tested SMP APPLY PTFS with zosmf gui.

Basically it works, but there are some quirks



1) The "corrective" type of apply should present a list of all ptfs received and not applied yet so i can choose from a list

If i want to apply all ptfs received with maybe some excludes there is no easy way to do this in gui

i have to create a list noapply report in Batch and copy this into the gui,


2) Ptfs usually? have a short one line description that should be presented in gui when ptfs are listed


3) Put the zip file output of smp processing into uss folder, so the whole process is documented on host-system


example


/basepathxxxx/ZOS25/Apply/2022_05_08_112033_corrective_summary.txt

/basepathxxxx/ZOS25/Apply/2022_05_08_112033_corrective_smpxx1.txt

/basepathxxxx/ZOS25/Apply/2022_05_08_112033_corrective_smphrpt.txt

etc



Or into pdse members


example


hlq.ZOS25.D220508.T112033.APPLY.COR(summary)

hlq.ZOS25.D220508.T112033.APPLY.COR(smpxx1)

hlq.ZOS25.D220508.T112033.APPLY.COR(smpxx2)


etc


Its tricky to reupload such txt from windows to host , because they contain LF char and not windows like cr-lf linetermination char


4) IF i have e.g. a broadcom tss apply in gui and i select "recommended" it creates following apply



APPLY


SOURCEID(RSU*

SECINT

HIPER

CAR*

RSL*

PRP)

GROUP

BYPASS(HOLDUSER

HOLDSYSTEM

HOLDFIXCAT)

CHECK

.


this list seems to be hardcoded.

it would be nice to allow to define a user defined apply sourceid list e.g. ORD000x


5) The SMP ACCEPT is not supported in GUI. I have to use Batch jobs.

This is needed in normal smp cycle receive, apply,accept

Automating PTF Receives in Batch is ok and sufficient for me

Other special cmds like RESTORE are rarely used and not so important




Idea priority Medium
  • Guest
    Reply
    |     Aug 17, 2022

    Hello Kurt, thanks for your comments

    I usually only receive ptfs, when there is a need, e.g. rsu

    I see no reason to automate daily. Except you may argue if i have a production problem AND a ptf is available for this AND internet receive fails AND Shop Z Method fails for whatever reason, then i´m in trouble



  • Guest
    Reply
    |     Aug 5, 2022
    Thank you for your suggestions for z/OSMF Software Update. Generally we agree with your ideas and will consider them as we plan future updates, but I would like to address some of your comments directly.

    (1) The "Install Corrective" action should display a list of PTFs that have been received but not yet applied and allow you to choose PTFs to apply from that list. I agree, this is a capability Software Update should offer.

    (2) Display a short description from the PTF when displaying PTFs in a list. I agree, this too is a capability Software Update should offer. In the mean time you should know when the Install Corrective action displays the list of PTFs you specified, the "Details" action is available to display the long description for a PTF. Find this action by clicking the vertical ellipsis (three dots) in the right-most column of a row.

    (3) Save the zip file of SMP/E output for an install operation on z/OS. Actually, the zip file containing the SMP/E output is already saved on z/OS, in the z/OSMF data directory, /global/zosmf/, but of course Software Update only makes the saved output available in the form of a zip file downloaded to a workstation. I think what you really want is an easy mechanism to save the plain text SMP/E output to z/OS. This is a request we have heard before and I agree this is a capability Software Update should offer.

    (4) Allow the user control of the SOURCIEDs specified on the apply for the "Install Recommended" action. I agree, this is a capability Software Update should offer.

    (5) Provide an SMP/E ACCEPT command action. I agree, this is a capability Software Update should offer.

    I am very glad to hear that you do not require a capability to perform SMP/E RECEIVE operations in Software Update. I believe the best practice is to automate SMP/E RECEIVE ORDER independently of z/OSMF and Software Update, and I am happy to read that you agree. Thank you again for your comments and suggestions.

    Kurt Quackenbush
    IBM, z/OS SMP/E and z/OSMF Software Management

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.