The SELECT control statement

The SELECT control statement identifies the element to be installed and the operands to be passed to the copy utility or SMP/E to enable its installation. The SELECT control statement must follow a COPY control statement and may span multiple 80-byte records.

Read syntax diagramSkip visual syntax diagram
SELECT control statement

>>-SELECT--type(name)--+---------------------+------------------>
                       |        .-,-----.    |   
                       |        V       |    |   
                       +-ALIAS(---alias-+-)--+   
                       |        .-,------.   |   
                       |        V        |   |   
                       '-EPARM(---option-+-)-'   

>--+--------------------------------------------------------+--->
   '-SHSCRIPT--(--'/directory/file'--+------+--+-------+--)-'   
                                     '-,PRE-'  '-,POST-'        

>--•-----------------------------------------------------------><

type
is the type of the element to be processed. Any valid data element type or hierarchical file system element type, including those with national language identifiers, may be specified. An element type name is formed by stripping the ++ from the beginning of the name of the MCS for that element. For example, the element type for an element defined by a ++CLIST MCS is CLIST, while the element type for a ++HFSRMS MCS is HFSRMS. See Data element MCS for a list of data element MCS and Hierarchical file system element MCS for a list of hierarchical file system element MCS.
name
is the name of element to be processed.
ALIAS
specifies the list of alias names for the data element. This operand applies only to data elements.
EPARM
is the parameter list to be passed for this invocation of the HFSCOPY utility. This operand applies only to hierarchical file system elements. The parameter list consists of an LL value and the actual execution parameters.
  • LL represents a halfword hexadecimal length of the character string (the HFSCOPY utility execution parameters) immediately following it as part of the EPARM value. The length of the character string described does not include the opening parenthesis preceding the LL value nor the closing parenthesis following the last option specified.

    No blanks are allowed between the opening parenthesis and the LL value. The opening parenthesis and the LL value must be in the same record.

    Because the LL value is nondisplayable (ready-to-use) hexadecimal, it may appear as blanks or odd characters. This is valid data and should not be removed or modified.

  • The option values are the execution parameters to be used by the HFSCOPY utility for this invocation of the utility. SMP/E always supplies execution parameters to the HFSCOPY utility, and the parameters are separated by commas with no intervening blanks.
    If the HFSCOPY UTILITY entry that is in effect supplies execution parameters, these values precede the SMP/E-generated information. For example, suppose the UTILITY entry has the following values:
    NAME
    MYHFSCPY
    PRINT
    MYPRINT
    PARM
    A-PARM-FOR-MYHFSCPY
    The character string for the execution parameters would be generated as:
    LLA-PARM-FOR-MYHFSCPY,ELEMENT(hfselm1),TYPE(TEXT),LINK('linknm01'))
    If a PARM value of user_info is specified in an element's MCS, the character string for the execution parameters would be generated as:
    LLA-PARM-FOR-MYHFSCPY,user_info,ELEMENT(hfselm1),TYPE(TEXT),LINK('linknm01'))
    These are the parameters that are generated by SMP/E, using information in the hierarchical file system element entry:
    ELEMENT(element_name)
    the name of the element to be installed in a UNIX file system. The element_name is an unquoted character string 1 to 8 bytes long. It is composed of uppercase alphabetic, numeric, or national ($, #, @) characters.
    LINK('linkname1','linkname2','linkname3'…)
    the alternate names by which this element can be known in the target library within a UNIX file system. A linkname can be up to 1023 characters long and can contain special characters other than just uppercase alphabetic, numeric, or national ($, #, and @) characters.

    SMP/E always puts apostrophes around each linkname and separates multiple values with commas with no intervening blanks.

    SYMLINK('linkname1','linkname2','linkname3'…)
    a list of symbolic links, which are file names that can be used as alternate names for referring to this element in a UNIX file system. Each linkname listed here is associated with a pathname listed in the SYMPATH operand. A symbolic link can be up to 1023 characters long and can contain characters in the range X'40' through X'FE'.

    SMP/E always puts apostrophes around each symbolic link and separates multiple values with commas with no intervening blanks.

    SYMPATH('pathname1','pathname2','pathname3'…)
    a list of pathnames that are associated with symbolic links identified by the SYMLINK operand. A symbolic pathname can be up to 1023 characters long and can contain characters in the range X'40' through X'FE'.

    SMP/E always puts apostrophes around each symbolic pathname and separates multiple values with commas with no intervening blanks.

    SYMPATH appears if SYMLINK appears, otherwise it is omitted.

    For information about how the pathnames and linknames are associated, see the description of the SYMPATH operand and Example 3: Packaging a SYSMOD with a symbolic link in Hierarchical file system element MCS.

    TYPE(TEXT|BINARY)
    the installation format for the element in a UNIX file system. SMP/E generates this parameter from information stored in the element entry in the target zone. If no setting exists for TEXT mode or BINARY mode, SMP/E does not pass this parameter to the HFS copy utility.
SHSCRIPT
indicates that a UNIX shell script is to be invoked to complete the installation of the selected element. This operand applies only to hierarchical file system elements whose ELEMENT entry contains a SHSCRIPT subentry.
/directory/file
is the full path specification for the shell script to be invoked. The /directory/file is derived from the SHELLSCR entry that matches the name in the hierarchical file system element's SHSCRIPT subentry. The SYSLIB subentry of the shell script identifies the ddname of the directory and the shell script name itself is the file.
PRE
indicates the shell script is to be invoked before the selected element is copied to the directory in a UNIX file system. This value is obtained from the SHSCRIPT subentry of the selected element.
POST
indicates the shell script is to be invoked after the selected element is copied to the directory in a UNIX file system. This value is obtained from the SHSCRIPT subentry of the selected element.