I am having some trouble understanding the documentation on COBOL LE
multiple enclave support. We have this turned off at present. Can
someone tell me what kind of situations would see a big benefit from
turning it on?
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
Available PAGE Ranges
"A colleague created this nice utility to graphically see your page gaps.
The JCL and explanation of the utility is found on his web site:
http://itdoesmorestuff.com/freeutils.htm. There's quite a few steps to
execute but the graph at the end makes it very easy to see where you
have gaps in a quick glance. This is always the first step I run before I
do an expansion.
symbol. This makes it very easy to see where your biggest areas lie, and
where the page-ranges gaps are.
Rose Kimlingen
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP
Normal
Normal
CA in the news
"Ex-Computer Associates CEO Pleads Guilty
Source: Associated Press/AP Online
Publication date: 2006-04-24
By TOM HAYS
NEW YORK - Sanjay Kumar, the former CEO of _Computer Associates
International Inc._
(https://www.suntrust.com/portal/server.pt/gateway/PTARGS_0_302319_246_0_0_43/http;/portlet-ice.suntrust.com/Portlets/YbxNews/coOverview.nsp?coID=249
&ID=suntrustdemo&scategory=Computers&) , and another former executive pleaded
guilty on Monday to obstruction of justice and securities fraud charges in a
massive accounting scandal at the business software company.
Kumar and Stephen Richards, its former head of worldwide sales, had been
accused in a 2004 indictment of engaged in a widespread scheme to falsely
inflate the company's quarterly earnings by backdating contracts.
According to the indictment, Kumar was so involved with adding revenue to a
financial quarter even after it closed that he flew to Paris in July 1999 to
finalize a deal and personally signed a contract that had been backdated.
The indictment also charged that executives instructed salespeople to
complete deals after the quarter had closed and ""cleaned up"" contracts by removing
time stamps from faxes.
""Your honor, my conduct was wrong. I take responsibility for participating in
this practice and I apologize for my actions,"" Kumar told the judge,
referring to the accounting fraud.
Richards pleaded guilty to the same charges in federal court in Brooklyn.
Both remain free on $5 million bond while awaiting their Sept. 12 sentencing.
The law allows a maximum sentence of 20 years in prison for the offenses,
but the term could be substantially less under federal sentencing guidelines.
Kumar is also a co-owner of the New York Islanders hockey team.
Computer Associates, which makes software and storage systems for large
corporations, agreed in 2004 to pay $225 million to shareholders in a settlement
letting it defer criminal prosecution.
The Islandia, N.Y.-based company restated its financial results from 2000 and
2001 to reflect $2.2 billion in revenue that was improperly booked.
During the company's fiscal year 2000, Computer Associates ""prematurely
recognized"" more than $1.4 billion in revenue from at least 116 contracts that
had not yet been signed, the Securities and Exchange Commission said.
Publication date: 2006-04-24
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP
Normal
Normal
CPU on IDMS 16.0/2/3
"Hi,
The last update to TB96715 was March 17th. Is this the final version and
will there be a version for 16.0 SP0/SP1?
Thanks
Chris Wood
Alberta Department of Energy
CANADA
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP
Normal
Normal
Re: CPU on IDMS 16.0/2/3
"Chris -
The March 17th version will be the final version of TB96715.
My issue with C.A. is now closed which means they will make this into a
published APAR.
A substantial (more than 1/2) of the increase appears to be due to these 4
related APARS:
LO17595
LO41352
LO52345
LO92953
I can't tell you if one or more represents the lion's share.
I have been told they should all be considered as a group.
These APARS are all sourced and C.A. has said they have no intention of
backing off APARS that fix known problems in favor of performance.
Therefore, I think we've gone as far as we can go with this issue.
I've asked 3 times if there will be an SP0 / SP1 version and never got a
direct answer.
I can only assume there will be because all published APARS I've looked at
have multiple versions for the various service packs.
Thanks.
Jon Gocher
Original Message -----
From: ""Chris Wood"" <Chris.Wood@GOV.AB.CA>
To: <IDMS-L@LISTSERV.IUASSN.COM>
Sent: Tuesday, April 25, 2006 11:52 AM
Subject: CPU on IDMS 16.0/2/3
Hi,
The last update to TB96715 was March 17th. Is this the final version and
will there be a version for 16.0 SP0/SP1?
Thanks
Chris Wood
Alberta Department of Energy
CANADA
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP
Normal
Normal
FW: ? related to Storage allocation in R16
"When we first upgraded to R16 on our largest CV we began noticing the new
SOS message (DC015007) showing up in the log for pool 255, but discovered
that the SOS counter in the 'DCMT D ALL STO POOL' display did not have any
record of pools having gone SOS. I suspected that it was because the
request for storage was too large for the pool and I wondered if a request
for storage had to 'violate' the cushion for a pool to be marked SOS in the
DCMT display. I asked that question of John Siraco at the IUA conference in
Dallas and below is his response. Thanks John!
One other thing we discovered was an apar related to these new SOS messages
and if you don't have it applied, you might want to look into it. The apar
is QO74800.
Linda Campbell
Informatix, Inc.
linda.campbell@informatixinc.com
_____
From: Siraco, John A [mailTo:John.Siraco@ca.com]
Sent: Wednesday, April 26, 2006 11:41 AM
To: Linda Campbell
Subject: ? related to Storage allocation
Hi Linda,
You had asked a question related to storage allocation at the IUA meeting in
Dallas. I believe you said there was a situation where a storage request was
larger than the amount of storage available in a pool yet there was no
indication that the getstg didn't work and the SOS count was not
incremented. I've just spent some time going through the 16.0 storage
manager. I can see where when the storage does not fit in the pools the SOS
flag would not be set but it looks to me that you should always receive at
least 1 message per storage pool which is capable of servicing the request.
During pass 2, the storage manager first checks to see if the pool size
is large enough to satisfy the request. If the pool is not large enough to
handle the request
a WTO is issued (xx015007). I guess it would be possible to miss this
message if the Route Codes setup within IDMS are not quite correct.
This is done for each pool capable of satisfying the request. In
this case the SCTSOS flag (Pool is sos would not be set).
If a pool is large enough to handle the storage request he then checks
to see if there are enough available pages in the pool to handle the
request. The same process
is repeated. If there are not enough available pages the WTO would be
displayed and the SOS flag for the pool would not be set.
For both of these cases, if the GETSTG was a conditional request, a
Return Code 8 would be returned to the caller. Otherwise, an IDMS #wait
would be issued and
the task would be waiting on SMTECB.
Next. If there were enough available pages in the pool to handle the
request we search for the contiguous space to satisfy the request. If not
found we would WTO a
message as documented above and the SOS pool flag would not be set.
If we found enough contiguous space we would then allocate the storage,
increment the # of pages in use, then compare the # in use to the Size of
the pool
minus the cushion.
If we used the cushion a WTO would be issued and we would set the SOS in
the pool flag.
Let me know if this answers your question or if you would like me to do some
more research on this.
Thanks
John A Siraco
CA
Principal Support Engineer
tel: +1 508 628-8247
fax: +1 508 628-8715
john.siraco@ca.com
_____
From: Linda Campbell [mailTo:linda.campbell@informatixinc.com]
Sent: Monday, March 07, 2005 1:59 PM
To: Siraco, John A; Torretto, Roseanna@HHSDC
Subject: RE: RMF Monitor III reports while HWIDMP43 was assigned to SYSSTC
on 02/25/2005
Hi John,
No. Roseanna defined a separate service class that only contains this one
CV with a velocity of 90, but it runs below SYSSTC. The numbers are about
5% better than the prior set of reports, but still not in line with what we
would expect with a velocity of 90.
Linda