4. CA MICS Facilities › 4.2 CA MICS Component Generator (MCG) › 4.2.4 Generator Definition Statements › 4.2.4.3 MSI Definition Statements › 4.2.4.3.8 File Sequence Statement (SEQUENCE)

Previous Topic: 4.2.4.3.7 Data Element Initialization Statement (INITIALIZE)

Next Topic: 4.2.4.3.9 Data Element Retention Statement (KEEP/DROP)
4.2.4.3.8 File Sequence Statement (SEQUENCE)

All CA MICS files must have a SORT sequence.  In MSI, the
sort sequence is composed of two segments, the User Sequence,
and the Timespan Sequence.  The User Sequence is optional and
consists of user-specified data elements.  The Timespan
Sequence is automatically generated by the MCG and cannot be
modified (except for some minor tailoring).  It consists of
common data elements describing the date and time the file is
summarized and sorted.

The SEQUENCE statement allows the specification of the User
Sequence.  If no SEQUENCE is specified, then no User Sequence
is applied to the sort sequence.

***********************  IMPORTANT  *************************
*                                                           *
*  NOTE:  In addition to the SEQUENCE statement, you must   *
*         insert a NAME @@ACCT statement in each file in    *
*         which you want cccACTn data elements.             *
*                                                           *
***********************  IMPORTANT  *************************

STATEMENT FORMAT

This keyword is coded with the KEYWORD starting in column 1,
free-form, and continuing through column 72.  Continuation is
not supported, although multiple SEQUENCE statements can be
specified.  The following describes the format and coding
rules for the SEQUENCE statement.

  SEQUENCE elements ...
           |
           +---ELEMENTS - Data Elements

STATEMENT OPTION DEFINITIONS

  SEQUENCE- Defines the data elements in this file which
            will specify the data elements of the User
            Sequence.

            ELEMENTS - The data element names of the User
                       Sequence.  Data Elements can also
                       include @@ACCT, which is the account
                       code structure.  Generic specification
                       is not allowed.

STATEMENT EXAMPLE

SEQUENCE SYSID DEVNAME @@ACCT