ca.portal.admin

Bizarre index problem

Discussion created by ca.portal.admin on Apr 20, 2009
Hi everyone,

I'm having a weird problem that I'm hoping someone will be able
to help me with. Here's the scenariTo: a developer is getting
an 1143 on an ERASE record-name ALL MEMBERS. The 1143 abend
indicates that there is a problem with the index. So, I ran a
DBAN against the test database, and get a whole bunch of
Unmatched DOWN pointer found in SR8. Since the index is MA, I
rebuilt the index, and reran the DBAN, and am still
getting Unmatched DOWN pointers, although not as many. I'm using the
same ssc to run the MAINTAIN INDEX and to run the DBAN, coming
out of the same library.

I would think that the REBUILD INDEX set-name FROM ALLROWS
would solve the problem, but I'm still getting errors.

Any tips in resolving this will be appreciated!

TIA,
Laura Rochon
Ajilon
This e-mail may contain confidential or privileged information. If
you think you have received this e-mail in error, please advise the
sender by reply e-mail and then delete this e-mail immediately.
Thank you. Aetna
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Bizarre index problem
"Did you rebuild from members? Prior to that you format the index area,=0D=
=0Aif it's system owned in it's own area/file=2E=0D=0A=0D=0ALutz Petzold=0D=
=0ATDM UDB/IDMS Support=0D=0A401-782-2265=0D=0APage 860 366 0865 or Telaler=
t=0D=0A =0D=0A =0D=0A=0D=0A-----Original Message-----=0D=0AFrom: IDMS Publi=
c Discussion Forum =0D=0A[mailTo:IDMS-L@LISTSERV=2EIUASSN=2ECOM] On Behalf =
Of Laura Rochon=0D=0ASent: Monday, April 20, 2009 3:04 PM=0D=0ATo: IDMS-L@L=
ISTSERV=2EIUASSN=2ECOM=0D=0ASubject: Bizarre index problem=0D=0A=0D=0AHi ev=
eryone,=0D=0A=0D=0AI'm having a weird problem that I'm hoping someone will =
be able =0D=0Ato help me with=2E Here's the scenariTo: a developer is gett=
ing =0D=0Aan 1143 on an ERASE record-name ALL MEMBERS=2E The 1143 abend =
=0D=0Aindicates that there is a problem with the index=2E So, I ran a =0D=
=0ADBAN against the test database, and get a whole bunch of =0D=0AUnmatched=
DOWN pointer found in SR8=2E Since the index is MA, I =0D=0Arebuilt the i=
ndex, and reran the DBAN, and am still=0D=0Agetting Unmatched DOWN pointers=
, although not as many=2E I'm using the=0D=0Asame ssc to run the MAINTAI=
N INDEX and to run the DBAN, coming =0D=0Aout of the same library=2E=0D=0A=
=0D=0AI would think that the REBUILD INDEX set-name FROM ALLROWS =0D=0Awoul=
d solve the problem, but I'm still getting errors=2E=0D=0A=0D=0AAny tips in=
resolving this will be appreciated!=0D=0A=0D=0ATIA,=0D=0ALaura Rochon=0D=
=0AAjilon=0D=0AThis e-mail may contain confidential or privileged informati=
on=2E If=0Ayou think you have received this e-mail in error, please advise =
the=0Asender by reply e-mail and then delete this e-mail immediately=2E=0AT=
hank you=2E Aetna
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Bizarre index problem
"We always do a DELETE of the index in a separate step the a REBUILD FROM
ALL in the next step. Maybe that will work.

Tim Gortner
Sogeti USA


----- Original message -----
From: ""Laura Rochon"" <l.rochon@VIDEOTRON.CA>
To: IDMS-L@LISTSERV.IUASSN.COM
Date: Mon, 20 Apr 2009 15:04:26 -0400
Subject: Bizarre index problem

Hi everyone,

I'm having a weird problem that I'm hoping someone will be able to help
me with. Here's the scenariTo: a developer is getting an 1143 on an
ERASE record-name ALL MEMBERS. The 1143 abend indicates that there is a
problem with the index. So, I ran a DBAN against the test database, and
get a whole bunch of Unmatched DOWN pointer found in SR8. Since the
index is MA, I rebuilt the index, and reran the DBAN, and am still
getting Unmatched DOWN pointers, although not as many. I'm using the
same ssc to run the MAINTAIN INDEX and to run the DBAN, coming out of
the same library.

I would think that the REBUILD INDEX set-name FROM ALLROWS would solve
the problem, but I'm still getting errors.

Any tips in resolving this will be appreciated!

TIA,
Laura Rochon
Ajilon
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Bizarre index problem
"We always do a DELETE of the index in a separate step the a REBUILD FROM
ALL in the next step. Maybe that will work.

Tim Gortner
Sogeti USA


----- Original message -----
From: ""Laura Rochon"" <l.rochon@VIDEOTRON.CA>
To: IDMS-L@LISTSERV.IUASSN.COM
Date: Mon, 20 Apr 2009 15:04:26 -0400
Subject: Bizarre index problem

Hi everyone,

I'm having a weird problem that I'm hoping someone will be able to help
me with. Here's the scenariTo: a developer is getting an 1143 on an
ERASE record-name ALL MEMBERS. The 1143 abend indicates that there is a
problem with the index. So, I ran a DBAN against the test database, and
get a whole bunch of Unmatched DOWN pointer found in SR8. Since the
index is MA, I rebuilt the index, and reran the DBAN, and am still
getting Unmatched DOWN pointers, although not as many. I'm using the
same ssc to run the MAINTAIN INDEX and to run the DBAN, coming out of
the same library.

I would think that the REBUILD INDEX set-name FROM ALLROWS would solve
the problem, but I'm still getting errors.

Any tips in resolving this will be appreciated!

TIA,
Laura Rochon
Ajilon
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Bizarre index problem
"Hi everyone,

I'm having a weird problem that I'm hoping someone will be able to help
me with. Here's the scenariTo: a developer is getting an 1143 on an
ERASE record-name ALL MEMBERS. The 1143 abend indicates that there is a
problem with the index. So, I ran a DBAN against the test database, and
get a whole bunch of Unmatched DOWN pointer found in SR8. Since the
index is MA, I rebuilt the index, and reran the DBAN, and am still
getting Unmatched DOWN pointers, although not as many. I'm using the
same ssc to run the MAINTAIN INDEX and to run the DBAN, coming out of
the same library.

I would think that the REBUILD INDEX set-name FROM ALLROWS would solve
the problem, but I'm still getting errors.

Any tips in resolving this will be appreciated!

TIA,
Laura Rochon
Ajilon
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Bizarre index problem
"Hi everyone,

I'm having a weird problem that I'm hoping someone will be able to help
me with. Here's the scenariTo: a developer is getting an 1143 on an
ERASE record-name ALL MEMBERS. The 1143 abend indicates that there is a
problem with the index. So, I ran a DBAN against the test database, and
get a whole bunch of Unmatched DOWN pointer found in SR8. Since the
index is MA, I rebuilt the index, and reran the DBAN, and am still
getting Unmatched DOWN pointers, although not as many. I'm using the
same ssc to run the MAINTAIN INDEX and to run the DBAN, coming out of
the same library.

I would think that the REBUILD INDEX set-name FROM ALLROWS would solve
the problem, but I'm still getting errors.

Any tips in resolving this will be appreciated!

TIA,
Laura Rochon
Ajilon
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Question about Terminals and Task priority
"This is a multipart message in MIME format.
--=_related 0054A3AE8625759F_=
Content-Type: multipart/alternative; boundary=""=_alternative 0054A3AF8625759F_=""


--=_alternative 0054A3AF8625759F_=
Content-Type: text/plain; charset=""US-ASCII""

We are currently running R16 sp7. There are some questions about
deadlocks.
While under R15.0 there were maybe 2 deadlocks on a specific task (WH06)
every 2-3 months, now the deadlocks are more frequent (once a week or
so).
Nothing in the sysgen has changed.
The tasks that are deadlocking are T1 a CICS transaction (WH06) and T2 a
batch program.
It is my understanding that they are both treated as ERUS and get a ""LD""
terminal allocated.

Question 1 where are the ""LD"" terminals defined?

The task code for T1 is WH06 and is not defined to IDMS it is a CICS task
so the CICS task is getting a priority of 5.

The batch job also gets a ""LD"" terminal allocated and also has the
priority of 5.

