A history file may be associated with a MAN file, a logstream, or a substream. This product assigns a unique DD name to each history file for a given SID. The DD name for a history file that is associated with a MAN file or logstream is HISTORY1 (primary pool) or HISTORY2 (alternate pool). The DD name for a history file that is associated with a substream is HISTcc1 (primary) or HISTcc2 (alternate), where "cc" is the stream code for the substream. The stream code can be found in a listing that is generated by the LISTC command, which is designated by "ID: cc" and located just to the right of the STREAMNAME.
When using SMS-managed DASD for history files, the OPTIONS, DUMPOPTIONS, and STREAMOPTIONS operands that are associated with SMS construct definitions can influence how this products history files are allocated on SMS-managed volumes. Issues can arise with DASD history file allocations, depending on how SMS is set up at your data center.
For DASD history allocations with the DYNAM option in effect, CA SMF Director preallocates a temporary history file dataset. The parameters for this allocation come from the OPTIONS / DUMPOPTIONS / STREAMOPTIONS settings and from parameters that may be coded on the //HISTORYn or //HISTccn DD statement. The amount of DASD space that is allocated is taken from the SPACE parameter.
When SMS constructs are coded in the DD statement, these codes override any PSTORC, PMGMTC, PDATAC, ASTORC, AMGMTC, and ADATAC operands that were coded in the OPTIONS / DUMPOPTIONS / STREAMOPTIONS statements. Likewise, when DSNTYPE=LARGE is coded on the history file DD statement, the history file is allocated with the large format attribute, even when the PDSNLARGE / ADSNLARGE parameter was not coded in the options.
Important! The ACS routine trumps any SMS specifications in JCL or elsewhere. Based on the ACS routine, SMS might not allow an allocation using the classes that are specified in the PSTORC/ASTORC, PDATAC/ADATAC, and PMGMTC/AMGMTC operands or in SMS construct parameters that are coded in the history file DD statement. This can result in the allocation of the history file with attributes other than the desired attributes. It can also result in an allocation error, causing the DUMP process to terminate.
Non-SMS history file allocation can be used:
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|