|
|
|
Indicates whether your product region attempts to reopen the VTAM ACB. If YES, the system attempts to open the VTAM ACB during initialization. The system also attempts to reopen the ACB if it is closed at some time during normal processing (for example, if VTAM is shut down), at 30-second intervals.
Default: YES
Sets the option for consoles to use SAF UTOKENs, which requires the use of a user security exit that returns UTOKENs.
Note: UTOKEN usage is supported for both JES and EXTMCS consoles.
This operand cannot be changed when AOM is active or when consoles are acquired.
Default: YES
Specifies the maximum time (in seconds) that the SYSCMD facility allows for any one multiline WTO to be collected completely. If this time-out value is exceeded and the end line is not seen, the multiline WTO undergoes further processing by AOMPROC, and so on.
Default: 5
Limits: 2 to 60
Specifies if the JES job ID is to prefix the message text when displayed at an OCS screen, for messages sourced by an z/OS system. The value of this parameter is used to set the message prefixing actions when a new OCS or NCL &INTCMD environment is created.
Default: YES
Specifies if the z/OS job name is to prefix the message text when displayed at an OCS screen, for messages sourced by an z/OS system. The value of this parameter is used to set the message prefixing actions when a new OCS or NCL &INTCMD environment is created.
Default: NO
Specifies if the minor lines of z/OS-sourced multiline WTO messages are to have SYSCMD prefixes inserted when displayed. The value of this parameter is used to set the message prefixing actions when a new OCS or NCL &INTCMD environment is created.
Default: NO
Specifies whether to prefix the originating system name to the message when it is delivered to an OCS window. The value of this parameter is used to set the message prefixing actions when a new OCS or NCL &INTCMD environment is created.
Default: NO
Specifies if the time the message was issued is to prefix the message text when displayed at an OCS screen. The value of this parameter is used to set the message prefixing actions when a new OCS or NCL &INTCMD environment is created.
AOMPRFTM=YES or AOMPRFTM=HMS causes the time to be displayed as hh:mm:ss.
AOMPRFTM=HM causes the time to be displayed as hh:mm.
Default: YES
Specifies the subsystem ID for use by the SYSCMD facility. The asterisk (*) uses the first four characters of the job name or started task (STC) name.
Default: NETM
Specifies whether the message tracing is to be active (for the number of messages defined in AOMTRLIM).
If YES, all messages from the local operating system are logged with trace information.
Default: NO
Specifies, for messages traced by AOMTRACE, how the message routing codes are to be formatted.
AOMTRCRC=HEX (the default) displays the routing codes in HEX format, showing 32 hexadecimal digits (corresponding to 16 bytes, or 128 bits, of routing codes).
AOMTRCRC=LIST displays the routing codes in list format, with numbers or ranges of numbers indicating the routing codes.
Default: HEX
Specifies the tracing limit. When reached, AOMTRACE is set to NO.
Default: 100
Limits: 1 to 100
If an unrecognized command string is entered from an OCS terminal, this operand specifies whether your product region assumes that it is the name of an NCL procedure which it then attempts to execute.
If AUTOEXEC=NO is specified, unrecognized strings are rejected with an error message.
If AUTOEXEC=YES is specified and the string is a potential NCL procedure name (that is, a valid member name), your region generates a START command for commands entered from OCS or an EXEC command for commands issued by an NCL procedure. If the string is not the name of a defined NCL procedure the command is then rejected.
Default: YES
Specifies whether a START command recognizes and executes a data set member as REXX procedure:
Default: NO
Specifies whether subpool zero is to be shared between &CALL subtasks and your product region's main task.
When &CALL statements are executed, a subtask is attached to execute the target load module. By default, the subtask does not share subpool zero with the main task. However, if multiple called modules open and process the same VSAM data set, VSAM can suffer abends unless subpool zero is shared.
Default: NO
Specifies the time (in seconds) your product region waits before sending output to an OCS terminal when a user is entering input on the keyboard.
OCS terminals can receive unsolicited output at any time. If a user is entering input on the keyboard and output becomes available, a contention condition arises (on SNA terminals) which prevents a terminal from accepting output until input is complete.
This contention is broken if it continues for more than the CDELAY interval by interrupting the keyboard input and forcing the available output to the terminal. Therefore, the CDELAY parameter should be set to an interval that provides a reasonable period for uninterrupted entry of commands on the keyboard without causing excessive delay before output can be sent. The default value of 15 seconds is usually adequate. CDELAY also applies to NCL panel display.
Default: 15
Limits: 0 to 300
Specifies the name of the CNM ACB.
Limits: One to eight characters
Specifies whether your product region is to write message N07002 to the activity log each time a terminal is connected to the system.
If using EASINET, this message occurs each time a terminal is returned to EASINET control after being logged on to another application. The LOGPROC NCL procedure can intercept these messages and retain statistics on terminal usage and the length of time terminals remain connected to other applications.
Default: NO
Specifies whether to request deferred mounting when allocating data sets.
Default: NO
Specifies whether automatic RACF resource protection is requested when dynamically allocating new data sets.
Default: NO
Specifies whether data sets created by dynamic allocation are defined with the RLSE option to free unused secondary extents.
Default: NO
Defines the operating system descriptor codes used for messages sent to the system console, including messages associated with the ppppOPER user ID. Specify NONE to cancel any previously set description codes.
Note: For an explanation of the impact of specifying certain codes, see the appropriate operating system documentation.
Default: NONE
Limits: 1 to 16 and NONE
Controls the format of generated ISPF statistics when Dataset Services is used to create or update a PDS member.
Default: STD
Specifies the maximum number of dynamic INMC links that can be active at the same time. Enter 0 to prevent any dynamic links from being established and to disable the dynamic facility.
Default: 10
Specifies the default setting for the CAPS command when using Panel Services. OFF specifies that entered data is to be retained in upper and lower case format. ON specifies that entered data is to be converted to upper case. The default attribute can be changed during editing by the CAPS command. When a member is saved, Edit Services retains the current CAPS setting and reinstated that value when the member is next edited regardless of the setting of the EDITCAPS operand.
Default: OFF
Specifies the default setting for the NULLS command when using Panel Services. If OFF is specified, trailing blanks are retained on each edit line. If ON is specified, trailing blanks on each edit line are converted to nulls (X'00') before being displayed for editing. Using nulls on an edit line lets you use the insert key to insert data amongst other text on the line. Use the NULLS command to change the default attribute while editing.
When a member is saved, Panel Services retains the current NULLS setting and reinstates that value when the member is next edited, regardless of the setting for the EDITNULL operand.
Default: ON
Determines the minimum repeat period (in seconds) permitted for an EVERY command. This can be used to stop the system from being flooded with timer commands inadvertently. If a value of 0 is specified, an EVERY command is executed immediately.
Default: 10
Limits: 0 to 300
Specifies the name of an NCL procedure that intercepts commands issued on completion of system transmissions.
These commands are executed under the control of the background system (BSYS) environment, subject to BSYS's authorization level. If a greater degree of control over these commands is required, you can write an NCL procedure (an FTSCPROC) that is called whenever a terminating transmission attempts to issue a command. The command, with information about the terminating transmission, is passed to your FTSCPROC, which issues the command or suppresses it. To activate your FTSCPROC, set its name in this operand. If you issue SYSPARMS FTSCPROC=NONE, no FTSCPROC is used, and commands are executed directly.
Note: For more information, see the Administration Guide.
Default: NONE
Specifies whether extended event data is created for $$FTS events for use by CA NetMaster FTM.
Note: For more information, see the Network Control Language Reference Guide.
Default: NO
Determines the maximum file block size that CA SOLVE:FTS processes.
In some circumstances (for example, tape data sets created with block sizes greater than 32 KB), the 64K setting is required to process the files successfully.
Default: 32K
Provides optional generation of an additional message (number N44807) at the end of a transmission at the receiving system. The message identifies the data set name into which the file has been received.
For SYS or ALL, the message is written both to the activity log and to OCS operators profiled to receive FTS messages. The generation of this extra message enables the LOGPROC NCL procedure to do the following:
Default: NO
Specifies whether CA SOLVE:FTS generates SMF records on successful completion of transmission or receipt of a file.
Generation of SMF records is possible only if CA SOLVE:FTS has been assigned an SMF record identifier to be used on all SMF records generated by the system. This identifier is set using the SMF parameter group of the Customizer.
Default: NO
Provides optional generation of an additional message (number N44307) at the end of a transmission at the transmitting system. The message identifies the data set name just transmitted.
For SYS or ALL, the message is written both to the activity log and to OCS operators profiled to receive CA SOLVE:FTS messages.
Default: NO
xxx defines the default number of messages that are queued for an OCS window in HOLDING or AUTOHOLD mode, or where the window is closed. When this limit is reached, the earliest messages are discarded to allow the latest messages to be queued and a warning that messages are lost is sent to the terminal. yyy defines the maximum depth of the message queue that any user can request when using the PROFILE HOLD command. This lets you limit the size of any individual operator's message queue by overriding the default range of the PROFILE HOLD command.
Default: (200,999)
Limits: 10 to 999, and xxx cannot exceed yyy.
Specifies the INMC buffer size (in KB) for all INMC traffic. This size is the default for all outbound messages on INMC sessions except for those sessions whose bind specifies a maximum RU size smaller than INMCBFSZ. For these sessions, the message size is equal to or smaller than the bind RU size.
Increasing INMCBFSZ can improve performance on high speed links, such as channel-to-channel or microwave links. Slow links can benefit from a lower INMCBFSZ value.
This operand can be changed at any time. However, the changed value of INMCBFSZ is not reflected in active links until they are stopped, reset, and restarted.
Default: 4
Defines the load module for the INMC Primary Security Exit to be invoked whenever any INMC link becomes active. exitname is any valid module name. If you specify NONE at a later stage, the definition of any existing primary exit is canceled. This operand is applicable only for systems configured with INMC.
Default: NONE
Defines the load module for the INMC Secondary Security Exit to be invoked whenever any INMC link becomes active. exitname is any valid module name. If you specify NONE at a later stage, the definition of any existing secondary exit is canceled. This operand is applicable only for systems configured with INMC.
Default: NONE
Controls the use of heartbeats for TCP/IP INMC and APPC links.
IPAMHB=NO disables heartbeats for INMC/APPC links using TCP/IP (regardless of the setting on the other side).
IPAMHB=(a,b) sets up heartbeats as follows:
If no heartbeats are received in (a*b) seconds from the other side of the session, then the session is closed. For INMC, the link is retried later.
If both sides of a link want heartbeats, then the minimum of each value is used; that is, the minimum of the two send intervals and the minimum of the two loss toleration counts.
Default: NO
Specifies the NCL procedure to be started when a journal swap occurs.
Default: $NDJPROC
Specifies whether the NDB journal data set is to be swapped automatically if a space error occurs on the active journal.
When YES is specified, the journal is swapped to the alternate journal if the file full condition occurs.
When NO is specified, the journal error prevents further updates to journaled NDBs and any updates in progress are held over until the NDB is successfully restarted.
Default: YES
Defines the language code for the system and the default language code for users.
Note: For the system recognized values that can be used to replace the cc option on this operand, see the Network Control Language Reference Guide.
Default: US
Specifies the repeat frequency at which OCS operators are warned of lost messages when in HOLDING, AUTOHOLD, or FS-HOLD mode. The warning message appears every number messages lost.
Default: 10
Limits: 1 to 999
Specifies whether a trace message is to be issued each time an attempt to open a session to a remote region fails.
If YES is specified, the system issues an N35006 trace message to Monitor status users each time an attempt to open a session to a remote system fails for any reason. The system retries such failures indefinitely at 60 second intervals until the session is opened or the link is stopped. If a remote system cannot be contacted, turn on this trace and examine the content of the LNKTRACE message to help resolve the cause of failure.
Default: NO
Specifies the LOCK command procedure. This procedure is invoked when a user enters the LOCK command to lock the terminal.
Default: $NMLOCK (supplied procedure)
Defines the number of lines per page of the activity log. This operand must be executed near the start of the NMINIT initialization procedure to become immediately effective. Values of 30 to 250 can be specified.
Default: 60
An MAI ACB name is constructed using a prefix and a numeric suffix. When an ACB fails to open, the suffix is incremented and the ACB open is retried. There are two types of failure:
There is no limit set on the number of retries allowed for non-error failures.
This operand sets the maximum number of consecutive retries allowed when an MAI ACB fails to open in an error situation.
When an ACB fails to open in a non-error situation, the retry limit is reset to the value of this operand.
Default: 5
Limits: 5 to 99
Specifies the name of an exit routine to take control whenever an MAI-OC session (both MAI-OC and MAI-FS) is started or ended and optionally when the VTAM ACB has been opened. The exit routine also receives notification of the LU name chosen by MAI. This routine is given information about the session to be created and can validate and alter those details, as well as having the capability of refusing the session. In addition, the routine has the capability of correlating information across session start and end calls. The MAIEX02 parameter supplies the name of the user exit routine to perform this function. MAIEX02=NO indicates that an existing exit is to be disabled or that no exit is required.
Specifies the way in which MAI serializes calls to the MAIEX02 exit routine. MAIEX02S=SYSTEM, the default, ensures that all calls to the routine are, in effect, queued within any one system, while MAIEX02S=USER only queues concurrent calls at an individual user level.
Specifies whether or not MAI will append a new line character (X'15') to data sent to the target application (that is, inbound from the terminal).
SYSPARMS MAIONL=YES, the default, appends a new line; SYSPARMS MAIONL=NO does not.
Default: YES
Specifies a character string which is used as the prefix to an LU name generated by MAI-OC, for example:
SYSPARMS MAIOPREF=MAI02
If the SYSPARMS MAIOPREF operand is not coded, MAI-OC assumes a default prefix of NMMAV.
Limits: One to five characters
When data is received from an application across an MAI-OC session, MAI-OC translates, by default, any characters below X'40' to an underscore (_) before displaying it at an OCS window and leaves all other data intact. The MAIOTRNS operand can be used to alter the translate table used by MAI-OC in this process. The value xx is two hexadecimal digits representing a value to be translated and yy two hexadecimal digits representing a value into which xx is to be translated. The yy value must represent a printable character.
For example, to translate a hexadecimal zero (X'00') to a blank, specify:
MAIOTRNS=(00,40)
Specifies the maximum request unit size for APPC sessions. If necessary this value overrides the LU6.2 session BIND parameters. The value specified on this command applies to new sessions established after the command is complete. The default value is 4096. The value specified is converted to a single byte RU size of the form X'ab' where number=a*2**b. Values must be in the range 128 to 32768 and the values which cannot be converted directly are rounded down.
Specifies an alternate menu for LU1 logons.
Default: $NMPMLU1 (supplied procedure)
Specifies an alternate primary menu procedure name.
Default: $NMPMENU (supplied primary menu procedure)
Specifies the name of a UAMS user ID definition, present on the UAMS data set, to be used as the model for dynamic user ID generation. Use the following scenarios to determine the most appropriate action for your system:
Default: NONE
Specifies the name of the NCL authorization exit. This exit provides security for NCL procedures and &SMFWRITE verbs.
Note: For full information about NCLEX01, see the Security Guide.
If NCLEX01 is frequently invoked, use the LOAD MOD=exit_name command to load a re-entrant version of the exit into the region to eliminate the overhead of loading the exit for each authorization.
If NO is specified, then the current exit name is deleted and exit invocation is stopped.
Note: The NCLEX01 load module is executed under a subtask and can therefore issue I/O and WAIT operations without impacting the main system.
Specifies a single global variable name, or a generic global variable prefix that is to be traced as changes occur to them. Each time an assignment occurs into a traced global variable, a log record is written that identifies the process performing the assignment. The first eight bytes of data are also traced.
If name is specified, only one global variable is traced. If prefix is specified, all global variables that start with the nominated prefix, excluding the standard global variable prefix, are traced as their values change.
The trace record is written as a single message, N23312, to the activity log. Tracing is turned off if no name or prefix is specified.
Specifies whether NCL writes a log message on completion of each NCL procedure. If YES is specified, the log message provides statistics on NCL processing units used by the procedure.
Default: NO
Specifies how many X'FF' field separators NCL places at the end of a record written to a UDB. If MULT is specified, and a record is written to a UDB where the record contains multiple null variables at the end, one X'FF' field separator is appended to the UDB record for each 'null' variable on the &FILEPUT or &FILEADD statement.
If NCL-format UDBs are created for processing by external systems, the use of this operand should be consistent.
Default: ONE
Specifies the maximum number of NCL trace messages that are generated in any one invocation of an NCL procedure. If 0 is specified, all tracing is inhibited.
Default: 100
Limits: 0 to 9999
Sets the number of VSAM logical records that will be formatted as a journaling area when an NDB is created using the NDB CREATE command. This journal area provides transaction integrity across system failures.
If the LOGSIZE parameter is specified on NDB CREATE, it overrides this value.
This value can be changed prior to issuing an NDB CREATE command, to change the journal size for that database.
Journal size is influenced by the possible complexity of an add, update, or delete operation on the database, which in turn depends on such things as the size of the data record, and the number of keys being added. The journal automatically extends if it is under-allocated.
Note: For more information, see the Network Control Language Programmer Guide.
Default: 40
Limits: 10 to 200
Controls whether the nominated NCLEX01 is called for &NDBOPEN.
Registers the name of the NCL phonetic exit program.
Sets the minimum number of consecutive RID numbers that can be reused. You can change this operand at any time.
Default: 20
Limits: 10 to 100
Sets the percentage of RID space to be scanned to collect RIDs for reuse. Values of 95 or greater cause the complete NDB to be scanned. For an NDB that is scanned daily, a default value of 15 means that the NDB is scanned completely every week. You can change this operand at any time.
Default: 15
Limits: 5 to 100
Enables (YES) or disables (NO) the scan optimizer.
Notes:
Default: YES
Sets the minimum number of subthreads that will stay active, for any NDB, awaiting database requests that can run asynchronously (&NDBSCAN and &NDBGET requests). When a database request arrives that can be run asynchronously, the database handler starts a separate copy of itself to run that request, unless there are already NDBSUBMX subthreads running. As the subthreads run out of work, they terminate unless the NDBSUBMN limit is reached.
Default: 3
Limits: 0 to 20
Sets the maximum number of subthreads allowed. See NDBSUBMN.
Default: 5
Limits: 1 to 20
Specifies whether this system is to run non-swappable (YES), or swappable (NO). This operand is valid only if your product region is running authorized.
For z/OS and MSP, your product region makes itself non-swappable automatically before system initialization. The NONSWAP operand can be utilized to change this status either during initialization or at any time after.
For VOS3, if your product region is authorized, it runs swappable, by default. It can be changed to run non-swappable by specifying YES. However, once running non-swappable, it is not possible to change the status back to swappable without stopping and restarting the system.
Note: For z/OS and MSP, optional features which require non-swappable operation blocks attempt to revert to swappable operation.
Specifies the maximum number of NRD messages that the system queues at any time before discarding the oldest messages. This queue is used by the NRDRET command to refresh the OCS NRD message display.
Default: 200
Limits: 10 to 10000
Sets the interval between retries when trying to connect to a CA NetSpy region. It is an integer number of seconds.
Default: 30
Limits: 10 to 600
Specifies whether NTS accounting data is to be collected for selected sessions only, for all sessions, or for no sessions. NTSACCT=SELECTIVE means that NTS attempts to collect accounting data for those sessions which have a sawclass specifying ACCT=YES (see the DEFCLASS command). NTS starts a specific trace for the primary resource if possible, otherwise the secondary resource if possible, to gather accounting information. No attempt is made to stop such selective tracing. This option is best used when accounting data is required only for a few applications in the host system. If NTSACCT=ALL is specified, then NTS starts tracing all network activity and collects accounting information for all sessions regardless of any Saw class parameters. If NTSACCT=NO is specified, then NTS does not collect any accounting information regardless of session parameters. Should any accounting be active when this is requested it ceases immediately. Once session awareness processing is active, only NTSACCT=NO can be specified. To change the SYSPARMS accounting value to either of the other options while session awareness is active, it must first be stopped, the command entered, and then session awareness restarted.
Default: SELECTIVE
Specifies the NTS correlation interval value, where nn is a number of seconds. This value represents the maximum interval that NTS is prepared to wait for certain different types of data to be correlated. For example, trace information can arrive ahead of the session notification for a particular session. If this occurs NTS queues such data and solicits the latest session information from VTAM. However, if the session data for the traced session does not arrive within the elapsed time of the correlation interval all uncorrelated data is purged. Similarly, if there is outstanding data (such as trace or RTM data) yet to arrive after a session has ended, NTS is prepared to wait for it for up to the correlation interval specified. If this interval expires then logging proceeds regardless of whether all outstanding data has arrived. The default should be adequate for most networks.
Default: 30
Specifies whether any sessions, which remain active when NTS is closed due to system initialization, are to be considered ended for the purpose of output logging. NTSCLOSE=NO means no active sessions are logged when NTS closes. If NTSCLOSE=YES is specified then those sessions still active are queued for output and time-stamped with the shutdown time. Such sessions are logged (according to the log options in effect) and are flagged with a C in subsequent NTS session selection lists indicating the session did not end normally but was closed by NTS. Because your product region only waits for a short period of time (about 10 seconds) between shutdown notification and actual termination, this technique is only useful where a small number of sessions remain which need to be logged. If a large number of sessions require closing before shutting down, the CLOSE operand of the NTS SAW STOP command is used to similarly close and log all active sessions before stopping.
Default: NO
Specifies whether NTS is to queue NTS CNM requests. NTSCNMQ=YES means that all CNM requests are queued until they are replied to by VTAM. NTSCNMQ=NO means that NTS CNM requests are not queued, but issued immediately. Issuing NTSCNMQ=NO while NTS is active results in all queued NTS CNM requests being purged.
Default: YES
Controls NTS event generation. If you want events to be generated then you must specify SYSPARMS NTSEVENT=YES. Issue SYSPARMS NTSEVENT=NO to immediately terminate all NTS event generation irrespective of what class definitions are in place. Subsequently issuing SYSPARMS NTSEVENT=YES restarts generation as per the current class definitions.
Default: NO
Specifies whether NTS intensive message recording is active. By enabling this function, certain activities can be tracked, such as the purging of uncorrelated trace data, and dumping of unrecognized entries in the trace buffer. This option is not usually required under normal operation.
Specifies a mask that enables intensive message recording for certain LUs and PUs only.
Wildcards: * (any number of characters) and ? (one character)
Default: NO
Specifies whether MAI sessions are presented to the NTS user exit. NTSMAIEX=NO indicates that NTS does not present MAI sessions to the NTS user exit. NTSMAIEX=YES indicates that an SMF type 39 record is built for MAI sessions and presented to the NTS user exit.
Note: For information about the record format, see the CA NetMaster NM for SNA Administration Guide.
Default: NO
Requests that MAI inform NTS of any current MAI session and subsequent MAI sessions. NTS must be activated before MAI session visibility becomes effective. SYSPARMS NTSMAISV=YES can be specified after NTS and MAI are already active and causes MAI to notify NTS of all currently existing MAI sessions. If NTSMAISV=NO is specified after the interface is active, sessions currently visible to NTS remain so but MAI does not notify NTS of new sessions.
Default: NO
Provides the maximum number of trace PIUs that any class definition or operator command can specify, as either the initial or final trace queue depth for any session.
Default: 100
Provides the maximum number of resources that can have a specific STRACE request outstanding. This includes both trace start requests in normal operation, and trace stop requests where global tracing is active and the resource is to be excluded. The number also includes those resources for which NTS started tracing to collect accounting data.
Default: 100
Specifies the interval length for resource statistics collection in minutes.
Default: 30
Limits: 1 through 480 (eight hours)
Specifies how many of the NTSRSINT intervals can occur before the statistics collected for the oldest interval are overwritten. This operand can be overridden selectively using the LIMIT operand of the DEFCLASS RESOURCE command. If this parameter is not specified and the relevant NTS resource class does not specify a LIMIT parameter, the default number of intervals is used.
Default: 16
Limits: 0 through 255
Specifies whether to collect resource statistics. If this parameter is not specified, or NTSRSTAT=NO is specified, then resource statistics collection is disabled. This means that no resource statistics are collected, irrespective of options set in resource class definitions. Once session awareness (or SAW) is enabled, only NTSRSTAT=NO can be specified.
Default: NO
Specifies the number and size of buffers that VTAM allocates for collecting session awareness data.
Specifies the number of buffers.
Default: 2
Limits: 2 through 255
Specify the buffer size in KB.
Default: 4
Limits: 2 through 32
Specifies the system default session keep count for sessions written to the NTS database. The number nn represents the maximum number of session incidences kept in the database for any specific session name pair. When a session ends and is written to the database, this value is placed in the session master record. You can use the NTSDBMOD command to modify this value. The real name and network of both session partners determine a session name pair. The default value of 10 means that only the ten most recent sessions for a session name pair are kept in the database. As each session ends, it is added to the database until the session count is reached after which any new sessions replace the oldest ones.
Default: 10
Limits: 1 through 255
Specifies whether to write timestamps in type 39 SMF records in GMT or local time.
All application timestamps in type 39 SMF records consist of the first four bytes of the system TOD clock value, plus a 4-byte signed number for the time zone adjustment value, in seconds. By definition, the first four bytes represent GMT time in approximately 1-second intervals. However, NetView (NLDM) writes the first four bytes of these timestamps in local time.
Default: GMT
Specifies whether the trace final queue buffers are to be consolidated when the first wrap occurs. For sessions experiencing heavy traffic, the trace final queue might wrap frequently. If trace buffers are allocated from a large set of pages, and tracing is enabled for many sessions, the paging overhead on the system might be considerable. Specifying NTSTRBFX=YES causes NTS to use a contiguous buffer pool for the allocation of trace buffers for a single session. This effectively fixes the pages in memory and therefore reduces the paging overhead. The movement of the contents of the trace buffers on the trace final queue into the contiguous storage buffer occurs when the trace final queue wraps for the first time.
Default: YES
Specifies the number and size of buffers that VTAM allocates for collecting trace data.
Specifies the number of buffers.
Default: 4
Limits: 2 through 255
Specify the buffer size in KB.
Default: 4
Limits: 2 through 32
Specifies the type of highlighting to be used for messages in OCS windows normally displayed in high intensity. The following options can be specified:
NONE specifies that messages are presented without change.
REVERSE specifies that messages are presented in reverse video.
BLINK specifies that messages are to blink.
USCORE specifies that messages are underscored.
For terminals that support color, the default color applies. This operand is ignored for terminals that do not support IBM extended highlighting and does not apply to individual high intensity fields resulting from comment lines from NCL procedures that commence with a plus sign (+) and that use the at symbol (@) field highlighter.
Default: NONE
Specifies whether the time appears at the end of the title line of an OCS window. If YES is specified, the current time in the format HH.MM is placed at the left hand end of the title line of an OCS window each time the window display is updated. This allows operators to determine when the last message occurred if the terminal has been left temporarily unattended. Specifying NO resets this option.
Default: YES
Specifies the maximum outbound data stream size (in KB) that can be generated for any terminal that is attached to your product region.
If your terminals receive large data streams such as complex extended data stream screen formats, increase the PANLBFSZ operand. A message is issued if an attempt is made to display a panel that is too large for the current PANLBFSZ setting.
Default: 16
Limits: 4 to 20
Specifies the maximum number of pages of virtual storage to use for concurrent terminal output operations. If 0 is specified, no limit is imposed.
This parameter throttles the simultaneous output to large numbers of terminals (for example, during broadcast processing or when starting a large EASINET network). Increase this number to speed up network startup and broadcasting, decrease it to throttle back these activities.
Before you increase this value, consider any effects an increase in virtual storage usage have on other functions.
Default: 40
Limits: 0 to 32767
Specifies the color to use when displaying unsolicited VTAM (PPO) messages on OCS consoles.
PPO messages are displayed in high intensity on noncolor devices.
Default: WHITE
Limits: BLUE, RED, PINK, GREEN, TURQUOISE, YELLOW, WHITE, and NONE
Specifies the type of extended highlighting used for unsolicited VTAM messages sent to OCS windows. The following options can be specified:
This operand is ignored for terminals that do not support IBM extended highlighting.
Default: NONE
Specifies how to log PPO messages received from VTAM as the result of VTAM commands entered from a system console or a local OCS window.
If one of the following conditions applies, VTAM relays copies of the results of system console commands:
The following options can be specified:
Default: LOG
Specifies how to log unsolicited PPO messages, regardless of DEFMSG options. The following options can be specified:
Default: NOLOG
Specifies the number of days after which users are forced to change their password. This operand takes effect the next time a user logs on. This operand has no effect if a security exit is in force that replaces the UAMS password maintenance functions. Enter a value of 0 to disable the automatic password expiry feature.
Default: 30
Limits: 1 to 366
Specifies the maximum acceptable length for passwords. This operand only takes effect from the next password change a user makes. The operand has no effect if a security exit is in force that replaces the UAMS password maintenance functions.
Default: 8
Limits: Value of PWMIN to 8
Specifies the minimum acceptable length for passwords. This operand only takes effect from the next password change a user makes. The operand has no effect if a security exit is in force that replaces the UAMS password maintenance functions.
Default: 3
Limits: 1 to the value of PWMAX
Specifies the number of password violations that are accepted before a logon attempt is denied. If the number is reached, a warning message is sent to all terminals with Monitor status. The message advises them of the user ID and terminal involved in the violation. This operand has no effect if a security exit is in force that replaces the UAMS password maintenance functions.
Default: 2
Limits: 1 to 10
Specifies the operating system routing codes to use for unsolicited messages sent to the system console (that is, to the ppppOPER user ID).
Note: For an explanation of the impact of specifying certain codes, see the appropriate operating system guide.
Default: 1,8,11
Limits: 1 to 16
Specifies the working stack size (in KB) of the REXX compiler.
Default: 3
Limits: 3 to 16
Specifies the size (in KB) of the initial storage to get for a REXX process. A nonzero value avoids startup overhead.
Default: 32
Limits: 0 to 128
Limits the maximum size (in KB) of a compiled REXX object.
Default: 256
Limits: 64 to 512
Specifies the maximum amount of storage (in KB) a REXX process can use.
Default: 4096
Limits: 32 to 10258
IBM REXX interpreters let quoted strings extend across multiple lines. The GREXX Compiler does not handle this by default. If RXQSFIX is set to YES, then quoted strings that extend across multiple lines are converted with all trailing blanks stripped. The string still cannot be larger than 250 bytes in length.
Note: There is one circumstance where the resulting REXX source, while syntactically correct, may not execute correctly. If the repaired string has a REXX operator of higher precedence than concatenate (||), the resulting expression is processed in the wrong order.
Default: NO
Specifies the size (in KB) of the REXX retained procedure pool.
0 specifies that no dynamically loaded procedures are retained.
Default: 200
Limits: 0 and 10 to 2048
Specifies the working stack size (in KB) of a REXX process.
Default: 4
Limits: 3 to 16
Specifies whether trace message N35007 is issued each time a session to a remote system opens or fails. If YES is specified, the system issues the trace message to Monitor status users, each time a session to a remote system is opened or fails. The system retries any failures indefinitely at intervals specified in the LINK command until the session is opened or the link is stopped.
This option can be particularly useful in an INMC operation, as it might be the only way to identify the fact that not all sessions making up a link are operational. If any sessions are open the link remains operational-the failure of an individual session does not disrupt traffic, but can affect performance. The default is NO.
Default: NO
Requests the dump of written SMF records.
Specifies the number of kilobytes below the 16-MB line at which an N01801 message is issued as a WTO indicating that the storage thresholds have been exceeded. This message can be repeated at 30‑second intervals until the storage use drops below the threshold.
Default: 0 (no warning limit)
Limits: 0 to 16,000
Specifies the number of kilobytes above the 16-MB line at which an N01801 message is issued as a WTO indicating that the storage thresholds have been exceeded. This message can be repeated at 30-second intervals until the storage use drops below the threshold.
Default: 0 (no warning limit)
Limits: 0 to 1,000,000
Specifies the default user ID for a master console that issues commands to your region when it is not signed on to the security system in use.
SYSCONMU can be set only during NMINIT. For master consoles that are not signed on to your security system, this user ID always applies, regardless of the setting of the SYSPARM SYSCONSO.
If this default user ID is not defined to your security system, then the user ID .MASTOP (which has a hard-coded profile) is used.
Note: For more information about master console user ID requirements, see the Security Guide.
Default: ppppMSOP, where pppp is the system user prefix
Limits: One to eight characters
Specifies the LU name that is assigned to system console environments. The following options can be specified:
Default: EXTMCS
Specifies whether the console user ID can default and whether signon is required. It is relevant to all operating system environments. The following options can be specified:
Note: There are interactions between the SYSCONSO and SYSCONXU parameters.
Default: DEFAULT
Specifies the default system console signon name. The name must be a valid user ID.
Note: The user ID is not used unless it exists in the security system in use.
Note: For more information about console user ID requirements, see the Security Guide.
Limits: One to eight characters
Specifies whether or not external console user IDs are to be used when signing on consoles. The following options can be specified:
Note: There are interactions between the SYSCONXU and SYSCONSO parameters.
Default: NO
Specifies whether none, all, or unsolicited VTAM messages written to the activity log, are also written to the system log. The following options can be specified:
Default: NO
Specifies the format of the SYSLOG lines produced if SYSLOG=YES or SYSLOG=PPO.
Format a line with four zeroes for ROUTCDE, time, and user ID in the JOBID column.
Specifies whether the Telnet Server will register new connections with the Packet Analyzer, for use by any CA NetMaster NM for TCP/IP regions on the same z/OS image.
Setting NO means connections are not registered.
Default: YES
Specifies the trace options to be applied when tracing data streams sent to or from a terminal. The value of cc is the character representation of a hexadecimal byte.
The following bit values represent valid trace options:
B'10000000'(X'80') Trace only first 256 bytes of each message. B'00000001'(X'01') Trace output before compression. B'00000010'(X'02') Trace output after compression. B'00000100'(X'04') Trace input from terminal.
Default: 06
Example:
SYSPARMS TRACEOPT=80
indicates that the tracing options required correspond to a hex byte with a value of X'80'. This byte in turn represents an 8-bit string with the value:
B'10000000'
Example:
The value specified on the TRACEOPT parameter can be any combination of the four options, expressed as a hex character, for example:
SYSPARMS TRACEOPT=84
indicates a request to trace the first 256 bytes received from the terminal, with the data stream being written to the activity log. Data recorded can then be examined using the standard online log browse facilities.
Tracing is started and stopped by the LUTRACE command.
Specifies whether the NCL system variable &USERPW is available for use in MAI logon data. &USERPW represents the user's product region password and is used when MAI sessions are created. This operand allows installations to control the availability of the &USERPW variable to MAI.
If YES or VERIFY is specified, the password is encrypted in storage so that it is not available in plain text. Specifying VERIFY indicates that MAI should prompt users for their password when a session is updated or added that contains &USERPW in the logon data.
Default: VERIFY
Specifies how the VTAM display command (D) is processed for users with command Network Partitioning. The following options can be specified:
Default: CMD
Specifies the system procedure name used for starting VTAM. If any other procedure name is used, then your product region must be informed of it so that the correct name can be used when generating VTAM commands.
Default: (ACF/VTAM and VTAM-G) NET or (ECS/VTAM) VTM
Limits: One to eight characters
Specifies whether your product region is to allocate buffer storage below the 16-MB line in XA systems if all storage in the extended private area has been used. NO means that if all XA storage in the product region address space has been used, further requests for XA storage by other processes fails, even if non-XA storage is still available below the line. Do not change this unless your installation requires your product region to run with a severely limited extended private area.
Default: NO
| Copyright © 2012 CA. All rights reserved. |
|