Appendix B. MTI Control Statement Reference › B.5 Create or update an MTI Component (MTIGENER)

B.5 Create or update an MTI Component (MTIGENER)

There are two ways to create and update an MTI component.
The first is to manually create the component definitions
in sharedprefix.MICS.GENLIB(cccGENIN) from scratch.

The second way is to let MTI create and maintain the MTI
component.  MTIGENER is used by the MTICREAT and cccUPDAT
jobs to create and update MTI component definitions based
upon the input data.  In this way, the MTI component is
customized to only those resources and resource subtypes
actually in the data.

Note that the purpose of MTIGENER is to create and update
MTI component definitions.  It does not execute the CA MICS
Component Generator.

STATEMENT SYNTAX

%MTIGENER(ccc
          {,INPUTCSV=ddname}
          {,LABEL=label_name}
          {,STEPNUM=step_number}
          {,FILEPREF=file_prefix}
          {,COMMIT=NO | YES})

   where:  Items in brackets are optional
           Items in uppercase are entered exactly as shown
           Items in lowercase (e.g. ddname) are user supplied
STATEMENT OPTION DEFINITIONS

ccc (required)

    is the three character name of the component to be
    generated and must start with U or Z.  If the component
    has been previously defined, MTIGENER will add any new
    resource found on the input data as new files.

The following are optional:

INPUTCSV=ddname

    specifies the DDNAME of the input data.  INPUTCSV is the
    default DDNAME.

LABEL=label_name

    sets the name of the component.  Label_name can be up to
    forty characters.  If LABEL= is not specified, MTIGENER
    creates a name for you.

STEPNUM=step_number

    specifies the step number for the DAILY, WEEKLY, MONTHLY,
    and YEARLY jobs.  It should have a unique value from 150
    through 190. If STEPNUM is not specified, MTIGENER will
    assign the first available step number.  If there is a
    concern that eventually all of the step numbers will be
    used, one should define a new information area within an
    existing user component.

FILEPREF=file_prefix

    sets the first characters of generated file names.  If
    not specified, MTIGENER will use the first two characters
    of the component name.

COMMIT=NO|YES

    controls whether not the definitions will be stored in
    sharedprefix.MICS.GENLIB(cccGENIN).  By default,
    MTIGENER will not update component definitions
    (COMMIT=NO).