ca.portal.admin

Re: Tab order in map

Discussion created by ca.portal.admin on Feb 24, 2005
If I read your question right, tabbing will always go left to right to
the next unprotected field.


----- Original message -----
From: ""Babija Paulose"" <babija.paulose@WIPRO.COM>
To: IDMS-L@LISTSERV.IUASSN.COM
Date: Thu, 24 Feb 2005 21:23:14 +0530
Subject: Tab order in map

How do we set the tab order in a map ?




Confidentiality Notice

The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of the addressee(s)
and may contain confidential or privileged information. If you are not
the intended recipient, please notify the sender at Wipro or
Mailadmin@wipro.com immediately and destroy all copies of this message
and any attachments.



Confidentiality Notice


The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin@wipro.com immediately
and destroy all copies of this message and any attachments.

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








Normal

Normal
Re: ABEND 1473 AND SYSGEN PARMS
"In an ideal world CICS and IDMS would be matched. The MAX ERUS parameter
would be equal to the sum of the max tasks in all the CICS regions + the
number of TSO sessions that can communicate with the IDMS region. However we
don't live in an ideal world.

MAX TASK in the sysgen is the maximum number of IDMS tasks you allow in your
idms region other than erus. The 2 values have no relation to each other.
IDMS uses MAX TASK + MAXERUS + 1 per line + DBRC + MSTR + 1 per line used
for OPS console to calculate the number of TCE to allocate.

Max ERUS in the sysgen is used by the CV at startup to allocate the number
of ERE. According to the manuals it should be what you allow from CICS +
what you allow from TSO + 10 to 20% of the ucf terminal defined in the
sysgen.

Typically in a CICS/IDMS environment 95% of your run units would come from
CICS. If you define MAX ERUS as the sum of all the max task defined in all
the CICS regions that can communicate with that CV you should not have 1473
anymore.

However CA recommends to have a low value for MAXERUS and MAXTASKS. This is
to avoid walking long chains in IDMS and improve performance. We have our
MAXERUS set at 200. When we tried to set it lower there was minimal
performance gain when the system was running warm. However when we hit the
peak day time volume we would get hundreds of 1473s. We decided that a
higher number was best for us. (Contrary to what the manual says you can't
always have MAXERUS 255. The ERE area is 64K in size and if you are using
the ERE extension that makes the ERE 272 bytes. So can only have 240 in
MAXERUS).

You can get 1473 abends in many ways. By the way that abend is so
misleading. You can have 1473 even if you never reached MAXERUS in your
systems statistics display. A tasks coming from CICS gets assigned an ERE.
Until IDMS recognise that it exists the maxerus count is not updated. If you
have a burst of tasks coming in through MACROS or something, all the EREs
will be taken, you will get 1473 abends and maxerus will be close to but not
at the maximum. We get this on a regular basis.

Another reason for 1473 is any type of slowdown in IDMS. For example someone
locking the MVS catalog while IDMS tries to open a file. The CICS tasks keep
coming but IDMS isn't processing anything while waiting for the file OPEN
MVS command. =1473.

If you have a small amount of MVS XA storage on your mainframe you will
incur a lot of MVS paging. MVS will temporarily write to disk pages from
memory that have not been accessed for a while to make room for other MVS
tasks. If this happens to storage used by the CV and the CV needs it for a
task, same as above. CICS keeps filling the ERE, IDMS processing is waiting
for the page IN and you get 1473.

Be aware that some MVS function performed on behalf of IDMS are single
threaded. This means the CV waits until the action is completed. The
solution to fix 1473 abends is not necessarily within the IDMS software.

As a rule I would suggest that you set the MAXIMUM ERUS parameter high.
Monitor the usage over a period of time and reduce the number to the average
high water mark + 10%. In my the small difference in CPU used by the CV
because of the larger value for MAXIMUM ERUS is better than dealing with the
political consequences of the 1473 abends.

If you have questions you can email me directly. En français si tu préfères.


Jacques Dumouchel
CCRA-ADRC
Ottawa On canada.

Jacques.dumouchel@ccra-adrc.gc.ca

Outcomes