<snip> 22219 03:28:57.34 STC46322 00000281 IEF234E K 120B,VP0597,PVT,HZSPROC,HZSSTEP - RACK=VP0597 22219 03:28:57.36 STC46322 00000090 HZS0001I CHECK(IBMCSV,CSV_LNKLST_SPACE): 071 22219 03:28:57.55 STC46322 00000090 HZS0001I CHECK(IBMCSV,CSV_APF_EXISTS): 072 </snip>
Based on the presence of the messages before HZS0001I for CHECK(IBMCSV,CSV_APF_EXISTS), perhaps that check caused the recall. But that check (and pretty much all HC processing that allocates data sets) requests "S99NOMIG". If you want to pursue this with L2, you'll likely need a dump of the HZSPROC address space when this occurs. Were any HZS exception messages issued earlier in the IPL? I ask because, even though I don't understand how, if a check such as CSV_LNKLST_SPACE didn't run until later than the start of HC, something unexpected is happening. Something akin to what Mark Zelden hypothesized regarding a logstream dataset (which could have affected running of checks, since running of checks might not begin until the intended logstream is activated). Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
