The definition statement syntax is a model statement that is formatted according to the code

conventions.
• Operand descriptions
This section describes each operand you can specify for the definition statement. The description
includes the specific values or variable information that you can specify for the operand.
• Cross-reference to related statements
This section lists other statements that can affect the definition statement.

Syntax Conventions for CNMSTYLE Definition Statements

These syntax conventions apply to the statements that can be specified in the CxxSTYLE member and its
included members:
• All of the customization in CxxSTYLE and its included members has the form of a REXX variable followed
by an equal sign and then a value. Spaces before or after the equal sign may be used for readability.
• The variable names are not case sensitive.
• Variable values related to internal usage within the NetView product or MVS values and commands are
mostly NOT case sensitive. You can use mixed cases to improve readability.
• Variable values related to OMVS, UNIX, DB2®, WAS and some other services are case sensitive for
values that require case sensitivity by those components. Most of CNMSTYLE variables that require
case sensitive values have appropriate comments in CxxSTYLE, %INCLUDE members, and Usage Note
section of Variable description in this book.
• Do not change the variable name except as directed for stem names.
• All variable names must begin in column 1.
• Do not use quotes; all values are literal.
• Some values can be very long, for example, a UNIX path or an URL. You can span such values over
multiple lines. To continue a line, begin the next line with a space in the first position, and continue from
the second character. Note that if the second character is a blank, that blank becomes part of the value.)
• A line beginning with a blank is regarded as a continuation of the preceding line, intervening comment
lines notwithstanding.
• Lines beginning with an asterisk (in column 1) are comments and ignored.
• Any data after string "//" are comments and also ignored.
• Lines that are entirely blank are also ignored.
• Trailing blanks are not significant.
• If the same variable is defined more than once, the last one takes effect unless otherwise noted, for
example, see styleMsg.
• If columns 73-80 in the first line of CxxSTYLE are all numeric, the entire file is assumed to have
sequence numbers in these columns, which are ignored. Otherwise columns 1-80 are read. Each
%INCLUDE member follows the same convention independently.
• Data REXX is not supported for the CxxSTYLE member, but is supported for %INCLUDE members.

Syntax Conventions for non-CNMSTYLE Definition Statements

These syntax conventions apply to most statements:
• Code at least one blank between a label name and the name of the definition statement, and between
the name of the definition statement and the first operand. One or more blanks, or a single comma
with no blanks, must separate the statement operands. You cannot separate the operands with a
combination of commas and blanks. If you omit the optional label name, you still need to precede the
definition statement with one or more blanks.
• The label field must not exceed 8 characters, and the field must start in column 1.

Chapter 1. Location of Statements and Samples 7

 • In general, continuation from one line to the next is not allowed. However, you can repeat the definition
statement and add the remaining information. For the following example:

LOGINIT AUTOFLIP=YES
LOGINIT RESUME=YES

Is the same as:

LOGINIT AUTOFLIP=YES,RESUME=YES

One exception is with CNMSTYLE and CNMCMD definition statements, which specify a keyword whose
value is a comma-delimited list. In this case, the value can be continued from one line to another by
ending the line to be continued with a comma, and resuming the list value in column 2 of the next line,
as shown in the following example:

ASSIGN.OPERGRP.GROUP = OPER1,OPER2,OPER3,OPER4,
OPER5,OPER6

