LISTGRP
Shows one RACF group and its members.
Also written LG
Why it matters. Before you give a team access, you check who is in the team. LISTGRP shows you.
Syntax
{LISTGRP | LG} [(group-name ...) | *] [NORACF] [DFP] [OMVS]- group-name
- The group to show. Leave it out to show your own current connect group.
- *
- Every group you are allowed to list.
- NORACF
- Leave out the base information, so you see only the segments you ask for.
- DFP
- Also show the DFP segment: default data, management and storage classes.
- OMVS
- Also show the z/OS UNIX segment: the group ID (GID).
Try it LISTGRP
- 1
Show the group ZBDEV. ZB0003 is already connected to it.
LISTGRP ZBDEV - 2
Now list your own group. Give no group name at all.
LISTGRP - 3
Ask about a group that doesn't exist: ZBQA.
LISTGRP ZBQA
Remember
- LISTGRP with a name shows that group.
- LISTGRP on its own shows your own group.
- Use it after ADDGROUP or CONNECT to check the change.
The usual mistake
LISTGRP ZB0003
ZB0003 is a user ID, not a group. LISTGRP looks for a group with that name and finds none.
LISTUSER ZB0003
On real z/OS
MF/OS prints the base part of a group in the real layout. The segment operands (DFP, OMVS and so on) are not modelled. For a group that does not exist the MF/OS terminal prints its own note instead of the real ICH51003I shown here. The line 'no users are connected' is MF/OS's own; for a universal group, real LISTGRP lists only some members.
Where can I practise LISTGRP?
Right here, at ZedBank. You take a junior job at a simulated bank and use LISTGRP in real work, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- RACFThe security manager for z/OS, which decides who may sign on, read a dataset, or run a transaction.
- RACF groupA named collection of users, used to grant access to many people at once rather than one at a time.
- RACF user IDA person or program's identity on the system. Short, unique, and the basis of every access decision.