GIM41101E error when issuing RESTORE CHECK on ACF2 USERMOD
Article ID: 235370
Updated On:
Products
Issue/Introduction
When doing a RESTORE with a CHECK for an ACF2 USERMOD, there is an error stating that a PTF that changed a module. When going to RESTORE the PTF that was identified, it has already been ACCEPTed. Is there a way around this error without needing to re-install all ACF2 maintenance from the beginning?
GIM41101E ** SMP/E DID NOT RESTORE MODULE ENTRY mod_name FOR SYSMOD xxxxxxx BECAUSE MODULE mod_name WAS CHANGED BY
RO99162.
GIM30208I RESTORE PROCESSING FAILED FOR SYSMOD xxxxxxx. JCLIN PROCESSING FAILED.
GIM22601E ** RESTORE PROCESSING FAILED FOR SYSMOD xxxxxxx.
GIM20501I RESTORE PROCESSING IS COMPLETE. THE HIGHEST RETURN CODE WAS 08.
Environment
Release : 16.0
Component : ACF2 for z/OS
Resolution
Review this IBM article which suggests to UCLIN the LASTUPD date for affected module to the USERMOD name. This is due to PTFs/USERMODs specifying the module in the JCLIN. Verifying USERMODs are RESTORE'd and REJECTed before APPLYing and ACCEPTing ACF2 maintenance will assist in avoiding this situation in the future.
The steps are as follows:
1. Take a backup of the SMP/E environment (SMP/E and product libraries).
2. Run the following SMP/E LIST/UCLIN job:
//SMPCNTL DD *
SET BOUNDARY ( targetzone ) .
LIST MOD(mod_name).
UCLIN .
REP MOD(mod_name) LASTUPD(xxxxxxx).
ENDUCL .
LIST MOD(mod_name).
Where targetzone - name of the SMP/E target zone
mod_name - name of the module
xxxxxxx - name of the problem USERMOD being restored
** NOTE: The LIST commands are so the status can be
determined if desired.
3. RESTORE the USERMOD
4. Continue with maintenance cycle processing.
Feedback
