Appendix C. WEB LOG EXTRACTOR (WLE) OVERVIEW › C.4 WLE Load Utility Messages
C.4 WLE Load Utility Messages
This appendix lists all messages generated by the WLE Server.
Some messages are generated during the processing of the
control statements, while others are caused by various
conditions in the data found during processing. The messages
are listed in ascending numerical sequence and include the
full text of the message, the type, the reason for the
message, appropriate user action, and applicable references
to documentation.
The following type codes are used to categorize the messages:
Information Designates a note that documents a web
server option or potentially important
feature in the data.
Warning Designates a condition in either the data or
the control statements that does not affect
the web server's operation, but that may
lead to unexpected results.
Error Designates that a problem has been
encountered with a control statement that
will prevent a successful run of the Server.
Execution is stopped after all control
statements are processed.
The message text often includes references to information
that is contained in a control statement or values of
permanent or temporary variables created during web server
processing. In the descriptions below, a message text may
contain a word beginning with a percent sign (%), which
indicates that a value will be substituted into the text at
execution time. %S signifies that a character string will be
substituted and %D signifies that a decimal string will be
substituted. For example, message WLE0054E reads as follows:
INVALID DATE IN LOG RECORD, FOUND %S.
If an invalid record was detected in a specific log record
where %S='Jun072000' then the message is printed as follows:
INVALID DATE IN LOG RECORD, FOUND JUN072000
This sections lists all messages generated by the CA MICS WLE
Load utility.
+----------+
| WLE0001E |
+----------+
TEXT: INVALID COMMAND LINE ARGS, USAGE:
PGNAME.EXE -d date FILENAME
TYPE: Error
REASON: The command line arguments were incorrect.
-d date is optional. Filename is required
and defines the path/filename of the
configuration file.
ACTION: Re-execute the program with the proper
command line arguments.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0002E |
+----------+
TEXT: OPEN FAILED FOR INPUT CONFIGURATION FILE
"FILENAME"
TYPE: Error
REASON: The open failed for the configuration file
specified as the first command line argument.
ACTION: Check the path and filename specified on the
command line argument and ensure the file
exists.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0003E |
+----------+
TEXT: EXECUTION TERMINATED DUE TO PREVIOUS ERROR
TYPE: Error
REASON: A severe error occurred and execution cannot
continue.
ACTION: Refer to previously printed messages for
problem determination.
REFERENCES: Refer to previously printed messages for
problem determination.
+----------+
| WLE0004E |
+----------+
TEXT: ERROR READING INPUT CONFIGURATION FILE
"FILE"
TYPE: Error
REASON: An error occurred while reading the input
configuration file.
ACTION: Check that the input configuration file
contains data.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0005E |
+----------+
TEXT: MALLOC FAILED FOR CONFIGURATION
TYPE: Error
REASON: An error occurred while attempting to
allocate storage to contain configuration
file data.
ACTION: Determine why storage is low in USS address
space and reexecute program.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0006E |
+----------+
TEXT: MAXIMUM LENGTH OF KEYWORD TOKEN IS 13,
FOUND "TOKEN"
TYPE: Error
REASON: A keyword was found that was longer than the
maximum allowable keyword length.
ACTION: Update the configuration file keyword
parameter in error and reexecute program.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0007E |
+----------+
TEXT: A VALUE MUST BE SPECIFIED WITH A KEYWORD
TYPE: Error
REASON: A valid keyword was entered with no
corresponding value.
ACTION: Update the configuration file keyword
parameter to contain a value.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0008E |
+----------+
TEXT: THE MAXIMUM LENGTH OF A KEYWORD VALUE IS 128,
FOUND "VALUE" THAT EXCEEDED THE MAXIMUM
ALLOWABLE VALUE LENGTH.
TYPE: Error
REASON: A valid keyword was entered with a value that
exceeded the maximum allowable value length.
ACTION: Update the configuration file keyword
parameter to contain a value of less than 128
characters.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0009E |
+----------+
TEXT: INVALID KEYWORD ENCOUNTERED, "KEYWORD"
TYPE: Error
REASON: An unknown keyword was encountered.
ACTION: Update the configuration file keyword in
error to an acceptable value.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0010E |
+----------+
TEXT: INVALID KEYWORD PARAMETER ENCOUNTERED,
"VALUE"
TYPE: Error
REASON: A valid keyword was encountered with an
invalid value.
ACTION: Update the configuration file keyword
parameter in error to an acceptable value.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0011E |
+----------+
TEXT: PARAMETER FOR THIS KEYWORD MUST BE YES OR NO
TYPE: Error
REASON: A valid keyword was encountered with a value
other than YES or NO.
ACTION: Update the configuration file keyword
parameter to a value of YES or NO.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0012E |
+----------+
TEXT: RECTYPE VALUE MUST BE BETWEEN 128 AND 255
TYPE: Error
REASON: A valid keyword was encountered with an out-
of-bounds value.
ACTION: Update the configuration file keyword
parameter to a value between 128 and 255.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0013E |
+----------+
TEXT: THE %s NAME EXCEEDS MAXIMUM OF 44 CHARACTERS
TYPE: Error
REASON: Either the DataSetName keyword or the
DSmodelDSCB keyword was specified with a name
containing more than 44 characters.
ACTION: Update the configuration file keyword
parameter to a value of less than 44
characters.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0014E |
+----------+
TEXT: THE FIRST CHARACTER OF EACH %s NODE MUST BE
ALPHABETIC
TYPE: Error
REASON: The first character of DataSetName node or
DSmodelDSCB name node was not an alphabetic
character.
ACTION: Update the configuration file keyword
parameter to a valid OS/390 data set name or
model DSCB.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0015E |
+----------+
TEXT: A NODE EXCEEDS THE MAXIMUM LENGTH OF 8
TYPE: Error
REASON: The DataSetName keyword value was found to
contain a node with more than 8 characters.
ACTION: Update the configuration file keyword
parameter to a valid OS/390 data set name.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0016E |
+----------+
TEXT: TWO CONSECUTIVE NODE SEPARATORS WERE FOUND,
INVALID
TYPE: Error
REASON: The DataSetName keyword value or the
DSmodelDSCB keyword value was found to
contain two consecutive node separators.
ACTION: Update the configuration file keyword
parameter to a valid OS/390 data set name.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0017E |
+----------+
TEXT: A NUMERIC VALUE WAS EXPECTED, FOUND
NON-NUMERIC DATA
TYPE: Error
REASON: A value that should contain numeric data was
found to have non-numeric data.
ACTION: If subsequent messages indicate keyword
processing, correct the keyword parameter in
the WLE configuration file. If processing log
file data, try to determine the cause of
invalid data that is logged in the log file.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0018E |
+----------+
TEXT: PARAMETER FOR THIS KEYWORD MUST BE SPECIFIED
AS NEW OR OLD
TYPE: Error
REASON: A keyword was encountered that requires a
value of NEW or OLD, and the value was
neither.
ACTION: Update the configuration file keyword
parameter to a value of NEW or OLD.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0019E |
+----------+
TEXT: COMPANY NAME MAY NOT EXCEED 40 CHARACTERS
TYPE: Error
REASON: The company keyword had a value that exceeded
the maximum allowable length.
ACTION: Update the configuration file keyword
parameter to contain value with 40 characters
or less.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0020E |
+----------+
TEXT: LENGTH OF KEYWORD VALUE EXCEEDS MAXIMUM
TYPE: Error
REASON: A keyword was encountered with a value that
exceeds the maximum length for that keyword.
ACTION: Update the configuration file keyword
parameter to contain a value with an
appropriate length.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0022E |
+----------+
TEXT: THIS KEYWORD PARAMETER REQUIRES UPPER CASE
TYPE: Error
REASON: A keyword requiring an uppercase value was
encountered that contained lowercase data.
ACTION: Update the configuration file keyword
parameter to contain a valid OS/390 unit
specification.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0023E |
+----------+
TEXT: VOLSER PARAMETER MUST BE 6 CHARACTERS IN
LENGTH
TYPE: Error
REASON: The VOLSER keyword specified a parameter that
was greater than 6 characters in length.
ACTION: Update the configuration file keyword
parameter to contain a valid OS/390 VOLSER
specification.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0024E |
+----------+
TEXT: THE FIRST CHARACTER OF VOLSER MUST BE
ALPHABETIC
TYPE: Error
REASON: The VOLSER keyword specified a parameter that
began with a non-alphabetic character.
ACTION: Update the configuration file keyword
parameter to contain a valid OS/390 VOLSER
specification.
REFERENCES: Sections C.2.1.1 or C.2.1.2 in this
guide.
+----------+
| WLE0025E |
+----------+
TEXT: THE FIRST CHARACTER OF %s MUST BE ALPHABETIC
TYPE: Error
REASON: The DSstorclas, DSdataClas, or DSmgmtClas
keyword specified a parameter that began with
a non-alphabetic character.
ACTION: Update the configuration file keyword
parameter to contain a valid OS/390 Storclas,
DataClas, or MgmtClas specification.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0026E |
+----------+
TEXT: DATASETNAME MUST BE SPECIFIED
TYPE: Error
REASON: The DataSetName keyword was not found.
ACTION: The DataSetName keyword must be specified
with a valid OS/390 data set name.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0027E |
+----------+
TEXT: FIRST CHARACTER OF SERVERNAME MUST BE
ALPHABETIC
TYPE: Error
REASON: The ServerName keyword was specified with a
parameter that began with a non-alphabetic
character.
ACTION: Update the configuration file keyword
parameter to contain a servername that begins
with an alphabetic character.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0028E |
+----------+
TEXT: THIS KEYWORD PARAMETER MUST BE ALPHA-NUMERIC
TYPE: Error
REASON: A keyword parameter that is required to be
alpha-numeric is not.
ACTION: Update the configuration file to contain a
value with alpha-numeric characters only.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0029E |
+----------+
TEXT: SERVERNAME KEYWORD MUST PRECEDE THIS KEYWORD
TYPE: Error
REASON: A keyword that must be associated with a
servername has been encountered, but no
servername keyword has been encountered.
ACTION: Update the configuration file to contain the
ServerName keyword before this keyword.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0030E |
+----------+
TEXT: DUPLICATE KEYWORD WITHIN SEGMENT FOUND
TYPE: Error
REASON: A duplicate keyword within a Servername
segment has been encountered and is invalid.
ACTION: Update the configuration file so that no two
keywords in a ServerName segment are the
same.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0031E |
+----------+
TEXT: KEYWORDS HOSTNAME, PORTNO, AND ORGSYSID ARE
REQUIRED AND NOT FOUND
TYPE: Error
REASON: The keywords HostName, PortNo, and Orgsysid
are required entries and none were found.
ACTION: Update the configuration file so that each
ServerName segment contains a HostName,
PortNo, and Orgsysid specification.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0032E |
+----------+
TEXT: AT LEAST ONE LOG FILE MUST BE SELECTED FOR
PROCESSING.
TYPE: Error
REASON: A ServerName segment was encountered that had
no log files specified for processing.
ACTION: Update the configuration file so that each
ServerName segment contains at least one log
file to process. If no log file processing
is required for this ServerName, remove it
from the configuration file.
REFERENCES: Sections C.2.1.1 or C.2.1.2 in this
guide.
+----------+
| WLE0033E |
+----------+
TEXT: AT LEAST ONE SERVERNAME PARAMETER WITH
SEGMENT PARAMETERS MUST BE SPECIFIED.
TYPE: Error
REASON: No ServerName keywords and associated
parameters were found in the configuration
file.
ACTION: Update the configuration file adding a
Servername keyword and associated segment
parameters. If no log file processing is
required for this ServerName, remove it from
the configuration file.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0034E |
+----------+
TEXT: CLOSE ERROR OCCURRED ON CONFIGURATION FILE.
TYPE: Error
REASON: An error occurred during close processing for
the configuration file.
ACTION: Reexecute the program. If the problem
persists, contact CA Technical Support.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0036E |
+----------+
TEXT: MALLOC FAILED FOR RECORD BUFFER.
TYPE: Error
REASON: An error occurred while trying to obtain
storage to hold record segment data.
ACTION: Determine why storage is low in UNIX System
Services and reexecute the program.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0037E |
+----------+
TEXT: FOPEN FAILED FOR WLEDATA.
TYPE: Error
REASON: An error occurred while opening the OS/390
ddname WLEDATA.
ACTION: If DSdisp in the configuration file was
specified as OLD, ensure that the data set
exists. If it does not, specify DSdisp as
new and reexecute program.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0038E |
+----------+
TEXT: FCLOSE FAILED FOR WLEDATA.
TYPE: Error
REASON: An error occurred while closing the OS/390
ddname WLEDATA.
ACTION: Reexecute the program. If the problem
persists, contact CA Technical Support.
REFERENCES: None
+----------+
| WLE0039E |
+----------+
TEXT: DYNALLOC FAILED, ERROR CODE = XXXX,
INFO CODE = XXXX, S99ERSN = XXXX.
TYPE: Error
REASON: An error occurred while attempting to
DYNALLOC the WLEDATA ddname.
ACTION: Look up the returned values for ERROR CODE,
INFO CODE, and S99ERSN to assist in problem
determination. Check for conflicting
parameters in the configuration file.
The meaning of the returned values for
ERROR CODE, INFO CODE and S99ERSN can be
found in the IBM Manual - MVS Programming:
Authorized Assembler Services Guide.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0040I |
+----------+
TEXT: WEB LOG EXTRACT CONFIGURATION PROCESSING
BEGINS.
TYPE: Informational
REASON: Indicates that configuration data is about to
be processed.
ACTION: None
REFERENCES: None
+----------+
| WLE0041I |
+----------+
TEXT: %D CONFIGURATION SEGMENTS CREATED IN %D
RECORDS.
TYPE: Informational
REASON: Indicates the number of configuration
segments processed and the number of records
written.
ACTION: None
REFERENCES: None
+----------+
| WLE0042I |
+----------+
TEXT: WEB LOG EXTRACT CONFIGURATION PROCESSING
COMPLETE.
TYPE: Informational
REASON: Indicates that configuration segment
processing completed successfully.
ACTION: None
REFERENCES: None
+----------+
| WLE0043E |
+----------+
TEXT: ERROR WRITING TO WLEDATA, ERRNO = %D.
TYPE: Error
REASON: An error occurred trying to write to DDname
WLEDATA.
ACTION: Use errno value to determine the cause of the
failure.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this guide.
+----------+
| WLE0044I |
+----------+
TEXT: %D RECORDS WRITTEN FOR THIS EXECUTION.
TYPE: Informational
REASON: Indicates the total number of records
written.
ACTION: None
REFERENCES: None
+----------+
| WLE0045E |
+----------+
TEXT: INVALID DATE ENTERED AS COMMAND LINE ARG,
FOUND %S.
TYPE: Error
REASON: The user entered a date as a command line
argument to process log files other than the
defaults, and the date was invalid.
ACTION: Reexecute WLELOAD supplying a valid date in
the format MMDDYYYY.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0046E |
+----------+
TEXT: ERROR PROCESSING LOG FILE %S.
TYPE: Error
REASON: An error occurred while processing this log
file.
ACTION: See other correlating error messages for more
detailed information about the error.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0047W |
+----------+
TEXT: OPEN FAILED FOR LOG FILE.
TYPE: Error
REASON: An error occurred while opening the log file
indicated in message WLE0051E.
ACTION: Determine if the path name specified in the
configuration file is correct. If the path
name is specified correctly, it may indicate
that no records were produced for this log
file in the preceding day.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0048E |
+----------+
TEXT: ERROR READING LOG FILE.
TYPE: Error
REASON: An error occurred while reading the log file
indicated in message WLE0046E.
ACTION: Determine that the log file exists and is
accessible to the program and rerun job. If
the problem persists, contact CA Technical
Support for assistance.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0049I |
+----------+
TEXT: WEB LOG EXTRACT LOG FILE PROCESSING BEGINS.
TYPE: Informational
REASON: Informational message indicating that log
file processing is starting.
ACTION: None
REFERENCES: None
+----------+
| WLE0050E |
+----------+
TEXT: MAXIMUM LENGTH OF DOMAIN NAME / TCP/IP
ADDRESS OR HOST NAME EXCEEDED.
TYPE: Error
REASON: Client IP address of hostname is longer than
expected.
ACTION: Review log file for possible corruption. If
log file appears correct and is in the common
log format, contact CA Technical Support.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0051I |
+----------+
TEXT: PROCESSING LOG FILE %S FOR SERVER %S.
TYPE: Informational
REASON: Informational message indicating the log file
being processed and the server that it
belongs to.
ACTION: None
REFERENCES: None
+----------+
| WLE0052E |
+----------+
TEXT: INVALID RECORD IN LOG FILE, FOUND %S.
TYPE: Error
REASON: An invalid record was detected in the log
being processed.
ACTION: Check the log records and make sure they are
in the common format. Possible missing
delimiter.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0053E |
+----------+
TEXT: MAXIMUM LENGTH OF AUTHID WAS EXCEEDED, FOUND
%S.
TYPE: Error
REASON: An invalid record was detected in the log
being processed.
ACTION: Check the log records and make sure they are
in the common format. Possible missing
delimiter.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0054E |
+----------+
TEXT: INVALID DATE IN LOG RECORD, FOUND %S.
TYPE: Error
REASON: An invalid record was detected in the log
being processed.
ACTION: Check the log records and make sure they are
in the common format. Possible missing
delimiter.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0055E |
+----------+
TEXT: MISSING TOKEN IN LOG RECORD, FOUND %S.
TYPE: Error
REASON: An invalid record was detected in the log
being processed.
ACTION: Check the log records and make sure they are
in the common format. Possible missing
delimiter.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0056E |
+----------+
TEXT: INVALID TIME IN LOG RECORD, FOUND %S.
TYPE: Error
REASON: An invalid record was detected in the log
being processed.
ACTION: Check the log records and make sure they are
in the common format. Possible missing
delimiter.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0057E |
+----------+
TEXT: INVALID REQUEST IN LOG RECORD, FOUND %S.
TYPE: Error
REASON: An invalid record was detected in the log
being processed.
ACTION: Check the log records and make sure they are
in the common format. Possible missing
delimiter.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0058E |
+----------+
TEXT: INVALID URI IN LOG RECORD, FOUND %S.
TYPE: Error
REASON: An invalid record was detected in the log
being processed.
ACTION: Check the log records and make sure they are
in the common format. Possible missing
delimiter.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0059E |
+----------+
TEXT: INVALID SERVER IN LOG RECORD, FOUND %S.
TYPE: Error
REASON: An invalid record was detected in the log
being processed.
ACTION: Check the log records and make sure they are
in the common format. Possible missing
delimiter.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0060E |
+----------+
TEXT: INVALID RELEASE IN LOG RECORD, FOUND %S.
TYPE: Error
REASON: An invalid record was detected in the log
being processed.
ACTION: Check the log records and make sure they are
in the common format. Possible missing
delimiter.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0061E |
+----------+
TEXT: INVALID STATUS IN LOG RECORD, FOUND %S.
TYPE: Error
REASON: An invalid record was detected in the log
being processed.
ACTION: Check the log records and make sure they are
in the common format. Possible missing
delimiter.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0062E |
+----------+
TEXT: INVALID BYTES TRANSFERRED IN LOG RECORD,
FOUND %S.
TYPE: Error
REASON: An invalid record was detected in the log
being processed.
ACTION: Check the log records and make sure they are
in the common format. Possible missing
delimiter.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0063I |
+----------+
TEXT: %D SUBTYPE %D %S SEGMENTS CREATED IN %D
RECORDS.
TYPE: Informational
REASON: Indicates how many log records were
processed, and how many subtype records were
written for which type of log being
processed.
ACTION: None
REFERENCES: None
+----------+
| WLE0064W |
+----------+
TEXT: EMPTY LOG FILE ENCOUNTERED, PROCESSING
CONTINUES.
TYPE: Warning
REASON: An empty log file was encountered.
ACTION: Determine if data was missed, and rerun job
if required.
REFERENCES: None
+----------+
| WLE0065E |
+----------+
TEXT: INVALID AGENT/REFERER DATA IN LOG RECORD,
FOUND %S.
TYPE: Error
REASON: An unexpected data format was found in the
agent referer log records.
ACTION: Make sure your server is recording log
information in the common log format and that
you are processing the correct file.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0066E |
+----------+
TEXT: CLOSE ERROR ON LOG FILE %S.
TYPE: Error
REASON: An error occurred while closing log file %s.
ACTION: Execute the web log extract again, if
problems persist, contact CA Technical
Support.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0067I |
+----------+
TEXT: WEB LOG EXTRACT EXECUTION COMPLETE.
TYPE: Informational
REASON: Web log extract processing has completed
successfully.
ACTION: None
REFERENCES: None
+----------+
| WLE0068E |
+----------+
TEXT: ERROR LIMIT FOR LOG FILE EXCEEDED.
TYPE: Error
REASON: Web log extract processing terminates because
the error threshold for an individual file
has been reached.
ACTION: Check to ensure the log file being processed
is the correct one. If so, raise the error
limit.
REFERENCES: Sections C.2.1.1 and C.2.1.2 in this
guide.
+----------+
| WLE0069W |
+----------+
TEXT: %d TOTAL LOG FILE DATA ERROR ENCOUNTERED.
TYPE: Warning
REASON: Web log extract processing detected nnnn
errors in log file data.
ACTION: If the error threshold was not exceeded,
execution ends successfully. If message
WLE0068E was issued previously, determine if
error threshold is not high enough or a bad
log file was processed.
REFERENCES: None
+----------+
| WLE0070W |
+----------+
TEXT: %d LOG FILE DATA ERRORS ENCOUNTERED FOR
PREVIOUS FILE.
TYPE: Warning
REASON: Web log extract processing detected nnnn
errors in log file data for the previous
file.
ACTION: Warning message issued when log file data
errors found without exceeding the error
threshold.
REFERENCES: None
+----------+
| WLE0071E |
+----------+
TEXT: LENGTH OF KEYWORD VALUE MUST BE 4.
TYPE: Error
REASON: The Orgsysid keyword parameter value coded is
not four bytes long.
ACTION: Update the prefix.MICS.PARMS(WLECONF) file
keyword parameter that is in error to contain
an Orgsysid value that is four bytes long.
REFERENCES: Section C.3.3 in this guide.
