Generalized Markup Language (GML) is the language used in the ICM of each remote file generated through CA Gen. The information in the ICM defines the contents of the database, RI trigger set, or load module remote file. For database and RI trigger remote files, all of the components specified in the ICM are found in the remote file. For a load module remote file, the complete load module is defined in the ICM, regardless of the number of components included in the remote file. (This is done for maintenance purposes. It allows you to change and regenerate portions of a load module without changing its definition.)
An incomplete load module ICM can result if the subset used to generate the remote file does not contain all the elements for the load module.
The following is an example of how the GML is used in the ICM of an RI trigger remote file.
:remote target=MVS type=CASCADE.
:split member=CASCADE type=ICM.
:execdef
user=USERNM
date=92/12/12
time=15:27:32
os=NT
:source
model='ORDER ENTRY IV'
subset='ALL'
dateup=0000/00/00
timeup=00:00
saved=NO
schema=9.1.A5
level=9.1.A5.01
codepage=1252
:esource.
:systems
source=E:\MODELS\ORDER.IEF\COBOL\.
:esystems.
:execunit
language=COBOL
os=MVS
dbms=DB2
dbname=ORDERDB1
pcompat=YES
Tokens in GML are represented as equate statements, which have an identifier to the left of the equal sign and the variable data to the right of the equal sign. Not all of the equate statements shown in an ICM are used as tokens by the script.
When the equate statements are processed into tokens, they are assigned to one of the five GML token types. The GML token types used by CA Gen follow.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|