Some problems that occur in the system logger can be fixed with
relatively simple adjustments to data set sizes or logger policy parameters.
The following is a list of common problems that can be remedied by
the user:
- If log stream data is missing or inaccessible, or new log stream offload data sets are being allocated before the old ones are filled, it may be that the Virtual Storage Access Method (VSAM) SHAREOPTIONS (3,3) was not specified when the data set was allocated (the default for SHAREOPTIONS is 1,3).
- If log stream data is deleted unexpectedly, or is retained too long, check AUTODELETE and RETPD in the LOGR policy to verify that the correct values have been specified.
- Offload problems may be caused by improper sizing of the log stream offload data sets (LS_SIZE). Small data sets may result in too many offload data sets, which can cause directory problems.
- Incorrect sizing of the staging data set (STG_SIZE) may cause offloads to occur too frequently.
- Message IXG251I with reason code 805 can mean that IXGLOGR is
not marked as TRUSTED to the security product, preventing data sets
from being allocated. If this is true, update the attribute and stop
and restart the IXGLOGR
address space to have the
new authority take affect. See Restarting the system logger address space for
information on getting the IXGLOGR address space restarted.
If this is not the cause of the problem (IXGLOGR is marked as
TRUSTED), examine associated syslog messages for a possible SMS or
catalog problem.
- Message IXG002E with return code 8 and reason code 823 can indicate that the LSR, LSTRR or DSEXTENT values in the logger policy are not sufficient.
- Incorrect sizing of a list structure or by having too many log streams in a list structure can cause errors. You might be able to avoid this problem by using the System z® Coupling Facility Structure Sizer Tool (CFSizer). The CFSizer simplifies the task of estimating the amount of storage required by the coupling facility structures used in your installation. The CFSizer asks questions about your existing configuration, and then use the answers you give to build customized jobs that you can run to create various structures as well as the LOGR couple data set, and OPERLOG and LOGREC log streams. See the http://www.ibm.com/systems/support/z/cfsizer/.
- Using IDCAMS REPRO to copy log stream offload data sets can result
in errors indicated by messages IDC3302I, IDC3350I such as the following:
REPRO INFILE(SYS00014) - OUTFILE(SYS00015) IDC3302I ACTION ERROR ON MTSYSL.CICSAAU3.USAUAAU3.DFHLOG.A0000010 IDC3350I 10014,15173874,00000000B000,D,AXR000,USZCZT0T,STEP1,6 6D7,DA,SYS00014,A6- OP,INCORR. LENGTH ,00000020000B0C,VSAM IDC3302I ACTION ERROR ON MTSYSL.CICSAAU3.USAUAAU3.A0010074.T5173829 IDC3351I ** VSAM I/O RETURN CODE IS 28 - RPLFDBWD = X'2908001C' IDC31467I MAXIMUM ERROR LIMIT REACHED. IDC0005I NUMBER OF RECORDS PROCESSED WAS 36 IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
If you receive this error, see the topic Managing logger log stream data sets for the subtopic on "Copying log stream offload data sets" in z/OS MVS Setting Up a Sysplex.