[mailto:[EMAIL PROTECTED] On Behalf Of Greg Dyck
Sent: Wednesday, September 07, 2005 12:24 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: VSMLIST OWNCOMM DETAIL
Tnx Greg, I always just ask for a FIN APAR.
*System owned is much better then Batch Job owner gone.
FIN must *only* be used for an APAR which
DB2 open PK10031 and close it with the following comment:
snip
This apar is being closed USE ( user error ). Users should
not be using MVS service aid information as a basis for direct
commands against storage. The actual reporting of DB2 storage
as 'orphaned' is considered an inaccuracy
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Greg Dyck
Sent: Tuesday, September 06, 2005 12:12 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: VSMLIST OWNCOMM DETAIL
DB2 open PK10031 and close it with the following comment:
snip
This apar
Subject: Re: VSMLIST OWNCOMM DETAIL
DB2 open PK10031 and close it with the following comment:
snip
This apar is being closed USE ( user error ). Users should
not be using MVS service aid information as a basis for direct
commands against storage. The actual reporting of DB2 storage
Tnx Greg, I always just ask for a FIN APAR.
*System owned is much better then Batch Job owner gone.
FIN must *only* be used for an APAR which IBM is prepared to ship the code
via service. Any customer may request a new APAR be opened to ship the fix
for a FIN APAR.
The only accepable closing
Is there a reason this cannot be tied to a DB2 address space that will
clean
it up when it terminates?
snip
Some of the global storage can be obtained *before* switching to a DB2 owned
address space so there is no way to show it owned by DB2 as would be
desired. The same issue exists for MQ
Status about my Owner Gone project with low prio.
Websphere MQ (IBM Hursley) is still working on this.
DB2 open PK10031 and close it with the following comment:
Various monitor programs and displays, report common storage
owned by DB2 as 'orphaned'. This occurs because the MVS service
for WMQ is still open but it seem to be same problem
(HASN PASN). Awaiting results
RRS accept a fin APAR OW57028 and fixed it in z/OS R5.
Non IBM products
StorageTek V5. Verify with new version
At least VSMLIST OWNCOMM DETAIL should be free of OD Owner Gone
storage even it`s not a really orpan
An: IBM-MAIN@BAMA.UA.EDU
Betreff: Re: VSMLIST OWNCOMM DETAIL
Is OG orphaned storage (Memory leak) or still owned by someone?
The owner is always the owner assigned when the storage was obtained. OG is far
from always being orphaned. It just might be misclassified. If you get
storage
Is OG orphaned storage (Memory leak) or still owned by someone?
The owner is always the owner assigned when the storage was obtained. OG is
far from always being orphaned. It just might be misclassified. If you
get storage and terminate and expect to use that storage later then you
ought to be
Is OG orphaned storage (Memory leak) or still owned by someone?
Our list of OG storage contains a lot of entries and I
believe they are still owned by someone.
Owner Gone might be a storage leak, or it might be storage
that contains code, data, control blocks yada yada, for products
that
CC said;
That's a good reason not to use the FREEMAIN option of products
(like ours and Tivoli/Candle) that offer a point and shoot shortcut
to your next unplanned IPL.
Had a junior do that once - even got a warning message that the storage had
changed and did he *REALLY* want to still delete
Since Shane's junior did in fact own up to his sins, it was appropriate not
to use thumb screws on that occasion.
About certain ISVs who use single short-lived ASs to start subsystems, I'm
more ambivalent; maybe thumb screws would be appropriate for them. The
'wasted' ASIDs are now
[mailto:[EMAIL PROTECTED] Im Auftrag von
john gilmore
Gesendet: Montag, 18. Juli 2005 01:01
An: IBM-MAIN@BAMA.UA.EDU
Betreff: Re: VSMLIST OWNCOMM DETAIL
Since Shane's junior did in fact own up to his sins, it was appropriate not to
use thumb screws on that occasion.
About certain ISVs who use single
Is OG orphaned storage (Memory leak) or still owned by someone?
Our list of OG storage contains a lot of entries and I believe they are still
owned by someone.
How did you handle them? Did you ask the ISV or IBM about them?
I've seen a large for RRS and IBM raise FIN APAR OW57028.
I now have
15 matches
Mail list logo
