When is it safe to reply RESET to the TSS9123A error?
Is it safe to reply RESET if the security file is on a new lpar?
Release : 16.0
Component : CA Top Secret for z/OS
"If system IS NOT OPERATIONAL it is safe to reply 'RESET', OTHERWISE REPLY 'WAIT'.
WARNING: INDISCRIMINATELY REPLYING 'RESET' MAY CAUSE CORRUPTION OF THE xxxxxxxxxxxx SECURITY FILE"
If the SECFILE was copied while it was live and enqueued (and it is almost always enqueued while live), then any active enqueue will be copied along with it and the TSS9123A error will result. The SECFILE should not be copied while it is active because the SECFILE is constantly being enqueued/dequeued.
If the new system on the new lpar is down - and the copied secfile on it is not being written to or enqueued - then yes it is safe to reply RESET to the TSS9123A error code.
Replying RESET to the TSS0123A error will remove the enqueue record that was copied from the active security file.
If you do RESET while the other system is writing to the security file, it could result in a corrupted security file.