Remember when you do a D U command it will display what it can find. So the UCB allocated is what Steve pointed out.
376E is what is allocated to OMVS. 376B is not allocated. Do a D U,,376B,1 instead. Do a D M=DEV(376B) instead See what the device looks like. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Steve Horein > Sent: Tuesday, February 23, 2016 7:00 AM > To: [email protected] > Subject: Re: DASD device not going offline > > Look again. > 376B ¬= 376E > > On Mon, Feb 22, 2016 at 10:31 PM, Mainframe Mainframe < > [email protected]> wrote: > > > Hello All, > > Thanks for all suggestion and we are very close to solve > > the issue. Let me explain what all I did, > > > > 1) created one more PROG member and copied all LNKLST definition. > > 2) CHANGED LNKLST00 to LNKLST01 ---- created new one. > > 3) run Seprog command for activating new setprog parmlib member > > 4) Activated new lnklst. > > 5) Then updated system to use new lnklst01 > > > > Now I am able to access SDSF too. But my basic issue still there, for > > which I started this thread ---- device not going offline > > > > I am still not able to make my primary res volume which I am not using > > it now, as my system is ipl'd from Alt res volume . I tried checking > > allocation that who is holding it > > > > /D U,DASD,ALLOC,376B,1 > > IEE106I 23.31.48 UNITS ALLOCATED 329 > > UNIT JOBNAME ASID JOBNAME ASID JOBNAME AS > > 376E OMVS 000F > > > > But I am not understanding how OMVS is using this device. > > > > > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
