Solution: Check the syslog; if the problem is caused by
having incorrect permissions set for the started task ID, you often see an
RACF authorization failure message, as shown in the following example. ICH408I USER(TASKID1 ) GROUP(TSOUSER ) NAME(FRED (FRED) 959
/argo/MA11BRK/ENVFILE
CL(DIRSRCH ) FID(01D7C7E2E3F0F8000F16000000000003)
INSUFFICIENT AUTHORITY TO LOOKUP
ACCESS INTENT(--X) ACCESS ALLOWED(OTHER ---)
IEE132I START COMMAND DEVICE ALLOCATION ERROR
IEA989I SLIP TRAP ID=X33E MATCHED. JOBNAME=*UNAVAIL, ASID=00A8.
D J,BPXAS
IEE115I 11.13.04 2001.212 ACTIVITY 601
In this example, the started
task ID does not have access to the file system component. The ICH408I message
shows: - The file that the task is trying to access
- The user ID that is trying to access the file
- The permissions that the ID is expecting to have (INTENT in
the message)
- The permissions that the ID actually has (ALLOWED in
the message)
You can use this information to correct the permissions
and then reissue, in this example, the start broker request. This type of
message is produced if the user who is issuing the command (which might be
to start the broker, or to submit JCL to start one of the utility jobs) does
not have the correct file system permissions for the file system component.
Use the ICH408I information to rectify the problem.
Another possible
reason for authorization failures is inconsistencies in the RACF definitions
for a user ID in the MVS image and the OMVS segment. You should also check
with your system administrator that the RACF ID that is used on MVS has a
corresponding OMVS image created.