In short yes, the system will be maxed out. So I think I am understanding
the problem, and I think it's not a problem.
---------------------------------------------
Is this a single system or a sysplex? ===> Single
What is CPU utilization like at the time? ===> Surely 100% and things are
waiting
How many engines are on the LPAR? ===> One
are you using JES2 inits and running
everything you can at once or using
WLM inits ===> JES2
What OS version are you running? ===> z/OS 1.5
---------------------------------------------
David Logan
Product Manager, Pitney Bowes Software
http://centrus.com
4750 Walnut St, Suite 200
Boulder, CO 80301
W: (720) 564-3056
C: (303) 818-8222
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Mark Zelden
Sent: Friday, February 29, 2008 7:30 AM
To: [email protected]
Subject: Re: Mysterious PDSE errors
On Fri, 29 Feb 2008 06:47:41 -0700, David Logan <[EMAIL PROTECTED]>
wrote:
>I run nightly builds using PDSE source datasets, object datasets and list
>datasets. In SYSLOG, I get the text below. Notice also that in this
>particular case, I issued the "recommended" command, and I get no useful
>results. I also get nothing whatsoever in any of the batch jobs as far as
>error/warning/informational messages.
>
>Any suggestions? Should I simply turn off monitoring?
>
>-------------------------------------------------------------
>00000090 *IGW038A Possible PDSE Problem(s) 132
>00000090 Recommend issuing V SMS,PDSE,ANALYSIS
>00000090 *IGW038A Possible PDSE Problem(s) 133
>00000090 Recommend issuing V SMS,PDSE,ANALYSIS
>00000290 V SMS,PDSE,ANALYSIS
>00000090 IGW031I PDSE ANALYSIS Start of Report 135
>00000090 ++ no exceptional data set conditions detected
>00000090 PDSE ANALYSIS End of Report
>-------------------------------------------------------------
>
Is this a single system or a sysplex?
What is CPU utilization like at the time? How many engines are on the
LPAR?
I ask because I have seen these messages caused by latches being held
too long due to lack of CPU cycles. If this is the case perhaps run less
jobs
at once (are you using JES2 inits and running everything you can at once or
using WLM inits).
What OS version are you running? If this is a CPU cycle issue and you are
running z/OS 1.7 or z/OS 1.8 the WLM "Blocked Workload Support" PTFs
may help - APAR OA17735. The support is included in base z/OS 1.9.
Take a console dump or set a slip on IGW038A and open a PMR with
IBM DFSMS support. This could be your first course of action if you
so desire.
Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[EMAIL PROTECTED]
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
