ca.portal.admin

Re: Max tasks

Discussion created by ca.portal.admin on Apr 25, 2008
yes - there is a formula - CA has passed around in years past - there
may even be a PIB on this

basically it assigned tasks for certain components (whether you have
them or not) - adds tasks for LINES and PRUs - to come up with the
recommended total

i will try to find this amoungst my other ""stuff""





This is Chris Hoelscher and I approved this email
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Max tasks revealed
"(this is old, but may still hold true)

GI16001


SYSGEN statements provide the initial value loaded into the MAXTASKS
field at startup time. The MAX-TASKS2-170 field is read from the
SYSMO-170 record by module RHDCBLD3 and moved into the OPTMAXT field.
This field will later be moved to TCANTASK from which the number of
TCEs will be allocated.
The SYSMO-170 record is built by SYSGEN generate. The value in field
MAX-TASKS2-170 is arrived at as follows:
1) Value on SYSTEM statement for MAXIMUM ERUS IS
2) Value on SYSTEM statement for MAXIMUM TASKS IS
3) Addition of +2 for MASTER and DBRC tasks
4) Add in the number of ADD LINE statements for line drivers!
5) Subtract 1 for each LINE statemnt that is for a CONSOLE line.

The total of these values is then stored in the SYSMO-170 record
in field MAX-TASKS2-170 which is the initial value stored in the
OPTMAXT field by RHDCBLD3.

After this value is stored in the OPTMAXT field, we process as follows:

In module RHDCBLD1, there is a routine BLDSDC. For each SDC we build,
we increment the MAXTASKS by 1. The process follows.

MAXTASKS first is incremented by one (1) for any SWITCH SERVICE DRIVER
(RHDCSWIT - (banking systems only)) defined to the system. MAXTASKS is
then incremented for each RUN UNIT SERVICE DRIVER (RHDCRUSD), these
service driver control blocks are for QUEUE, LOADER, MSGDICT, SIGNON,
SYSDEF(DEST), DDLDML SOURCE, USER, SCRATCH MANAGEMENT, SQL LOADER,
SQL SECURITY, SYSTEM SECURITY, and APPLICATION DICTIONARY rununits that
may be defined in the SYSGEN.
NOTE: These SDCs are built and MAXTASKS is incremented for each SDC
built even if the SYSGEN does not contain a definition for those
type of rununits!! There are twelve (12) SDCs built and thus,
MAXTASKS is incremented by twelve (12). If you only have RUNUNITS
statements in the SYSGEN SYSTEM statement for 6 types of RUNUNITS,
the system still has 12 preallocated TCEs. Six (6) will be used
by RHDCRUSD tasks. The other six (6) will be available in the TCE
pool for USER tasks. This effectively makes the MAXIMUM TASK IS
statement in the SYSGEN less than the real value available for
user tasks by six (6).
(*NOTE2 - In release 10.2x, there were only 6 possible SDC blocks)

