The client ran the following statements in an SMP/E ACCEPT CHECK run of the View 14.0 Sysmods:
ACCEPT CHECK /*** Remove to accept all Functions ***/
SELECT ( CBRME00 /*CA-View */
CBROE00 /*CA-EBC OM Common Dbase Driver */
CBY3E00 /*CA-OM DATA REPOSITORY AGENT SERVICES */
CBY3E02 /*CA-OM DATA REPOSITORY AGENT SERVICES */
CBRNE00 /*CA-Deliver */
CCAFE00 /*CA Output Management Web Viewer */ )
which resulted in GIM24701W messages for PTFs RO95796, RO96445 RO99656 and SO00833.
Are the messages of any concern?
In the client's SMP/E listing, was the following message:
GIM20501I ACCEPT PROCESSING IS COMPLETE. THE HIGHEST RETURN CODE WAS 04.
The message indicates that a successful ACCEPT will occur, when the CHECK is not used.
Here is the order of the client's SMP/E processing:
. RECEIVE - View base Sysmods
. APPLY - View base Sysmods
. RECEIVE - maintenance
. APPLY - maintenance
. ACCEPT - View base Sysmods
If the RECEIVE/APPLY/ACCEPT on the View base Sysmods had been done, before applying any maintenance, then there would have been no GIM24701W messages generated.
The GIM24701W messages were generated from PTFs RO95796, RO96445 RO99656 and SO00833
This is a link to the IBM explanation of the GIM24701W message:
In the message's Explanation, it states:
"Note: This message is normal when SMP/E ACCEPTs elements into the distribution libraries for the first time."
The first-time of a run of ACCEPT, on the noted PTFs, accounts for the GIM24701W warning messages.
As a rule, the GIM24701W messages should be ignored.
The reason being that a product's runtime libraries and USS directories are taken from the target zone, and the modules are not linked based on default settings when the APPLY is done.
The distribution zone, which is updated by the ACCEPT, is only a backup of the target zone.
The reason the modules are being linked to distribution, based on defaults, is because it is just a backup.
Runtime will not be using the modules from the distribution zone.
In an SMP/E LIST ALLZONES report, entries that are shown are those that are in the target zone (CAIT0), and not in the distribution zone (CAID0).
The target zone is shown because runtime will not be using any modules from the distribution zone.