I've seen similar issues over the years with OEM/ISV products not being ready for new z/OS releases. Why don't you try stripping down this LPAR to the bare minimum and then slowly add products back in to determine what is breaking your system? I normally would try and bring up a bare bones system first after a ServerPac installation and then I slowly customized it by adding various OEM products in a phased approach. CA normally was my culprit if I ran into issues like you are seeing...
Todd Burrell, PMP, ITIL Expert, CISSP | Project Manager | ITSO AHB | Centers for Disease Control and Prevention (CDC) Contractor - HP Enterprise Services | 1600 Clifton Rd, Building 21, MS D24, RM 1300 | Atlanta, GA 30338 | 404-971-7275 (Blackberry) 404-723-2017 (Cell) | [email protected] THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is for use only by the intended recipient. If you received this in error, please notify the sender and delete the communication from all computers. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of venkat kulkarni Sent: Tuesday, June 10, 2014 3:22 AM To: [email protected] Subject: Re: SYSPLEX ISSUE Below are some more dump detail, I am getting on console after bringing down Netview IEA794I SVC DUMP HAS CAPTURED: 651 DUMPID=055 REQUESTED BY JOB (JES2 ) DUMP TITLE=COMPON=SSI,COMPID=5752SC1B6,ISSUER=IEFJSARR,MODULE=I EFJRASP,ABEND=S0C4,REASON=00000004,SNAME=NETV IEF196I IGD100I 376A ALLOCATED TO DDNAME SYS00056 DATACLAS ( ) IEF196I IEF285I SYS1.DUMP.D140610.T071632.SYS8.S00055 CATALOGED IEF196I IEF285I VOL SER NOS= RES001. IEA611I COMPLETE DUMP ON SYS1.DUMP.D140610.T071632.SYS8.S00055 655 DUMPID=055 REQUESTED BY JOB (JES2 ) FOR ASID (0027) INCIDENT TOKEN: GTOP SYS8 06/10/2014 07:16:32 SDRSN = 00000000 00000000 00000000 40000000 TASKS RESET DISPATCHABLE PRIOR TO DUMP COMPLETION ERROR ID = SEQ02834 CPU00 ASID0027 TIME00.16.32.6 On Tue, Jun 10, 2014 at 12:54 AM, Gibney, Dave <[email protected]> wrote: > Check the DUMPDS command in the MVS commands book. > > > -----Original Message----- > > From: IBM Mainframe Discussion List > > [mailto:[email protected]] On Behalf Of venkat kulkarni > > Sent: Monday, June 09, 2014 12:07 PM > > To: [email protected] > > Subject: Re: SYSPLEX ISSUE > > > > Yes, I resolved SMS issues. For the current dmup dataset, you want > > me to > just > > delete it from ISPF 3.4 . Or something else. > > Ex : > > > > > > SYS1.DUMP.D140609.T151417.SYS9.S00001 > > SYS1.DUMP.D140609.T151417.SYS9.S00003 > > SYS1.DUMP.D140609.T151418.SYS9.S00002 > > SYS1.DUMP.D140609.T151418.SYS9.S00004 > > SYS1.DUMP.D140609.T151418.SYS9.S00005 > > SYS1.DUMP.D140609.T151418.SYS9.S00006 > > SYS1.DUMP.D140609.T151419.SYS9.S00007 > > SYS1.DUMP.D140609.T151419.SYS9.S00008 > > SYS1.DUMP.D140609.T151419.SYS9.S00009 > > > > > > On Tue, Jun 10, 2014 at 12:30 AM, Gibney, Dave <[email protected]> wrote: > > > > > When your problem is to many dumps, the answer is to fix problem > > > causing the dumps, not to increase the number of dumps you can process. > > > Fix the SMS problem and throw away all the dumps in the full directory. > > > > > > > -----Original Message----- > > > > From: IBM Mainframe Discussion List > > > > [mailto:[email protected]] On Behalf Of venkat kulkarni > > > > Sent: Monday, June 09, 2014 11:57 AM > > > > To: [email protected] > > > > Subject: Re: SYSPLEX ISSUE > > > > > > > > yes, there was issue with SMS and it was not started. But how > > > > this can > > > cause > > > > DUMP issues, what we facing. I think both issues are separate. > > > > What you suggest. > > > > > > > > > > > > > > > > > > > > On Tue, Jun 10, 2014 at 12:19 AM, Gibney, Dave <[email protected]> > > wrote: > > > > > > > > > Why is this? > > > > > IEFJ003I DUPLICATE SUBSYSTEM SMS NOT INITIALIZED. > > > > > Check the IEFSSNxx members. > > > > > Verify your parmlib concatenation is what you want. > > > > > > > > > > > -----Original Message----- > > > > > > From: IBM Mainframe Discussion List > > > > > > [mailto:[email protected]] On Behalf Of venkat > > > > > > kulkarni > > > > > > Sent: Monday, June 09, 2014 11:45 AM > > > > > > To: [email protected] > > > > > > Subject: Re: SYSPLEX ISSUE > > > > > > > > > > > > Yes, this is my first z/OS 2.1 system. > > > > > > > > > > > > START RACF,SUB=MSTR > > > > > > IEE252I MEMBER IEFSSN02 FOUND IN SYS1.PARMLIB IEA045I AN SVC > > > > DUMP > > > > > > HAS STARTED AT TIME=08.14.17 DATE=06/09/2014 > > > > > > 273 > > > > > > FOR ASID (0001) > > > > > > ERROR ID = SEQ00004 CPU00 ASID0001 TIME08.14.17.5 QUIESCE = > > YES > > > > > > IEFJ003I DUPLICATE SUBSYSTEM SMS NOT INITIALIZED > > > > > > 76 IEA793A NO DUMP DATA SETS AVAILABLE FOR DUMPID=001 BY > > JOB > > > > > > (*MASTER*). > > > > > > USE THE DUMPDS COMMAND OR REPLY D TO DELETE THE DUMP > > > > IEE389I MVS > > > > > > COMMAND PROCESSING AVAILABLE IFB097I LOGREC RECORDING MEDIUM > > > > > > CHANGED FROM DATASET > > TO > > > > > > LOGSTREAM 279 > > > > > > IEE252I MEMBER ADYSET00 FOUND IN SYS1.PARMLIB IEE252I > > MEMBER > > > > > > MPFLSTSK FOUND IN SYS1.PARMLIB IEE538I IEASLP00 MEMBER NOT > > > > FOUND IN > > > > > > SYS1.PARMLIB IEA794I SVC DUMP HAS CAPTURED: 274 > > > > > > DUMPID=001 REQUESTED BY JOB (*MASTER*) DUMP > > > > > > > > TITLE=COMPON=SSI,COMPID=5752SC1B6,ISSUER=IEFJSARR,MODULE=I > > > > > > EFJRASP,ABEND=S0C4,REASON=00000011,SNAME=NETV > > > > > > IEA045I AN SVC DUMP HAS STARTED AT TIME=08.14.17 > > > > DATE=06/09/2014 > > > > > > 276 > > > > > > FOR ASID (0009) > > > > > > ERROR ID = SEQ00007 CPU00 ASID0009 TIME08.14.17.9 QUIESCE = > > YES > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Jun 10, 2014 at 12:05 AM, Gibney, Dave > > > > > > <[email protected]> > > > > wrote: > > > > > > > > > > > > > You obviously have a serious configuration problem. Is > > > > > > > this your first z/OS 2.1 system? > > > > > > > After the IEA371 message, what is the very first > > > > > > > abend/dump > > > message? > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: IBM Mainframe Discussion List [mailto:IBM- > > > > > > [email protected]] > > > > > > > > On Behalf Of venkat kulkarni > > > > > > > > Sent: Monday, June 09, 2014 11:26 AM > > > > > > > > To: [email protected] > > > > > > > > Subject: Re: SYSPLEX ISSUE > > > > > > > > > > > > > > > > We just starting VLF and DLF, we have proc for LLA proc > > > > > > > > as well but > > > > > not > > > > > > > using > > > > > > > > it . > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Jun 9, 2014 at 11:53 PM, venkat kulkarni > > > > > > > > <[email protected] > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Sure. I will check now. But I am also getting many > > > > > > > > > other messages related to dump and keep filling my > > > > > > > > > volumes > > > > > > > > > > > > > > > > > > > > > > > > > > > IEF196I IGD100I 376A ALLOCATED TO DDNAME SYS00011 > > DATACLAS > > > > ( > > > > > > ) > > > > > > > > > IEF196I IEF237I 376A ALLOCATED TO SYS00010 > > > > > > > > > IEC999I IFG0TC0A,IFG0TC0B,MSTJCL00,LLA ,DEB > > ADDR=6D20EC > > > > ,DSN > > > > > > = > > > > > > > > > SYS1.DUMP.D140609.T151419.SYS2.S00009 > > > > > > > > > IEF196I IEF237I 376A ALLOCATED TO SYS00011 > > > > > > > > > IEF196I IEC999I IFG0TC0A,IFG0TC0B,MSTJCL00,LLA ,DEB > > > > > > ADDR=6D20EC , > > > > > > > > > IEF196I DSN = SYS1.DUMP.D140609.T151419.SYS2.S00009 > > > > > > > > > IEF196I IEA995I SYMPTOM DUMP OUTPUT IEF196I IEF237I > > > > > > > > > 376A ALLOCATED TO SYS00012 IEF196I SYSTEM > > > > > > > > COMPLETION > > > > > > > > > CODE=C03 IEF196I TIME=08.14.32 SEQ=01295 CPU=0000 > > > > ASID=0005 > > > > > > > > > IEF196I PSW AT TIME OF ERROR 070C0000 87050F90 ILC 2 > > INTC > > > > 0D > > > > > > > > > IEF196I NO ACTIVE MODULE FOUND > > > > > > > > > IEF196I NAME=UNKNOWN > > > > > > > > > IEF196I IEF237I 376A ALLOCATED TO SYS00013 > > > > > > > > > IEF196I DATA AT PSW 07050F8A - 58108014 0A0D58C0 > > > > 549C9180 > > > > > > > > > IEF196I GR 0: 000001F7_07050F90 1: 00000000_80C03000 > > > > > > > > > IEE340E DUMP DATA SET UNUSABLE: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > IEC999I IFG0TC0A,IFG0TC0B,MSTJCL00,BPXOINIT,DEB > > > > ADDR=6D60EC > > > > > > ,DSN > > > > > > > > = > > > > > > > > > SYS1.DUMP.D140609.T163507.SYS2.S00016 > > > > > > > > > IEF196I IEC999I > > > > > > > > > IFG0TC0A,IFG0TC0B,MSTJCL00,BPXOINIT,DEB > > > > > > > > ADDR=6D60EC , > > > > > > > > > IEF196I DSN = SYS1.DUMP.D140609.T163507.SYS2.S00016 > > > > > > > > > IEF196I IEA995I SYMPTOM DUMP OUTPUT IEF196I SYSTEM > > > > COMPLETION > > > > > > > > > CODE=C03 IEF196I TIME=09.35.08 SEQ=02322 CPU=0000 > > > > > > > > > ASID=0005 > > > > > > > > > IEF196I PSW AT TIME OF ERROR 070C0000 87050F90 ILC 2 > > INTC > > > > 0D > > > > > > > > > IEF196I NO ACTIVE MODULE FOUND > > > > > > > > > IEF196I NAME=UNKNOWN > > > > > > > > > IEF196I DATA AT PSW 07050F8A - 58108014 0A0D58C0 > > > > 549C9180 > > > > > > > > > IEF196I GR 0: 000059B9_07050F90 1: 00000000_80C03000 > > > > > > > > > IEF196I 2: 00000000_87050F78 3: 00000000_006FC540 > > > > > > > > > IEF196I 4: 00000000_7FFC9290 5: 00000000_7FF9A618 > > > > > > > > > IEF196I 6: 00000000_07050D3A 7: 00000000_7FFC9290 > > > > > > > > > > > > > > > > > > > > > > > > > > > DUMPID=701 REQUESTED BY JOB (DUMPSRV ) DYNALLOC > > FAILED > > > > > > RETURN > > > > > > > > > CODE=04 ERROR RSN CODE=4714 INFO RSN CODE=041D > > VOLUME > > > > > > > > ALLOCATION > > > > > > > > > FAILED > > > > > > > > > *47 IEA793A NO DUMP DATA SETS AVAILABLE FOR DUMPID=701 > > BY > > > > > > JOB > > > > > > > > (DUMPSRV ). > > > > > > > > > USE THE DUMPDS COMMAND OR REPLY D TO DELETE THE > > DUMP > > > > > > > > IKJ56245I DATA > > > > > > > > > SET SYS1.DUMP.D140609.T144600.SYS2.S00735 NOT > > ALLOCATED, > > > > > > > > > NOT ENOUGH SPACE ON VOLUMES+ IKJ56245I USE DELETE > > > > COMMAND > > > > > > > > > TO DELETE UNUSED DATA SETS > > > > > > IEA799I > > > > > > > > > AUTOMATIC ALLOCATION OF SVC DUMP DATASET FAILED 624 > > > > > > > > > DUMPID=702 REQUESTED BY JOB (DUMPSRV ) DYNALLOC > > FAILED > > > > > > RETURN > > > > > > > > > CODE=04 ERROR RSN CODE=4714 INFO RSN CODE=041D > > VOLUME > > > > > > > > ALLOCATION > > > > > > > > > FAILED > > > > > > > > > *48 IEA793A NO DUMP DATA SETS AVAILABLE FOR DUMPID=702 > > BY > > > > > > JOB > > > > > > > > (DUMPSRV ). > > > > > > > > > USE THE DUMPDS COMMAND OR REPLY D TO DELETE THE > > DUMP > > > > > > > > > IEF196I IEF285I SYS1.DUMP.D140609.T144559.SYS2.S00733 > > > > > > > > CATALOGED > > > > > > > > > IEF196I IEF285I VOL SER NOS= RES001. > > > > > > > > > IEA611I PARTIAL DUMP ON > > > > SYS1.DUMP.D140609.T144559.SYS2.S00733 > > > > > > 628 > > > > > > > > > DUMPID=700 REQUESTED BY JOB (DUMPSRV ) FOR ASID > > > > > > > > > (0005) > > > > > > > > > > > > > > > > > > Not getting hint to point the exact issue. > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Jun 9, 2014 at 11:49 PM, Ed Jaffe > > > > > > > > > <[email protected]> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > >> On 6/9/2014 11:04 AM, venkat kulkarni wrote: > > > > > > > > >> > > > > > > > > >>> We dont have this CSVLLAxx parmlib member defined in > > > > > > > > >>> our > > > > systems. > > > > > > > > >>> > > > > > > > > >> > > > > > > > > >> In that case, LLA should not even start. > > > > > > > > >> > > > > > > > > >> I also see MSTJCL00 in the message, so you might want > > > > > > > > >> to check the libraries referenced there to be sure > > > > > > > > >> all is > well... > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> -- > > > > > > > > >> Edward E Jaffe > > > > > > > > >> Phoenix Software International, Inc > > > > > > > > >> 831 Parkview Drive North El Segundo, CA 90245 > > > > > > > > >> http://www.phoenixsoftware.com/ > > > > > > > > >> > > > > > > > > >> > > > > > -------------------------------------------------------------- > > > > > ---- > > > > > --- > > > > > > > > >> - 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 > > > > > > > > > > > > > > ---------------------------------------------------------- > > > > > > > ---- > > > > > > > ---- > > > > > > > ---- 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 > > > > > > > > > > -------------------------------------------------------------- > > > > > ---- > > > > > ---- 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 > > > > > > ------------------------------------------------------------------ > > > ---- 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 > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
