Logstream size considerations
We might need to modify the size of the logstream record size if the application server is attempting to write messages that are too large. If a message is too large, you will receive an error message that will be written to the job log.
If the logstream record size is too small for a message being written to it, you see a message similar to the following written to your job log:
- TRAS0024I: Log entry is of size 5012 bytes which is too large to be added to log stream which is configured for 4096 byte records. Log entry will not be logged to the log stream.
The original message is also written to the job log and can be viewed there.
To resolve this issue and ensure the messages fit into the logstream, change the MAXBUFSIZE of the error log logstream. The following code shows an example where the sample BBOERRLG job generated by the Profile Management Tool or the zpmt command is modified to set the MAXBUFSIZE to 8192:
- //BBOERRLG JOB (ACCTNO,ROOM),'USER10',CLASS=A,REGION=0M //* //* //* //BBORCLGS EXEC PGM=IXCMIAPU //STDOUT DD STDERR=* //SYSIN DD * DATA TYPE(LOGR) DEFINE LOGSTREAM NAME(WAS.TY5.ERROR.LOG) DASDONLY(YES) HLQ(LOGGER) LS_SIZE(500) STG_SIZE(500) MAXBUFSIZE(8192) AUTODELETE(YES) RETPD(1) LS_DATACLAS(STANDARD)
Related tasks
Reference topic