> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of Mainframe Mainframe
> Sent: Saturday, February 20, 2016 7:17 AM
> To: [email protected]
> Subject: Re: DASD device not going offline
> 
> I think because, these dataset were in diff volume and after making indriect
> catalog, updated catalog entry, we getting this error.
> 
> Now I tried updating linklist dynamically  Issue the following MVS commands:
>         SETPROG LNKLST,UNALLOCATE
>         P LLA
>         SET PROG=09
>         S LLA,SUB=MSTR
>         SETPROG LNKLST,ALLOCATE
> 
> But after issuing this SETPROG LNKLST,ALLOCATE command, I am getting below
> error.
> 
>  CSV540E LNKLST SET LNKLST00 is in error.
>  DATASET SET SYS1.SERBLINK
>  HAS VOLUME ID DOESNT NOT MATCH WITH CATALOG.
> 
>  Now do I need to IPL system, So that LNKLIST can look at dataset in correct
> volume and catalog or  is there any way we can do this dynamically.
> 
> On Sat, Feb 20, 2016 at 7:15 PM, Mainframe Mainframe <
> [email protected]> wrote:
> 
> > These below 4 datasets were directly was pointing into primary res
> > volume, So I changed back to point to indirect catalog.
> > SYS1.SCSFMOD0
> > SYS1.SISFLOAD
> > SYS1.SASMMOD1
> > SYS1.SERBLINK
> >
> >
> >
> > On Sat, Feb 20, 2016 at 6:28 PM, Eric Mendelson <
> > [email protected]> wrote:
> >
> >> Did you bring in a new link list. Looks like a dataset is missing or
> >> one dataset went into secondary extents
> >>
> >> Sent from my iPhone
> >>
> >> > On Feb 20, 2016, at 7:52 AM, Mainframe Mainframe <
> >> [email protected]> wrote:
> >> >
> >> > Thanks for help .
> >> > I think I found the problem, it was related to indirect logging. I
> >> > made necessary changes and changed dataset to indirect catalog but
> >> > now I am
> >> not
> >> > able to access SDSF, I am getting below error while accessing panel.
> >> >
> >> >                               ISPF Dialog Error Command ===>
> >> >
> >> >
> >>
> ******************************************************************************
> >> > * ISPD212
> >> >   *
> >> > *
> >> >   *
> >> > * Invalid PGM name
> >> >  *
> >> > * Link to 'ISFISP' failed, abend code = x'00000106'.
> >> >  *
> >> > *
> >> >   *
> >> > *
> >> >   *
> >> > *
> >> >   *
> >> > *
> >> >   *
> >> > *
> >> >   *
> >> > *
> >> >   *
> >> > * Current dialog statement:
> >> >   *
> >> > * SELECT PGM(ISFISP) PARM() NEWAPPL(ISF) PASSLIB NOCHECK SCRNAME(SDSF)
> >> >  *
> >> > *
> >> >   *
> >> > * Enter HELP command for further information regarding this error.
> >> >  *
> >> > * Press ENTER key to terminate the dialog.
> >> >  *
> >> > *
> >> >   *
> >> > *
> >> >   *
> >> > *
> >> >   *
> >> > *
> >> >   *
> >> >
> >> >
> >> >
> >> > On Sat, Feb 20, 2016 at 5:28 PM, Steve Horein <[email protected]>
> >> > wrote:
> >> >
> >> >> The presence of XCFAS looks indicative of a LNKLST'ed dataset on the
> >> the
> >> >> volume.
> >> >> This may help:
> >> >>
> >> >>
> >> https://www-
> 01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieae200/remen
> q.htm
> >> >>
> >> >>
> >> >> On Sat, Feb 20, 2016 at 5:47 AM, Mainframe Mainframe <
> >> >> [email protected]> wrote:
> >> >>
> >> >>> Hello Steve,
> >> >>>                    result is
> >> >>> D U,DASD,ALLOC,376B,1
> >> >>> IEE106I 04.48.06 UNITS ALLOCATED 730
> >> >>> UNIT    JOBNAME  ASID   JOBNAME  ASID   JOBNAME  ASID   JOBNAME  ASID
> >> >>> 376B    *MASTER* 0000   XCFAS    0006
> >> >>>
> >> >>>
> >> >>>
> >> >>> On Sat, Feb 20, 2016 at 5:10 PM, Steve Horein <[email protected]
> >> >
> >> >>> wrote:
> >> >>>
> >> >>>> What is the result of D U,DASD,ALLOC,<dasd ucb>,1
> >> >>>>
> >> >>>> On Sat, Feb 20, 2016 at 5:06 AM, Mainframe Mainframe <
> >> >>>> [email protected]> wrote:
> >> >>>>
> >> >>>>> Hello,
> >> >>>>>        One of my dasd device not going offline. I tried all possible
> >> >>> way
> >> >>>>> but still not success. I am not able to find, who is holding this
> >> >>> device.
> >> >>>>> We are in Sysplex env and from other system, this device is offline.
> >> >>>>>
> >> >>>>> 1) I am able to make offline this device from all other system
> >> except
> >> >>>> from
> >> >>>>> the system where it is required to be used.
> >> >>>>>
> >> >>>>> 2) I tried checking link to CHPID as well but I did see any path
> >> >> going
> >> >>>> bad.
> >> >>>>>
> >> >>>>> 3) I also check conjunction using D GRS,C but nothing i could find .
> >> >>>>>
> >> >>>>>
> >> >>>>> Finally when I try forcing device making offline using force
> >> command,
> >> >>>> this
> >> >>>>> goes in boxed status.
> >> >>>>> Can you please help, if any other way to find reason for this and
> >> >> solve
> >> >>>>> this issue.
> >> >> ----------------------------------------------------------------------
> >> >>>>> 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

Reply via email to