FILEMGMT overview: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (add link)
 
(16 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==Prerequisites==
==Prerequisites==
<p>In order to use FILEMGMT:</p>
<p>
In order to use FILEMGMT:</p>
<ul>
<ul>
<li>You must have Dictionary/204 and its subsystems running.</li>
<li>You must have Dictionary/204 and its subsystems running.</li>
<li>You should have an understanding of <var class="product">Model&nbsp;204</var> file management. See [[File management overview]] for details.</li>
<li>You should have an understanding of <var class="product">Model&nbsp;204</var> file management. See [[File management overview]] for details.</li>
<li>You need file management privileges and the appropriate <var class="product">Model&nbsp;204</var> privileges:  
<li>You need file management privileges and the appropriate <var class="product">Model&nbsp;204</var> privileges:  
<ul>
<ul>
<li>Creating a new <var class="product">Model&nbsp;204</var> file requires login account privileges that include superuser privileges.</li>
<li>Creating a new <var class="product">Model&nbsp;204</var> file requires login account privileges that include superuser privileges.</li>
<li> Changing an existing file requires a <var class="product">Model&nbsp;204</var> password indicating that you have the necessary update privileges for the file.</li>
<li> Changing an existing file requires a <var class="product">Model&nbsp;204</var> password indicating that you have the necessary update privileges for the file.</li>
</ul>  
</ul> </li>
</li>
</ul>
</ul>


==Overview==
==Overview==
<p>The Dictionary/204 File Management Subsystem facility, FILEMGMT, is a [[FILEMGMT screens overview|full-screen interface]] to <var class="product">Model&nbsp;204</var> file management. The facility enables you to create <var class="product">Model&nbsp;204</var> files quickly, reliably, and securely. You define a file and its contents on the series of screens that FILEMGMT provides. FILEMGMT uses your definitions to:</p>
<p>
The Dictionary/204 File Management Subsystem facility, FILEMGMT, is a [[FILEMGMT screens overview|3270-screen interface]] or a [[RKWeb|web-browser interface]] to <var class="product">Model&nbsp;204</var> file management.  
 
The FILEMGMT facility enables you to create <var class="product">Model&nbsp;204</var> files quickly, reliably, and securely. You define a file and its contents on the series of screens that FILEMGMT provides. FILEMGMT uses your definitions to:</p>
<ul>
<ul>
<li>Construct the <var class="product">Model&nbsp;204</var> commands that create the physical file</li>
<li>Construct the <var class="product">Model&nbsp;204</var> commands that create the physical file</li>
<li>Store the appropriate entries in your installation's dictionary </li>
<li>Store the appropriate entries in your installation's dictionary </li>
</ul>
</ul>
<p>By combining the two operations, FILEMGMT eliminates the need to enter this information twice. FILEMGMT validates the information for accuracy and consistency, and it creates and stores all necessary dictionary entries and references.</p>
<p>
<p>FILEMGMT does more than create new files. You can use the facility to:</p>
By combining the two operations, FILEMGMT eliminates the need to enter this information twice. FILEMGMT validates the information for accuracy and consistency, and it creates and stores all necessary dictionary entries and references.</p>
<p>
FILEMGMT does more than create new files. You can use the facility to:</p>
<ul>
<ul>
<li>View existing file data</li>
<li>View existing file data</li>
Line 29: Line 38:


==FILEMGMT maintenance functions==
==FILEMGMT maintenance functions==
<p>FILEMGMT consists of the following maintenance functions:</p>
<p>
FILEMGMT consists of the following maintenance functions:</p>
<ul>
<ul>
<li>File maintenance</li>
<li>File maintenance</li>
Line 36: Line 46:
<li>Field group maintenance </li>
<li>Field group maintenance </li>
</ul>
</ul>
<p>These maintenance functions let you define FILE, FIELD, RECORD, and FIELD GROUP entries, as well as modify and delete these entries. The facility also creates the actual files, fields, records, and field groups that correspond to the dictionary entries that you have defined or modified.</p>
<p>
<p>Each maintenance function has its own full-screen interface that you can select from the FILEMGMT primary screen. Using the facility screens you can specify the characteristics and relationships of your files, fields, records, and field groups. The FILEMGMT facility also sizes files automatically based on information you provide about file characteristics. The section [[ Managing file and table size with FILEMGMT#File sizing overview|File sizing overview]] explains in more detail how file sizing works.</p>
These maintenance functions let you define FILE, FIELD, RECORD, and FIELD GROUP entries, as well as modify and delete these entries. The facility also creates the actual files, fields, records, and field groups that correspond to the dictionary entries that you have defined or modified.</p>
<p>
Each maintenance function has its own full-screen interface that you can select from the FILEMGMT primary screen. Using the facility screens you can specify the characteristics and relationships of your files, fields, records, and field groups. The FILEMGMT facility also sizes files automatically based on information you provide about file characteristics. The section [[ Managing file and table size with FILEMGMT#File sizing overview|File sizing overview]] explains in more detail how file sizing works.</p>
 
==FILEMGMT and command execution==
==FILEMGMT and command execution==
<p>After you have defined the characteristics and relationships of an entry, FILEMGMT stages your entry for the specified commands. The commands can be executed in one of four active or inactive modes, depending upon the execution options that are supported at your installation. Your dictionary administrator selects a default mode, but you can override that selection with another supported option. The section [[#Dictionary/204 and staging|Dictionary/204 and staging]] explains the execution options in detail.</p>
<p>
<p>When the commands are executed, FILEMGMT creates the file, field, record, or field group as you have defined it. The facility also creates the corresponding (nonstaged) dictionary entry. The section [[#Staging entries|Staging entries]] explains staged and nonstaged entries.</p>
After you have defined the characteristics and relationships of an entry, FILEMGMT stages your entry for the specified commands. The commands can be executed in one of four active or inactive modes, depending upon the execution options that are supported at your installation. Your dictionary administrator selects a default mode, but you can override that selection with another supported option. The section [[#Dictionary/204 and staging|Dictionary/204 and staging]] explains the execution options in detail.</p>
<p>
When the commands are executed, FILEMGMT creates the file, field, record, or field group as you have defined it. The facility also creates the corresponding (non-staged) dictionary entry. The section [[#Staging entries|Staging entries]] explains staged and non-staged entries.</p>
<p>If it becomes necessary to modify an existing file, FILEMGMT locks all the file, field, record, and field group definitions for that file to protect the integrity of the dictionary data. The section [[#File locking|File locking]] explains file locking.</p>
<p>If it becomes necessary to modify an existing file, FILEMGMT locks all the file, field, record, and field group definitions for that file to protect the integrity of the dictionary data. The section [[#File locking|File locking]] explains file locking.</p>
===Staging entries===
===Staging entries===
<p>FILEMGMT coordinates these general activities:</p>
<p>
FILEMGMT coordinates these general activities:</p>
<ul>
<ul>
<li>Construction and execution of <var class="product">Model&nbsp;204</var> commands</li>
<li>Construction and execution of <var class="product">Model&nbsp;204</var> commands</li>
<li>Storage of entries in your installation's dictionary </li>
<li>Storage of entries in your installation's dictionary </li>
</ul>
</ul>
<p>The activities can be completed in a single FILEMGMT session or can be performed across multiple sessions. A dictionary entry containing your specifications is staged until all commands pertaining to the entry are executed. The entry is described as existing once execution is completed.</p>
<p>
<p>Some FILEMGMT functions let you operate on staged entries; others do not. The following descriptions of the FILEMGMT screens specify the circumstances under which you can redefine, delete, and rename staged entries.</p>
The activities can be completed in a single FILEMGMT session or can be performed across multiple sessions. A dictionary entry containing your specifications is staged until all commands pertaining to the entry are executed. The entry is described as existing once execution is completed.</p>
<p>
Some FILEMGMT functions let you operate on staged entries; others do not. The following descriptions of the FILEMGMT screens specify the circumstances under which you can redefine, delete, and rename staged entries.</p>
 
====Dictionary/204 and staging====
====Dictionary/204 and staging====
<p>Internally, Dictionary/204 manages staging by supporting two copies of every dictionary entry affected by your request. For example, if you are performing a file recreate, your request might affect entries of the following entity types in your installation's dictionary:</p>
<p>
Internally, Dictionary/204 manages staging by supporting two copies of every dictionary entry affected by your request. For example, if you are performing a file recreate, your request might affect entries of the following entity types in your installation's dictionary:</p>
<p class="code">FILE
<p class="code">FILE
FIELD
FIELD
Line 57: Line 78:
FIELD GROUP
FIELD GROUP
</p>
</p>
<p>Copies of these entries exist until your commands have been executed. The copies have the entity types of:</p>
<p>
Copies of these entries exist until your commands have been executed. The copies have the entity types of:</p>
<p class="code">STAGED FILE
<p class="code">STAGED FILE
STAGED FIELD
STAGED FIELD
Line 63: Line 85:
STAGED FIELD GROUP  
STAGED FIELD GROUP  
</p>
</p>
<p>The two copies are identical except that the staged version contains:</p>
<p>
The two copies are identical except that the staged version contains:</p>
<table>
<table>
<tr>
<tr>
Line 69: Line 92:
<td>Specifies the command to be generated</td>
<td>Specifies the command to be generated</td>
</tr>
</tr>
<tr>
<tr>
<td>COMMAND STATE attribute</td>
<td>COMMAND STATE attribute</td>
Line 74: Line 98:
</tr>
</tr>
</table>
</table>
<p>A file create request, unlike a file recreate, has only staged entries.</p>
<p>
<p>FILEMGMT copies an existing (or nonstaged) entry to a staged entry when you initiate a change to a file, field, record, or field group. When all relevant commands have been executed, FILEMGMT copies the staged entry to a nonstaged entry by deleting the nonstaged entry and renaming the staged entry as nonstaged.</p>
A file create request, unlike a file recreate, has only staged entries.</p>
===Executing commands===
<p>
<p>FILEMGMT constructs <var class="product">Model&nbsp;204</var> commands from the information you enter. The commands, when executed, perform the functions you requested from the primary screen.</p>
FILEMGMT copies an existing (or non-staged) entry to a staged entry when you initiate a change to a file, field, record, or field group. When all relevant commands have been executed, FILEMGMT copies the staged entry to a non-staged entry by deleting the non-staged entry and renaming the staged entry as non-staged.</p>
<p>The execution of a command depends upon the following factors:</p>
 
===How commands are executed===
<p>
FILEMGMT constructs <var class="product">Model&nbsp;204</var> commands from the information you enter. The commands, when executed, perform the functions you requested from the primary screen.</p>
<p>
The execution of a command depends upon the following factors:</p>
<ul>
<ul>
<li>Completeness of the request for a FILEMGMT function
<li>Completeness of the request for a FILEMGMT function
<p>For example, a file create function is not complete when you finish entering a file description, because the file must be sized. FILEMGMT must complete the description to construct the <var class="product">Model&nbsp;204</var> commands that perform the create operation.</p>
<p>
<p>Until your request is completely specified, and until the commands constructed from the request have actually been executed, your request is considered to be staged.</p>
For example, a file create function is not complete when you finish entering a file description, because the file must be sized. FILEMGMT must complete the description to construct the <var class="product">Model&nbsp;204</var> commands that perform the create operation.</p>
<p>To execute the commands, you advance to the Execute Commands screen, select the <var class="product">Model&nbsp;204</var> commands that are waiting to be executed, and press the PF6 (EXEcute) key.</p>
<p>
Until your request is completely specified, and until the commands constructed from the request have actually been executed, your request is considered to be staged.</p>
<p>To execute the commands, you advance to the Execute Commands screen, select the <var class="product">Model&nbsp;204</var> commands that are waiting to be executed, and press the F6 (EXEcute) key.</p>
</li>
</li>
<li>Execution option you select
<li>Execution option you select
<p>When Dictionary/204 is installed, the dictionary administrator determines which execution options are available to FILEMGMT users and which one is the default option. The execution option determines how staged <var class="product">Model&nbsp;204</var> commands are executed on the Execute Commands screen.</p>
<p>
When Dictionary/204 is installed, the dictionary administrator determines which execution options are available to FILEMGMT users and which one is the default option. The execution option determines how staged <var class="product">Model&nbsp;204</var> commands are executed on the Execute Commands screen.</p>
<p>The execution options are:</p>
<p>The execution options are:</p>
</li>
<ul>
<li>Active immediate</li>
<li>Active immediate</li>
<li>Active delayed</li>
<li>Active delayed</li>
<li>Inactive with commands written to a procedure file</li>
<li>Inactive with commands written to a procedure file</li>
<li>Inactive with commands written to a directed output file </li>
<li>Inactive with commands written to a directed output file </li>
</ul></li>
</ul>
</ul>
<p>Dictionary/204 provides an option for requiring that all commands against files be executed through the FILEMGMT interface.   </p>
<p>
Dictionary/204 provides an option for requiring that all commands against files be executed through the FILEMGMT interface. See [[Dictionary/204 administration#File Management options|File Management options]].</p>
 
====Execution options====
====Execution options====
<p>The options provided by FILEMGMT are listed in the following table. They are more fully described again in the section "Execute Commands screen".</p>
<p>
<b>Note</b>
The options provided by FILEMGMT are listed in the following table. They are more fully described again in [[Executing and deleting commands with FILEMGMT#Execute Commands screen|Execute Commands screen]].</p>
<p>If you select Inactive mode, then the Dictionary/204 files are updated, but not the physical files.  </p>
<p class="note"><b>Note:</b>
If you select Inactive mode, then the Dictionary/204 files are updated, but not the physical files.  </p>
<table>
<table>
<tr class="head">
<tr class="head">
Line 104: Line 141:
<th>Commands selected on the Execute Commands screen are...</th>
<th>Commands selected on the Execute Commands screen are...</th>
</tr>
</tr>
<tr>
<tr>
<td>Active immediate</td>
<td>Active immediate</td>
<td>Executed as soon as FILEMGMT verifies that you have the necessary privileges to execute the commands.</td>
<td>Executed as soon as FILEMGMT verifies that you have the necessary privileges to execute the commands.</td>
</tr>
</tr>
<tr>
<tr>
<td> Active delayed</td>
<td> Active delayed</td>
<td>
<td>Updated as pending and are executed at a later time in batch mode. FILEMGMT verifies that you have the necessary privileges to execute the commands before it flags them as pending.  
<p>Updated as pending and are executed at a later time in batch mode. FILEMGMT verifies that you have the necessary privileges to execute the commands before it flags them as pending. </p>
<p>
<p>Consult the Rocket <var class="product">Model&nbsp;204</var> Installation Guide for your operating system for information about the JCL or CCAIN statements you need to include for a batch run.  </p>
Consult the Rocket <var class="product">Model&nbsp;204</var> Installation Guide for your operating system for information about the JCL or CCAIN statements you need to include for a batch run.  </p>
</td>
</td></tr>
</tr>
 
<tr>
<tr>
<td> Inactive USE file</td>
<td> Inactive USE file</td>
<td>
<td>Not executed. Instead, they are generated and written to a directed output USE file. You specify the name of this file on the Execute Commands screen. OUTFILE is the default if you do not specify a file name.
<p>Not executed. Instead, they are generated and written to a directed output USE file. You specify the name of this file on the Execute Commands screen. OUTFILE is the default if you do not specify a file name. </p>
<p>
<p>A default USE file can be defined by the dictionary administrator in the Facility Administration feature of the Dictionary Administration facility or obtained from the user's ACCOUNT entry. </p>
A default USE file can be defined by the dictionary administrator in the Facility Administration feature of the Dictionary Administration facility or obtained from the user's ACCOUNT entry. </p>
<p>The section [[ Executing and deleting commands with FILEMGMT#Execute Commands screen|Execute Commands screen]] describes the JCL you need to include for the USE file.</p>
<p>
</td>
The section [[ Executing and deleting commands with FILEMGMT#Execute Commands screen|Execute Commands screen]] describes the JCL you need to include for the USE file.</p>
</tr>
</td></tr>
 
<tr>
<tr>
<td> Inactive procedure file</td>
<td nowrap>Inactive procedure file</td>
<td>
<td>Not executed. Instead, they are generated and written to a procedure file. You specify the name of the procedure file and its password (if any) on the Execute Commands screen.  
<p>Not executed. Instead, they are generated and written to a procedure file. You specify the name of the procedure file and its password (if any) on the Execute Commands screen. </p>
<p>
<p>The dictionary administrator can define a default procedure file in the Facility Administration feature of the Dictionary Administration facility. </p>
The dictionary administrator can define a default procedure file in the Facility Administration feature of the Dictionary Administration facility. </p>
</td>
</td></tr>
</tr>
</table>
</table>
===File locking===
 
<p>FILEMGMT provides a file locking capability to control file access and enhance data integrity. While you are creating a file or making any changes to the file definition, the file lock prevents other users from changing the file's:</p>
==File locking==
<p>
FILEMGMT provides a file locking capability to control file access and enhance data integrity. While you are creating a file or making any changes to the file definition, the file lock prevents other users from changing the file's:</p>
<ul>
<ul>
<li>Definitions</li>
<li>Definitions</li>
Line 138: Line 179:
<li>Parameters and other characteristics</li>
<li>Parameters and other characteristics</li>
</ul>
</ul>
<p>The file lock is maintained until you release the file by either executing or deleting the commands that FILEMGMT constructed. Your work can span multiple FILEMGMT sessions, if desired. Dictionary/204 maintains the file lock across sessions by keeping track of the account name. Only users who log in with the appropriate account name have access to the file. </p>
<p>
<p>&nbsp;</p>
The file lock is maintained until you release the file by either executing or deleting the commands that FILEMGMT constructed. Your work can span multiple FILEMGMT sessions, if desired. Dictionary/204 maintains the file lock across sessions by keeping track of the account name. Only users who log in with the appropriate account name have access to the file. </p>
[[Category:File management]]
==Other FILEMGMT topics==
<ul>
<li>[[FILEMGMT screens overview]] </li>
<li>[[Logging on to FILEMGMT]] </li>
</ul>
 
==See also==
{{Template: Dictionary/204 topic list}}
 
[[Category:FILEMGMT application subsystem]]
[[Category:FILEMGMT application subsystem]]
[[Category: Overviews]]

Latest revision as of 00:16, 17 June 2017

Prerequisites

In order to use FILEMGMT:

  • You must have Dictionary/204 and its subsystems running.
  • You should have an understanding of Model 204 file management. See File management overview for details.
  • You need file management privileges and the appropriate Model 204 privileges:
    • Creating a new Model 204 file requires login account privileges that include superuser privileges.
    • Changing an existing file requires a Model 204 password indicating that you have the necessary update privileges for the file.

Overview

The Dictionary/204 File Management Subsystem facility, FILEMGMT, is a 3270-screen interface or a web-browser interface to Model 204 file management. The FILEMGMT facility enables you to create Model 204 files quickly, reliably, and securely. You define a file and its contents on the series of screens that FILEMGMT provides. FILEMGMT uses your definitions to:

  • Construct the Model 204 commands that create the physical file
  • Store the appropriate entries in your installation's dictionary

By combining the two operations, FILEMGMT eliminates the need to enter this information twice. FILEMGMT validates the information for accuracy and consistency, and it creates and stores all necessary dictionary entries and references.

FILEMGMT does more than create new files. You can use the facility to:

  • View existing file data
  • Reset file parameters
  • Add fields, records, and field groups to existing files
  • Calculate and change the size of a file
  • Copy files, fields, and records

FILEMGMT maintenance functions

FILEMGMT consists of the following maintenance functions:

  • File maintenance
  • Field maintenance
  • Record maintenance
  • Field group maintenance

These maintenance functions let you define FILE, FIELD, RECORD, and FIELD GROUP entries, as well as modify and delete these entries. The facility also creates the actual files, fields, records, and field groups that correspond to the dictionary entries that you have defined or modified.

Each maintenance function has its own full-screen interface that you can select from the FILEMGMT primary screen. Using the facility screens you can specify the characteristics and relationships of your files, fields, records, and field groups. The FILEMGMT facility also sizes files automatically based on information you provide about file characteristics. The section File sizing overview explains in more detail how file sizing works.

FILEMGMT and command execution

After you have defined the characteristics and relationships of an entry, FILEMGMT stages your entry for the specified commands. The commands can be executed in one of four active or inactive modes, depending upon the execution options that are supported at your installation. Your dictionary administrator selects a default mode, but you can override that selection with another supported option. The section Dictionary/204 and staging explains the execution options in detail.

When the commands are executed, FILEMGMT creates the file, field, record, or field group as you have defined it. The facility also creates the corresponding (non-staged) dictionary entry. The section Staging entries explains staged and non-staged entries.

If it becomes necessary to modify an existing file, FILEMGMT locks all the file, field, record, and field group definitions for that file to protect the integrity of the dictionary data. The section File locking explains file locking.

Staging entries

FILEMGMT coordinates these general activities:

  • Construction and execution of Model 204 commands
  • Storage of entries in your installation's dictionary

The activities can be completed in a single FILEMGMT session or can be performed across multiple sessions. A dictionary entry containing your specifications is staged until all commands pertaining to the entry are executed. The entry is described as existing once execution is completed.

Some FILEMGMT functions let you operate on staged entries; others do not. The following descriptions of the FILEMGMT screens specify the circumstances under which you can redefine, delete, and rename staged entries.

Dictionary/204 and staging

Internally, Dictionary/204 manages staging by supporting two copies of every dictionary entry affected by your request. For example, if you are performing a file recreate, your request might affect entries of the following entity types in your installation's dictionary:

FILE FIELD RECORD FIELD GROUP

Copies of these entries exist until your commands have been executed. The copies have the entity types of:

STAGED FILE STAGED FIELD STAGED RECORD STAGED FIELD GROUP

The two copies are identical except that the staged version contains:

COMMAND attribute Specifies the command to be generated
COMMAND STATE attribute Indicates the status of the command

A file create request, unlike a file recreate, has only staged entries.

FILEMGMT copies an existing (or non-staged) entry to a staged entry when you initiate a change to a file, field, record, or field group. When all relevant commands have been executed, FILEMGMT copies the staged entry to a non-staged entry by deleting the non-staged entry and renaming the staged entry as non-staged.

How commands are executed

FILEMGMT constructs Model 204 commands from the information you enter. The commands, when executed, perform the functions you requested from the primary screen.

The execution of a command depends upon the following factors:

  • Completeness of the request for a FILEMGMT function

    For example, a file create function is not complete when you finish entering a file description, because the file must be sized. FILEMGMT must complete the description to construct the Model 204 commands that perform the create operation.

    Until your request is completely specified, and until the commands constructed from the request have actually been executed, your request is considered to be staged.

    To execute the commands, you advance to the Execute Commands screen, select the Model 204 commands that are waiting to be executed, and press the F6 (EXEcute) key.

  • Execution option you select

    When Dictionary/204 is installed, the dictionary administrator determines which execution options are available to FILEMGMT users and which one is the default option. The execution option determines how staged Model 204 commands are executed on the Execute Commands screen.

    The execution options are:

    • Active immediate
    • Active delayed
    • Inactive with commands written to a procedure file
    • Inactive with commands written to a directed output file

Dictionary/204 provides an option for requiring that all commands against files be executed through the FILEMGMT interface. See File Management options.

Execution options

The options provided by FILEMGMT are listed in the following table. They are more fully described again in Execute Commands screen.

Note: If you select Inactive mode, then the Dictionary/204 files are updated, but not the physical files.

Option Commands selected on the Execute Commands screen are...
Active immediate Executed as soon as FILEMGMT verifies that you have the necessary privileges to execute the commands.
Active delayed Updated as pending and are executed at a later time in batch mode. FILEMGMT verifies that you have the necessary privileges to execute the commands before it flags them as pending.

Consult the Rocket Model 204 Installation Guide for your operating system for information about the JCL or CCAIN statements you need to include for a batch run.

Inactive USE file Not executed. Instead, they are generated and written to a directed output USE file. You specify the name of this file on the Execute Commands screen. OUTFILE is the default if you do not specify a file name.

A default USE file can be defined by the dictionary administrator in the Facility Administration feature of the Dictionary Administration facility or obtained from the user's ACCOUNT entry.

The section Execute Commands screen describes the JCL you need to include for the USE file.

Inactive procedure file Not executed. Instead, they are generated and written to a procedure file. You specify the name of the procedure file and its password (if any) on the Execute Commands screen.

The dictionary administrator can define a default procedure file in the Facility Administration feature of the Dictionary Administration facility.

File locking

FILEMGMT provides a file locking capability to control file access and enhance data integrity. While you are creating a file or making any changes to the file definition, the file lock prevents other users from changing the file's:

  • Definitions
  • Fields, records, and field groups
  • Parameters and other characteristics

The file lock is maintained until you release the file by either executing or deleting the commands that FILEMGMT constructed. Your work can span multiple FILEMGMT sessions, if desired. Dictionary/204 maintains the file lock across sessions by keeping track of the account name. Only users who log in with the appropriate account name have access to the file.

Other FILEMGMT topics

See also