You do not need ISPF to run SDSF. You can issue SDSF from the READY Prompt in
native TSO. It does not have all of the niceties it has under ISPF, but is
very functional.
Check your catalog entries. Make sure the LISTC ENT('xxxx') ALL shows the
indirect catalog entry
Lizette
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of Mainframe Mainframe
> Sent: Saturday, February 20, 2016 10:11 AM
> To: [email protected]
> Subject: Re: DASD device not going offline
>
> Hello Lizette,
> Thanks for suggestion. As expected, command D
> PROG,LINKLIST showing my dataset on wrong volume. Basically we have two RES
> volume ZS21P1( primary ) and ZS21T1 ( Ale RES volume) , and system is
> indirectlry catalogged. My system is curently IPL'd from Alt Res volume, But
> today I noticed that
>
> SYS1.SCSFMOD0
> SYS1.SISFLOAD
> SYS1.SASMMOD1
> SYS1.SERBLINK
>
> dataset were pointing to Primary res volume,So I updated and made it indirect
> cataloged. So, that it will point to ZS21T1 now as currently system is IPL'd
> from ZS21T1.
>
> Now when I issued D PROG,LINKLST , these dataset still showing me in ZS21P1
> which is wrong.
>
> In my PROG00, we dont put volume serial number , like below.
>
> LNKLST DEFINE NAME(LNKLST00) /* DEFINE */
> LNKLST ADD NAME(LNKLST00) DSNAME(SYS1.SISFMOD1) /* SDSF */
>
> We don't use CSVLLAxx member in our system .
>
> Now I tried to run below command from HMC console, as I am not able to access
> SDSF because of this issue,
>
> SETPROG LNKLST,DEFINE,NAME=LNKLST01,COPYFROM=LNKLST00
> SETPROG LNKLST,ACTIVATE,NAME=LNKLST01
> SETPROG LNKLST,UPDATE,JOB=*
>
> But I am not able to run these command anY get syntax issue etc.
>
> Please suggest
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
