CPF2105: Object not found

What it means

CPF2105 is an escape message from QCPFMSG with the text "Object &1 in &2 type *&3 not found". It belongs to the CPF21xx family that IBM i's library and object commands use, such as RNMOBJ and CRTDUPOBJ, and delete commands send it too. It means the same as CPF9801, with the object type added to the text.

The type matters. IBM i allows a file called PAYMAST and a program called PAYMAST in the same library, because they are different types. So CPF2105 can appear even when DSPLIB shows something with that name, if it is the wrong type.

Many CL programs expect this message. The common pattern deletes a work file before building it again and monitors for CPF2105, so the program carries on when the file isn't there. When monitored like that, CPF2105 in a job log is normal. It only matters if the program stops with a function check (CPF9999) after it.

Common causes

• A CL program deletes a work object that doesn't exist yet, for example on the first run or in a new job where QTEMP is empty, and doesn't monitor for the message.
• The object name or library is misspelled, or a variable built the wrong name.
• The command names the wrong object type, for example *PGM when the object is a *SRVPGM or a *CMD.
• The object was already deleted, moved or renamed by an earlier step or another job.
• With *LIBL, the library that holds the object isn't on the job's library list.

How to find the problem

1. Open the job log with DSPJOBLOG, put the cursor on CPF2105 and press F1. The help shows the object, library and type. The command logged just before it shows the exact names the program used.
2. Run WRKOBJ OBJ(*ALL/PAYWORK) to see every library holding an object of that name, and its type.
3. If the command used *LIBL, run DSPLIBL in the same kind of job to see which libraries were searched.
4. If a function check followed, F9 on the CPF9999 message shows the program and statement.

How to fix it

• For a delete that may find nothing, monitor for the message: DLTF FILE(QTEMP/PAYWORK) followed by MONMSG MSGID(CPF2105).
• Correct the name, library or object type on the command.
• If the object should exist, find out which step deletes or fails to create it, and fix the order of the steps.
• Qualify the library instead of relying on *LIBL when the object always lives in one place.

What it looks like

Object PAYWORK in QTEMP type *FILE not found.

DSPMSGD MSGID(CPF2105) MSGF(QSYS/QCPFMSG)

Technical reviewer: Albert Joseph, WND Software.

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 IBM i release.