EXAMPLE: Startup automatically increments OPTMAXT for 12 possible
RHDCRUSD tasks. (OPTMAXT is the cv's initial MAXTASKS field)
In your sysgen SYSTEM statement you have defined the following:
1 RUNUNITS FOR LOADER = 2
2 RUNUNITS FOR SECURITY = 1
3 RUNUNITS FOR SIGNON = 1
4 RUNUNITS FOR MSGDICT = 2
5 RUNUNITS FOR QUEUE = 2
6 RUNUNITS FOR SYSTEM/DEST = 2
The MAXTASKS field is automatically incremented by 12 but the SYSGEN
has only defined six (6) types of rununits. Since MAXTASKS has been
incremented by six (6) more than the number you have used, the extra
six (6) TCEs allocated as a result of the MAXTASKS value now become
available for USER tasks! BE AWARE OF THIS FOR FINELY TUNED SYSTEMS!

----------------------------------------------------------------------
MAXTASKS will next be incremented for each LOG SERVICE DRIVER (RHDCLGSD)
defined to the system. DEFAULT is 3 for MVS and 1 for all other
operating systems.
----------------------------------------------------------------------
MAXTASKS next are incremented for PERFMON SDCs which are always built
even if perfmon is not installed. SDCs are built before the NLT is
filled in, or before we know if PERFMON is installed. The number of
PERFMON service drivers is two (2). (PMONCIOD and PMONCROL)
----------------------------------------------------------------------
MAXTASKS is now incremented for the DEADLOCK DETECTION SERVICE DRIVER.
The number of DEADLOCK DETECTION SERVICE DRIVERS increment is (2).
(RHDCDEAD)
----------------------------------------------------------------------

At this point, the MAXTASK (OPTMAXT) field is set at a number that will
be the number of TCEs allocated at startup time.
The number of MAXTASKS incremented in a Release 12.0 CV is as follows:
* MAXTASKS from SYSMO-170 record (SYSGEN record).
Number of MAXIMUM TASKS on system statement
Number of MAXIMUM ERUS on system statement
Number of LINE statements in sysgen
Add +2 for MASTER task and DBRC task
Subtract one for each CONSOLE line defined in sysgen
* MAXTASKS from RHDCBLD1 at startup time
Number of SDC control blocks allocated for RU Service Drivers = 12
Number of SDC control blocks for PERFMON DRIVERS = 2
Number of SDC control blocks for LOG SERVICE DRIVERS = 3 for MVS
LOG SERVICE DRIVERS = 1 for non-MVS
Allocation for DEADLOCK DETECTION SERVICE DRIVER = 2
* Total MAXTASKS from RHDCBLD1 for an MVS system is nineteen (19)

When the CV comes up, the TCANTASK field is used to allocate the number
of TCEs we will allocate for the system. If we VARY the MAX TASKS the
OPTMAXT field will by updated and this value is used to control the
number of MAX TASKS that will run on the CA-IDMS CV. The number of MAX
TASKS varied can NOT be greater than the value in the TCANTASK field!































This is Chris Hoelscher and I approved this email
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
One program One queue Two Schemas in One CV
"Hi,

Help!
I have a problem that needs a simple (or very little programming)
solution. If not possible, I believe, our other course is to use two
CVs.

Current environmSent:
1. ADS/DC-COBOL writes to a trigger queue. (we have about 10 of these
situations)
2. Queue-QA starts associated ""non-terminal"" Task-TA which initiates
associated Program-PA
3. Same with Queue-QB
4. With a necessary and complex evil, we have two projects in
development which require separate Database schemas till August, when
they can be combined. (Don't go there... Please!)
4. Both projects will use most of the, approx. 10, trigger queues
5. Program PA needs to access Database Version-D1, and, you guessed it,
PB needs to access D2. That is, trigger initiated programs need to see
their version (schema changes) of the database.
6. The queue record contains the database name and can be used to choose
the correct version of the queue initiated DC-COBOL load module compiled
against the appropriate dictionary/subschema.
7. Source between PA and PB is currently different, but, someday,
hopefully in the fall, will be the same again.

Problem:
1. Current environment exists and works well.
2. Is it possible for CV to choose correctly from two DC-COBOL programs
with the same name from a non-terminal task
3. It appears that DCUF SET TEST is not available in this environment.
3. I believe a non-terminal task does not maintain user info, such as,
DICTNAME or DBNAME.
4. There are versions in queues, but, my reading seems to indicate only
one version can be used by CV.
5. And worse, some of these DC-COBOLs start a SET TIMER to re-inititiate
themselves if failure occurs during the process. One in particular is
continuously re-starting at set intervals.

Again, just in case I missed a feature or lack the brain power, does
anyone see an alternative, rather than a second CV.

Just for infTo:
I have already designed a ""traffic cop"" type program which will be
started by each queue, but it requires maintaining two programs for each
DC-COBOL with different internal and external names and queue
references, etc.
But, again. It's deemed not worth the effort compared to using another
CV till the Fall of this year.

I hope I explained this problem sufficiently!


Take Care,
Bruce
Office: (717) 605-2019
Cell: (610) 468-9506
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Max tasks revealed
"Thanks to Chris and Bill - that is what I was looking for.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
IDMS 16.0 upgrade gets s800
"Has anyone on 16.0 experienced S800 abends in the condense step of the
journal offload jobs? Or any S800's at all?

Lutz Petzold
TDM UDB/IDMS Support
Monday, Tuesday, Friday 401 782 2265
Wednesday, Thursday 860 636 0291
Page 860 366 0865 or Telalert



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: IDMS 16.0 upgrade gets s800
"Sometimes this can be caused by:

1. A lack of storage for job
2. Using invalid unit type.


Rob Klan/Cincinnati/IBM
Phone: 1-877-205-4871 (T/L: 349-2446)
VOIP Users 1-513-897-8148
ITN: 23492446
Email: rklan@us.ibm.com



""Petzold, Lutz"" <PetzoldL@AETNA.COM>
Sent by: IDMS Public Discussion Forum <IDMS-L@LISTSERV.IUASSN.COM>
04/29/2008 08:13 AM
Please respond to
IDMS Public Discussion Forum <IDMS-L@LISTSERV.IUASSN.COM>


To
IDMS-L@LISTSERV.IUASSN.COM
cc

Subject
Re: IDMS 16.0 upgrade gets s800






Hi Steve, thanks for responding. The reason code is a 1.

SYSTEM COMPLETION CODE=800 REASON CODE=00000001



Lutz Petzold
TDM UDB/IDMS Support
Monday, Tuesday, Friday 401 782 2265
Wednesday, Thursday 860 636 0291
Page 860 366 0865 or Telalert



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: IDMS 16.0 upgrade gets s800
"Some info on a s800 abend:

800

Explanation: During processing of an I/O request, execute channel program
(EXCP) processing encountered an error. Each X'800' abend code has a
reason code that explains the error:

Code Explanation

1 An error occurred during indirect address word (IDAW) or channel
command word (CCW) validity check processing. An access
protection error occurred when:

o The EXCP IDAW routine tried to access the IDAW using an
incorrect storage protection key.
o The EXCP CCW validity check routine tried to access the
virtual channel program using an incorrect storage
protection key.
o The channel program attempted to execute a restricted
operation. An access protection error can occur when there
is an error in the channel program. Correct the channel
program.


Peter van de Ven Atos Origin

* Tel: +31(0)40 2142211 +31(0)622567218
* Fax: +31(0)402144423


ü 51 25' 43.86"" 5 31'50.36""

Outcomes