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

IRR010I

User ID assigned to job (no USER on job card)RACF MESSAGE

Informational: the job card had no USER parameter, so the submitting user's ID was assigned to the job. Normal, and no action is needed.

MOST LIKELY

The JOB statement has no USER parameter.

FIRST CHECK

No action needed.

TRY IT ▸

Site search

What it means

IRR010I is a notice that goes only to the job log. It shows that the JOB statement did not name a user, so the ID of whoever submitted the job was attached to it. This is ordinary user ID propagation, and processing carries on as normal.

Seeing it is not a warning. It is useful when you need to confirm which ID a batch job ran under, because the job log records it.

Typical causes

  • The JOB statement has no USER parameter.
  • The job takes on the ID of the user who submitted it.
  • The message only records which ID the job is running under, so nothing has gone wrong.

How to fix it

  1. No action needed.
  2. Check the job log to confirm the user ID shown is the one you expected.
  3. If the wrong ID is shown, check who submitted the job and ask your RACF security administrator, through the normal process, whether a USER should be coded on the JOB statement.

Example

Illustrative only; names and values are invented.

IRR010I USERID USER01 IS ASSIGNED TO THIS JOB.