For some reason the program associated with T1 (MFCT002C) has a task code
defined in the CV with a priority of 100. As far as I can tell the task
is never getting executed.
The program MFCT002c is running in the CICS region making a DB request to
the CV and getting a ""LD"" terminal allocated with a priority of 5.

Question 2 How can we get the batch and CICS programs separated to give
the CICS tasks a higher priority that the batch jobs?

The main problem/opportunity that the user/annalist wants is that incase
of a deadlock the batch job gets selected as the victim and the on-line
CICS task continues....






George H Lewandowski
Database Administrator
GIS
7x24 Operations
GA-25, J46-2E

Work (847) 938-5526
Pager (800) 209-1305
george.lewandowski@abbott.com




This communication may contain information that is proprietary,
confidential, or exempt from disclosure. If you are not the intended
recipient, please note that any other dissemination, distribution, use or
copying of this communication is strictly prohibited. Anyone who receives
this message in error should notify the sender immediately by telephone or
by return e-mail and delete it from his or her computer.

--=_alternative 0054A3AF8625759F_=
Content-Type: text/html; charset=""US-ASCII""


<br><font size=2 face=""sans-serif"">We are currently running R16 sp7.  
There are some questions about deadlocks.  </font>
<br><font size=2 face=""sans-serif"">While under R15.0 there were maybe 2
deadlocks on a specific task (WH06) every 2-3 months,  now the deadlocks
are more frequent (once a week or so). </font>
<br><font size=2 face=""sans-serif"">Nothing in the sysgen has changed.</font>
<br><font size=2 face=""sans-serif"">The tasks that are deadlocking are T1
a CICS transaction (WH06) and T2 a batch program.</font>
<br><font size=2 face=""sans-serif"">It is my understanding that they are
both treated as ERUS and get a &quot;LD&quot; terminal allocated.</font>
<br>
<br><font size=2 face=""sans-serif"">Question 1 where are the &quot;LD&quot;
terminals defined?</font>
<br>
<br><font size=2 face=""sans-serif"">The task code for T1 is WH06 and is
not defined to IDMS it is a CICS task so the CICS task is getting a priority
of 5.</font>
<br>
<br><font size=2 face=""sans-serif"">The batch job also gets a &quot;LD&quot;
terminal allocated and also has the priority of 5.</font>
<br>
<br><font size=2 face=""sans-serif"">For some reason the program associated
with T1 (MFCT002C) has a task code defined in the CV with a priority of
100.  As far as I can tell the task is never getting executed.</font>
<br><font size=2 face=""sans-serif"">The program MFCT002c is running in the
CICS region making a DB request to the CV and getting a &quot;LD&quot;
terminal allocated with a priority of 5.</font>
<br>
<br><font size=2 face=""sans-serif"">Question 2  How can we get the
batch and CICS programs separated to give the CICS tasks a higher priority
that the batch jobs?</font>
<br>
<br><font size=2 face=""sans-serif"">The main problem/opportunity that the
user/annalist wants is that incase of a deadlock the batch job gets selected
as the victim and the on-line CICS task continues....</font>
<br>
<br>
<br><font size=2 face=""sans-serif""><br>
</font><font size=3><br>
</font>
<table>
<tr>
<td colspan=4>
<div align=center>
<hr noshade></div>
<tr valign=top>
<td bgcolor=white><font size=1 face=""Arial""><b>George H Lewandowski</b></font>
<br><font size=1 face=""Arial"">Database Administrator<br>
GIS <br>
7x24 Operations<br>
GA-25, J46-2E</font>
<td bgcolor=white>
<td bgcolor=white><font size=1 face=""Arial"">Work (847) 938-5526<br>
Pager (800) 209-1305</font><font size=1 color=blue face=""Arial""><u><br>
</u></font><font size=1 color=blue face=""Arial""><u>george.lewandowski@abbott.com</u></font>
<td bgcolor=white>
<div align=right><font size=1 face=""Arial""><br>
</font><img src=cid:_1_03B39BA403B397BC0054A3AC8625759F><font size=1 face=""Arial""><br>
</font></div>
<tr>
<td colspan=4>
<div align=center>
<hr noshade></div>
<tr>
<td colspan=4><font size=1 color=#808080 face=""Arial"">This communication
may contain information that is proprietary, confidential, or exempt from
disclosure. If you are not the intended recipient, please note that any
other dissemination, distribution, use or copying of this communication
is strictly prohibited. Anyone who receives this message in error should
notify the sender immediately by telephone or by return e-mail and delete
it from his or her computer.</font></table>
<br>
--=_alternative 0054A3AF8625759F_=--
--=_related 0054A3AE8625759F_=
Content-Type: image/gif
Content-ID: <_1_03B39BA403B397BC0054A3AC8625759F>
Content-Transfer-Encoding: base64

R0lGODlhcAAdAMQAAAAAANva2v8AAISEhE5OTv9+fiMjI////7W1tf/MzP9PT3BwcObm5pmZmUFB
Qf/W1szMzBMTE2ZmZvf39/+MjP8YGKioqMHBwTMzM3t7e1taWo+Pj/+kpAgICO/v7/9bWyH5BAUU
AAcALAAAAABwAB0AAAX/oCCOZGmeY0UdbOu+hyVbjAs1MwJfuHzBwOAkUHsFAi6Ucmn6TILGSGea
cWUA0w4BpsFOJdAwy2LQvCAGg6fFbDM/YtYVQDe4LpkI3QFDLDp0ZnFBXXwuDVhrLG6MKCtiBnSS
Py4Oe0GRAIKDLx56hi0YABFPi42nKWIQWBKSCy+WAFsIAzQtmWAWtYotEwgbtUW+ogAYEMcXXVgX
EDUPz9DR0tPUDwkKJWJXDgyAAAalLLEOBJIRFiyZDsSjlDGZdB2vq5L19nRgnPoHD9lhkQMOxALg
TqAkDA3YIYFHoEGmCGsQSGpwAZeHDJkMZNiYgZi8DDr2cepHIswFLDUs/0jKJy7eGnoAqmQcM/FA
pi0xJhmUZYVOBJEiSY4IswCLBg3lfIaLhYHFBD0A+NxkEWBlVTpVDsB8Nc5F0VG8XFhLQLas2bNn
wwkV8e+epJA7QWVqmklQt0An6QQ8cFVT3AMMIByYA9EDBCQHOFRAVSJBi7UCoORFcAzCAEmbuh6Y
MNdmIBZ3NcHc2xdM1ysBLo86ILEpB8YmHLOADKVV017eSLX8Btqbmc5aJQ2Y4C1fXgAN/qImfOCk
gwSLYZOQzc/fmQaAMFgQDMECVE06BjaY8BWADngIJigDIPirgRqtvj1JioGBJQ8b4qXWFF36COq0
wTAQHVuwU48HomiBBf9mLOgRgSXeAPDKZkl1kJFgOdXDRwARfhNACRUUIOKIJJZYIi8BvmDBAiyy
iE4DLbaYwQQwJrcBBgY4sEELAyyAzgA4OoCOCxZokIYDA4RlgQMGYLCAIhcQkIYGSDQGFAwpXqnl
loOU8ACXs1kH5phkHuDlmFmWqeaVZ4KZ5ppwctIml2/GaScUc25Z5518JkHCl26KGYcHRxSxZgBh
wRBOL4ix8SeaghK5CQsaDNDjXoMOaZIEhsLAQFYHeGDjcH6OoEAC1aQqzTWRtpCBBI2S1wKsE9TA
QKMMrIFYDUO0gGgvGwz562ZFMMBSrR4sIFivB/Tn3xIVBMEDBDs6JcH9MX40oAECCGQwQHKVSjBA
BhtMsMGnDQy3wQYZYGisBPhtsEAAUQ7JwISANQABARtAkEEDG3hAwbNtPAKDBPrixAIBA6zLQAM6
SPCEsmA0kFwGnwZwrWEE8LAJAswElNovLdxb8ivlLrBBMjt+QLAScADBAAEybOsUvgdQdMCEIAUE
8WCfAqaLH5W1YMEFPIQKkqYmg1bFAMZSdthmLr9cghNBBEtVPrK2oHOwFyRZxc8YD0CtvwG0K4PR
CCR7wQbcaurBttxadgDUv5zdAgXOPqtCGBbwYkEpcGlVxAIarPHD1BdM8MMGGggWgAYLhHOEVhrs
eHkL8rJ4THNrQAOuQwgAOw==
--=_related 0054A3AE8625759F_=--
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Question about Terminals and Task priority
"
We are currently running R16 sp7. There are some questions about deadlocks.
While under R15.0 there were maybe 2 deadlocks on a specific task (WH06) every 2-3 months, now the deadlocks are more frequent (once a week or so).
Nothing in the sysgen has changed.
The tasks that are deadlocking are T1 a CICS transaction (WH06) and T2 a batch program.
It is my understanding that they are both treated as ERUS and get a ""LD"" terminal allocated.

