VIEW FILEORG command: Difference between revisions
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
'''After this change,''' | '''After this change,''' | ||
for an in-memory file: | for an in-memory file: | ||
<small>FILEORG X'0008' (Hashed,In-Memory) File organization</small> | |||
or, for an Imagine file: | or, for an Imagine file: | ||
<sub>FILEORG X'0008' (Hashed,Imagine) File organization</sub> | <sub>FILEORG X'0008' (Hashed,Imagine) File organization</sub> | ||
Revision as of 16:00, 20 August 2026
What's New
The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.
For Example:
Before this change: FILEORG X'0008' (Hashed) File organization
After this change, for an in-memory file:
FILEORG X'0008' (Hashed,In-Memory) File organization
or, for an Imagine file: FILEORG X'0008' (Hashed,Imagine) File organization
Note: Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.
Benefit
In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.
Compatibility Notes ===
• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged. • Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.