I cannot see any way to select by task number for the PMAM batch
reports. You can select by task code or task type, but not task number.
Does anyone know of a way to do this?
Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email:
Kay.Rozeboom@Iowa.Gov
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP
Normal
Normal
Performance Monitor question
"I cannot see any way to select by task number for the PMAM batch
reports. You can select by task code or task type, but not task number.
Does anyone know of a way to do this?
Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email:
Kay.Rozeboom@Iowa.Gov
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP
Normal
Normal
Re: Deadlocks
"Hello Joe:
The answer is no a task does not abend immediately, IDMS allows a dead lock
to occur and the tasks will wait on each other. Then the Dead Lock detection
mechanism (RHDCDEAD) wakes up at the sysgen defined Dead Lock detection
Interval looks at all dead locked takes and determines who to Kill (Dead Lock
Victims in the DMCT DIS STAT SYS display).
You can also issue a DCMT command to display and alter the dead lock
detection interval.
Starting with release 15.0 there are some new SYSIDMS Parameters, such as
ABEND_ON_DEADLOCK and DEADLOCK_DETAILS=ON, these were very helpful in debugging
my release 16.0 dead lock problems.
I use the IBM Book Manager Library for Windows and I have not had any
problems with it?
Bill Allen
In a message dated 10/21/2005 2:57:32 P.M. Eastern Daylight Time,
Joe.Lupico@AIG.COM writes:
Hi All,
I have two questions....
1. When a task encounters a deadlock condition, does it ABEND immediately or
does it use one of the system timers?
2. Is there a place which explains how to read the IDMS documentation CDs
(I'm trying 15.0 right now)? I am trying Library Reader, Softcopy Reader
and Adobe and none of them are working real well. I know I had it figured
out at one time, but that knowledge has escaped through the various holes in
my head.
Thanks.
Joe Lupico
IDMS System Support
""Our World is a Happy World""
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP
Normal
Normal
Re: Deadlocks
"Joe,
To add to Chris and Bill's responses, you should know that the task does not
have to ABEND on a deadlock. It is true that once the deadlock detection
interval expires, the deadlock will be detected and one of the run units
will be ‘victimized’. The victim run unit is terminated but not the user’s
task. All the victim’s resources are released. The task that owns that run
unit is notified via IDMS-STATUS. At that point the RU is dead and no
successful calls can be made to it. However the task is free to continue.
Many programmers end the program unpleasantly when the deadlock status is
returned so it looks like IDMS forced the ABEND. This is neither necessary
nor desirable. I believe that it is better to reacquire/reinitialize
resources and retry the transaction from the top rather than blow up in the
user’s face. You can’t deadlock again on the same resource with the same
partner because the other task was allowed to acquire its desired resource
and has likely moved on. If it is still hanging around, like a batch job,
you will wait, but not deadlock. This is due to the fact that when you get
back to the point where you attempt to reacquire the resource you once had,
and that the other task wanted, he will have it and you will have to wait
for it.
When you successfully retry deadlocks this way, the end user doesn’t see the
deadlock though their response time will be higher; twice do the work twice
plus, on average, ½ the deadlock detection interval. It isn’t pretty but
it’s better than crashing.
Think of it this way…ABEND ½ of 1% of your transaction and your application
may become the butt of jokes at the water cooler. Retry them quietly and no
one will notice; which is a good thing.
Obviously it is best to eliminate deadlocks rather than deal with them.
YES, THEY CAN BE ELIMINATED. There are many techniques available but this
is not the place to explore them all. With that said, one of the best
things you can do is to acquire hot spot resources in the same order in
every program.
HAVE AN ABEND FREE DAY SOON!
Tom
PS: I solved my IBM Reader issues by using the PDF documentation.