Question 1 where are the ""LD"" terminals defined?

The task code for T1 is WH06 and is not defined to IDMS it is a CICS task so the CICS task is getting a priority of 5.

The batch job also gets a ""LD"" terminal allocated and also has the priority of 5.

For some reason the program associated with T1 (MFCT002C) has a task code defined in the CV with a priority of 100. As far as I can tell the task is never getting executed.
The program MFCT002c is running in the CICS region making a DB request to the CV and getting a ""LD"" terminal allocated with a priority of 5.

Question 2 How can we get the batch and CICS programs separated to give the CICS tasks a higher priority that the batch jobs?

The main problem/opportunity that the user/annalist wants is that incase of a deadlock the batch job gets selected as the victim and the on-line CICS task continues....





________________________________

George H Lewandowski
Database Administrator
GIS
7x24 Operations
GA-25, J46-2E

Work (847) 938-5526
Pager (800) 209-1305
george.lewandowski@abbott.com <mailTo:george.lewandowski@abbott.com>




________________________________

This communication may contain information that is proprietary, confidential, or exempt from disclosure. If you are not the intended recipient, please note that any other dissemination, distribution, use or copying of this communication is strictly prohibited. Anyone who receives this message in error should notify the sender immediately by telephone or by return e-mail and delete it from his or her computer.

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Question about Terminals and Task priority
"This is a multi-part message in MIME format.


------_=_NextPart_001_01C9C298.7CBF4CA4
Content-Type: text/plain;
charset=""US-ASCII""
Content-Transfer-Encoding: quoted-printable

I beleive that LD's are not sysgenned=2E They are defined dynamically,=0D=
=0Aand initially I think it's equal to the number of ERUS in the sysgen=2E=
=0D=0A =0D=0AI've never found priorities to fix deadlocks anyway=2E If yo=
u can=0D=0Aeliminate waits, then that will fix deadlocks=2E And, eliminati=
ng OOAK=0D=0Atype records, like a record that everybody accesses to get thr=
ough the=0D=0Adata structure=2E Those are best readied retrieval in a subr=
outine, cause=0D=0Aa second retrieval only run unit to be created without i=
mplicit update=0D=0Alocking, and then returned to the calling program that =
ready's the area=0D=0Ain update if needed=2E=0D=0A =0D=0AThe CICS class max=
task can be a useful tool for certain tasks, that at=0D=0Aare known to bot=
tle neck the data=2E These tasks will wait until a task=0D=0Ais available =
and the single threading is transparent to the user=2E=0D=0A =0D=0A=0D=0ALu=
tz Petzold=0D=0ATDM UDB/IDMS Support=0D=0A401-782-2265=0D=0APage 860 366 08=
65 or Telalert=0D=0A=0D=0A=0D=0A=0D=0A =0D=0A=0D=0A=0D=0A__________________=
______________=0D=0A=0D=0A From: IDMS Public Discussion Forum=0D=0A[mailTo:=
IDMS-L@LISTSERV=2EIUASSN=2ECOM] On Behalf Of George H Lewandowski=0D=0A Sen=
Sent: Tuesday, April 21, 2009 11:24 AM=0D=0A To: IDMS-L@LISTSERV=2EIUASSN=2ECO=
M=0D=0A Subject: Question about Terminals and Task priority=0D=0A =0D=0A =
=0D=0A=0D=0A We are currently running R16 sp7=2E There are some questions=
=0D=0Aabout deadlocks=2E =0D=0A While under R15=2E0 there were maybe 2 de=
adlocks on a specific=0D=0Atask (WH06) every 2-3 months, now the deadlocks=
are more frequent (once=0D=0Aa week or so)=2E =0D=0A Nothing in the sysgen=
has changed=2E =0D=0A The tasks that are deadlocking are T1 a CICS transac=
tion (WH06)=0D=0Aand T2 a batch program=2E =0D=0A It is my understanding th=
at they are both treated as ERUS and=0D=0Aget a ""LD"" terminal allocated=2E =
=0D=0A =0D=0A Question 1 where are the ""LD"" terminals defined? =0D=0A =0D=
=0A The task code for T1 is WH06 and is not defined to IDMS it is a=0D=0ACI=
CS task so the CICS task is getting a priority of 5=2E =0D=0A =0D=0A The ba=
tch job also gets a ""LD"" terminal allocated and also has=0D=0Athe priority =
of 5=2E =0D=0A =0D=0A For some reason the program associated with T1 (MFCT0=
02C) has a=0D=0Atask code defined in the CV with a priority of 100=2E As f=
ar as I can=0D=0Atell the task is never getting executed=2E =0D=0A The prog=
ram MFCT002c is running in the CICS region making a DB=0D=0Arequest to the =
CV and getting a ""LD"" terminal allocated with a priority=0D=0Aof 5=2E =0D=
=0A =0D=0A Question 2 How can we get the batch and CICS programs separated=
=0D=0Ato give the CICS tasks a higher priority that the batch jobs? =0D=0A =
=0D=0A The main problem/opportunity that the user/annalist wants is=0D=0Ath=
at incase of a deadlock the batch job gets selected as the victim and=0D=0A=
the on-line CICS task continues=2E=2E=2E=2E =0D=0A =0D=0A =0D=0A =0D=0A =0D=
=0A =0D=0A________________________________=0D=0A=0D=0AGeorge H Lewandowski =
=0D=0ADatabase Administrator=0D=0AGIS =0D=0A7x24 Operations=0D=0AGA-25, J46=
-2E Work (847) 938-5526=0D=0APager (800) 209-1305=0D=0Ageorge=2Elewandows=
ki@abbott=2Ecom <mailTo:george=2Elewandowski@abbott=2Ecom> =0D=0A=0D=0A =
=0D=0A=0D=0A________________________________=0D=0A=0D=0AThis communication =
may contain information that is proprietary,=0D=0Aconfidential, or exempt f=
rom disclosure=2E If you are not the intended=0D=0Arecipient, please note t=
hat any other dissemination, distribution, use=0D=0Aor copying of this comm=
unication is strictly prohibited=2E Anyone who=0D=0Areceives this message i=
n error should notify the sender immediately by=0D=0Atelephone or by return=
e-mail and delete it from his or her computer=2E=0D=0A=0D=0A=0D=0A=0D=0A=
=0D=0AThis e-mail may contain confidential or privileged information=2E If=
=0Ayou think you have received this e-mail in error, please advise the=0Ase=
nder by reply e-mail and then delete this e-mail immediately=2E=0AThank you=
=2E Aetna
------_=_NextPart_001_01C9C298.7CBF4CA4
Content-Type: image/gif;
name=""ATT4410700.gif""
Content-Transfer-Encoding: base64
Content-ID: <652254215@21042009-07B0>
Content-Description: ATT4410700.gif
Content-Location: ATT4410700.gif

