II12460: SYSTEM LOGGER DATA SET MANAGEMENT: PHYSICAL DELETION, RETPD & AUTODELETE.

APAR status

• INTRAN

Error description

• Choosing the Right Retention Period and Automatic Deletion
  Policy For a Log Stream
  .
  The RETPD parameter allows you to specify a retention period for
  a log stream. On RETPD, you specify the number of days that you
  want to keep data in the log stream, even if the data has been
  marked for deletion using IXGDELET. For example, if you specify
  RETPD(7) in the LOGR policy for a log stream, the retention
  period for data in that log stream is 7 days from the time the
  data is written to the log stream by the application. System
  logger processes the retention period on a log data set basis.
  Once the retention period for the entire log data set has
  expired, the data set is eligible for deletion. System logger
  may not physically delete data as soon as it hits the retention
  period. The point at which system logger physically deletes the
  data depends on when the data set fills and what you specify on
  the AUTODELETE parameter.  See "Deleting Log Data and Log Data
  Sets" in topic 9.5.
  .
  Note: If IXCMIAPU is run to UPDATE the RETPD, AUTODELETE or
  OFFLOADRECALL the change will take affect when the next
  dataset switch occurs at R703.  The update is made when
  a new connection is made or the last disconnect
  occurs at R705.
  .
  When Is My Log Data or Log Data Set Physically Deleted?
  .
  After log data is marked for deletion, system logger does not
  physically delete the log data or log data set until an offload
  requires a new data set to be allocated. This means that there
  will often be a delay before eligible log data sets are
  physically deleted, since offloading will not occur until the
  high threshold associated with the log stream is reached. If
  offloads are relatively infrequent, then there may be a
  considerable delay before log data sets that are eligible for
  deletion are actually deleted.
  .
  Allocation errors can also delay log data set deletion. If
  logger cannot delete a log data set because it is currently
  allocated, it will attempt to delete the log data set on a
  subsequent offload when delete processing is again performed.
  This situation can also delay the deletion of a log data set
  since system logger may attempt to delete an eligible log data
  set several times before it actually succeeds. See "Finding and
  Deleting Orphaned Log Data Sets" in topic 9.5.4.
  .
  If you specify the RETPD and AUTODELETE parameters to set a
  retention period and automatic deletion policy for a log stream
  the data set becomes eligable for deletion once the retention
  period has expired for all the log data in the log data set.
  System logger deletes the data on a log data set basis when the
  log data set is full, is no longer in use as the current logdata
  set for the log stream, and is not allocated by any system in
  the plex the next time a data set switch occurs.
  .
  Deleting Log Data
  .
  Use one of the following methods to delete log data:
  .
  Use the IXGDELET service in an application to delete data from
  the log stream as soon as the data is no longer needed.     This
  will help to manage log data set storage consumption by making
  sure log data sets are deleted as soon as possible.     See
  OS/390 MVS Programming: Assembler Services Reference for
  information on using the IXGDELET service.
  .
  *     For logrec log stream data, run EREP using the LOGR
  subsystem with the delete option. See program IFBEREPS in
  SYS1.SAMPLIB for examples of archiving and deleting logrec log
  data sets. See OS/390 MVS Diagnosis: Tools and Service Aids for
  information on using EREP.
  .
  *     For OPERLOG, use the IEAMDBLG program in SYS1.SAMPLIB with
  the DELETE parameter.
  .
  Use RETPD / AUTODELETE logstream options when new data set
  acquired during offload processing.  If you specify the RETPD an
  AUTODELETE parameters to set a retention period and automatic
  deletion policy for a log stream the data set becomes eligable
  for deletion once the retention period has expired for all the
  log data in the log data set.  System logger deletes the data on
  a log data set basis when the log data set is full, is no longer
  in use as the current log data set for the log stream, and is no
  allocated to be any system in the plex the next time a data set
  switch occurs.
  .
  *     For the CICS log manager, CICS automatically deletes data
  in a CICS system log. For CICS general logs, use the RETPD and
  AUTODELETE parameters in the log stream definition to manage the
  amount of log data automatically.  You can also use CICS/VR to
  archive or delete CICS log data.
  .
  Note that using DFHSM to migrate log stream data sets to tape
  does not solve the data set directory full condition because the
  migrated data sets will still count toward the data set director
  entry limit. Deleting DASD log stream data sets (using a TSO/E
  DELETE command, for example) also does not solve the data set
  directory full condition.
  .
  Deleting Log Data Sets
  .
  To delete a log data set use one of the methods for making the
  offload data set eligable for deletion as described in 9.5.1 and
  wait or cause a logger offload and data set switch to occur, or
  cause the application to disconnect from the logstream.
  .
  The deletion of the log stream definition from the LOGR policy
  will cause the deletion of all the offload data sets associated
  with the deleted log stream (see "Deleting Log Streams From the
  LOGR Policy" in topic 9.4.10 and see "When Is My Log Data or Log
  Data Set Physically Deleted?" in topic 9.5.3).
  .
  Note that IBM does not recommend other methods for deleting data
  sets, such as the TSO/E DELETE command, because system logger
  cannot perform any clean-up and the deleted data sets will still
  count toward the data set directory limit.
  .
  Finding and Deleting Orphaned Log Data Sets
  .
  When you delete a log data set, allocation errors may result in
  an "orphaned" log data set -- a log data set that should have
  been deleted but was not. When a log data set is orphaned, syste
  logger issues message IXG252I. System logger frees up the data
  set's entry in the directory extent in this case, but the data
  set still consumes storage. If an allocation error occurs when
  you delete a log stream or when system logger is deleting a log
  data set, you will need to manually delete the resulting
  unnecessary log data sets. The orphaned data sets should be
  deleted using the IDCAMS delete command.  Note that when you
  delete a logstream by deleting it from the LOGR policy, system
  logger deletes all the log data sets associated with the log
  stream that have entries in the logger directory.  If a dataset
  was orphaned or simply matches the log stream naming convention
  but is not in the logger directory, then logger will NOT
  attempt to delete the dataset when the log stream is deleted.
  .
  If you suspect you may have possible orphaned data sets that may
  have previously been associated with a logstream, use  LIST
  LOGSTREAM NAME(log_stream_name) DETAIL(YES) on the  IXCMIAPU
  utility  for DATA TYPE(LOGR).
  .
  Refer to the section in the output report entitled "POSSIBLE
  ORPHANED LOG STREAM DATA SETS:" to find any data sets that match
  the logstream naming convention but are not part of Logger's
  dataset directory for the logstream. For information on the LIST
  parameter of IXCMIAPU, see  Appendix B, "Administrative Data
  Utility" in topic B.0.
  Searchable Text:  5752SCLOG
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels