|
- MONITOR_EDIT_MACRO_COMMANDS
- Should the ISPF Activity Monitoring Exit be invoked for ISREDIT
commands invoked from an ISPF Edit Macro. Valid values are YES and
NO.
The default is NO.
- ALLOW_SUBMIT_FROM_BROWSE
- Should users be allowed to issue the SUBMIT command from with
a Browse session. Valid values are YES and NO.
The default is
YES.
- ALLOW_SUBMIT_FROM_VIEW
- Should users be allowed to issue the SUBMIT command from with
a View session. Valid values are YES and NO.
The default is YES.
- WARN_ON_RENAME_TO_GDG_NAME
- Should a warning panel be displayed when a user attempts to rename
a data set to a new name that matches the naming convention of a GDG
generation. The renamed data set may become a valid generation if
it matches the naming convention of an existing GDG data set. If that
new generation causes the LIMIT parameter value specified when the
GDG was defined to be exceeded, the system will take action based
on the SCRATCH/NOSCRATCH and EMPTY/NOEMPTY parameters that were specified
when the GDG was defined. This action may result in one or all of
the existing generations being deleted or uncataloged. Valid values
are YES and NO.
The default is YES.
- DEFAULT_EDIT/BROWSE/VIEW_MEMBER_LIST
- Should option 3.4 (Data Set List utility) use the enhanced member
list for the Edit, Browse and View actions. Performance is improved
if the traditional member list ID used, but capability is improved
using the enhanced member list. Valid values are YES and NO.
The
default is YES.
- IS_VIEW_SUPPORTED
- Should users be allowed to use the View function from option 1
or only the Browse function. Because it is based on ISPF Edit, View
can impact system resource utilization. Valid values are YES and NO.
The default is YES.
- USE_ALTERNATE_PANEL_ISRTSOA
- Should alternate ISPF Command Shell panel ISRTSOA be used in place
of panel ISRTSO. ISRTSOA contains both an ISPF command line and a
TSO command line, ISRTSO contains only one input field for both ISPF
and TSO commands. Valid values are YES and NO.
The default is
NO.
- PRINT_USING_ICF
- Indicates whether foreground print requests should be processed
using an ICF printer definition. Valid values are YES and NO.
The
default is NO.
- DISALLOW_WILDCARDS_IN_HLQ
- Indicates whether wildcards (* or %) are allowed in the high-level
qualifier for data set list. Valid values are YES and NO.
The
default is NO.
- MAXIMUM_NUMBER_OF_SPLIT_SCREENS
- Maximum number of separate logical screens a user can have active.
The maximum value for this field is 32, and minimum value is 4.
The
default is 8.
- APPLID_FOR_USER_COMMAND_TABLE
- The application ID for 1 to 3 user command tables. The application
ID must be 1 to 4 alphanumeric or special characters, with the first
character being either alphabetic or a special character. The application
ID values can be specified in either of the formats:
- User
- to specify a single application ID.
- (usr1) or (usr1,usr2) or (usr1,usr2,usr3)
- to specify 1 to 3 application IDs.
The default value is
NONE (no user command tables).
In addition, a special format
can be used to obtain the application ID from the current system name
(ISPF dialog variable ZSYSID). The special format is: *, *m, or *m:n.
As
the system name can be up to 8 characters, m and n are
the start and end positions within the system name used to determine
the application ID for the user command tables. The values for m and n must
be in the range 1 to 8, where m is less
than or equal to n and the difference in
their values is no more than 3.
The default value for m is
1. The default value for n is m+3,
to a maximum value of 8.
- Compatibility Issue:
- For compatibility of the ISPF configuration options with previous
releases, do not specify any of the special formats (*, *m, or *m:n)
as either the first user or site application ID.
- APPLID_FOR_SITE_COMMAND_TABLE
- The application ID for 1 to 3 site command tables. The application
ID must be 1 to 4 alphanumeric or special characters, with the first
character being either alphabetic or a special character. The application
ID values can be specified in either of the formats:
- Site
- to specify a single application ID.
- (sit1) or (sit1,sit2) or (sit1,sit2,sit3)
- to specify 1 to 3 application IDs.
The default value is
NONE (No site-wide command tables).
In addition, a special
format can be used to obtain the application ID from the current system
name (ISPF dialog variable ZSYSID). The special format is: *, *m, or *m:n.
As
the system name can be up to 8 characters, m and n are
the start and end positions within the system name used to determine
the application ID for the site command tables. The values for m and n must
be in the range 1 to 8, where m is less
than or equal to n and the difference in
their values is no more than 3.
The default value for m is
1. The default value for n is m+3,
to a maximum value of 8.
- Compatibility Issue:
- For compatibility of the ISPF configuration options with previous
releases, do not specify any of the special formats (*, *m, or *m:n)
as either the first user or site application ID.
- SITE_COMMAND_TABLE_SEARCH_ORDER
- Determines whether the site-wide command tables are searched before
or after the default ISP command table. Valid values are AFTER and
BEFORE.
The default is BEFORE.
Depending on this setting,
the search order will be: Table 1. Search order detailsSearch Order = BEFORE |
Search Order = AFTER |
---|
1. Application |
1. Application |
2. USER (1 to 3) |
2. USER (1 to 3) |
3. SITE (1 to 3) |
3. System |
4. System |
4. SITE (1 to 3) |
- YEAR_2000_SLIDING_RULE
- The cutoff value used by ISPF to determine whether a 2-character
year date specified to ISPF should be considered a 19xx or 20xx date.
Values less than or equal to this date will be considered 20xx, values
greater will be considered 19xx. Value can be an absolute number or
a number preceded by a minus sign to indicate the cutoff should be
the specified number of years before the current year. For example,
specifying 72 indicates that any 2-character year less than or equal
to 72 should be considered 20xx, anything greater should be 19xx.
Specifying -40 (assuming the current year is 1999) will yield a cutoff
value of 59.
The default is 65.
- SHOW_ENQ_DISPLAYS
- Used to indicate that users should not be able to see who has
existing data set ENQs when they press the help key or when they use
the ISRDDN utility.
The default is blank.
- DEFAULT_SESSION_LANGUAGE
- Selects the language to use as the default language for ISPF.
The value chosen will be the language used by ISPF if no language
is specified on invocation. Valid values are:
- English
- Uppercase English
- German
- Swiss German
- Japanese
The default is 1 (English).
- PATHNAME_SUBSTITUTION_CHARACTER
- This field defines the character which can be used to represent
the full path name of a selected file. This character shows the position
of the file name when it is specified as an argument in a z/OS® UNIX command,
TSO command, CLIST, or REXX exec. The substitution character can be
used with commands that are invoked through the z/OS UNIX Directory
List utility (ISPF option 3.17).
The default character is ! (exclamation
point).
- NUMBER_OF_ROWS_FOR_TBADD
- The number of rows to be used in calculating the amount of storage
required when a TBADD service is invoked. The value can be an integer
from 1 to 1000.
The default is 1.
- RETRIEVE_COMMAND_STACK_SIZE
- The size, in bytes, of the command stack that RETRIEVE command
uses. ISPF uses the command stack to hold commands (stripped of leading
and trailing blanks) and some ISPF internal information. A stack of
512 bytes holds approximately 20 commands with a length of 10 characters
each. The value can be an integer from 312 to 4096.
The default
is 512.
- ENABLE_ISPF_EXITS
- Indicates whether exit routines are available:
- YES
- Indicates that installation-written routines are provided or planned,
and that the ISPEXITS load module is to be loaded at ISPF initialization.
If you plan to use exit routines but those routines have not been
written, you can code YES for this field, causing the IBM-provided
defaults module, ISPEXITS, to be loaded. Later, you can replace ISPEXITS
without having to repeat this part of the installation process.
- NO
- Indicates that exit routines are not provided or planned, and
that ISPEXITS is not to be loaded, reducing startup time.
The default is NO.
- ENABLE_XTIOT
- Indicates whether ISPF can process data sets dynamically allocated
with an XTIOT and whether ISPF itself requests an XTIOT via dynamic
allocation:
- YES
- XTIOT capability is requested. ISPF checks whether NON_VSAM_XTIOT
support has been activated before enabling XTIOT support fully. For
an explanation of this keyword in the DEVSUPxx member of parmlib,
see Chapter 18, "Using BSAM, BPAM, and QSAM support for XTIOT, uncaptured
UCBs, and DSAB above the 16 MB line" in z/OS DFSMS Using the New Functions.
The
ISRDDN utility indicates whether an allocation uses XTIOT and disables
line command input if XTIOT support is disabled.
- NO
- XTIOT data sets cannot be processed.
The default is NO.
|