PIPE EDIT
Syntax
Syntax
Synonyms
| Stage Operands | Synonym |
|---|---|
| AUTOTOKEN | AUTOTOKE, IFRAUTOK |
| C2GV | C2VG |
| COLOR | COLOUR, LINEATTR, LINEATTRS |
| COPYREV | COPYREVERSE, REVERSECOPY, REVCOPY |
| DESC | IFRAUWDS |
| FINDLINE | LINE |
| GV2C | VG2C |
| IFRAUHND | AUTOMATED |
| JOBNAME | JOBID, IFRAUWJA |
| JOBNUM | IFRAUWJU |
| LEFT | L |
| LASTLINE | LL |
| LINEORIGIN | LINEORIGN |
| MCSFLAGS | MCSFLAG |
| MSGORIGIN | MSGORIGN |
| MSGSENDR | MSGSENDER |
| NEXT | N |
| NEXTLINE | NL |
| NEXTWORD | NW |
| READLINE | RL |
| RIGHT | R |
| ROUTECODES | ROUTCDE, IFRAUWRT |
| SYSCONID | IFRAUCON |
| TOPLINE | TL |
| UCHARS | IFRAUSRC |
| UFLAGS | IFRAUSRB |
| WORD | TOKEN, W1, W2, ... W9 |
| WRITELINE | WL |
Command Description
- Message or command data
- Line attributes
- Message attributes
- Literal data
With EDIT, messages or commands can be created or reformatted in any fashion that you want. In some cases modification of the message attributes and line attributes are also supported.
- Avoid creating a loop in REXX to manipulate messages.
- Improve performance. Editing within a pipeline flow is faster than driving a command to make the changes.
- Preserve message attributes while changing the message text.
- Improve programmer productivity when writing procedures to manipulate message data.
When used as a first stage, EDIT can be used to create multiline messages from literals.
- Defining padding characters.
- Defining how message data is parsed.
- Providing messages or commands from the input stream to the edit phrase.
- Writing messages or commands from the edit phrase to the output stream.
- Edit phrases operate on only one line at a time. Global orders control which line of a multiline message is processed by the edit phrase.
- There are many environments in which edit orders can be run:
- PIPE EDIT
- WHEN statements
- REVISE statements
- Acquire
- AutoEdit
- Common Base Events
- All orders that are valid for REVISE actions are also valid for WHEN actions, except that when used for output only, the NEXT, NEXTWORD, and numeric char position can be used.
- Input Orders
- These orders define the source of data that is processed by the
conversion and output orders of the edit phrase. Examples of input
orders include:
- Literal data
- Message attributes
- Line attributes
- All or part of the message data
- Conversion Orders
- These orders define how the data is to be manipulated. Conversion
orders are optional. Examples of conversion orders include:
- Data conversion, such as from binary to character
- Date/time conversion
- Selecting a subset of the data
- Output Orders
- These orders define how the resulting data is to be placed in the output line and subsequently on the output data stream.
Together, global orders and edit phrases define an edit script. An edit script can be simple with one edit phrase, or a complex message processing program with hundreds of global orders and edit phrases. For an example of complex edit processing, see sample CNME2011 (SESMGET). To begin with simple examples, see Example: Selecting a Word and Example: Creating a Command.
Some simple examples are shown at the end of this help.
| Global Order | Task Performed |
|---|---|
| CONSZERO | Sets the 4-byte console ID to zero. |
| COPY | Copies one or more unread lines in a multiline message from input to output. The order of output is in ascending order. |
| COPYREST | Copies all unread lines in a multiline message from input to output. |
| COPYREV | Copies one or more lines in a multiline message from input to output. The order of output is in descending order. |
| FINDLINE n | Changes the current line to the absolute line number indicated by the argument. |
| FINDLINE /string/ | Advances the current line to the line that contains the specified target string. |
| FWDLINE n | Moves the current line forward by the number specified. |
| LASTLINE | Resets the input to the last line of a multiline message. |
| LOGTO | Sets an option to log the messages that are displayed using the CONSOLE stage or ROUTE stage. |
| NAMEBIND | Creates a name/value pair that is recognized by the alert and message adapters. |
| NEXTLINE | Specifies both the READLINE and WRITELINE keywords, and advances both the input message line (source) and the output message line (destination). |
| NOEXPOSE | Sets the IFRAUNEX automation flag. |
| NOLOGTO | Sets an option to not log the messages that are displayed using the CONSOLE stage or ROUTE stage. |
| NOTECHO | Turns off the echo flag (WQEMCSM) in the message that is logged or automated. NOTECHO does not affect the display. |
| ONTO | Redefines the logical end of the input line. |
| PAD | Defines the padding character to be used by all other orders. |
| PARSE | Defines how the WORD input order counts words. |
| READLINE | Provides the next line of a multiline message to the input orders. |
| RESET | Cancels all existing SKIPTO and UPTO orders. |
| RESETAUTO | Sets the IFRAUHND, IFRAUMTB, and IFRAUNEX automation flags to 0. |
| ROUTEZERO | Overrides route codes for a specific message. |
| SETACTION | Sets the IFRAUACN and IFRAUNVD automation flags. |
| SETAUTO | Sets the IFRAUMTB automation flag to 1. |
| SETBEEP | Sets an audible alarm for message output. |
| SETCLEAR | Sets the IFRAUCLR automation flag. |
| SKIPTO | Redefines the logical start of the input line. |
| TOPLINE | Resets the input to the first line of a multiline message. |
| UPTO | Redefines the logical end of the input line. |
| WRITELINE | Writes all text built by the output orders to the output message. |
| Input Order | Task Performed |
|---|---|
| AIFR | Specifies that the input is the 256-byte AIFR body. |
| ALL | Inputs the text in the current line. Same as 1.*. |
| ASTYPE | Indicates how the address space was started (job type). |
| AUTHGRP | Specifies the ACEE group ID (ACEEGRPN),
if available. If it is not available, returns *UNKNWN*. The values that are supplied for the AUTHUSER and AUTHGROUP input orders are derived from the ACEE that is active at the time the message is routed through the z/OS® subsystem interface. Certain authorized programs issue messages in an environment that causes them to be routed asynchronously through the CONSOLE address space. These messages show |
| AUTHISSUER | Specifies whether the program that issued the WTO is APF-authorized or not. |
| AUTHUSER | Specifies the z/OS ACEE user ID (ACEEUSRI), if available.
If it is not available, returns *UNKNWN*. The values that are supplied for AUTHUSER and AUTHGROUP input orders are derived from the ACEE that is active at the time the message is routed through the z/OS subsystem interface. Certain authorized programs issue messages in an environment that causes them to be routed asynchronously through the CONSOLE address space. These messages show |
| CHKEY | Obtains the CHKEY as defined by system macro IEECHAIN. This is the step-name of a task or the job-name of a job. |
| CMDX | Inputs the first 88 (X'58') bytes of the IEZVX101 control block. |
| COLOR | Inputs text describing the line attributes. |
| CONSAUTH | Indicates the authority of the console issuing the command. |
| CONSNAME | Obtains the console name, or indicates the name of the console issuing the command. |
| CURRGMT | Obtains an 8-byte store clock value generated at the time the order is executed. |
| CZID | Obtains the Canzlog ID of a message or command or DOM that has been logged. |
| D4NV | Indicates whether the console name to which a message is delivered is owned by a NetView® task. |
| DELETE | Determines whether a message has been deleted. |
| disposition | Provide information about the disposition of the message. |
| flag_bytes | Produces a string that corresponds to the bit in the referenced flag byte. |
| FLGDSCDn | Indicates that the specified descriptor code byte is to be read. |
| FLGRTCDn | Indicates that the specified route code byte is to be read. |
| FLOODACT |
Indicates whether Message Flood Automation has acted upon the message. |
| HDRMTYPE | Indicates that the one-byte message type indicator is to be read. |
| hexstring | Specifies a hexadecimal string. |
| IFRAUHND | Use as input the automation action flag from the message. |
| IFRAUIN3 | Indicates that the 32 bits that are defined as IFRAUIN3 are used as input. |
| IFRAUMTB | Use as input the automation submission flag from the message. |
| IFRAUNEX | Use as input the forbid exposure flag from the message. |
| JOBNAME | Indicates the job name. |
| LEVEL | Specifies the data set concatenation level of the current line. |
| lineattr | Specifies that the input is one of the line attributes of the current line. |
| LINESENDER | Specifies the name of the sender. |
| MCSFLAGS | Provides a 16-bit output suitable as input to a C2B conversion. |
| MRT | Indicates that the message has been exposed to the Message Revision Table. |
| msgattr | Specifies that the input is one of the message attributes of the current message. |
| MSGID | The message identifier of the received message. |
| MSGSENDR | Indicates the name of the task that created or most recently sent the message. |
| MSUSEG | Indicates the contents of one segment of an MSU. |
| NVABLE | Returns "Yes" if a NETVONLY action
can succeed, otherwise returns "No". A NETVONLY action cannot succeed if the NetView procedural space is down, the subsystem router is down, or if the task defined by the ?MVSCmdRevision CNMSTYLE statement is inactive. |
| position.length | Specifies the subset of the input line to be processed. The subset is defined by specifying a starting character and the total number of characters. |
| REPLYL | Returns the length of the reply ID in decimal format, with a leading plus sign (+). |
| SESSID | Specifies the TAF session ID for messages from TAF or SAF ID of messages received from the PPI. |
| /string/ | Specifies a delimited character string. |
| UCHARS | Obtains the 16-byte "user char" area. In the MRT, this field is available only if previously set. |
| UFLAGS | Obtains the 2-byte "user flags" area. In the MRT, this field is available only if previously set. |
| WORD | Specifies the subset of the input line to be processed. The subset is defined by specifying a starting word and the total number of words. |
| WQE | Enables the WQE for conversion. |
| WTOKEY | Obtains the key field associated with the WTO system macro, which is the WQEKEY in system macro IHAWQE. |
| Conversion Order | Task Performed |
|---|---|
| ASTYPE | From a 2-byte binary ASID, a one-character
value is returned. Note: The message revision table (MRT) supports
ASTYPE only as an input order.
|
| B2C | Converts string of Boolean values to a character string. |
| CHKEY | Obtains the CHKEY as defined by system macro IEECHAIN. This is the step-name of a task or the job-name of a job. |
| C2B | Converts input to a string of Boolean values. |
| C2D | Converts input to a string representing a decimal number. |
| C2F | Converts input to a string representing a signed floating point number. |
| C2G | Converts fixed-length string to double-byte (DBCS) string. |
| C2GV or C2VG | Converts varying length string to double-byte (DBCS) string. |
| C2P | Converts a packed-decimal number into a signed decimal. |
| C2S | Converts internal, floating point data into a 14-byte output string. |
| C2V | Converts a varying length string to a character string. |
| C2X | Converts input to a string representing its hexadecimal notation. |
| CHKEY | Obtains the CHKEY as defined by system macro IEECHAIN. This is the step-name of a task or the job-name of a job. |
| CNVDT | Converts the input from one date or time format to another. If the input cannot be converted, it is passed unchanged to the output. |
| CNVDT0 | Converts the input from one date or time format to another. If the input cannot be converted, no data is output. |
| D2C | Converts a signed integer number into a fullword. |
| D2X | Converts a decimal number to hexadecimal representation. |
| DT | Assumes that the input text is a
store clock (STCK) and converts the value to a readable 17-character
string for the local time zone in the format MM/DD/YY HH:MM:SS. Note: The current GMT offset is used in interpreting the local
date and time, whether a different offset was in effect at the given
date and time. For example, if the given value was before the latest
daylight saving time adjustment, the result can be off one hour from
another interpretation of the same date and time of an application.
|
| DTS | Assumes that the input text is a
17-character local time in the format MM/DD/YY HH:MM:SS and converts it to a store clock (STCK) value. Note: The current
GMT offset is used in interpreting the local date and time, whether
a different offset was in effect at the given date and time. For example,
if the given value was before the latest daylight saving time adjustment,
the result can be off one hour from another interpretation of the
same date and time of an application.
|
| ETIME | Converts the store clock (STCK) to a decimal number indicating the elapsed time in microseconds since NetView startup. |
| FOUND | Normally used after a SKIPTO or FINDLINE
operation, FOUND translates a null string into No and any other string into Yes. |
| F2C | Converts a signed floating point number into a doubleword. |
| G2C | Converts double-byte (DBCS) data to single-byte (SBCS) data. |
| GV2C or VG2C | Converts double-byte (DBCS) data into a varying length single-byte (SBCS) string. |
| JOBNAME | From a 2-byte binary ASID, the corresponding job name is returned. |
| LEFT | Truncates or pads the input to the length specified. Characters are counted from the beginning, or left, of the input. |
| NOT |
|
| ODDBYTES | Alternately, keeps and discards the input data. |
| OPDT | Assumes that the input text is a store clock (STCK) and converts the value to a readable 17-character string representing the date and time in the format specified by the DEFAULTS command. |
| P2C | Converts a signed decimal number into packed-decimal. |
| PREFIX | Adds a constant to the beginning of a string. |
| RIGHT | Truncates or pads the input to the length specified. Characters are counted from the end, or right, of the input. |
| RVAR | From an input revision variable name, returns the current value or a null string. |
| SQUEEZE | Specifies that delimiter characters at the start, at the end, and within the data are to be removed. The delimiter characters are defined by the most recent PARSE global order specification. |
| STRIP | Removes all padding characters from the beginning and end of the input. |
| STRIPL | Removes all padding characters from the beginning of the input. |
| STRIPR | Removes all padding characters from the end of the input. |
| SUBSTR | Selects a subset of the input data. |
| UPCASE | Translates the standard 26-character Latin letters (as defined in code page 037) to uppercase. The asterisk argument is required. |
| V2C | Converts input to a varying length string. |
| X2C | Converts character data to internal hexadecimal format. |
| YESNO | Converts a 1-byte field to the character
string Yes or No. |
| ZDT | Assumes that the input text is a
store clock (STCK) and converts the value to a readable character
string for Greenwich Mean Time in the format MM/DD/YY HH:MM:SS. |
| Output Order | Task Performed |
|---|---|
| ACTIONFLAG | Sets the one-character message prefix that is shown on a z/OS console before the text of an action message. |
| AUTOTOKEN | Sets the 8-character automation token in the message (IFRAUTOK). |
| COLOR | Sets presentation attributes for the output line. |
| CONSNAME | Sets the console name. |
| DELETE | Deletes a message or command, or undeletes a previously deleted message or command. |
| disposition | Control or change the disposition, subject to certain system constraints. |
| FINDLINE | Functions the same as global order FINDLINE n except that the target to be found is derived from the previous input order or conversion order. If the number is negative, EDIT counts from the end of the message. |
| flag_bytes | Accepts a string that corresponds to the bit in the referenced flag byte. |
| FLGDSCDn | Indicates that the specified descriptor code byte is to be written. |
| FLGRTCDn | Indicates that the specified route code byte is to be written. |
| HDRMTYPE | Indicates that the one-byte message type indicator is to be written. |
| LINETYPE | Defines the line type attribute of the output line. |
| MRT | Indicates that the message has been exposed to the Message Revision Table. |
| NEXT | Specifies that the input is to be placed into the output without an intervening blank. |
| NEXTWORD | Specifies that the input is to be placed into the output with an intervening blank. |
| position | Specifies that the data is to be placed in the output line beginning at the character indicated by position. |
| SETGMT | Sets the IFRAUGMT value of the output message and zeros out the CANZLOG reference in the output message. The order is carried out only if the input available is exactly eight bytes. |
| UCHARS | Sets a 16-byte "user char" area. When used as an output order, you can specify data with a length other than 16. If the length is shorter than 16, it uses that; if the length is greater than 16, then it truncates the length to 16. |
| UFLAGS | Sets a 2-byte "user flags" area. UFLAGS (much like UCHARS) is supported as an input or output order in both the MRT and PIPE EDIT. For the MRT, this field accepts a string of up to 16 characters consisting of 0s, 1s, and Xs. These correspond to the requirement to clear, set, or leave intact the corresponding bit in the byte being referenced. For PIPE EDIT, you can specify data with a length other than 2. If the length is shorter than 2, it uses that; if the length is greater than 2, then it truncates the length to 2. |
| WTOKEY | For the Message Revision Table (MRT), WTOKEY sets the key field associated with the WTO system macro, which is the WQEKEY in system macro IHAWQE. |
| EDIT Order | PIPE | MRT REVISE and WHEN | CRT REVISE and WHEN | Auto Edit and Acquire |
|---|---|---|---|---|
| ACTIONFLAG | X | |||
| AIFR | X | X | ||
| ALL | X | X | X | X |
| AMRF | X | |||
| ASID | X | X | X | X |
| ASTYPE | X | X | X | X |
| AUTHGRP | X | X | X | |
| AUTHISSUER | X | |||
| AUTHUSER | X | X | X | |
| AUTOMATE | X | |||
| AUTOMATED | X | X | ||
| AUTOTOKEN | X | X | X | |
| B2C | X | X | ||
| BROADCAST | X | |||
| C2B | X | X | X | X |
| C2D | X | X | X | X |
| C2F | X | X | ||
| C2G | X | X | ||
| C2GV | X | X | ||
| C2P | X | X | ||
| C2S | X | X | ||
| C2V | X | X | ||
| C2VG | X | X | ||
| C2X | X | X | X | X |
| CHKEY | X | X | X | |
| CMDX | X | |||
| CNVDT | X | X | ||
| CNVDT0 | X | X | ||
| COLOR | X | X | X | |
| CONSAUTH | X | |||
| CONSNAME | X | X | ||
| CONSZERO | X | |||
| COPY | X | X | ||
| COPYREST | X | X | ||
| COPYREV | X | X | ||
| CURRGMT | X | X | X | |
| CZID | X | X | ||
| D2C | X | X | X | X |
| D2X | X | X | X | X |
| D4NV | X | |||
| DELETE | X | X | ||
| DESC | X | X | ||
| DISPLAY | X | |||
| DT | X | X | ||
| DTS | X | X | ||
| ETIME | X | X | ||
| F2C | X | X | ||
| FINDLINE | X | X | ||
| flag_bytes | X | |||
| FLGDSCDn | X | |||
| FLGRTCDn | X | |||
| FLOODACT | X | |||
| FOUND | X | X | X | X |
| FWDLINE | X | X | ||
| G2C | X | X | ||
| GV2C | X | X | ||
| HDRMTYPE | X | X | ||
| IFRAUCON | X | X | ||
| IFRAUCPY | X | X | ||
| IFRAUGMT | X | X | ||
| IFRAUHND | X | X | ||
| IFRAUIN3 | X | X | ||
| IFRAUMTB | X | X | ||
| IFRAUNEX | X | X | ||
| IFRAUPPT | X | X | ||
| IFRAUPRI | X | X | ||
| IFRAUSDR | X | X | ||
| IFRAUSEC | X | X | ||
| IFRAUTOK | X | X | ||
| IFRAUWAS | X | X | ||
| IFRAUWDS | X | X | ||
| IFRAUWJA | X | X | ||
| IFRAUWJU | X | X | ||
| IFRAUWRT | X | X | ||
| JOBNAME | X | X | X | X |
| JOBNUM | X | X | X | |
| LASTLINE | X | X | ||
| LEFT | X | X | X | X |
| LEVEL | X | |||
| LINE | X | X | ||
| LINEATTR | X | X | X | |
| LINECOUNT | X | |||
| LINEORIGIN | X | X | ||
| LINESENDER | X | X | ||
| LINETYPE | X | X | ||
| LOGTO | X | |||
| MCSFLAGS | X | X | X | |
| MRT | X | X | ||
| MSGCOUNT | X | |||
| MSGID | X | X | X | |
| MSGORIGIN | X | X | ||
| MSGSENDR | X | X | ||
| MSUSEG | X | X | ||
| NAMEBIND | X | X | ||
| NEXT | X | X | X | X |
| NEXTLINE | X | |||
| NEXTWORD | X | X | X | X |
| NOEXPOSE | X | |||
| NOLOGTO | X | |||
| NOT | X | X | X | X |
| NOTECHO | X | |||
| NVABLE | X | |||
| ODDBYTES | X | X | ||
| ONTO | X | X | X | X |
| OPDT | X | X | ||
| P2C | X | X | ||
| PAD | X | X | X | X |
| PARSE | X | X | X | X |
| position | X | X | X | X |
| PREFIX | X | X | ||
| PROG | X | |||
| READLINE | X | X | ||
| RESET | X | X | X | X |
| RESETAUTO | X | |||
| RIGHT | X | X | X | X |
| ROUTECODES | X | X | ||
| ROUTEZERO | X | |||
| RVAR | X | X | ||
| SESSID | X | X | ||
| SETACTION | X | X | ||
| SETAUTO | X | |||
| SETBEEP | X | X | ||
| SETCLEAR | X | |||
| SETGMT | X | |||
| SKIPTO | X | X | X | X |
| SQUEEZE | X | X | X | X |
| STRIP | X | X | X | |
| STRIPL | X | X | X | |
| STRIPR | X | X | X | |
| SUBSTR | X | X | X | X |
| SYSCONID | X | X | ||
| SYSLOG | X | |||
| SYSNAME | X | X | ||
| TOKEN | X | X | X | |
| TOPLINE | X | X | ||
| UCHARS | X | X | X | |
| UFLAGS | X | X | X | |
| UPCASE | X | X | X | |
| UPTO | X | X | X | X |
| V2C | X | X | ||
| VG2C | X | X | ||
| W1, W2, ... W9 | X | X | ||
| WORD | X | X | X | X |
| WQE | X | |||
| WRITELINE | X | |||
| WTOKEY | X | X | X | |
| X2C | X | X | X | X |
| YESNO | X | X | X | X |
| ZDT | X | X |
Streams
| Stream Type | Number Supported |
|---|---|
| Input | 1 |
| Output | 1 |
Termination Conditions
EDIT terminates when the input stream and the output streams are disconnected.
Operand Descriptions
Usage Notes
- Code one edit phrase or one global order on each source line because edit scripts consisting of many edit phrases can be difficult to read. Together with appropriate commentary, your edit script is easy to understand. See sample CNME2011 (SESMGET) for an example of this type of coding.
- When converting date and time values using CNVDT or CNVDT0, if
the input data is longer than the specified input format, only a substring
of the input data is compared and converted. The remainder remains
as-is in the output. For example, the following statements convert the first 8 characters, the date portion, of the Greenwich Mean Time, to the date format specified by the DEFAULT command:
PIPE ...|EDIT IFRAUGMT ZDT CNVDT ('MM/DD/YY' DATE) NEXT|...The last 9 characters remain in their original input format in the output.
In date conversion, the first, or leading, characters of the input are converted. In time conversion, the last, or trailing characters of the input are converted. For example, the following statements convert the time portion of the GMT:PIPE ...|EDIT IFRAUGMT ZDT CNVDT ('HH:MM:SS' TIME) NEXT|...
Common Operands and Keywords
- hexstring
- Specifies a hexadecimal string. A hexstring can be in either of the following forms:
- 'nnnnnn'X
- X'nnnnnn'
Before processing, the hexstring is converted to the corresponding character string.
When used as an input order operand, hexstring acts as a literal to be used as input.
- position.length
- The starting position and number of characters to be
processed.
Position indicates the starting character within the line. By default, position is counted from the first character of the line. For input orders, the starting point for the count can be modified by the global orders.
Position can be any positive or negative number. A negative value for position indicates that the starting position is to be counted from the end of the line, rather than from the beginning.
Length is an unsigned positive number indicating the number of characters from position to be processed. An asterisk (*) can be specified for length indicating that all characters after position are to be used. Position without length and the period (.) separator defaults length to 1.
If length is larger than the available characters, all available characters are used. The LEFT conversion order can be used to pad the resulting text if required.
Consider the following message:PIPES CAN BE FUN!- This...
- Results in...
- 1.*
PIPES CAN BE FUN!- +7.6
CAN BE- -7.*
BE FUN!- 9.20
N BE FUN!- 8
A- -25.5
- a null string is returned
- -18.3
- PI
- number
- An unsigned positive number. See the descriptions for the orders using number to determine the meaning of number.
- /string/
- A delimited character string. When used as an input order, /string/ defines a literal to be used as input.
See the descriptions for other orders using /string/ to determine the meaning of /string/.
The plus sign (+), minus sign (-), and asterisk (*) have special meanings in edit scripts. To avoid confusion, do not use these characters as /string/ delimiters in edit scripts.
Global Orders
- CONSZERO (global order)
- Sets the 4-byte console ID to zero.
- COPY (global order)
- COPY is used when the input is a multiline message. COPY copies
one or more lines from the input to the output. Unlike COPYREST,
COPY copies beginning with the current line, in ascending order. One of the following parameters is required:
- *
- Indicates all remaining lines in the input are to be copied.
- number
- A non-negative number indicating the number of lines to be copied.
COPY includes the current output line. If you want the first line of a multiline message to become the last line, you can code the following command stream:EDIT 1.* 1 /* get first line and output at position 1 */ READLINE /* Get next line */ COPY * /* copy lines 2 through end to output */ WRITELINE /* write first line */The WRITELINE in this example is required because COPYREST cancels the implied WRITELINE created by the output order 1. See the description of WRITELINE for more information.
- COPYREST (global order)
- COPYREST is used when the input is a multiline message. COPYREST
copies all unread lines from the input to the output. It is the equivalent
of coding the following process for all input messages minus one:
READLINE 1.* 1 WRITELINECOPYREST does not affect or write the current output line. If you want the first line of a multiline message to become the last line, you can code the following process:
The WRITELINE in this example is required because COPYREST cancels the implied WRITELINE created by the output order 1. See WRITELINE for more information.EDIT 1.* 1 /* get first line and output at position 1 */ COPYREST /* copy lines 2 through end to output */ WRITELINE /* write first line */ - COPYREV (global order)
- COPYREV is used when the input is a multiline message. COPYREV
copies one or more lines from the input to the output. Unlike COPY,
COPYREV begins with the current line, copies the number of lines requested,
and displays the output in reverse order. One of the following parameters is required:
- *
- Indicates all remaining lines in the input are to be copied.
- number
- A non-negative number indicating the number of lines to be copied.
- FINDLINE n (global order)
- Changes the current line to the absolute line number indicated
by the argument. Note that FINDLINE 1 is
equivalent to TOPLINE. If the number specified is greater than the
number of lines in the current message, a null line is used for subsequent
input orders.
If the number is negative, EDIT counts from the end of the message. For example, LINE -1 selects the last line of a multiline message and LINE -2 selects the next to last line. LINE 0 (zero) results in a null line.
- FINDLINE /string/ (global order)
- Advances the current line forward to a line containing the specified target string. If no line after the current line contains the target, a null line is used for subsequent input orders.
- FWDLINE n (global order)
- Moves the current line ahead by the number specified.
- LASTLINE (global order)
- Cancels all previous READLINE orders and performs a RESET. Input
is set to the last line of the multiline message.
LASTLINE is a complementary function to TOPLINE. Where LASTLINE sets the input to the last line, TOPLINE sets the input to the first line of the multiline message.
See also TOPLINE.
- LOGTO (global order)
- Sets an option such that if the message is presented for display
using either the CONSOLE stage or the ROUTE stage, the message is
logged. One of these arguments is required:
- N
- This action is for the net log.
- S
- This action is for the system log.
- H
- This action is for the hardcopy log.
- *
- This action is for all three log methods: net log, system log, and hardcopy log.
Usage:- If the message is automated, then automation can override the logging options set by EDIT. If the message is delivered to a distributed autotask, then the log options are honored on the local domain, but is reset to default values by RMTCMD message forwarding. Also, if a message is routed directly to a remote domain, the options are reset to default values.
- Messages that are exposed for logging are always written to the CanzLog file. You can control visibility of your messages in the CanzLog file by using the TAG keyword of the LOGTO stage.
- NAMEBIND (global order)
- NAMEBIND writes the value of the /name/ and the text previously produced by other output orders, if any,
to a new output line. Both the /name/ and
the output line data are preceded in the output line by a halfword
length value. The message ID (HDRMTYPE) and the line counter
meet the name binding requirements for events sent to the NetView Alert and Message Adapters.
Lines created by NAMEBIND can be transferred to the adapter using the PPI stage. Examples of NAMEBIND can be found in Example: Sending an Alert to the NetView Alert Adapter, CNMEALUS, and CNMEMSUSCNMEALUS and CNMEMSUS. For more information about PPI, see PIPE PPI. see HELP PIPE PPI.
To create a valid adapter name/value pair binding, do one of these items:- Copy the original contents of the automated alert or message to
the output using a COPY * EDIT order. Note: This step is required for alert automation. Alerts cannot be modified. For message automation messages can be modified using other EDIT orders prior to sending them to the output.
- Choose names and values consisting of displayable EBCDIC characters.
- Specify /name/ with a maximum 31 characters
beginning with an alphabetic character. Note: The name specified in /name/ must also be defined in the Tivoli® Event Adapter Profiles. IHSAACDS and IHSAMFMT are DSIPARM samples of adapter profiles.
Note: Because NAMEBIND causes a line to be written, it cancels implicitly WRITELINE orders in effect. - Copy the original contents of the automated alert or message to
the output using a COPY * EDIT order.
- NEXTLINE (global order)
- This specifies both the READLINE and WRITELINE keywords, and advances both the input message line (source) and the output message line (destination).
- NOEXPOSE (global order)
- Sets the IFRAUNEX automation flag. Subsequent routing of the message within a domain or cross-domain does not result in automation, message trapping, user exits, or logging.
- NOLOGTO (global order)
- Sets an option such that if the message is presented for display
using either the CONSOLE stage or the ROUTE stage, the message is
not logged. One of these arguments is required:
- N
- This action is for the net log.
- S
- This action is for the system log.
- H
- This action is for the hardcopy log.
- *
- This action is for all three log methods: net log, system log, and hardcopy log.
Usage:- If the message is automated, then automation can override the logging options set by EDIT. If the message is delivered to a distributed autotask, then the log options are honored on the local domain, but is reset to default values by RMTCMD message forwarding. Also, if a message is routed directly to a remote domain, the options are reset to default values.
- Messages that are exposed for logging are always written to the Canzlog file. You can control visibility of your messages in the Canzlog file by using the TAG keyword of the LOGTO stage.
- NOTECHO (global order)
- Turns off the echo flag (WQEMCSM) in the message that is logged or automated. NOTECHO does not affect the display.
- ONTO (global order)
- Sets the logical end of the line for input orders position.length and WORD to be a point other than the
last character in the line.
- /string/
- Indicates that the input orders consider the line to end after the given /string/. Previous SKIPTO or UPTO orders are respected. ONTO is similar to UPTO except that the target string is included in the new logical line.
- PAD (global order)
- Specifies the padding character to be used by subsequent orders.
Examples of orders which use the padding character include the LEFT
conversion order and the position output
order.
PAD must be followed by one-character value. This value can be specified as a delimited string, /char/, or as a hexstring.
The default PAD character is a blank.
- PARSE (global order)
- Specifies how the WORD input order counts words.
- C
- Indicates that all blank delimited tokens are counted as words.
- Q
- Indicates that tokens enclosed in single quotation marks are counted as words regardless of embedded blanks. The single quotation marks are removed from the parsed words. If the input data contains unbalanced quotation marks, only the data to the point where the error was discovered is returned.
- /string/
- Specifies how subsequent work/token orders counts words. The characters
in the specified string, and only those characters, are counted as
token delimiters. Note: A parse order always cancels the effect of any previous parse order.
For example, consider the following line:'PIPES ARE' 'REALLY' 'FUN'If PARSE Q is specified, this line contains 3 words:- PIPES ARE
- REALLY
- FUN
If PARSE C is specified, this line contains 4 words:- 'PIPES
- ARE'
- 'REALLY'
- 'FUN'
For the command revision table environment, the default PARSE value is/ ,=()/where the string consists of the following characters:
For all other environments, the default PARSE value is C.(space) , = ( ) - READLINE (global order)
- READLINE is used with multiline input messages. READLINE makes
the next line of the multiline message available to the input orders.
In the following example, you issue
MVS D A,Lin your pipeline and want to retrieve only the time data and number of TS users from the resulting output.The output fromMVS D A,Lis similar to the following output:IEE114I 11.44.14 96.141 ACTIVITY 444 JOBS M/S TS USER SYSAS INITS ACTIVE/MAX VTAM OAS 00000 00006 00001 00016 00002 00001/00300 00000The following edit script builds a line containing the time data contained in the first line and the number of TS users from the third line:WORD 2 1 READLINE READLINE WORD 3 NEXTWORDThe output from this edit script is
11.44.14 00001.If required, READLINE performs a RESET.
Executing READLINE more times that the number of lines in the input message is not an error. If READLINE attempts to retrieve lines beyond the end of the message, a null line is passed to the input order.
- RESET (global order)
- Cancels all previous SKIPTO and UPTO orders. The original input line is made available to input orders specified subsequent to RESET.
- RESETAUTO (global order)
- Sets the IFRAUHND, IFRAUMTB, and IFRAUNEX automation flags to zero ('0'B). Take care not to create automation loops when using this function.
- ROUTEZERO (global order)
- Overrides any previous specifications of route code for the message being revised.
- SETACTION (global order)
- Sets the IFRAUACN and IFRAUNVD automation flags. This causes the message to be held on an operator's screen unless a setting by the DEFAULTS or OVERRIDE command prevents it. See also the BULLETIN option of the PIPE ROUTE stage command in the NetView online help or in IBM Z® NetView Programming: Pipes.
- SETAUTO (global order)
- Sets the IFRAUMTB automation flag to one ('1'B). Subsequent routing of the message within a domain does not result in a submission to the automation table.
- SETBEEP (global order)
- Sets an audible alarm for message output. When the message output is displayed, the audible alarm is issued.
- SETCLEAR (global order)
- Sets the IFRAUCLR automation flag. This causes the NetView command facility screen to be erased just before presentation of the message containing this flag. Use with care to avoid losing important operator messages.
- SKIPTO (global order)
- Sets the logical start of the line for input orders position.length and WORD to be a point other than the
first character in the line.
- /string/
- Indicates that the input orders consider the line to start at
the given /string/. Previous SKIPTO or
UPTO orders are respected. For example, if the current line is:
PIPES ARE FUN. PIPES USING EDIT ARE EVEN BETTER!And, the edit script is:SKIPTO /FUN/ SKIPTO /PIPES/ WORD 6 NEXTThe line is processed as follows:- SKIPTO /FUN/ sets the starting point to the beginning of the word FUN.
- SKIPTO /PIPES/ sets the starting point to the beginning of the word PIPES.
- Retrieves the sixth word.
The line is processed as follows:
And, the output is:BETTER! - number
- Indicates that the input orders consider the line to start at
character number. Number must be a positive number. Previous SKIPTO or UPTO orders
are respected. For example, if the current line is:
PIPES ARE FUN. PIPES USING EDIT ARE EVEN BETTER!And, the edit script is:SKIPTO /USING/ SKIPTO 2 WORD 1 NEXTThe line is processed as follows:- SKIPTO /USING/ sets the starting point to the beginning of the word USING.
- SKIPTO 2 sets the starting point to the second letter of the word USING.
- WORD 1 selects the current word, beginning with the starting point set by the prior step.
The line is processed as follows:
And, the output is:SING
If the /string/ is not in the input, or a number is specified which is larger than the length of the input, none of the input is available to the input orders.
UPTO is a complementary function to SKIPTO. Where
SKIPTO 1returns the entire line,UPTO 1returns none of the line.See also UPTO and RESET.
- TOPLINE (global order)
- Cancels all previous READLINE orders and performs a RESET. Input
is set to the first line of the multiline message.
TOPLINE is a complementary function to LASTLINE. Where TOPLINE sets the input to the first line, LASTLINE sets the input to the last line of the multiline message.
See also LASTLINE.
See also HELP PIPE LASTLINE.
- UPTO (global order)
- Sets the logical end of the line for input orders position.length and WORD to be a point other than the
last character in the line.
- /string/
- Indicates that the input orders consider the line to end at the
given /string/. Previous SKIPTO or UPTO
orders are respected. For example, if the current line is:
PIPES ARE FUN. PIPES USING EDIT ARE EVEN BETTER!And, the edit script is:UPTO /FUN/ WORD -1 NEXTThe line is processed as follows:- UPTO /FUN/ sets the starting point to the beginning of the word FUN.
- WORD -1 selects the previous word, beginning with the starting point set by the prior step.
The line is processed as follows:
And, the output is:ARE - number
- Indicates that the input orders consider the line to end at character number. Number must
be an unsigned, positive number. Previous SKIPTO or UPTO orders are
respected. For example, if the current line is:
And, the edit script is:PIPES ARE FUN. PIPES USING EDIT ARE EVEN BETTER!UPTO 21 WORD -1 NEXTThe line is processed as follows:- UPTO 21 sets the starting point to the character N in the word USING.
- WORD -1 selects the previous word, beginning with the starting point set by the prior step.
The line is processed as follows:
And, the output is:PIPES
If the /string/ is not in the input, or a number is specified which is larger than the length of the input, all of the input is available to the input orders.
SKIPTO is a complementary function to UPTO. Where
SKIPTO 1returns the entire line,UPTO 1returns none of the line.See also SKIPTO and RESET.
- WRITELINE (global order)
- Is used to build a multiline message. WRITELINE causes
all text built so far by the output orders to be written to the output
message. All text subsequently built by the output orders is inserted
as a new line in the multiline message. Note: Output orders generate an implied WRITELINE at the end of the edit script unless WRITELINE is explicitly included. An implied WRITELINE remains in effect until an explicit WRITELINE or COPYREST is encountered.
Input Orders
- Literal text contained in the input order.
- Text received on the input data stream.
- Line attributes of the line received on the input data stream.
- Message attributes of the message received on the input data stream.
- AIFR (input order)
- Specifies that the input is the 256-byte AIFR body. For additional
information about the AIFR fields, see IBM Z NetView Programming:
Assembler.
Conversion orders, such as SUBSTR, can be used to obtain specific pieces of the AIFR.
Note: The position specified in SUBSTR must be the position described in IBM Z NetView Programming: Assembler plus one (1). - ALL
- Inputs the text in the current line. Same as 1.*.
- ASTYPE (input order)
- Indicates how the address space was started (job type):
- Value
- Description
- D
- USS persistent procedure.
The address space has a name for initiated programs, appropriate for a JOB. However, the existence of an OpenMVS address space block indicates a special purpose USS persistent procedure.
- E
- The address space is a system address space that is started during operating system initialization (NIP) processing, and the message was issued before NetView subsystem initialization.
- J
- The address space is a JOB.
- N
- The address space is a system address space started during operating system initialization (NIP) processing.
- S
- The address space is a Started Task (STC). Note: Because of the manner in which TN3270 is started, it may appear as type S rather than type D, as might be expected.
- T
- The address space is a Time-Sharing User (TSO).
- U
- The address space is a USS forked or spawned procedure.
- *
- Error: the address space where the command originated has closed or else the message is not from the local LPAR.
- ?
- Error: inconsistent data (might be a transient condition).
- !
- Error: inconsistent data.
- >
- Error: the supplied ASID is larger than the allowed ASID limit for the system
- AUTHISSUER (input order)
- Indicates the APF authorization of the routine that is issuing
the WTO, as indicated by WQEAUTH. AUTHISSUER produces a binary representation
of the value (X'00' or X'80'), which can be converted to a YES or
NO value using the YESNO conversion order.
- Value
- Description
- 00
- Issuer is not APF authorized.
- 80
- Issuer is APF authorized.
- CHKEY (input order)
- Obtains the CHKEY as defined by system macro IEECHAIN. This is the step-name of a task or the job-name of a job.
- CMDX (input order)
- Inputs the first 88 (X'58') bytes of the IEZVX101 control block.
- COLOR (input order)
- Inputs the characters describing the attributes of the current
line, including color, highlighting, line type, and intensity. See Output Orders for the description of
text values. This is an example:
CY HU IN TD - CONSAUTH (input order)
- Indicates the authority of the console issuing the command:
- Value
- Description
- M
- Master
- I
- I/O
- S
- System
- C
- Console
- X
- Information is not available, or conflicting data is found.
- CONSNAME (input order)
- Obtains the console name:
- For the CRT, returns the name of the console issuing the command.
- For the MRT, returns the destination console name.
- CURRGMT (input order)
- CURRGMT provides an 8-byte store clock value generated at the time the order is executed.
- CZID (input order)
- Obtains the Canzlog ID of a message or command echo or DOM that has been logged. It returns 0 if the message has not been logged.
- D4NV (input order)
- D4NV (destined for the NetView program) is used with a WHEN or REVISE statement. This input-only edit order indicates whether the console name to which a message is to be delivered is owned by a NetView task. You can reenable system logging for a particular message, if desired, by using the SYSLOG order.
- DELETE (input order)
- Determines whether a message has been marked for deletion.
If the message has been marked for deletion, the DELETE input order
supplies a non-null output; if the message has not been marked for
deletion, the output is a null character. This output can be used
as input to other decision-making orders such as the YESNO order.
The DELETE input order is only available for message revision.
- disposition (input order)
- When used as input orders, these orders provide information about
the disposition of the message. These edit orders produce a binary
representation of the value (X'00' or X'80'), which
can be converted to a
YesorNovalue using the YESNO conversion. The disposition orders are as follows:- AMRF
- Returns the following status: message is to be retained in AMRF
- AUTOMATE
- Indicates whether the message is to be automated.Note: Even if the value indicates that the message is not to be automated, a solicited message is still automated by the NetView program.
- BROADCAST
- Indicates that the message is to be sent to all active consoles
- DISPLAY
- Indicates that the message is to be displayed at the console.
- PROG
- Displays programming information
- SYSLOG
- Writes to the system log
- flag_bytes (input order)
- Used with routing and descriptor codes and represents an 8-bit section of the field. When used as an input order, it produces a string of 8 characters, consisting of 0s and 1s. These correspond to the bit values in the byte that is being referenced.
- FLGDSCDn (input order)
- Indicates that the specified descriptor code byte is to be read, where n is 1, 2, 3, or 4. The value of the byte is supplied as a string of eight EBCDIC values (either 0 or 1).
- FLGRTCDn (input order)
- Indicates that the specified route code byte is to be read, where n is 1 to 16. The value of the byte is supplied as a string of eight EBCDIC values (either 0 or 1).
- FLOODACT (input order)
- Indicates whether Message Flood Automation has acted upon the message.
- HDRMTYPE (input order)
- Indicates that the one-byte message type indicator is to be read in the message line that is being processed.
- IFRAUHND (input order)
- Use as input the automation action flag from the message. Bit value '1'B indicates the message matched a meaningful automation statement in the automation table. This is returned as the high-order bit in a 1-byte field.
- IFRAUIN3 (input order)
- Indicates that the 32 bits that are defined as IFRAUIN3 are used as input. For these 32 flags, see the DSIIFR assembler macro.
- IFRAUMTB (input order)
- Use as input the automation submission flag from the message. Bit value '0'B indicates the message has not been submitted for automation. This is returned as the high-order bit in a 1-byte field.
- IFRAUNEX (input order)
- Use as input the forbid exposure flag from the message. Bit value '1'B indicates the message cannot be automated, trapped, or logged This bit is set by output from CONSOLE ONLY and is returned as the high-order bit in a 1-byte field.
- LEVEL (input order)
- Specifies that the input is the data set read by a previous <
(from disk) stage containing the current line. The data set is indicated
by the concatenation level of the data definition. The level is returned
as a number preceded by a plus sign (+). For example, if the following data sets are concatenated in this order under the DSIPARM DDNAME:
And the current input line is contained inUSER.INIT USER2.INIT NMPTLS.INIT BNVE330E.PROCEED.DSIPARM NETV.E120E.PROCEED.DSIPARM NETV.E120E.PROCEED.CNMSAMPNMPTLS.INIT, the edit phrase input is+3.Note:- If the data set is in-storage as a result of the INSTORE pipe
stage, the LEVEL is
+0. - The EDIT stage containing LEVEL must be after a < (from disk) stage and cannot have a NETVIEW or COUNT stage between < (from disk) and EDIT. The NETVIEW and COUNT stages reset the concatenation values.
- If the data set is in-storage as a result of the INSTORE pipe
stage, the LEVEL is
- lineattr (input order)
- Specifies that the edit phrase input is one of the line attributes
of the current line processed by the edit phrase. Edit phrases operate
on one line at a time. The lineattr specifies
attributes of the current line being processed by the edit phrase.
The lineattr attribute can be one of the following values:
- LINECOUNT
- LINECOUNT gets the line count from the current line as set by
a previous COUNT EACHLINE, VET ROWS, or STEM (as a first stage). Any
other source for LINECOUNT yields unpredictable results. See PIPE COUNT, PIPE VET, and PIPE STEM and PIPE $STEM for more information. See the following examples for more information:
HELP PIPE,COUNT HELP PIPE,VET HELP PIPE,STEMLINECOUNT returns an EBCDIC number preceded by either a plus (+) or a minus (-) sign. This number is not padded unless the global order PAD /0/ is specified. If padded, LINECOUNT always returns a plus or minus sign followed by a 10-character number padded with leading zeros.
- LINEORIGIN
- Uses as input the value of the HDRDOMID field for the message
buffer being examined. The HDRDOMID field usually contains the domain
ID where the line originated, but it might contain some other value.
For example, when the From Disk (<) stage command is used, the
HDRDOMID field contains the member name read from disk. The value
can differ for different lines in the same message. For example, if
the COLLECT stage is used to build the message with source messages
from different domains, the message lines retain their origin domain
IDs.
LINEORIGIN returns 8 characters.
- LINETYPE
- Produces as input 2 characters indicating whether the current
line being processed is a control, label, data, or end line. The lines
returned are:
- TC
- The current line is a control line.
- TL
- The current line is a label line.
- TD
- The current line is a data line.
- TE
- The current line is an end line.
See also the LINETYPE output order.
- LINESENDER
- Specifies that the edit phrase input is the 8-character sender name of the current line.
For example, the output from the following specification:
might beLINETYPE NEXTWORD READLINE LINETYPE NEXTWORD
whereTC TDTCwas returned from the first line input andTDwas returned from the second line. - MCSFLAGS (input order)
- The 16-bit MVS™ multiple console
support flag. Check these bits:
- Bit
- Meaning
- 2
- The message is to be queued to the console if it is active
- 3
- The message is a command response WTO
- 5
- The message is a reply to a WTOR
- 6
- The message is to be broadcast to all active consoles
- 7
- The message is to be queued to hardcopy only
- 8
- The message is to be queued unconditionally to the console
- 9
- The message is not to be time-stamped
- 14
- The message is not to be queued to hardcopy
Length: 16 bits
Type: Message
- MRT (input order)
- Indicates that the message has been exposed to the Message Revision Table. If this flag is on when a message is output with a WTO command, then the message is not subject to further processing by the MRT unless overridden. See the NetView online help or the IBM Z NetView Command Reference Volume 2 (O-Z) for information about the WTO command.
- msgattr (input order)
- Specifies that the edit phrase input is one of the message attributes
of the data received on the input data stream. For additional information
on the attributes named, or with synonyms, beginning "IFRAU", see
the assembler mapping of DSIIFR and the IBM Z NetView Automation
Guide. msgattr can be one of the following specifications:
- ASID
- Use as input the 2 hexadecimal character Address Space ID of the MVS originator of the message. If
the message was not received from MVS, X'0000' is returned.
Use the C2X conversion order to view or print this field.
ASID is synonymous with IFRAUWAS.
- AUTHGRP
- Specifies the ACEE group ID (ACEEGRPN), if available. If it is
not available, returns *UNKNWN*.
The values that are supplied for AUTHUSER and AUTHGROUP input orders are derived from the ACEE that is active at the time the message is routed through the z/OS subsystem interface. Certain authorized programs issue messages in an environment that causes them to be routed asynchronously through the CONSOLE address space. These messages show
"+CONSOLE"as the AUTHUSER value and a single asterisk (*) as the AUTHGROUP value. Messages that are issued from the master scheduler show"+MASTER+"for the AUTHUSER value, instead. Only authorized programs can issue messages in this way. - AUTHUSER
- Specifies the z/OS ACEE
user ID (ACEEUSRI), if available. If it is not available, returns
*UNKNWN*.
The values that are supplied for AUTHUSER and AUTHGROUP input orders are derived from the ACEE that is active at the time the message is routed through the z/OS subsystem interface. Certain authorized programs issue messages in an environment that causes them to be routed asynchronously through the CONSOLE address space. These messages show
"+CONSOLE"as the AUTHUSER value and a single asterisk (*) as the AUTHGROUP value. Messages that are issued from the master scheduler show"+MASTER+"for the AUTHUSER value, instead. Only authorized programs can issue messages in this way. - AUTOTOKEN
- Use as input the 8-character MPF automation token.
AUTOTOKEN is synonymous with IFRAUTOK.
- DESC
- Use as input the 2-byte MVS Descriptor Code set by the originator of the message. If the message
was not received from MVS, binary
zeros are returned.
Use the C2B conversion order to view or print this field.
DESC is synonymous with IFRAUWDS.
- IFRAUTOK
- See AUTOTOKEN.
- IFRAUGMT
- Use as input the store clock value (STCK) at the time the message
was created or received by the NetView program.
Use the OPDT or C2X conversion orders to view or print this field.
- IFRAUCON
- See SYSCONID.
- IFRAUCPY
- Use as input the copy flag from the message. This is returned as the high-order bit in a 1-byte field.
- IFRAUIN3
- Indicates that the 32 bits that are defined as IFRAUIN3 are used as input. For these 32 flags, see the DSIIFR assembler macro.
- IFRAUPRI
- Use as input the primary receiver flag from the message. This is returned as the high-order bit in a 1-byte field.
- IFRAUPPT
- Use as input the PPT origin flag from the message. This is returned as the high-order bit in a 1-byte field.
- IFRAUSDR
- Use as input the Task ID of the originator of the message.
- IFRAUSEC
- Use as input the secondary receiver flag from the message. This is returned as the high-order bit in a 1-byte field.
- IFRAUWAS
- See ASID.
- IFRAUWDS
- See DESC.
- IFRAUWJA
- See JOBNAME.
- IFRAUWJU
- See JOBNUM.
- IFRAUWRT
- See ROUTECODES.
- JOBNAME
- Use as input the 8-character JES job name of the originator of
the message. JOBNAME is 8 null characters if the message was not
received from MVS.
JOBNAME is synonymous with IFRAUWJA.
- JOBNUM
- Use as input the 8-character JES job number of the originator
of the message. JOBNUM is 8 null characters if the message was not
received from MVS.
JOBNUM is synonymous with IFRAUWJU.
- MSGCOUNT
- Use as input the results from a prior stage that sets the count value, which includes only the
COUNT EACHMSG and the DELDUPES COUNT stages. Only use MSGCOUNT if a stage preceding EDIT is one of
these stages. Any other source for MSGCOUNT yields unpredictable results. See HELP PIPE,COUNT or HELP PIPE,DELDUPES for more information.
MSGCOUNT returns an EBCDIC number preceded by either a plus (+) or a minus (-) sign. This number is not padded unless the global order PAD /0/ is specified. If padded, MSGCOUNT always returns a + or - sign followed by a 10-character number padded with leading zeros.
- MSGID
- The message identifier of the received message. MSGID is a character ID of up to 12 characters. The message identifier is usually the first token of the message. If a REPLYID is sent with the message, the REPLYID is not used as the first token.
- MSGORIGIN
- Use as input the 8-character domain ID where the message originated.
- MSGSENDR
- Indicates that the edit phrase input is the 8-character name (OPID) of the task that created the message or, if the message was routed between tasks, that most recently sent the message.
- MSUSEG
- Indicates the contents of one segment of an MSU. The compare items
can be a bit string or a parse template. Use any of these choices to specify the location of the data to be compared:
- H
- For an MDS-MU, indicates that the first key is to be obtained at the MDS-MU level, rather than the major-vector level. If you use this parameter and the MSU being processed is not an MDS-MU, MSUSEG returns a value of null.
- key
- The 2- or 4-character representation of the 1- or 2-byte hexadecimal
ID of the generalized data stream (GDS) variable or key of the major
vector, subvector, subfield, or sub-subfield.
You can specify multiple key values, separating them with periods. Each additional key specifies a lower-level structure within the structure identified by the preceding key.
- occurnum
- The occurrence number, counting from 1, of the generalized data stream (GDS) variable, major vector, subvector, subfield, or sub-subfield. An asterisk (*) indicates that you want any occurrence. For example, used at the subvector level, an occurnum value of 2 means that you want the second instance of the key subvector. An occurnum value of * means that you want the first subvector with a key of key, if any, that results in equality with the compare item that you specified. The maximum occurnum value is 32 767. The default value is 1.
- MSGSENDR (input order)
- Indicates that the edit phrase input is the 8-character name (OPID) of the task that created the message or, if the message was routed between tasks, that most recently sent the message.
- NVABLE (input order)
- Returns "Yes" if a NETVONLY action can succeed, otherwise returns
"No".
A NETVONLY action cannot succeed if the NetView procedural space is down, the subsystem router is down, or if the task defined by the ?MVSCmdRevision CNMSTYLE statement is inactive.
- REPLYL (input order)
- Returns the length of the reply ID in decimal format, with a leading plus sign (+).
- ROUTECODES (input order)
- Use as input the 16-character MVS route code data. If the message was not received from MVS, binary zeros are returned.
Use the C2B conversion order to view or print this field.
ROUTECODES is synonymous with IFRAUWRT.
- SESSID (input order)
- Specifies that the edit phrase input is the TAF session ID or, following a PPI pipe receive stage, is the SAF ID of the PPI sender.
- SYSCONID (input order)
- Use as input the 8-character MVS System Console name. If the message was not received from MVS, blanks are returned.
SYSCONID is synonymous with IFRAUCON.
- SYSNAME (input order)
- Use as input the 8-character name of the system from which the message originated. If the message was issued locally, the name of the local system is returned. If the message is a remote message (one which originated on another system in a sysplex), the name returned is the remote system name, which is different from the local system name. You can compare the value returned with the &SYSNAME. system symbolic to determine whether the message is local or remote.
- UCHARS (input order)
- Obtains the 16-byte "user char" area. In the MRT, this field is available only if previously set. In PIPE EDIT, this field is equivalent to IFRAUSRC.
- UFLAGS (input order)
- Obtains the 2-byte "user flags" area. In the MRT, this field is available only if previously set.
- WORD (input order)
- WORD is similar to position.length in
that it specifies that a subset of the data received on the input
data stream is used as input to EDIT. Unlike position.length, WORD counts blank delimited tokens or words within the
input data. A word ends when a blank is encountered. The next word
begins with the next nonblank character.
Startword.numwords must be specified.
Startword indicates the starting word within the current line. By default, startword is counted from the first word of the line.
Startword can be a positive or negative number. A negative value for startword indicates that the starting position is to be counted from the end of the current line, rather than from the beginning.
Numwords is an unsigned, positive number indicating the number of words from startword to be processed. An asterisk (*) can be specified for numwords indicating that all words after startword are to be used. Startword without numwords and the period (.) separator defaults numwords to 1.
If numwords is larger than the available words, all available words are used. The LEFT conversion order can be used to pad the resulting text if required.
Note: The PARSE global order can affect the way words are defined.Consider the following message:PIPES CAN BE FUN!- This ...
- Results in ...
- WORD 1.*
PIPES CAN BE FUN!- WORD 2.2
CAN BE- WORD -2.*
BE FUN!- WORD 2.3
CAN BE FUN!- WORD 2
CAN- WORD -25.5
- a null string is returned
- WORD -6.3
- PIPES
- WQE (input order)
- Enables the WQE for conversion. Always use the SUBSTR order following
WQE and determine the positions needed by consulting mapping IHAWQE.
The SUBSTR order uses a position.length (starting
with one) and not an offset (starting with zero). The maximum allowable
character string length for revision orders is 127.
For example, the WQEMCSC command response flag is not typically accessible with an edit order. From a listing, we can determine that WQEMCSC is at offset X'AC' (decimal 172) in the WQE and it is the third bit in that byte. Therefore, the edit phrase
WQE SUBSTR 173.1 c2b substr 3.1yields either a character 1 or a character 0, according to the value of the WQEMCSC flag. - WTOKEY (input order)
- Obtains the key field associated with the WTO system macro, which is the WQEKEY in system macro IHAWQE.
Conversion Orders
Conversion orders, if specified, must be in an edit phrase. That is, they must come after an input order and before an output order.
- ASTYPE (conversion order)
- Specifies that the input contains a two-byte binary ASID value.
A one-character value is returned as indicated in Table 6.
Table 6. Returned Value from ASTYPE Value Description D USS persistent procedure. The address space has a name for initiated programs, appropriate for a JOB. However, the existence of an OpenMVS address space block indicates a special purpose USS persistent procedure.
E The address space is a system address space that is started during operating system initialization (NIP) processing, and the message was issued before NetView subsystem initialization. J The address space is a JOB. N The address space is a system address space started during operating system initialization (NIP) processing. S The address space is a Started Task (STC). T The address space is a Time-Sharing User (TSO). U The address space is a USS forked or spawned procedure. > Error: the supplied ASID is larger than the allowed ASID limit for the system * Error: the supplied ASID is not currently assigned (no such address space). ? Error: inconsistent data (might be a transient condition). ! Error: inconsistent data. - B2C (conversion order)
- Specifies that the input data contains a text string. The text
string is converted into its equivalent, internal, binary representation.
For example, if the input is 1100000111000010 B2C returns AB.
The input data must be in exact multiples of eight characters. The converted data is one-eighth the length of the original.
B2C is the inverse of C2B.
- C2B (conversion order)
- Specifies that the input data is treated as a string of Boolean
values. The input data is converted to a text string representing
the individual bits. For example, if the input is AB, C2B returns
1100000111000010.
C2B is especially useful in converting bit string data such as that returned from DESC (IFRAUWDS) to a readable form.
Because C2B returns a character string 8 times longer than the original, you can easily generate a message which exceeds the 32 000 character limit for NetView messages. Use C2B to convert only the substring requiring conversion. For more information, see the conversion order for SUBSTR.
C2B is the inverse of B2C.
- C2D (conversion order)
- Specifies that the input data is treated as a 2's complement binary
number. This input data is then converted into a positive or a negative
decimal number. For example, if the input is 1, C2D returns a result
of -15. If the input is AB, C2D returns a result of -15934, as shown
in the following example:
PIPE LIT /AB/ | EDIT 1.* C2D | CONS ONLYIf the input is hexadecimal data and this data must be interpreted as a positive number, use PAD as the global order. The following example returns a result of 49602:PIPE LIT /AB/ | EDIT PAD '00'X 1.* RIGHT 3 C2D | CONS ONLYUse C2D with an input of 4 characters or less. The results of C2D are unpredictable with an input of more than 4 characters. Use C2D to convert only the substring requiring conversion.
C2D is the inverse of D2C.
- C2F (conversion order)
- Specifies that the input data is converted to a displayable
floating point notation. The input can be a 2- to 8-byte floating
point number. The converted value is a 22-byte, right-aligned, output
string in the form
-n.mmmmmE-ddwhere the exponentE-ddand the decimal point are only included if the converted number requires. When the exponentE-ddis not produced, the output is equivalent to packed decimal.A maximum of 17 decimal digits are used in the conversion with leading and trailing zeros stripped. An 18th digit is calculated and used to round the results. For example, the repeating decimal number 1.9999999... is converted to 2.
See also the conversion order for F2C and the conversion order for C2S.
- C2G (conversion order)
- Converts fixed-length strings to double-byte (DBCS) character
strings by adding a shift-out character in front of the string and
a shift-in after the string.
C2G is the inverse of G2C.
This conversion order is particularly useful when dealing with data interacting with the SQL pipe stage.
- C2GV or C2VG (conversion order)
- Converts varying-length strings to double-byte (DBCS) character
strings by adding a shift-out character in front of the string and
a shift-in after the string.
The input string must start with a 2-byte length field containing the number of DBCS characters. The number of data bytes after the length field must be twice the value of the length field because each DBCS character is represented by two bytes of data. The length field is not copied to the converted string.
C2GV is the inverse of GV2C.
This conversion order is particularly useful when dealing with data interacting with the SQL pipe stage.
- C2P (conversion order)
- Specifies that the input data is converted to displayable floating
point notation of a specified precision. Scale indicates the number of decimal digits retained.
- If scale is 0 (zero), the resulting number is an integer. For example,
C2P 0converts the input X'123C' to 123. - If scale is positive, the resulting
number has scale number digits after the
decimal point. For example,
C2P 2converts the input X'123C' to 123.45. - If scale is negative, the resulting
number has scale zeros added to the number.
For example,
C2P -1converts the input X'123C' to 120.
C2P is the inverse of P2C.
- If scale is 0 (zero), the resulting number is an integer. For example,
- C2S (conversion order)
- Specifies that the input data is converted to a displayable
floating point notation. The input can be a 2- to 8-byte floating
point number. The converted value is a 14-byte, right-aligned, output
string in the form
-n.mmmmmE-ddwhere the exponentE-ddand the decimal point are included only if required by the converted number. When the exponentE-ddis not produced, the output is equivalent to packed decimal.A maximum of 17 decimal digits are used in the conversion with leading and trailing zeros stripped. An 18th digit is calculated and used to round the results. For example, the repeating decimal number 1.9999999... is converted to 2.
See also the conversion order for F2C and the conversion order for C2F.
- C2V (conversion order)
- Specifies that the input data is a variable length string to be
converted to a displayable string. The input data starts with a 2-byte,
unsigned length value indicating the length of the string.
C2V is the inverse of V2C.
This conversion order is particularly useful when dealing with data interacting with the SQL pipe stage.
- C2X (conversion order)
- Specifies that the input data is converted to hexadecimal notation.
For example, if the input is AB, C2X returns the EBCDIC hexadecimal
value X'C1C2'. C2X is particularly useful when you must
display input data containing nondisplayable characters.
C2X is the inverse of X2C.
- CHKEY
- Obtains the CHKEY as defined by system macro IEECHAIN. This is the step-name of a task or the job-name of a job.
- CNVDT (conversion order)
- Specifies that the input data is a date or time value and is changed
to another date or time format. CNVDT must be followed by a parenthetical
expression containing two entries. Each of these entries specifies
a date or time format. The first entry is the format of the input
data and the second is the format of the converted output. Each entry can be the keyword DATE, the keyword TIME, or a string 4 - 8 characters in length. Specifying one entry for date and another for time is not supported.
- DATE
- Indicates the format is the date format specified by the DEFAULTS or OVERRIDE command.
- TIME
- Indicates the format is the time format specified by the DEFAULTS or OVERRIDE command.
- from template or to template
- Indicates that the conversion format is provided.
If a template is supplied, it must conform to the conditions specified for the date or time templates used with the DEFAULTS or OVERRIDE command. When using a template, both entries within the parenthetical expression must be for dates or times.
The input data is searched from the beginning of the data for a date format. For time conversion the input is searched from the end.
- CNVDT0 (conversion order)
- Specifies that the same conversion is done as for CNVDT. However, if the input data does not match the specified input format, no data is passed to the output.
- D2C (conversion order)
- Specifies that the input character string representing a signed
or unsigned decimal number is to be converted to a 4-byte signed binary
number. Use the
RIGHT 2conversion order to reduce the output to 2 bytes. For example, if the input was 49602, D2C returns AB.Use D2C with an input resulting in 4 characters or less. The results of D2C are unpredictable with an input resulting in more than 4 characters. Use D2C to convert only the substring requiring conversion. For more information, see the conversion order for SUBSTR. See HELP PIPE SUBSTR for more information.
D2C is the inverse of C2D.
- D2X (conversion order)
- Specifies that a decimal number is to be converted to hexadecimal representation.
- DT (conversion order)
- Specifies that the input data is a store clock (STCK) value, such
as that obtained from the IFRAUGMT input order, and is to be converted
to a 17-character date/time value. The data and time are for the
local time zone and are in the converted to the form:
MM/DD/YY HH:MM:SS.To convert to Greenwich Mean Time, use ZDT.
Note: The current GMT offset is used in interpreting the local date and time, whether a different offset was in effect at the given date and time. For example, if the given value was before the latest daylight saving time adjustment, the result can be off one hour from another interpretation of the same date and time of an application. - DTS (conversion order)
- Specifies that the input data is a 17-character local date/time
value in the form
MM/DD/YY HH:MM:SS, and is to be converted to a store clock (STCK) value which is based on Greenwich Mean Time.Note: The current GMT offset is used in interpreting the local date and time, whether a different offset was in effect at the given date and time. For example, if the given value was before the latest daylight saving time adjustment, the result can be off one hour from another interpretation of the same date and time of an application. - ETIME (conversion order)
- Specifies that the input data is a store clock (STCK) value and is to be converted to a decimal number representing the elapsed time in microseconds since NetView startup. The result is a decimal number that can be longer than 10 digits. The result can also be a negative number indicating that the message originated before NetView startup.
- FOUND (conversion order)
- FOUND is used after a SKIPTO or FINDLINE operation to translate
a null string into
Noand any other string intoYes. The case of the character string is exactly as displayed,NoorYes. - F2C (conversion order)
- Specifies that the input character data represents
a signed or unsigned floating point number and is to be converted
to an 8-byte internal floating point representation. You can use the
LEFT 4conversion order to reduce the output to a short floating point internal number if desired.F2C is the inverse of C2F.
- G2C (conversion order)
- Converts double-byte (DBCS) character strings to fixed-length
strings by removing the shift-out character in front of the string
and the shift-in after the string.
G2C is the inverse of C2G.
This conversion order is particularly useful when dealing with data interacting with the SQL pipe stage.
- GV2C or VG2C (conversion order)
- Converts double-byte (DBCS) character strings to varying-length
strings by removing the shift-out character in front of the string
and the shift-in after the string. A 2-byte, unsigned length value
precedes the converted string.
GV2C is the inverse of C2GV.
This conversion order is particularly useful when dealing with data interacting with the SQL pipe stage.
- JOBNAME (conversion order)
- Specifies that the input contains a 2-byte binary ASID value. The corresponding job name is returned. If an error occurs, one of the four error tokens (>,*,?, or !) in Table 6 might be returned.
- LEFT (conversion order)
- Specifies that the input data is to be truncated or padded to the length specified by number. Characters are counted from the beginning, or left, of the input. If padding is required, the character specified on the most recent PAD global order is used.
- NOT (conversion order)
-
- Converts a positive indicator into a negative.
- Converts a negative indicator into a positive.
- ODDBYTES (conversion order)
- Specifies that the input text be alternately kept and discarded.
The format of ODDBYTES is ODDBYTES keep.discard.
- keep
- is an unsigned, positive number specifying the number of characters to keep.
- discard
- is an unsigned, positive number specifying the number of characters to discard.
For example, if the input is 13:15:45 and ODDBYTES 2.1 is specified, 131545 is returned. That is, two characters were kept and one was discarded. Then, another two characters were kept, and one was discarded. And so on.
- OPDT (conversion order)
- Specifies that input text is to be treated as a store clock (STCK)
value. OPDT converts the input into a 17-character string representing
the date and time in readable form. The converted form is the one
specified by DEFAULTS or OVERRIDE date and time formats for the system
and operator where the conversion is done.
For example, after the command OVERRIDE LONGDATE=YY.MM.DD, the value
X'CADA6B86F34C3820'is converted to13.01.31 10:28:11.A typical use is to take the input provided by the IFRAUGMT msgattr input order and convert it to readable form.
Note: The data representing a store clock is 8 characters in length. If the input data provided OPDT is not 8 characters, results are unpredictable. - P2C (conversion order)
- Specifies that the input data is a character string representing
a signed or unsigned floating point number. The input is converted
to an internal packed decimal representation with scale decimal digits precision.
- If scale is 0, the integer portion of the number is converted to packed decimal.
For example,
C2P 0converts the input 123.456 to X'123C' which is the packed decimal number representing 123. - If scale is positive, the resulting
number has scale number digits included
in the packed decimal. For example,
C2P 2converts the input 123.456 to X'12345C' which is the packed decimal representing 12345. - If scale is negative, the resulting
number has scale number of digits removed
from the integer portion of the packed decimal. The decimal portion
is ignored. For example,
C2P -1converts the input 123.456 to X'012C' which is the packed decimal number representing 12.
C2P is the inverse of P2C.
- If scale is 0, the integer portion of the number is converted to packed decimal.
For example,
- PREFIX (conversion order)
- Adds a constant to the beginning of a string.
- RIGHT (conversion order)
- Specifies that the input data is to be truncated or padded to the length specified by number. Characters are counted from the end, or right, of the input. If padding is required, the character specified on the most recent PAD global order is used.
- RVAR (conversion order)
- From input revision variable name, returns the current value.
- SQUEEZE (conversion order)
- Specifies that delimiter characters at the start, at the end, and within the data are to be
removed. The delimiter characters are defined by the most recent PARSE global order
specification.Note: If SQUEEZE is specified with PARSE Q in effect, it is ignored.
- STRIP (conversion order)
- Specifies that padding characters at the start or end of the data are to be removed. The padding character is defined by the most recent PAD global order specification within the edit phrase.
- STRIPL (conversion order)
- Specifies that padding characters at the beginning of the data are to be removed. The padding character is defined by the most recent PAD global order specification within the edit phrase.
- STRIPR (conversion order)
- Specifies that any padding characters at the end of the data are to be removed. The padding character is defined by the most recent PAD global order specification within the edit phrase.
- SUBSTR (conversion order)
- Specifies that a subset of the input data is to be selected.
Position.length indicates the starting position and length of data to be
selected. For information about defining
position.length, see position.length.
For information on defining position.length, see
the description of the position.length common operand.
If padding is required for the data to be the required length, the characters specified by the most recent PAD global order is used.
- UPCASE (conversion order)
- UPCASE translates the standard 26-character Latin letters (as defined in code page 037) to uppercase.
- V2C (conversion order)
- Specifies that the input data is a displayable string and is to
be converted to a variable length string prefixed with a 2-byte, unsigned
length value.
V2C is the inverse of C2V.
This conversion order is particularly useful when dealing with data interacting with the SQL pipe stage.
- X2C (conversion order)
- Specifies that the input data is converted from displayable hexadecimal
notation to internal binary representation. For example, if the input
is X'C1C2', C2X returns the hexadecimal values X'AB'. The resulting hexadecimal value is half the length of the original.
X2C is the inverse of C2X.
- YESNO (conversion order)
- Specifies that the first byte of the input data is converted from
a bit string to a value of
YesorNo. If any bit in the first byte is a one (1),Yesis returned. If all bits in the first byte are zero (0),Nois returned. The case of the character string is exactly as displayed,YesorNo.This conversion order is particularly useful when using the IFRAUCPY, IFRAUPPT, IFRAUPRI, and IFRAUSEC msgattr input orders.
- ZDT (conversion order)
- Specifies that the input data is a store clock (STCK) value, such
as that obtained from the IFRAUGMT input order, and is to be converted
to a 17-character date/time value. The date and time are for Greenwich
Mean Time and are in the converted form:
MM/DD/YY HH:MM:SS.To convert to local time, use DT.
Output Orders
- ACTIONFLAG (output order)
- ACTIONFLAG sets the one-character message prefix which appears on a z/OS console immediately prior to the message text. The input to the ACTIONFLAG order specifies whether the routine that issued the WTO should be considered to be APF authorized or not. The values of descriptor code bits 1, 2 and 11, at the point where the ACTIONFLAG order appears in the edit script, identify whether the message is an action message or not. The character that is set is determined as follows:
- When descriptor code bits 1, 2 and 11 are all zero (not an action message), a blank space is set.
- When the input is null, the letter N or the number 0 (designating that the issuing routine is not APF authorized), and any of the descriptor bits 1, 2 or 11 is one (designating an action message), an at character (@) is set.
- When the input is a non-null value other than the letter N or the number 0 (designating that the issuing routine is APF authorized), and any of descriptor bits 1, 2 or 11 is one (designating an action message) an asterisk character (*) is set.
- According to MVS convention, action messages that are issued by APF authorized programs are prefixed with an asterisk character (*). MVS action messages that are issued by programs that are not APF authorized are prefixed with an at character (@). For a description of MVS message prefix characters, refer to the "Messages sent to MCS/SMCS consoles" section in the MVS System Messages documentation.
- The AUTHISSUER and ACTIONFLAG orders can be used together to set the prefix character according to MVS convention.
- AUTOTOKEN (output order)
- Sets the 8-character automation token in the message.
AUTOTOKEN is synonymous with IFRAUTOK.
- COLOR (output order)
- Specifies the presentation attributes of the resulting output
line including color, highlighting, line type, and intensity. Multiple
attributes must be enclosed in delimiters. Unknown attributes are
ignored. Valid attributes are:
- Color
-
- CB
- Blue
- CR
- Red
- CP
- Pink
- CY
- Yellow
- CG
- Green
- CW
- White
- CT
- Turquoise
- CD
- Default
- Intensity
-
- IN
- Not intensified
- IH
- Intensified
- ID
- Output line is dark. Although the output line exists, it is not displayed.
- Highlighting
-
- HR
- Reverse video
- HU
- Underlined
- HB
- Blinking
- HD
- Default
- Line Type
-
- TC
- Control line
- TL
- Label line
- TD
- Data line
- TE
- End line
For example, if you want to create a blue, flashing data line of normal intensity, specify:/CB IN HB TD/ COLORCOLOUR, LINEATTR, and LINEATTRS are synonyms for COLOR.
- CONSNAME (output order)
- Sets the console name.
- DELETE (output order)
- Deletes a message or command, or undeletes a previously deleted
message or command, depending on the input:
- If the input is null, the letter
N, or the number 0, the DELETE output order undoes a previous deletion. - If the input is
a non-null value other than the letter
Nor the number 0, the DELETE output order deletes the message or command. Marking a message for deletion does not prevent the message from being automated.
The DELETE output order is available only when performing a REVISE action.
- If the input is null, the letter
- disposition (output order)
- When used as output orders, these orders control or change the
disposition, subject to certain system constraints. These edit orders
write null strings and the 0, n, and N strings to the WQE as a 0.
Any other string writes a 1 to the WQE indicating the function is
enabled. Following are the disposition orders, and
the resulting action when the input value indicates a true condition
(anything other than a null, 0, n or N):
- AMRF
- Retains the message in AMRF
- AUTOMATE
- Sets a flag that indicates whether
automation is to be performed on the message.Notes:
- Setting AUTOMATE to an affirmative value, such as Y, causes a foreign unsolicited message to be automated.
- The AUTOMATE order has no effect on solicited messages by the NetView program.
- BROADCAST
- Sets an indicator that causes the operating system to send messages to all active consoles.
- DISPLAY
- Sets an indicator that the message is displayable at the console.
Note: If a command response message (descriptor code 5 being the standard method for marking a message as a command response) is marked for suppression (e.g. by using 'N' DISPLAY in a Message Revision Table), it is still returned to a pipe (even when WINDOW is used) that correlates an MVS command response. To prevent a message correlated to a pipe from also being returned to the pipe, use 'Y' DELETE.
- PROG
- Displays programming information
- SYSLOG
- Writes to the system log
- FINDLINE (output order)
- Functions the same as global order FINDLINE n except that the target to be found is derived from the previous input order or conversion order. If the number is negative, EDIT counts from the end of the message.
- flag_bytes (output order)
- Used with routing and descriptor codes and represents an 8-bit
section of the field. When used as an output order, it requires a
string of 8 characters, consisting of 0s, 1s, and Xs. These correspond
to the requirement to clear, set, or leave as-is the corresponding
bit in the byte that is being referenced.The following example indicates that the message is to be sent to route codes 1 and 2 but not to route code 5, and that the other route codes are to be left as is:
REVISE('11xx0xxx' FLGRTCD1) ! Send to rt cd 1 and 2, not 5, leave others as is. - FLGDSCDn (output order)
- Indicates that the specified descriptor code byte is
to be written, where n is 1, 2, 3, or 4. The value
of the byte is changed according to the input mask. The input mask
must be a string of eight EBCDIC values (0, 1, or x). Each descriptor code
flag bit that corresponds to a 0 is turned
off; each descriptor code flag bit that corresponds to a 1 is turned on; and the other bits are left as is.Usage Notes:
- CAUTION: MVS uses predefined conventions for message descriptor bits. Modifying various bits can produce results that are incomplete or not valid. For details, refer to the "Descriptor Codes" section in any of the MVS System Messages documentation. Neither the NetView program nor MVS validate the result of changes made to revised descriptor flags.
- The ACTIONFLAG global order can be used when descriptor code bits 1, 2 or 11 are changed to add or remove the appropriate action flag character. For a description of the action message flag characters, refer to the "Messages sent to MCS/SMCS consoles" section in any of the MVS System Messages documentation.
- To conform to MVS conventions when changing the status of a message (action or non-action), consider factors such as whether the message should be deleted when the issuing task terminates (descriptor bit 7); whether the task issuing the message is APF authorized or not (which is determined by the AUTHISSUER input order); if the first character of the message text is required to be a plus sign "+"; and any additional considerations.
- FLGRTCDn (output order)
- Indicates that the specified route code byte is to be written, where n is 1 to 16. The value of the byte is changed according to the input mask. The input mask must be a string of eight EBCDIC values (0, 1, or x). Each route code flag bit that corresponds to a 0 is turned off; each route code flag bit that corresponds to a 1 is turned on; and the other bits are left as is.
- HDRMTYPE (output order)
- Indicates that the one-byte message type indicator is to be written in the message line that is being processed.
- LINETYPE (output order)
- Specifies the line type attribute of the resulting output line.
The LINETYPE value is received from its input and must be one of the
following values:
- TC
- Output line is to be a control line.
- TL
- Output line is to be a label line.
- TD
- Output line is to be a data line.
- TE
- Output line is to be an end line.
LINETYPE is not case-sensitive.
If the input to LINETYPE is not one of these four values, or if LINETYPE is not specified, the current line type attribute is retained.
- MRT (output order)
- Indicates that the message has been exposed to the Message Revision Table.
- NEXT (output order)
- Specifies that the input to NEXT is to be inserted, without an intervening blank, into the output line after any text already in the output line.
- NEXTWORD (output order)
- Specifies that the input to NEXTWORD is to be inserted into the output line. If the output line already contains text, one blank is inserted into the output line prior to the data.
- position (output order)
- Specifies that the data be placed in the output line beginning at the character indicated by
position. If position is larger than the current
length of the output line, the existing output line is padded with the character defined by the PAD
global order and the data added after the padding characters. If the output line created is already
longer than position, the existing text beginning at
position is overlaid. Position can be a negative number. In this case, the
new text is inserted at a point found by counting backwards from the end of the existing output
text.For example consider the following message on the input stream to EDIT:
CAN BE FUN WITH EDIT!With the following edit script:/PIPES/ 1 1.* 7PIPESis written to the output stream beginning at position 1. Then, the entire input stream is read using1.*and written to the output stream beginning in position 7. The resulting output data is:PIPES CAN BE FUN WITH EDIT!ConsiderCAN BE FUN WITH EDIT!as the input stream to the following edit script:PAD /*/ 1.* 5In this case the entire input stream is written to the output stream beginning at position 5. The first four positions are padded with asterisks (*) which was defined as the pad character. The resulting output data is:****CAN BE FUN WITH EDIT!Now consider the following edit script which receivesCAN BE FUN WITH EDIT!on the input stream:/MANIPULATING MESSAGES IS HARD/ 1 1.* 23FirstMANIPULATING MESSAGES IS HARDis written to the output. Then, all the data received on the input stream is read by the input order 1.* and written to the output at position 23. BecauseMANIPULATING MESSAGES IS HARDis longer than 23 characters, the data read and the resulting output by1.* 23overlays the existing output data resulting in the following text on the output stream:MANIPULATING MESSAGES CAN BE FUN WITH EDIT! - SETGMT (output order)
- SETGMT sets the IFRAUGMT value of the output message. The order is carried out only if the input available is exactly eight bytes. You can use this order with the CURRGMT order if you want to reinsert a message into the Canzlog log.
- UCHARS (output order)
- Sets a 16-byte "user char" area. In PIPE EDIT, UCHARS is equivalent to the previously-existing IFRAUSRC, except that UCHARS accepts a value shorter than 16 characters (no padding occurs) or truncates a value longer than 16 characters.
- UFLAGS (output order)
- Sets a 2-byte "user flags" area. In the MRT, this field accepts a string of up to 16 characters consisting of 0s, 1s, and Xs. These correspond to the requirement to clear, set, or leave as-is the corresponding bit in the byte being referenced. In PIPE EDIT, UFLAGS is equivalent to the previously-existing IFRAUSRB, except that UFLAGS accepts a value shorter than 2 characters (no padding occurs) or truncates a value longer than 2 characters.
- WTOKEY
- For the Message Revision Table (MRT), WTOKEY sets the key field associated with the WTO system macro, which is the WQEKEY in system macro IHAWQE.
Example: Selecting a Word
WORD 5
NEXTIf the input line processed by this script
is DSI001I MESSAGE SENT TO NETOP2, NETOP2 is placed in the output line. If the output line currently contains
text, NETOP2 is added without an intervening blank.
Example: Creating a Command
TYPE: OST TASKID: RESOURCE: A01A441 STATUS: NOT ACTIVE/START TASK=/ 1
WORD 5
NEXT/START TASK=/ is an input
order. A single number can be either an input or output order. Because /START TASK=/ is the input order, the number 1 following /START TASK=/ must be an output order. So, START TASK=
is written to the first position of the output line.
WORD 5 is also an input order. WORD requires a value, which
in this case is 5. Because no global orders were specified for PARSE,
parsing is done on blank delimited words. In the example line, the
fifth blank delimited word, A01A441, is selected. The NEXT output order causes the selected word to be placed in the output
line without an intervening blank.
START TASK=A01A441If a NETVIEW stage follows the EDIT stage, this output is invoked as a command.
Example: Sending an Alert to the NetView Alert Adapter
/* construct a value from MYVAR and a unique identifier */
/* (GMT value set when alert received). Note: convert GMT to */
/* displayable chars */
'PIPE (NAME TECBIND)',
'| SAFE *', /* copy complete automation alert into pipeline */
'| EDIT', /* begin edit */
'COPY *', /* copy complete automation alert to EDIT output*/
'/'myvar'/' 1, /* start value one: variable value */
'IFRAUGMT C2X NEXTWORD', /* add EBCDIC hex value */
'NAMEBIND /EVENTID/', /*create output line for TEC slot */
'/'MSUSEG('0000.31.30',3)'/ 1', /*start line with text vec */
'NAMEBIND /ALERT31/', /* create another TEC slot */
'| PPI TECROUTE IHSATEC' /* transfer event to TEC */
/* Note use of virgule (/) to create a delimited string from the*/
/* value of MSUSEG function assumes no virgule (and no stage sep*/
/* character) exists in the text. In actual practice, it would */
/* be wise to use non-printable characters for both delimiters. */