RETRY - YESINO

defines the default for whether an attempt to allocate a conversation between this NetView and all the domains specified by CDRMDEF statements will be made every 10 minutes if the first attempt fails. Code this keyword in the member identified by the MEM keyword of the TASK statement that has a TASKID of

DSIAMLUT.

YES means the session monitor attempts to establish an initial conver-sation with the other domains once every 10 minutes.

DSTINIT

NO means the session monitor attempts to establish an initial conver-sation with the other domains only once.

Note: The RETRY parameter of the CORMOEF statement can override this default for specific domains.

Related Statements: ALJASMEM, CORMOEF, CNMAUTH, CNMTARG, CTL, INITMOO, LOGINIT, R, REPORTS, TASK, W

F (Filter) Statement

The F statement lets you associate messages to the message indicator classes you defined with the A statement. Based on the tests you specify, a message indicator can be triggered at the authorized receiver. The NETLOG action of the IF-THEN auto-mation statement can also be used to trigger message indicator'S. See "IF-THEN Automation Statement" on page 34 for more information. The F statement is used in the OSICNM member of OSIPARM.

Notes:

1. Messages OSI5311, OSI5591, OSI546I, and OSI5471 are routed to all NetView operators who are logged on. If an operator is in a terminal access facility (TAF) session when a message is sent, the message is not sent to the operator's screen until the TAF session is exited. At that time, the filter and alert in the status monitor is set off. Depending on how much time has elapsed while the operator was in the TAF session, the circumstances under which the message was issued may have changed and the message may no longer be relevant.

2. When the VTAM function MSGMOO=ON is coded, VTAM inserts a five-character module name into all 1ST messages between the message number and the message text. If MSGMOO is coded as ON, the F statements you code for 1ST mes-sages will have unpredictable results.

Code as many F statements for each message as you like. You can code F state-ments only for message indicator classes 1 through 4.

F

is the statement name and must be in column 1.

class

is the message indicator class number and must be from 1 through 4. This value must be in column 5 of the statement. This number corresponds to the class number on the A statement.

msgnum

is the first parsed element of a message (&1). This value must begin in column 7 of the statement.

Note: You can code as many F statements for a message number as you require. NetView classifies the message based upon the first true F statement for the message number. A single F statement can contain.several comparison expressions. Comparison expressions are separated by commas. All of the comparisons on a single F statement must be true for the classification to be made.

F (Filter)

&9

the element selected for comparison to string. The expression must be located in columns 16 through 72. If the expression must continue onto successive lines, make a comma the last character on a line.

aD Domain identifier

ao

Operator identifier aT Time (hh:mm:ss)

aM

The HDRMTYPE from OSITI8. See NetView Customization: Using Assembler for more information on the message header type.

an

The number of the element as parsed by NetView. This number must be from 1 to 255. &1 is the message number.

operator

the logical symbol used to determine the relationship between &e and string.

The following logical symbols are allowed:

=

&e is equal to string.

¢ &e is not equal to string.

>

&e is greater than string .

..., >

&e is not greater than string.

<

&9 is less than string .

...,<

&e is not less than string.

'string •

the value or string you want compared with &e.

continuation expression

the continuation of an expression from the preceding line. Begin the continua-tion statement with an F and then continue the expression in columns 16 through 72.

modname

the name of an optional module that processes &e and returns a value that NetView will compare to string. modname must begin in column 16.

NetView is delivered with the module CNMFANGC, which returns a one-character string that represents the type of node. The type of node depends on the value of &9. You can write other modules to meet your needs or use CNMFANGC or both. Your module or CNMFANGC is invoked with the following registers:

REG1 REG13 REG14 REG15

Address of a parameter list Address of the caller's save area Return address of the calling program Entry-point address of modname.

The parameter list passed in REG1 contains five addresses:

Word Address Description

2 3

4

5

MVTADDR TXTPTR TXTLEN

RESPTR

RESLEN

The MVT address.

The address of &e.

The address of a one-byte field containing the length of &e.

The address of the field containing the result of modname processing. (For CNMFANGC, this is one of the node types described in the following table.) The address of a one-byte field containing the length of the result (pointed to by RESPTR). This word is set to the length of string and cannot be altered. (CNMFANGC

uses this word to blank out RESPTR before putting any-thing in it.)

As an example, CNMFANGC takes &e (a node name) and converts it to one of the following one-character node types:

H Host

N NCP major node L Line

C pu/cluster T Lu/terminal

S Switched major node R Switched PU

Q Switched LU F Local major node

E Local PU D Local LU

B Application major node A Application minor node Y CORM major node

Z

CORM

W CORSC major node X CORSC

BLANK No node found

This result is then compared to string to determine if an alert should be set up.

Related Statements: A, IF-THEN

Dans le document Who Should Use This Book (Page 37-42)