System prerequisites for the CEA TSO/E address space services

Table 1 describes the system prerequisites for using the CEA TSO/E address space services.

Table 1. System prerequisites
Prerequisite	Description
CEA must be active.	The CEA TSO/E address space manager runs in the CEA address space, which is started automatically during z/OS® initialization. If your installation has stopped CEA, restart it. Otherwise, the services are not enabled. To determine whether the CEA address space is active, enter the following z/OS system console command: `D A,CEA`
The TRUSTED attribute must be assigned to the CEA started task.	To allow the CEA TSO/E address space manager to access or create any resource it needs, the CEA started task requires the TRUSTED(YES) attribute to be set on the RDEFINE STARTED CEA.** definition. If the TRUSTED attribute is not assigned to the CEA started task, the CEA TSO/E address space manager services might not be operational. For example, the services will not be able to create or access z/OS UNIX message queues. For more information about the RACF® TRUSTED attribute, see the topic on associating started procedures and jobs with user IDs in &icha200t;, and the topic on using started procedures in &icha700t;.
The CEA address space must be started in full function mode.	Because the CEATsoRequest API requires z/OS UNIX System Services, CEA must be started in full function mode. For information about starting CEA in full function mode, see the topic about customizing CEA in &e0zb100t;.
Callers must be authorized to SAF resource profile CEA.CEATSO.TSOREQUEST.	To access the CEATsoRequest API, callers must be authorized by their security product to SAF resource profile CEA.CEATSO.TSOREQUEST.
Users must be authorized to the appropriate resources.	The user ID of the user for whom the caller is requesting TSO/E address space services must be authorized to use TSO/E, OMVS, and any other resources the address space requires.