|
|
|
Following lists and describes the ADDRESS WTO optional keywords:
Defines the console area ID to display the message. You must use this keyword to specify the console to receive the message. You also must specify the DESC keyword with the values 8 and 9.
You cannot use the AREAID keyword with the REPLY keyword.
Defines the names of the consoles that will receive the WTO or WTOR message. Specify up to 16 alphanumeric console names containing up to eight characters each.
Defines how long OPSWTO suspends processing before executing the current command. You can abbreviate DELAY as DL.
Specify any delay time between 1 and 300 seconds. DELAY has no default value.
In any type of AOF rule except for time-of-day (TOD) and request (REQ) rules, specifying the DELAY keyword, the WAIT keyword, or the REPLY keyword automatically converts an ADDRESS WTO instruction to an OPSWTO command processor and sends it to a server for asynchronous processing.
However, when a TOD or REQ rule contains an ADDRESS WTO command that specifies the DELAY, WAIT, or REPLY keywords, CA OPS/MVS permits the ADDRESS WTO command to execute synchronously. The TOD or REQ rule waits until the ADDRESS WTO command completes before it resumes processing.
Note: The use of the REPLY, WAIT, or DELAY keyword in a TOD rule may delay the execution of other TOD rules.
Defines message descriptor codes for the current message. Descriptor codes are numbers between 1 and 16; codes 1 through 6 and descriptor code 11 are mutually exclusive.
You can assign codes 7 through 10 in combination with any other code, but each code must be unique. If you specify more than one code, separate them with commas as shown in the following example:
DESC(1,7)
The following is a list of additional descriptor codes and their corresponding values:
1-SYSFAIL
2-IMEDACTN
3-EVENACTN
4-SYSSTAT
5-IMEDCMD
6-JOBSTAT
7-APPLPRGM
8-OOLMSG
9-OPERREQ
10-DYNSTAT
11-CRITEVET
12-HILITE
Notes:
Determines how the WTO or WTOR message displays on the console that receives it. Specify HILITE to send a high-intensity, non-scrollable WTO or WTOR, or specify LOWLITE to make the message scrollable and displayed in low intensity.
Designates control and label lines in the WTO message.
Possible values for this keyword are:
Indicates MCS flag values, which are passed to the operating system. Each MCS flag is a unique character string. Following are sample MCS flags:
MCSFLAGS(REG0) MCSFLAGS(BRDCST)
You can specify any of these flag values:
Defines the message ID that prefixes the WTO text. If you omit the MSGID keyword, the OPSWTO command processor uses a default message ID, OPS1371I. Other message IDs can contain up to 10 characters. Message IDs are not padded with blanks.
Suppresses the generation of message OPS1370H, which documents the origin and parameters of the WTO message. NOLOG may only be specified in an AOF rules environment.
Performs the same function that the OPTION argument of the OPSSEND() OPS/REXX built-in function does. Its purpose is to precisely route messages to a specific area in a local or cross-system environment.
If you issue the ADDRESS WTO command from a message rule (for example, to re-route the message), the route and descriptor codes that are used will be the same as those for the original message that caused the rule to execute. You can override this by specifying the ROUTE keyword, DESC keyword, or both in the text of the ADDRESS WTO command.
WTO messages that arrive at a remote copy of CA OPS/MVS through an MSF link are always logged in OPSLOG; however, the OPTION keyword permits you to specify additional processing that should occur for those messages.
Values for OPTION are:
If you specify A in any rule other than a REQ or TOD rule, it is converted to W.
You cannot specify OPTION(A) if you have specified a value for either the REPLY keyword or the TEXTVAR keyword.
You cannot specify OPTION(B) if you have specified a value for either the REPLY keyword or the TEXTVAR keyword.
You cannot specify OPTION(C) if you have specified a value for either the REPLY keyword or the TEXTVAR keyword.
You cannot specify OPTION(L) if you have specified a value for either the REPLY keyword or the TEXTVAR keyword.
The SYSNAME column in OPSLOG on the receiving system will indicate the system from which the message was sent, but the SYSLOG/ OPERLOG will show the message as being locally issued on the receiving system. This differs from option C which issues the message as a foreign or reissued WTO on the receiving system.
Note: Values A and B are not valid for multi-line WTOs. If any of these values are specified for the OPTION keyword in an MLWTO, the OPS1361S message is issued and a return code of 128 is generated.
In any type of AOF rule (except for TOD and REQ rules), specifying the REPLY, WAIT, or DELAY keywords in an ADDRESS WTO instruction automatically converts the ADDRESS WTO instruction to an OPSWTO command processor and sends it to a server for asynchronous processing.
However, when a TOD or REQ rule contains an ADDRESS WTO command that specifies the REPLY, WAIT, or DELAY keywords, CA OPS/MVS permits the ADDRESS WTO command to execute synchronously. The TOD or REQ rule waits until the ADDRESS WTO command completes before it resumes processing.
OPSWTO waits for the operator to respond (for the time specified with the WAIT keyword) and echoes any reply made with the TSO PUTLINE service. This lets a CLIST pick up the reply using TSO SYSOUTTRAP mechanism. For SYSOUTTRAP mechanism details, see the chapter “POI Command Processors.”
Notes:
Defines route codes for the message. You can specify as many route codes as you need to, separated by commas.
A route code is any number between 1 and 128 or one of the following character strings:
Important! Routing codes 30-40 may be specified, but they are considered reserved routing codes by IBM and are ignored.
Defines the subsystem ID of the system that will receive the WTO message.
Sends a WTO message to a remote system. Specify one of these values for SYSTEM:
Output is returned only when you specify a single system name as the value of sysnames. Output may be generated if you specify the WTOID or REPLY keyword.
For the SYSTEM keyword to work, MSF must connect the copies of CA OPS/MVS running on the local and remote systems.
Note: Also, see the description of the SYSWAIT keyword.
Defines the number of seconds (from 1 to 300) of wait time to accommodate communication delays across systems. CA OPS/MVS adds the value of the SYSWAIT keyword to the MSFSYSWAIT value.
Note: Also see the description of the SYSTEM keyword.
Defines the text of a single-line WTO message. This text must meet these criteria:
Following are some sample text strings:
TEXT('this is a test value')
TEXT('put quotes in "double" quotes')
TEXT(' provide a leading blank')
You can insert the contents of a REXX variable into the message text. For example, the following example inserts the contents of variable FIELDA into the message text as a text string:
TEXT('"||FIELDA||"')
Provides the stem for a set of REXX variables, each variable containing one line of a multiline WTO message. You define these variables and assign lines of message text to them in separate statements in the OPS/REXX program that invokes the ADDRESS WTO environment. You are limited to a maximum of 255 lines of message text.
For example, if you specify TEXTVAR(LINE_DATA.), the names of the variables storing lines of your WTO will be LINE_DATA.1, LINE_DATA.2, and so on.
The stem name you specify must meet standard REXX conventions for stem names. If you are not familiar with these conventions, consult The REXX LANGUAGE: A Practical Approach to Programming by M.F. Cowlishaw. You can order a copy of the Cowlishaw book from Prentice-Hall.
Instead of a stem, the TEXTVAR keyword can also specify a valid REXX variable name prefix. For example, if you specify TEXTVAR(PREFIX_DATA), the names of variables storing your WTO are PREFIX_DATA1, PREFIX_DATA2, and so on.
The number of lines of output produced depends on the number of consecutive variables that meet the criteria.
Thus, in the following example:
LineData.1 = "Line1"
LineData.2 = "Line2"
LineData.4 = "Line4"
A command specifying ADDRESS WTO TEXTVAR(“LineData.”) produces only two lines of data output.
Note: The TEXTVAR and REPLY keywords are mutually exclusive.
Defines a one- to four-character name or a one- to four-byte hexadecimal value such as ABCD or X'0A204200'. The token value can be used in delete-operator-message (DOM) processing to delete all messages that have the same token value.
Determines how long OPS/REXX waits for a reply to the WTOR message. You can specify any wait time between 1 and 3600 seconds. As soon as the wait time expires, the WTOR message is deleted.
In any type of AOF rule except for time-of-day (TOD) and request (REQ) rules, specifying the WAIT keyword (or the REPLY or DELAY keywords) in an ADDRESS WTO instruction automatically converts the ADDRESS WTO instruction to an OPSWTO command processor and sends it to a server for asynchronous processing. However, when a TOD or REQ rule contains an ADDRESS WTO command that specifies the REPLY, WAIT, or DELAY keywords, CA OPS/MVS permits the ADDRESS WTO command to execute synchronously. The TOD or REQ rule waits until the ADDRESS WTO command completes before it resumes processing.
Note: Using the REPLY, WAIT, or DELAY keyword in a TOD rule may delay the execution of other TOD rules.
If you specify the WTOID keyword with no argument, OPS/REXX returns the number for the WTO message into the OPS/REXX external data queue.
The optional wtoid argument specifies the name of the variable that will store the WTO ID number. The value returned will be in unprintable binary format.
You can use the REXX C2X function to convert the value to displayable hexadecimal format. For example:
C2X(WTOID_VAR_NAME)
To convert the value to displayable numeric format, use the REXX C2D function. For example:
C2D(WTOID_VAR_NAME)
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |