KD2_PFnn_HIS_SEQ_TYP
Storage mechanism
- Description
-
If you specified VSAMSEQ, VSAMSEQTHVSAM, SEQTHVSAM you can choose one of the following 3 alternatives to store trace data in sequential files:
- Static sequential S
- You may specify 2 to 7 sequential datasets for trace data collection. When the first dataset is full the Near-Term History Data Collector switches to the next available dataset. When the last available dataset in the sequence is full, the Near-Term History Data Collector switches to the first dataset in the sequence again and overwrites the data in the first dataset. Each time the Near-Term History Data Collector switches to a full sequential dataset to overwrite it, you can archive its content to additional sequential datasets.
- Dynamic sequential D
- The Near-Term History Data Collector always allocates a new dataset when the currently used dataset becomes full. As a result, the collected data is not overwritten.
- GDG G
- In this case a Generation Data Group GDG is used. The mechanism is similar to the one described for the storage type Static sequential. When all datasets are full the Near-Term History Data Collector overwrites the trace data in the first dataset. However, in a GDG, the z/OS, not the Near-Term History Data Collector, switches between the different datasets generations. For this alternative archiving is not supported.
- Required or optional
- Optional (Required in case KD2_PF_HIS_START is set to C,Y and KD2_PF_HIS_STORE is set to VSAMSEQ,VSAMSEQTHVSAM,SEQTHVSAM)
- Default value
- S
- Permissible values
- S, D, G
- Location where the parameter value is stored
- This value is not stored in a configuration member.
- PARMGEN name
- KD2_PFnn_HIS_SEQ_TYP
- PARMGEN classification
- NTH