Learn it on Mainframe Path. Do it with MainframeKit.Learn on Mainframe Path ▸
MainframeKit

S282

RACF reported a bad RACROUTE requestSYSTEM ABEND

RACF found an error in the parameters of a security request. It issued ICH409I and abended the caller with 282 and a reason code.

MOST LIKELY

A resource or user name contains a blank, often from extra spaces in a configuration file.

FIRST CHECK

Read ICH409I and note the hexadecimal reason code.

TRY IT ▸

Record decoder

What it means

Abend 282 is not an access denial. It means the program (or a product acting for it) built an invalid RACROUTE REQUEST=AUTH call, such as a bad length, a missing class name or a malformed resource name. ICH409I carries the same hexadecimal reason code.

For example, reason 5C means the resource or entity name contained a blank. In one IBM case, stray leading spaces in a configuration file value were passed on as part of a user ID name.

Typical causes

  • A resource or user name contains a blank, often from extra spaces in a configuration file.
  • A required class name or resource name was not supplied.
  • A name length is outside the allowed range.
  • An authority option was used by a caller that has no APF authorization or system key.
  • A user-written routine or exit built the parameter list wrongly.

How to fix it

  1. Read ICH409I and note the hexadecimal reason code.
  2. Look up the reason code in the RACF messages and codes or RACROUTE documentation.
  3. Check configuration values for stray spaces or wrong names, then restart the product.
  4. If your own program issues the call, correct its parameter list.
  5. If an IBM or vendor product issues it, open a case with the exact message and reason code.

Example

Illustrative only; names and values are invented.

ICH409I 282-05C ABEND DURING RACHECK PROCESSING