CA Top Secret TSS Messages › TSS9101W to TSS9198I › TSS9123A

TSS9123A

MAY CAUSE CORRUPTION OF THE xxxxxxxxxxxx SECURITY FILE

Reason:

CA Top Secret has not been able to obtain the Security File lock or an enqueue. The resource has been held on the system for nn minutes. If BLP appears after the “system”, the initial system is in the process of backing up the security file.

If the system holding the resource has gone down, replying RESET recovers the Security File lock.

Replying WAIT retries the request a set number of times. If none of the retries are successful, TSS9123A is reissued.

If the message is issued for the security file lock and the security file lock record is being maintained in the coupling facility, then the system will be identified as $CFLOCK$ in the message. The number of minutes the lock has been held will be unreliable.

Action:

Reply with desired option: RESET or WAIT. The correct response to the message is WAIT unless all live systems sharing the Security File have been issued the TSS9123A message as well. When all systems have the message, respond RESET on the first system and WAIT on the remaining systems.

If no response is received after one minute has elapsed, CA Top Secret will automatically reply to this message with WAIT.

If you set up an automated reply to message TSS9123A:

• Do not automate a reply of RESET. This will cause security file corruption.
• Ensure that an automated WAIT response is not issued under the same subtask that issued the WTOR for the message. This may cause a system outage. For example, the CA-OPS/MVS AOF facility allows for inline responses and is not recommended. Generate the reply via the OPSCMD POI command processor. This allows the command to be issued from an OPS/MVS OSF server and not the subtask that issued the message.