Thanks to all that responded.  The dataset permissions came about with our
testing of AMISYS release 11.  The batch claims job aborted with user
(class) not having write access to one of the new datasets in the OPTIONS
database.  In the Amisys release 11 database conversion jobs, AMISYS made an
assumption that all their client's databases were originally created using
"password security" as opposed to "level security".  They did not realize
there would be older AMISYS shops whose databases were originally created
using the "level security".  Since two of our databases were created with
this level security, the AMISYS database conversion job set the default
security for all the new datasets that were implemented in release 11.  With
Adager's assistance, I changed this level security to password security for
both the health and option database.  Then I correct the security settings
for all the new datasets in these two databases.  Adager saved the day
again!


Jackie

-----Original Message-----
From: Jacqueline Savinon [mailto:[log in to unmask]]
Sent: Monday, January 13, 2003 9:25 AM
To: [log in to unmask]
Subject: [HP3000-L] TurboImage Dataset Permissions


I need to obtain a listing of the permissions for a turboimage dataset? How
is this done?

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


The information in this E-mail message is legally privileged and
confidential information intended only for the use of the individual(s)
named above.  If you, the reader of this message, are not the intended
recipient, you are hereby notified that you should not further disseminate,
distribute, copy or forward this E-mail message. This is strictly
prohibited. If you have received this E-mail in error, please notify the
sender immediately and delete the original. Thank you.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *