No RACF OMVS segment

If there is no RACF OMVS segment defined to the TSO user ID used to execute an ISPF tool using an Application Workflow Manager modeled application, the following error message is displayed:

This message was issued by z/Server (the remote software), the scheduler address space in particular. The scheduler address space had started the user server address space needed to establish the master configuration data set that contains the ISPF application. That address space did come up, but was unable to signal itself READY to the scheduler address space. Message SLR0131E is issued to the client after a predefined wait period to tell the client that it could not talk to the user server address space.

The administrator for z/Server needs to check for errors. For this particular problem, the z/OS hardcopy log shows:

ICH408I USER(user   ) GROUP(group    ) NAME(####################) 
  CL(PROCESS )                                                    
  OMVS SEGMENT NOT DEFINED                                       

Job output in user server maintask has this error message again detailing the missing OMVS RACF segment:

TAU0143S  07:35:19.091 This indicates an z/OS UNIX process initialisation failure.    
                       This is usually an indication that a proper OMVS RACF segment  
                       is not defined for the user ID associated with the application 
                       The RACF OMVS segment may not be defined or may contain error  
                       such as an improper HOME() directory specification.            
TAU0139E  07:35:24.094 SVC with function code 00000800 failed with RC 00000008       

In this case, the TSO user ID must be defined with an OMVS segment (usually done by the RACF administrator) as detailed in the z/Server Installation and Reference.