R0lGODlhcAAdAMQAAAAAANva2v8AAISEhE5OTv9+fiMjI////7W1tf/MzP9PT3BwcObm5pmZmUFB
Qf/W1szMzBMTE2ZmZvf39/+MjP8YGKioqMHBwTMzM3t7e1taWo+Pj/+kpAgICO/v7/9bWyH5BAUU
AAcALAAAAABwAB0AAAX/oCCOZGmeY0UdbOu+hyVbjAs1MwJfuHzBwOAkUHsFAi6Ucmn6TILGSGea
cWUA0w4BpsFOJdAwy2LQvCAGg6fFbDM/YtYVQDe4LpkI3QFDLDp0ZnFBXXwuDVhrLG6MKCtiBnSS
Py4Oe0GRAIKDLx56hi0YABFPi42nKWIQWBKSCy+WAFsIAzQtmWAWtYotEwgbtUW+ogAYEMcXXVgX
EDUPz9DR0tPUDwkKJWJXDgyAAAalLLEOBJIRFiyZDsSjlDGZdB2vq5L19nRgnPoHD9lhkQMOxALg
TqAkDA3YIYFHoEGmCGsQSGpwAZeHDJkMZNiYgZi8DDr2cepHIswFLDUs/0jKJy7eGnoAqmQcM/FA
pi0xJhmUZYVOBJEiSY4IswCLBg3lfIaLhYHFBD0A+NxkEWBlVTpVDsB8Nc5F0VG8XFhLQLas2bNn
wwkV8e+epJA7QWVqmklQt0An6QQ8cFVT3AMMIByYA9EDBCQHOFRAVSJBi7UCoORFcAzCAEmbuh6Y
MNdmIBZ3NcHc2xdM1ysBLo86ILEpB8YmHLOADKVV017eSLX8Btqbmc5aJQ2Y4C1fXgAN/qImfOCk
gwSLYZOQzc/fmQaAMFgQDMECVE06BjaY8BWADngIJigDIPirgRqtvj1JioGBJQ8b4qXWFF36COq0
wTAQHVuwU48HomiBBf9mLOgRgSXeAPDKZkl1kJFgOdXDRwARfhNACRUUIOKIJJZYIi8BvmDBAiyy
iE4DLbaYwQQwJrcBBgY4sEELAyyAzgA4OoCOCxZokIYDA4RlgQMGYLCAIhcQkIYGSDQGFAwpXqnl
loOU8ACXs1kH5phkHuDlmFmWqeaVZ4KZ5ppwctIml2/GaScUc25Z5518JkHCl26KGYcHRxSxZgBh
wRBOL4ix8SeaghK5CQsaDNDjXoMOaZIEhsLAQFYHeGDjcH6OoEAC1aQqzTWRtpCBBI2S1wKsE9TA
QKMMrIFYDUO0gGgvGwz562ZFMMBSrR4sIFivB/Tn3xIVBMEDBDs6JcH9MX40oAECCGQwQHKVSjBA
BhtMsMGnDQy3wQYZYGisBPhtsEAAUQ7JwISANQABARtAkEEDG3hAwbNtPAKDBPrixAIBA6zLQAM6
SPCEsmA0kFwGnwZwrWEE8LAJAswElNovLdxb8ivlLrBBMjt+QLAScADBAAEybOsUvgdQdMCEIAUE
8WCfAqaLH5W1YMEFPIQKkqYmg1bFAMZSdthmLr9cghNBBEtVPrK2oHOwFyRZxc8YD0CtvwG0K4PR
CCR7wQbcaurBttxadgDUv5zdAgXOPqtCGBbwYkEpcGlVxAIarPHD1BdM8MMGGggWgAYLhHOEVhrs
eHkL8rJ4THNrQAOuQwgAOw==

------_=_NextPart_001_01C9C298.7CBF4CA4--
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Question about Terminals and Task priority
"--_004_BFE615A1BBF8CA40B016B28E1BABC62402B66ED2BAiowadsmex104i_
Content-Type: text/plain; charset=""us-ascii""
Content-Transfer-Encoding: quoted-printable

1) The LD terminals are dynamically allocated as needed.

2a) To assign a priority to a CICS task, define a task code that matches t=
he CICS task.
2b) To assign a priority to a batch program, define a task code that match=
es the program name (not the job name).
2c) For both CICS and batch task definitions, the program should be specif=
ied as ""RHDCNP3S"".

You can use exit 36 to ensure that the batch job does not get selected as t=
he victim in a deadlock situation. This is an assembler program that you h=
ave to write yourself.

________________________________
From: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM] On B=
ehalf Of George H Lewandowski
Sent: Tuesday, April 21, 2009 10:24 AM
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: Question about Terminals and Task priority


We are currently running R16 sp7. There are some questions about deadlock=
s.
While under R15.0 there were maybe 2 deadlocks on a specific task (WH06) ev=
ery 2-3 months, now the deadlocks are more frequent (once a week or so).
Nothing in the sysgen has changed.
The tasks that are deadlocking are T1 a CICS transaction (WH06) and T2 a ba=
tch program.
It is my understanding that they are both treated as ERUS and get a ""LD"" te=
rminal allocated.

Question 1 where are the ""LD"" terminals defined?

The task code for T1 is WH06 and is not defined to IDMS it is a CICS task s=
o the CICS task is getting a priority of 5.

The batch job also gets a ""LD"" terminal allocated and also has the priority=
of 5.

For some reason the program associated with T1 (MFCT002C) has a task code d=
efined in the CV with a priority of 100. As far as I can tell the task is =
never getting executed.
The program MFCT002c is running in the CICS region making a DB request to t=
he CV and getting a ""LD"" terminal allocated with a priority of 5.

Question 2 How can we get the batch and CICS programs separated to give th=
e CICS tasks a higher priority that the batch jobs?

The main problem/opportunity that the user/annalist wants is that incase of=
a deadlock the batch job gets selected as the victim and the on-line CICS =
task continues....




________________________________
George H Lewandowski
Database Administrator
GIS
7x24 Operations
GA-25, J46-2E Work (847) 938-5526
Pager (800) 209-1305
george.lewandowski@abbott.com<mailTo:george.lewandowski@abbott.com>

[cid:566174015@21042009-3313]
________________________________
This communication may contain information that is proprietary, confidentia=
l, or exempt from disclosure. If you are not the intended recipient, please=
note that any other dissemination, distribution, use or copying of this co=
mmunication is strictly prohibited. Anyone who receives this message in err=
or should notify the sender immediately by telephone or by return e-mail an=
d delete it from his or her computer.


--_004_BFE615A1BBF8CA40B016B28E1BABC62402B66ED2BAiowadsmex104i_
Content-Type: image/gif; name=""ATT00001.gif""
Content-Description: ATT00001.gif
Content-Disposition: inline; filename=""ATT00001.gif""; size=1156;
creation-date=""Tue, 21 Apr 2009 10:43:51 GMT"";
modification-date=""Tue, 21 Apr 2009 10:43:51 GMT""
Content-ID: <566174015@21042009-3313>
Content-Transfer-Encoding: base64

R0lGODlhcAAdAMQAAAAAANva2v8AAISEhE5OTv9+fiMjI////7W1tf/MzP9PT3BwcObm5pmZmUFB
Qf/W1szMzBMTE2ZmZvf39/+MjP8YGKioqMHBwTMzM3t7e1taWo+Pj/+kpAgICO/v7/9bWyH5BAUU
AAcALAAAAABwAB0AAAX/oCCOZGmeY0UdbOu+hyVbjAs1MwJfuHzBwOAkUHsFAi6Ucmn6TILGSGea
cWUA0w4BpsFOJdAwy2LQvCAGg6fFbDM/YtYVQDe4LpkI3QFDLDp0ZnFBXXwuDVhrLG6MKCtiBnSS
Py4Oe0GRAIKDLx56hi0YABFPi42nKWIQWBKSCy+WAFsIAzQtmWAWtYotEwgbtUW+ogAYEMcXXVgX
EDUPz9DR0tPUDwkKJWJXDgyAAAalLLEOBJIRFiyZDsSjlDGZdB2vq5L19nRgnPoHD9lhkQMOxALg
TqAkDA3YIYFHoEGmCGsQSGpwAZeHDJkMZNiYgZi8DDr2cepHIswFLDUs/0jKJy7eGnoAqmQcM/FA
pi0xJhmUZYVOBJEiSY4IswCLBg3lfIaLhYHFBD0A+NxkEWBlVTpVDsB8Nc5F0VG8XFhLQLas2bNn
wwkV8e+epJA7QWVqmklQt0An6QQ8cFVT3AMMIByYA9EDBCQHOFRAVSJBi7UCoORFcAzCAEmbuh6Y
MNdmIBZ3NcHc2xdM1ysBLo86ILEpB8YmHLOADKVV017eSLX8Btqbmc5aJQ2Y4C1fXgAN/qImfOCk
gwSLYZOQzc/fmQaAMFgQDMECVE06BjaY8BWADngIJigDIPirgRqtvj1JioGBJQ8b4qXWFF36COq0
wTAQHVuwU48HomiBBf9mLOgRgSXeAPDKZkl1kJFgOdXDRwARfhNACRUUIOKIJJZYIi8BvmDBAiyy
iE4DLbaYwQQwJrcBBgY4sEELAyyAzgA4OoCOCxZokIYDA4RlgQMGYLCAIhcQkIYGSDQGFAwpXqnl
loOU8ACXs1kH5phkHuDlmFmWqeaVZ4KZ5ppwctIml2/GaScUc25Z5518JkHCl26KGYcHRxSxZgBh
wRBOL4ix8SeaghK5CQsaDNDjXoMOaZIEhsLAQFYHeGDjcH6OoEAC1aQqzTWRtpCBBI2S1wKsE9TA
QKMMrIFYDUO0gGgvGwz562ZFMMBSrR4sIFivB/Tn3xIVBMEDBDs6JcH9MX40oAECCGQwQHKVSjBA
BhtMsMGnDQy3wQYZYGisBPhtsEAAUQ7JwISANQABARtAkEEDG3hAwbNtPAKDBPrixAIBA6zLQAM6
SPCEsmA0kFwGnwZwrWEE8LAJAswElNovLdxb8ivlLrBBMjt+QLAScADBAAEybOsUvgdQdMCEIAUE
8WCfAqaLH5W1YMEFPIQKkqYmg1bFAMZSdthmLr9cghNBBEtVPrK2oHOwFyRZxc8YD0CtvwG0K4PR
CCR7wQbcaurBttxadgDUv5zdAgXOPqtCGBbwYkEpcGlVxAIarPHD1BdM8MMGGggWgAYLhHOEVhrs
eHkL8rJ4THNrQAOuQwgAOw==

