f



Restrict access

Is there a way to restrict access to only a certain user within an account.=
 For example I would only like user OPERATOR.AIS to have access to everythi=
ng in the FILES.AIS group and account.

[cid:image005.jpg@01CA3E0B.CA79C220]

Reginald C. Monroe Jr | Sr. Systems Administrator |  Mercury Insurance
555 W. Imperial Hwy. Brea, CA 92821
(714) 671-6753 Direct  (714) 671-6541 Fax
www.mercuryinsurance.com<http://www.mercuryinsurance.com>




This email and/or any files or attachments transmitted with it are confiden=
tial and intended solely for the use of the individual or entity to whom th=
ey are addressed, and may contain information that is privileged, confident=
ial and exempt from disclosure under applicable law. If you are not the int=
ended recipient, or the employee or agent responsible for delivering the me=
ssage to the intended recipient, you are hereby notified that any dissemina=
tion, distribution or copying of this e-mail and/or any files or attachment=
s transmitted with it is strictly forbidden. If you have received this emai=
l in error, please delete the e-mail and/or any files or attachments, and a=
lso notify the system manager (PostMaster@mercuryinsurance.com) of the erro=
r. Please note that any views or opinions presented in this email are solel=
y those of the author and do not necessarily represent those of the company=
.. Finally, the recipient should check this email and any attachments for th=
e presence of viruses. The company accepts no liability for any damage caus=
ed by any virus transmitted by this email and/or any files or attachments t=
ransmitted with it.


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

0
RMonroe (1)
9/26/2009 1:12:49 AM
comp.sys.hp.mpe 25828 articles. 0 followers. rhorner (2) is leader. Post Follow

14 Replies
838 Views

Similar Articles

[PageSpeed] 33

Reggie:

Yes if I understand the question right.

This is done through access rights.

Use altgroup, altacct  to set them up the way you want (;ACCESS=3D=20
r,l,a,w,x,s:any,ac,gu,al,gl,cr) depending on the alt type and altuser=20
(;cap=3Dsm,am,al,gl,di,op) depending on the level of access you want the =

user to have.

ALTGROUP FILES.AIS;ACCESS=3Dr,l,a,w,x,s:GL
ALTUSER OPERATOR.AIS;CAP=3DGL,OP and any other capabilities you want

Hope this is of some help.

With MPEX, alot more can be done.

Olav Kappert
IOMIT International
http://IOMIT.UnitedStates.com


Reggie Monroe wrote:

>Is there a way to restrict access to only a certain user within an accou=
nt. For example I would only like user OPERATOR.AIS to have access to eve=
rything in the FILES.AIS group and account.
>
>[cid:image005.jpg@01CA3E0B.CA79C220]
>
>Reginald C. Monroe Jr | Sr. Systems Administrator |  Mercury Insurance
>555 W. Imperial Hwy. Brea, CA 92821
>(714) 671-6753 Direct  (714) 671-6541 Fax
>www.mercuryinsurance.com<http://www.mercuryinsurance.com>
>
>
>
>
>This email and/or any files or attachments transmitted with it are confi=
dential and intended solely for the use of the individual or entity to wh=
om they are addressed, and may contain information that is privileged, co=
nfidential and exempt from disclosure under applicable law. If you are no=
t the intended recipient, or the employee or agent responsible for delive=
ring the message to the intended recipient, you are hereby notified that =
any dissemination, distribution or copying of this e-mail and/or any file=
s or attachments transmitted with it is strictly forbidden. If you have r=
eceived this email in error, please delete the e-mail and/or any files or=
 attachments, and also notify the system manager (PostMaster@mercuryinsur=
ance.com) of the error. Please note that any views or opinions presented =
in this email are solely those of the author and do not necessarily repre=
sent those of the company. Finally, the recipient should check this email=
 and any attachments for the presence of viruses. The company accepts no =
liability for any damage caused by any virus transmitted by this email an=
d/or any files or attachments transmitted with it.
>
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
> =20
>

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

0
Olav
9/26/2009 1:51:18 AM
Actually, not quite.

Giving the user and group GL capability would be the right solution 
ONLY if the user OPERATOR.AIS had FILES as his/her home group.

Once a user strays from his/her home group, he/she loses GL capability.

So, rather than use GL for the purpose of restricting access, AL 
could appropriate.

However, if any other user in the account had AL capability, they too 
would have access to the files in the FILES group.

Of course, any user with AM or SM capability would have unlimited 
access to any file in any group of the account.

So, in Reggie's specific case, GL would work as long as OPERATOR's 
home group is FILES.

Or, if that's not the case, changing GL to AL in the given ALTUSER 
and ALTGROUP commands would serve the purpose - as long as no other 
user in the account (other than the account manager who cannot be 
restricted in any case) has AL capability.

If that too is not the case, I cannot think of a way to so narrowly 
restrict access to a group of files to a specific user.

Hope that makes sense.

