4. CA MICS Facilities › 4.2 CA MICS Component Generator (MCG) › 4.2.4 Generator Definition Statements › 4.2.4.4 Standard Data Element Definition Statements › 4.2.4.4.3 Name Statement (NAME or NAMX)
4.2.4.4.3 Name Statement (NAME or NAMX)
This statement identifies a data element and defines its
program tag, 40-character label, group cluster code (which is
discussed with the OPTION statement), and the status of the
data element in each of the database's timespans. Special
name definitions are used by the generator to indicate
different generation facilities. These are explained under
the description for TAG.
STATEMENT FORMAT
This keyword is coded with the KEYWORD starting in column
1, free-form, and continuing through column 72. Continuation
is not supported. The following describes the format and
coding rules for the statement.
name nnnnnnnn c x d w m y xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
| | | | | | | | |
| | | | | | | | +---LABEL - element description
| | | | | | | |
| | | | | | | +---YEARS - Timespan data element
| | | | | | | active status
| | | | | | |
| | | | | | +---MONTHS - Timespan data element
| | | | | | active status
| | | | | |
| | | | | +---WEEKS - Timespan data element
| | | | | active status
| | | | |
| | | | +---DAYS - Timespan data element
| | | | active status
| | | |
| | | +---DETAIL - Timespan data element
| | | active status
| | |
| | +---CLUSTER - Data element cluster
| | definition
| |
| +---TAG - Data element name (4-8 characters). If
| the data element is not a Common data element
| (X or Xx), then positions 1-3 must contain the
| file ID defined in the FILE statement.
|
+-----Statement identifier - NAME for essential data
elements, or NAMX for non-essential data elements.
STATEMENT OPTIONS DEFINITION
NAME - Defines an essential data element.
- or -
NAMX - Defines a non-essential data element. Typical
user component definitions do not use the NAMX
statement because non-essential data elements
would not be defined.
TAG - Data element name (4-8 characters). If
the data element is not a Common data
element, then positions 1-3 must
contain the file ID defined in the FILE
statement.
There are several names that have
special functions:
@@ACCT - Specifies that the generated
account codes are to be
inserted in place of this
action name. For example, if
the Batch and Operations
Analyzer was being generated
and the user defined two
account codes, then two
fields (ACCTNO1 and ACCTNO2)
would be substituted for the
@@ACCT field.
@@FIRST- Specifies that computation
expressions (EXP) immediately
following this statement are
not to be associated with a
field, but are to be the
first computations made on
this file's content, prior to
calculating the standard
computed elements. A TYPE
statement for computed (C)
elements must precede this
statement.
@@LAST - Specifies that computation
expressions (EXP) immediately
following this statement are
not to be associated with a
field, but are to be the last
computations made on the
contents of this file after
calculating the standard
computed elements. A TYPE
statement for computed (C)
elements must precede this
statement.
CLUSTER - Data element cluster definition.
Normally set to 00, unless one of
the following:
Note: See the individual Product
Guides for information on
cluster codes used in each data
integration product.
Common Definition Cluster Codes
Code Keyword Description
---- ------- --------------------------
99 none Common definition data
element
99xx none Common definition data
element that is also a
CLUSTER of one of the
above clusters.
For example, if the CLUSTER is defined
as 01, then the element will be
included if RACF is defined in the
OPTION statement for the Batch and
Operations Analyzer (SMFGENIN). It
will be excluded if NORACF is defined.
Code 99 is used to point the MCG logic
to a common definition of this data
element, located in either cccGENIN or
$DEGENIN. If 99 is coded in CLUSTER,
the LABEL field on the NAME statement
and all description from the preceding
TYPE statement is ignored. That
information is taken from the
description of the data element with
the same TAG in member cccGENIN or
$DEGENIN.
Code 9901 would define a common data
element (99) that is controlled by the
RACF (01) option.
DETAIL - Timespan data element active status
(Refer to the status definition below.)
DAYS - Timespan data element active status
(Refer to the status definition below.)
WEEKS - Timespan data element active status
(Refer to the status definition below.)
MONTHS - Timespan data element active status
(Refer to the status definition below.)
YEARS - Timespan data element active status
(Refer to the status definition below.)
LABEL - A 40-character element description
(Reference CLUSTER 99, above).
Recommendation on timespan status definition
This definition determines an element's active and
sequence/summary status according to the following
guidelines:
N - Inactive; the data element is not to be kept in the
file for the designated timespan.
0 (zero) - Active; the data element is to be kept in the
file for the designated timespan.
n - Active sequence/summary element; the data element is
to be kept in the file for the designated timespan.
"n" defines the order in which the data element is
used to sequence or summarize the file (n=1 is the
major sequence, n=2 the second most major sequence,
and so forth). Up to 20 sequence/summarization
elements are allowed within a file's timespan
definition.
The @@FIRST and @@LAST elements may not be defined as
sequence/summary fields.
@@ACCT elements are generally defined as
sequence/summary fields, but you do not need to
consider the number of account codes that will
replace this special name because the generator
inserts them and increments the sequence numbers for
you.
For example, if the sequence of a file is SYSID,
account codes, and ENDTS, then SYSID would be defined
as the most major field (n=1), @@ACCT the second most
major field (n=2), and ENDTS the last field (n=3).
If there is more than one account code, say ACCTNO1
and ACCTNO2, the generator inserts them correctly and
increments the sequence definitions of those
following to reflect the number of account numbers
that were inserted. In this example, the sequences
after generation are SYSID (first), ACCTNO1 (second),
ACCTNO2 (third), and ENDTS (fourth).
Dn - Active sequence/summary element; the data element is
to be kept in the file for the designated timespan.
The sequence pattern of this data element will be
descending.
