Thanks for reply .I checked this link before. But issue is, how do I know
 that do I have any SYSPLEX dump directory defined on my system or not. Any
display command. Because  I don't find any dataset SYS1.DDIR with this name
etc.  Currently we are at z/OS 2.1




On Mon, Jun 9, 2014 at 7:45 PM, Lizette Koehler <[email protected]>
wrote:

> You did not mention the release of z/OS you are on.
>
> Next, the DAE dataset is not what is the problem
>
> Creating the sysplex dump directory
>
> The sysplex dump directory is a shared VSAM data set that contains
> information about SVC dumps that have been taken on each of the systems in
> the sysplex. As each SVC dump is written to a data set, an entry is added
> by the dumping services address space (DUMPSRV) to the sysplex dump
> directory to store information like dump data set name, dump title, and
> symptom string.
>
> The Incident Log task uses the sysplex dump directory as the repository
> for information about incidents that have occurred in the sysplex. If your
> installation has not already created a sysplex dump directory, this topic
> describes the steps for doing so.
>
>
> Try this URL
>
> http://pic.dhe.ibm.com/infocenter/zosmf/vxrx/index.jsp?topic=%2Fcom.ibm.zosmf.configguide.help.doc%2FIZUHPINFO_CreateSysplexDumpDirectory.html
>
> Lizette
>
>
> > -----Original Message-----
> > From: IBM Mainframe Discussion List [mailto:[email protected]] On
> > Behalf Of venkat kulkarni
> > Sent: Monday, June 09, 2014 5:40 AM
> > To: [email protected]
> > Subject: Re: SYSPLEX ISSUE
> >
> > Hello Lizette,
> >                          Yes, I checked IEA651E message and also checked
> with
> > DUMPSRV address space. But not able to point out exact issue.
> >
> >
> >
> >
> > On Mon, Jun 9, 2014 at 5:50 PM, Lizette Koehler <[email protected]
> >
> > wrote:
> >
> > > Did you check the message ?
> > >
> > > IEA651E
> > > SYSPLEX DUMP DIRECTORY PROCESSING TERMINATED Explanation
> > Because of a
> > > failure, the system could not automatically add a source description
> > > for an SVC dump to the sysplex dump directory. This is the tenth
> > > failure. The cause of the failures could be that:
> > >
> > >     The sysplex dump directory was full.
> > >     A sysplex dump directory had not been created.
> > >     The sysplex dump directory was not specified.
> > >     The sysplex dump directory was continually in use.
> > >     The SYSDDIR statement in the BLSCUSER parmlib has not been
> processed.
> > >
> > > System action
> > >
> > > The system disables the function to add source descriptions for SVC
> > > dumps to the sysplex dump directory. The system deletes the
> > > outstanding requests to add source descriptions; no new requests is
> created.
> > > Programmer response
> > >
> > > Check the causes listed in the explanation and correct the problem.
> > > Then cancel the DUMPSRV address space. When the DUMPSRV address space
> > > restarts, the add function is again enabled.
> > >
> > > Lizette
> > >
> > >
> > > > -----Original Message-----
> > > > From: IBM Mainframe Discussion List
> > > > [mailto:[email protected]] On Behalf Of venkat kulkarni
> > > > Sent: Monday, June 09, 2014 4:53 AM
> > > > To: [email protected]
> > > > Subject: SYSPLEX ISSUE
> > > >
> > > > Hello,
> > > >           I am suddenly getting below error on one of my SYSPLEX
> system.
> > > >
> > > > IEA651E SYSPLEX DUMP DIRECTORY PREOCESS TERMINATED.
> > > >
> > > > there is no associated message with this. I check the DUMPSRV
> > > > address
> > > space
> > > > and this is also working. But I am not able to identify that how to
> > > check for current
> > > > status of SYSPLEX dump dataset to take necessary action.
> > >
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to