At 09:51 PM 2009-09-25, Olav Kappert wrote:
>Reggie:
>
>Yes if I understand the question right.
>
>This is done through access rights.
>
>Use altgroup, altacct  to set them up the way you want (;ACCESS= 
>r,l,a,w,x,s:any,ac,gu,al,gl,cr) depending on the alt type and 
>altuser (;cap=sm,am,al,gl,di,op) depending on the level of access 
>you want the user to have.
>
>ALTGROUP FILES.AIS;ACCESS=r,l,a,w,x,s:GL
>ALTUSER OPERATOR.AIS;CAP=GL,OP and any other capabilities you want
>
>Hope this is of some help.
>
>With MPEX, alot more can be done.
>
>Olav Kappert
>IOMIT International
>http://IOMIT.UnitedStates.com
>
>
>Reggie Monroe wrote:
>
>>Is there a way to restrict access to only a certain user within an 
>>account. For example I would only like user OPERATOR.AIS to have 
>>access to everything in the FILES.AIS group and account.
>>
>>[cid:image005.jpg@01CA3E0B.CA79C220]
>>
>>Reginald C. Monroe Jr | Sr. Systems Administrator |  Mercury Insurance
>>555 W. Imperial Hwy. Brea, CA 92821
>>(714) 671-6753 Direct  (714) 671-6541 Fax
>>www.mercuryinsurance.com<http://www.mercuryinsurance.com>
>>
>>
>>
>>
>>This email and/or any files or attachments transmitted with it are 
>>confidential and intended solely for the use of the individual or 
>>entity to whom they are addressed, and may contain information that 
>>is privileged, confidential and exempt from disclosure under 
>>applicable law. If you are not the intended recipient, or the 
>>employee or agent responsible for delivering the message to the 
>>intended recipient, you are hereby notified that any dissemination, 
>>distribution or copying of this e-mail and/or any files or 
>>attachments transmitted with it is strictly forbidden. If you have 
>>received this email in error, please delete the e-mail and/or any 
>>files or attachments, and also notify the system manager 
>>(PostMaster@mercuryinsurance.com) of the error. Please note that 
>>any views or opinions presented in this email are solely those of 
>>the author and do not necessarily represent those of the company. 
>>Finally, the recipient should check this email and any attachments 
>>for the presence of viruses. The company accepts no liability for 
>>any damage caused by any virus transmitted by this email and/or any 
>>files or attachments transmitted with it.
>>
>>
>>* To join/leave the list, search archives, change list settings, *
>>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>>
>>
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

-------------------------------------------------------------------------------------------------
Gilles Schipper
GSA Inc.
HP System Administration Specialists
300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
Voice: 416.702.7900     Fax: 905.889.3001
email:  gilles@gsainc.com  web: http://www.gsainc.com
-------------------------------------------------------------------------------------------------

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

0
Gilles
9/26/2009 2:10:23 AM
of course you could use ACDs.....
yeah..  nevermind.

-Craig

Reggie Monroe wrote: 
> Is there a way to restrict access to only a certain user within an account. For example I would only like user OPERATOR.AIS to have access to everything in the FILES.AIS group and account.
> [cid:image005.jpg@01CA3E0B.CA79C220]
> Reginald C. Monroe Jr | Sr. Systems Administrator |  Mercury Insurance
> 555 W. Imperial Hwy. Brea, CA 92821
> (714) 671-6753 Direct  (714) 671-6541 Fax
> www.mercuryinsurance.com<http://www.mercuryinsurance.com>
> This email and/or any files or attachments transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail and/or any files or attachments transmitted with it is strictly forbidden. If you have received this email in error, please delete the e-mail and/or any files or attachments, and also notify the system manager (PostMaster@mercuryinsurance.com) of the error. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any
 attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email and/or any files or attachments transmitted with it.
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

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

0
Craig
9/26/2009 5:37:27 PM
Well you could, but only for the files already existing in the group.

It doesn't really provide a consistent and permanent solution to the problem.

The only real way I can think of is to use GL and home group options 
as described earlier.

At 01:37 PM 2009-09-26, Craig Lalley wrote:
>of course you could use ACDs.....
>yeah..  nevermind.
>
>-Craig
>
>Reggie Monroe wrote:
> > Is there a way to restrict access to only a certain user within 
> an account. For example I would only like user OPERATOR.AIS to have 
> access to everything in the FILES.AIS group and account.
> > [cid:image005.jpg@01CA3E0B.CA79C220]
> > Reginald C. Monroe Jr | Sr. Systems Administrator |  Mercury Insurance
> > 555 W. Imperial Hwy. Brea, CA 92821
> > (714) 671-6753 Direct  (714) 671-6541 Fax
> > www.mercuryinsurance.com<http://www.mercuryinsurance.com>
> > This email and/or any files or attachments transmitted with it 
> are confidential and intended solely for the use of the individual 
> or entity to whom they are addressed, and may contain information 
> that is privileged, confidential and exempt from disclosure under 
> applicable law. If you are not the intended recipient, or the 
> employee or agent responsible for delivering the message to the 
> intended recipient, you are hereby notified that any dissemination, 
> distribution or copying of this e-mail and/or any files or 
> attachments transmitted with it is strictly forbidden. If you have 
> received this email in error, please delete the e-mail and/or any 
> files or attachments, and also notify the system manager 
> (PostMaster@mercuryinsurance.com) of the error. Please note that 
> any views or opinions presented in this email are solely those of 
> the author and do not necessarily represent those of the company. 
> Finally, the recipient should check this email and any
>  attachments for the presence of viruses. The company accepts no 
> liability for any damage caused by any virus transmitted by this 
> email and/or any files or attachments transmitted with it.
> > * To join/leave the list, search archives, change list settings, *
> > * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

-------------------------------------------------------------------------------------------------
Gilles Schipper
GSA Inc.
HP System Administration Specialists
300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
Voice: 416.702.7900     Fax: 905.889.3001
email:  gilles@gsainc.com  web: http://www.gsainc.com
-------------------------------------------------------------------------------------------------

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

0
Gilles
9/26/2009 6:55:07 PM
If you are wanting one user to be able to access files in a particular=20
group, and others user in the same account be denied access to files in=20
that group, then the following should work.

ALTGROUP THEGRP;ACCESS=3D(S,L,A,R,W,X:GU);PASS=3DFOOBAR
ALTUSER THEONE;HOME=3DTHEGRP

So the user "THEONE" will logon without being prompted for the group=20
password FOOBAR, because it is the users home group.

Other "NORMAL" users who are not "HOME'd" to the group will not be able=20
to access any file in "THEGRP" group,
 unless a RELEASE is applied to the file,
 or the account manager issues an ALTUSER xxxx;HOME=3DTHEGRP

