Apply check doesn't open any target traditional datasets, or Unix System Services paths, so it's WAD. Whether it should is a different question.
Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com ------- Original Message ------- On Tuesday, September 5th, 2023 at 8:25 PM, Phil Smith III <li...@akphs.com> wrote: > I have a statement in the allocate job: > > ADD DDDEF(VSHZFSX) PATH'/u/some/directory') . > > > > The later Apply Check job just does: > > //SMPCNTL DD * > > SET BOUNDARY(TARGET) . > > APPLY S(VVSH840) CHECK . > > > > So it doesn't validate access to or even existence of that directory. > Could/should it? I don't know whether this is even reasonable, which makes it > a bit hard to research! Obviously we'll document it in great detail, but as > previously noted, I'm trying to make this as easy as possible for the users, > and failing on Apply Check seems more correct than on Apply (which is where > it fails now if that directory isn't there or the user doesn't have R/W > access). > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
