The CHKINOBJ command in TURNOVER® for iSeries v100 is used to check in an object not just a source member, but any object type (like *PGM, *FILE, *MODULE, etc.) that was previously checked out through TURNOVER’s source control system. It’s the object-level counterpart to CHKINMBR, and it plays a key role in maintaining integrity across your development lifecycle.
What CHKINOBJ Does
This command:
- Returns a checked-out object from a working library back to its controlled library
- Releases the lock, making the object available for other developers
- Updates TURNOVER’s audit trail, recording who checked it in and when
- Optionally links the check-in to a request, task, or worklist item
It’s the command-line equivalent of using option 3=Check In on the Work with Objects panel.
Here’s a breakdown of the key fields:
| Parameter | Description |
|---|---|
OBJNAME | Name of the object to check in |
OBJTYPE | Type of object (e.g., *PGM, *FILE, *MODULE) |
LIBRARY | Working library where the object currently resides |
REQUEST | Optional request ID to associate the check-in with a change request |
TASKID | Optional task ID for tracking |
PWLNAME | Optional Programmer Worklist name |
COMMENT | Optional description of the changes made |
Let’s say you’ve finished updating the compiled RPGLE program ORDENTR in your dev library DEVLIB. You’d run:
This checks the object back into TURNOVER’s controlled environment, logs the action, and frees it up for promotion or further edits.
- Use this command after compiling and validating your object changes.
- Always pair it with
CHECKOUTandPROMOTEin your lesson flows to teach the full lifecycle. - Great for scripting object-level check-ins in batch workflows or emergency change scenarios.