I have several questions on CSDATA reporting.
We are trying to look up the access of 2 dataset profiles and RESOLVING the group access to the User IDs. We want to include the CSDATA field $FIELD1 from the UserID record. But for some reason what we are seeing with the look up does not match what is on the user id. Here is the carla:
SUP MSG=(2226,27,28,29,1788,286,293);
Newlist n=based1 segment=base required allowrestrict,
,
tt="Sensitive Dataset Overview",
st='Pxx Project' retain
Select s=base c=dataset,
profile=('DSN1.NODEA.NODEB.**','DSN2.NODEC.NODED.**')
sortlist " - complex"(tt,page) complex(tt,page) stamp(tt),
,
searchkey(nd) key(26,wrap) proftype(1) | warning(1,hb) |,
erase(1,hb),
uacc owner acl:$field1,
acl(sort(ACCESS),universal,resolve) acl:revoke(hb,1) |,
acl:revoke_inactive(hb,1) acl:name(trunc) acl:dfltgrp(trunc),
acl:instdata(0,trunc)
How can we lookup the $FIELD1 from the RESOLVED UserID?
Not sure if this was a good decision on our part or not but $FIELD1 is defined to USERIDs and GROUPS, so we have CFIELD for GROUP.CSDATA.$FIELD1 and USER.CSDATA.$FIELD1 Could that cause lookup issues?
Today we use CSDATA heavily on the User ID record, and minimally on Groups, Resources, and Datasets. But that is going to get larger for Groups, Resources, and Datasets. So reporting on the CSDATA segments will be very important. I don't want to bother you guys everytime we have a lookup question. Is there a sample library, documentation, or other material about using CSDATA segments in reporting. I had an RFE for reporting on CSDATA that lead to some changes for CSDATA in release 2.5. But it seems more could be done, I may need to document some scenarios and open up another RFE.
Thanks for your assistance.
------------------------------
Linnea Sullivan
------------------------------