The CHKINMBR command in TURNOVER® for iSeries v100 is used to check in a source member that was previously checked out—essentially the final step in TURNOVER’s source control cycle. It’s your way of saying, “I’m done editing, let’s return this to the controlled library.”
What CHKINMBR Does
This command:
- Returns the source member from your working library back to the controlled library
- Releases the lock, making it 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 Source Members panel.
Here’s a breakdown of the key fields:
| Parameter | Description |
|---|---|
SRCMBR | Name of the source member to check in |
SRCLIB | Working library where the member currently resides |
SRCFILE | Source physical file containing the member |
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 |
How It Fits in Your Workflow
Let’s say you’ve finished refactoring ORDENTR in your dev library DEVLIB. You’d run:
CHKINMBR SRCMBR(ORDENTR) SRCLIB(DEVLIB) SRCFILE(QRPGLESRC) REQUEST(RQ12345) COMMENT('Refactored order entry logic for modernization')
This safely checks the member back into TURNOVER’s controlled environment, updates the audit trail, and frees it up for promotion or further edits.
- Always run
CHKINMBRafter compiling and testing your changes. - Use the
COMMENTfield to document what was done—great for audit reports and team visibility. - Pair it with
CHECKOUTandPROMOTEin your Thrive Apprentice tutorials to teach the full lifecycle.