Convert Overlay to PFM (CVTOVLPFM)
| Where allowed to run: All environments (*ALL) Threadsafe: No |
Parameters Examples Error messages |
Convert Overlay to PFM
This command allows you to convert an overlay to a member in a physical database file.
Error messages for CVTOVLPFM
*ESCAPE Messages
- AFP0010
- An error occurred.
| Top |
Parameters
| Keyword | Description | Choices | Notes |
|---|---|---|---|
| OVL | Overlay | Qualified object name | Required, Positional 1 |
| Qualifier 1: Overlay | Name | ||
| Qualifier 2: Library | Name, *LIBL, *CURLIB | ||
| DTAFMT | Format of data | *FIXED, *CONTINUOUS | Required, Positional 2 |
| FILE | To file | Qualified object name | Required, Positional 3 |
| Qualifier 1: To file | Name, *VM, *MVS | ||
| Qualifier 2: Library | Name, *CURLIB | ||
| MBR | To member | Name, *OVL | Optional, Positional 4 |
| TEXT | Text 'description' | Character value, *OVLTXT | Optional |
| REPLACE | Replace | *YES, *NO | Optional |
| CRTFILE | Create file | *YES, *NO | Optional |
| FILETEXT | Text 'description' | Character value, *BLANK | Optional |
| Top |
Overlay (OVL)
Specifies the qualified name of the overlay that is converted. This is a required parameter.
The possible library values are:
- *LIBL
- The library list is used to locate the overlay.
- *CURLIB
- The current library for the job is used to locate the overlay. If no library is specified as the current library for the job, QGPL is used.
- library-name
- Specify the library where the overlay resides.
| Top |
Format of data (DTAFMT)
Specifies how data are filled in a physical file member.
The possible values are:
- *FIXED
- One record has one structured field. The padding character is binary 0s. The record length of the file using fixed format is the longest length of the AFPDS structured fields in the overlay or the page segment. If the length of the existing file is smaller than the longest length of the structured field, an error message is displayed. If the length of the existing file is larger than the longest length of the structured field, padding characters are added to the end of the records. This format is for the VM system or the MVS system.
- *CONTINUOUS
- The structured fields are filled continuously and folded. Only the last record has padding characters; the padding characters are binary 0s. Any record length of the existing file is allowed. The created record length of the file is 256 bytes. This format is for the OS/2 system.
This is a required parameter.
| Top |
File (FILE)
Specifies the qualified name of the physical file being used to fill the overlay data.
The possible values are:
- *VM
- Specifies that the name OVLY38PP is used. It will be a valid filetype for an overlay on the VM system.
- *MVS
- Specifies that the name O1xxxxxx is used. The 'xxxxxx' is the first six valid characters of the name specified in the OVL parameter. It will be a valid member name for an overlay on the MVS system.
- physical-file-name
- Type the name of a physical file used to fill the overlay data.
The possible library values are:
- *CURLIB
- The current library for the job is used to locate the file. If no library is specified as the current library for the job, QGPL is used.
- library-name
- Specify the library where the file resides.
| Top |
Member (MBR)
Specifies the name of the physical file member which is filled with the overlay data.
The possible values are:
- *OVL
- Specifies the name of the overlay specified in the OVL parameter.
- member-name
- Specify the name of a member used to fill the overlay data.
| Top |
Text 'description' (TEXT)
Specifies text that briefly describes the member and its function.
The possible values are:
- *OVLTXT
- Specifies the same description specified in the OVL parameter.
- 'description'
- Specifies no more than 50 characters of text, enclosed in apostrophes.
| Top |
Replace (REPLACE)
Specifies whether or not the physical file member replaces the existing physical file member if a physical file member of the same name already exists in the library.
The possible values are:
- *NO
- A new physical file member is not created if an old physical file member of the same name already exists in the library.
- *YES
- A new physical file member is created and the old physical file member is replaced by it.
| Top |
Create file (CRTFILE)
Specifies whether or not the file is created if the file does not exist.
The possible values are:
- *NO
- Do not create the file.
- *YES
- Create the file.
| Top |
Text 'description' (FILETEXT)
Specifies text that briefly describes the file and its function. This prompt is valid only when CRTFILE parameter is *YES.
The possible values are:
- *BLANK
- No text is specified.
- 'description'
- Specifies no more than 50 characters of text, enclosed in apostrophes.
| Top |
Examples
None| Top |
| Top |