Huegel, Thomas
2006-03-07 16:59:39 UTC
I used a NICDEF directory statement very similiar to the example below from
the CP Planning and Admin guide. The VSWITCH is defined in the SYSTEM CONFIG
file I do not have a MODIFY VSWITCH GRANT statement for this user. When the
user logs on I get an error saying he is not authorized to couple to the
VSWITCH. I know it is easy enough to fix that with the SET VSWITCH command,
but I was under the impression that this was not necessary if the NICDEF was
used in the directory (even without a MODIFY VSWITCH GRANT), as opposed to a
DEFINE VSWITCH command.
Did I miss something or are the old brain cells in need of a PTF or two?
Define a simulated QDIO adapter using I/O devices 0500-0507 (eight devices)
which will be coupled to the SYSTEM-owned INEWS LAN during LOGON processing:
NICDEF 500 TYPE QDIO DEV 8 LAN SYSTEM INEWS
__________________________________________________________________
<< ella for Spam Control >> has removed VSE-List messages and set aside
VM-List for me
You can use it too - and it's FREE! http://www.ellaforspam.com
the CP Planning and Admin guide. The VSWITCH is defined in the SYSTEM CONFIG
file I do not have a MODIFY VSWITCH GRANT statement for this user. When the
user logs on I get an error saying he is not authorized to couple to the
VSWITCH. I know it is easy enough to fix that with the SET VSWITCH command,
but I was under the impression that this was not necessary if the NICDEF was
used in the directory (even without a MODIFY VSWITCH GRANT), as opposed to a
DEFINE VSWITCH command.
Did I miss something or are the old brain cells in need of a PTF or two?
Define a simulated QDIO adapter using I/O devices 0500-0507 (eight devices)
which will be coupled to the SYSTEM-owned INEWS LAN during LOGON processing:
NICDEF 500 TYPE QDIO DEV 8 LAN SYSTEM INEWS
__________________________________________________________________
<< ella for Spam Control >> has removed VSE-List messages and set aside
VM-List for me
You can use it too - and it's FREE! http://www.ellaforspam.com