The CHKOUTDFU command in TURNOVER® for iSeries v100 is used to check out a Data File Utility (DFU) program, a specialized type of object that allows direct editing of database files.
This command is part of TURNOVER’s source control system and ensures DFU programs are safely managed during development and change cycles.
CHKOUTDFU works with Date File Utility Programs:
- Copies a DFU program from a controlled library to a working library for editing
- Locks the DFU object, preventing simultaneous changes by other developers
- Tracks the checkout in TURNOVER’s audit and promotion system
- Optionally links the checkout to a request, task, or worklist item
It’s the DFU-specific counterpart to the general CHECKOUT command used for source members and other objects.
Here’s a breakdown of the key fields:
| Parameter | Description |
|---|---|
DFUNAME | Name of the DFU program to check out |
LIBRARY | Controlled library where the DFU currently resides |
TGTLIB | Target working library where the DFU 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 |
COMMENT | Optional description of the reason for checkout |
Let’s say you need to modify a DFU program called EDITCUST in library PRODLIB. You’d run:
CHKOUTDFU DFUNAME(EDITCUST) LIBRARY(PRODLIB) TGTLIB(DEVLIB) REQUEST(RQ45678) COMMENT('Update DFU logic for customer file edits')
This securely checks out the DFU program, logs the action, and sets you up for editing and eventual check-in or promotion.
- Always validate DFU logic in a test environment before promoting.
- Use
CHKINDFUto return the DFU to the controlled library once changes are complete. - Great for scripting DFU lifecycle management in your RPGLE modernization tutorials.