IDMS lock problem

Thread View: bit.listserv.idms-l

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Matthijs Fri, 11 Jul 2003 13:20

#51

Author: Matthijs
Date: Fri, 11 Jul 2003 13:20

35 lines
2133 bytes

During the day a rollback was performed (by mistake) on an online
(update) IDMS system.

At 21.15 we put IDMS in retrieval mode, to check everything went fine
we ran a lock-check on the areas. The job came back with CC=0000,
meaning no areas had locks on them.

At 04.00 the next morning IDMS was shut down and restarted again,
bypassing the warm start.

At 07.00 We now ran the same lock-check job, and it came back showing
locks: 18 areas had locks on them.

It was only now that we went and checked the first lock-check job
(from 21.15) and noticed that while NO areas had locks on them, 18
areas were still in "Upd" mode when shutting down and gave an "Error
Closing AREA".


We tried to put IDMS in update, but this didn't work, bescause of the
locks. After varying the areas in retrieval manually we WERE able to
get all areas in update.



My question: 
1. Why did I get the "Error Closing AREA" while there were NO locks on
the areas? What's the meaning of this?
2. Does IDMS (even after a cold start) keep track of the (upd/Ret)
status of areas and automatically put a lock on the areas when
performing a cold start?
3. Why was I able to get the areas in update AFTER putting them in
retrieval mode? I always thought that IDMS starts in retrieval mode
after a cold start? Is this auto-lock setting some kind of
"protection"?

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads