Ordering publications

You can order many Tivoli publications online at http://www.ibm.com/e-business/linkweb/publications/

servlet/pbi.wss
You can also order by telephone by calling one of these numbers:
• In the United States: 800-426-4968
• In Canada: 800-879-2755
In other countries, contact your software account representative to order Tivoli publications. To locate the
telephone number of your local representative, perform the following steps:
1. Go to http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss.
2. Select your country from the list and click the grey arrow button beside the list.
3. Click About this site to see an information page that includes the telephone number of your local
representative.

Accessibility
Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to
use software products successfully. Standard shortcut and accelerator keys are used by the product and
are documented by the operating system. Refer to the documentation provided by your operating system
for more information.
For additional information, see the Accessibility appendix in the User's Guide: NetView.

Tivoli user groups

Tivoli user groups are independent, user-run membership organizations that provide Tivoli users with
information to assist them in the implementation of Tivoli Software solutions. Through these groups,
members can share information and learn from the knowledge and experience of other Tivoli users.

Support information
If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following
ways for you to obtain the support you need:
Online
Please follow the instructions located in the support guide entry: https://www.ibm.com/support/
home/pages/support-guide/?product=4429363.
Troubleshooting information
For more information about resolving problems with the IBM Z NetView product, see the IBM Z
NetView Troubleshooting Guide. You can also discuss technical issues about the IBM Z NetView
product through the NetView user group located at https://groups.io/g/NetView. This user group is for
IBM Z NetView customers only, and registration is required. This forum is also monitored by interested
parties within IBM who answer questions and provide guidance about the NetView product. When a
problem with the code is found, you are asked to open an official case to obtain resolution.

Conventions used in this publication

This section describes the conventions that are used in this publication.

Typeface conventions
This publication uses the following typeface conventions:

xx IBM Z NetView: Administration Reference

 Bold
