How about using a LISTC ENT(/) in front of the non-existing dataset? Would that work?
Werner Von: Juergen Kehr <[email protected]> An: [email protected], Datum: 07.04.2014 09:39 Betreff: ISPF 3.4 question Gesendet von: IBM Mainframe Discussion List <[email protected]> Hello, when using ISPF 3.4 I got the following strange situation: Using dataset level PP.**.BBLOAD I get the following output, which is completely correct PP.MVI.BBLOAD SYR101 Using dataset level *.**.BBLOAD I get this output PP.MVI.BBLOAD SYR101 PP.MVI.BBLOAD SYR103 Trying to access the dataset on SYR103 leads to Data set not found A listing of datasets on SYR103 shows that dataset PP.MVI.BBLOAD is not on that volume. An IDCAMS LISTCAT (without catalog parameter) for this dataset shows volume SYR101. So my assumption is, that the dataset is contained in some other active catalog, but I couldn't find out in which catalog ISPF does find the entry. Can anybody help? I would like to get rid of this (and probably some other) errorneous catalog entries. Thanks in advance for any help. Juergen ---------------------------------------------------------------------- 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
