19.8.2 – Description
The SET FILE/RU_JOURNAL command marks an RMS file for recovery
unit journaling. To use recovery unit journaling for a data file,
a data file must be marked for recovery unit journaling with the
SET FILE/RU_JOURNAL command, and transactions must be defined
in an application program using DECdtm transaction services. You
can also use this command to specify the default volume on which
recovery unit journals will be created for this file.
Use the SET FILE/NORU_JOURNAL command to unmark a file for
recovery unit journaling. After you use the SET FILE/NORU_JOURNAL
command for a file, modifications to that data file will no
longer be written to a recovery unit journal.
If you wish to delete a file that has been marked for recovery
unit journaling, you must use the SET FILE/NORU_JOURNAL command
before you can delete the file.
There is no reason other than performance to keep recovery unit
journals on a different volume from the file being journaled.
Unlike after-image journaling, which protects against a system
failure such as a head crash that causes a loss of data, recovery
unit journaling ensures that a predefined set of operations are
either done in their entirety, or not done at all. In the event
of an abnormal termination of the application, such as a system
crash or a Ctrl/Y, any incomplete transactions are automatically
rolled back (undone). Because all recovery unit journals must
be available before the data files can be rolled back, locating
recovery unit journals on a volume where availability might be
low could reduce the availability of the data files that use
those recovery unit journals.
Specifying a location for recovery unit journals for a file
does not guarantee that the recovery unit journals will always
be located on the named device or volume. For any active
transaction, there is always only one recovery unit journal for
local files. Thus, if many files are involved in a transaction, a
single recovery unit journal is used, even if different locations
for the journals had been specified (for individual files) with
different SET FILE/RU_JOURNAL commands.
Remote files are an exception to this rule. Each remote file
associated with a transaction has its own recovery unit and
recovery unit journal. The recovery unit journal resides on the
remote system. The volume is chosen in the same way as for local
files. Remote files have no effect in determining where the local
recovery unit journal resides.
A journal is not deleted when the transaction has been completed.
Recovery unit journals are automatically deleted only when
all of the files involved in the transaction are closed and
the application exits. RMS journaling automatically creates a
recovery unit journal at run time, whenever the first record
stream associates with a transaction. All record streams in
the process associated with the same transaction share a single
recovery unit journal. Once a recovery unit journal is created,
it can be reused for another transaction by the process that
created it. A recovery unit journal is created only when there is
no available recovery unit journal opened by the process for the
current transaction.
19.8.3 – Examples
1.$ SET FILE/RU_JOURNAL FINANCE_DISK:[PAYROLL]WEEKLY.DAT
This command marks the file WEEKLY.DAT for recovery unit
journaling. Any operation within an application that modifies
this file must be in a defined transaction (defined by DECdtm
transaction services).
2.$ SET FILE/AI_JOURNAL=(FILE=JNL_DISK:, CREATE)-
_$ /RU_JOURNAL/LOG OVERDUE.DAT
%SET-I-JCREATED, journal JNL_DISK:[PAYABLE]OVERDUE.RMS$JOURNAL;1
created
%SET-I-FILMARKAI, WORK_DISK:[PAYABLE]OVERDUE.DAT;1 marked for RMS
after-image journaling
-SET-I-JFILE, using journal JNL_DISK:[PAYABLE]OVERDUE.RMS$JOURNAL;1
%SET-I-FILMARKRU, WORK_DISK:[PAYABLE]OVERDUE.DAT;1 marked for RMS
recovery-unit journaling
%SET-I-MODIFIED, WORK_DISK:[PAYABLE]OVERDUE.DAT;1 modified
$ SET FILE/AI_JOURNAL=(FILE=JNL_DISK:OVERDUE)-
_$ /RU_JOURNAL/LOG CURRENT.DAT
%SET-I-FILMARKAI, WORK_DISK:[PAYABLE]CURRENT.DAT;1 marked for RMS
after-image journaling
-SET-I-JFILE, using journal JNL_DISK:[PAYABLE]OVERDUE.RMS$JOURNAL;1
%SET-I-FILMARKRU, WORK_DISK:[PAYABLE]CURRENT.DAT;1 marked for RMS
recovery-unit journaling
%SET-I-MODIFIED, WORK_DISK:[PAYABLE]CURRENT.DAT;1 modified
In this example, the files OVERDUE.DAT and CURRENT.DAT are
marked for after-image and recovery unit journaling using two
SET FILE commands. In this example, a single journal (JNL_
DISK:[PAYABLE]OVERDUE.RMS$JOURNAL) is used for after-image
journaling.
The first SET FILE command uses the /CREATE
qualifier to create a new after-image journal, JNL_
DISK:[PAYABLE]OVERDUE.RMS$JOURNAL, for the file OVERDUE.DAT.
The file specification uses the current default directory
[PAYABLE] and the default file extension RMS$JOURNAL.
The second SET FILE command marks the file CURRENT.DAT for
after-image and recovery unit journaling, checks the disk JNL_
DISK to see whether an after-image journal already exists, and
uses the existing journal JNL_DISK:[PAYABLE]OVERDUE.RMS$JOURNAL
for the file CURRENT.DAT.
20 – HOST
Connects your terminal (through the current host processor)
to another processor, called the remote processor. The command
requires that:
o You must have an account on the remote system to log in.
o The NETMBX (network mailbox) privilege is set.
For more information about using the following qualifiers, see
help for the appropriate subtopic.
Qualifier Type of Connection
/DTE Connects your system to a remote system through an
outgoing terminal line.
/DUP Connects your terminal to a storage controller
through the appropriate bus for that controller.
/HSC Connects your terminal to an HSC disk and tape
controller through the computer interconnect (CI)
bus.
/LAT Connects your terminal to a specified service
available on the local area network (LAN).
/RLOGIN Allows you to log in to a remote host over a TCP/IP
connection and start an interactive terminal session
by accessing the RLOGIN application.
/TELNET Connects you to a remote host over a TCP/IP
connection by invoking the TELNET application.
/TN3270 Connects you to a remote IBM host over a TCP/IP
connection, causing the local keyboard to emulate
an IBM 3279-class terminal keyboard by invoking the
TN3270 terminal emulator.
Format
SET HOST node-name
20.1 – Parameter
node-name
Specifies the node name of the remote processor to which you will
connect.
20.2 – Qualifiers
20.2.1 /APPLICATION_PROTOCOL
/APPLICATION_PROTOCOL[=protocol]
Specifies the protocol connection, CTERM (CTDRIVER) or RTERM
(RTTDRIVER) on the specified node. CTERM protocol is the default
if no connection is specified.
20.2.2 /BUFFER_SIZE
/BUFFER_SIZE=n
Changes the packet size of the protocol message sent between the
terminal and the remote processor if a connection to the remote
processor is already established. The default buffer size is 1010
bytes; however, the buffer size n can range from 140 bytes to
1024 bytes. The value of the parameter n is reset to 140 bytes if
a value below 140 is specified; a value for n above 1024 bytes is
reset to 1024.
You can force the host node to write to the terminal in smaller
packets, thereby ensuring that write operations to the terminal
are displayed at more frequent intervals, by setting n to a
value just above the minimum of 140 bytes. On slow DECnet links,
setting the buffer size to a smaller value may decrease pauses
between write operations when large amounts of data are being
scrolled to the screen.
20.2.3 /LOG
/LOG[=filespec]
/NOLOG (default)
Controls whether a log file of the entire session is kept. If you
use the /LOG qualifier without the file specification, the log
information is stored in the file SETHOST.LOG.
20.2.4 /MOP
/MOP client-name
Connects your system to a remote system using the MOP protocol.
Note that this qualifier is displayed only if DECnet-Plus is
installed on your system.
For more information, type the following command:
$ $ SET PREFIX "(!%T)"
$ SET VERIFY
.
.
.
$ TEMP = F$VERIFY(PROC_VER, IMAGE_VER)
$ SET PREFIX "''HOLD_PREFIX'"
This command procedure uses the F$ENVIRONMENT lexical function
to save the current procedure and image verification setting,
as well as the current verification prefix string. The SET
PREFIX command sets the verification prefix to be used in
the current command procedure. It uses an FAO control string
to produce the time each command is read by the command
interpreter (DCL), surrounded by parentheses. Then the SET
VERIFY command turns on both procedure and image verification.
Subsequently, the F$VERIFY lexical function is used to restore
the original verification settings. The SET PREFIX command
returns the verification prefix to its previous setting. Note
how the symbol HOLD_PREFIX is used in the SET PREFIX command.
This preserves casing and special characters in the stored
string.
4.$ SET VERIFY
$ @TEST
$ RUN AVERAGE
1
2
3
$ EXIT
In this example, the SET VERIFY command turns procedure and
image verification on. When the command procedure TEST.COM is
executed interactively, the command lines and the data lines
for the program AVERAGE are displayed on the terminal. The data
lines were entered in the command procedure on lines that did
not begin with the DCL prompt.
5.$ SET VERIFY
$ COUNT = 1
$ IF P'COUNT' .NES. "" THEN GOTO &P'COUNT'
.
.
.
$ EXIT
When this command procedure is executed interactively, the
SET VERIFY command causes the command and data lines to be
displayed. Symbols that are substituted during the first
phase of symbol substitution (such as 'COUNT') are displayed
by the SET VERIFY command, but other symbols are not. The
following lines are displayed when this procedure is executed
interactively:
$ COUNT = 1
$ IF P1 .NES. "" THEN GOTO &P1
.
.
.
Although these values are not displayed, the value for P1 is
substituted during the third phase of symbol substitution, and
the value for &P1 is substituted during the second phase.
48 – VOLUME
Changes the characteristics of one or more mounted Files-11
volumes. The SET VOLUME command affects only the node on which
the command is issued, and will not affect any other nodes, even
when a volume is mounted on multiple nodes in an OpenVMS Cluster
configuration.
If you are not the owner of the volume, requires control access
to the volume.
Format
SET VOLUME device-name[:][,...]
48.1 – Parameter
device-name[:][,...]
Specifies the name of one or more mounted Files-11 volumes.
48.2 – Qualifiers
48.2.1 /ACCESSED
/ACCESSED[=n]
Requires OPER (operator) privilege.
Specifies the number of directories to be maintained in system
space for ready access. You can specify a value n in the range
of 0 to 255. If you specify the qualifier /ACCESSED and omit
the number of directories, a default value of 3 is used. If you
specify a value greater than the current value, the new value is
effective immediately; otherwise, the new value is not effective
until the next time the volume is mounted.
48.2.2 /CACHE
/CACHE=(option[,...])
Enables or disables XFC caching for the volume. If CLEAR_DATA
option is specified, then contents of the volume already in cache
are cleared. (If you do not specify the /CACHE qualifier, XFC
caching attributes of the volume as well as the contents of
the volume already in cache are not affected.) Keywords are as
follows:
Keyword Description
DATA Enables XFC caching for the volume.
[NO]DATA Disables XFC caching for the volume.
CLEAR_DATA Clears contents of the volume present in the XFC
cache (if any).
48.2.3 /DATA_CHECK
/DATA_CHECK[=(option[,...])]
Defines a default for data check operations following all read
and write operations to the specified volume. (If you do not
specify the /DATA_CHECK qualifier, no checks are made.) Keywords
are as follows:
[NO]READPerforms checks following all read operations.
[NO]WRITPerforms checks following all write operations (default).
48.2.4 /ERASE_ON_DELETE
/ERASE_ON_DELETE
/NOERASE_ON_DELETE (default)
Determines whether the space occupied by a file is overwritten
with a system-specified pattern when a file on the volume is
deleted.
48.2.5 /EXTENSION
/EXTENSION[=n]
Specifies the number of blocks to be used as a default extension
size for all files on the volume. You can specify a value n in
the range of 0 to 65,535. If you specify the /EXTENSION qualifier
without specifying a value, a default value of 0 (the OpenVMS RMS
default) is used.
For example, during an update operation, the extension default
is used when a file increases to a size greater than its initial
default allocation.
48.2.6 /FILE_PROTECTION
/FILE_PROTECTION=(ownership[:access][,...])
Sets the default protection to be applied to all files on the
specified disk volume. Specify the ownership parameter as system
(S), owner (O), group (G), or world (W) and the access parameter
as read (R), write (W), execute (E), or delete (D). A null access
specification means no access.
NOTE
This attribute is not used while the volume is in use on an
OpenVMS system, but the attribute is provided to control
the process use of the volume on RSX-11M systems. The
OpenVMS system always uses the default file protection;
the protection can be changed with the DCL command SET
PROTECTION/DEFAULT.
48.2.7 /HIGHWATER_MARKING
/HIGHWATER_MARKING
/NOHIGHWATER_MARKING
Determines whether the file highwater mark (FHM) volume attribute
is set. The FHM attribute guarantees that a user cannot read data
that was not written by the user. Applies to Files-11 On-Disk
Structure Level 2 (ODS-2) and 5 (ODS-5) volumes only.
48.2.8 /LABEL
/LABEL=volume-label
Specifies a 1- to 12-character ANSI name to be encoded on the
volume. The specified label remains in effect until it is changed
explicitly; dismounting the volume does not affect the label. VSI
strongly recommends that a volume label should consist of only
alphanumeric characters, dollar signs ($), underscores (_), and
hyphens (-).
NOTE
Changing the volume label does not change other structures
that used the original volume label. For example, the
DISK$label logical volume name is not changed nor is the
device-lock name that is kept internally by OpenVMS. As a
result, if you attempt to access another disk that has the
same volume label as the original volume of this device,
you may get error messages such as the following: "%MOUNT-F-
VOLALRMNT, another volume of same label already mounted".
VSI recommends that, if you change a disk volume label,
you also dismount and remount the disk on all nodes in the
cluster so that the names and locks are consistent.
If you change the volume label on a nonsystem disk and the
PRODUCT INSTALL command has been used to install software
products on that disk, you must update the software product
database to reflect this change. To accomplish this, first
dismount and remount the disk. Then use the PRODUCT REGISTER
VOLUME command to replace all occurrences of the old DISK$label
with the new logical volume name that was created by the MOUNT
command.
NOTE
You do not need to take this action when you change
the label of the system disk. The POLYCENTER Software
Installation Utility continues to use the old logical
volume name until the system is rebooted. After reboot (when
the system disk is remounted), the utility automatically
identifies the system disk using its new logical volume
name.
48.2.9 /LIMIT
/LIMIT[=n]
Specifies that the volume is to be enabled for volume expansion.
n specifies the upper limit of the expansion (in blocks). If no
value is specified, the maximum expansion potential is set up.
The maximum expansion size depends on the cluster size defined
for the volume using the INITIALIZE/CLUSTER_SIZE command. If
the cluster size is 8 or more, the current maximum expansion
supported on OpenVMS (1TB) is set up. If the cluster size is less
than 8, the expansion limit is set to 65535*4096*Cluster-size
because the maximum size of the bitmap is 65535 blocks. For more
information about volume expansion, see the VSI Volume Shadowing
for OpenVMS manual.
This command must be executed while the disk is mounted
privately.
If you add additional physical storage in the future, you can use
the /SIZE qualifier to increase the volume size.
48.2.10 /LOG
/LOG
/NOLOG (default)
Determines whether the volume specification of each volume is
displayed after the modification.
48.2.11 /MOUNT_VERIFICATION
/MOUNT_VERIFICATION
/NOMOUNT_VERIFICATION
Determines whether mount verification is enabled. Mount
verification prevents interruption to user input/output
operations and notifies the operator of problems with the disk.
48.2.12 /OWNER_UIC
/OWNER_UIC[=uic]
Sets the owner user identification code (UIC) of the volume
to the specified UIC. The default UIC is that of the current
process. Brackets ([]) are required around the UIC. Specify the
UIC by using standard UIC format as described in the VSI OpenVMS
Guide to System Security.
48.2.13 /PROTECTION
/PROTECTION=(ownership[:access][,...])
Specifies the protection to be applied to the volume. The
following rules apply:
o Specify the ownership parameter as system (S), owner (O),
group (G), or world (W).
o Specify the access parameter as read (R), write (W), create
(C), or delete (D).
The default protection is all types of access by all categories
of user.
48.2.14 /REBUILD
/REBUILD[=FORCE]
Recovers caching limits for a volume that was dismounted
improperly. If a disk volume was dismounted improperly (such
as during a system failure), and was then remounted with the
MOUNT/NOREBUILD command, you can use SET VOLUME/REBUILD to
recover the caching that was in effect at the time of the
dismount. The FORCE option forces the disk to be rebuilt
unconditionally, thus updating the free block count in the disk
volume's lock value block.
48.2.15 /RETENTION
/RETENTION=(min[,max])
Specifies the minimum and maximum retention times to be used by
the file system to determine the expiration date for files on
the volume. When a file is created, its expiration date is set
to the current time plus the maximum time. Each time the file is
accessed, the current time is added to the minimum time. If the
sum is greater than the expiration date, a new expiration date is
computed.
If you omit the maximum value, a default value that
is the smaller of (2 x min) or (min + 7) days is
used. For example, /RETENTION=3- is the same as
/RETENTION=(3-,6-), while /RETENTION=10- is the same as
/RETENTION=(10-,17-).
The command SET VOLUME/RETENTION=0 disables retention times on
the volume.
48.2.16 /SIZE
/SIZE[=nnn]
Specifies the amount of disk space (in blocks) that is usable for
the file system. This value must be greater than the current
logical volume size and less than or equal to the physical
size of the disk or the expansion limit (specified by /LIMIT),
whichever is smaller.
If the value is omitted, the usable space is increased to the
physical size of the disk or the expansion limit, whichever is
smaller.
48.2.17 /STRUCTURE_LEVEL
/STRUCTURE_LEVEL=n
Sets the structure level of the volume. Use the value 5 to set
the volume to ODS-5.
When the /STRUCTURE_LEVEL qualifier is used with other
qualifiers, the volume structure level is set prior to the other
qualifiers being performed.
You cannot use the SET VOLUME command to change a volume from
ODS-5 to ODS-2. To reset a volume to ODS-2, see the instructions
in the VSI OpenVMS System Manager's Manual, Volume 1: Essentials.
48.2.18 /SUBSYSTEM
/SUBSYSTEM
/NOSUBSYSTEM
Enables the processing of subsystem ACEs. Requires the SECURITY
privilege. By default, the disk from which you boot has protected
subsystems enabled but other disks do not. For further details on
subsystems, see the VSI OpenVMS Guide to System Security.
48.2.19 /UNLOAD
/UNLOAD (default)
/NOUNLOAD
Specifies whether the volume is unloaded (spun down) when the DCL
command DISMOUNT is entered.
48.2.20 /USER_NAME
/USER_NAME[=user-name]
Specifies a user name of up to 12 alphanumeric characters to be
recorded on the volume. The default name is the current process
user name.
48.2.21 /VOLUME_CHARACTERISTICS
/VOLUME_CHARACTERISTICS=([[NO]HARDLINKS,] [[NO]ACCESS_
DATES[=delta-time]])
Enables or disables hardlinks and automatic updates of access
dates on ODS-5 volumes.
To limit the performance impact if a file is accessed frequently,
you can suppress update of the access time if the change is
small. A delta time is used to determine when a new access time
is significant. The default value for delta-time is 1 second,
chosen to comply with the "seconds since EPOCH" time interface
required by POSIX st_atime. A site can choose a larger delta time
to reduce overhead if 1-second granularity is not required.
To disable access date support on a volume, use the SET
VOLUME/VOLUME_CHARACTERISTICS=NOACCESS_DATES command. This
command affects only the node on which the command is issued.
Other nodes are not affected by the change until the next time
the volume is mounted.
48.2.22 /WINDOWS
/WINDOWS[=n]
Specifies the number of mapping pointers to be allocated for file
windows.
The value of n can be from 7 to 80; the default value is 7.
48.2.23 /WRITETHROUGH
/WRITETHROUGH
/NOWRITETHROUGH
This qualifier only affects applications such as PATHWORKS that
can request deferred writes to file headers. You use it to
control whether these applications can use the deferred write
feature.
Use /NOWRITETHROUGH to allow these applications to use the
deferred write feature. When one of these applications explicitly
requests a deferred write when updating a file header, control
returns to the application when the I/O request has been queued;
the application does not have to wait until the data is on disk.
Note that although the SHOW DEVICES/FULL command shows the volume
status as write-back caching enabled, the extended file cache
(XFC) will still be in write-through mode.
Use /WRITETHROUGH to disable the deferred write feature, so that
no applications can use it. The SHOW DEVICES/FULL command shows
the volume status as write-through caching enabled.
The deferred write feature is not available on Files-11 ODS-1
volumes.
48.3 – Examples
1.$ SET VOLUME/DATA_CHECK=(READ,WRITE) DKA5
The SET VOLUME command in this example requests that data
checks be performed following all read and write operations
to DKA5.
2.$ SET VOLUME/FILE_PROTECTION=(S:RWED,O:RWED,G:RE,W:RE) DKA5
The SET VOLUME command in this example sets the default
protection to be applied to all files created on volume DKA5.
System (S) and owner (O) are granted all types of access;
group (G) and world (W) are permitted only to read and execute
files on DKA5.
3.$ SET VOLUME/LABEL=LICENSES DKA5
The SET VOLUME command in this example encodes the label
LICENSES on the volume DKA5. Note that if characters in labels
are entered in lowercase, they are changed to uppercase by the
/LABEL qualifier.
4.$ SET VOLUME/ACCESSED=25/USER_NAME=MANAGER/LOG DKA0:
The SET VOLUME command in this example specifies that 25
directories are to be maintained in system space for ready
access for the volume DKA0. The command also assigns the
user name MANAGER to the volume and displays the volume
specification after the volume is modified.
5.$ SET VOLUME/REBUILD/LOG NODE$DKA2:
%SET-I-MODIFIED, _NODE$DKA2: modified
The SET VOLUME command in this example causes a rebuild
operation to begin on the volume that is mounted on NODE$DKA2.
The /LOG qualifier directs the SET VOLUME command to display a
notification message.
6.$ DISMOUNT/CLUSTER/NOUNLOAD $252$DUA716:
$ MOUNT $252$DUA716: TST716
$ SET VOLUME/LIMIT $252$DUA716:
$ DISMOUNT/NOUNLOAD $252$DUA716:
$ MOUNT/CLUSTER $252$DUA716: TST716
This example shows how to increase the expansion limit of a
volume mounted in a cluster.
7.$ SET VOLUME SYS$DISK/VOLUME_CHARACTERISTICS=NOHARDLINKS
This command disables hard links on SYS$DISK.
8.$ SET VOLUME $DKA100/CACHE=CLEAR_DATA
This command clears the contents of the volume $DKA100 present
in the XFC cache (if any). The caching mode of the volume
$DKA100 is not altered.
9.$ SET VOLUME $DKA100/CACHE=DATA
This command enables XFC caching for the volume $DKA100. The
contents of the volume $DKA100 already present in the XFC cache
is not affected in anyway.
10$ SET VOLUME $DKA100/CACHE=(DATA,CLEAR_DATA)
This command enables XFC caching for the volume $DKA100 and
clears the contents of the volume $DKA100 present in the XFC
cache (if any).
49 – WORKING_SET
Redefines the default working set size for the process, or sets
an upper limit to which the working set size can be changed by an
image that the process executes. Working set limits cannot be set
to exceed those defined in the user authorization file (UAF).
Specify the value of n as a number of 512-byte pagelets on Alpha.
Note that the OpenVMS system rounds up this value to the nearest
CPU-specific page so that the actual amount of physical memory
allowed may be larger than the specified amount on Alpha.
Format
SET WORKING_SET
49.1 – Qualifiers
49.1.1 /ADJUST
/ADJUST (default)
/NOADJUST
Controls whether the system can automatically adjust the size of
the process working set.
49.1.2 /EXTENT
/EXTENT=n
Specifies the maximum number of physical pages that can be
resident in the working set during image execution.
The extent value must be greater than the minimum working set
defined at system generation, and it must be less than or equal
to the authorized extent defined in the UAF.
If you specify a value greater than the authorized extent, the
command sets the working set limit at the maximum authorized
value.
49.1.3 /LIMIT
/LIMIT=n
Specifies the size to which the working set is to be reduced at
image exit.
If you specify a value greater than the current quota, the quota
value is also increased.
49.1.4 /LOG
/LOG
/NOLOG (default)
Determines whether confirmation of the SET WORKING_SET command is
displayed.
49.1.5 /QUOTA
/QUOTA=n
Specifies the maximum number of physical pages that any image
executing in the process context can request. An image can set
the working set size for the process by calling the $ADJWSL
(Adjust Working Set Limit) system service.
If you specify a quota value that is greater than the authorized
quota, the working set quota is set to the authorized quota
value.
49.2 – Examples
1.$ SHOW WORKING_SET
Working Set /Limit= 150 /Quota= 700 /Extent= 700
Adjustment enabled Authorized Quota= 700 Authorized Extent= 700
$ SET WORKING_SET/QUOTA=1000
%SET-I-NEWLIMS, new working set: Limit = 150 Quota = 700 Extent = 700
The SHOW WORKING_SET command in this example displays the
current limit, quota, and extent, as well as the authorized
quota and authorized extent. The SET WORKING_SET command
attempts to set a quota limiting the maximum number of pages
any image can request that is greater than the authorized
quota. Note from the response that the quota was not increased.
2.$ SHOW WORKING_SET
Working Set /Limit= 150 /Quota= 350 /Extent= 350
Adjustment enabled Authorized Quota= 350 Authorized Extent= 350
$ SET WORKING_SET/LIMIT=100
%SET-I-NEWLIMS, new working set: Limit = 100 Quota = 350 Extent = 350
$ SHOW WORKING_SET
Working Set /Limit= 100 /Quota= 350 /Extent= 350
Adjustment enabled Authorized Quota= 350 Authorized Extent= 350
The SET WORKING_SET command in this example sets the working
set size for any image in the process to 100.