
19
© 2002. Reproduction prohibited. Please inform Xephon of any infringement.
MCI05E: SEGMENT NAME INVALID
Error (12) – Specified SEGMENT name not allowed for the specified profile
type.
Action – Check that the segment name is valid for the CLASS and PROFILE
specified.
MCI05E: WORK AREA TOO SMALL, TRY FEWER FIELDS
Error (16) – The workarea in the program is too small for the amount of data
requested. This is an internal limit set by the length of the getmained workarea
which is currently 32K.
Action – Either request less data to be returned or increase the size of the
workarea in the program by changing the ORG statement immediately
preceding the RACWAL label.
MCI05E: ICHEINTY RC=nnn REASON=nnn
Error (16) – An undetermined error occurred during a RACF database access
request.
Action – Check the code reported in the list of RETURN and REASON codes
for the ICHEINTY interface in the Security Server – Macros and Interfaces
manual.
MCI06E: NO USERDATA IN PROFILE
Error (4) – For a GET USERDATA request, none was found in profile named.
Action – Put some in.
MCI06E: USERDATA FIELD NOT FOUND
Error (4) – For a GET or DEL USERDATA request a requested FIELD was not
found in the profile.
Action – If the field is expected to be there try listing all USERDATA to see if
its name has been mis-spelled (omit the FIELD parameter).
MCI07E: NOT AUTHORIZED TO class.segment.field
Error (8) – The caller did not have sufficient access to perform the operation
requested on the field named in the message.
Action – Check they have the authority as described in the section entitled
‘Authorization’.
MCI07E: NOT ALL FIELDS RETURNED (ACCESS CHECK FAILED)
Error (8) – The caller did not have sufficient field level access to perform the
operation requested on SOME of the fields, but no information is returned by
RACF to indicate which particular fields.
Action – Try one field at a time to determine which ones cause the error.
These will produce the “NOT AUTHORIZED to class.segment.field” message.
MCI08E: USERDATA SUPPORTED IN BASE SEGMENT ONLY
Error (12) – USERDATA can be stored/retrieved only in the BASE segment of
a profile.
Action – Remove the SEGMENT parameter from the request.
Figure 4 (part two): Messages, errors, and actions (continued)
Comentarios a estos manuales