The Type Record syntax defines the Type processing sequence in the Type Sequence member for Global Type Processing.
Type records use the following syntax:
TYPe ‘Type-name’ [SYStem ‘system-name’] [CATegory ‘category-value’] DESCription ‘Sample Type Description’.
The following general rules apply to the Type record syntax:
Specifies a one- to eight-character Type. Enclosing the name in single quotes is optional. The name is converted to uppercase characters.
(Optional) Specifies the one- to eight-character System name where the Type is located. Enclosing the name in single quotes is optional. If Types with the same name are located in different Systems, this clause lets you specify different processing orders for each Type and System combination. If this clause is omitted, the Type sequence order for the Type name applies to the entire site. The name is converted to uppercase characters.
(Optional) Specifies a one- to eight-character alphanumeric name for a Type group. Enclosing the category-value in single quotes is required. During Concurrent Action Processing (CAP) dispatch, if Category was specified, the Category value is compared to the previous request. If the Category values match, the action is dispatched and processed simultaneously with the previous request.
The Category value does not affect how the request chains are built or sorted, nor does it affect normal processing order. This parameter simply enables the next Type in the sequence to start processing before the prior Type in the sequence finishes, provided both requests are in the same Category group. If the Category clause is omitted, the Type is still processed in order.
The value is converted to uppercase characters. If CAP is not enabled, the Category clause has no effect.
Note: The Type grouping capability affects processing only when CAP is in effect; it has no effect on Global Type Sequencing itself. Global Type Sequencing alone simply uses the Type processing order defined in the Type Sequencing member, but does not cause the simultaneous processing of actions.
Specifies an up to 50-character description of the Type. Enclosing the description in single quotes is required. When the text contains single quotes, these quotes are converted to blanks. The description text can be entered in either uppercase or lowercase characters.
Example: Global Type Sequence with Type Categories
In this example, the following table lists element Types in the order that a Administrator wants the Types to be processed. The Category column indicates the category for simultaneous processing for Concurrent Action Processing. Thus elements of Type ASMMAC, CHDR, and COPYBOOK can be processed at the same time when the Concurrent Action Processing feature is in use. Regardless of whether Concurrent Action Processing is being used, elements of Type CICSMAP cannot start processing untill all elements of Type COPYBOOK are finished.
|
Type |
System |
Category |
Description |
|
INCLUDE |
|
|
Processor Includes |
|
PROCESS |
|
|
CA Endevor Processors |
|
OPT |
|
|
CONPARMX and Compiler Options |
|
PARM |
|
|
Utility Parameters |
|
ASMMAC |
|
1 |
Assembler Program Macros |
|
CHDR |
|
1 |
Program Headers |
|
COPYBOOK |
|
1 |
COBOL Copybooks |
|
CICSMAP |
|
|
CICS Maps |
|
ASMPGM |
|
2 |
Assembler Program Source |
|
CPGM |
|
2 |
C Program Source |
|
COBOL |
|
2 |
COBOL Program Source |
|
FORTRAN |
|
2 |
FORTRAN Source |
|
JAVA |
|
2 |
JAVA Source |
|
PL1 |
|
2 |
PL/1 Source |
|
EZTINCL |
|
|
EZTRIEVE Includes |
|
EZTRIEVE |
|
|
EZTRIEVE Source |
|
LINK |
|
|
Linkage-Editor JCL |
|
BIND |
|
|
Data Base Binds |
|
Copyright © 2014 CA.
All rights reserved.
|
|