Top Secret

 View Only
  • 1.  Prefixing WHOHAS queries in CASECAUT and UNIXPRIV

    Posted May 12, 2016 09:11 AM

    I stumbled across a behavior in TSS that I don't understand:

     

    We have rules defined in CASECAUT(TSS) and UNIXPRIV(CHOWN)—that is, those are owned, and there are privileges issued under them.  When I do a WHOHAS on either one, I get the normal listing.

     

    When I do a WHOHAS UNIXPRIV(C), I'm shown the CHOWN owner and all permissions, just as though I'd spelled out "CHOWN".  This makes sense to me.

     

    But when I do WHOHAS CASECAUT(T), I get this:

       TSS0240E  INVALID RESOURCE NAME

       TSS0301I  WHOHAS   FUNCTION FAILED, RETURN CODE =  4

     

     

    On the other hand I can do the same thing with CASECAUT(TS) and get the correct listing as though I'd spelled out CASECAUT(TSS).

     

    I infer that both classes can be "prefixed", but that CASECAUT has a minimum prefix length of 2 and UNIXPRIV of 1.  I trot off to the RDT, therefore, to see what controls that (I don't know much about class definitions yet), but don't see anything that explains it.

     

    I don't have to know, but I'm curious:  What's the difference here?



  • 2.  Re: Prefixing WHOHAS queries in CASECAUT and UNIXPRIV

    Broadcom Employee
    Posted May 12, 2016 11:39 AM

    Robert,

     

    Need to investigate your question. Couldnt find anything on our problem tracking system that explains why one character works for one resource class and not the other for a WHOHAS command.

     

    Will definitely get back to you. I will open a support ticket to track your question and get you an answer.

     

    Regards,

     

    Joseph Porto - CA Level 1 Support



  • 3.  Re: Prefixing WHOHAS queries in CASECAUT and UNIXPRIV
    Best Answer

    Broadcom Employee
    Posted May 17, 2016 03:53 PM

    Bob,

     

    OK here is what I found out and tested.

     

    Resource class that have the attribute of NOMASK allows for only one character on the TSS WHOHAS command.

     

    tss list(rdt) resclass(otran)

    ACCESSORID = *RDT*     NAME       = RESOURCE DEFINITIONS

     

       RESOURCE CLASS = OTRAN

        RESOURCE CODE = X'06E'

            ATTRIBUTE = NOMASK,MAXOWN(08),MAXPERMIT(008),ACCESS

               ACCESS = NONE(0000),UPDATE(6000),EXECUTE(4000),INSTALL(0400)

               ACCESS = INQUIRE(0080),SET(0040),COLLECT(0002),ALL(FFFF)

               DEFACC = EXECUTE

    TSS0300I  LIST     FUNCTION SUCCESSFUL

    READY

     

    tss whohas otran(a)

    OTRAN      = A                                             OWNER(IDENNIS )

      XAUTH     = A                                              ACID(HARBEWS )

        ACCESS  = EXECUTE

     

    TSS0300I  WHOHAS   FUNCTION SUCCESSFUL

    READY

     

     

     

    Resource classes with MASK, require at least 2 characters when using the TSS WHOHAS command.

     

    tss list(rdt) resclass(casecaut)

    ACCESSORID = *RDT*     NAME       = RESOURCE DEFINITIONS

     

       RESOURCE CLASS = CASECAUT

        RESOURCE CODE = X'156'   POSIT =    592

            ATTRIBUTE = MASKABLE,MAXOWN(26),MAXPERMIT(044),ACCESS,DEFPROT

               ACCESS = NONE(0000),GRANT(1C00),CONTROL(6400),PRIVILEG(6000)

               ACCESS = UPDATE(2000),USE(4000),ALL(FFFF)

               DEFACC = USE

    TSS0300I  LIST     FUNCTION SUCCESSFUL

    READY

     

    tss whohas casecaut(t)

    TSS0240E  INVALID RESOURCE NAME

    TSS0301I  WHOHAS   FUNCTION FAILED, RETURN CODE =  4

    READY

     

    Please let me know if there are any questions.

     

    Regards,

    Joseph Porto - CA Level 1 Support



  • 4.  Re: Prefixing WHOHAS queries in CASECAUT and UNIXPRIV

    Posted May 26, 2016 10:10 AM

    Thanks, Joe.  In that case I probably won't bother remembering which of my resources are which; I'll just try it one way and then the other.

     

    Is this behavior documented anywhere?  I'm still learning my way around.



  • 5.  Re: Prefixing WHOHAS queries in CASECAUT and UNIXPRIV

    Broadcom Employee
    Posted May 26, 2016 10:25 AM

    Bob,

     

    I will be submitting a doc update to have this information added. I will also create a knowledge document with the same information.

     

    Please let me know if there is anything else that you need.

     

    Regards,

     

    Joseph Porto - CA Level 1 Support