_004_BFE615A1BBF8CA40B016B28E1BABC62402B66ED2BAiowadsmex104i_
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Question about Terminals and Task priority
"This is a multi-part message in MIME format.

------_=_NextPart_001_01C9C299.27724E41
Content-Type: text/plain;
charset=""us-ascii""
Content-Transfer-Encoding: quoted-printable

Hi George,
=20
My understanding of what happens when a CICS transaction issues a BIND
RUNUNIT is that IDMS will check for a TASK name equal to that of the
BIND program name assuming that this is non blank. If a TASK not found
it then checks for a TASK name of nnnnBULK where nnnn is the TPNAME
defined in the CICSOPT macro being used by the IDMSINTC processing the
BIND. If this fails it takes defaults.
=20
For batch it again looks for BIND program name and if not found looks
for BATCBULK.
=20
We have defined several CICS program names as TASK codes and they get
invoked. I would check that MFCT002C does move its name into
PROGRAM-NAME is subschema control.
=20
A base starting we did years ago before fine tuning was to define
nnnnBULK (one for each CICS system) with priority of 100 and BATCBULK
with priority 110. Yes batch wins in a deadlock over CICS as it could
have been running for hours.
=20
Over the years we have added task name equal to BIND program names, for
both batch and CICS, with different priorities to more finely control
the 'winners and loser' in a DEADLOCK.
=20
HTH.=20
=20
Pete =20

________________________________

From: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM]
On Behalf Of George H Lewandowski
Sent: 21 April 2009 16:24
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: Question about Terminals and Task priority



We are currently running R16 sp7. There are some questions about
deadlocks. =20
While under R15.0 there were maybe 2 deadlocks on a specific task (WH06)
every 2-3 months, now the deadlocks are more frequent (once a week or
so).=20
Nothing in the sysgen has changed.=20
The tasks that are deadlocking are T1 a CICS transaction (WH06) and T2 a
batch program.=20
It is my understanding that they are both treated as ERUS and get a ""LD""
terminal allocated.=20

Question 1 where are the ""LD"" terminals defined?=20

The task code for T1 is WH06 and is not defined to IDMS it is a CICS
task so the CICS task is getting a priority of 5.=20

The batch job also gets a ""LD"" terminal allocated and also has the
priority of 5.=20

For some reason the program associated with T1 (MFCT002C) has a task
code defined in the CV with a priority of 100. As far as I can tell the
task is never getting executed.=20
The program MFCT002c is running in the CICS region making a DB request
to the CV and getting a ""LD"" terminal allocated with a priority of 5.=20

Question 2 How can we get the batch and CICS programs separated to give
the CICS tasks a higher priority that the batch jobs?=20

The main problem/opportunity that the user/annalist wants is that incase
of a deadlock the batch job gets selected as the victim and the on-line
CICS task continues....=20





________________________________

George H Lewandowski=20
Database Administrator
GIS=20
7x24 Operations
GA-25, J46-2E Work (847) 938-5526
Pager (800) 209-1305
george.lewandowski@abbott.com <mailTo:george.lewandowski@abbott.com> =09

=20

________________________________

This communication may contain information that is proprietary,
confidential, or exempt from disclosure. If you are not the intended
recipient, please note that any other dissemination, distribution, use
or copying of this communication is strictly prohibited. Anyone who
receives this message in error should notify the sender immediately by
telephone or by return e-mail and delete it from his or her computer.


------_=_NextPart_001_01C9C299.27724E41
Content-Type: image/gif;
name=""ATT5300459.gif""
Content-Transfer-Encoding: base64
Content-ID: :love:43103815@21042009-018E>
Content-Description: ATT5300459.gif
Content-Location: ATT5300459.gif

R0lGODlhcAAdAMQAAAAAANva2v8AAISEhE5OTv9+fiMjI////7W1tf/MzP9PT3BwcObm5pmZmUFB
Qf/W1szMzBMTE2ZmZvf39/+MjP8YGKioqMHBwTMzM3t7e1taWo+Pj/+kpAgICO/v7/9bWyH5BAUU
AAcALAAAAABwAB0AAAX/oCCOZGmeY0UdbOu+hyVbjAs1MwJfuHzBwOAkUHsFAi6Ucmn6TILGSGea
cWUA0w4BpsFOJdAwy2LQvCAGg6fFbDM/YtYVQDe4LpkI3QFDLDp0ZnFBXXwuDVhrLG6MKCtiBnSS
Py4Oe0GRAIKDLx56hi0YABFPi42nKWIQWBKSCy+WAFsIAzQtmWAWtYotEwgbtUW+ogAYEMcXXVgX
EDUPz9DR0tPUDwkKJWJXDgyAAAalLLEOBJIRFiyZDsSjlDGZdB2vq5L19nRgnPoHD9lhkQMOxALg
TqAkDA3YIYFHoEGmCGsQSGpwAZeHDJkMZNiYgZi8DDr2cepHIswFLDUs/0jKJy7eGnoAqmQcM/FA
pi0xJhmUZYVOBJEiSY4IswCLBg3lfIaLhYHFBD0A+NxkEWBlVTpVDsB8Nc5F0VG8XFhLQLas2bNn
wwkV8e+epJA7QWVqmklQt0An6QQ8cFVT3AMMIByYA9EDBCQHOFRAVSJBi7UCoORFcAzCAEmbuh6Y
MNdmIBZ3NcHc2xdM1ysBLo86ILEpB8YmHLOADKVV017eSLX8Btqbmc5aJQ2Y4C1fXgAN/qImfOCk
gwSLYZOQzc/fmQaAMFgQDMECVE06BjaY8BWADngIJigDIPirgRqtvj1JioGBJQ8b4qXWFF36COq0
wTAQHVuwU48HomiBBf9mLOgRgSXeAPDKZkl1kJFgOdXDRwARfhNACRUUIOKIJJZYIi8BvmDBAiyy
iE4DLbaYwQQwJrcBBgY4sEELAyyAzgA4OoCOCxZokIYDA4RlgQMGYLCAIhcQkIYGSDQGFAwpXqnl
loOU8ACXs1kH5phkHuDlmFmWqeaVZ4KZ5ppwctIml2/GaScUc25Z5518JkHCl26KGYcHRxSxZgBh
wRBOL4ix8SeaghK5CQsaDNDjXoMOaZIEhsLAQFYHeGDjcH6OoEAC1aQqzTWRtpCBBI2S1wKsE9TA
QKMMrIFYDUO0gGgvGwz562ZFMMBSrR4sIFivB/Tn3xIVBMEDBDs6JcH9MX40oAECCGQwQHKVSjBA
BhtMsMGnDQy3wQYZYGisBPhtsEAAUQ7JwISANQABARtAkEEDG3hAwbNtPAKDBPrixAIBA6zLQAM6
SPCEsmA0kFwGnwZwrWEE8LAJAswElNovLdxb8ivlLrBBMjt+QLAScADBAAEybOsUvgdQdMCEIAUE
8WCfAqaLH5W1YMEFPIQKkqYmg1bFAMZSdthmLr9cghNBBEtVPrK2oHOwFyRZxc8YD0CtvwG0K4PR
CCR7wQbcaurBttxadgDUv5zdAgXOPqtCGBbwYkEpcGlVxAIarPHD1BdM8MMGGggWgAYLhHOEVhrs
eHkL8rJ4THNrQAOuQwgAOw==

