While most of your CA Endevor/DB Batch work will be done in the PROCESS mode, the PUNCH mode can be used. Examples of when you might want to use PUNCH mode are:
If you enter a command in PUNCH mode, CA Endevor/DB writes syntax to a punch dataset for all objects in the CCDB that meet the selection criteria. The generated syntax is not echoed on the CA Endevor/DB Batch listing. You can review the punched syntax for the command(s) you entered and, if needed, edit it. You can run the edited commands in PROCESS mode to execute the commands against the CCDB.
If, for example, you wanted to produce syntax for all the entities in the CCDB, you would enter the following commands:
SET OPTION PUNCH.
ADD ENTITY.
CA Endevor/DB would then punch the following:
ADD ENTITY NAME IS "COEDASO "
TYPE IS "DIALOG "
VERSION IS 00001
COMMENT IS "CLAP ON "
.
ADD ENTITY NAME IS "COEDASO-PREMAP "
TYPE IS "PROCESS "
VERSION IS 00001
COMMENT IS "CLAP OFF "
.
ADD ENTITY NAME IS "COEDASO-RESPONSE"
TYPE IS "PROCESS "
VERSION IS 00001
COMMENT IS "CLAP ON "
.
ADD ENTITY NAME IS "COEDSHIP "
TYPE IS "DIALOG "
VERSION IS 00001
COMMENT IS "CLAP OFF "
.
In the example above, CA Endevor/DB punched four ADD ENTITY commands, one for each entity in the CCDB. As you can see, CA Endevor/DB included the NAME, TYPE, VERSION, and COMMENT clauses in the syntax. You can now review all the entities in the CCDB, along with all the information for those entities located in the CCDB.
If you wanted to change any of the commands and then execute them against a CCDB, you can use your standard editor.
In this example CCDB, there are only four entities. If there were more entities in the CCDB, they would also be punched.
|
Copyright © 2013 CA.
All rights reserved.
|
|