The CHECKOUT command in TURNOVER® for iSeries v100 is a key part of the source control and change management workflow. It’s used to check out source members from a controlled library so developers can safely modify them without disrupting production or conflicting with other changes.
This command can be used for both batch and interactive checkout processing from the Programmer Worklist (option 21). It can also be executed from the TURNOVER® for iSeries v100 command line to check out source either by object or by source member.
What CHECKOUT Does
This command:
- Copies a source member from a controlled library (like a production or baseline library) to a working library for editing
- Locks the member to prevent simultaneous changes by other developers
- Tracks the change in TURNOVER’s audit and promotion system
- Optionally links the checkout to a request, task, or worklist item
It’s the command-line equivalent of using the Work with Source Members panel and selecting Option 2=Check Out.
Here’s a breakdown of the key fields:
| Parameter | Description |
|---|---|
SRCMBR | Name of the source member to check out |
SRCLIB | Source library where the member currently resides |
SRCFILE | Source physical file containing the member |
TGTLIB | Target working library where the member will be copied |
REQUEST | Optional request ID to associate the checkout with a change request |
TASKID | Optional task ID for tracking |
PWLNAME | Optional Programmer Worklist name |
LOCK | Whether to lock the member (*YES or *NO) |
COMMENT | Optional description of the reason for checkout |
How It Fits in Your Workflow
Let’s say you’re updating the ORDENTR RPGLE program in PRODLIB and want to work on it in your dev library DEVLIB. You’d run:
This securely checks out the member, logs the action, and sets you up for editing and eventual promotion.
Use CHECKOUT in batch scripts to automate source control for multiple members. Pair it with CHECKIN when you're ready to return the member to the controlled library.