Subject: Re: DTSECTAB
August.Carideo@avon.com
Date: Wed Nov 11 2009 - 15:22:25 EST
on 3.1 you will also get that message if you create a ID longer then 4 char
for a ICCF user
not sure about 4.1
non ICCF user can be greater
if restriction was lifted
industrynews@winw
holesale.com
Sent by: To
owner-vse-l@Lehig "VSE Discussion List"
h.EDU <vse-l@Lehigh.EDU>
cc
11/11/2009 03:05 Subject
PM Re: DTSECTAB
Please respond to
vse-l@Lehigh.EDU
owner-vse-l@Lehigh.EDU wrote on 11/11/2009 01:54:56 PM:
> First off, I didn’t install the VSE (4.1) system so I don’t know the
> complete BSM background. From what I can tell, SEC=YES was used
> because the BSM is running in FB and when I added a new PROG user a
> couple days ago I was “not authorized” to use ICCF and the IESI
> transaction code until I added the user to the appropriate groups.
Well, don't get VSE SEC=YES confused with CICS SEC=YES. The two
are not the same -- even if related. The issue you experienced is related
to CICS SEC=YES but is NOT related to VSE SEC=YES. To use CICS SEC=YES, no
DTSECTAB is required at all. VSE SEC=YES (and DTSECTAB, by association) is
only required for VSE library and batch security. CICS is a separate
issue. Did that clear anything up? ...or, did you already know this much?
Sincerely,
Dave Clark
WinWholesale Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please immediately
notify the sender and delete and destroy the message and all copies. All
unauthorized direct or indirect use or disclosure of this message is
strictly prohibited. No right to confidentiality or privilege is waived or
lost by any error in transmission.
This archive was generated by hypermail 2b25 : Tue Nov 24 2009 - 15:50:06 EST