9545E

9545E MASTER SUBSYSTEM IN USE, SSID = ssid

9545E                          JOB  = jobname

9545E                          PROD = productname

9545E                          PLEX = sysplexname

9545E                          DSN  = sync.data

Written to:

SYSLOG, JESMSGLG.

Explanation:

A second master (STC or batch job) has tried to sign on to a database which is already in use. The message provides the following information about the subsystem that is using the database:

• Subsystem ID ssid
• Jobname
• Product name of the master that has control over the database
• Name of the sysplex
• Dataset name of the SYNC file

This message may also be issued if the started task or job that had control over the database last was terminated improperly.

System Action:

The second master (STC or batch job) is terminated.

Operator Response:

None if the STC or batch job jobname is active. In this case, the active STC or batch job has control over the product database, and it is normal that other STCs or batch jobs are prevented from gaining control.

If the STC or batch job jobname has terminated improperly, the obsolete entry in the SYNC file prevents your STC or batch job from taking control over the database. Do one of the following:

• Restarting the STC or rerunning the batch job

  An existing entry in the SYNC file prevents other subsystems from taking control over the database, but it does not prevent the same subsystem from regaining control. Subsystem-related information in the SYNC file is checked during restart. The entry in the SYNC file will be removed when the STC is stopped or the batch job terminates properly.

  If an STC or batch job has terminated abnormally, another subsystem from the same sysplex (same GRS complex) is allowed to gain control over the database. A GRS enqueue safeguards against several subsystems taking control of the same database.

• Running BnnCLSYN

  You can run job BnnCLSYN to clean the SYNC file (see "BnnCLSYN: Cleaning the SYNC file" in BSA Installation and System Guide).