Invoking Edit Commands

Managing Environments in Batch › Batch Admin Edit Macros

Batch Admin Edit Macros

Use the Batch Environment Administration facility (Batch Admin) edit commands to create model SCL statements for the Build, Define, and Delete SCL statements. These commands are implemented as ISPF/PDF edit macros.You can invoke the commands in an ISPF/PDF edit session that has the CA Endevor SCM iprfx.iqual.CSIQCLS0 installation library allocated to its SYSPROC concatenation. The edit macros are written in REXX. Therefore, they are only available on TSO/E Version 2 or higher and ISPF/PDF Version 2.3 or higher. To invoke a command, open a blank member in a PDS dataset and execute the command name and object type. The syntax for the edit command is:

├── command name ─ object_type ─┬───────────────┬─ . ──────────────────────────┤
                                └─ object_name ─┘

Command Name

Identifies the SCL action you are creating and places model SCL statements at the current cursor location of the data set you are editing. The following general rules apply to the SCL created by the edit commands:

SCL actions that contain optional clauses with default values are generated using the default value. For example, the Define System action includes the optional clause Comments Not Required.
SCL actions that contain required clauses are generated with a place holder in which you can enter the appropriate information. The place holder is a string of question marks ('?'). For example, the ENBUILD command generates the following To Dsname clause: TO DSNAME ????????? .
There is one SCL clause on each data record. If necessary, an SCL clause can span multiple lines.
The ENDEFINE command and the ENBUILD command generate the Stage Number, instead of the Stage ID, on the To clause.

Specify one of the following commands:

ENDEFINE— Generates model SCL statements for DEFINE statements.

ENDELETE— Generates model SCL statements for DELETE statements.

ENBUILD— Generates model SCL statements for BUILD statements.

Note: For more information about the edit macros, enter ENBUILD HELP, ENDEFINE HELP or ENDELETE HELP on the ISPF/PDF edit session command line to view tutorials.

Object_Type

Identifies the kind of environment definition that you are creating.

The following table provides a list of valid object types and their abbreviations and the corresponding environment definition created. Object types are only valid for the commands marked with an "x" in the table below.

Object_type	Object_type Abbreviations	Environment Definition Created	Valid for ENDEFINE	Valid for ENDELETE	Valid for ENBUILD
SYSTEM	SYS	System	x	x	x
SUBSYSTEM	SUB	Subsystem	x	x	x
TYPE	TYP	Element Type	x	x	x
APPROVER	APP	Approver Group	x	x	x
RELATION	REL	Approver Group Relation	x	x	x
GROUP	GRO	Processor Group	x	x	x
SYMBOL	SYM	Processor Symbol	x	x	x
SEQUENCE	SEQ	Type Sequence*	x		x
ENVIRONMENT	ENV	Environment*			x
DESTINATION	DES	Package Shipment Destination	x	x	x
MAPRULE	MAP	Package Shipment Map Rule for Data Sets*	x	x
USSMAPRULE	USS	Package Shipment Map Rule for USS Path Names*	x	x

*Note:

Type Sequence: You cannot create or delete a Type Sequence. You can only update and build based on an exisiting Type Sequence.

Environment: You cannot delete an Environment. You can use ENBUILD to generate Define SCL that can be used to update the subordinate objects of the Environment or to define a new Environment based on the existing Environment and its subordinate objects.

Package Shipment Map Rules: You can only define or delete map rules. You cannot build a map rule based on an existing map rule.

Object_Name: (Optional.) Names the environment definition for which you are creating SCL. The macro substitutes the object_name into the SCL generated.

Examples: Batch Admin Edit Macro Commands

The following examples show how to code Batch Admin edit macro commands in an ISPF/PDF edit session to create SCL statements.

To create Define SCL for a System, enter one of the following:

ENDEFINE SYSTEM
ENDEFINE SYS

The result is a model Define System statement coded with default options. All variable values are indicated by question marks to indicate where you must specify a value. You can change the default options.

DEFINE SYSTEM '????????'                        
  TO ENVIRONMENT '????????'                     
  DESCRIPTION '???????? '                       
  NEXT SYSTEM '????????'                        
  COMMENTS NOT REQUIRED                         
  CCID NOT REQUIRED                             
  DUPLICATE ELEMENT CHECK IS NOT ACTIVE         
  DUPLICATE PROCESSOR OUTPUT CHECK IS NOT ACTIVE
  ELEMENT JUMP ACKNOWLEDGMENT REQUIRED          
  SIGNOUT IS NOT ACTIVE                         
  SIGNOUT DATASET VALIDATION IS NOT ACTIVE      
  STAGE ONE LOAD LIBRARY IS                     
     '???????? '                                
  STAGE ONE LIST LIBRARY IS                     
     '???????? '                                
  STAGE TWO LOAD LIBRARY IS                     
     '???????? '                                
  STAGE TWO LIST LIBRARY IS                     
     '???????? '

To create a Delete statement for a Subsystem named SUB1, enter one of the following:
- ENDELETE SUBSYSTEM SUB1
- ENDELETE SUB SUB1
The result is a model Delete Subsystem statement coded with the Subsystem name you specified. The Environment and System names need to be added. Also, you can edit the object name SUB1, if you decided on another name.
```
DELETE SUBSYSTEM 'SUB1'      
  FROM ENVIRONMENT '????????'
       SYSTEM '????????'  
```