• Lowercase commands and mixed case commands that are otherwise difficult to distinguish from
surrounding text
• Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons,
list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs,
property sheets), labels (such as Tip:, and Operating system considerations:)
• Keywords and parameters in text
Italic
• Citations (examples: titles of publications, diskettes, and CDs
• Words defined in text (example: a nonswitched line is called a point-to-point line)
• Emphasis of words and letters (words as words example: "Use the word that to introduce a
restrictive clause."; letters as letters example: "The LUN address must start with the letter L.")
• New terms in text (except in a definition list): a view is a frame in a workspace that contains data.
• Variables and values you must provide: ... where myname represents...
Monospace
• Examples and code examples
• File names, programming keywords, and other elements that are difficult to distinguish from
surrounding text
• Message text and prompts addressed to the user
• Text that the user must type
• Values for arguments or command options

Operating system-dependent variables and paths

For workstation components, this publication uses the UNIX convention for specifying environment
variables and for directory notation.
When using the Windows command line, replace $variable with %variable% for environment variables
and replace each forward slash (/) with a backslash (\) in directory paths. The names of environment
variables are not always the same in the Windows and UNIX environments. For example, %TEMP% in
Windows environments is equivalent to $TMPDIR in UNIX environments.
Note: If you are using the bash shell on a Windows system, you can use the UNIX conventions.

Syntax diagrams
The following syntax elements are shown in syntax diagrams. Read syntax diagrams from left-to-right,
top-to-bottom, following the horizontal line (the main path).
• “Symbols” on page xxi
• “Parameters” on page xxii
• “Punctuation and parentheses” on page xxii
• “Abbreviations” on page xxiii
For examples of syntax, see “Syntax examples” on page xxiii.

Symbols
The following symbols are used in syntax diagrams:

Marks the beginning of the command syntax.

About this publication xxi

 Marks the end of the command syntax.

Indicates that the command syntax is continued on the next line.

Indicates that a statement is continued from the previous line.

|
Marks the beginning and end of a fragment or part of the command syntax.

Parameters
The following types of parameters are used in syntax diagrams:
Required
Required parameters are shown on the main path.
Optional
Optional parameters are shown below the main path.
Default
Default parameters are shown above the main path. In parameter descriptions, default parameters
are underlined.
Syntax diagrams do not rely on highlighting, brackets, or braces. In syntax diagrams, the position of
the elements relative to the main syntax line indicates whether an element is required, optional, or the
default value.
When you issue a command, spaces are required between the parameters unless a different separator,
such as a comma, is specified in the syntax.
Parameters are classified as keywords or variables. Keywords are shown in uppercase letters. Variables,
which represent names or values that you supply, are shown in lowercase letters and are either italicized
or, in NetView help, displayed in a differentiating color.
In the following example, the USER command is a keyword, the user_id parameter is a required variable,
and the password parameter is an optional variable.
USER user_id
password

Punctuation and parentheses

You must include all punctuation that is shown in the syntax diagram, such as colons, semicolons,
commas, minus signs, and both single and double quotation marks.
When an operand can have more than one value, the values are typically enclosed in parentheses and
separated by commas. For a single value, the parentheses typically can be omitted. For more information,
see “Multiple operands or values” on page xxiv.
If a command requires positional commas to separate keywords and variables, the commas are shown
before the keywords or variables.
When examples of commands are shown, commas are also used to indicate the absence of a positional
operand. For example, the second comma indicates that an optional operand is not being used:

COMMAND_NAME opt_variable_1,,opt_variable_3

You do not need to specify the trailing positional commas. Trailing positional and non-positional commas
either are ignored or cause a command to be rejected. Restrictions for each command state whether
trailing commas cause the command to be rejected.

xxii IBM Z NetView: Administration Reference

Abbreviations
Command and keyword abbreviations are listed in synonym tables after each command description.

Syntax examples
The following examples show the different uses of syntax elements:
• “Required syntax elements” on page xxiii
• “Optional syntax elements” on page xxiii
• “Default keywords and values” on page xxiii
• “Multiple operands or values” on page xxiv
• “Syntax that is longer than one line” on page xxiv
• “Syntax fragments” on page xxiv

Required syntax elements

Required keywords and variables are shown on the main syntax line. You must code required keywords
and variables.
REQUIRED_KEYWORD required_variable

A required choice (two or more items) is shown in a vertical stack on the main path. The items are shown
in alphanumeric order.
REQUIRED_OPERAND_OR_VALUE_1

REQUIRED_OPERAND_OR_VALUE_2

Optional syntax elements

Optional keywords and variables are shown below the main syntax line. You can choose not to code
optional keywords and variables.

OPTIONAL_OPERAND

A required choice (two or more items) is shown in a vertical stack below the main path. The items are
shown in alphanumeric order.

OPTIONAL_OPERAND_OR_VALUE_1

OPTIONAL_OPERAND_OR_VALUE_2

Default keywords and values

Default keywords and values are shown above the main syntax line in one of the following ways:
• A default keyword is shown only above the main syntax line. You can specify this keyword or allow it
to default. The following syntax example shows the default keyword KEYWORD1 above the main syntax
line and the rest of the optional keywords below the main syntax line.
• If an operand has a default value, the operand is shown both above and below the main syntax line. A
value below the main syntax line indicates that if you specify the operand, you must also specify either
the default value or another value shown. If you do not specify the operand, the default value above the
main syntax line is used. The following syntax example shows the default values for operand OPTION=*
above and below the main syntax line.

About this publication xxiii

 KEYWORD1 OPTION=*
COMMAND_NAME
KEYWORD1 OPTION= *

KEYWORD2 VALUE1

KEYWORD3 VALUE2

Multiple operands or values

An arrow returning to the left above a group of operands or values indicates that more than one can be
selected or that a single one can be repeated.
KEYWORD= (
,

REPEATABLE_OPERAND_OR_VALUE_1

REPEATABLE_OPERAND_OR_VALUE_2

REPEATABLE_OPERAND_OR_VALUE_3

value_n )

Syntax that is longer than one line

If a diagram is longer than one line, each line that is to be continued ends with a single arrowhead and the
following line begins with a single arrowhead.
OPERAND1 OPERAND2 OPERAND3 OPERAND4 OPERAND5 OPERAND6

OPERAND7 OPERAND8

Syntax fragments
Some syntax diagrams contain syntax fragments, which are used for lengthy, complex, or repeated
sections of syntax. Syntax fragments follow the main diagram. Each syntax fragment name is mixed case
and is shown in the main diagram and in the heading of the fragment. The following syntax example
shows a syntax diagram with two fragments that are identified as Fragment1 and Fragment2.

COMMAND_NAME Fragment1

Fragment2

Fragment1
KEYWORD_A= valueA KEYWORD_B KEYWORD_C

Fragment2
KEYWORD_D KEYWORD_E= valueE KEYWORD_F

xxiv IBM Z NetView: Administration Reference

Chapter 1. Location of Statements and Samples

This chapter provides a table that explains the location of statements within samples and the location of
samples within the NetView program.
For information on changes to definition statements from previous releases, refer to the IBM Z NetView
Installation: Migration Guide.

How to Use the NetView Definition Statement Reference

Use the following methods to locate specific definition statement information:
• When you know a statement or keyword name, look it up in alphabetical order. The definition
statements are listed in alphabetical order in their respective chapters. Use the dictionary-style
headings for quick reference.
• When you know an operand name but not the statement with which it is used, locate the operand name
in the index.
• When you know only the sample name and want information on the statements in the sample, use Table
1 on page 1 to find the sample name and its associated statements.

Table 1. Location of Statements within Samples and Location of Samples within the NetView Program
Sample Statements Page Location
AAUCNMTD DSTINIT “DSTINIT” on DSIPARM
page 302
AAUPRMLP All statements are defined in the CNMSTYLE member DSIPARM
and are referenced by the AAUPRMLP member.
A01APPLS STATOPT “STATOPT” on VTAMLST
page 369
A01SNA STATOPT “STATOPT” on VTAMLST
page 369
BNJMBDST All statements are defined in the CNMSTYLE member DSIPARM
and are referenced by the BNJMBDST member.
CNMCMD %INCLUDE “%INCLUDE” on DSIPARM
page 316
CMDDEF “CMDDEF” on
page 286
END “END” on page
307
CNMPOLCY TCP390 “TCP390” on DSIPARM
page 451
CNMSCNFT %INCLUDE “%INCLUDE” on DSIPARM
page 316
ACTION “ACTION” on
page 278
CMDLINE “CMDLINE” on
page 292

© Copyright IBM Corp. 1997, 2019 1

Table 1. Location of Statements within Samples and Location of Samples within the NetView Program (continued)
Sample Statements Page Location
COLUMNHEAD “COLUMNHEAD”
on page 295
HELD “HELD” on page
311
HOLDPCNT “HOLDPCNT” on
page 312
HOLDWARN “HOLDWARN” on
page 313
IMDAREA “IMDAREA” on
page 315
INDENT “INDENT” on
page 318
LASTLINE “LASTLINE” on
page 324
LOCKIND “LOCKIND” on
page 325
MLINDENT “MLINDENT” on
page 331
NOPREFIX “NOPREFIX” on
page 347
NORMAL “NORMAL” on
page 348
NORMQMAX “NORMQMAX”
on page 349
PREFIX “PREFIX” on
page 359
TITLE “TITLE” on page
374
TITLEDATE “TITLEDATE” on
page 375
TITLEDOMID “TITLEDOMID”
on page 377
TITLEOPID “TITLEOPID” on
page 378
TITLESTAT “TITLESTAT” on
page 380
TITLETIME “TITLETIME” on
page 381
CNMSTYLE See Chapter 2, “CNMSTYLE Initialization Statements ,” DSIPARM
on page 9
CNMSTPWD PWD “PWD” on page DSIPARM
202

2 IBM Z NetView: Administration Reference

Table 1. Location of Statements within Samples and Location of Samples within the NetView Program (continued)
Sample Statements Page Location
DSIALATD ALIASMEM “ALIASMEM” on DSIPARM
page 279
DSTINIT “DSTINIT” on
page 302
DSIALTAB COS “COS” on page DSIPARM
297
LU “LU” on page
328
MODE “MODE” on page
332
ORIGNET “ORIGNET” on
page 354
DSIAMLTD All statements are defined in the CNMSTYLE member DSIPARM
and are referenced by the DSIAMLTD member.
DSICNM A (Alert) “A (Alert)” on DSIPARM
page 275
C (Command List) “C (Command
List)” on page
285
F (Filter) “F (Filter)” on
page 307
M (Maximum) “M (Maximum)”
on page 329
O MONIT “O MONIT” on
page 350
O RESET “O RESET” on
page 351
O SECSTAT “O SECSTAT” on
page 351
O SENDMSG “O SENDMSG”
on page 352
SENDMSG “SENDMSG” on
page 367
DSICPINT DSTINIT “DSTINIT” on DSIPARM
page 302
END “END” on page
307
DSICRTTD DEFFOCPT “DEFFOCPT” on DSIPARM
page 299
DSTINIT “DSTINIT” on
page 302

Chapter 1. Location of Statements and Samples 3

Table 1. Location of Statements within Samples and Location of Samples within the NetView Program (continued)
Sample Statements Page Location
END “END” on page
307
DSIDB2DF SUBSYSTEM “SUBSYSTEM” DSIPARM
on page 372
DSIELMEM DSTINIT “DSTINIT” on DSIPARM
page 302
DSIELXIT END “END” on page DSIPARM
307
DSIHINIT DSTINIT “DSTINIT” on DSIPARM
page 302
END “END” on page
307
PARTNER “PARTNER” on
page 355
RETRY “RETRY” on page
364
DSIILGCF All statements are defined in the CNMSTYLE member DSIPARM
and are referenced by the DSIILGCF member.
DSIKINIT DSTINIT “DSTINIT” on DSIPARM
page 302
DSILOGBK All statements are defined in the CNMSTYLE member DSIPARM
and are referenced by the DSILOGBK member.
DSILUCTD All statements are defined in the CNMSTYLE member DSIPARM
and are referenced by the DSILUCTD member.
DSIOPF %INCLUDE “%INCLUDE” on DSIPARM
page 316
END “END” on page
307
OPERATOR “OPERATOR” on
page 353
PROFILEN “PROFILEN” on
page 362
DSIPRFxx AUTH “AUTH” on page DSIPRF
280
DOMAINS “DOMAINS” on
page 301
END “END” on page
307
ISPAN “ISPAN” on page
319
PROFILE “PROFILE” on
page 361

4 IBM Z NetView: Administration Reference

Table 1. Location of Statements within Samples and Location of Samples within the NetView Program (continued)
Sample Statements Page Location
SPAN “SPAN” on page
368
DSIPROFxx AUTH “AUTH” on page DSIPRF
280
DOMAINS “DOMAINS” on
page 301
END “END” on page
307
ISPAN “ISPAN” on page
319
PROFILE “PROFILE” on
page 361
SPAN “SPAN” on page
368
DSIQTSKI CMDRCVR “CMDRCVR” on DSIPARM
page 294
REP “REP” on page
363
TASK “TASK
(DSIQTSKI)” on
page 373
DSIREXCF All statements are defined in the CNMSTYLE member DSIPARM
and are referenced by the DSIREXCF member.
DSIRHOST ACCESS “ACCESS” on DSIPARM
page 277
DSIROVSI DSTINIT “ACCESS” on DSIPARM
page 277
DSIRSHCF All statements are defined in the CNMSTYLE member DSIPARM
and are referenced by the DSIRSHCF member.
DSIRTTTD All statements are defined in the CNMSTYLE member DSIPARM
and are referenced by the DSIRTTTD member.
DSISECUR RMTSEC “RMTSEC” on DSIPARM
page 365
DSISVRTD DSTINIT “DSTINIT” on DSIPARM
page 302
DSITCPCF All statements are defined in the CNMSTYLE member DSIPARM
and are referenced by the DSITCPCF member.
DSITCPRF NETCONV_IP “NETCONV_IP” DSIPRF
on page 334
WEB_SERVER “WEB_SERVER”
on page 384

Chapter 1. Location of Statements and Samples 5

Table 1. Location of Statements within Samples and Location of Samples within the NetView Program (continued)
Sample Statements Page Location
DSITRCBK DSTINIT “DSTINIT” on DSIPARM
page 302
LOGINIT “LOGINIT” on
page 327
DSIVPARM DSTINIT “DSTINIT” on DSIPARM
page 302
VPDINIT “VPDINIT” on
page 383
DSIWBMEM All statements are defined in the CNMSTYLE member DSIPARM
and are referenced by the DSIWBMEM member.
DSI6INIT DEFENTPT “DEFENTPT” on DSIPARM
page 298
DEFFOCPT “DEFFOCPT” on
page 299
DSTINIT “DSTINIT” on
page 302
RETRY “RETRY” on page
364
DUIFPMEM All statements are defined in the CNMSTYLE member DSIPARM
and are referenced by the DUIFPMEM member.
DUIGINIT See Chapter 9, “Graphic Monitor Facility Host DSIPARM
Subsystem Statements,” on page 531
DUIIGHB All statements are defined in the CNMSTYLE member DSIPARM
and are referenced by the DUIIGHB member.
DUIISFP AMELINIT “AMELINIT” on DSIPARM
page 280
DSTINIT “DSTINIT” on
page 302
EKGCUST See Chapter 8, “Resource Object Data Manager CNMSAMP
Definition Statements,” on page 511
EZLCFG01 See Chapter 4, “Policy File Definitions,” on page 387 DSIPARM
EZLINSMP See Chapter 5, “Inform Policy Member,” on page 467 DSIPARM

Statement Formats
The format of a definition statement is:
• Statement name
• General introduction
The general introduction explains overall options, assumptions, and the purpose of the statement. Each
introduction explains the name of the member and where you code the statement.
• Definition statement syntax

6 IBM Z NetView: Administration Reference