Defining JES as a RACF started procedure

z/OS Security Server RACF Security Administrator's Guide

Previous topic | Next topic | Contents | Contact z/OS | Library | PDF

Defining JES as a RACF started procedure

z/OS Security Server RACF Security Administrator's Guide
SA23-2289-00

For performance and ease of migration, JES should be defined as a started procedure with the trusted attribute when RACF® is installed.

To do this, perform the following steps:

Ask your JES system programmer for the name of your JES started procedure.
Verify that the name of your JES started procedure exists as one of the following:
- An entry in the STARTED class (the preferred method). If it is not defined, you need to create one. For example, if the name of your started procedure is JES2, issue:
```
SETROPTS GENERIC(STARTED)
RDEFINE STARTED JES2.* UACC(NONE)
   STDATA(USER(jes-userid) TRUSTED(YES))
```
  Be sure to refresh the class after you create the entry. Issue:
```
SETROPTS RACLIST(STARTED) REFRESH
```
- An entry in the RACF started procedures table (module ICHRIN03). If none is defined, create an entry for JES.
In either case, be sure that JES has the trusted attribute.

Create a user profile for the JES started procedure:

ADDUSER jes-userid
        DATA('JES started procedure')
        NOPASSWORD
        DFLTGRP(appropriate-group)

For more information on adding a started procedure, see Using started procedures and z/OS Security Server RACF System Programmer's Guide.

Go to the previous page

Go to the next page

Notices | Terms of use | Support | Contact z/OS | zFavorites

Copyright IBM Corporation 1990, 2014