IBM Security Z Security

 View Only

  • 1.  Carla question

    Posted Wed March 27, 2024 05:12 PM

    Hello,

    I don't have a problem as such more of a query as to why this is needed.

    I have created some CARLa to extract users that have:

    1. been inactive for more than 90 days.
    2. have a TSO segment.
    3. are marked as Human under a custom field - CSDATA.

    to achieve this, I needed to use 3 NEWLISTS and the PROFLIST keyword to pass the select criteria from one NEWLIST to the other. Code below.

    /* Print out list of all inactive TSO Human users on the system */

    Newlist  Type=RACF Name=#CSDATA NoPage

    Select   Class=User Segment=CSData NonHuman=(Human)

    Newlist  Type=RACF Name=#TSO Outlim=0 Proflist=#CSData

    Select   Class=User Segment=TSO

    Sortlist Segment

    Newlist  Type=RACF PageLength=0 NoDup Proflist=#TSO ,

             TopTitle="List of all the Inactive users on the system" ,

             SubTitle="ID has not been used in the last 3 months"

    Define   #Total("Total", 5) Count

    Select   Class=User Segment=BASE LJDATE<Today-90

    Sortlist LJDATE(NonDisplay)        ,

             Key("MF ID", 8)           ,

             Name(20)                  ,

            :TLPROC                    ,

             DFLTGRP("Def Group", 9)   ,

             LJDATE("Last Con Dt", 11) ,

            :NonHuman("NonHuman", 8)

    Summary  * Complex(7) #Total(>1)

    My question is why I need to include the SORTLIST SEGMENT on the 2nd NEWLIST. If I don't use a SORTLIST my 3rd NEWLIST output does not filter on HUMAN



    ------------------------------
    Mark Beach
    ------------------------------



  • 2.  RE: Carla question

    Posted Tue April 02, 2024 11:56 AM

    Hi Mark,

    To be honest, when I saw your query I was curious why the first NEWLIST did not require a LIST family command.

    The technical answer to your question is that the property that PROFLIST is in effect (because of NEWLIST or OPTION) is copied to the query when the LIST family command is seen. 

    Since your first NEWLIST does not have PROFLIST, it works fine regardless.
    What happens when your second NEWLIST doesn't have the property request set, is that its list of selections is not filtered against the first list of selections.

    I would have to read the manual very carefully to see if anything was promised for this circumstance, so I am not sure I would regard this as an official bug, but I can see that it might be preferable if it worked more easily.

    For what it is worth.

    Regards,



    ------------------------------
    Jeroen Tiggelman
    IBM - Software Development Manager IBM Security zSecure Suite
    Delft
    ------------------------------

    Original Message