John Eells wrote: >Whether it's a bug or a doc error vs. a feature depends on exactly what >weirdness you saw and whether it's expectedly or unexpectedly weird. That's a >question for Level 2 or RACF-L. But as I understand it, some of the weird >things derive from commands against a class that shares a POSIT with another >being implicitly (and, I am told, intentionally) driven against both classes. >Sometimes the command does not apply to the second class, and apparent errors >ensue.
>Much or all of this is documented in the RACF SAG. My simple-minded approach >to life since learning about this not too long ago is to *never* share a POSIT >value. Well, yeah, "Don't share a POSIT" is wise. But when there's no easy way to see what POSITs are in use, that's a semi-weak suggestion, I'm afraid. LISTCDT works, but telling a customer who is having a problem that they need to download and run a program from a website (even from IBM) doesn't go over very well. They have to get there (firewalls), download the XMITBIN, upload that as binary correctly, RECEIVE it, copy or upload the JCL, tailor it...by that time they're pretty irritated, and I don't blame them! Why isn't LISTCDT part of the product? It's clearly needed. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