------_=_NextPart_001_01C9C299.27724E41--
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Question about Terminals and Task priority
"Hi George,

My understanding of what happens when a CICS transaction issues a BIND
RUNUNIT is that IDMS will check for a TASK name equal to that of the
BIND program name assuming that this is non blank. If a TASK not found
it then checks for a TASK name of nnnnBULK where nnnn is the TPNAME
defined in the CICSOPT macro being used by the IDMSINTC processing the
BIND. If this fails it takes defaults.

For batch it again looks for BIND program name and if not found looks
for BATCBULK.

We have defined several CICS program names as TASK codes and they get
invoked. I would check that MFCT002C does move its name into
PROGRAM-NAME is subschema control.

A base starting we did years ago before fine tuning was to define
nnnnBULK (one for each CICS system) with priority of 100 and BATCBULK
with priority 110. Yes batch wins in a deadlock over CICS as it could
have been running for hours.

Over the years we have added task name equal to BIND program names, for
both batch and CICS, with different priorities to more finely control
the 'winners and loser' in a DEADLOCK.

HTH.

Pete

________________________________

From: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM]
On Behalf Of George H Lewandowski
Sent: 21 April 2009 16:24
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: Question about Terminals and Task priority



We are currently running R16 sp7. There are some questions about
deadlocks.
While under R15.0 there were maybe 2 deadlocks on a specific task (WH06)
every 2-3 months, now the deadlocks are more frequent (once a week or
so).
Nothing in the sysgen has changed.
The tasks that are deadlocking are T1 a CICS transaction (WH06) and T2 a
batch program.
It is my understanding that they are both treated as ERUS and get a ""LD""
terminal allocated.

Question 1 where are the ""LD"" terminals defined?

The task code for T1 is WH06 and is not defined to IDMS it is a CICS
task so the CICS task is getting a priority of 5.

The batch job also gets a ""LD"" terminal allocated and also has the
priority of 5.

For some reason the program associated with T1 (MFCT002C) has a task
code defined in the CV with a priority of 100. As far as I can tell the
task is never getting executed.
The program MFCT002c is running in the CICS region making a DB request
to the CV and getting a ""LD"" terminal allocated with a priority of 5.

Question 2 How can we get the batch and CICS programs separated to give
the CICS tasks a higher priority that the batch jobs?

The main problem/opportunity that the user/annalist wants is that incase
of a deadlock the batch job gets selected as the victim and the on-line
CICS task continues....





________________________________

George H Lewandowski
Database Administrator
GIS
7x24 Operations
GA-25, J46-2E Work (847) 938-5526
Pager (800) 209-1305
george.lewandowski@abbott.com <mailTo:george.lewandowski@abbott.com>




________________________________

This communication may contain information that is proprietary,
confidential, or exempt from disclosure. If you are not the intended
recipient, please note that any other dissemination, distribution, use
or copying of this communication is strictly prohibited. Anyone who
receives this message in error should notify the sender immediately by
telephone or by return e-mail and delete it from his or her computer.

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Question about Terminals and Task priority
"I beleive that LD's are not sysgenned. They are defined dynamically,
and initially I think it's equal to the number of ERUS in the sysgen.

I've never found priorities to fix deadlocks anyway. If you can
eliminate waits, then that will fix deadlocks. And, eliminating OOAK
type records, like a record that everybody accesses to get through the
data structure. Those are best readied retrieval in a subroutine, cause
a second retrieval only run unit to be created without implicit update
locking, and then returned to the calling program that ready's the area
in update if needed.

The CICS class max task can be a useful tool for certain tasks, that at
are known to bottle neck the data. These tasks will wait until a task
is available and the single threading is transparent to the user.


Lutz Petzold
TDM UDB/IDMS Support
401-782-2265
Page 860 366 0865 or Telalert






________________________________

From: IDMS Public Discussion Forum
[mailTo:IDMS-L@LISTSERV.IUASSN.COM] On Behalf Of George H Lewandowski
Sent: Tuesday, April 21, 2009 11:24 AM
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: Question about Terminals and Task priority



We are currently running R16 sp7. There are some questions
about deadlocks.
While under R15.0 there were maybe 2 deadlocks on a specific
task (WH06) every 2-3 months, now the deadlocks are more frequent (once
a week or so).
Nothing in the sysgen has changed.
The tasks that are deadlocking are T1 a CICS transaction (WH06)
and T2 a batch program.
It is my understanding that they are both treated as ERUS and
get a ""LD"" terminal allocated.

Question 1 where are the ""LD"" terminals defined?

The task code for T1 is WH06 and is not defined to IDMS it is a
CICS task so the CICS task is getting a priority of 5.

The batch job also gets a ""LD"" terminal allocated and also has
the priority of 5.

For some reason the program associated with T1 (MFCT002C) has a
task code defined in the CV with a priority of 100. As far as I can
tell the task is never getting executed.
The program MFCT002c is running in the CICS region making a DB
request to the CV and getting a ""LD"" terminal allocated with a priority
of 5.

Question 2 How can we get the batch and CICS programs separated
to give the CICS tasks a higher priority that the batch jobs?

The main problem/opportunity that the user/annalist wants is
that incase of a deadlock the batch job gets selected as the victim and
the on-line CICS task continues....





________________________________

George H Lewandowski
Database Administrator
GIS
7x24 Operations
GA-25, J46-2E Work (847) 938-5526
Pager (800) 209-1305
george.lewandowski@abbott.com <mailTo:george.lewandowski@abbott.com>



________________________________

This communication may contain information that is proprietary,
confidential, or exempt from disclosure. If you are not the intended
recipient, please note that any other dissemination, distribution, use
or copying of this communication is strictly prohibited. Anyone who
receives this message in error should notify the sender immediately by
telephone or by return e-mail and delete it from his or her computer.




This e-mail may contain confidential or privileged information. If
you think you have received this e-mail in error, please advise the
sender by reply e-mail and then delete this e-mail immediately.
Thank you. Aetna
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Question about Terminals and Task priority
"1) The LD terminals are dynamically allocated as needed.

2a) To assign a priority to a CICS task, define a task code that matches the CICS task.
2b) To assign a priority to a batch program, define a task code that matches the program name (not the job name).
2c) For both CICS and batch task definitions, the program should be specified as ""RHDCNP3S"".

You can use exit 36 to ensure that the batch job does not get selected as the victim in a deadlock situation. This is an assembler program that you have to write yourself.

________________________________
From: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM] On Behalf Of George H Lewandowski
Sent: Tuesday, April 21, 2009 10:24 AM
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: Question about Terminals and Task priority


We are currently running R16 sp7. There are some questions about deadlocks.
While under R15.0 there were maybe 2 deadlocks on a specific task (WH06) every 2-3 months, now the deadlocks are more frequent (once a week or so).
Nothing in the sysgen has changed.
The tasks that are deadlocking are T1 a CICS transaction (WH06) and T2 a batch program.
It is my understanding that they are both treated as ERUS and get a ""LD"" terminal allocated.

Question 1 where are the ""LD"" terminals defined?

The task code for T1 is WH06 and is not defined to IDMS it is a CICS task so the CICS task is getting a priority of 5.

The batch job also gets a ""LD"" terminal allocated and also has the priority of 5.

For some reason the program associated with T1 (MFCT002C) has a task code defined in the CV with a priority of 100. As far as I can tell the task is never getting executed.
The program MFCT002c is running in the CICS region making a DB request to the CV and getting a ""LD"" terminal allocated with a priority of 5.

Question 2 How can we get the batch and CICS programs separated to give the CICS tasks a higher priority that the batch jobs?

The main problem/opportunity that the user/annalist wants is that incase of a deadlock the batch job gets selected as the victim and the on-line CICS task continues....




________________________________
George H Lewandowski
Database Administrator
GIS
7x24 Operations
GA-25, J46-2E Work (847) 938-5526
Pager (800) 209-1305
george.lewandowski@abbott.com<mailTo:george.lewandowski@abbott.com>

