Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Description z/OS MVS Programming: Authorized Assembler Services Reference SET-WTO SA23-1375-00 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Note: IBM® recommends that you use the WTO macro with
the MCSFLAG=HRDCPY parameter instead of WTL, because WTO supplies
more data than WTL.
The WTL macro causes a message to be written to the system log (SYSLOG) or the operations log (OPERLOG) log stream depending on which one of these logs, or both, is active. The message can include any character that can be used in a C-type (character) DC statement, and is assembled as a variable-length record. Note: When a message is recorded in SYSLOG, the exact format of the
output of the WTL macro varies depending on the job entry subsystem
(JES2 or JES3) that is being used, the output class that is assigned
to the log at system initialization, and whether DLOG is in effect
for JES3. See the z/OS® MVS™ System
Messages manuals for information on the format of logged messages.
z/OS JES3 Commands also contains information about the format of logged messages. The description of the WTL macro follows. The WTL macro is also described in z/OS MVS Programming: Assembler Services Reference IAR-XCT (with the exception of the OPTION parameter). EnvironmentThe requirements for the caller are:
Programming requirementsNone. RestrictionsMessage text cannot exceed 126 characters. If the message text exceeds 126 characters, truncation occurs after the 126th character. Input register informationBefore issuing the WTL macro, the caller does not have to place any information into any register unless using it in register notation for a particular parameter, or using it as a base register. Output register informationWhen control returns to the caller, the GPRs contain:
When control returns to the caller, the access registers (ARs)
contain:
Some callers depend on register contents remaining the same before and after issuing a service. If the system changes the contents of registers on which the caller depends, the caller must save them before issuing the service, and restore them after the system returns control. Performance implicationsNone. SyntaxThe standard form of the WTL macro is written as follows:
ParametersThe parameters are explained as follows:
ABEND codesNone. Return and reason codesWhen the WTL macro returns control to your program, GPR 15 contains
a hexadecimal return code and GPR 0 contains a hexadecimal reason
code. WTL issues a return code (either 00 or 04), with multiple reason
codes for each. The return codes indicate the following:
Example 1Write a message to the system log.
Example 2Write a message to the system log specifying a prefix to identify
the system log record.
Example 3Build a parameter list for a message to be written to the system
log.
Example 4Write a message constructed in the list form of WTL.
|
Copyright IBM Corporation 1990, 2014
|