Reason:
In CA Top Secret r5.3 and above, if CA Top Secret starts before JES is fully initialized, the $$$LOG$$ file will be suppressed until such time as JES becomes available, and entries which might have been written to the file will be ignored. When JES does become available, the file will be allocated according to the SYSOUT control option. The associated message $HASP250 TSS53 PURGED - (JOB KEY WAS BBA71465) may be ignored, when TSSMNGR4 attempts to spin off a non-existent old version of the log.
Action:
If you intended to start CA Top Secret before JES, the task is operating as designed. If you had intended to start after JES was completed, remove the SUB=MSTR operand from the operator command used to start the product.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|