On 11/25/2013 3:19 AM, [email protected] wrote:
For years (forever) I thought that any 3.4 listing done using ISPF is done
using the catalog search sequence (unless I deliberately specify a volume). I
did not specify a volser and listed sys1.afom*. I got 4 hits. One was missing
(sys1.afomhfs), that had just given me a JCL error 'data set not found'. I
redid the search using *.afom*. I got 5 hits, including my missing data set. I
went to the volser and listed everything on that volser. Yes, data set was
there. listc on it resulted in 'data set not found' (some catalog error).
I did not set anything special for ISPF options, but I am baffled that using
HLQ * would get me an uncatalogued data set. Have I gotten that wrong all these
years? Or is there another explanation?
I ended up issuing a c in front of that entry, and now the data set is
catalogued. Considering that this is a DLIB data set that does not have a
volser in the DDDEF, I wonder how the ADCD people ever got this to be populated
in the first place. (Well, I don't wonder, since the ADCD system doesn't have
an SMPE environment usable for serious SMPE work, it was clearly copied
together to fit on the mod3 volumes).
Barbara
Barbara,
When you wildcard the HLQ in ISPF 3.4, ISPF searches ALL catalogs, so
you may end up with hits that are not in the standard search order, such
as offline resvols, etc. That's why I submitted a requirement and ISPF
added the catalog name to 3.4 if you check that option.
Regards,
Tom Conley
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
