Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

CMBS shortage - HASP050

410 views
Skip to first unread message

jagadishan perumal

unread,
Dec 29, 2012, 9:51:45 AM12/29/12
to
Hello Group,
 
One of our test Box is encountering shortage of CMBS. This test system is being used voraciously for variuous testing activities and understanding the situation we have kept the BUFNUM and BUFFREE to the max but still there is no improvement. After doing a search I found a very good link which gives more insight about shortage of CMBS. Even the system is designed in such a way that console buffers get written to the console and the syslog but still we are having a CMBS shortage.
 
 
Z/OS : 1.13
 
Apart from the above approach are there any other alternative which can help me to do a research.
--
Regards,
Jags

Lizette Koehler

unread,
Dec 29, 2012, 10:20:07 AM12/29/12
to
Jags,

Have you tried the JD commands to understand when you are having issues?
It might be a specific time or trend. Is the system getting a lot of JES2
commands being issued that is causing the CMBS to grow? I think CMBS is due
to JES2 commands rather than workload.

Lizette

Lizette Koehler

unread,
Dec 29, 2012, 10:31:18 AM12/29/12
to
Jags

The other thought that crossed my mind was JES2 Exits.

Do you have any coded and which ones are they? Do you use the $WTO?

From the JES2 manual:

$WTO PARAMETER LIST ERROR symptom records can be caused by problems in JES2
or in JES2 installation exits. Possible causes include the incorrect use of
$WTO, $WTOR and $BLDMSG macro instructions and related data, or the
incorrect manipulation of a $CMB data area by a JES2 installation exit 10
routine. Typically, multiple $WTO PARAMETER LIST ERROR symptom records are
created for a given type of problem. Format log data from the logrec data
set using EREP and search for "$WTO PARAMETER LIST ERROR". See the EREP
User's Guide for more information on formatting the log data set.

JES2 validates the $WTO parameter list at key points in JES2 processing and
creates a $WTO PARAMETER LIST ERROR symptom record if it discovers an error.
Additionally, JES2 corrects some errors. However, JES2 cannot detect or
correct every possible error. Some errors cause problems in later
processing, including causing JES2 to place CMBs on a queue where they could
remain indefinitely. In some cases, this may result in a $HASP050 resource
shortage message for CMBs. See Resource shortages for more information on
handling resource shortages.

Lizette


> -----Original Message-----
> From: JES2 discussion group [mailto:JES...@listserv.vt.edu] On Behalf Of
jagadishan
> perumal
> Sent: Saturday, December 29, 2012 7:51 AM
> To: JES...@LISTSERV.VT.EDU
> Subject: CMBS shortage - HASP050
>
> --f46d0402df88de195204d1fee96c
> Content-Type: text/plain; charset=ISO-8859-1

jagadishan perumal

unread,
Dec 29, 2012, 12:19:52 PM12/29/12
to
Hi Lizzette,
 
Thanks but I am not sure if $WTO exits are installed. I will definetly try with EREP report to see if I I could nail down certain problems.
 
Jags

--
Regards,
Jagadishan

jagadishan perumal

unread,
Jan 1, 2013, 9:35:09 AM1/1/13
to
Hi,
 
CMB queue seems to be good. Finally understood that everyday almost 7000 thousand Jobs are purged and which inturn has caused the CMB shortage.(Based on the output Class).
 
Jags

--
Regards,
Jagadishan
0 new messages