Modifying a trace
The following table describes several modifiable options that you might want to change after starting a trace where logging is already active:
Panel option name/keyword | Possible use |
|---|---|
Overwrite logs/TRREUSE | Allows you to change from Y to N to prevent overlaying data that has not been archived. However, new data will be lost when available data sets are full. Changing from N to Y assures that a data set is always available for new trace data, but old trace data may be overlaid before it can be archived. |
log switch time/TRSWTIME | Allows you to change the time when a log switch occurs. For example, you might want to add a data set by increasing TRNUMDS and then force a switch to free the current data set. |
Archive STC/TRARCSTC | Allows you to change the name of the archive job; for example, to archive to a different set of archive data sets. |
number of logs/TRNUMDS | Allows you to increase or decrease the number of log data sets. If TRNUMDS is increased and TRDISP=NEW, the additional data sets are allocated before the modify request is considered successful. |
volumes/TRVOLS,primary CYLS/TRCYL,SMS Storage Class/TRSMSSCL,SMS Management Class/TRSMSMCL,orSMS Data Class/TRSMSDCL | If TRDISP=NEW and you are adding log data sets by increasing TRNUMDS, you may want to change the allocation parameters for these new data sets to cause them to be allocated on different volumes or to increase their size. |
If the number of logs is increased by using the Modify command, the additional log data sets must be successfully allocated before the request is considered successful. If the log date sets cannot all be allocated, the request fails and any additional data sets that were dynamically allocated (DISP=NEW) are deleted. Logging continues with the original number of log data sets.