Title: SMS CONSTRUCTS IN HISTORY FILE DD STATEMENT ARE IGNORED
Product: JARSSM
Release: 12.7
Opsys: OS
Solution #: 16
https://support.ca.com/irj/portal/SolutionCDNResults?aparNo=RO67886&actionID=4
Description:
**** HIGH IMPACT NOTIFICATION ALERT ****
***NOTE*** This PTF corrects an ERROR hold on CASFC70
PROBLEM DESCRIPTION:
JARSSM 320
SMS constructs (STORCLAS, MGMTCLAS, and DATACLAS) that are coded in
a HISTORY file DD statement for a DUMP are ignored.
SYMPTOMS:
History files do not get allocated with the requested SMS
attributes.
IMPACT:
The impact depends on what the SMS storage, management, and data
classes are used for, and what SMS constructs are the defaults.
This problem could result in data loss if the history files get
assigned by default to a class that automatically gets deleted
after a certain number of days.
CIRCUMVENTION:
Code the desired SMS constructs in the PSTORC/ASTORC,
PMGMTC/AMGMTC, and PDATAC/ADATAC OPTIONS, DUMPOPTIONS, or
STREAMOPTIONS.
PRODUCT(S) AFFECTED:
CA SMF Director Release 12.7
=============================================================================
PROBLEM DESCRIPTION:
JARSSM 318
When DSNTYPE=LARGE is coded in an output history file DD statement
in DUMP JCL, but the PDSNLARGE / ADSNLARGE option for the
configuration is not set to YES, CA SMF Director allocates the
history file without the large format attribute.
SYMPTOMS:
If the history file requires more than 65,535 tracks on a single
volume, this can result in a SB37 ABEND.
IMPACT:
The DUMP may need to be rerun.
CIRCUMVENTION:
Code the PDSNLARGE / ADSNLARGE option in the OPTIONS, DUMPOPTIONS,
or STREAMOPTIONS statement, and recompile the configuration.
PRODUCT(S) AFFECTED:
CA SMF Director Release 12.7