Required resources

Developer for z/OS® requires the allocation of the systems resources listed in Table 1. The resources listed in Table 2 are required for optional services. Plan to have these resources available because, depending on the policies at your site, it might take some time to get them.

Table 1. Required resources
Resource	Default value	Information
MVS build procedures	ELAXF*	PROCLIB changes

Table 2. Optional resources
Resource	Default value	Information
LPA data set	FEL.SFELLPA	LPA definitions in LPALSTxx
port range for host-confined use	any available port is used	Common Access Repository Manager (CARMA) Host-based code analysis
CICS® JCL update	FEL.SFELLOAD	CICS bidirectional language support
PROCLIB update	AKG*	Host-based code analysis

The configuration of Developer for z/OS requires more than the typical system programming permissions and expertise; therefore, assistance from others might be needed. Table 3 and Table 4 list the administrators who are needed for the required and optional customization tasks.

Table 3. Administrators needed for required tasks
Administrator	Task	Information
System	Typical system programmer actions are required for all customization tasks	N/A

Table 4. Administrators needed for optional tasks
Administrator	Task	Information
Security	Define data set profiles	"Security considerations" in Host Configuration Reference
TCP/IP	Define new TCP/IP ports	CRASRV.properties, the RSE interface to CARMA Multiple Code coverage invocations
CICS TS	Update CICS region JCL Update CICS region CSD Define CICS resources	CICS bidirectional language support Diagnostic IRZ messages for Enterprise Service Tools
WLM	Assign goals to Developer for z/OS tasks	"WLM considerations" in the Host Configuration Reference