If a user of the account issues a CHGROUP THEGRP command (to become a=20
group user of THEGRP) they will be asked for the password assigned to=20
the group.

NOTE:
Users with capabilities like SM,AM,AL,GL, and possibly PM will be able=20
to access THEGRP.
Altering a users home group may have negative consequences for any=20
application that is not using 'group' qualified filenames, however=20
adding file equations to the users logon UDC may solve that problem.

Michael Anderson,
J3k Solutions
Sr.Systems Programmer/Analyst
832.515.3868



Reggie Monroe wrote:
> Is there a way to restrict access to only a certain user within an acco=
unt. For example I would only like user OPERATOR.AIS to have access to ev=
erything in the FILES.AIS group and account.
>
> [cid:image005.jpg@01CA3E0B.CA79C220]
>
> Reginald C. Monroe Jr | Sr. Systems Administrator |  Mercury Insurance
> 555 W. Imperial Hwy. Brea, CA 92821
> (714) 671-6753 Direct  (714) 671-6541 Fax
> www.mercuryinsurance.com<http://www.mercuryinsurance.com>
>
>
>
>
> This email and/or any files or attachments transmitted with it are conf=
idential and intended solely for the use of the individual or entity to w=
hom they are addressed, and may contain information that is privileged, c=
onfidential and exempt from disclosure under applicable law. If you are n=
ot the intended recipient, or the employee or agent responsible for deliv=
ering the message to the intended recipient, you are hereby notified that=
 any dissemination, distribution or copying of this e-mail and/or any fil=
es or attachments transmitted with it is strictly forbidden. If you have =
received this email in error, please delete the e-mail and/or any files o=
r attachments, and also notify the system manager (PostMaster@mercuryinsu=
rance.com) of the error. Please note that any views or opinions presented=
 in this email are solely those of the author and do not necessarily repr=
esent those of the company. Finally, the recipient should check this emai=
l and any attachments for the presence of viruses. The company accepts no=
 liability for any damage caused by any virus transmitted by this email a=
nd/or any files or attachments transmitted with it.
>
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>  =20

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

0
Michael
9/26/2009 9:53:12 PM
Yes, that will work.

But then you have the problem of group password maintenance (Everyone 
regularly changes passwords, don't they?)

The same thing can be accomplished without the annoyance of group 
passwords, as follows:

ALTGROUP THEGRP;ACCESS=(S,L,A,R,W,X:GL)  ---> NOTE use of GL instead of GU
ALTUSER THEONE;HOME=THEGROUP;CAP=+GL

This works while maintaining the desired security because only a user 
logged into the home group has GL capability.

Once any user strays from home their group the user does not have GL 
capability - even if given that attribute.


At 05:53 PM 2009-09-26, Michael wrote:
>If you are wanting one user to be able to access files in a 
>particular group, and others user in the same account be denied 
>access to files in that group, then the following should work.
>
>ALTGROUP THEGRP;ACCESS=(S,L,A,R,W,X:GU);PASS=FOOBAR
>ALTUSER THEONE;HOME=THEGRP
>
>So the user "THEONE" will logon without being prompted for the group 
>password FOOBAR, because it is the users home group.
>
>Other "NORMAL" users who are not "HOME'd" to the group will not be 
>able to access any file in "THEGRP" group,
>unless a RELEASE is applied to the file,
>or the account manager issues an ALTUSER xxxx;HOME=THEGRP
>
>If a user of the account issues a CHGROUP THEGRP command (to become 
>a group user of THEGRP) they will be asked for the password assigned 
>to the group.
>
>NOTE:
>Users with capabilities like SM,AM,AL,GL, and possibly PM will be 
>able to access THEGRP.
>Altering a users home group may have negative consequences for any 
>application that is not using 'group' qualified filenames, however 
>adding file equations to the users logon UDC may solve that problem.
>
>Michael Anderson,
>J3k Solutions
>Sr.Systems Programmer/Analyst
>832.515.3868
>
>
>
>Reggie Monroe wrote:
>>Is there a way to restrict access to only a certain user within an 
>>account. For example I would only like user OPERATOR.AIS to have 
>>access to everything in the FILES.AIS group and account.
>>
>>[cid:image005.jpg@01CA3E0B.CA79C220]
>>
>>Reginald C. Monroe Jr | Sr. Systems Administrator |  Mercury Insurance
>>555 W. Imperial Hwy. Brea, CA 92821
>>(714) 671-6753 Direct  (714) 671-6541 Fax
>>www.mercuryinsurance.com<http://www.mercuryinsurance.com>
>>
>>
>>
>>
>>This email and/or any files or attachments transmitted with it are 
>>confidential and intended solely for the use of the individual or 
>>entity to whom they are addressed, and may contain information that 
>>is privileged, confidential and exempt from disclosure under 
>>applicable law. If you are not the intended recipient, or the 
>>employee or agent responsible for delivering the message to the 
>>intended recipient, you are hereby notified that any dissemination, 
>>distribution or copying of this e-mail and/or any files or 
>>attachments transmitted with it is strictly forbidden. If you have 
>>received this email in error, please delete the e-mail and/or any 
>>files or attachments, and also notify the system manager 
>>(PostMaster@mercuryinsurance.com) of the error. Please note that 
>>any views or opinions presented in this email are solely those of 
>>the author and do not necessarily represent those of the company. 
>>Finally, the recipient should check this email and any attachments 
>>for the presence of viruses. The company accepts no liability for 
>>any damage caused by any virus transmitted by this email and/or any 
>>files or attachments transmitted with it.
>>
>>
>>* To join/leave the list, search archives, change list settings, *
>>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>>
>>
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

-------------------------------------------------------------------------------------------------
Gilles Schipper
GSA Inc.
HP System Administration Specialists
300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
Voice: 416.702.7900     Fax: 905.889.3001
email:  gilles@gsainc.com  web: http://www.gsainc.com
-------------------------------------------------------------------------------------------------

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

0
Gilles
9/26/2009 10:58:14 PM
There are users within this account that has AL and or GL access. Is there =
a way to limit the access to this group to only a particular user without c=
hanging the access capabilities of the other users that already have AL and=
 or GL access.

Thank you.

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:HP3000-L@RAVEN.UTC.EDU] On Behalf =
Of Gilles Schipper
Sent: Saturday, September 26, 2009 3:58 PM
To: HP3000-L@RAVEN.UTC.EDU
Subject: Re: [HP3000-L] Restrict access

