SMP install of RMOATHTB table using BRNSATHT job failed with GIM50301E
search cancel

SMP install of RMOATHTB table using BRNSATHT job failed with GIM50301E

book

Article ID: 235730

calendar_today

Updated On:

Products

Deliver

Issue/Introduction

The BRNSATHT job failed with a RC=12 during installation of the RMOATHTB security table (USERMOD=BRNATB).

Summary of errors received:

RECEIVE SELECT(BRNATB) SYSMODS   LIST.
GIM50301E ** BRNATB WAS NOT PROCESSED BECAUSE IT IS NOT AN FMIDSET DEFINED IN THE GLOBAL ZONE.
GIM60001S ** RECEIVE PROCESSING FAILED BECAUSE AN SMPCSI OR SMPPTS DATA SET WAS NOT AVAILABLE
GIM59605W    ENQ FAILED FOR SHARED USE OF <CSI data set name>  FOR RECEIVE PROCESSING.        
GIM20501I    RECEIVE PROCESSING IS COMPLETE. THE HIGHEST RETURN CODE WAS 12. 

Environment

Release : 14.0

Component : Deliver

Cause

The GIM50301E is documented in QUICKREF as:

GIM50301E    value WAS NOT PROCESSED BECAUSE IT IS NOT AN FMIDSET DEFINED 
             IN THE GLOBAL ZONE.                                          
                                                                          
             Explanation:                                                 
                                                                          
             value     value                                              
                                                                          
             SMP/E tried to determine whether the indicated value is an   
             FMID or an FMIDSET name. The value is not 7 characters long, 
             so it is not an FMID.  Therefore, SMP/E checked whether there
             was an FMIDSET entry defined in the global zone with the same
             name as this value. However, it did not find any.            
                                                                          
             System Action:  SYSMOD processing stops.                     
                                                                          
             Programmer Response:  Do one of the following:               
                                                                          
             o   If you meant to specify an FMIDSET name, either correct  
                 the value you specified or create the desired FMIDSET    
                 entry. Then rerun the job.                               
                                                                          
             o   Otherwise, take no action. 

The cause of the error was due to the name of the usermod only being 6 characters in length (BRNATB )and there not being an FMIDSET entry defined in the global zone.

Resolution

Changing the name of the USERMOD from the default of "BRNATB" to a 7 character name of "BRNATHB" solved this problem.