Another exception is with the webmenu statement; for information, see the usage notes in “webmenu”
on page 264.
• Place comments on a separate line for DSIPARM members. The first column of a comment line must
contain an asterisk (*).
• Many definition files conclude with an END statement. This END statement has no operands and cannot
begin in column 1.
• All NetView program identifiers, which are called names, must not exceed 8 characters unless specified.
The first character must be alphabetical and alphabetical characters must be in uppercase.
• Command names, command list names, and any other NetView program identifiers must not contain
commas (,), periods (.), blanks ( ), apostrophes ('), ampersands (&), asterisks (*), or equal signs (=).
Commas, periods, blanks, and equal signs are used as delimiters when the definition statements are
parsed. The other characters have special meanings for NetView command lists.
• Command names and command list names must begin in column 1.
• System symbolics can be coded on any NetView definition statement to provide unique information to
the NetView system. System symbolics are useful when running NetView on different systems where
you want to have different characteristics. This unique information (as defined by the system symbolic
values) remains on your system definitions until you change those definitions and restart MVS.

8 IBM Z NetView: Administration Reference

Chapter 2. CNMSTYLE Initialization Statements

NetView initialization statements are defined in the CNMSTYLE member in the DSIPARM data set. To
make changes to a CNMSTYLE statement, copy the statement to either the CNMSTUSR or CxxSTGEN
member and then make any necessary updates. For more information on NetView initialization and
updating CNMSTYLE statements, refer to IBM Z NetView Installation: Getting Started.
Some CNMSTYLE statements are preceded with a tower parameter, or tower and subtower parameters.
The syntax diagrams do not list the associated tower and subtower parameters. For example, the
(TEMA.CONNACT) parameters are not listed with the syntax of the NACMD.INTCONNACT CNMSTYLE
statement.

(TEMA.CONNACT)NACMD.INTCONNACT = 900

For tower and subtower information associated with a statement, review the CNMSTYLE member in the
DSIPARM data set.

ACBpassword
Purpose
The ACBpassword statement specifies the password for ACBs for the NetView program if they have not
previously been specified in an SAF product, such as the Resource Access Control Facility (RACF®), or
in the NetView startup procedure, CNMSJ009. The password specified is used for the main application
control block (ACB), for the primary program operator interface task (PPT), and for operator station tasks
(OSTs).

Syntax
The ACBpassword statement has the following syntax:
ACBpassword = password

where:
password
Specifies the password that is to be associated with the NetView ACBs. It can be up to eight
characters in length and must match the value configured to VTAM in the APPL statement for NetView
program. It is set to the NetView domain name in the CNMSTPWD member provided by the NetView
program.

Usage note
The ACBpassword statement must be included in member CNMSTPWD so that the password can be
hidden. CNMSTPWD cannot be displayed by the BROWSE command.

AlertRcvName
Purpose
The AlertRcvName statement defines the PPI alert receiver name that is associated with the
MOD=CNMCALRT task.

Syntax
The AlertRcvName statement has the following syntax:

© Copyright IBM Corp. 1997, 2019 9

 AlertRcvName = name

where:
name
Specifies a 1 - 8 character PPI alert receiver name.

Usage notes
• If you run more than one alert receiver task on this NetView program, specify a 1 - 8 character name
beginning with an asterisk (*). In this case, each PPI name is set to the task name. For the task name
CNMCALRT, the PPI name is always set to NETVALRT.
• To implement definition changes while the NetView program is active, change the value in the
CNMSTUSR or CxxSTGEN member, and enter the RESTYLE ALERTRCVNAME command.

APSERV.PREFIX
Purpose
The APSERV.PREFIX statement prescribes the behavior of the APSERV command interface for clients
that are identified by the statement. For clients that begin each inbound command with a fixed string,
APSERV will examine the token that follows such string. When such token is a valid NetView command,
APSERV will ignore the prefix string.

Syntax
The APSERV.PREFIX statement has the following syntax:
*NONE*=*ALL*
APSERV.PREFIX.
*NONE*=*NONE*
<
prefixStr= safID

Where:
prefixStr
Is a one-to-eight character string, which will receive special handling if it is found at the beginning of
an input command string.
safID
Is a one-to-eight character identifier registered with a System Authorization Facility (SAF) security
service. This name identifies a client for which the prefix defined by this statement is relevant.

Usage notes
• If no SAF product is used, do not code an APSERV statement.
• The default line APSERV.PREFIX.*NONE*=*ALL* represents the behavior of APSERV prior to support
for the APSERV statements. It means that any Authorized Program Facility (APF)-authorized program
can use APSERV, but no prefix string will receive any special handling. There is no need to code this
statement.
• The second line APSERV.PREFIX.*NONE*=*NONE* represents the baseline that is built upon when
the first APSERV.PREFIX statement is encountered. It means that no string receives special handling,
and no program is authorized to use APSERV. There is no need to code this statement when any other
APSERV.PREFIX statement is specified.
• Code enough APSERV.PREFIX statements based on your requirements. Each statement that specifies
a prefixStr and one or more safIDs will add extra strings and authorizations.

10 IBM Z NetView: Administration Reference

 • For more information about APSERV, see the IBM Z NetView Application Programmer's Guide.
• To implement definition changes while the NetView program is active, change the value in the
CNMSTUSR or CxxSTGEN member, and enter the RESTYLE APSERV command.

ARCHIVE.ACCESSDELAY
Purpose
The ARCHIVE.ACCESSDELAY statement indicates the amount of time that the NetView program waits
before attempting to access any archive data sets.

Syntax
The ARCHIVE.ACCESSDELAY statement has the following syntax:
ARCHIVE.ACCESSDELAY = 00:00:00

ARCHIVE.ACCESSDELAY = delay_time

where:
delay_time
Specifies the amount of time that the NetView program waits to access archive data sets. Specify the
time in the format hh:mm:ss, where hh is the number of hours, mm is the number of minutes, and ss is
the number of seconds.
The value must be between 00:00:00 and 23:59:59, inclusive. The default value is 00:00:00.

Usage notes
• The ARCHIVE.ACCESSDELAY statement only applies to NetView initialization. Use this statement when
archive data sets cannot be successfully accessed until a system is in a state to allow access. For
example, if the IBM Z System Automation product is used to start the Data Facility Hierarchical Storage
Manager (DFSMShsm) program and one or more of the archive data sets was migrated, you must give
enough time for the DFSMShsm program to start before the NetView program can access the archive
data sets.
• During the delay time, archiving is not performed and users cannot access archived messages. When
the time expires, a RESTYLE ARCHIVE command is issued.
When the RESTYLE ARCHIVE command is issued (either at the timer expiration sor before), archive
data sets can be accessed using the specified ARCHIVE.HLQ and ARCHIVE.WRITE values. If a RESTYLE
ARCHIVE command is issued before the timer expires, the outstanding timer is canceled to avoid
issuing another RESTYLE ARCHIVE command.
• If the ARCHIVE.ACCESSDELAY statement is omitted or the ARCHIVE.ACCESSDELAY statement has a
value 00:00:00, archive data sets can be accessed as needed.
• To allow access to archive data sets as early as possible, implement automation to issue a RESTYLE
ARCHIVE command as soon as access to data sets is allowed (for example, when the DFSMShsm
program becomes active).
If you are using the Z System Automation product, see its library for more information on issuing
the RESTYLE ARCHIVE command. If you use automation, specify a value on ARCHIVE.ACCESSDELAY
statement that is higher than the longest amount of time that it takes for automation to take place.

Chapter 2. CNMSTYLE Initialization Statements 11

ARCHIVE.BROWSE.DATASPACES
Purpose
The ARCHIVE.BROWSE.DATASPACES statement specifies the maximum number of data spaces that the
NetView program can allocate for browsing the archived Canzlog data.

Syntax
The ARCHIVE.BROWSE.DATASPACES statement has the following syntax:
ARCHIVE.BROWSE.DATASPACES=1

ARCHIVE.BROWSE.DATASPACES= nn

where:
nn
Specifies the maximum number of data spaces: 1 - 10, inclusive. The default value is 1.

Usage notes
• Ensure that at least 128MB of virtual storage is available for the allocation of a data space or archived
Canzlog data can not be browsed.
• Virtual storage usage for browsing Canzlog archives is dynamic. The limit on the amount of virtual
storage used to browse Canzlog archives will initially start off very small (128MB) and will increase as
necessary up until the maximum amount of virtual storage that was specified. Each data space specified
raises the limit on virtual storage usage by 2 gigabytes.
• ARCHIVE.BROWSE.DATASPACES can be increased and restyled. Although
ARCHIVE.BROWSE.DATASPACES can be decreased and restyled, virtual storage used by archived
Canzlog messages will not decrease without restarting the NetView program.
• If a large amount of Canzlog data is referenced at one time and the defined number of data spaces is
insufficient, it is possible for storage to be re-used rapidly and result in incorrect data being retrieved or
displayed.
• Data space storage can also be limited by the IEFUSI exit.

ARCHIVE.BROWSE.MAXDSPSIZE
Purpose
The ARCHIVE.BROWSE.MAXDSPSIZE statement specifies the maximum number of megabytes of virtual
storage that the NetView program can allocate for browsing the archived Canzlog data.

Syntax
The ARCHIVE.BROWSE.MAXDSPSIZE statement has the following syntax:
ARCHIVE.BROWSE.MAXDSPSIZE= 2040

ARCHIVE.BROWSE.MAXDSPSIZE= nn

where:

12 IBM Z NetView: Administration Reference

 nn
Specifies the maximum number of megabytes of virtual storage that the NetView program can
allocate for browsing the archived Canzlog data, ranging from 128 to 20400, inclusive. The default
value is 2040 or one full data space.

Usage notes
• The value specified must be a multiple of 8. If the value given is not a multiple of 8, a message will be
issued and the value will be rounded down to the nearest valid value. For example, if a value of 258 is
specified (which is not a multiple of 8), a value of 256 will be used instead.
• Ensure that at least 128MB of virtual storage is available for the allocation of a data space, or archived
Canzlog data can not be browsed.
• Virtual storage usage for browsing Canzlog archives is dynamic. The limit on the amount of virtual
storage used to browse Canzlog archives will initially start off very small (128MB) and will increase as
necessary up until the maximum amount of virtual storage that was specified.
• ARCHIVE.BROWSE.MAXDSPSIZE can be increased and restyled. Although
ARCHIVE.BROWSE.MAXDSPSIZE can be decreased and restyled, virtual storage used by archived
Canzlog messages will not decrease without restarting the NetView program.
• If a large amount of Canzlog data is referenced at one time and the defined amount of virtual storage is
insufficient, it is possible for storage to be re-used rapidly and result in incorrect data being retrieved or
displayed.
• Data space storage can also be limited by the IEFUSI exit.

ARCHIVE.HLQ
Purpose
The ARCHIVE.HLQ statement specifies the high-level qualifier for data sets that have or will have archived
Canzlog data.

Syntax
The ARCHIVE.HLQ statement has the following syntax:
ARCHIVE.HLQ = *NONE*

ARCHIVE.HLQ = high_level_qualifier

where:
high_level_qualifier
Specifies the 1 - 26 character high-level qualifier. The high-level qualifier must conform to DFSMS
data set naming conventions. The first character must be an alphabetic or a national character (@, #,
$). The value can include periods to separate qualifiers. The last character cannot be a period because
all suffixes added by the NetView program begin with a period. Mixed case values are converted to
upper case.
*NONE*
Specifies that this instance of the NetView program cannot write to the archive or read from it.

Usage notes
• The NetView program uses the high-level qualifier to begin the names of all the data sets in the archive.
For information about the archive data set names, format, and contents, see IBM Z NetView Installation:
Configuring Additional Components.

Chapter 2. CNMSTYLE Initialization Statements 13

 • When you define a high-level qualifier, this instance of the NetView program can browse archived data,
if there is data stored in the archive data set using the specified high-level qualifier.
• If you do not specify a high-level qualifier, then this instance of the NetView program cannot browse
archived Canzlog data.
• To implement definition changes while the NetView program is active, change the value in the
CNMSTUSR or CxxSTGEN member, and enter the RESTYLE ARCHIVE command. For more information
about changing CNMSTYLE statements, see IBM Z NetView Installation: Getting Started.
• If you specify a valid value for the ARCHIVE.HLQ statement other than *NONE*, it is saved in the
value of a common global variable that may be examined by using the NetView program's services for
accessing common global variables. For more information about the common global variables related
to the Canzlog archiving function, see Appendix A, “Common Global Variables for the Canzlog Archiving
Function,” on page 559.

ARCHIVE.INDEX.BLOCKSIZE
The ARCHIVE.INDEX.BLOCKSIZE statement specifies the block size to use for the archive Canzlog
primary index and index data sets.
The ARCHIVE.INDEX.BLOCKSIZE statement has the following syntax:
ARCHIVE.INDEX.BLOCKSIZE = 27920

ARCHIVE.INDEX.BLOCKSIZE = nnnnn

where:
nnnnn
Specifies the blocksize: 80 - 32720, inclusive. Use a value that is a multiple of 80 (no remainder). The
default value is 27920.

Usage notes
• If you are not using the SMS data class (or another selection method), use the
ARCHIVE.INDEX.BLOCKSIZE statement to define a block size for a particular device type.
• Whether you specify a value for the ARCHIVE.INDEX.BLOCKSIZE statement or the default value is
taken, the value is ignored if any of the following statements are coded with a value other than *NONE*:
– ARCHIVE.INDEX.DATACLAS
– ARCHIVE.INDEX.MGMTCLAS
– ARCHIVE.INDEX.STORCLAS
• To implement definition changes while the NetView program is active, change the value in the
CNMSTUSR or CxxSTGEN member, and enter the RESTYLE ARCHIVE command. For more information
about changing CNMSTYLE statements, see IBM Z NetView Installation: Getting Started.
• Whether you specify a valid value for the ARCHIVE.INDEX.BLOCKSIZE statement or the default value
is taken, the value is saved in the value of a common global variable. You can use the NetView program's
services for accessing common global variables to examine the value. For more information about the
common global variables related to the Canzlog archiving function, see Appendix A, “Common Global
Variables for the Canzlog Archiving Function,” on page 559.

ARCHIVE.INDEX.DATACLAS
The ARCHIVE.INDEX.DATACLAS statement specifies the Storage Management Subsystem (SMS) data
class for the Canzlog archive data sets that contain index data (individual index data sets and primary
index data set).
The ARCHIVE.INDEX.DATACLAS statement has the following syntax:

14 IBM Z NetView: Administration Reference

 ARCHIVE.INDEX.DATACLAS = *NONE*

ARCHIVE.INDEX.DATACLAS = data_class_name

where:
data_class_name
Specifies the 1 - 8 character SMS data class name
*NONE*
Specifies not to use a data class when the new index data set is allocated. This is the default value.

Usage notes
• The data class is used for the index data set attributes. The NetView program only validates the length
of the data class name. The data class name is then validated by the operating system when the data
set is allocated.
• If you specify a value other than *NONE* for the ARCHIVE.INDEX.DATACLAS,
ARCHIVE.INDEX.MGMTCLAS, or ARCHIVE.INDEX.STORCLAS statement, the NetView program assumes
that you are using SMS to provide archive index data set characteristics and ignores the values of these
statements:
– ARCHIVE.INDEX.BLOCKSIZE
– ARCHIVE.INDEX.SPACE
– ARCHIVE.INDEX.UNIT
– ARCHIVE.INDEX.VOLUME
Whether a data class is explicitly defined to the NetView program by using the
ARCHIVE.INDEX.DATACLAS statement, a data class must be selected for data set allocation, and it
must adhere to the following specifications:
– Specify a logical record length (LRECL) 80.
– Specify a block size (BLKSIZE) that is an even multiple of the LRECL (80). Make sure that the block
size is 80 - 32720, inclusive.
– Specify a space allocation that is large enough to accommodate the data set. Remember to consider
the device type and block size when you determine the space allocation.
– Do not specify a retention period (RETPD) or expiration date (EXPDT).
• If you are not running or are not using the SMS facility to provide message data set characteristics,
either omit the ARCHIVE.INDEX.DATACLAS statement or code a value of *NONE* to indicate that data
class is not being used.
• To implement definition changes while the NetView program is active, change the value in the
CNMSTUSR or CxxSTGEN member, and enter the RESTYLE ARCHIVE command. For more information
about changing CNMSTYLE statements, see IBM Z NetView Installation: Getting Started.
• If you specify a valid value for the ARCHIVE.INDEX.DATACLAS statement other than *NONE*, it
is saved in the value of a common global variable that may be examined by using the NetView
program's services for accessing common global variables. For more information about the common
global variables related to the Canzlog archiving function, see Appendix A, “Common Global Variables
for the Canzlog Archiving Function,” on page 559

Chapter 2. CNMSTYLE Initialization Statements 15

ARCHIVE.INDEX.MGMTCLAS
Purpose
The ARCHIVE.INDEX.MGMTCLAS statement specifies the Storage Management Subsystem (SMS)
management class name for Canzlog archive data sets that contain index data (individual index data
sets and primary index data set).

Syntax
The ARCHIVE.INDEX.MGMTCLAS statement has the following syntax:
ARCHIVE.INDEX.MGMTCLAS = *NONE*

ARCHIVE.INDEX.MGMTCLAS = management_class_name

where:
management_class_name
Specifies the 1 - 8 character name of the SMS management class name
*NONE*
Specifies not to use a management class when the new index data set is allocated. This is the default
value.

Usage notes
• The management class is used for index data set management. The NetView program only validates the
length of the management class name. The management class name is then validated by the operating
system when the data set is allocated.
• If you specify a value other than *NONE* for the ARCHIVE.INDEX.DATACLAS,
ARCHIVE.INDEX.MGMTCLAS, or ARCHIVE.INDEX.STORCLAS statement, the NetView program assumes
that you are using SMS to provide archive index data set characteristics and ignores the values of these
statements:
– ARCHIVE.INDEX.BLOCKSIZE
– ARCHIVE.INDEX.SPACE
– ARCHIVE.INDEX.UNIT
– ARCHIVE.INDEX.VOLUME
Whether a data class is explicitly defined to the NetView program by using the
ARCHIVE.INDEX.MGMTCLAS statement, a data class must be selected for data set allocation, and it
must adhere to the following specifications:
– Specify a logical record length (LRECL) 80.
– Specify a block size (BLKSIZE) that is an even multiple of the LRECL (80). Make sure that the block
size is 80 - 32720, inclusive.
– Specify a space allocation that is large enough to accommodate the data set. Remember to consider
the device type and block size when you determine the space allocation.
– Do not specify a retention period (RETPD) or expiration date (EXPDT).
• If you are not running or are not using the SMS facility to provide archive data set characteristics, either
omit the ARCHIVE.INDEX.MGMTCLAS statement or code a value of *NONE* to indicate that data class is
not being used.
• To implement definition changes while the NetView program is active, change the value in the
CNMSTUSR or CxxSTGEN member, and enter the RESTYLE ARCHIVE command. For more information
about changing CNMSTYLE statements, see IBM Z NetView Installation: Getting Started.

16 IBM Z NetView: Administration Reference