Overview › Batch Coding Conventions › Using a Mask Character For Entity Names › Using Asterisks For Segmented Names

Using Asterisks For Segmented Names

You can use asterisks in different positions within a segmented name. To illustrate these positions, refer to the examples in this section. For these examples, we use entities that have a type of LOGICAL-RECORD. However, the same principles apply to the other three types of entities that have segmented names: SUBSCHEMA, SET, and MODULE.

All the examples in this section refer to the following set of entities of type LOGICAL-RECORD.

The identification of one or more of the entities in this list may be done in several ways. You can specify a whole name, whole name segments, asterisks and commas, or a combination of these.

You can place an asterisk in the following positions:

• As the last, non-blank character in a particular name segment. For example:

  ENTITY NAME = "CUSTOMER-ORDER.SALESUB*.SALESCHM" TYPE = LR
  

  This example identifies a specific logical record, CUSTOMER-ORDER, with each subschema. It requests the indicated logical record for all subschemas whose name begins with "SALESUB", but restricts the request to only those subschemas (and thus only those logical records) compiled against the SALESCHM schema.

  In the table illustrated above, CA Endevor/DB would process records 1, 2, and 3.

• As the last non-blank character in the full name. For example:

  ENTITY NAME = "SALES*"
  

  This example identifies all logical records whose names start with "SALES", regardless of the schema or subschema.

  In the table illustrated above, CA Endevor/DB would process records 4, 5, 6, 7, 8, and 9.

• In place of a name segment. For example:

  SALESPERSON-ORD.*.SALESCHM
  

  This example identifies the SALESPERSON-ORD LOGICAL-RECORD as defined in all subschemas compiled against the schema SALESCHM.

  In the table illustrated above, CA Endevor/DB would process records 7, 8, and 9.