Whether a dataset is SMS-managed or not has no relevance to the information displayed by the program, but has relevance to whether or not there is a "match". That match is done as part of "Open" processing, for example.
An APF list entry created by a specification such as DSN(MY.DSN) SMS will match a dataset named MY.DSN that is SMS-managed. It will not match a data set named MY.DSN that is not SMS-managed. The other side of that is that an APF list entry created by DSN(MY.DSN) VOLUME(V) will match a dataset named MY.DSN that is on VOLUME V whether or not the data set is SMS-managed (but if the data set is SMS-managed and moves to a different volume, there would no longer be a match from that APF list entry). The DEBAPFIN bit is used to determine if the concatenation is considered to be APF-authorized or not. It works approximately like this: initially, the DEBAPFIN bit is turned on. If any data set is found in the concatenation that is not APF-authorized, the DEBAPFIN bit is turned off. Since the code you show does not use an intended programming interface, I will not comment on its correctness. IPLINFO itself must have been changed when dynamic APF was introduced but chose not to use the provided programming interface (CSVAPF REQUEST=LIST) to gain access to the data. 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
