IKJ56225I: Data set already in use, try later

What it means

z/OS protects each data set with an enqueue on its name. A job or user that has a data set with DISP=SHR holds a shared enqueue, and others can share it. One that has it with DISP=OLD, NEW or MOD holds an exclusive enqueue, and nobody else can get it at all. TSO allocations don't wait for an enqueue to be released. If yours conflicts, dynamic allocation fails at once with error code 0210, and TSO writes IKJ56225I.

The first line names the data set and ends with a plus sign. The second-level line, DATA SET IS ALLOCATED TO ANOTHER JOB OR USER, confirms the reason. Type a question mark at the READY prompt to see it if it isn't shown.

The enqueue belongs to whoever allocated the data set, and it lasts until they free it or their job or session ends. A batch job that has the data set as DISP=OLD holds it for the whole job unless the system releases it earlier, and a TSO user holds an allocation until they FREE it or log off.

Common causes

• A batch job is running with the data set allocated DISP=OLD, NEW or MOD.
• Another TSO user allocated it with OLD, for example through a CLIST, a REXX exec or a product that allocates OLD by default and never frees it.
• You asked for exclusive use (OLD) when you only need to read it, while someone else has it shared.
• A started task or long-running region, such as a CICS region, keeps the data set allocated.
• A job or session that used the data set has hung or is waiting, so it hasn't released it.

How to find the problem

1. Under ISPF, run TSO ISRDDN and use its ENQ command with the data set name to see who holds the enqueue.
2. Ask operations, or use SDSF if you are allowed, to issue D GRS,RES=(SYSDSN,PROD.PAYROLL.MASTER). It lists the jobs or users that own or wait for the data set.
3. Check your own command or exec. If it allocates OLD, ask whether SHR would do.
4. Check the schedule for batch jobs that update the data set.

How to fix it

• Ask for shared access when you only read the data set, for example ALLOC FI(PAYIN) DA('PROD.PAYROLL.MASTER') SHR REUSE.
• Wait for the holding job to finish, then retry, as the message says.
• Ask the other user to free it with FREE DATASET('PROD.PAYROLL.MASTER') or to log off if the session is idle.
• Change execs and CLISTs that allocate OLD so they use SHR where possible and FREE the data set when done.
• If a hung job or session holds it, ask operations to deal with that job. Don't cancel other people's work yourself.

What it looks like

IKJ56225I DATA SET PROD.PAYROLL.MASTER ALREADY IN USE, TRY LATER+
IKJ56225I DATA SET IS ALLOCATED TO ANOTHER JOB OR USER

Last reviewed 2026-10-18 by the WND Software team. Written in our own words. For the full reference, check IBM’s documentation for your z/OS release.