Candle KLVHSKONCT GC32-9172-00 User Manual

Page 19

Advertising
background image

KLVHS001–KLVSC009

19

KLVLW041

RKLVLOG DATASET DISABLED BY PERMANENT ERROR

Explanation: A BSAM WRITE issued against the currently active RKLVLOG file
failed because of a permanent error.
System Action: RKLVLOG recording is suspended.
User Response: Refer to the MVS SYSLOG for any messages that may have
been issued by IBM’s data management routines. Issue TLVLOG SWITCH to
attempt to allocate a new RKLVLOG dynamically.
Severity: ALERT.

KLVLW081

DYNAMIC ALLOCATION FAILED FOR RKLVLOG: R15(rc) ERROR(error)
INFO(
info)

Explanation: A TLVLOG SWITCH request was not successful because the
dynamic allocation for a new SYSOUT file failed. rc is the return code from the
DYNALLOC request; error and info are the error and information reason codes.
System Action: The command terminates. The previous RKLVLOG is still
active.
User Response: Refer to RKLVLOG or VIEWLOG for any KLVDAnnn
messages that may have been issued. Refer to IBM’s Authorized Assembler
Programming Reference

for DYNALLOC return codes.

Severity: LOG, ERROR.

KLVLW082

COULD NOT OPEN ddname FOR RKLVLOG

Explanation: A TLVLOG SWITCHrequest could not open a dynamically
allocated SYSOUT file. ddname is the ddname that could not be opened.
System Action: The command terminates. The previous RKLVLOG is still
active; ddname remains allocated to the CT/Engine address space.
User Response: Refer to SYSLOG for any IEFxxxxx messages that may
describe the OPEN error.
Severity: LOG, ERROR.

KLVLW083

DYNAMIC DEALLOCATION FAILED FOR RKLVLOG: R15(rc)
ERROR(
error) INFO(info)

Explanation: A TLVLOG SWITCH request could not dynamically deallocate
the RKLVLOG JCL DD statement. rc is the return code from the DYNALLOC
request; error and info are the error and information reason codes.
System Action: The RKLVLOG JCL DD statement remains allocated to the
CT/Engine address space. Refer to IBM’s Authorized Assembler Programming
Reference

for DYNALLOC return codes.

Severity: LOG, ERROR.

KLVLW084

*SYSTLG* OPERATOR LOGON FAILED

Explanation: The pseudo-operator *SYSTLG* could not be initialized.
System Action: *SYSTLG* will not be recognized if specified with the AS
operator command. All other RKLVLOG processing continues normally.
User Response: If you are using operator validation in a NAM user exit (for
example, KLVA2NEV), ensure that the *SYSTLG* operator is authorized for
logon.
Severity: LOG, ERROR.

Advertising