Yes, that will work.

But then you have the problem of group password maintenance (Everyone
regularly changes passwords, don't they?)

The same thing can be accomplished without the annoyance of group
passwords, as follows:

ALTGROUP THEGRP;ACCESS=3D(S,L,A,R,W,X:GL)  ---> NOTE use of GL instead of G=
U
ALTUSER THEONE;HOME=3DTHEGROUP;CAP=3D+GL

This works while maintaining the desired security because only a user
logged into the home group has GL capability.

Once any user strays from home their group the user does not have GL
capability - even if given that attribute.


At 05:53 PM 2009-09-26, Michael wrote:
>If you are wanting one user to be able to access files in a
>particular group, and others user in the same account be denied
>access to files in that group, then the following should work.
>
>ALTGROUP THEGRP;ACCESS=3D(S,L,A,R,W,X:GU);PASS=3DFOOBAR
>ALTUSER THEONE;HOME=3DTHEGRP
>
>So the user "THEONE" will logon without being prompted for the group
>password FOOBAR, because it is the users home group.
>
>Other "NORMAL" users who are not "HOME'd" to the group will not be
>able to access any file in "THEGRP" group,
>unless a RELEASE is applied to the file,
>or the account manager issues an ALTUSER xxxx;HOME=3DTHEGRP
>
>If a user of the account issues a CHGROUP THEGRP command (to become
>a group user of THEGRP) they will be asked for the password assigned
>to the group.
>
>NOTE:
>Users with capabilities like SM,AM,AL,GL, and possibly PM will be
>able to access THEGRP.
>Altering a users home group may have negative consequences for any
>application that is not using 'group' qualified filenames, however
>adding file equations to the users logon UDC may solve that problem.
>
>Michael Anderson,
>J3k Solutions
>Sr.Systems Programmer/Analyst
>832.515.3868
>
>
>
>Reggie Monroe wrote:
>>Is there a way to restrict access to only a certain user within an
>>account. For example I would only like user OPERATOR.AIS to have
>>access to everything in the FILES.AIS group and account.
>>
>>[cid:image005.jpg@01CA3E0B.CA79C220]
>>
>>Reginald C. Monroe Jr | Sr. Systems Administrator |  Mercury Insurance
>>555 W. Imperial Hwy. Brea, CA 92821
>>(714) 671-6753 Direct  (714) 671-6541 Fax
>>www.mercuryinsurance.com<http://www.mercuryinsurance.com>
>>
>>
>>
>>
>>This email and/or any files or attachments transmitted with it are
>>confidential and intended solely for the use of the individual or
>>entity to whom they are addressed, and may contain information that
>>is privileged, confidential and exempt from disclosure under
>>applicable law. If you are not the intended recipient, or the
>>employee or agent responsible for delivering the message to the
>>intended recipient, you are hereby notified that any dissemination,
>>distribution or copying of this e-mail and/or any files or
>>attachments transmitted with it is strictly forbidden. If you have
>>received this email in error, please delete the e-mail and/or any
>>files or attachments, and also notify the system manager
>>(PostMaster@mercuryinsurance.com) of the error. Please note that
>>any views or opinions presented in this email are solely those of
>>the author and do not necessarily represent those of the company.
>>Finally, the recipient should check this email and any attachments
>>for the presence of viruses. The company accepts no liability for
>>any damage caused by any virus transmitted by this email and/or any
>>files or attachments transmitted with it.
>>
>>
>>* To join/leave the list, search archives, change list settings, *
>>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>>
>>
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

---------------------------------------------------------------------------=
----------------------
Gilles Schipper
GSA Inc.
HP System Administration Specialists
300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
Voice: 416.702.7900     Fax: 905.889.3001
email:  gilles@gsainc.com  web: http://www.gsainc.com
---------------------------------------------------------------------------=
----------------------

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


This email and/or any files or attachments transmitted with it are confiden=
tial and intended solely for the use of the individual or entity to whom th=
ey are addressed, and may contain information that is privileged, confident=
ial and exempt from disclosure under applicable law. If you are not the int=
ended recipient, or the employee or agent responsible for delivering the me=
ssage to the intended recipient, you are hereby notified that any dissemina=
tion, distribution or copying of this e-mail and/or any files or attachment=
s transmitted with it is strictly forbidden. If you have received this emai=
l in error, please delete the e-mail and/or any files or attachments, and a=
lso notify the system manager (PostMaster@mercuryinsurance.com) of the erro=
r. Please note that any views or opinions presented in this email are solel=
y those of the author and do not necessarily represent those of the company=
.. Finally, the recipient should check this email and any attachments for th=
e presence of viruses. The company accepts no liability for any damage caus=
ed by any virus transmitted by this email and/or any files or attachments t=
ransmitted with it.

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

0
Reggie
9/27/2009 6:16:22 PM
Yes there is.

If you wish to restrict the group FILES to be able to be accessed by 
only the user OPERATOR, do the following:

:ALTGROUP FILES;ACCESS=(R,L,X,W,A,S:GL)
:ALTUSER OPERATOR;HOME=FILES;CAP=+GL

This will restrict any kind of access to files within the FILES group 
to only the user OPERATOR, with the following possible exceptions:

1. Any user in that account that has AM capability cannot be denied 
access to files in that group.
2. If any other user in the account has its home group as FILES - AND 
also has GL capability, then that user will also have access to the 
files in the FILES group.

So, in the specific example you cite, you only need to ensure that 
any other user that has GL capability does not also have FILES as the 
home group. (Of course, as stated previously, you cannot deny access 
to any user in the account that possesses AM capability).

Possessing AL capability does not provide access, since, as shown in 
the above ALTGROUP command, all forms of access are given ONLY to 
users with GL capability.

And GL capability is negated for all users that log in to other than 
their HOME groups.

To repeat - this technique allows you the proper file access 
restrictions WITHOUT the nuisance of group passwords, because if any 
user in the account (other than an AM user) logs in to this group 
(and does not have FILES as the home group or lacks GL capability) 
that user will be denied access to all files in the FILES group.

Hope that makes sense.

At 02:16 PM 2009-09-27, Reggie Monroe wrote:
>There are users within this account that has AL and or GL access. Is 
>there a way to limit the access to this group to only a particular 
>user without changing the access capabilities of the other users 
>that already have AL and or GL access.
>
>Thank you.
>
>-----Original Message-----
>From: HP-3000 Systems Discussion [mailto:HP3000-L@RAVEN.UTC.EDU] On 
>Behalf Of Gilles Schipper
>Sent: Saturday, September 26, 2009 3:58 PM
>To: HP3000-L@RAVEN.UTC.EDU
>Subject: Re: [HP3000-L] Restrict access
>
>Yes, that will work.
>
>But then you have the problem of group password maintenance (Everyone
>regularly changes passwords, don't they?)
>
>The same thing can be accomplished without the annoyance of group
>passwords, as follows:
>
>ALTGROUP THEGRP;ACCESS=(S,L,A,R,W,X:GL)  ---> NOTE use of GL instead of GU
>ALTUSER THEONE;HOME=THEGROUP;CAP=+GL
>
>This works while maintaining the desired security because only a user
>logged into the home group has GL capability.
>
>Once any user strays from home their group the user does not have GL
>capability - even if given that attribute.
>
>
>At 05:53 PM 2009-09-26, Michael wrote:
> >If you are wanting one user to be able to access files in a
> >particular group, and others user in the same account be denied
> >access to files in that group, then the following should work.
> >
> >ALTGROUP THEGRP;ACCESS=(S,L,A,R,W,X:GU);PASS=FOOBAR
> >ALTUSER THEONE;HOME=THEGRP
> >
> >So the user "THEONE" will logon without being prompted for the group
> >password FOOBAR, because it is the users home group.
> >
> >Other "NORMAL" users who are not "HOME'd" to the group will not be
> >able to access any file in "THEGRP" group,
> >unless a RELEASE is applied to the file,
> >or the account manager issues an ALTUSER xxxx;HOME=THEGRP
> >
> >If a user of the account issues a CHGROUP THEGRP command (to become
> >a group user of THEGRP) they will be asked for the password assigned
> >to the group.
> >
> >NOTE:
> >Users with capabilities like SM,AM,AL,GL, and possibly PM will be
> >able to access THEGRP.
> >Altering a users home group may have negative consequences for any
> >application that is not using 'group' qualified filenames, however
> >adding file equations to the users logon UDC may solve that problem.
> >
> >Michael Anderson,
> >J3k Solutions
> >Sr.Systems Programmer/Analyst
> >832.515.3868
> >
> >
> >
> >Reggie Monroe wrote:
> >>Is there a way to restrict access to only a certain user within an
> >>account. For example I would only like user OPERATOR.AIS to have
> >>access to everything in the FILES.AIS group and account.
> >>
> >>[cid:image005.jpg@01CA3E0B.CA79C220]
> >>
> >>Reginald C. Monroe Jr | Sr. Systems Administrator |  Mercury Insurance
> >>555 W. Imperial Hwy. Brea, CA 92821
> >>(714) 671-6753 Direct  (714) 671-6541 Fax
> >>www.mercuryinsurance.com<http://www.mercuryinsurance.com>
> >>
> >>
> >>
> >>
> >>This email and/or any files or attachments transmitted with it are
> >>confidential and intended solely for the use of the individual or
> >>entity to whom they are addressed, and may contain information that
> >>is privileged, confidential and exempt from disclosure under
> >>applicable law. If you are not the intended recipient, or the
> >>employee or agent responsible for delivering the message to the
> >>intended recipient, you are hereby notified that any dissemination,
> >>distribution or copying of this e-mail and/or any files or
> >>attachments transmitted with it is strictly forbidden. If you have
> >>received this email in error, please delete the e-mail and/or any
> >>files or attachments, and also notify the system manager
> >>(PostMaster@mercuryinsurance.com) of the error. Please note that
> >>any views or opinions presented in this email are solely those of
> >>the author and do not necessarily represent those of the company.
> >>Finally, the recipient should check this email and any attachments
> >>for the presence of viruses. The company accepts no liability for
> >>any damage caused by any virus transmitted by this email and/or any
> >>files or attachments transmitted with it.
> >>
> >>
> >>* To join/leave the list, search archives, change list settings, *
> >>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> >>
> >>
> >
> >* To join/leave the list, search archives, change list settings, *
> >* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>-------------------------------------------------------------------------------------------------
>Gilles Schipper
>GSA Inc.
>HP System Administration Specialists
>300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
>Voice: 416.702.7900     Fax: 905.889.3001
>email:  gilles@gsainc.com  web: http://www.gsainc.com
>-------------------------------------------------------------------------------------------------
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>
>This email and/or any files or attachments transmitted with it are 
>confidential and intended solely for the use of the individual or 
>entity to whom they are addressed, and may contain information that 
>is privileged, confidential and exempt from disclosure under 
>applicable law. If you are not the intended recipient, or the 
>employee or agent responsible for delivering the message to the 
>intended recipient, you are hereby notified that any dissemination, 
>distribution or copying of this e-mail and/or any files or 
>attachments transmitted with it is strictly forbidden. If you have 
>received this email in error, please delete the e-mail and/or any 
>files or attachments, and also notify the system manager 
>(PostMaster@mercuryinsurance.com) of the error. Please note that any 
>views or opinions presented in this email are solely those of the 
>author and do not necessarily represent those of the company. 
>Finally, the recipient should check this email and any attachments 
>for the presence of viruses. The company accepts no liability for 
>any damage caused by any virus transmitted by this email and/or any 
>files or attachments transmitted with it.
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

-------------------------------------------------------------------------------------------------
Gilles Schipper
GSA Inc.
HP System Administration Specialists
300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
Voice: 416.702.7900     Fax: 905.889.3001
email:  gilles@gsainc.com  web: http://www.gsainc.com
-------------------------------------------------------------------------------------------------

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

0
Gilles
9/27/2009 8:05:35 PM
Thank you very much and that does make sense.

-----Original Message-----
From: Gilles Schipper [mailto:gsainc@rogers.com] =

Sent: Sunday, September 27, 2009 1:06 PM
To: Reggie Monroe; HP3000-L@RAVEN.UTC.EDU
Subject: Re: [HP3000-L] Restrict access

Yes there is.

If you wish to restrict the group FILES to be able to be accessed by =

only the user OPERATOR, do the following:

:ALTGROUP FILES;ACCESS=3D(R,L,X,W,A,S:GL)
:ALTUSER OPERATOR;HOME=3DFILES;CAP=3D+GL

This will restrict any kind of access to files within the FILES group =

to only the user OPERATOR, with the following possible exceptions:

1. Any user in that account that has AM capability cannot be denied =

access to files in that group.
2. If any other user in the account has its home group as FILES - AND =

also has GL capability, then that user will also have access to the =

files in the FILES group.

So, in the specific example you cite, you only need to ensure that =

any other user that has GL capability does not also have FILES as the =

home group. (Of course, as stated previously, you cannot deny access =

to any user in the account that possesses AM capability).

Possessing AL capability does not provide access, since, as shown in =

the above ALTGROUP command, all forms of access are given ONLY to =

users with GL capability.

And GL capability is negated for all users that log in to other than =

their HOME groups.

To repeat - this technique allows you the proper file access =

restrictions WITHOUT the nuisance of group passwords, because if any =

user in the account (other than an AM user) logs in to this group =

(and does not have FILES as the home group or lacks GL capability) =

that user will be denied access to all files in the FILES group.

Hope that makes sense.

At 02:16 PM 2009-09-27, Reggie Monroe wrote:
>There are users within this account that has AL and or GL access. Is =

>there a way to limit the access to this group to only a particular =

>user without changing the access capabilities of the other users =

>that already have AL and or GL access.
>
>Thank you.
>
>-----Original Message-----
>From: HP-3000 Systems Discussion [mailto:HP3000-L@RAVEN.UTC.EDU] On =

>Behalf Of Gilles Schipper
>Sent: Saturday, September 26, 2009 3:58 PM
>To: HP3000-L@RAVEN.UTC.EDU
>Subject: Re: [HP3000-L] Restrict access
>
>Yes, that will work.
>
>But then you have the problem of group password maintenance (Everyone
>regularly changes passwords, don't they?)
>
>The same thing can be accomplished without the annoyance of group
>passwords, as follows:
>
>ALTGROUP THEGRP;ACCESS=3D(S,L,A,R,W,X:GL)  ---> NOTE use of GL instead of =
GU
>ALTUSER THEONE;HOME=3DTHEGROUP;CAP=3D+GL
>
>This works while maintaining the desired security because only a user
>logged into the home group has GL capability.
>
>Once any user strays from home their group the user does not have GL
>capability - even if given that attribute.
>
>
>At 05:53 PM 2009-09-26, Michael wrote:
> >If you are wanting one user to be able to access files in a
> >particular group, and others user in the same account be denied
> >access to files in that group, then the following should work.
> >
> >ALTGROUP THEGRP;ACCESS=3D(S,L,A,R,W,X:GU);PASS=3DFOOBAR
> >ALTUSER THEONE;HOME=3DTHEGRP
> >
> >So the user "THEONE" will logon without being prompted for the group
> >password FOOBAR, because it is the users home group.
> >
> >Other "NORMAL" users who are not "HOME'd" to the group will not be
> >able to access any file in "THEGRP" group,
> >unless a RELEASE is applied to the file,
> >or the account manager issues an ALTUSER xxxx;HOME=3DTHEGRP
> >
> >If a user of the account issues a CHGROUP THEGRP command (to become
> >a group user of THEGRP) they will be asked for the password assigned
> >to the group.
> >
> >NOTE:
> >Users with capabilities like SM,AM,AL,GL, and possibly PM will be
> >able to access THEGRP.
> >Altering a users home group may have negative consequences for any
> >application that is not using 'group' qualified filenames, however
> >adding file equations to the users logon UDC may solve that problem.
> >
> >Michael Anderson,
> >J3k Solutions
> >Sr.Systems Programmer/Analyst
> >832.515.3868
> >
> >
> >
> >Reggie Monroe wrote:
> >>Is there a way to restrict access to only a certain user within an
> >>account. For example I would only like user OPERATOR.AIS to have
> >>access to everything in the FILES.AIS group and account.
> >>
> >>[cid:image005.jpg@01CA3E0B.CA79C220]
> >>
> >>Reginald C. Monroe Jr | Sr. Systems Administrator |  Mercury Insurance
> >>555 W. Imperial Hwy. Brea, CA 92821
> >>(714) 671-6753 Direct  (714) 671-6541 Fax
> >>www.mercuryinsurance.com<http://www.mercuryinsurance.com>
> >>
> >>
> >>
> >>
> >>This email and/or any files or attachments transmitted with it are
> >>confidential and intended solely for the use of the individual or
> >>entity to whom they are addressed, and may contain information that
> >>is privileged, confidential and exempt from disclosure under
> >>applicable law. If you are not the intended recipient, or the
> >>employee or agent responsible for delivering the message to the
> >>intended recipient, you are hereby notified that any dissemination,
> >>distribution or copying of this e-mail and/or any files or
> >>attachments transmitted with it is strictly forbidden. If you have
> >>received this email in error, please delete the e-mail and/or any
> >>files or attachments, and also notify the system manager
> >>(PostMaster@mercuryinsurance.com) of the error. Please note that
> >>any views or opinions presented in this email are solely those of
> >>the author and do not necessarily represent those of the company.
> >>Finally, the recipient should check this email and any attachments
> >>for the presence of viruses. The company accepts no liability for
> >>any damage caused by any virus transmitted by this email and/or any
> >>files or attachments transmitted with it.
> >>
> >>
> >>* To join/leave the list, search archives, change list settings, *
> >>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> >>
> >>
> >
> >* To join/leave the list, search archives, change list settings, *
> >* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>--------------------------------------------------------------------------=
-----------------------
>Gilles Schipper
>GSA Inc.
>HP System Administration Specialists
>300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
>Voice: 416.702.7900     Fax: 905.889.3001
>email:  gilles@gsainc.com  web: http://www.gsainc.com
>--------------------------------------------------------------------------=
-----------------------
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>
>This email and/or any files or attachments transmitted with it are =

>confidential and intended solely for the use of the individual or =

>entity to whom they are addressed, and may contain information that =

>is privileged, confidential and exempt from disclosure under =

>applicable law. If you are not the intended recipient, or the =

>employee or agent responsible for delivering the message to the =

>intended recipient, you are hereby notified that any dissemination, =

>distribution or copying of this e-mail and/or any files or =

>attachments transmitted with it is strictly forbidden. If you have =

>received this email in error, please delete the e-mail and/or any =

>files or attachments, and also notify the system manager =

>(PostMaster@mercuryinsurance.com) of the error. Please note that any =

>views or opinions presented in this email are solely those of the =

>author and do not necessarily represent those of the company. =

>Finally, the recipient should check this email and any attachments =

>for the presence of viruses. The company accepts no liability for =

>any damage caused by any virus transmitted by this email and/or any =

>files or attachments transmitted with it.
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

---------------------------------------------------------------------------=
----------------------
Gilles Schipper
GSA Inc.
HP System Administration Specialists
300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
Voice: 416.702.7900     Fax: 905.889.3001
email:  gilles@gsainc.com  web: http://www.gsainc.com
---------------------------------------------------------------------------=
----------------------




This email and/or any files or attachments transmitted with it are confiden=
tial and intended solely for the use of the individual or entity to whom th=
ey are addressed, and may contain information that is privileged, confident=
ial and exempt from disclosure under applicable law. If you are not the int=
ended recipient, or the employee or agent responsible for delivering the me=
ssage to the intended recipient, you are hereby notified that any dissemina=
tion, distribution or copying of this e-mail and/or any files or attachment=
s transmitted with it is strictly forbidden. If you have received this emai=
l in error, please delete the e-mail and/or any files or attachments, and a=
lso notify the system manager (PostMaster@mercuryinsurance.com) of the erro=
r. Please note that any views or opinions presented in this email are solel=
y those of the author and do not necessarily represent those of the company=
.. Finally, the recipient should check this email and any attachments for th=
e presence of viruses. The company accepts no liability for any damage caus=
ed by any virus transmitted by this email and/or any files or attachments t=
ransmitted with it.

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

0
Reggie
9/28/2009 9:18:03 PM
Hi All,
    Any clues?  I haven't found anything searching the archives just yet...=
..

Thanks
Art "firewall fun <NOT> hehehe" Bahrs

Art Bahrs
Security Engineer
(503) 216-2722


This message is intended for the sole use of the addressee, and may contain=
 information that is privileged, confidential and exempt from disclosure un=
der applicable law. If you are not the addressee you are hereby notified th=
at you may not use, copy, disclose, or distribute to anyone the message or =
any information contained in the message. If you have received this message=
 in error, please immediately advise the sender by reply email and delete t=
his message.

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

0
Bahrs
2/4/2010 12:37:42 AM
Let me know if this is of any help, Art.

jack

-----Original Message-----
From: Bahrs, Art [mailto:Arthur.Bahrs@PROVIDENCE.ORG]
Sent: Wednesday, February 03, 2010 7:38 PM
To: HP3000-L@RAVEN.UTC.EDU
Subject: [HP3000-L] OT: Reflection Ports going to an AS/400?

Hi All,
    Any clues?  I haven't found anything searching the archives just yet...=
..

Thanks
Art "firewall fun <NOT> hehehe" Bahrs

Art Bahrs
Security Engineer
(503) 216-2722


This message is intended for the sole use of the addressee, and may contain=
 information that is privileged, confidential and exempt from disclosure un=
der applicable law. If you are not the addressee you are hereby notified th=
at you may not use, copy, disclose, or distribute to anyone the message or =
any information contained in the message. If you have received this message=
 in error, please immediately advise the sender by reply email and delete t=
his message.

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

Be sure to ask us about short term and long term rentals on servers, workst=
ations, storage and more!

CONFIDENTIALITY NOTICE: This communication with its contents may contain co=
nfidential information. It is solely for the use of the intended recipient(=
s). Unauthorized interception, review, use or disclosure is prohibited and =
may violate applicable laws including the Electronic Communications Privacy=
 Act. If you are not the intended recipient, please contact the sender and =
destroy all copies of the communication.

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

0
Jack
2/4/2010 1:04:20 AM
Art,
=A0
In the menu bar, go to connection --> setup --> advanced --> TCPIP=20
=A0
and hit the drop down
=A0
-Craig


--- On Wed, 2/3/10, Bahrs, Art <Arthur.Bahrs@PROVIDENCE.ORG> wrote:


From: Bahrs, Art <Arthur.Bahrs@PROVIDENCE.ORG>
Subject: OT: Reflection Ports going to an AS/400?
To: HP3000-L@RAVEN.UTC.EDU
Date: Wednesday, February 3, 2010, 4:37 PM


Hi All,
=A0 =A0 Any clues?=A0 I haven't found anything searching the archives just =
yet....

Thanks
Art "firewall fun <NOT> hehehe" Bahrs

Art Bahrs
Security Engineer
(503) 216-2722


This message is intended for the sole use of the addressee, and may contain=
 information that is privileged, confidential and exempt from disclosure un=
der applicable law. If you are not the addressee you are hereby notified th=
at you may not use, copy, disclose, or distribute to anyone the message or =
any information contained in the message. If you have received this message=
 in error, please immediately advise the sender by reply email and delete t=
his message.

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

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

0
Craig
2/4/2010 1:16:42 AM
Hi Don, Craig and All :)
    Thanks for the great quick help!

Thanks,
Art

Art Bahrs
Security Engineer
(503) 216-2722

From: Craig Lalley [mailto:mr_lalley@yahoo.com]
Sent: Wednesday, February 03, 2010 5:17 PM
To: HP3000-L@RAVEN.UTC.EDU; Bahrs, Art
Subject: Re: OT: Reflection Ports going to an AS/400?

Art,

In the menu bar, go to connection --> setup --> advanced --> TCPIP

and hit the drop down

-Craig


--- On Wed, 2/3/10, Bahrs, Art <Arthur.Bahrs@PROVIDENCE.ORG> wrote:

From: Bahrs, Art <Arthur.Bahrs@PROVIDENCE.ORG>
Subject: OT: Reflection Ports going to an AS/400?
To: HP3000-L@RAVEN.UTC.EDU
Date: Wednesday, February 3, 2010, 4:37 PM
Hi All,
    Any clues?  I haven't found anything searching the archives just yet...=
..

Thanks
Art "firewall fun <NOT> hehehe" Bahrs

Art Bahrs
Security Engineer
(503) 216-2722


This message is intended for the sole use of the addressee, and may contain=
 information that is privileged, confidential and exempt from disclosure un=
der applicable law. If you are not the addressee you are hereby notified th=
at you may not use, copy, disclose, or distribute to anyone the message or =
any information contained in the message. If you have received this message=
 in error, please immediately advise the sender by reply email and delete t=
his message.

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



________________________________
This message is intended for the sole use of the addressee, and may contain=
 information that is privileged, confidential and exempt from disclosure un=
der applicable law. If you are not the addressee you are hereby notified th=
at you may not use, copy, disclose, or distribute to anyone the message or =
any information contained in the message. If you have received this message=
 in error, please immediately advise the sender by reply email and delete t=
his message.

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

0
Bahrs
2/5/2010 3:47:04 PM
Hi Jack :)
   Yes... this was very helpful... sent it on to our Network Engineer doing=
 the work for us...

Thanks!
Art

Art Bahrs
Security Engineer
(503) 216-2722


-----Original Message-----
From: Jack Connor [mailto:jconnor@abtechsupport.com]
Sent: Wednesday, February 03, 2010 5:04 PM
To: Bahrs, Art; HP3000-L@RAVEN.UTC.EDU
Subject: RE: [HP3000-L] OT: Reflection Ports going to an AS/400?

Let me know if this is of any help, Art.

jack

-----Original Message-----
From: Bahrs, Art [mailto:Arthur.Bahrs@PROVIDENCE.ORG]
Sent: Wednesday, February 03, 2010 7:38 PM
To: HP3000-L@RAVEN.UTC.EDU
Subject: [HP3000-L] OT: Reflection Ports going to an AS/400?

Hi All,
    Any clues?  I haven't found anything searching the archives just yet...=
..

Thanks
Art "firewall fun <NOT> hehehe" Bahrs

Art Bahrs
Security Engineer
(503) 216-2722


This message is intended for the sole use of the addressee, and may contain=
 information that is privileged, confidential and exempt from disclosure un=
der applicable law. If you are not the addressee you are hereby notified th=
at you may not use, copy, disclose, or distribute to anyone the message or =
any information contained in the message. If you have received this message=
 in error, please immediately advise the sender by reply email and delete t=
his message.

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

Be sure to ask us about short term and long term rentals on servers, workst=
ations, storage and more!

CONFIDENTIALITY NOTICE: This communication with its contents may contain co=
nfidential information. It is solely for the use of the intended recipient(=
s). Unauthorized interception, review, use or disclosure is prohibited and =
may violate applicable laws including the Electronic Communications Privacy=
 Act. If you are not the intended recipient, please contact the sender and =
destroy all copies of the communication.

This message is intended for the sole use of the addressee, and may contain=
 information that is privileged, confidential and exempt from disclosure un=
der applicable law. If you are not the addressee you are hereby notified th=
at you may not use, copy, disclose, or distribute to anyone the message or =
any information contained in the message. If you have received this message=
 in error, please immediately advise the sender by reply email and delete t=
his message.

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

0
Bahrs
2/5/2010 4:08:09 PM
Reply: