You need to complain to ASG and push for better behavior on the use of
SCOPE=COMMON data spaces as do I.
On this system which has 35 SCOPE=COMMON data spaces in use 9 are from
ASG/TMON :-(
MXI - DSP -- BSYS - HOME ----- CPU 43 UIC 2540 PAG 0 ---------- Row 1 of
36
Command ===> Scroll ===>
CSR
CADS=36/77
Name Jobname ASID ASCB ASTE SToken Scope
$HUBL#01 LSSHUBRB 00B7 00F43700 04CFFE00 80008A0000000E09 COMMON 1
$HUBLSS2 LSSHUBB 04C5 00F57280 04CFFF00 80007D0000000E04 COMMON 2
$MDSL#01 LSSHUBRB 00B7 00F43700 04D00280 8000830000000E07 COMMON 3
$MDSLSS2 LSSHUBB 04C5 00F57280 04D00000 80007E0000000E02 COMMON 4
CNZSCLOT CONSOLE 000A 00F3E080 04CFF780 80002F0000000031 COMMON
CNZSCMDB CONSOLE 000A 00F3E080 04CFF800 8000300000000032 COMMON
CSM31002 *MASTER* 0001 00FCB780 04D00100 80009F0000000164 COMMON
CSM64001 *MASTER* 0001 00FCB780 04D00080 80009E0000000163 COMMON
CSVRTLS *MASTER* 0001 00FCB780 04CFF700 80002E0000000030 COMMON
CUNDS001 *MASTER* 0001 00FCB780 04CFFA80 8000020200000002 COMMON
DAT1CMSB EYUX310 00BA 00EA9680 04D00400 80004603000000A4 COMMON
DMDSCMSB EYUX310 00BA 00EA9680 04D00300 80004503000000A1 COMMON
EPWFDSPC EPWFFST 004A 00EAC580 04CFFC80 80003A010000003B COMMON
EPWPDSPC EPWFFST 004A 00EAC580 04CFFC00 8000120200000012 COMMON
EPWS76QU EPWFFST 004A 00EAC580 04CFFD00 80003B010000003C COMMON
IEAM000A CONSOLE 000A 00F3E080 04CFF880 8000370000000039 COMMON
IEECMCAD *MASTER* 0001 00FCB780 04CFF900 800038000000003A COMMON
ISTF52BF NET 0064 00F34A00 04D00180 8000A50000000194 COMMON
IXLCTCAD XCFAS 0006 00FA6200 04CFF580 8000100000000010 COMMON
LMRKL#01 LSSHUBRB 00B7 00F43700 04CFFD80 8000800000000E08 COMMON 5
LMRKLSS2 LSSHUBB 04C5 00F57280 04CFFF80 8000820000000E03 COMMON 6
MAS1CMSB EYUX310 00BA 00EA9680 04D00480 80004903000000AD COMMON
QUE1CMSB EYUX310 00BA 00EA9680 04D00380 8000510300003B0D COMMON
SYSANTMN ANTMAIN 000C 00F93280 04CFFB00 8000050200000005 COMMON
SYSANT00 ANTAS000 000D 00F93100 04CFFB80 8000060200000006 COMMON
SYSBMFDS SMSPDSE 0008 00FA6E80 04CFF680 80002C000000002E COMMON
SYSCOMDS *MASTER* 0001 00FCB780 04CFF500 8000010000000001 COMMON
SYSZBPXX OMVS 000E 00F65500 04CFFA00 8000390000000040 COMMON
SYSZBPX1 OMVS 000E 00F65500 04CFF980 80003A000000003F COMMON
SYSZILM1 *MASTER* 0001 00FCB780 04CFF600 80002B000000002D COMMON
TCPIPDS1 TCPB1 00A3 00F43880 04D00200 8000DB00000001F3 COMMON
TIMSLOGC TIMB 0155 00AB7700 04D00680 80000B02000068FC COMMON 7
TMDBPKGS TDBB 00F3 00F45E80 04D00600 80003903000035B1 COMMON 8
TMDBSQLC TDBB 00F3 00F45E80 04CFFE80 80001B03000035B0 COMMON 9
TOP1CMSB EYUX310 00BA 00EA9680 04D00500 8000620300003B11 COMMON
WLM1CMSB EYUX310 00BA 00EA9680 04D00580 80009E030000018B COMMON
We need to complain loudly to vendors who use more than one.
SCOPE=COMMON data spaces are like everlasting gobstoppers one should be
enough for anyone.
You might take a list of all the TMON data spaces to ASG and raise an issue
with the use of multiple ones as causing you an outage to get it increased.
It will only get fixed if customers complain loud and long about the issue.
The TMON hub needs 3 it would be nice if it was reworked to only use 1.
TMON is hardly the only piggish product in this respect. I think that
products using ESA facilities instead of common storage is great but in most
cases I think it is fair to ask them to restrict themselves to one
SCOPE=COMMON and then as many SCOPE=ALL or SCOPE=SINGLE data spaces as they
need. If you assume the main reason for using SCOPE=COMMON is data access
and exchange with potentially any address space in the system then do you
really need more than 2G of space for that? Reasons cited in the past by
some developers for multiple SCOPE=COMMON spaces were RAS with isolation of
various component code. I am sure there are some valid reasons but mostly
ISVs don't appreciate the nuisance that increasing something like this and
arranging IPLs can be for customers it sneaks up on.
This would be another area where z/OS probably needs a warning message. A
highlighted warning WTO when you get down to some threshold of CADS
available to allocate would warn customers sufficiently in advance to
increase this on the next planned IPL before trying to install software that
would not fit.
Best Regards,
Sam Knutson, GEICO
Performance and Availability Management
mailto:[EMAIL PROTECTED]
(office) 301.986.3574
"Think big, act bold, start simple, grow fast..."
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Jon Brock
Sent: Friday, August 05, 2005 3:47 PM
To: [email protected]
Subject: Re: $HASP473
So did we. It requires a change to MAXCAD and an IPL to fix.
Jon
<snip>
We had the same problem with T<ON and LSSHUB </snip>
<>
====================
This email/fax message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution of this email/fax is prohibited. If
you are not the intended recipient, please destroy all paper and electronic
copies of the original message.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
