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.
Thank you for taking the time to suggest an enhancement to our product. Many of our product enhancements result from feedback from our customers, so your input is always very important to us. However, your request for enhancement is not currently aligned with our product strategy and vision and we have no plans to address your request in the near future. Again, thank you for your suggestion and continued support.
Yes, this is a z/os explorer RFE and there's a high possibility that it's going to be rejected.
I'm not sure which version of PDSMAN the customer is using but in the description found in the manual, it states....
"PDSMAN intercepts BLDL, FIND, and STOW operations to PDS and PDSE data sets. Specified access or update operations may be:
Allowed
Allowed, with a warning message
Allowed and logged to SMF (audit trail)
Allowed, with a warning message and logged to SMF
Prevented
Prevented and logged to SMF (audit trail)
All library accesses and updates that are logged to SMF may be reported by the PDSM17 utility, providing an audit trail of this activity."
https://docops.ca.com/ca-pdsman/7-7/en/using/auditing-and-comparison-facilities/maintaining-update-and-access-audit-trails-and-security/update-and-access-audit-trails-description
The most important part of the description is the first sentence. Essentially anything that deals with datasets will have to call those macros in the background (ISPF services included).
What I suspect is they have a rule in their PDSMAN config to Allow ISPF services to execute WITHOUT logging an SMF record for it. (ie. option 1 in the list above) Even in the manual, under section "Excessive Recording", it states to be mindful of logging all accesses as the SMF log could fill up quite quickly if they were to log every single VIEW/BROWSE/EDIT requests.
https://docops.ca.com/ca-pdsman/7-7/en/using/auditing-and-comparison-facilities/maintaining-update-and-access-audit-trails-and-security/update-and-access-audit-trails-implementation#UpdateandAccessAuditTrailsImplementation-ExcessiveRecording
I've also tried running ISRSUPC (option 3.14 Search-For) that they claim does not update the last reference date but my tests show the opposite. The last reference date for the dataset in the criteria is updated after every search. This is normal behaviour as we are "referencing" the dataset when we do the search.