On Tue, 30 Jul 2013 22:27:30 +0530, Robert Hahne <[email protected]> 
wrote:

>Hi , 
>
> We have a problem in our Z/os 1.11 system where GPMSERVE started task 
> continuosly abends after IPL with the below message  and then starts fine 
> later on when start command is issued manually . The message is given below . 
> TCPIP is already initialized before this happens .  Any thoughts ?
>
>
> CEE3798I ATTEMPTING TO TAKE A DUMP FOR ABEND U4093 TO DATA SET:         
> *BYPASS*.D209.T0501293.GPMSERVE                                         
> IEA820I TRANSACTION DUMP REQUESTED BUT NOT TAKEN 417                    
>         DUMP DATA SET NAME NOT VALID                                   
> CEE3796I AN ATTEMPT TO DYNAMICALLY TAKE A DUMP WAS NOT SUCCESSFUL. 418  
> THE ERROR RETURN CODE WAS 00000008 AND THE REASON CODE WAS 00000021.    
> IEA995I SYMPTOM DUMP OUTPUT 419                                         
>   USER COMPLETION CODE=4093 REASON CODE=00000090                        
>  TIME=05.01.29  SEQ=00026  CPU=0000  ASID=0068                          
>  PSW AT TIME OF ERROR  078D1000   80008BD4  ILC 2  INTC 0D              
>    ACTIVE LOAD MODULE           ADDRESS=000072D8  OFFSET=000018FC       
>    NAME=CEEBINIT                                                        
>    DATA AT PSW  00008BCE - 00181610  0A0DA7F4  001C1811                 
>    GR 0: 84000000   1: 84000FFD                                         
>              2: 00000090   3: 0B0C00FD    
>      4: 141CD300   5: 80011818    
>      6: 141CD300   7: 141CD7B0    
>      8: 00000000   9: 09249D4E    
>      A: 00008B98   B: 80008B00    
>      C: 141CEB48   D: 141D6018    
>      E: 80000000   F: 00000090    
> END OF SYMPTOM DUMP                          
>
>IEF450I GPMSERVE GPMSERVE - ABEND=S000 U4093 REASON=00000090  
>IEF404I GPMSERVE - ENDED                                      
>
>  Regards,
>Bob            
>                                         

I assume you are asking because z/OS 1.11 is EOS and you don't have
an extended support contract with IBM??

Return code is "Condition management for MVS could not be initialized"

Have you tried getting / looking at the LE dump?

If you are sure OMVS is fully initialized (which I am assuming it is since
you said TCP/IP is fully functional before starting it), it could be related
to MAXPROCUSER since it is timing related.  What UID does it run under?

You could take the easy way out (since this is an unsupported system)
and just start it later in the IPL to begin with!  

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS       
mailto:[email protected]                                        
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html 
Systems Programming expert at http://expertanswercenter.techtarget.com/

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to