[cid:566174015@21042009-3313]
________________________________
This communication may contain information that is proprietary, confidential, or exempt from disclosure. If you are not the intended recipient, please note that any other dissemination, distribution, use or copying of this communication is strictly prohibited. Anyone who receives this message in error should notify the sender immediately by telephone or by return e-mail and delete it from his or her computer.

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
IDMS 17 & zIIP
"preliminary results

our heaviest hit CV: 10-12 million transactions/hour
defaulted to 11 subtask - MQDEPTH of 4 (i have since lowered it to 3)

DISPLAY MPMODE TABLE
*** MULTITASK ENVIRONMENT, MPMODE TABLE ***
NAME REQUEST COUNT WAIT COUNT
---- ------------- ----------
ANY 1,470,820,261 00
DC 3,267,846,172 59,505,028
DB 2,835,150,425 2,527,385,023
USER 9,596 00
LOADER 128 00
DRIVER 35,999 00

DISPLAY SUBTASKS
*** Display all subtasks ***
Work Task dispatch
Name Nr type Status count Wakeup count Total CPU
time
---- -- ---- ------ ------------- ------------
--------------
MAINTASK 01 IDMS IDLE 6,916 2,191
00:00:01.0722
SUBT0001 02 IDMS IDLE 00 00
00:00:00.0000
SUBT0002 03 IDMS IDLE 00 00
00:00:00.0000
SUBT0003 04 IDMS IDLE 00 00
00:00:00.0000
SUBT0004 05 IDMS IDLE 21 02
00:00:00.0000
SUBT0005 06 IDMS IDLE 2,655 202
00:00:00.0000
SUBT0006 07 IDMS IDLE 225,131 18,183
00:00:00.0113
SUBT0007 08 IDMS IDLE 17,259,205 1,223,667
00:00:00.5681
SUBT0008 09 IDMS IDLE 513,523,667 32,498,883
00:00:16.8398
SUBT0009 10 IDMS BUSY 1,633,182,761 171,603,197
00:01:13.4576
SUBT0010 11 IDMS IDLE 1,493,003,343 1,072,724,051
00:06:43.1507

DISPLAY SUBTASK 011
*** Display Subtask details ***
Name SUBT0010
Number 11
Status IDLE
Work type IDMS
Count wakeups 1,073,640,352
Count task dispatches 1,497,998,329
User mode CPU time 00:00:00.0000
System mode CPU time 15:37:16.2435
CPU effectiveness (%) 80
Count times fast posted 1,129,049,368
Count times OS posted 00
Count found work pass 1 997,711,198
Count found work pass 2 500,287,131
Count times POSTEXIT resumed 1,070,597,878
*** Enclave Info ***
zIIP time 15:10:27.3379
zIIP on CP time 00:20:05.3424
CPU effectiveness (%) 100
Count swap attempts 14,885,075
Count actual swaps 14,885,061

DISPLAY SUBTASK 010
*** Display Subtask details ***
Name SUBT0009
Number 10
Status BUSY
Work type IDMS
Count wakeups 172,083,035
Count task dispatches 1,634,439,141
User mode CPU time 00:00:00.0000
System mode CPU time 03:55:27.7465
CPU effectiveness (%) 83
Count times fast posted 7,879,043
Count times OS posted 00
Count found work pass 1 1,550,134,708
Count found work pass 2 84,304,433
Count times POSTEXIT resumed 172,081,958
*** Enclave Info ***
zIIP time 03:41:39.8137
zIIP on CP time 00:12:34.4059
CPU effectiveness (%) 99
Count swap attempts 2,622,414
Count actual swaps 2,622,412

DISPLAY SUBTASK 009
*** Display Subtask details ***
Name SUBT0008
Number 09
Status IDLE
Work type IDMS
Count wakeups 32,527,577
Count task dispatches 513,790,538
User mode CPU time 00:00:00.0000
System mode CPU time 01:02:42.6629
CPU effectiveness (%) 81
Count times fast posted 296,225
Count times OS posted 00
Count found work pass 1 495,360,877
Count found work pass 2 18,429,661
Count times POSTEXIT resumed 32,527,515
*** Enclave Info ***
zIIP time 00:57:19.5505
zIIP on CP time 00:05:06.2642
CPU effectiveness (%) 98
Count swap attempts 650,039
Count actual swaps 650,039

DISPLAY SUBTASK 008
*** Display Subtask details ***
Name SUBT0007
Number 08
Status IDLE
Work type IDMS
Count wakeups 1,223,958
Count task dispatches 17,261,417
User mode CPU time 00:00:00.0000
System mode CPU time 00:02:03.1556
CPU effectiveness (%) 74
Count times fast posted 4,899
Count times OS posted 00
Count found work pass 1 16,606,326
Count found work pass 2 655,091
Count times POSTEXIT resumed 1,223,957
*** Enclave Info ***
zIIP time 00:01:41.8965
zIIP on CP time 00:00:20.6906
CPU effectiveness (%) 98
Count swap attempts 21,445
Count actual swaps 21,445

DISPLAY SUBTASK 007
*** Display Subtask details ***
Name SUBT0006
Number 07
Status IDLE
Work type IDMS
Count wakeups 18,184
Count task dispatches 225,131
User mode CPU time 00:00:00.0000
System mode CPU time 00:00:01.6190
CPU effectiveness (%) 75
Count times fast posted 63
Count times OS posted 00
Count found work pass 1 215,671
Count found work pass 2 9,460
Count times POSTEXIT resumed 18,184
*** Enclave Info ***
zIIP time 00:00:01.2986
zIIP on CP time 00:00:00.3090
CPU effectiveness (%) 97
Count swap attempts 323
Count actual swaps 323

DISPLAY SUBTASK 006
*** Display Subtask details ***
Name SUBT0005
Number 06
Status IDLE
Work type IDMS
Count wakeups 202
Count task dispatches 2,655
User mode CPU time 00:00:00.0000
System mode CPU time 00:00:00.0180
CPU effectiveness (%) N/A
Count times fast posted 01
Count times OS posted 00
Count found work pass 1 2,543
Count found work pass 2 112
Count times POSTEXIT resumed 202
*** Enclave Info ***
zIIP time 00:00:00.0147
zIIP on CP time 00:00:00.0033
CPU effectiveness (%) 98
Count swap attempts 01
Count actual swaps 01

DISPLAY SUBTASK EFFECTIVENESS
*** Subtask display ***
Subtask Elapsed time Total CPU time %
CPU SRB
Name TCB SRB TCB SRB TCB
SRB
-------- -------------- -------------- -------------- -------------- ---
---
MAINTASK 00:00:04.3765 00:00:00.0684 00:00:01.0722 00:00:00.0749 24
109 Y
SUBT0001 00:00:00.0001 00:00:00.0000 00:00:00.0000 00:00:00.0000 00
N/A Y
SUBT0002 00:00:00.0001 00:00:00.0000 00:00:00.0000 00:00:00.0000 00
N/A Y
SUBT0003 00:00:00.0000 00:00:00.0000 00:00:00.0000 00:00:00.0000 N/A
N/A Y
SUBT0004 00:00:00.0000 00:00:00.0001 00:00:00.0000 00:00:00.0001 N/A
100 Y
SUBT0005 00:00:00.0000 00:00:00.0183 00:00:00.0000 00:00:00.0180 N/A
98 Y
SUBT0006 00:00:00.0149 00:00:01.6460 00:00:00.0113 00:00:01.6077 75
97 Y
SUBT0007 00:00:00.7672 00:02:05.0245 00:00:00.5685 00:02:02.6041 74
98 Y
SUBT0008 00:00:20.5983 01:03:33.8557 00:00:16.8550 01:02:27.3845 81
98 Y
SUBT0009 00:01:27.7680 03:56:32.8645 00:01:13.5999 03:54:26.2755 83
99 Y
SUBT0010 00:08:21.4708 15:29:31.2295 00:06:44.2907 15:32:01.1725 80
100 Y
-------- -------------- -------------- -------------- -------------- ---
---
Totals 00:10:14.9959 20:31:44.7070 00:08:16.3976 20:30:59.1373 80
99


to be honest - it will take me a while to digest all this to determine
what this means - but our perf/tuning folks tell me that IDMS is
exploiting zIIP more than any other WLM group on the LPAR ...(DDF is a
not-so-close second ...)

Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
choelscher@humana.com




