The caller cannot have any enabled, unlocked task (EUT) FRRs established.

In general, all request types must be issued from the same home address space from which the IXCARM REQUEST=REGISTER request was issued. However, IXCARM requests for elements that represent abstract resources (ELEMBIND=CURSYS is specified) can be issued from any address space. IXCARM DEREGISTER requests for elements that represent jobs or started tasks (ELEMBIND=CURJOB is specified) can be issued from the master address space or the same home address space from which the REGISTER request was issued.

Registration for ELEMBIND=CURJOB elements can only be done from started tasks that were initiated with the START command. Started tasks initiated by TSO/E logins or the ASCRE (address space create) macro in a program will not be restartable by ARM.

The security administrator may control the use of automatic restart management by unauthorized applications through the use of RACF® or another security product. Unauthorized applications can use only element names that are registered as ELEMBIND=CURJOB elements. Ensure that you are authorized to issue the IXCARM macro for such unauthorized applications.

To define profiles that control unauthorized applications' use of automatic restart management, the security administrator can:

1. Define resource profile IXCARM.elemtype.elemname in the FACILITY class.
2. Specify the users who have access to automatic resource management services using the RACF PERMIT command.
3. Make sure the FACILITY class is active and generic profile checking is in effect. If in-storage profiles are maintained for the FACILITY class, refresh them.

RDEFINE FACILITY IXCARM.xxxxxxxx.yyyyyyyyyyyyyyyy UACC(NONE)

PERMIT IXCARM.xxxxxxxx.yyyyyyyyyyyyyyyy CLASS(FACILITY) 
       ID(userid) ACCESS(UPDATE)

SETROPTS CLASSACT(FACILITY)

For information about RACF, see z/OS Security Server RACF Security Administrator's Guide.