Administration Guide › Special Comment Reference › *SP= [Sample Profile]

*SP= [Sample Profile]

Lists a PROFILE EXEC file to give to a user ID when a 191 minidisk is defined or when a new user is enrolled in SFS and the IPL statement will be updated with the file pool name. Specify the profile file name in the following format when you add a *SP= comment to a directory entry or skeleton file:

*SP= filename filetype

filename filetype

Name and type of the PROFILE EXEC to assign to a user ID created by way of a skeleton file containing this comment.

CA VM:Director removes the *SP= comment from a user’s directory entry when a 191 minidisk is created for that user ID or when that user ID is enrolled in SFS and the IPL statement is updated with the file pool name, because its information is no longer required.

If the specified sample profile can be found, CA VM:Director copies the profile to the 191 minidisk or top-level directory. If no *SP= special comment is found, CA VM:Director behaves as if *SP= SAMPLE PROFILE was specified. CA VM:Director looks for the specified or default profile as follows:

• First, on your A-disk (or the A-disk of the user ID adding the 191 minidisk or enrolling the user ID)
• Second, on any of the CA VM:Director minidisks in CMS search order. If CA VM:Director cannot find the profile, no profile is copied

To copy any sample profile to an SFS directory, whether specified on a *SP= special comment or defaulted, the Servant Facility must be active. This requirement is not necessary for 191 minidisks.

Copying a sample profile depends on whether you are copying to a 191 minidisk or to an SFS file space:

• When copying to a 191 minidisk:

  CA VM:Director copies the sample profile whenever the minidisk is created.

• When copying to an SFS file space:
  • If a user ID is being enrolled, either explicitly or implicitly, and the IPL statement is going to be updated with the file pool name, CA VM:Director copies the sample profile to the new top-level directory.
  • When the MOVE2SFS command is used and the IPL statement is updated, CA VM:Director copies the sample profile to the top-level directory (which may not be new), regardless of the destination directory of the minidisk being migrated to SFS. The user may already be enrolled in the file pool, and the top-level directory may already have files in it. If the PROFILE EXEC file already exists, no sample profile is copied.

These rules for adding a PROFILE EXEC to a user ID’s new 191 minidisk also apply to the directory entries CA VM:Director creates using the ADDENTRY command with the NOSKEL option. In that case, CA VM:Director uses the directory entry specified by the command in place of a skeleton file.