The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
IDMS 17 & zIIP
"preliminary results

our heaviest hit CV: 10-12 million transactions/hour
defaulted to 11 subtask - MQDEPTH of 4 (i have since lowered it to 3)

DISPLAY MPMODE TABLE
*** MULTITASK ENVIRONMENT, MPMODE TABLE ***
NAME REQUEST COUNT WAIT COUNT
---- ------------- ----------
ANY 1,470,820,261 00
DC 3,267,846,172 59,505,028
DB 2,835,150,425 2,527,385,023
USER 9,596 00
LOADER 128 00
DRIVER 35,999 00

DISPLAY SUBTASKS
*** Display all subtasks ***
Work Task dispatch
Name Nr type Status count Wakeup count Total CPU
time
---- -- ---- ------ ------------- ------------
--------------
MAINTASK 01 IDMS IDLE 6,916 2,191
00:00:01.0722
SUBT0001 02 IDMS IDLE 00 00
00:00:00.0000
SUBT0002 03 IDMS IDLE 00 00
00:00:00.0000
SUBT0003 04 IDMS IDLE 00 00
00:00:00.0000
SUBT0004 05 IDMS IDLE 21 02
00:00:00.0000
SUBT0005 06 IDMS IDLE 2,655 202
00:00:00.0000
SUBT0006 07 IDMS IDLE 225,131 18,183
00:00:00.0113
SUBT0007 08 IDMS IDLE 17,259,205 1,223,667
00:00:00.5681
SUBT0008 09 IDMS IDLE 513,523,667 32,498,883
00:00:16.8398
SUBT0009 10 IDMS BUSY 1,633,182,761 171,603,197
00:01:13.4576
SUBT0010 11 IDMS IDLE 1,493,003,343 1,072,724,051
00:06:43.1507

DISPLAY SUBTASK 011
*** Display Subtask details ***
Name SUBT0010
Number 11
Status IDLE
Work type IDMS
Count wakeups 1,073,640,352
Count task dispatches 1,497,998,329
User mode CPU time 00:00:00.0000
System mode CPU time 15:37:16.2435
CPU effectiveness (%) 80
Count times fast posted 1,129,049,368
Count times OS posted 00
Count found work pass 1 997,711,198
Count found work pass 2 500,287,131
Count times POSTEXIT resumed 1,070,597,878
*** Enclave Info ***
zIIP time 15:10:27.3379
zIIP on CP time 00:20:05.3424
CPU effectiveness (%) 100
Count swap attempts 14,885,075
Count actual swaps 14,885,061

DISPLAY SUBTASK 010
*** Display Subtask details ***
Name SUBT0009
Number 10
Status BUSY
Work type IDMS
Count wakeups 172,083,035
Count task dispatches 1,634,439,141
User mode CPU time 00:00:00.0000
System mode CPU time 03:55:27.7465
CPU effectiveness (%) 83
Count times fast posted 7,879,043
Count times OS posted 00
Count found work pass 1 1,550,134,708
Count found work pass 2 84,304,433
Count times POSTEXIT resumed 172,081,958
*** Enclave Info ***
zIIP time 03:41:39.8137
zIIP on CP time 00:12:34.4059
CPU effectiveness (%) 99
Count swap attempts 2,622,414
Count actual swaps 2,622,412

DISPLAY SUBTASK 009
*** Display Subtask details ***
Name SUBT0008
Number 09
Status IDLE
Work type IDMS
Count wakeups 32,527,577
Count task dispatches 513,790,538
User mode CPU time 00:00:00.0000
System mode CPU time 01:02:42.6629
CPU effectiveness (%) 81
Count times fast posted 296,225
Count times OS posted 00
Count found work pass 1 495,360,877
Count found work pass 2 18,429,661
Count times POSTEXIT resumed 32,527,515
*** Enclave Info ***
zIIP time 00:57:19.5505
zIIP on CP time 00:05:06.2642
CPU effectiveness (%) 98
Count swap attempts 650,039
Count actual swaps 650,039

DISPLAY SUBTASK 008
*** Display Subtask details ***
Name SUBT0007
Number 08
Status IDLE
Work type IDMS
Count wakeups 1,223,958
Count task dispatches 17,261,417
User mode CPU time 00:00:00.0000
System mode CPU time 00:02:03.1556
CPU effectiveness (%) 74
Count times fast posted 4,899
Count times OS posted 00
Count found work pass 1 16,606,326
Count found work pass 2 655,091
Count times POSTEXIT resumed 1,223,957
*** Enclave Info ***
zIIP time 00:01:41.8965
zIIP on CP time 00:00:20.6906
CPU effectiveness (%) 98
Count swap attempts 21,445
Count actual swaps 21,445

DISPLAY SUBTASK 007
*** Display Subtask details ***
Name SUBT0006
Number 07
Status IDLE
Work type IDMS
Count wakeups 18,184
Count task dispatches 225,131
User mode CPU time 00:00:00.0000
System mode CPU time 00:00:01.6190
CPU effectiveness (%) 75
Count times fast posted 63
Count times OS posted 00
Count found work pass 1 215,671
Count found work pass 2 9,460
Count times POSTEXIT resumed 18,184
*** Enclave Info ***
zIIP time 00:00:01.2986
zIIP on CP time 00:00:00.3090
CPU effectiveness (%) 97
Count swap attempts 323
Count actual swaps 323

DISPLAY SUBTASK 006
*** Display Subtask details ***
Name SUBT0005
Number 06
Status IDLE
Work type IDMS
Count wakeups 202
Count task dispatches 2,655
User mode CPU time 00:00:00.0000
System mode CPU time 00:00:00.0180
CPU effectiveness (%) N/A
Count times fast posted 01
Count times OS posted 00
Count found work pass 1 2,543
Count found work pass 2 112
Count times POSTEXIT resumed 202
*** Enclave Info ***
zIIP time 00:00:00.0147
zIIP on CP time 00:00:00.0033
CPU effectiveness (%) 98
Count swap attempts 01
Count actual swaps 01

DISPLAY SUBTASK EFFECTIVENESS
*** Subtask display ***
Subtask Elapsed time Total CPU time %
CPU SRB
Name TCB SRB TCB SRB TCB
SRB
-------- -------------- -------------- -------------- -------------- ---
---
MAINTASK 00:00:04.3765 00:00:00.0684 00:00:01.0722 00:00:00.0749 24
109 Y
SUBT0001 00:00:00.0001 00:00:00.0000 00:00:00.0000 00:00:00.0000 00
N/A Y
SUBT0002 00:00:00.0001 00:00:00.0000 00:00:00.0000 00:00:00.0000 00
N/A Y
SUBT0003 00:00:00.0000 00:00:00.0000 00:00:00.0000 00:00:00.0000 N/A
N/A Y
SUBT0004 00:00:00.0000 00:00:00.0001 00:00:00.0000 00:00:00.0001 N/A
100 Y
SUBT0005 00:00:00.0000 00:00:00.0183 00:00:00.0000 00:00:00.0180 N/A
98 Y
SUBT0006 00:00:00.0149 00:00:01.6460 00:00:00.0113 00:00:01.6077 75
97 Y
SUBT0007 00:00:00.7672 00:02:05.0245 00:00:00.5685 00:02:02.6041 74
98 Y
SUBT0008 00:00:20.5983 01:03:33.8557 00:00:16.8550 01:02:27.3845 81
98 Y
SUBT0009 00:01:27.7680 03:56:32.8645 00:01:13.5999 03:54:26.2755 83
99 Y
SUBT0010 00:08:21.4708 15:29:31.2295 00:06:44.2907 15:32:01.1725 80
100 Y
-------- -------------- -------------- -------------- -------------- ---
---
Totals 00:10:14.9959 20:31:44.7070 00:08:16.3976 20:30:59.1373 80
99


to be honest - it will take me a while to digest all this to determine
what this means - but our perf/tuning folks tell me that IDMS is
exploiting zIIP more than any other WLM group on the LPAR ...(DDF is a
not-so-close second ...)

Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
choelscher@humana.com




The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: IDMS 17 & zIIP
"Chris, two questions come to mind.

1. How many engines are available to the LPAR where this=20
system runs?
2. How do your stats look running at 3 subtasks ?


Hal Govan
Senior Database Administrator
Reed Elsevier - Technology Services
harold.govan@reedelsevier.com
Phone: (937) 865-7820

Outcomes