Good Day Fellow Members!

I have an interesting issue with the "LOGTO" SB+ command.   I am trying to allow a specific Security Group to have access to our TRN.DATA account.  (Our "TRN.DATA" is a our "sandbox" account to allow our power user(s) to test new processes and/or experimenting with setting up our business needs.)

Currently, when I ask the user to perform a "/LOGTO TRN.DATA" , they get "TRN.DATA ACCESS DENIED".   (I have added an attachment on what the users are seeing.)    I have tried to add the account to the Security Group through the SB+ Security Group Maintenance, but the updated data is not being saved to the Security Group record.

I did ask our Unix administrator to check the permissions and our admin did make adjustment to all user to access the account.  However, this did not resolve the issue.

So, my question to the group is what I am missing?  What do I need to look at or investigate?

Any suggestions and feedback will be welcomed.

Thank you for your time and consideration.  Looking forward to the responses.

Hi

Can you check TRN.DATA is Authorized in all parent sb group until ROOT ?

Then VOC DMSYSDEFN and DMSECURITY must be identical in start Account and TRN.DATA account. 

Manu

Manu,

It's also worth checking thet user IDs in the security record are in the correct case - there is a priotity of checking for as-entered/upper-case/lower-case/mixed-case (I don't recall the rules and order after all this time) and a mixture can give you some odd results with multiple entries that are treated as the same user ID even they have different casing - and they can exist simultaneously.

Regards

JJ  

------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------