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.
z/OS JES3 Commands also contains information on the format of logged messages.
The requirements for the caller are:
| Environmental factor | Requirement |
|---|---|
| Minimum authorization: | Problem state and any PSW key. |
| Dispatchable unit mode: | Task |
| Cross memory mode: | PASN=HASN=SASN |
| AMODE: | 24- or 31-bit |
| ASC mode: | Primary |
| Interrupt status: | Enabled for I/O and external interrupts |
| Locks: | No locks held |
| Control parameters: | Must be in the primary address space. |
None.
Message text cannot exceed 126 characters. If the message text exceeds 126 characters, truncation occurs at the last embedded blank before the 126th character; when there are no embedded blanks, truncation occurs after the 126th character.
Before 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.
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.
None.
The standard form of the WTL macro is written as follows:
| Syntax | Description |
|---|---|
| name | name: Symbol. Begin name in column 1. |
| ␢ | One or more blanks must precede WTL. |
| WTL | |
| ␢ | One or more blanks must follow WTL. |
| ‘msg’ | msg: Up to 126 characters. |
The parameter is explained as follows:
None.
| Return Code | Reason Code | Meaning and Action |
|---|---|---|
| 0 | None | Meaning: WTL processing completed successfully.
The system logged the message in SYSLOG, and, if OPERLOG was requested,
the system logged the message in OPERLOG. Action: None. |
| 0 | 04 | Meaning: WTL processing completed successfully.
The message was logged in the operations log (OPERLOG log stream).
The system log was not active. Action: If you want the message logged in the system log, start the system log and rerun the program. |
| 0 | 08 | Meaning: WTL processing completed, but
the message was only logged in the operations log because the WTL
system log buffers are full. Action: Do one of the following,
if you want subsequent messages logged in the system log:
|
| 0 | 0C | Meaning: WTL processing completed, but
the message was only logged in the system log because the operations
log was not active. Action: If you want the message logged in the operations log, start the operations log and rerun the program. This will also place the message in the system log. |
| 0 | 10 | Meaning: WTL processing completed, but
the message was only logged in the system log. The message was not
logged in the OPERLOG log stream because of a storage problem. Action: If you want the message logged in the operations log, retry the request. This will also place the message in the system log. If the problem persists, contact the IBM Support Center. Provide the return and reason code. |
| 04 | 04 | Meaning: System error. WTL processing was
not successful. Recovery could not be established. Action: Retry the request. If the problem persists, record the return and reason code and supply them to the appropriate IBM support personnel. |
| 04 | 08 | Meaning: Environmental error. The system
log and the operations log are not active. Action: Start the logs and rerun your program. |
| 04 | 0C | Meaning: Environmental error. The WTL limit
has been reached. Action: Do one of the following:
Note: If the problem is persistent, you might want to perform
step 2 first and step 3 at the next IPL.
|
| 04 | 10 | Meaning: System error. An internal error
occurred. The system issues message IEE390I. Action: Contact the IBM Support Center. Provide the return and reason code. |
| 04 | 14 | Meaning: System error. The system encountered
a (VSM) error. The system issues message IEE390I. Action: Contact the IBM Support Center. Provide the return and reason code. |
| 04 | 18 | Meaning: Environmental error. The message
was not logged in either the system log or the operations log, because
neither log is active. Action: Do one of the following:
|
| 04 | 1C | Meaning: Environmental error. The message
was not logged in the system log, as requested, because the WTL limit
has been reached. The operation log was not active at the time, so
the message was not logged there either. Action: To log
the message in the system log, do the following:
To log the message in the operations log, start the operations log and rerun the program. |
| 04 | 20 | Meaning: Environmental error. The message
was not logged in the operations log, as requested, because of storage
problems. The system log was not active. Action: To log the message in the operations log, retry the request. If the problem persists, contact the IBM Support Center, providing the return and reason codes. To log the message in the system log also, start the system log and rerun the program. |
| 04 | 24 | Meaning: Environmental error. The message
was not logged in the system log because the WTL limit has been reached,
and was not logged in the operation log because of storage problems. Action: To log the message in the operations log, retry the request. If the problem persists, contact the IBM Support Center, providing the return and reason codes. |
WTL 'THIS IS THE STANDARD FORMAT FOR THE WTL MACRO'WTL MF=(E,(R2))