IBM Z Software
This portal is to open public enhancement requests against IBM Z Software products. 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.
Please note that this capability has now been delivered via PTF for APAR PH42125 for CICS CM 5.4. https://www.ibm.com/support/pages/apar/PH42125
• Why did you use a DFHCSDUP job to install the resources, and not a CICS CM batch INSTALL?
We needed CICSCM to be more of a spoke and wheel product with a centralized repository rather than the linear product that it was designed as. We did not want to have CICS CM running on each LPAR as it presented a bit of a maintenance nightmare when upgrading.
• How did you determine the resources to INSTALL from the Migrate post-exit CPPOMG01?
The resources to install came from the export file which we then read in via a temporary TD queue.
• Did you consider immediate submission of the batch job, with JES2 SCHEDULE statement HOLDUNTIL parameter to control its date/time of execution?
Have not considered that, but can. Either way, having a date/time entered would be necessary on the screen.
• Did you consider using the change package External Reference or Notes fields to signal the date/time schedule requirement?
Why did these fields not suit you? Could have used these except the External Reference was already being used. Notes requires going to a separate screen, so did not consider that.
• The Description field persists when the package is saved.
How do you control subsequent MIGRATEs of the package inheriting the previously scheduled value?
We try not to reuse packages for a number of reasons.
Is persisting the schedule date/time important? Would a pop-up panel asking for the exit data suit your purposes? Schedule date/time can be important when the developer has scheduled an install of a program and the CICS definitions need to coincide with their change.
• If the user must enter the date/time for the INSTALL, could they not just use ISPF option 3.7, edit the JCL to insert a SCHEDULE statement and submit the job? We submit the job via the internal reader from CICS CM, I don't know that option exists.
Thank you for raising this RFE. Can you please provide answers for the following questions:
• Why did you use a DFHCSDUP job to install the resources, and not a CICS CM batch INSTALL?
• How did you determine the resources to INSTALL from the Migrate post-exit CPPOMG01?
• Did you consider immediate submission of the batch job, with JES2 SCHEDULE statement HOLDUNTIL parameter to control its date/time of execution?
• Did you consider using the change package External Reference or Notes fields to signal the date/time schedule requirement?
Why did these fields not suit you?
• The Description field persists when the package is saved.
How do you control subsequent MIGRATEs of the package inheriting the previously scheduled value?
Is persisting the schedule date/time important? Would a pop-up panel asking for the exit data suit your purposes?
• If the user must enter the date/time for the INSTALL, could they not just use ISPF option 3.7, edit the JCL to insert a SCHEDULE statement and submit the job?