Resolving system logger allocation errors

IXGLOGR allocation error messages related to system logger offload or staging data sets will be prefixed with IXG251I. These types of IXG251I prefixed messages provide the information necessary to resolve allocation failure. Figure 1 is an example of a IXG251I prefixed error message.

Figure 1. Example: IXG251I prefixed error message
IXG251I IKJ56893I DATA SET
IXGLOGR.CICSTS13.CICSVR.DFHLGLOG.A0000000 NOT
 ALLOCATED+                                          
IXG251I IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET IXGLOGR.CICSTS13.CICSVR.DFHLGLOG.A0000000
IXG251I RETURN CODE IS 56 REASON CODE IS 6 IGG0CLFT  
IXG251I IGD306I UNEXPECTED ERROR DURING IGG0CLFT PROCESSING  
IXG251I RETURN CODE 56 REASON CODE 6 
IXG251I THE MODULE THAT DETECTED THE ERROR IS IGDVTSCU    
IXG251I SMS MODULE TRACE BACK - VTSCU VTSCT VTSCH VTSCD VTSCC VTSCR SIRT          
IXG251I SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00007   
IXG251I IGD17219I UNABLE TO CONTINUE DEFINE OF DATA SET IXGLOGR.CICSTS13.CICSVR.DFHLGLOG.A0000000
IXG002E LOGR POLICY PROCESSING ENDED WITH RETCODE=00000008 RSNCODE=00000805  
IXG003I LOGR POLICY PROCESSING ENCOUNTERED AN UNEXPECTED ERROR. 
DIAGNOSIS INFORMATION: 00000004 000042CF 0107001B 00000000
Note: If you take the second word of the Diagnosis Information and convert it from hex to decimal, you will get the IGD message suffix. In this case, &hex;42CF is 17103 decimal. Searching the Syslog for Message IGD17103I will allow you to find more information related to this problem.
Some common reasons for allocation failure are:
  1. IXGLOGR Start of changeaddress spaceEnd of change does not have TRUSTED authority.
    • The allocation failure can be resolved by updating the IXGLOGR Start of changeaddress spaceEnd of change to have TRUSTED authority. For new authority to take effect, the IXGLOGR Start of changeaddress spaceEnd of change must be stopped and restarted. See Restarting the system logger address space for information on stopping and restarting the IXGLOGR address space.
  2. There is not enough space on DASD to allocate the data set.
    • In this case, free up space or allow SMS to use more volumes.
  3. The error message indicates the data set is not in the catalog or the catalog can not be accessed.

    The problem could be caused by one of the following:

    • The data set was manually deleted.
      • Prevent users from manually deleting system logger offload or staging data sets.
    • There is a catalog problem.
      • The catalog problem must be resolved
    • The shareoptions of the data set are not 3,3.
      • Update the SHAREOPTIONS to 3,3 (the default for SHAREOPTIONS is 1,3) using IDCAMS, and update the DATACLASS associated with the log stream to prevent future problems.
    • Two or more sysplexes are trying to allocate the same staging data set at the same time.
      • Use different log stream names on the different sysplexes, or do not share the catalog across the sysplexes.
    • Two or more sysplexes allocating to the same named staging data set, one after the other, may result in system logger's failure to recover data for one or both of the sysplexes involved.
      • Use different log stream names on the different sysplexes, or do not share the catalog across the sysplexes.

      For example, if SYSA in PLEXA did not delete the staging data set when the last disconnect occurred, then SYSA needs to have the staging data set available when it reconnects to the log stream to offload data. However, if SYSB in PLEXB tries to connect to a log stream which requires a staging data set with the same name as the staging data set left behind by SYSA, SYSB will delete the existing data set and create a new one. So, when SYSA reconnects later, recovery for the log stream will fail.

For a complete list of IXG messages, see z/OS MVS System Messages, Vol 10 (IXC-IZP).

Parent topic: System logger