I am experiencing a problem when I define multiple skeletons in my VMSECURE MANAGERS file.

Document ID : KB000054888
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

How can I eliminate a problem I'm having when I define many skeletons in my VMSECURE MANAGERS file for a manager?

I receive message VMXEDT0500E Continued 'SKELETON' record exceeds 255 characters when a new user is created by MANAGE. I have shortened the skeleton names as much as possible, but still have this problem. I have the possibility of adding even more skeleton files in the future.

Solution:

The following is documented in the VM:Secure System Administrator's guide, in the chapter VM:Secure Managers File Reference:

The VMSECURE MANAGERS file physical line length is 71 characters.
The maximum logical line length, a record continued over several lines, in the VMSECURE MANAGERS file is 255 characters.

So, this is working as documented.

You can however, include the GRANT ANYSKEL authorization for users that require access to many skeleton files. This GRANT authorizes the user to use any skeleton file that is defined to VM:Secure.

You still have to have one entry on the SKELETON record in the MANAGERS file for these authorized users to indicate their default skeleton for new user creation.

Here is an example of a definition in the VMSECURE MANAGERS file:

MANAGER VMXMAINT * POOL1
SKELETON VMXMAINT GENERAL
DEVTYPE VMXMAINT 3390


This example specifies VMXMAINT?s default skeleton for user creation is GENERAL.
To allow VMXMAINT to use any skeleton file, place the following GRANT record in the VM:Secure AUTHORIZ CONFIG:

GRANT ANYSKEL TO VMXMAINT

ANYSKEL authorization may very well satisfy your needs. It also eliminates having to code a large MANAGERS file to specify all the skeletons defined on your system.