CA Endevor® SCM - 17.0 - ENU - Administrating - 20180504
CA Endevor® SCM - 17.0 - ENU - Administrating - 20180504
CA Endevor® SCM - 17.0 - ENU - Administrating - 20180504
17.0
Administrating
Date: 04-May-2018
CA Endevor® SCM - 17.0
This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as
the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This
Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or
duplicated, in whole or in part, without the prior written consent of CA.
If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make
available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with
that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.
The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable
license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to
certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY
KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE,
DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST
INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE
POSSIBILITY OF SUCH LOSS OR DAMAGE.
The use of any software product referenced in the Documentation is governed by the applicable license agreement and such
license agreement is not modified in any way by the terms of this notice.
Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions
set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or
their successors.
Copyright © 2018 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to
their respective companies.
04-May-2018 3/1109
Table of Contents
Administrating 4
Automated Configuration ........................................................................... 68
Software Configuration Management ........................................................................................................ 68
ACM Facilities ........................................................................................................................................... 70
Component Monitor ............................................................................................................................. 70
Component List ................................................................................................................................... 70
Component Data and Batch Reporting ............................................................................................... 71
Software Control Language (SCL) Enhancements ............................................................................. 71
ACM Query Facility ............................................................................................................................. 71
ACM Operational Areas ............................................................................................................................ 72
Data Collection .................................................................................................................................... 72
Data Storage ....................................................................................................................................... 72
Software Configuration Analysis and Management ............................................................................ 74
Using ACM ................................................................................................................................................ 74
Configure the ACM Facility ................................................................................................................. 74
Enable ACM and the ACM Query Facility .................................................................................. 75
Activate the ACM Query Facility ................................................................................................ 75
Maintaining Root and Cross-Reference Data Sets ............................................................................. 78
How to Reorganize Root and Cross-Reference Data Sets ........................................................ 79
How to Create Backup Copies of the ACM Query Data Sets .................................................... 79
How to Synchronize ACM Query Data with Inventory Data ....................................................... 79
How to Monitor and Collect Data ........................................................................................................ 80
Component Monitor .................................................................................................................... 80
Program Object Support ............................................................................................................ 80
Activate the ACM Component Monitor ....................................................................................... 81
How to Monitor Components in Dynamically Allocated Data Sets ............................................. 81
How to Monitor Input Components ............................................................................................. 82
How to Monitor Components in a Generate Processor .............................................................. 82
How to Monitor Components in a Move Processor .................................................................... 85
How to Monitor Components in a Delete Processor .................................................................. 87
How to Store Configuration Information .............................................................................................. 87
Component List .......................................................................................................................... 88
View Component List Information ....................................................................................................... 91
Display Summary Information (SX) ............................................................................................ 92
Display the Current Version and Level of an Element (BX) ....................................................... 92
Display Component Changes (CX) ............................................................................................ 92
Display Change History (HX) ..................................................................................................... 92
Input and Output Component Footprints .................................................................................... 92
How Element Processing Works ......................................................................................................... 93
ACM Query Facility ................................................................................................................................... 93
Start ACMQ ......................................................................................................................................... 93
Refresh ACMQ Data ........................................................................................................................... 94
ACMQ Circular, Indirect, Related References ........................................................................... 94
Administrating 5
Circular References ................................................................................................................... 94
Indirect References .................................................................................................................... 95
Related Element References ..................................................................................................... 96
ACM Query Panel ............................................................................................................................... 96
ACMQ Create GENERATE SCL Panel ............................................................................................... 98
ACM Submit JOBCARD Statements Panel ......................................................................................... 99
Batch SCM Query Utility ..................................................................................................................... 99
Create SCL Statements for Generate Actions ........................................................................... 99
Create a Query Report Using the Batch ACM Query Utility ..................................................... 102
List Using Components For Element ....................................................................................... 102
List Used Components For Element ........................................................................................ 104
Analyzing and Managing Software Configuration Information ................................................................ 106
Software Control Language .............................................................................................................. 106
LIST Action ............................................................................................................................... 106
Print Action ............................................................................................................................... 107
Set Build Statement ................................................................................................................. 108
Set Options Statement ............................................................................................................. 108
Set Where Statement ............................................................................................................... 108
Clear Statements ..................................................................................................................... 109
How to Perform Impact Analysis ....................................................................................................... 109
How to Analyze System Behavior ............................................................................................ 109
How to Propagate a Component Change to All Affected Programs ........................................ 111
How to Validate a System for Consistent Use of Components ................................................ 114
How to Recreate Past Program Versions ................................................................................ 117
How to Move Related Source Components During Promotion to Production .......................... 119
How to Add Related Elements to a Component List ................................................................ 121
How to Write Elements to an External Location ....................................................................... 121
Administrating 6
Commands and Function Keys ......................................................................................................... 126
TSO and Roscoe ............................................................................................................................... 127
Name Masking .................................................................................................................................. 127
Display List Processing ..................................................................................................................... 127
The Environment Selection List ............................................................................................... 128
The System Selection List ........................................................................................................ 128
The Subsystem Selection List .................................................................................................. 129
The Action Prompt Panel ......................................................................................................... 129
Processing Elements in the Foreground ................................................................................................. 130
Foreground Default Values for Action Options .................................................................................. 130
Displaying Element Information in the Foreground ........................................................................... 130
The Option Field ....................................................................................................................... 131
The List Panels ........................................................................................................................ 133
The Environment Selection List ............................................................................................... 133
The System Selection List ........................................................................................................ 134
The Subsystem Selection List .................................................................................................. 134
The Element Selection List ...................................................................................................... 135
The Summary of Levels Panel ................................................................................................. 136
The Element Master Panels ..................................................................................................... 138
The Element Browse Panel ...................................................................................................... 141
The Element Changes Panel ................................................................................................... 143
The Element History Panel ...................................................................................................... 145
Displaying Footprint Information ........................................................................................................ 148
The Footprint Display Panel ..................................................................................................... 148
Footprint Display Panel Fields ................................................................................................. 149
The Library Selection List ......................................................................................................... 149
The CA Endevor® SCM Load Module IDR Display Panel ....................................................... 151
The CA Endevor® SCM Browse Panel for a Footprinted Member .......................................... 152
Retrieving Elements Using the Foreground Retrieve Action ............................................................. 152
Element Selection List for Retrieve Action ............................................................................... 155
Processing Elements in Batch ................................................................................................................. 156
Accessing the Batch Options Menu .................................................................................................. 156
Build SCL .......................................................................................................................................... 157
The SCL Generation Panel ...................................................................................................... 158
Displaying Element Information in Batch ........................................................................................... 159
Adding and Updating Elements ......................................................................................................... 159
The Member Selection List for the Add/Update Action ............................................................ 162
The Type Selection List ............................................................................................................ 163
The Processor Group Selection List ........................................................................................ 164
Retrieving Elements .......................................................................................................................... 165
The Element Selection List for the Retrieve Action .................................................................. 168
Retrieving Prior Versions ......................................................................................................... 169
Administrating 7
Generating Elements ........................................................................................................................ 169
The Element Selection List for the Generate Action ................................................................ 172
Moving Elements ............................................................................................................................... 173
The Element Selection List for the Move Action ...................................................................... 176
Deleting Elements ............................................................................................................................. 177
The Element Selection List for the Delete Action ..................................................................... 179
Printing Elements .............................................................................................................................. 181
The Element Selection List for the Print Elements Action ........................................................ 183
Signin Elements ................................................................................................................................ 184
The Element Selection List for the Signin Action ..................................................................... 186
Transferring Elements ....................................................................................................................... 187
The Element Selection List for the Transfer Action .................................................................. 191
Printing Members .............................................................................................................................. 193
The Member Selection List for the Print Members Action ........................................................ 193
Listing Elements ................................................................................................................................ 194
The Element Selection List for the List Element Action ........................................................... 196
The List Output Panel .............................................................................................................. 198
Listing Members ................................................................................................................................ 198
The Member Selection List for the List Member Action ........................................................... 200
Archiving Elements ........................................................................................................................... 201
The Element Selection List for the Archive Action ................................................................... 203
Edit the Request Data Set ................................................................................................................. 204
Submit the Request Data Set ............................................................................................................ 205
Build the JCL for the Action Request ................................................................................................ 206
Estimating Resource Requirements ........................................................................................................ 206
CA Endevor SCM CA Roscoe Interface Resource Requirements (Roscoe) .................................... 206
Interface Processing Structure .......................................................................................................... 206
Interface Storage Requirements ....................................................................................................... 207
CA Endevor CA Roscoe Interface Messages ......................................................................................... 208
C1R1001 ........................................................................................................................................... 209
C1R101I ............................................................................................................................................ 209
C1R102E ........................................................................................................................................... 209
C1R103E ........................................................................................................................................... 210
C1R104E ........................................................................................................................................... 210
C1R105E ........................................................................................................................................... 210
C1R106E ........................................................................................................................................... 211
C1R107E ........................................................................................................................................... 211
C1R108E ........................................................................................................................................... 211
C1R109E ........................................................................................................................................... 212
C1R110E ........................................................................................................................................... 212
C1R115E ........................................................................................................................................... 212
C1R118E ........................................................................................................................................... 213
Administrating 8
C1R119I ............................................................................................................................................ 213
C1R120E ........................................................................................................................................... 213
C1R122I ............................................................................................................................................ 214
C1R201E ........................................................................................................................................... 214
C1R202E ........................................................................................................................................... 214
C1R203E ........................................................................................................................................... 215
C1R205E ........................................................................................................................................... 215
C1R301E ........................................................................................................................................... 215
C1R302E ........................................................................................................................................... 216
C1R303E ........................................................................................................................................... 216
C1R304E ........................................................................................................................................... 216
C1R305E ........................................................................................................................................... 217
C1R306E ........................................................................................................................................... 217
C1R307E ........................................................................................................................................... 217
C1R308E ........................................................................................................................................... 218
C1R309E ........................................................................................................................................... 218
C1R311E ........................................................................................................................................... 218
C1R312E ........................................................................................................................................... 219
C1R313E ........................................................................................................................................... 219
C1R314E ........................................................................................................................................... 219
C1R316E ........................................................................................................................................... 220
C1R318E ........................................................................................................................................... 220
C1R319E ........................................................................................................................................... 220
C1R320E ........................................................................................................................................... 220
C1R502E ........................................................................................................................................... 221
C1R503I ............................................................................................................................................ 221
C1R507I ............................................................................................................................................ 221
C1R504E ........................................................................................................................................... 222
C1R505I ............................................................................................................................................ 222
C1R506E ........................................................................................................................................... 222
Installing the Interface ............................................................................................................................. 222
How the CA Roscoe Interface Works ................................................................................................ 223
Install the Configuration Module ............................................................................................... 224
Update the Initialization Exit ..................................................................................................... 224
Modify the Roscoe ETSO Eligible Program List (EPL) ............................................................ 225
Update the Roscoe Application JCL ........................................................................................ 226
Modify ROSXINIT ..................................................................................................................... 227
Copy the Interface RPFs to the Public RPF Library ................................................................. 227
Create the Interface Panel Library Userid ................................................................................ 228
Recycle the Roscoe System .................................................................................................... 228
Install the CA Endevor SCM Batch JCL ................................................................................... 228
How to Make the Interface Unavailable to Users .............................................................................. 229
Administrating 9
Quiesce the Interface ............................................................................................................... 229
Terminate the Roscoe Interface ............................................................................................... 229
Administrating 10
Resizing and Allocating New Base Libraries ..................................................................................... 259
Resizing the Delta Libraries .............................................................................................................. 260
Evaluating and Modifying Processors ............................................................................................... 260
Running a Full Unload of Each Environment .................................................................................... 260
Adjusting Type Definitions ................................................................................................................. 260
Reloading Inventory by System ........................................................................................................ 260
Validating the Results ....................................................................................................................... 261
How to Convert a Forward/Reverse Delta to a Full-Image Delta ............................................................ 261
Restore Action and Converting Delta Formats ........................................................................................ 261
How to Convert Elements to Log Delta Format ....................................................................................... 262
Administrating 11
Processor Groups ................................................................................................................................... 279
Processors and Element Types .............................................................................................................. 279
Processors Invoked by Actions ............................................................................................................... 280
Writing Processors .................................................................................................................................. 281
Processor Names .............................................................................................................................. 282
Processor Features ........................................................................................................................... 284
Reserved Words and Labels for Processors ............................................................................ 284
Authorized Program Table ................................................................................................................ 285
Processor Keywords ......................................................................................................................... 285
The FOOTPRNT Keyword ....................................................................................................... 285
MAXRC Keyword ..................................................................................................................... 287
EXECIF Keyword ..................................................................................................................... 288
BACKOUT Keyword ................................................................................................................. 289
MONITOR Keyword ................................................................................................................. 289
ALTID Keyword ........................................................................................................................ 290
Symbolic Parameters ........................................................................................................................ 294
Ampersand (&) Character ........................................................................................................ 294
Symbols Guidelines ................................................................................................................. 295
User Symbols ........................................................................................................................... 297
Site Symbols ............................................................................................................................ 297
CA Endevor® SCM Symbols ................................................................................................... 299
In-Stream Data ......................................................................................................................... 307
Controlling Processor Flow Using the IF-THEN-ELSE Statement .................................................... 308
RC Expression ......................................................................................................................... 315
The ABENDCC Expression ...................................................................................................... 315
ABEND Expression .................................................................................................................. 315
ABEND Expression .................................................................................................................. 315
RUN True Expression .............................................................................................................. 315
RUN False Expression ............................................................................................................. 316
IF-THEN-ELSE Trace Facility .................................................................................................. 316
Dynamically Allocated Libraries ........................................................................................................ 317
Internal Reader ................................................................................................................................. 318
Processor Utilities .................................................................................................................................... 319
Including Processor Utilities in Processor Logic ................................................................................ 319
BC1PDSIN Utility .............................................................................................................................. 321
BC1PTMP0 Utility .............................................................................................................................. 322
Sample JCL and Parameters ................................................................................................... 323
Return Codes ........................................................................................................................... 323
REXX Exec or CLIST Executing a DB2 Bind ........................................................................... 324
BC1PXFPI Utility ............................................................................................................................... 325
BC1PMVCL Utility .................................................................................................................... 325
BSTCOPY Utility ............................................................................................................................... 326
Administrating 12
BSTCOPY Copy Functions ...................................................................................................... 326
C1BM3000 Utility .............................................................................................................................. 330
Considerations When Using the C1BM3000 Utility .................................................................. 331
C1WORK01-06 DD Statements ............................................................................................... 331
C1PRMGEN Utility ............................................................................................................................ 332
CONAPI Utility ................................................................................................................................... 333
CONDELE Utility ............................................................................................................................... 334
CONLIST Utility ................................................................................................................................. 335
Banner Pages .......................................................................................................................... 335
STORE Option ......................................................................................................................... 336
PRINT Option ........................................................................................................................... 337
PRTMBR (Print Member) Option ............................................................................................. 337
The COPY Option .................................................................................................................... 338
DELETE Option ........................................................................................................................ 338
Guidelines When Creating Listings .......................................................................................... 339
CONPARMX Utility ............................................................................................................................ 341
How to Create a CONPARMX Processor JCL Step ................................................................ 341
CONPARMX - Dynamically Build a Parameter String .............................................................. 342
How CONPARMX Creates a Parameter String ....................................................................... 345
Return Codes for CONPARMX ................................................................................................ 347
Options Member Syntax Rules ................................................................................................ 347
Options Member Examples ...................................................................................................... 348
CONRELE Utility ............................................................................................................................... 349
CONRELE Utility Commands ................................................................................................... 349
RELATE ELEMENT Command Syntax .................................................................................... 350
RELATE MEMBER Command Syntax ..................................................................................... 351
RELATE OBJECT Command Syntax ...................................................................................... 351
RELATE COMMENT Command Syntax .................................................................................. 351
SET ERROR RETURN CODE Command Syntax ................................................................... 352
Example of CONRELE Syntax ................................................................................................. 352
CONSCAN Utility .............................................................................................................................. 353
CONSCAN Parameter Data Set .............................................................................................. 354
PARMSCAN Parameter Statements ........................................................................................ 354
Excluding Source Data ............................................................................................................. 354
Selecting Source Data ............................................................................................................. 356
Scan Rule Processing .............................................................................................................. 363
CONWRITE Utility ............................................................................................................................. 364
Writing Component List Data to an External Location ............................................................. 364
Writing Elements to an External Location ................................................................................ 365
The Standard Form of CONWRITE ......................................................................................... 365
Extended Form of CONWRITE ................................................................................................ 366
Command Syntax for the CONWRITE Utility ........................................................................... 366
Using CONWRITE to Expand INCLUDEs ................................................................................ 368
Administrating 13
Writing Exit Programs to Use CONWRITE Input ..................................................................... 369
ENUSSUTL Utility ............................................................................................................................. 370
LEXTRCTR and BC1PCCSP Utilities ............................................................................................... 370
Classifying and Managing Processors .................................................................................................... 370
Implement Processors ...................................................................................................................... 371
Maintain Processors .......................................................................................................................... 373
Where CA Endevor® SCM Looks for Processors .................................................................... 373
Using Processor Groups ......................................................................................................................... 373
Processor Groups Overview ............................................................................................................. 373
Suggested Naming Conventions for Processor Groups .......................................................... 374
Processor Group Information ............................................................................................................ 376
Create, Update, and Display Processor Group Information (Environment Options Menu) ...... 376
Create, Update, and Display Processor Group Information (Type Definition Panel) ............... 377
Change or Display Processor Group Symbols .................................................................................. 377
Change or Display Processor Group Symbols - Example ....................................................... 378
Display Processors .................................................................................................................. 379
Processor Group Selection List ......................................................................................................... 379
Processor Group Definition Panel ..................................................................................................... 380
Identification Fields .................................................................................................................. 381
Output Management Information Fields ................................................................................... 382
Processor Group Symbolics Panel ................................................................................................... 384
Identification Fields .................................................................................................................. 384
Symbolic Identification Fields ................................................................................................... 384
Processor Display Panel ................................................................................................................... 384
Sample Processors ................................................................................................................................. 385
How to Convert PROCs to Processors ............................................................................................. 385
Generate Processors ........................................................................................................................ 386
The GASMNBL Generate Processor ....................................................................................... 387
The GCIIDBL Generate Processor .......................................................................................... 389
The GCIINBL Generate Processor .......................................................................................... 392
The GLNKNBL Generate Processor ........................................................................................ 394
The LOADONLY Generate Processor ..................................................................................... 396
Delete Processors ............................................................................................................................. 397
The DLODDNL Delete Processor ............................................................................................ 397
The DLODNNL Delete Processor ............................................................................................ 398
Move Processors .............................................................................................................................. 398
The MLODDNL Move Processor ............................................................................................. 399
The MLODNNL Move Processor ............................................................................................. 401
Other Processors .............................................................................................................................. 402
CSP Processors ................................................................................................................................ 402
The GELCL CSP Processor ..................................................................................................... 403
The GELPCLB CSP Processor ................................................................................................ 407
Administrating 14
The GELTCL CSP Processor .................................................................................................. 412
The GELPTCLB CSP Processor .............................................................................................. 417
The GCSP41LN CSP Processor .............................................................................................. 423
Unsupported Parameters ........................................................................................................................ 425
General Restrictions .......................................................................................................................... 425
SET Statement .................................................................................................................................. 425
INCLUDE Statement ......................................................................................................................... 426
EXEC Statement Parameters ........................................................................................................... 426
DD Statement Parameters ................................................................................................................ 426
DCB Subparameters ......................................................................................................................... 426
DDNAME Subparameters ................................................................................................................. 427
Administrating 15
Footprint Synchronization ........................................................................ 438
How Synchronizing Source and Executables Works .............................................................................. 438
FOOTPRNT=VERIFY Statement ...................................................................................................... 438
Footprint Reports ..................................................................................................................... 439
Source Input from Executables ............................................................................................................... 439
How to Install Remote Footprint Synchronization ................................................................................... 439
How CA Endevor SCM Stores Footprints ............................................................................................... 440
Footprints and Library Data Sets ...................................................................................................... 440
Footprints and Sequential Object Data Sets ..................................................................................... 441
Footprints and Load Libraries ........................................................................................................... 441
Footprints and PDS/E Load Libraries ................................................................................................ 441
Footprints and USS Directories ......................................................................................................... 441
How to Copy the C1DEFLTS Table ........................................................................................................ 442
How to Create CONLIB ..................................................................................................................... 442
How to Create the JCL Library .......................................................................................................... 442
Sample JCL .............................................................................................................................. 442
BC1JFEXT ............................................................................................................................... 443
How to Use the Footprint Synchronization Facility .................................................................................. 443
Footprint Report Information ................................................................................................................... 444
How to Generate Footprint Reports ........................................................................................................ 444
How to Specify Data Extract Phase Selection Criteria ...................................................................... 445
Syntax Examples for Generating Footprint Reports .......................................................................... 447
Name Masking .................................................................................................................................. 448
CONRPT80 Library Member Footprint Report ........................................................................................ 448
Library Member Footprint Report ...................................................................................................... 448
CONRPT81 Library CSECT Listing ......................................................................................................... 449
Library CSECT Listing Report ........................................................................................................... 449
CONRPT82 Library Zapped CSECT Profile ............................................................................................ 450
Library Zapped CSECT Profile Report .............................................................................................. 451
CONRPT83 Footprint Exception Report ................................................................................................. 452
Footprint Exception Report ............................................................................................................... 452
Executable Module Footprint Report - Sample JCL ................................................................................ 454
VSE/ESA - Sample JCL .................................................................................................................... 454
VM/ESA EXEC - Sample JCL ........................................................................................................... 454
z/OS - Sample JCL ........................................................................................................................... 455
Administrating 16
CA Endevor SCM InfoMan Interface Operation ...................................................................................... 457
The CA Endevor SCM InfoMan Interface Batch Utility ............................................................................ 458
The CA Endevor SCM InfoMan Interface Package Level ....................................................................... 459
Information Available from the Package Level of the Interface ......................................................... 460
The CA Endevor SCM InfoMan Interface Action Level ........................................................................... 460
Information Available from the Action Level of the Interface ............................................................. 461
Installing infoman interface ...................................................................................................................... 461
How CA Endevor SCM InfoMan Interface Installation Works ........................................................... 462
How Installation at Customized InfoMan Sites Works .............................................................. 462
How Installation at IIF Sites Works .......................................................................................... 462
How to Install Basic InfoMan ............................................................................................................. 462
Define Users to InfoMan Classes ............................................................................................. 463
Prepare a Session Parameter Member .................................................................................... 463
Put Information Management Load Library Data Set in LINKLIST .......................................... 463
Move BLGISPFD into ISPPLIB ................................................................................................ 463
Summary of Basic InfoMan Installation .................................................................................... 464
How to Modify Basic InfoMan for the Interface ................................................................................. 464
Copy Interface Report Shells into the RFT Data Set ............................................................... 464
Copy Modified BLG6CORQ into the RPANEL0 Data Set ........................................................ 465
Copy Dictionary Update ........................................................................................................... 465
Create the Standard IBM PIDT and PIPT Tables .................................................................... 466
Build a Rule Set ....................................................................................................................... 466
Copy the BLGSESxx Module to STEPLIB ............................................................................... 466
How to Connect the Interface ............................................................................................................ 467
Modify the EINFO Macro .......................................................................................................... 467
Assemble and Link BC1TEI90 ................................................................................................. 468
Reassemble C1DEFLTS with the InfoMan Password .............................................................. 469
Make Sure Required Panels Are in ISPPLIB ........................................................................... 469
Make Sure INFO01, PKEX21, and PKMR02 Are in ISPMLIB .................................................. 469
Edit C1SB3000 Skeleton JCL .................................................................................................. 469
How to Verify the Installation ............................................................................................................. 469
Required PIDT and PIPT Tables .............................................................................................. 471
Setting Up the CA Endevor SCM INFO Table ......................................................................................... 473
The CA Endevor® SCM Side of the Interface ................................................................................... 473
How to Implement the CA Endevor® SCM Side ............................................................................... 474
CA Endevor® SCM INFO Table Syntax ............................................................................................ 474
Table Syntax Components ....................................................................................................... 475
Syntax Diagram Conventions ................................................................................................... 476
The TABLE Statement ...................................................................................................................... 476
The Control Block .............................................................................................................................. 477
Control Block Syntax ................................................................................................................ 477
Possible Requests ................................................................................................................... 479
Administrating 17
CTRL Statement Examples ...................................................................................................... 480
Use Blocks ........................................................................................................................................ 480
The USE Statement ................................................................................................................. 481
The NOTFOUND Statement .................................................................................................... 483
The FOUND Statement ............................................................................................................ 484
The EUSE Statement ............................................................................................................... 484
Label Blocks ...................................................................................................................................... 485
The LABEL Statement ............................................................................................................. 485
The ELABEL Statement ........................................................................................................... 486
CPASS/CFAIL Statements ....................................................................................................... 486
TSP Statements ....................................................................................................................... 487
Comments ................................................................................................................................ 488
RC Statements ......................................................................................................................... 489
MSG Statements ...................................................................................................................... 490
Criteria Blocks ................................................................................................................................... 491
The Populate Block ........................................................................................................................... 492
FIELD Statements ............................................................................................................................. 494
FIELD Statement Syntax .......................................................................................................... 495
Field Panel (Pname) and Index (S-Word) Clauses .................................................................. 496
The Length Value ..................................................................................................................... 496
The Value Clause - Criteria Block ............................................................................................ 496
The Value Clause - Populate Block ......................................................................................... 497
The IFYES/IFNO Statement ..................................................................................................... 497
TEXT Clauses .......................................................................................................................... 498
CA Endevor® SCM Control Block Availability ................................................................................... 498
Control Blocks for Stand-alone Actions .................................................................................... 498
Available $ENVDS Fields ......................................................................................................... 499
Available $ELMDS Fields ......................................................................................................... 500
Available $FILDS Fields ........................................................................................................... 507
Available $ECBDS Fields ......................................................................................................... 507
Available $REQPDS Fields ...................................................................................................... 508
Control Blocks for Packages and Package Actions ................................................................. 509
$PREQPDS .............................................................................................................................. 510
$PHDRDS ................................................................................................................................ 511
$PACTREQ .............................................................................................................................. 512
Interface Syntax Batch Utility Output Report ..................................................................................... 514
Setting Up the Interface ........................................................................................................................... 514
The InfoMan API ............................................................................................................................... 514
How to Set Up the InfoMan Side ....................................................................................................... 515
How to Build InfoMan PIDT Tables ................................................................................................... 516
Inquiry PIDT Required Fields ................................................................................................... 517
Retrieve PIDT Required Fields ................................................................................................ 517
Administrating 18
Create PIDT Required Fields ................................................................................................... 518
Update PIDT Required Fields .................................................................................................. 519
Using the Stand-alone Action Table Syntax Template ............................................................................ 519
The Syntax Template ........................................................................................................................ 520
IIF Syntax Templates for Stand-Alone Actions ........................................................................ 520
IIF Sample Syntax ............................................................................................................................. 520
Building the CA Endevor SCM Info Table Using Table Syntax ............................................................... 535
Displaying Interface Information .............................................................................................................. 547
How to Display Information Stored in InfoMan .................................................................................. 547
How to List and Display CCID Information ........................................................................................ 547
The CCID List Panel ................................................................................................................ 548
The Action Prompt Panel ......................................................................................................... 548
The CCID Correlation Panel .................................................................................................... 549
How to Display Package Information ................................................................................................ 549
Using Interface Reports ........................................................................................................................... 550
The Interface Reports ....................................................................................................................... 550
Run the Reports in Native InfoMan ................................................................................................... 551
Run the Reports in Batch .................................................................................................................. 551
Contention for the ISPF Profile Data Set ................................................................................. 551
How to Set Defaults in InfoMan for Output Destination and Class for Reports ........................ 551
How to Customize the Reports ......................................................................................................... 552
The Action Change Record Summary Report ................................................................................... 552
The Action Change Record Detail Report ......................................................................................... 553
The Action Problem Record Summary/Detail Reports ...................................................................... 553
The Package Parent Record Summary Report ................................................................................. 554
The Package/Activity Record Summary Report ................................................................................ 554
The Package/Activity Record Detail--Package Detail Report ........................................................... 556
The Package/Activity Detail--Activity Detail Report ........................................................................... 556
Information for Advanced Users .............................................................................................................. 556
The Modified Assisted Entry Panel (BLG6CORQ) ............................................................................ 556
The PMF Report for the BLG6CORQ Panel ............................................................................ 557
Customized Dictionary Entry ............................................................................................................. 557
The PWORD XREF Report ...................................................................................................... 557
Reserved InfoMan Fields .................................................................................................................. 557
Inquiry PIDT Required Fields ................................................................................................... 557
Retrieve PIDT Required Fields ................................................................................................ 558
Create PIDT Required Fields ................................................................................................... 559
Update PIDT Required Fields .................................................................................................. 559
Installing the Interface Under IIF ............................................................................................................. 560
Phase 1. How to Install Basic InfoMan .............................................................................................. 560
Step 1. Define Users to InfoMan Classes ................................................................................ 561
Step 2. Prepare a Session Parameter Member ....................................................................... 561
Administrating 19
Step 3. Put Information Management Load Data Set in LINKLIST .......................................... 561
Step 4. Move BLGISPFD into ISPPLIB .................................................................................... 562
Phase 1 Summary .................................................................................................................... 562
Phase 2. How to Modify Basic InfoMan for the Interface .................................................................. 562
Step 1. Copy Interface Report Shells into the RFT Data Set ................................................... 562
Step 2. Copy Modified Panels into the RPANEL0 Data Set .................................................... 563
Step 3. Copy Dictionary Update ............................................................................................... 563
Step 4. Create CA PIDT and PIPT Tables ............................................................................... 564
Step 5. Build a Rule Set ........................................................................................................... 564
Step 6. Copy the BLGSESxx Module to STEPLIB ................................................................... 565
Phase 2 Summary .................................................................................................................... 565
Phase 3. How to Connect the Interface ............................................................................................ 565
Step 1. Modify the EINFO Macro ............................................................................................. 565
Step 2. Assemble and Link BC1TEI90 ..................................................................................... 567
Step 3. Reassemble C1DEFLTS with the InfoMan Password ................................................. 567
Step 4. Make Sure Required Panels Are in ISPPLIB ............................................................... 567
Step 5. Make Sure INFO01, PKEX21, and PKMR02 Are in ISPMLIB ..................................... 568
Step 6. Edit C1SB3000 Skeleton JCL ...................................................................................... 568
Phase 4. How to Verify the Installation ............................................................................................. 568
Required PIDT and PIPT Tables .............................................................................................. 570
Administrating 20
How the SET ASSIGN Statement Assigns the Default CCID and Comment .......................... 585
How to Use Additional SET ASSIGN Statements within Requests .......................................... 585
How Clear Statements Work ............................................................................................................. 586
How the CLEAR ALL Statement Works ................................................................................... 586
How the CLEAR ASSIGN Statement Works ............................................................................ 586
How the CLEAR FROM/USING Statement Works .................................................................. 586
How the EOF (EOJ) Processing Statement Works ........................................................................... 587
How Analyze Requests are Processed ............................................................................................. 587
Customizing the Inventory Analyzer .................................................................................................. 588
How to Customize the Inventory Analyzer ............................................................................... 588
How to Customize the Output Model Definition ....................................................................... 588
How Symbolics Work ............................................................................................................... 589
How the Output Model Definition Template Works .................................................................. 592
How Symbolics Work in the Output Model Definition Template ............................................... 593
How the Same Template is Used for a SUCCESS and FAILURE Condition ........................... 594
Change Type and Processor Group Conventions ................................................................... 594
How ESTABLISH Statements Change Types and Processor Groups ..................................... 595
Using the Inventory Analyzer Reports ..................................................................................................... 595
Report Options .................................................................................................................................. 596
Parameter Syntax Report .................................................................................................................. 596
Request Syntax Report ..................................................................................................................... 596
Output Model Definition Syntax Report ............................................................................................. 597
Final Request Interpretation Report .................................................................................................. 597
Request Processing Report .............................................................................................................. 597
Analysis Summary Report ................................................................................................................. 598
Load Module Summary Report ......................................................................................................... 598
Execution Summary Report .............................................................................................................. 598
Understanding the Execution JCL ........................................................................................................... 599
JCL to Execute the Inventory Analyzer ............................................................................................. 599
How to Override the DDnames ......................................................................................................... 599
How the Program Parameter Works ................................................................................................. 600
Understanding Types and Processor Groups ......................................................................................... 601
How Types and Processor Groups are Named ................................................................................ 601
Processor Group Names ................................................................................................................... 601
Language type (positions 1-3) .................................................................................................. 602
Database environment (position 4) .......................................................................................... 602
Operating environment (position 5) .......................................................................................... 602
Output type (position 6) ............................................................................................................ 603
Processor Names .............................................................................................................................. 603
Processor type (position 1) ...................................................................................................... 603
Language type or utility (positions 2-4) .................................................................................... 604
Database environment (position 5) .......................................................................................... 604
Administrating 21
Operating environment (position 6) .......................................................................................... 604
Output type (position 7) ............................................................................................................ 605
Data Set Names ................................................................................................................................ 605
How the Inventory Analyzer Supports Type and Processor Group Combinations ............................ 607
Types and Processor Groups for NODBMS ...................................................................................... 608
Types and Processor Groups for DB2DBMS .................................................................................... 626
Types and Processor Groups for IDMSDBMS .................................................................................. 645
Types and Processor Groups for IMSDBMS .................................................................................... 663
Types and Processor Groups for TOTALDBM .................................................................................. 681
Types and Processor Groups for Non-3GL Type Items .................................................................... 700
Understanding the User Exit ................................................................................................................... 700
Administrating 22
Reviewing Packages ......................................................................................................................... 720
Executing Packages .......................................................................................................................... 721
Committing Packages ....................................................................................................................... 721
Processing Packages in Batch ................................................................................................................ 722
Specify SCL Data Set Information .................................................................................................... 723
Create a Selection List of Packages ................................................................................................. 724
Build a Package Selection List ................................................................................................. 724
Define or Update a Package .................................................................................................... 725
How to Specify Actions to Perform on Selected Packages ............................................................... 726
Package Actions ...................................................................................................................... 726
How to Specify Additional Package Action Information .................................................................... 728
Approve Package Panel ........................................................................................................... 729
Archive Package Panel ............................................................................................................ 729
Cast Package Panel ................................................................................................................. 730
Create a Package Panel .......................................................................................................... 731
Deny Package Panel ................................................................................................................ 733
Execute Package Panel ........................................................................................................... 734
Export Package Panel .............................................................................................................. 734
Modify an Existing Package Panel ........................................................................................... 735
Package Summary Panel ......................................................................................................... 737
Submit Package Panel ............................................................................................................. 737
Enter Package Note Text Panel ............................................................................................... 738
Display Package Note Text Panel ............................................................................................ 738
Submit SCL for Processing ............................................................................................................... 738
Batch Package Execution Report ..................................................................................................... 738
Statement Summary Report ..................................................................................................... 739
Action Execution Report ........................................................................................................... 739
Action Summary Report ........................................................................................................... 739
Approver Groups ..................................................................................................................................... 739
External Approver Groups and RACF ............................................................................................... 741
External Approver Groups and CA Top Secret ................................................................................. 742
External Approver Groups and CA ACF2 for z/OS ........................................................................... 742
Approver Group Request Panel ........................................................................................................ 743
Display an Approver Group Definition ...................................................................................... 744
Display an Approver Group Selection List ............................................................................... 744
Delete an Approver Group Definition ....................................................................................... 744
Create an Approver Group Definition ....................................................................................... 745
Update an Approver Group Definition ...................................................................................... 745
Approver Group Selection List .......................................................................................................... 745
Display an Approver Group Definition ...................................................................................... 746
Delete an Approver Group Definition ....................................................................................... 746
Update an Approver Group Definition ...................................................................................... 747
Administrating 23
Approver Group Definition Panel ...................................................................................................... 747
Delete an Approver Group Definition ....................................................................................... 748
Create an Approver Group Definition ....................................................................................... 749
Update an Approver Group Definition ...................................................................................... 749
Dynamic Approver Group Panel ....................................................................................................... 750
Approver Group Relation Request Panel .......................................................................................... 751
Display a List of All Approver Group Relationships .................................................................. 752
Display a Relationship Between an Inventory Area and an Approver Group .......................... 752
Delete a Relationship Between an Inventory Area and an Approver Group ............................ 753
Create a Relationship Between an Inventory Area and an Approver Group ........................... 754
Change the Approver Group for an Inventory Area ................................................................. 754
Approver Group Relationship List ..................................................................................................... 755
Display a Relationship Between an Inventory Area and an Approver Group .......................... 755
Delete a Relationship Between an Inventory Area and an Approver Group ............................ 756
Change the Approver Group for an Inventory Area ................................................................. 757
Approver Group Relationship Panel .................................................................................................. 757
Delete a Relationship Between an Inventory Area and an Approver Group ............................ 758
Create a Relationship Between an Inventory Area and an Approver Group ........................... 758
Change the Approver Group for an Inventory Area ................................................................. 759
Locking and Approver Groups .......................................................................................................... 759
Using Promotion Packages ..................................................................................................................... 761
How Promotion Packages are Processed ......................................................................................... 761
How to Ship a Promotion Package Before Map Ends ....................................................................... 763
Stop-at-Stage Feature .............................................................................................................. 763
How the Stop-at-Stage Feature Works .................................................................................... 764
How to Enable the Stop-at-Stage Feature ............................................................................... 764
How to Use the SUPPRESS_AUTOCAST Option ................................................................... 765
Using the CA 7 Interface for Package Execution .................................................................................... 765
How the CA 7 Interface Works .......................................................................................................... 766
How to Implement the CA 7 Interface ............................................................................................... 767
The CA 7 Parameters .............................................................................................................. 767
Verify the CA 7 Information ...................................................................................................... 767
Package SCL and CA 7 .................................................................................................................... 767
Package Display Panel and CA 7 ..................................................................................................... 768
CA 7 Reports ..................................................................................................................................... 768
Package Ship Facility .............................................................................................................................. 768
How to Set Up Package Ship ............................................................................................................ 769
How to Enable Package Ship ................................................................................................... 769
How to Enable Post-Ship Script Execution .............................................................................. 808
How to Enable USS Supported Files for Package Ship ........................................................... 814
How to Enable Backout and Shipment for Natural Objects ...................................................... 820
Host Package Shipment Job Steps .......................................................................................... 828
Administrating 24
How the Remote Copy/Delete Job Steps Work ....................................................................... 835
How to Build, Track, and Confirm Package Shipments .................................................................... 838
Ship One Package to One Destination .................................................................................... 839
Ship One Package to Multiple Destinations ............................................................................. 840
Ship Multiple Packages to One Destination ............................................................................. 840
Package Shipment Panel ......................................................................................................... 841
Package Selection List ............................................................................................................. 841
Destination Selection List ......................................................................................................... 842
Confirm a Package for Shipment (Packages) .......................................................................... 843
Shipment Tracking and Confirmation ....................................................................................... 843
Request Queue ........................................................................................................................ 846
Display Shipment Status .......................................................................................................... 847
Ship Package Syntax ............................................................................................................... 847
How to Manage Package Ship .......................................................................................................... 849
Package Shipment Reports ..................................................................................................... 850
Package Shipment Activity Report ........................................................................................... 850
Package Shipment Assembler Reports ................................................................................... 852
Shipment Confirmation Email Notification ................................................................................ 853
Back Out and Back In Package Outputs ................................................................................................. 853
Why Do a Backout? .......................................................................................................................... 854
Why Backout Does Not Affect Source ..................................................................................... 854
Package Ship and Package Backout Status ............................................................................ 854
Restrictions .............................................................................................................................. 855
Prerequisites ............................................................................................................................ 855
Back Out an Entire Package ............................................................................................................. 856
Back In an Entire Package ................................................................................................................ 856
Back Out a Package Element Action ................................................................................................ 857
Back In a Package Element Action ................................................................................................... 858
View Package Backout Information .................................................................................................. 859
Backout and Backin Execution Logs ................................................................................................. 860
LLACOPY .......................................................................................................................................... 860
Administrating 25
Inventory Structure ............................................................................................................................ 869
Environments ........................................................................................................................... 870
Systems ................................................................................................................................... 870
Subsystems .............................................................................................................................. 871
Types ....................................................................................................................................... 871
Processor Groups ............................................................................................................................. 872
Processor Symbols ........................................................................................................................... 873
Processor Symbols Definition Defaults ............................................................................................. 873
Configuration Tables ......................................................................................................................... 874
Global Type Sequencing ................................................................................................................... 874
Best Practice Implementation Source Files ...................................................................................... 875
Run BPISTART ....................................................................................................................................... 875
Customize the BPI Input Tables .............................................................................................................. 877
Input Table Format Rules .................................................................................................................. 877
T ADMALL--Allocations for Admin Environment ............................................................................... 878
T ADMSUB--SubSystem Names for ADMIN Environment ................................................................ 879
T ADMSYS--System Names for ADMIN Environment ...................................................................... 879
T ADMTYP--Types for the ADMIN Environment ............................................................................... 880
T ALLOC--Allocations for Non-ADMIN Environments ....................................................................... 880
T ENVMTS--Environment and Stage Names .................................................................................... 882
T GLBSEQ--Global Type Sequence Member ................................................................................... 883
T LIBRYS--Allocations for Site-Wide Data Sets ................................................................................ 883
T SUBSYS--Subsystem Names for All Environments Except All Standard or Application Environments
.......................................................................................................................................................... 884
T SYMBLS--Symbol Names for All Environments Except ADMIN and UNCLMED .......................... 884
T SYSTMS--System Names for Standard or Application Environments ........................................... 885
T TYPES--Types for Non-ADMIN Environments .............................................................................. 885
Prepare the BPI Job Card ....................................................................................................................... 885
Define Symbol Values for BPI Jobs ........................................................................................................ 886
Submit BPI Jobs ...................................................................................................................................... 886
Iterative BPI Process ......................................................................................................................... 887
Administrating 26
Delta Level Management ........................................................................................................................ 892
Automated Element Level Versioning ............................................................................................... 893
Element Delta Consolidation Method ................................................................................................ 893
Aged Delta Retention Method ........................................................................................................... 894
Implement Age Level Retention ........................................................................................................ 897
Identify Old Delta Levels ................................................................................................................... 898
Mapping Multiple Environments .............................................................................................................. 898
Selecting a Library Type for Base and Delta Members ........................................................................... 899
Benefits and Drawbacks of Library Types ............................................................................................... 899
Converting from One Library Type to Another .................................................................................. 901
Setting the RECBUFFSIZE Parameter ................................................................................................... 902
Monitoring CA L-Serv Performance ........................................................................................................ 902
Evaluating Buffer Pool Usage ........................................................................................................... 902
Displaying Information About the Communications Server ............................................................... 903
Using z/OS SYSPLEX VSAM Record Level Sharing (RLS) Support for MCFs and Package Data Set . 903
Implementing RLS ................................................................................................................................... 904
Tuning Your Processors .......................................................................................................................... 904
Tuning Your Systems .............................................................................................................................. 905
Virtual Inventory Configuration NoSource Option ................................................................................... 906
How Virtual Inventory Configuration Works ...................................................................................... 907
Administrating 27
Reassemble the C1DEFLTS Table ................................................................................................... 919
Implementation Scenarios ....................................................................................................................... 919
Single CPU Implementation .............................................................................................................. 919
How to Implement a Single CPU .............................................................................................. 920
Multiple CPU Implementation Using Remote Journaling .................................................................. 920
How to Implement a Multiple CPU ........................................................................................... 921
Performance Considerations for a Multiple CPU Implementation Using Remote Journaling .. 922
Multiple CPU Implementation Using Local Journaling ...................................................................... 922
How to Implement Multiple CPU Using Local Journaling ......................................................... 923
Performance Considerations for a Multiple CPU Implementation Using Local Journaling ...... 923
Perform Periodic Backups of CA Endevor® SCM ................................................................................... 923
Perform Point in Time Recovery ............................................................................................................. 924
How to Execute the CA L-Serv LDMAMS Utility ............................................................................... 924
How to Disable Point in Time Recovery Journaling .......................................................................... 925
How to Restore the Data Sets to Be Recovered ............................................................................... 925
How to Execute the Recovery Utility ................................................................................................. 925
Recovery Utility Syntax ............................................................................................................ 925
Recover Examples ................................................................................................................... 926
Journal Recovery Execution Report ........................................................................................................ 927
The Journal Recovery Transaction Detail Report ............................................................................. 927
The Journal Recovery Journal Input Record Summary .................................................................... 928
The Journal Recovery Data Set Activity Summary ........................................................................... 928
The Journal Recovery SCL Statement Summary ............................................................................. 929
Search and Replace Element Text Strings and Component List Output
Data Set Names ...................................................................................... 930
Search and Replace Utility ...................................................................................................................... 930
Searching and Replacing Text Strings .................................................................................................... 930
How the Search and Replace Utility Begins the Search ................................................................... 931
The Search String ............................................................................................................................. 932
Search and Replace Utility Processing Modes ................................................................................. 932
Search and Replace Column Definitions .......................................................................................... 933
Search and Replace Utility Operating Considerations ............................................................................ 933
Miscellaneous Operating Considerations .......................................................................................... 933
Serializing the Element ..................................................................................................................... 934
Exits Invoked by the Search and Replace Utility ............................................................................... 934
Validate Mode ................................................................................................................................... 935
Search-Only Mode ............................................................................................................................ 936
Search-Only Mode Processing ................................................................................................ 936
Generating Search Elements SCL ........................................................................................... 937
Administrating 28
ENSSCLOT File ....................................................................................................................... 937
Replacement Mode ........................................................................................................................... 937
Replacement Mode Processing ............................................................................................... 938
Processing Checkpoints ........................................................................................................... 938
Search and Replace Execution JCL ........................................................................................................ 939
ENSSCLIN DD Statement ................................................................................................................. 939
PARM= Statement ............................................................................................................................ 940
Search Elements SCL ............................................................................................................................. 940
Search Elements Syntax ................................................................................................................... 941
Search Element Clause .................................................................................................................... 942
From Clause ...................................................................................................................................... 942
For Clause ......................................................................................................................................... 943
Where Clauses .................................................................................................................................. 944
Option Clauses .................................................................................................................................. 945
Text Replacement ................................................................................................................................... 947
Compare Column Ranges ................................................................................................................. 947
IN COLUMNS Rules ......................................................................................................................... 948
BOUNDS ARE Rules ........................................................................................................................ 948
Shorter Replacement String .............................................................................................................. 948
Shorter Replacement String Example ............................................................................................... 949
Longer Replacement String .............................................................................................................. 949
Longer Replacement String Examples .............................................................................................. 950
Multiple Occurrences of the Search String ........................................................................................ 951
Search and Replace Utility Reports ........................................................................................................ 951
Search and Replace Control Statement Summary Report ............................................................... 952
Search and Replace Utility Execution Report ................................................................................... 952
Search and Replace Utility Summary Report .................................................................................... 952
Text Search and Replace Usage Scenarios ........................................................................................... 953
Test Elements ................................................................................................................................... 953
HELLO.C Element ............................................................................................................................. 954
HELLO.COB Element ....................................................................................................................... 954
HELLO.TXT Element ........................................................................................................................ 954
Scenario 1 Simple Search in Search-Only Mode .............................................................................. 955
Simple Search SCL .................................................................................................................. 955
Simple Search Output .............................................................................................................. 955
Scenario 2 Simple Search with Replace in Search-Only Mode ........................................................ 956
Simple Search with Replace Mode SCL .................................................................................. 956
Simple Search with Replace Output ........................................................................................ 956
Scenario 3 Search Environment Map, Replace, and Update ............................................................ 957
Search Environment Map SCL ................................................................................................. 957
Search Environment Map Output ............................................................................................. 958
Administrating 29
ELIB Data Sets ........................................................................................ 965
Data Sets ................................................................................................................................................. 965
BC1PNLIB Utility ..................................................................................................................................... 966
Initialize Function .............................................................................................................................. 966
Expand Function ............................................................................................................................... 969
Adjust Function ................................................................................................................................. 970
Reorganize Function ......................................................................................................................... 971
Inquire Function ................................................................................................................................ 971
BC1PNLST Utility .................................................................................................................................... 972
BC1PNCPY Utility ................................................................................................................................... 973
How to Allocate and Initialize an ELIB Data Set ...................................................................................... 975
Select an Access Method for ELIB Data Sets ................................................................................... 976
Estimate Space Requirements for ELIB Data Sets ........................................................................... 976
How to Allocate and Initialize the Data Set ....................................................................................... 976
Allocate and Initialize a BDAM ELIB Data Set ......................................................................... 976
Allocate and Initialize a VSAM ELIB Data Set ......................................................................... 978
Reinitialize an ELIB Data Set ................................................................................................... 979
How to Expand ELIB Data Sets .............................................................................................................. 980
How to Adjust ELIB Data Sets ................................................................................................................. 980
How to Reorganize ELIB Directory Pages .............................................................................................. 981
How to Print ELIB Data Set Information .................................................................................................. 982
How to Print Data Set Header Information ........................................................................................ 982
How to Print Member Information ..................................................................................................... 983
How to Print Target Directory Page Information ...................................................................................... 983
How to Print Data Set Analysis Information ............................................................................................ 984
How to Convert to or from ELIB Format .................................................................................................. 985
Administrating 30
Sample Unload Control Cards .......................................................................................................... 992
Reload Function ...................................................................................................................................... 994
Reload Control Card ......................................................................................................................... 995
Reloading Master Control File Information ........................................................................................ 995
Reloading Element Information ......................................................................................................... 996
Reload and Packages ....................................................................................................................... 997
Locking During Reload Processing ................................................................................................... 997
Example 1. Base/Delta Recovery ..................................................................................................... 997
Example 2 VSAM Master Control File Recovery .............................................................................. 998
Example 3 Package Data Set Recovery ........................................................................................... 999
Sample Reload Control Cards ........................................................................................................ 1000
Validate Function ................................................................................................................................... 1000
Validate Control Card ...................................................................................................................... 1001
Validate Processing ......................................................................................................................... 1001
Sample Validate Control Card ......................................................................................................... 1002
Administrating 31
Retrieve Action CCID Updates ........................................................................................................ 1020
Generate Action CCID Updates ...................................................................................................... 1020
Move Action CCID Updates ............................................................................................................ 1021
Transfer Action CCID Updates ........................................................................................................ 1021
Delete Action CCID Updates ........................................................................................................... 1022
Restore Action CCID Updates ........................................................................................................ 1022
Summary CCID Impact Chart .......................................................................................................... 1023
Administrating 32
BSTPCOMP for Comparing Members or Files ...................................... 1048
How to Control Compare Output ........................................................................................................... 1048
No Overrides Method ...................................................................................................................... 1049
Control Card Execution Method ...................................................................................................... 1049
PARM-Controlled Execution Method ............................................................................................... 1051
Sample Changes Report Output ........................................................................................................... 1053
BSTPCOMP Return Codes ................................................................................................................... 1054
IEBUPDTE Request Card Generator .................................................................................................... 1055
How to Generate Control Cards from a CA Endevor® SCM Element ............................................ 1055
How to Generate Control Cards When Two Members Differ .......................................................... 1056
Administrating 33
Member Name ................................................................................................................................ 1071
Expand Includes SCL ............................................................................................................................ 1071
Expand Includes Syntax .................................................................................................................. 1072
EXPAND INCLUDES Clause .......................................................................................................... 1072
FROM Clause .................................................................................................................................. 1072
TO Clause ....................................................................................................................................... 1073
OPTIONS Clauses .......................................................................................................................... 1074
Expand Includes Utility Reports ............................................................................................................ 1074
Expand Includes Control Statement Summary Report ................................................................... 1074
Expand Includes Execution Report ................................................................................................. 1075
Expand Includes Summary Report ................................................................................................. 1075
Administrating 34
CA Endevor® SCM Load Utility Requests ............................................................................................ 1093
Load Utility Statements ................................................................................................................... 1093
Load Request Syntax ...................................................................................................................... 1093
Load Request Rules ........................................................................................................................ 1094
Load Request Required Clauses ........................................................................................... 1094
Load Request Optional Clauses ............................................................................................ 1095
Set Statements ................................................................................................................................ 1095
SET FROM Statement ........................................................................................................... 1096
SET TO Statement ................................................................................................................. 1096
SET OPTIONS Statement ...................................................................................................... 1097
SET FOOTPRINT Statement ................................................................................................. 1097
Clear Statements ............................................................................................................................ 1098
Load Utility Reports ............................................................................................................................... 1098
Load Execution Log ........................................................................................................................ 1099
Data Validation Report .................................................................................................................... 1099
Load Execution Report .................................................................................................................... 1100
Load Execution Summary ............................................................................................................... 1100
Example of the Load Utility Process ...................................................................................................... 1101
How to Load the Request ................................................................................................................ 1101
How to Execute the JCL .................................................................................................................. 1101
How to Review the Reports ............................................................................................................. 1102
Load Request Numbers ......................................................................................................... 1102
Load Execution Log (DDname = C1BMLLOG) ...................................................................... 1103
Data Validation Report (DDname = C1BMLSYN) .................................................................. 1103
Load Execution Report (DDname = C1BMLDET) .................................................................. 1104
Load Execution Summary (DDname = C1BMLSUM) ............................................................ 1104
Load Utility Footprint Override Exit ........................................................................................................ 1105
Load Utility Footprint Exit Operation ............................................................................................... 1105
LOADDS Load Exit Control Block .......................................................................................... 1106
C1BMLXIT Exit ................................................................................................................................ 1106
Administrating 35
CA Endevor® SCM - 17.0
Administrating
Important! We recommend that you begin using the Administrating content by reading
Roadmap to Administrator Tasks (see page 37). This article describes common tasks with
links to associated content.
04-May-2018 36/1109
CA Endevor® SCM - 17.0
04-May-2018 37/1109
CA Endevor® SCM - 17.0
04-May-2018 38/1109
CA Endevor® SCM - 17.0
04-May-2018 39/1109
CA Endevor® SCM - 17.0
04-May-2018 40/1109
CA Endevor® SCM - 17.0
How to Alter Master Control File Element Metadata (see page 41)
How to Set Up the Alter Action (see page 44)
Review Alter Action Activity (see page 46)
You can use the Alter action to change Element master record information (Element metadata) in the
Master Control File. You specify an Element and what changes you want made to its metadata.
Different metadata fields and multiple Element instances can be changed by the same Alter action.
The Element metadata is changed at the location where the matching elements are found; the Alter
action never fetches the Element.
The Alter action can be executed in Update or Noupdate mode. Noupdate mode produces the same
output messages as Update mode; however the Master Control File Element record is not updated.
Noupdate mode is an analysis tool that lets you see what effect the Update mode would have before
you run it.
The Alter action is an Element action and is processed similarly to other Element actions, for example,
the Add, Delete, Generate actions. However, the Alter action does not execute processors.
Using the Alter action, you can change the following Master Control File Element record metadata
fields:
Generate CCID
CCID for the last Add, Update, Generate, Move, or Transfer action that executed the Generate
processor against the Element.
04-May-2018 41/1109
CA Endevor® SCM - 17.0
Retrieve CCID
CCID for the last Retrieve action that was executed against the Element.
Signout UserID
Current user ID to which the Element is signed out.
Description
Base description for the Element. This value is usually set by the Comment field when the
Element is added.
User Data
An 80-byte field stored with the Element. This value can also be set using a User Exit 2 (before
action) program on an Add, Update, or Generate action.
To change the Master Control File element metadata, code the Alter statement. Submit the Alter
statement for batch processing or include it in a Package. Packages can be submitted in foreground
or batch. The Alter action is not available from the Foreground Options menu. Alter statements can
be submitted from the Batch Options menu, but the SCL Generation menu does not have an option
for the Alter action.
Note: For more information about the SCL syntax for the Alter statement, see Alter
Statement (https://docops.ca.com/display/CE17/Alter+Statement).
When you create or modify a Package, you cannot use the Build Package Actions option on the
Create/Modify Package panel to build the Alter action. The Build Package Actions option does not
support building the Alter action.
Wildcarding or masking of the from location fields (Environment, System, and so on) is not
permitted.
The Alter action Search option is not permitted in a Package and if coded, the Package cast
will fail.
The default settings in the Optional Features table that affect package processing can be adjusted
depending on the preferences of the administrator. For more information about the Optional
Features table, see How to Set Up the Alter Action (see page 44).
04-May-2018 42/1109
CA Endevor® SCM - 17.0
Functional security -- The Alter Action uses CA Endevor SCM security to verify that a user is
authorized to perform the requested actions against the Element. The following security checks
are performed:
Does the user have retrieve authority for the Element at the inventory location at which it is
found? This check is performed before altering an Element.
Does the user have Override Signout authority at the inventory location at which the Element
is found? This check is performed when the Override Signout clause is specified and the
Element is not signed out to the current user.
If using ESI, does the user have Alter authority for the Element at the target Stage and
Environment?
If using Endevor Native Security, does the user have Update authority for the Element at
Stage 1 or the Entry Stage of the target Environment and Move authority for the Element at
Stage 2?
For information on how to setup security, see How to Set Up the Alter Action (see page 44).
Signout UserID -- The Alter Action does not alter Elements that are signed out to users other than
the current user, unless the Override Signout option is specified.
To perform the Alter action when the Element is signed out to someone else, Override
Signout must be used and the corresponding authority granted.
The Alter action retains the current Signout Userid for the Element; it does not update the
Signout UserID with the user ID of the person performing the Alter action. If you want the
Signout Userid Element field to be changed as part of the Alter action, use the Replace
Signout UserID clause.
Element locking -- Serializing the Element applies to Update mode and Noupdate mode. The Alter
action puts a lock on an Element when it is being processed. The following search criteria
determine which Elements get locked:
When the Search option is specified -- At the first Environment where the Element is found in
the logical map when Search First option is used, or at all Environments where the Element is
found in the logical map when the Search All option is used.
04-May-2018 43/1109
CA Endevor® SCM - 17.0
Alter actions are processed in Global Type Sequence order and follow the same Type Sequence
rules as other Element actions.
Concurrent Action Processing supports the Alter action. If Concurrent Action Processing is
enabled and requested, Alter actions are processed concurrently in Global Type Sequence order.
Whenever an Element metadata field is updated, an SMF record is written for the updated field.
The Element metadata field is updated and the SMF record is written, even if the Element
metadata field value is identical before and after the update.
The Alter Action invokes the following CA Endevor SCM User Exits: User Exit 1 (security), User Exit
2 (before action), and User Exit 3 (after action).
A User Exit 2 or User Exit 3 program can query all the Alter fields that are defined in the
assembler $ALTRDS User Exit block or the COBOL ALTER-ACTION-BLOCK of EXITBLKS, but none
of these fields can be modified.
A User Exit 2 program can modify the action CCID, the action Comment, and the Override
Signout (Y/N) options located in the assembler $REQPDS block or REQUEST-INFO-BLOCK of
the COBOL Exit block EXITBLKS.
The signout check is performed on the Element at the target location after the User Exit 2 call,
but before matching and Alter action processing are performed.
The Signout Userid and User Data Exit Request block fields cannot be modified for the Alter
action.
The SMF record is not passed to the User Exit 3 program for the Alter action.
The Alter action exit control block contains information associated with the Alter action. This
block is pointed to by the primary information exit control block. This block is only available at
the time of User Exit 2 and User Exit 3 calls for the Alter action.
04-May-2018 44/1109
CA Endevor® SCM - 17.0
Review Alter action security -- The CA Endevor SCM administrator works with the site security
administrator to enable certain user IDs to perform the Alter action.
The CA Endevor SCM administrator reviews the BC1TNEQU table to determine if the delivered
setting is appropriate for their site. Permission to process the Alter action is determined by
the security authorization function (SAF) set in the Endevor Security Interface (ESI) BC1TNEQU
table. The following entry for the Alter action is included in the BC1TNEQU sample that is
included with the Version 17.0 release: FUNCEQU SAFAUTH=ALTER,C1ACTNS=(ALTER). As
delivered, the SAF authorization value of Alter is equated with the Alter access level
(c1access). This entry restricts access to the Alter action to users who have ALTER authority
for the ESI pseudo data set name.
Important: If you already have a BC1TNEQU table in place, you must add a statement
for the Alter action to control its use; otherwise, anyone can execute the Alter action.
The site security administrator ensures that the appropriate user IDs are associated to the
Alter access level.
Note: For more information about security, see Securing (see page 41).
Enable Global Type Sequencing -- Global Type Sequencing may already be enabled at your site,
because it is a prerequisite for other functions. Global Type Sequencing determines the order in
which Types are processed in batch.
For Global Type Sequencing to be in effect, both the Parmlib data set and the Type Sequence
member must be defined to the Defaults table C1DEFLTS.
Note: For more information about Global Type Sequencing, see How to Enable Global
Type Sequencing.
04-May-2018 45/1109
CA Endevor® SCM - 17.0
Enable the SMF option -- The SMF option may already be enabled at your site, because it is a
prerequisite for other functions. The SMF option can record each action and each security
violation that occurs during CA Endevor SCM processing and is set per Environment.
For the SMF option to be in effect, the Defaults table (C1DEFLTS) must include the following
parameters:
The SMFREC# parameter must be set in the TYPE=MAIN portion of the Defaults table.
SMFREC# sets the SMF record number that is assigned to SMF records written by CA Endevor
SCM at this site.
The parameter SMFACT=Y must be set in the TYPE=ENVIRONMENT portion of the Defaults
table to write out SMF action records.
If you want to track security violations for your own auditing purposes, make sure that SMFSEC=Y
is set in the TYPE=ENVIRONMENT portion of the Defaults table to write out SMF security records.
Note: For more information about the SMF option, see SMF Recording (see page 1031).
(Optional) Configure Package Processing Options -- The Optional Features table includes the
following options that affect package processing. Depending on how you want the Alter action to
be used, adjust the default settings as appropriate:
Limit processing to one action in the same package -- (Optional) You can limit package
processing to one action against the same Element instance within the same package. This
option disallows additional actions that modify the same Element instance within the same
package. This restriction applies to any action, not only to Alter actions. The following
message is delivered with the severity level of C (for caution with a return code of 8):
C1G0507C ELEMENT IS REFERENCED BY MULTIPLE ACTIONS WITHIN THIS PACKAGE
To disallow more actions, set the severity level for this message to E (for error with a return
code of 12) using this parameter in update the Optional features table, ENCOPTBL:
ENHOPT MSGSEVERITY_C1G0507=C W/C/E O002833
Allow nonpackage actions -- (Optional) If you want to use the Alter action outside of a
package against an Element in an inventory location that usually requires a package, add the
Alter action to this option:
ALLOW_NON_PKG_ACTIONS -- Specifies actions that can be performed outside of a package,
even if the inventory location would usually require a package.
Allow packages containing Alter actions only to skip approval process -- (Optional) If you
want to use the Alter action in a package, but want to skip the package approval process, add
the Alter action to this option:
PKG_ACTIONS_NO_APPRVR -- Specifies actions in a package that do not require approval.
04-May-2018 46/1109
CA Endevor® SCM - 17.0
Review the Alter action messages and return codes (see page 47).
View the Element master panels (see page 49) for the following information:
Current metadata values for the Element, which may have been changed by Alter actions,
including the User Data field.
Metadata about Alter actions that were performed against the Element.
Print the Element master to view the current metadata, which may have been changed by Alter
actions. Currently, printing the Element master does not print the User Data field or the metadata
about the Alter actions that were performed against the Element. For more information about
how to print, see Print Element Information (https://docops.ca.com/display/CE17
/Printing+Element+Information+Using+the+Print+Elements+Action).
Review the Alter action metadata fields returned by the List Element function. You can use the
following options to access this data:
An API program. For more Information about the Alter action metadata response structure
fields for the API function List Element, see Information about Alter Action Metadata in Using
API Function Calls (https://docops.ca.com/display/CE17/API+Function+Calls).
The Comma Separated utility. For more information about the Alter action metadata fields
extracted by the List Element option of the Comma-Separated utility, see Alter Action
Metadata, in Comma-Separated Value (CSV) Utility (https://docops.ca.com/display/CE17
/CSV+Reporting+Utility).
By default the Action Execution report and the Action Summary report are written to the C1MSGS1
DD statement. If your batch execution JCL is coded with the C1MSGS1 and C1MSGS2 DD statements
the Action Execution Report is written to the C1MSGS1 file and the Execution Summary report is
written to the C1MSGS2 file. The execution report can be viewed online by browsing data sets userid.
C1TEMPR1.MSGS or userid.C1TEMPR2.MSGS.
Various messages are issued during Alter action processing, including the following:
If the from-value is omitted or fully wildcarded, the mask-value in message C1G0076I is set to an
asterisk:
C1G0076I MASK: FIELD-NAME MASK-VALUE
04-May-2018 47/1109
CA Endevor® SCM - 17.0
The Alter action changes the Master Control File for each matching Element at the location where
the Element resides. No copyback logic occurs. Message C1G0280I prints the location where the
Element was located and updated:
C1G0280I ELEMENT AT LOCATION environment/stage id/system name/subsystem name/type
name SELECTED FOR PROCESSING
C1MSGS2 Summary Report -- Return codes indicate whether all, some, or no fields matched the
mask. *NOUPDT* denotes Noupdate mode in which no updates were performed.
Return codes are associated with certain conditions. In the following descriptions of the return codes,
the Replace clause matches when the Alter action statement specifies a value for the Master Control
File field you want to replace and the specified value matches what is currently in the Master Control
File field.
Note: When Noupdate is active, report messages and return codes simulate what would
happen in Update mode.
RC=0
Indicates that the Alter request completed 100% successfully. All requested Master Control File
fields are (or will be) updated as specified by the submitted Alter action syntax. RC=0 is returned
in the following cases:
All Replace clauses match and Update option is specified, therefore the Master Control File
record is updated.
All Replace clauses match but Noupdate option is specified, therefore the Master Control File
record is not updated.
No from-value is provided and Update option is specified. The Master Control File record is
updated.
No from-value is provided and Noupdate option is specified. The Master Control File record is
not updated.
RC=4
Indicates that the Alter request only partially completed. One or more of the request fields in the
SCL are not (or will not be) updated. RC=4 helps you to determine that some Master Control File
fields were updated successfully, but not all, without having to read all report messages. RC=4 is
returned in the following cases:
Some Replace clauses match and Update option is specified, therefore only the matched
Master Control File fields are updated, while the non-matched fields are bypassed.
Some Replace clauses match but Noupdate option is specified, therefore the Master Control
File record is not updated.
No Elements found.
04-May-2018 48/1109
CA Endevor® SCM - 17.0
RC=8
Indicates that no from-values matched the current Master Control File fields for any of the
replace clauses specified. RC=8 lets you quickly determine which Elements were not updated at
all; identify possible error conditions or an invalid SCL request. RC=8 is returned in the following
cases:
No Replace clauses match and Update option is specified, therefore the Master Control File
record is not updated.
No Replace clauses match and Noupdate option is specified, therefore the Master Control File
record is not updated.
RC=12
Indicates invalid syntax or specification.
04-May-2018 49/1109
CA Endevor® SCM - 17.0
Information about Alter actions that were performed against the Element (Alter action
metadata)
The Alter Action section of the Element record in the Master Control File provides information
about the Alter actions that were run against the Element. This metadata concerns the Alter
action itself, for example the last date and time that the Alter action was run against the Element.
You can see this Alter action metadata displayed on the last panel of the Element Master panel in
the Alter Action section.
Navigate to the end of the last Element Master panel to find the Alter Action section. Review the
following fields in the Alter Action section to see information about the Alter actions that were
run against this Element:
First Date/Time
Indicates the date and time that the first Alter action was performed against this copy of the
Element.
Last Date/Time
Indicates the date and time that the last Alter action was performed against this copy of the
Element. If the First Date/Time matches the Last Date/Time, then the Alter action was only
run once.
Last UserID
Indicates the user ID associated with the last Alter action performed against this copy of the
Element.
Note: The Last Element Action section on the Element Master panels is not changed by the
Alter action, or by Signin or Retreive.
Certain Element actions clear the Alter action metadata fields. For more information, see
Element Actions that Clear Alter Action Metadata (see page 51) and Element Actions that
Retain Alter Action Metadata (see page 51).
04-May-2018 50/1109
CA Endevor® SCM - 17.0
Add or Update that causes a fetch to the target location -- For example: Suppose you add an
existing Element from a production Environment to a target location lower in the map. And
suppose that the existing Element had been altered and had Alter metadata before it was fetched
back to the target. Then the Element that was added at the target location, does not include the
Alter action metadata.
If you Generate Element Y at Stage 2 with Copyback to Stage 1, then the Alter metadata gets
cleared at Stage 1.
If you Generate Element Y at Stage 2 with Nosource to Stage 1, then the Alter metadata gets
cleared at Stage 1.
If your site uses the CA Endevor SCM Quick Edit option, when Edit is used to fetch an element
back to a lower stage.
Move -- For example: If you Move Element Y from Stage 2 with or without history, to the next
location in the map, then the Alter metadata is retained at the target location. If the Bypass
Element Delete option is coded on the Move action, the Alter metadata is retained at the source
location.
Transfer -- For example: If you Transfer Element Y from Stage 2 to an archive file, then Transfer it
back from the archive file, the Alter metadata is retained at the target location. This is true even if
the target location is a different location than where it was archived from.
Restore
Generate in place
Update in place -- For example: If you Update Element Y that resides at Stage 1, then the Alter
metadata is retained at Stage 1.
Archive
Copy
Signin
04-May-2018 51/1109
CA Endevor® SCM - 17.0
SMF Recording
You can audit Alter action activity by reviewing SMF records. SMF recording, which can record
security violations and action activity, must be active to enable the Alter action.
Security records can show if a user attempted to perform an Alter action for which they do not
have permission. For example, suppose someone attempted to alter an element at an
Environment they did not have access to, an error would be produced. The security record would
log who attempted to perform the failed action.
Activity records show if the Alter action was performed and what effect the action had on the
Element record in the Master Control File.
CONRPT40 -- Security Violation Summary. For each system requested, this report gives a detailed
account of each security violation that occurred. Specifically, this report lists each attempt -- by any
user -- to perform an unauthorized action. Attempts to perform unauthorized Alter actions are
recorded.
CONRPT42 -- Element Activity Profile. This report details each action performed against the Elements
within a particular system, subsystem, Element type, and stage. Using this report, you can determine
exactly which Elements were changed using the Alter action. Also, shown are the Replace clause
specified on the Alter action and the Master Control File Element record value before and after it was
replaced and the mask value that was specified on the Alter action. If the Replace User Data clause
was specified, the additional parameters are shown.
Note: For more information about Alter action fields for the List SMF function, see
ALSMFA_RS Response Structure Fields for Activity Requests (see page 41).
04-May-2018 52/1109
CA Endevor® SCM - 17.0
As a software developer, you can automatically generate elements that use a component. Such
elements are known as using elements. For example, if you have a component element copybook
COPYA, then the programs that use that copybook are using elements. To automatically generate
using elements, you specify the Autogen action option on the Add, Update, or Generate action that
acts on the component element. This option is available in batch only and cannot be used in
packages.
2. Code an Autogen or an Autogen Span action option in a batch processing request (see page
59).
04-May-2018 53/1109
CA Endevor® SCM - 17.0
3. (Optional) Run the Autogen batch job in simulation mode for impact analysis (see page 60).
Note: Although the Autogen action option can only be used in batch, component elements
can be generated in foreground or batch as follows:
Review Prerequisites
Before using the Autogen action option, complete the following prerequisites:
Verify that the CA Endevor SCM Automated Configuration option has been purchased and
enabled for your site. You can use the Display Site panel to determine if this option is activated
(ASCM=Y) at your site.
Verify that Global Type Sequencing is enabled. This processing option causes the batch processing
of element actions to occur in a Type sequence defined at the site level. Autogen requires Global
Type Sequencing so that the elements that use a component are generated after all of the
components have been processed (for example, macros before source, source before load
modules). For more information about enabling Global Type Sequencing, see How to Enable
Global Type Sequencing.
Verify the AUTOGEN_SOURCE setting in the Optional Features table. When AUTOGEN_SOURCE is
not turned on, Generate actions for using elements are built with the NoSource option. This is the
default.
Note: An administrator can change the behavior of the Autogen feature, by activating
AUTOGEN_SOURCE in the Optional Features Table (ENCOPTBL). When this option is
activated, the Generate actions for the using Elements are built with the Copyback,
instead of the NoSource, option.
How to code SCL statements. For more information, see SCL Reference (https://docops.ca.com
/display/CE17/SCL+Reference).
04-May-2018 54/1109
CA Endevor® SCM - 17.0
Make sure that you understand how Autogen works. Autogen generates only those using
elements that are in the same logical map as the target component. Certain Autogen Span
options also generate using elements that are found in different Systems and Subsystems within
the Environment and Stage of the logical map. The following topics explain the different Autogen
options and how they affect processing:
How the Autogen Action Option Affects Processing (see page 56)
Autogen is available in batch only for the Add, Update, and Generate actions and cannot be used in
packages. CCIDs and comments from the original generated element are used. Autogen generates
only those using elements that are found at the same inventory location as the target component or
are found higher up the logical map. To generate using elements that are located across Systems or
Subsystems, you can use the Autogen Span options. For more information about the Span options,
see Autogen Spans Across Systems and Subsystems (see page 58).
If you specify the Autogen option on any one of a group of statements, then all of those statements
are resolved based on the current inventory contents before any statement is executed. Statements
such as GENERATE ELEMENT * create actions based on the location and options of the Generate
action. During processing, duplicate Generate actions are eliminated, and the NoSource option is
enabled for all the Generate actions that are built by Autogen.
Note: An administrator can change the behavior of the Autogen feature, by activating
AUTOGEN_SOURCE in the Optional Features Table (ENCOPTBL). When this option is
activated, the Generate actions for the using Elements are built with the Copyback, instead
of the NoSource, option.
Autogen improves processing by eliminating duplicate processing of components and reduces the
work that is required of users, who no longer must use the Automated Configuration Manager Query
facility (ACMQ) to create additional Generate actions for element components and then run another
batch job to process them.
You can run Autogen in simulation mode, to preview the effects of an Autogen request.
04-May-2018 55/1109
CA Endevor® SCM - 17.0
Autogen requires Global Type Sequencing so that the elements that use a component are
generated after all of the components have been processed (for example, macros before source,
source before load modules).
Autogen only acts on components whose Types are listed in the Global Type Sequencing table. If
the component's Type is not listed in the Global Type Sequencing table, the Autogen request is
ignored.
Your site must have purchased and activated the option CA Endevor SCM Automated
Configuration. You can use the Display Site panel to determine if this option is activated (ASCM=Y)
at your site.
Autogen cannot be specified on actions that are included in a package, because approvers must
see the SCL statements that they are approving.
Autogen and the bypass generate element (GENERATE ELEMENT=N) options are mutually
exclusive.
1. An ACMQ search is performed for all elements that use the component element being
generated.
04-May-2018 56/1109
CA Endevor® SCM - 17.0
2. For each using element, a Generate action is created and added to the list of actions to be
performed. However, duplicate Generate actions are eliminated, so that each using element
will only be generated once, even if multiple components are being generated that are used
by use the same element.
The Generate action created for each using element will perform as follows:
Generate the using element in the same inventory location as the component.
Use the same CCID and COMMENT specified in the original statement.
Accordingly, the using elements are generated as if the following Generate statement had
been specified:
GENERATE ELEMENT name
FROM <inventory location in the original command>
TYPE type
OPTION CCID <same ccid>
COMMENT <same comment>
<override signout, if specified on original command>
NOSOURCE.
If the Copyback option is specified on the original action, then the Copyback only applies to
the component element that is specified on the original request. The NoSource option is
always used on all the Generate statements built for the using elements, unless the
administrator has activated the AUTOGEN_SOURCE option in ENCOPTBL.
3. Autogen only acts on components whose Types are listed in the Global Type Sequencing
table. If the component's Type is not listed in the Global Type Sequencing table, the Autogen
request is ignored.
4. Global type sequencing is used to determine the order in which the elements are generated.
However, with the Autogen option, SCL requests are fully resolved based on current inventory
contents prior to any action being processed. When multiple actions are specified and the
Autogen option is specified on at least one of the actions, all the actions are expanded before
any of the actions are processed. All name masking is resolved and individual actions are built
and then the expanded actions are executed according to the Global type sequence order.
Consequently, if the Generate Autogen option is specified and several Move actions are
included in the same request, the Move actions do not include any of the additional elements
that are copied back as a result of the Generate action.
Example: Autogen Processing when Move actions are included on the same request
04-May-2018 57/1109
CA Endevor® SCM - 17.0
In this example, Macro MD1 exists at the DEV stage 1 location. This macro is used in program PD1
located at the DEV stage 1 location and in programs PQ2 and PQ3 located at the QA stage 2 location.
The following two actions are included in the same batch job:
SET FROM ENV DEV SYS SYS1 SUBS SUB1 STAGE NUM 1.
GENERATE ELE MD1 OPTION AUTOGEN.
MOVE ELE *.
The Generate action results in elements MD1, PD1, PQ2, and PQ3 being generated at the DEV stage 1
location. However, the Move action results in only the MD1 and PD1 elements being moved to the
next location in the logical map. This is because PQ2 and PQ3 were originally not at the STG1
location, so they remain at the DEV stage 1 environment.
For all Autogen and Autogen Span results, any generated elements that are not currently at the
target location are brought back as sourceless elements. However, an administrator can change the
behavior of the Autogen feature, by activating AUTOGEN_SOURCE in the Optional Features Table
(ENCOPTBL). When this option is activated, the Generate actions for the using elements are built with
the Copyback, instead of the NoSource, option.
Also for all Autogen and Autogen Span results, using elements are not generated if they are located in
unmapped Environments or they are located lower in the map than the target location of the
component.
You can run any of the Autogen Span options in simulation mode, to preview the effects of an
Autogen request.
Autogen or Autogen Span None: Generates only those using elements that are in the same logical
map of the component specified. Whether you specify "Autogen" or "Autogen Span None", the
SCL is written as "Autogen Span None".
Autogen Span All: Generates using elements from all Systems and Subsystems.
Autogen Span Systems: Generates using elements from all Systems with the same-named
Subsystem of the component specified.
Autogen Span Subsystems: Generates using elements from all Subsystems with the same-named
System of the component specified.
04-May-2018 58/1109
CA Endevor® SCM - 17.0
Common libraries must be included in the generate processor concatenations of the Systems and
Subsystems of the using elements. If the libraries are not included, then the Generate action does
include the changes made to the component element when searching across Systems or
Subsystems.
The same Systems and Subsystems must exist in each Environment and Stage location. For
example, if ELEMENTA is a using element in the PROD Environment, system A, then system A
must exist in the DEV Environment also.
SPAN only includes using elements from Systems or Subsystems located in the target
Environment and higher up the map.
SPAN does not include using elements from outside the Environment map.
2. Complete the fields as appropriate for your task. Select option 1, BUILD SCL and press Enter.
The SCL Generate panel opens. This panel allows you to select the type of action request you
want to generate,
3. Specify the option number that corresponds to the action (Add/Update or Generate) that you
want to perform and then press Enter.
After you press Enter, the action panel opens that corresponds to the action option you
selected.
4. Code the Add, Update, or Generate action to include one of the following Autogen action
options and verify that Bypass Generate Processor option is not set.
AUTOGEN
Generates all elements that use the component that is the target of the action. These using elements
are generated at the target location that is specified in the SCL statement. If they do not exist at the
target location, they are brought back to the target location as sourceless or sourced elements,
depending on the Optional Features table (ENCOPTBL) setting. To find out how the SOURCE_OPTION
parameter is set in ENCOPTBL, contact your CA Endevor® SCM administrator. If you specify AUTOGEN
or AUTOGEN SPAN NONE in CA Endevor SCM Quick Edit or from the Foreground Batch panel, the SCL
is written as “AUTOGEN SPAN NONE”.
Generates all elements that use the component being acted upon. This option has the exact same
effect as the option "AUTOGEN."
04-May-2018 59/1109
CA Endevor® SCM - 17.0
Generates using elements that are found in any System and Subsystem combinations within the
Environment and Stage of the component's logical map.
Generates using elements that are found in any System, provided the element's Subsystem name
matches the name of the Subsystem of the target component. Only Systems found within the
Environment and Stage of the component's logical map or higher up the map are searched. This
option is different from the Autogen option in that it includes additional Systems with the same
Subsystem name in the search.
Generates using elements from all Subsystems with the same-named System of the component
specified. Only Subsystem found in the System of the target component within the Environment and
Stage of the component's logical map or higher up the map are searched. This option is different
from the Autogen option in that it includes additional Subsystems with the same System in the
search.
Your SCL statement for the Add/Update or Generate request include the Autogen option of your
choice.
Note: Autogen, or any of the Autogen Span action options, can be specified in a Set
Options statement. The Set Options statement tells CA Endevor® SCM to apply one or a
series of options to all subsequent actions, until the next Set Options statement or a Clear
Options statement is encountered, or processing ends. If you enter an option in the
element action statement and have coded that option in the Set Options statement, the
entry in the action statement overrides the Set Options selection.
1. Append the EN$AUSIM DD statement to your batch job that includes Autogen options. For
Foreground Batch requests (or CA Endevor Quick Edit requests) use the Include Additional JCL
option to add the DD statement. An example of the DD statement is shown next:
//EN$AUSIM DD SYSOUT=*
04-May-2018 60/1109
CA Endevor® SCM - 17.0
3. Review the reports for impact analysis to see what the results would be if the actions were
performed.
In all the examples, System SYSTEMC Subsystem SUB1 and SUBC contain elements that are used in
compiling programs in the Application systems, SYSTEM1, SYSTEM2, and SYSTEM3. The graphics
show the component element COPYC1 highlighted along with the using programs PGMC1 and
PGMC2.
DEV maps to QAS, and QAS maps to PRD. The EMER environment maps to PRD. ADMIN is separate,
and holds the processors that all of the other environments use.
The Common SYSTEMC libraries are concatenated in every Generate processor for every
application System in every Environment.
Consequently, all changes made in DEV in the common Systems are automatically picked up by
the application Systems at every Stage, before a package or promotion to PRD has been
performed.
For these use cases, COPYC1 is a component of all PGMC, PGMC1, and PGMC2 programs
Each use case assumes that the elements and locations are as shown in the original chart. Use
cases are not affected by prior use cases.
04-May-2018 61/1109
CA Endevor® SCM - 17.0
No other using programs outside the logical map of the component are affected.
Now the developer can complete his testing, and create a package with Move actions that includes all
the effected elements.
After a Generate with Autogen -- The following graphic shows results after a Generate with Autogen
or Autogen Span None request is performed on COPYC1 at the target location Environment ‘DEV’,
Stage 1, System ‘SYSTEMC’, Subsystem ‘SUB1’.
04-May-2018 62/1109
CA Endevor® SCM - 17.0
04-May-2018 63/1109
CA Endevor® SCM - 17.0
Element PGMC, located outside the map at PRD/SYSTEM2/SUBA/2 is bypassed because Autogen
Span attempts to build the generate request with PGMC’s system and subsystem at the target
environment, but DEV/SYSTEM2/SUBA/1 does not exist.
Element PGMC, located outside the map at EMER/SYSTEM2/SUB1/2 is unaffected, since EMER is
not in the environment map of component, COPYC1.
Now the developer can complete his testing, and create a package with Move actions that includes all
the effected elements.
04-May-2018 64/1109
CA Endevor® SCM - 17.0
COMMENT 'EDIT COMMON COPY BOOKS'
COPYBACK
AUTOGEN SPAN SYSTEMS .
Element PGMC, located outside the map at EMER/SYSTEM2/SUB1/2 is unaffected, since EMER is
not in the environment map of component, COPYC1.
No other Subsystems except Subsystem SUB1 are affected with an Autogen Span Systems request
and thus, using elements in Subsystems SUBA, SUBC, and SUB2 are not generated.
Now the developer can complete his testing, and create a package with Move actions that includes all
the effected elements.
04-May-2018 65/1109
CA Endevor® SCM - 17.0
No other Systems are affected with an Autogen Span Subsystems request and thus, using
elements in Systems SYSTEM1, SYSTEM2, and SYSTEM3 are not generated.
Now the developer can complete his testing, and create a package with Move actions that includes all
the effected elements.
04-May-2018 66/1109
CA Endevor® SCM - 17.0
04-May-2018 67/1109
CA Endevor® SCM - 17.0
Automated Configuration
Contents
CA Endevor SCM Automated Configuration (ACM) works with CA Endevor® SCM Change Manager (CA
Endevor® SCM) to enable you to manage, through advanced automated technology, the
interrelationships between software components.
The CA Endevor® SCM system has been installed in accordance with the instructions provided in
Installing (https://docops.ca.com/display/CE17/Installing).
When a program is translated (for example, compiled, link-edited) from source to executable, all of
the components which make up that program are extracted by language translators and/or linkage
editors from their resident libraries, such as copylibs or maclibs. The major challenge is ensuring that
the relationship between a program and its related components is accurate and up-to-date, at any
given point in time. This synchronization is typically accomplished by retranslating a program each
time one of its subordinate components is changed. A problem arises, however, when a component
is changed but that modification is not propagated to all affected programs.
The lack of automated, reliable methods for coordinating program-component relationships has
created major obstacles to software development and maintenance. Manual definition of program-
component relationships is error-prone and time-consuming by today’s standards. In addition,
manual methodologies do not yield the level of component detail (version/ level/ location) needed to
accurately plan and stage application development activities.
Traditional approaches to software configuration management have been severely limited in their
ability to produce accurate and reliable results. Source scanning techniques, while an improvement
over manual definition, provide only a static "picture" of the program-component relationship. This
picture may not relate to the actual state of the software at the time of program translation. Source
scanning is a separate operation that is run independently of the compile process and, as such, is only
04-May-2018 68/1109
CA Endevor® SCM - 17.0
scanning is a separate operation that is run independently of the compile process and, as such, is only
accurate at the time of the scan. Furthermore, scanning neither stores historical information nor
provides the level of detail that is needed to analyze and perform configuration management
functions.
Building on advanced monitoring and data storage technology, ACM overcomes the shortcomings
inherent in traditional approaches to change control and configuration management. ACM monitors
the libraries that house program components and automatically captures related components during
the translation process. ACM then stores this information using expert base/delta technology to help
in determining changes to components from one translation to the next. Unlike source scanning,
ACM works as an integral part of the translation procedure to track program components
automatically over time.
The following shows how ACM works to automatically track program components over time.
As previously shown, when activated, ACM forms an "envelope" around the translation process (for
example, compiler or linkage editor). When the program or module is executed under an CA
Endevor® SCM processor, ACM tracks all requested change activity and application program-
component relationships. Module interrelationships are automatically captured as part of the
translation procedure. Optionally, this information can also be automatically stored in Root and Cross-
reference data sets for "where-used" analysis.
04-May-2018 69/1109
CA Endevor® SCM - 17.0
ACM Facilities
The following facilities are supplied with CA Endevor® SCM ACM:
Component Monitor
Component List
Component Monitor
The ACM Component Monitor is invoked by adding a special "MONITOR=COMPONENTS" keyword to
DD statements in a CA Endevor® SCM processor. Monitoring is performed on a data set basis. Once
initiated, components that are used from the specified data sets are automatically tracked by ACM’s
Component Monitor.
The processor keyword MONITOR cannot be specified on DD statements that refer to HFS path and
file names.
Component List
The CA Endevor® SCM ACM Component List provides a detailed "snapshot" of all the components
from monitored data sets at the time of program translation. The Component List provides five types
of information: element, processor, symbol, input, and output.
The processor information describes the CA Endevor® SCM processor that is used to generate or
move the element.
The symbol information identifies the user-defined symbolics that are used in the CA Endevor®
SCM processor, and their values.
The input components identify (by step, DDname, dsname, and volume) the component items
that are referenced and any footprints that existed in a monitored data set.
The output components identify (by step, DDname, dsname, and volume) the members that were
created during processor execution.
The first time ACM monitoring is enabled for an element, a "base" component list is stored. This
component list contains all of the aforementioned element, processor, input, and output
information. Subsequent generations produce new component lists which ACM internally compares
to produce "delta levels." (A new delta level is stored only when one or more items change in the
04-May-2018 70/1109
CA Endevor® SCM - 17.0
to produce "delta levels." (A new delta level is stored only when one or more items change in the
component list.) This base/delta architecture makes it possible to compare component list changes
from compile to compile. With this information, you can quickly determine what has changed
because the last compile, and greatly reduce debug time.
Component List Level Numbers— The level numbers that are assigned to a component list
(component levels) are independent of the level numbers that are assigned to an element (element
levels). Because an element may be recompiled many times due to copy or macro changes, there
may be more component levels than element levels. In addition, monitoring may be initiated at any
time and at any element level. For example, an element at level 77 has a component list at level 0
when it is first enabled for monitoring by ACM.
Note: For more information about the ACM Query Facility, see ACM Query Facility (see
page 93).
04-May-2018 71/1109
CA Endevor® SCM - 17.0
Data collection
Data storage
The following figure illustrates how the different areas work within ACM.
In these areas, you can see how data definition and collection starts in the ACM Component Monitor,
data storage continues in the ACM Component List, software configuration analysis and management
flows to the Root and Cross Reference Data Sets, and finally to the ACM Query Facility.
Data Collection
Data Collection begins when you invoke ACM through the MONITOR=COMPONENTS parameter in an
CA Endevor® SCM processor. With this parameter, you specify the libraries and data sets that are to
be monitored automatically by ACM. Then, the Component Monitor tracks all change activity and
program-component relationships for the data sets you earmarked for monitoring.
The processor keyword MONITOR cannot be specified on DD statements that refer to HFS path and
file names.
Data Storage
ACM produces a component list during program translation (compilation), thus beginning the data
storage process. The component list is an internal data structure which assembles all program-
component information, with an audit stamp or "footprint" for each component, at the time of each
compile. Component list "levels" (differences in component lists from one translation to the next) are
stored in CA Endevor® SCM base/delta format. The component list provides a "snapshot" of a
04-May-2018 72/1109
CA Endevor® SCM - 17.0
stored in CA Endevor® SCM base/delta format. The component list provides a "snapshot" of a
program at compilation -- identifying an element components, where they originated, their version
and level, and the output that is created as the result of the translation.
Example
The following figure illustrates how ACM stores and remembers the components that are used to
create the outputs for a particular generate date and time, version, and level of a typical COBOL
program -- PROGRAM X -- as transformed by the CA Endevor® SCM processor COMPLINK.
The ACM Component Monitor has captured all the components of PROGRAM X, with the CA
Endevor® SCM footprint information associated with those components. The resulting component list
provides an integrated view of all configuration information relating to PROGRAM X at the time of
the translation.
04-May-2018 73/1109
CA Endevor® SCM - 17.0
Using ACM
CA Endevor SCM ACM functions can be separated into the following categories:
Enable ACM
Manual setup function performed by CA Endevor SCM administrators.
04-May-2018 74/1109
CA Endevor® SCM - 17.0
C1DEFLTS TYPE=MAIN, X
...
...
PROC=Y,
To ensure that you have enabled ACM, select option 1 (DISPLAY) on the Primary Options menu and
press Enter. Select option 3 (SITE) and press Enter. On the Site Information panels, check the ASCM
and PROC OPTIONS. If ACM iand processors are correctly enabled, a Y displays in these fields.
1. Update the C1DEFLTS Table with the ACM Root and Cross-reference data sets.
C1DEFLTS TYPE=MAIN,
...
04-May-2018 75/1109
2.
To ensure that you have enabled ACM, select option 1 (DISPLAY) on the Primary Options
menu and press Enter. CA Endevor SCM displays the Display Options Menu. Check the ASCM
field under OPTIONS. If ACM is enabled, you will see a Y in this field. The panel displays the
Root and Cross-reference data set names. If you are implementing CA Endevor SCM for the
first time, you must estimate the number of elements to add to CA Endevor SCM, and then
calculate space requirements
The Root data set contains the names of each CA Endevor SCM element and all related
components.
The Cross-reference data set contains a record for each component relationship.
1. Execute the SYSTEM INVENTORY SUMMARY REPORT (CONRPT02) to get an overall count of
CA Endevor SCM elements. Increase this value by 50 percent (that is, if the report determines
that there are 4000 elements, the estimated total elements should be increased to 6000 to
include related components which are not CA Endevor SCM elements).
You must have already assembled the C1DEFLTS Table with the ACM Root and Cross-
reference data sets prior to the execution of this JCL.
2. A 3390 cylinder can hold approximately 6000 components. Using the value obtained above,
allocate enough cylinders to accommodate your current inventory and future expansion. This
value represents the primary and secondary allocation of the Root file.
3. Multiply the composite element total from the first step by 10 to estimate the total number of
relationships to be added in the XREF file (i.e., 6000 * 10 = 60,000 estimated relationships).
4. A 3390 cylinder can hold approximately 120,000 relationships. Using the value obtained in the
previous step, allocate enough cylinders to accommodate your current inventory and future
expansion. This value represents the primary and secondary allocation of the XREF file.
1. Use member BC1JACMD, located in iprfx.iqual.CSIQJCL, to create the Root and Cross-
reference data sets.
2. Edit member BC1JACMD to add the space requirement information that you previously
calculated.
04-May-2018 76/1109
CA Endevor® SCM - 17.0
3.
iprfx
Highest-level qualifier used when assigning data set names for installation and execution
data sets.
iqual
Second-level qualifier used when assigning data set names for installation and execution
data sets.
vvolser
Volume serial number of the disk on which the MCF and package data sets will be
allocated.
4. Follow the instructions in BC1JACMD to further tailor the JCL. After you have tailored the JCL,
make sure you have a valid JOBCARD, and submit the JOB to create and initialize the Root and
Cross-reference data sets.
2. Edit member BC1JACML to make the above modifications. Follow the instructions in
BC1JACML to further tailor the JCL and SCL. After you have tailored the JCL and SCL, make
sure you have a valid JOBCARD, and submit the job to load the Root and Cross-reference data
sets.
iprfx
Highest-level qualifier used when assigning data set names for installation and execution data
sets.
iqual
Second-level qualifier used when assigning data set names for installation and execution data
sets.
tdisk
Unit label for temporary disk data sets.
You can use JCL member BC1JACMQ, located in iprfx.iqual.CSIQJCL, to run a quick validation that the
ACM extended query data sets have been loaded correctly.
04-May-2018 77/1109
CA Endevor® SCM - 17.0
The performance of CA Endevor SCM depends on well maintained ACM Query files. The batch job
BC1JACMO is provided to maintain the ACM Query files. The JCL for BC1JACMO can be found in iprfx.
iqual.CSIQJCL. The job BC1JACMO invokes program BC1PACMO to reorganize the root and cross-
reference data sets. Reorganization removes records that are no longer used and merges newly
inserted records into the sorted areas of the files.
Reorganization
Run the BC1PACMO utility regularly to reorganize the root and cross-reference data sets. For
more information, see How to Reorganize Root and Cross-Reference Data Sets (https://support.ca.
com/cadocs/0/CA%20Endevor%20Software%20Change%20Manager%2016%200%20PUBLIC%20ACCESS%
20%20LIMITED%20%20Bookshelf-ENU/Bookshelf_Files/HTML/EndevorSCM_AutoConfig_Option_ENU
/activate_the_acm_query_facility.html#o1712255).
Backup
Edit the BC1PACMO utility so that it creates backup copies of the data sets each time the data
sets are reorganized. For more information, see How to Create Backup Copies of the ACM Query
Data Sets (https://support.ca.com/cadocs/0/CA%20Endevor%20Software%20Change%20Manager%2016%
200%20PUBLIC%20ACCESS%20%20LIMITED%20%20Bookshelf-ENU/Bookshelf_Files/HTML
/EndevorSCM_AutoConfig_Option_ENU/activate_the_acm_query_facility.html#o1712257).
Synchronization
Use the Validate parameter in BC1PACMO to synchronize ACM Query data with inventory data to
remove orphan ACM Query entires. For more information, see How to Synchronize ACM Query
Data with Inventory Data (https://support.ca.com/cadocs/0/CA%20Endevor%20Software%20Change%
20Manager%2016%200%20PUBLIC%20ACCESS%20%20LIMITED%20%20Bookshelf-ENU/Bookshelf_Files
/HTML/EndevorSCM_AutoConfig_Option_ENU/activate_the_acm_query_facility.html#o1712258).
Replacement
Reload the ACM Query data to refresh existing ACM Query references. Program BC1PACMO is
used by job BC1JACML to load new ACM Query data or to refresh existing ACM Query references
with new data from the ACMCOMP DD. For more information, see Load Root and Cross-
Reference Data Sets (https://support.ca.com/cadocs/0/CA%20Endevor%20Software%20Change%
20Manager%2016%200%20PUBLIC%20ACCESS%20%20LIMITED%20%20Bookshelf-ENU/Bookshelf_Files
/HTML/EndevorSCM_AutoConfig_Option_ENU/activate_the_acm_query_facility.html#o1388303).
Although the BC1JACMO job can run concurrently with other CA Endevor SCM jobs, we recommend
that you run it outside of peak hours, to avoid waits in the jobs that update the ACM Query data sets.
BC1PACMO always reserves the ACM Query ROOT and XREF data sets for exclusive use, thus blocking
any other CA Endevor SCM access to ACM Query data for the duration of the job step. Typically, the
execution of BC1PACMO takes less than one minute. However, the Validate parameter greatly slows
04-May-2018 78/1109
CA Endevor® SCM - 17.0
execution of BC1PACMO takes less than one minute. However, the Validate parameter greatly slows
down BC1PACMO execution. We strongly recommend that you use the Validate parameter only
during hours of low CA Endevor SCM activity, because the exclusive access of BC1PACMO blocks most
CA Endevor SCM activities for the duration of the run.
To automate the batch job to run after a minimum number of 5,000 file inserts have been registered,
activate the following setting in the Optional Features Table (ENCOPTBL):
AUTO_ACMQ_FILE_REORG=(on,5000)
If you would rather receive a console message when the threshold is met, instead of automatically
invoking the batch job, also activate the following ENCOPTBL option:
ACMQ_REORG_BY_WTO=ON
For more information, see the comments in the ENCOPTBL table file.
We recommend that you create backup copies of ACM files using BC1PACMO. Although IDCAMS
REPRO and other programs can make copies of the files, the copies created by those programs may
not be synchronized. Therefore, the copies cannot be used to back up the ACMQ data sets.
The BC1PACMO program can back up ROOT and XREF data and reorganize the data set contents. To
create backups, add the following DD statements to BCIPACMO:
//ROOTCOPY DD DISP=(NEW,CATLG),DSN=your.root.copy(+1),
// LRECL=4096,RECFM=FB,DSORG=PS
//XREFCOPY DD DISP=(NEW,CATLG),DSN=your.xref.copy(+1),
// LRECL=4096,RECFM=FB,DSORG=PS
When these two DD statements are present, the elapsed time of BC1PACMO increases by a few
seconds.
EXEC PGM=NDVRC1,PARM='BC1PACMOVALIDATE'
04-May-2018 79/1109
CA Endevor® SCM - 17.0
VALIDATE Verifies that each parent in the ACMQ ROOT file is defined in your inventory (MCF
/ELMCATL). If a parent record is not defined in the inventory, the entry is deleted from ACMQ and the
program returns RC=4.
Component Monitor
ACM has been built to be compatible with source translators (COBOL compilers, assemblers, PL/1
compilers, and linkage editors) without modification. These translators resolve element-to-
component relationships by reading in components—called "input components"—from specific
libraries. Utilities such as the linkage editor, CONLIST, create and write members—called "output
components"—to various libraries.
The ACM Component Monitor automatically and transparently captures relationships by monitoring
selected library data sets. You select the libraries you want monitored by ACM through a processor.
The information captured by the Component Monitor includes the step name, DD statement,
volume, data set name, PDS or PDS/E directory and footprint information (if it exists).
Optionally, ACM provides the CONSCAN processor utility to add additional component information.
04-May-2018 80/1109
CA Endevor® SCM - 17.0
With DFSMS/MVS 1.1 installed, processor steps which execute IEWL—the old linkage editor—actually
execute the binder. Note that component monitoring during execution of the binder and any other
utilities which manipulate program objects also requires the use of the IEWBIND programming
interface or the Directory Entry Services (DESERV) programming interfaces in DFSMS/MVS 1.3.
MONITOR=COMPONENTS
BACKOUT=N
FOOTPRINT=CREATE
As a result, CA Endevor SCM chooses the default values for parameters, which means that by default:
To modify these parameters, specify a DD name starting with ‘EN$DYN’ to define one or more data
set names (in a concatenation) with their monitor/backout/footprint specifications.
CA Endevor SCM does not support FOOTPRNT=CREATE on a concatenated data set. If case this is
required, more than one EN$DYNXX statement is required.
In the following example, no backout records are written to file &SYSLIB1, even if IKJEFT01 allocates it
and writes members to &SYSLIB1. Similarly, all members created in SYSLIB2 are footprinted.
//STEP1EXEC PGM=IKJEFT01
//EN$DYN00 DD DISP=SHR,DSN=&SYSLIB1.,BACKOUT=NO
//EN$DYNM DD DISP=SHR,DSN=&SYSLIB2.,FOOTPRNT=CREATE
In the next example, components are monitored from all files in the SYSLIB concatenation, even if
04-May-2018 81/1109
CA Endevor® SCM - 17.0
In the next example, components are monitored from all files in the SYSLIB concatenation, even if
EDCPRLK reallocates each file separately under another DD name.
In the previous example, the MONITOR=COMPONENTS statements can be removed from the SYSLIB
concatenation, as their presence on the EN$DYNDS DD statement causes all of their components to
be monitored regardless of the DD name under which the file is eventually (re-) allocated.
//SYSLIB DD DSN=BST.C1DEMO.COPYLIB1,DISP=SHR,MONITOR=COMPONENTS
// DD DSN=BST.C1DEMO.COPYLIB2,DISP=SHR,MONITOR=COMPONENTS
Typical outputs would be load modules, program objects, object decks, and listings. The linkage
editor, for example, writes load modules to a SYSLMOD DD statement. For each output data set you
want to monitor, code MONITOR=COMPONENTS, as shown in the following example:
//SYSLMOD DD DSN=BST.C1DEMO.LOADLIB1,DISP=SHR,MONITOR=COMPONENTS
The Component Monitor does not support programs that use EXCP (such as IEBCOPY) to perform I/O
operations.
You are not restricted to the following programs, identified according to program, the Ddname and
descriptions.
CONWRITE ddname
Writes to the first DDname after the EXEC statement. To monitor components expanded by
CONWRITE (namely INCLUDEs), code MONITOR=COMPONENTS on the DDname. If
MONITOR=COMPONENT is coded, set the parameter at PARM=EXPINCL(Y). ACM then monitors
for input components.
IGYCRCTL SYSLIB
Input components (usually copylibs not COBOLlibs).
SYSLIN
Output components. Code only if writing to permanent data set.
04-May-2018 82/1109
CA Endevor® SCM - 17.0
SYSPRINT
Output components. Code only if writing to a permanent data set.
IEWL SYSLIB
Input components (usually utilities not system libraries).
SYSLMOD
Output components.
SYSLIN
Input components. Code only if reading from a permanent data set. ddname—Any data set that
may be referenced by linkage editor control cards.
CONLIST C1LLIBO
Output components.
In the following example, we monitor several data sets in the CA Endevor SCM generate processor
GCIINBL; therefore, we add the keyword MONITOR=COMPONENTS after those data sets. An
explanation describing why each data set was selected for monitoring is included in each example.
//*******************************************************************
//** **
//** COBOL COMPILE AND LINK-EDIT PROCESSOR **
//** **
//** **
//** **
//*******************************************************************
//**
//GCIINBL PROC COBLIB=‘CEE.SCEERUN’,
// COBSTPLB=‘IGY.SIGYCOMP’,
// CSYSLIB1=‘uprfx.uqual1.COPYLIB’,
// CSYSLIB2=‘uprfx.uqual2.COPYLIB’,
// EXPINC=N,
// LISTLIB=‘uprfx.uqual1.LISTING’,
// LOADLIB=‘uprfx.uqual1.LOADLIB’,
// LSYSLIB1=‘uprfx.uqual1.LOADLIB’,
// LSYSLIB2=‘uprfx.uqual2.LOADLIB’,
// MEMBER=&C1ELEMENT.,
// PARMCOB=‘LIB,NOSEQ,OBJECT,PMAP,DMAP’,
// PARMLNK=‘LIST,MAP,SIZE(9999K)’,
// SYSOUT=A,
// WRKUNIT=tdisk
//**
//**********************************************************************
//* ALLOCATE TEMPORARY LISTING DATA SETS *
//**********************************************************************
//*
//INIT EXEC PGM=BC1PDSIN,MAXRC=0
//C1INIT01 DD DSN=&&COBLIST.,DISP=(,PASS,DELETE),
// UNIT=&WRKUNIT.,SPACE=(CYL,(1,2),RLSE),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171,DSORG=PS)
//C1INIT02 DD DSN=&&LNKLIST.,DISP=(,PASS),
04-May-2018 83/1109
CA Endevor® SCM - 17.0
// UNIT=&WRKUNIT.,SPACE=(CYL,(1,2),RLSE),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=3630,DSORG=PS)
//*
Unlike the COBOL compiler or Linkage Editor steps, the CONWRITE step may not contain DD
statements for input. This exclusion is because CONWRITE can reference the INCLUDE libraries as
specified in the TYPE definition and searches for members when expanding those INCLUDE
statements. Therefore, to instruct CONWRITE to monitor inputs, we specify
"MONITOR=COMPONENTS" in the output statement (ELMOUT). This addition instructs the
Component Monitor to monitor CONWRITE as it expands INCLUDEs.
//**********************************************************************
//* GET THE SOURCE FROM THE BASE/DELTA LIBRARIES *
//**********************************************************************
//*
//CONWRITE EXEC PGM=CONWRITE,PARM=‘EXPINCL(&EXPINC)’
//ELMOUT DD DSN=&&ELMOUT.,DISP=(,PASS),
// SPACE=(TRK,(1,1),RLSE),UNIT=&WRKUNIT.,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120),
// MONITOR=COMPONENTS
//**
//*******************************************************************
//** COMPILE THE ELEMENT **
The data sets specified by &CSYSLIB1 and &CSYSLIB2 are being monitored because they are located
where the COBOL compiler reads in copybooks. In this example, we monitor (per the PROC
statement) uprfx.uqual1.COPYLIB (Stage 1) and uprfx.uqual2.COPYLIB (Stage 2). You do not want to
monitor the &COBLIB DD because this calls extraneous COBOL subroutines.
//*******************************************************************
//**
//COMPILE EXEC PGM=IKFCBL00,COND=(0,NE),MAXRC=4,
// PARM=‘&PARMCOB.,BUF=512K,SIZE=1024K’
//STEPLIB DD DSN=&COBSTPLB.,DISP=SHR
//SYSLIB DD DSN=&CSYSLIB1.,
// MONITOR=COMPONENTS,DISP=SHR
// DD DSN=&CSYSLIB2.,
// MONITOR=COMPONENTS,DISP=SHR
//SYSIN DD DSN=&&ELMOUT.,DISP=(OLD,DELETE)
//SYSLIN DD DSN=&&SYSLIN.,DISP=(,PASS,DELETE),
// UNIT=&WRKUNIT.,SPACE=(TRK,(3,5),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120),
// FOOTPRNT=CREATE
//SYSUT1 DD UNIT=&WRKUNIT.,SPACE=(CYL,(1,1))
//SYSUT2 DD UNIT=&WRKUNIT.,SPACE=(CYL,(1,1))
//SYSUT3 DD UNIT=&WRKUNIT.,SPACE=(CYL,(1,1))
//SYSUT4 DD UNIT=&WRKUNIT.,SPACE=(CYL,(1,1))
//SYSUT5 DD UNIT=&WRKUNIT.,SPACE=(CYL,(1,1))
//SYSPRINT DD DSN=&&COBLIST.,DISP=(OLD,PASS)
//**
//*******************************************************************
//** LINK EDIT THE ELEMENT **
//*******************************************************************
The data set indicated by &LOADLIB (uprfx.uqual1.LOADLIB in this example) is monitored because it is
where the Linkage Editor or binder stores the output executable (load module or program object).
//**
//LKED EXEC PGM=IEWL,COND=((0,NE,CONWRITE),(4,LT,COMPILE)),
// PARM=‘PARMLNK’,MAXRC=4
//SYSLIN DD DSN=&&SYSLIN.,DISP=(OLD,DELETE)
//SYSLMOD DD DSN=&LOADLIB(&MEMBER).,
// MONITOR=COMPONENTS,DISP=SHR
//SYSLIB DD DSN=&LSYSLIB1.,
04-May-2018 84/1109
CA Endevor® SCM - 17.0
SYSLIB is where the Linkage Editor or binder resolves CALL or INCLUDE statements, based on inputs.
In this example, we are monitoring the data sets indicated by &LSYSLIB1 (uprfx.uqual1.LOADLIB -
Stage 1) and &LSYSLIB2 (uprfx.uqual2.LOADLIB - Stage 2).
// MONITOR=COMPONENTS,DISP=SHR
// DD DSN=&LSYSLIB2.,
// MONITOR=COMPONENTS,DISP=SHR
// DD DSN=&COBLIB.,
//SYSUT1 DD UNIT=&WRKUNIT.,SPACE=(CYL,(1,1))
//SYSPRINT DD DSN=&&LNKLIST.,DISP=(OLD,PASS)
//**
//*******************************************************************
//* STORE THE LISTINGS IF: &LISTING=LISTING. LIBRARY NAME *
//*******************************************************************
The data set indicated by &LISTLIB (uprfx.uqual1.LISTING, in this example) is monitored because
"C1LLIBO" is where CONLIST writes its output listings.
//*
//CONLIST EXEC PGM=CONLIST,MAXRC=0,PARM=STORE,
// EXECIF=(&LISTLIB.,NE,NO)
//C1LLIBO DD DSN=&LISTLIB.,DISP=SHR,
// MONITOR=COMPONENTS
//C1BANNER DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171)
//LIST01 DD DSN=&&COBLIST.,DISP=(OLD,DELETE)
//LIST02 DD DSN=&&LNKLIST.,DISP=(OLD,DELETE)
//*
Since MONITOR=COMPONENTS has been specified after certain data sets within GCOBNBL, ACM’s
Component Monitor is activated and automatically collects changes to the components each time the
generate processor is executed. The change information for those data sets is further stored as ACM
Component Lists in base/delta format.
Do not re-create load modules at the target stage by coding a compile and link step in a move
processor. This causes the load module footprint to become out of synchronization with Master
Control File Generate information for the element.
Typically, the move processor is coded to perform two generic functions: 1) to perform a translation
(compile and link-edit), and 2) to move a load module and any other entry stage members created by
the entry stage generate processor.
If you code a move processor to perform a translation (for example, compile, link-edit), code
MONITOR=COMPONENTS as described in Monitoring Components in a Generate Processor.
If you code a move processor in order to move load modules, listings, and so on from the entry
stage to the next mapped stage, you might also want to move the current (version/level) of the
Component List. You can do this using a special processor utility BC1PMVCL, which is provided
with ACM. To execute this program, code a step in the CA Endevor SCM move processor that
specifies the EXEC statement with a MAXRC=0, as illustrated below:
04-May-2018 85/1109
CA Endevor® SCM - 17.0
Now when the element in the entry stage is moved to the next mapped stage, its corresponding
Component List (containing all the element-to-component relationships) will also be moved to the
next mapped stage.
If you want a move processor to replace the OUTPUT components of the existing component list with
the new output components that are the result of the move processor then
MONITOR=COMPONENTS should be coded only on the OUTPUT files of the steps in the processor.
When BC1PMVCL gets executed as the last step of the processor, it automaticallys replace the
existing OUTPUT components with the newly captured output components. If you do not want this to
happe, do not code MONITOR=COMPONENTS in your move processor.
The utility program BC1PMVCL is not the last step in the move processor and
components are being monitored in any step following BC1PMVCL.
In the following sample move processor (MLODNNL), we've specified that when the load module is
moved from Stage 1 to Stage 2, its associated Component List information is also moved and
updated.
//**********************************************************************
//* *
//* COPY LOAD MODULES FROM STAGE 1 TO STAGE 2 AND THEIR ASSOCIATED *
//* COMPONENT LIST AND LISTINGS. *
//* *
//**********************************************************************
//*
//MLODNNL PROC LISTLIB='YES',
// LISTLIB1='&PROJECT..&GROUP.&STG1..LISTLIB',
// LISTLIB2='&PROJECT..&GROUP.&STG2..LISTLIB',
// LOADLIB1='&PROJECT..&GROUP.&STG1..LOADLIB',
// LOADLIB2='&PROJECT..&GROUP.&STG2..LOADLIB',
// PROJECT='IPRFX.IQUAL',
// GROUP='SMPL',
// STG1='&C1SSTAGE.', CURRENT STAGE
// STG2='&C1STAGE.', TO STAGE
// MONITOR=COMPONENTS,
// SYSOUT=*,
// WRKUNIT=TDISK
//**********************************************************************
//* ALLOCATE TEMPORARY LISTING DATASETS *
//**********************************************************************
//INIT EXEC PGM=BC1PDSIN
//C1INIT01 DD DSN=&©LIST.,DISP=(,PASS,DELETE),
// UNIT=&WRKUNIT.,SPACE=(CYL,(1,2),RLSE),
04-May-2018 86/1109
CA Endevor® SCM - 17.0
// DCB=(RECFM=V,LRECL=121,BLKSIZE=125,DSORG=PS)
//**********************************************************************
//* COPY THE LOAD MODULE *
//**********************************************************************
//BSTCOPY EXEC PGM=BSTCOPY,MAXRC=04
//SYSPRINT DD DSN=&©LIST.,DISP=(OLD,PASS)
//SYSUT3 DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1))
//SYSUT4 DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1))
//INDD DD DSN=&LOADLIB1.,DISP=SHR
//OUTDD DD DSN=&LOADLIB2.,DISP=SHR,MONITOR=&MONITOR.
//SYSIN DD *
COPY O=OUTDD,I=INDD
SELECT MEMBER=((&C1ELEMENT.,,R))
//*******************************************************************
//* COPY & STORE THE LISTINGS IF: &LISTING=LISTING LIBRARY *
//*******************************************************************
//COPYLIST EXEC PGM=CONLIST,MAXRC=0,PARM=COPY,COND=EVEN,
// EXECIF=(&LISTLIB.,EQ,YES)
//C1LLIBI DD DSN=&LISTLIB1.,DISP=SHR
//C1LLIBO DD DSN=&LISTLIB2.,DISP=SHR,MONITOR=&MONITOR.
//C1BANNER DD DSN=&&BANNER.,DISP=(,PASS,DELETE),
// UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171,DSORG=PS)
//LIST01 DD DSN=&©LIST.,DISP=(OLD,DELETE)
//*******************************************************************
//* PRINT THE LISTINGS IF: &LISTING=NO. *
//*******************************************************************
//PRNTLIST EXEC PGM=CONLIST,MAXRC=0,PARM=PRINT,COND=EVEN,
// EXECIF=(&LISTLIB.,EQ,NO)
//C1BANNER DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171,DSORG=PS)
//C1PRINT DD SYSOUT=&SYSOUT.,
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=1330,DSORG=PS)
//LIST01 DD DSN=&©LIST.,DISP=(OLD,DELETE)
//**********************************************************************
//* UPDATE THE COMPONENT LIST WITH THE NEW OUTPUT COMPONENTS *
//* AND MOVE THE COMPONENT LIST TO THE NEXT STAGE
//**********************************************************************
//MOVECL EXEC PGM=BC1PMVCL,COND=(0,NE)
//*
Important! The delete processor runs as the result of a DELETE action. When the DELETE
action is executed, the element and its associated Component List are deleted. Therefore,
you should not monitor a delete processor.
04-May-2018 87/1109
CA Endevor® SCM - 17.0
Component List
The ACM component list comprises multiple internal component categories. Each of these
component categories provides an essential piece of the in-depth information to analyze and manage
software configurations.
Element Information
Source for which an CA Endevor SCM processor is being executed. It tells you what the originating
CA Endevor SCM element source was when the component list was created.
Processor Information
Processor that is being executed for this particular element. It contains the
MONITOR=COMPONENTS keyword for specific data sets, and tells you the specific CA Endevor
SCM processor used when the component list was created.
Symbol Information
Symbolics that have been defined by the user for this processor. It tells you the symbolic, the
value that will be substituted for it when the processor is run, and where that value has been
defined — either directly in the PROC statement of the processor or as overridden through the
Processor Group Symbolics panel.
Input Components
Members in the monitored data sets which are read by programs (such as the compiler or linkage
editor) in the CA Endevor SCM processor when it collects components to build composite
modules. It tells you the related "pieces" of the element and where they came from.
Output Components
Monitored data sets which are written to by programs (such as the linkage editors or CA Endevor
SCM utilities) when composite modules are created. It tells you the members created during
processor execution.
The following diagram illustrates where the different pieces of component list information are
derived.
04-May-2018 88/1109
CA Endevor® SCM - 17.0
When a processor step abends, the monitored component information is logged in a new component
Delta level. If no component information has been logged at the time of the abend, then a Delta level
without component information is created.
The component list Base and Delta members are stored in the Delta library as defined on the Type
definition.
If the executed processor or processor group is changed to *NOPROC*, CA Endevor SCM deletes the
existing component list and its history.
Base/Delta Technology
The first time an CA Endevor SCM ACM component list is produced for a processor, it becomes the
base. Subsequent processor executions create new component lists, which are automatically
compared against the base to reflect component changes. ACM gives each set of changes (delta) a
new component level number. These base and deltas are stored in base and delta libraries as defined
in the element type definition.
04-May-2018 89/1109
CA Endevor® SCM - 17.0
As previously illustrated, ACM assigns each set of changes (delta) a new component level number. In
this example, the numbers assigned are Component Level 01.00 through Component Level 01.03.
Component Levels
The component level is indicated in the COMPONENT LEVEL INFORMATION section of the component
list. There may be a discrepancy between the component level and the element level because there is
absolutely no correlation between the component level and the element level .
Component levels are created each time a component list is generated and has changed since the last
generation. Component-level numbers are merely relative to the most recent generation; for
example, if component level 01.53 is the most recent level, level 01.52 is the one preceding it, and so
forth.
The element level, on the other hand, is automatically increased each time the element is updated,
regardless of whether the processor executed successfully.
component levels 51 through 96 are renumbered as component levels 02 through 46. This process is
04-May-2018 90/1109
CA Endevor® SCM - 17.0
component levels 51 through 96 are renumbered as component levels 02 through 46. This process is
repeated each time component level 96 is passed. What’s important to remember is that, at any
point in time, component level 00 is always considered to be the base, with subsequent component
levels treated as deltas.
The Display Elements/Components List panel appears. From this panel, you can view different
types of information about Components lists.
6. Identify the element and the information that you want to display on this panel and press
Enter. The panel that displays next depends on the value in the DISPLAY SYS/SBS LIST field:
If you provided a wildcard in the SYSTEM and/or SUBSYSTEM fields and DISPLAY SYS/SBS
LIST = Y, CA Endevor SCM displays a System and/or Subsystem Selection List. Make
selections as necessary, pressing Enter after each selection.
If you provided a wildcard in the ELEMENT field, CA Endevor SCM displays an Element
Selection List or Confirmation panel, as indicated in the following:
If Build using MAP=Y, CA Endevor SCM displays a selection list of all elements in all
map environments that meet search criteria.
If Build using MAP=N (Default), CA Endevor SCM displays a selection list of all elements
in the current environment that meet search criteria.
If Build using MAP=Y, CA Endevor SCM displays a confirmation panel, indicating the
number of elements selected (from all environments).
04-May-2018 91/1109
CA Endevor® SCM - 17.0
If Build using MAP=N, CA Endevor SCM displays a confirmation panel, indicating the
number of elements selected (from the current environment).
If a Confirmation panel appears, press Enter to view the requested display for the number
of elements indicated on the Confirmation panel.
If an Element Selection List appears, use it to display information for one or more
elements. You can select any of the options by typing the option to the left of the element
name and pressing Enter.
The product footprints contain the following information: site ID, environment, system, subsystem,
04-May-2018 92/1109
CA Endevor® SCM - 17.0
The product footprints contain the following information: site ID, environment, system, subsystem,
element, type, stage, version/level, and generate date/time.
When elements are controlled by CA Endevor SCM, their footprints are carried into the component
list during program execution. If, for example, you reference a copy record in a PDS that is CA
Endevor SCM controls, it contains a footprint that appears on the component list.
Load Modules controlled by CA Endevor SCM can contain multiple footprints. Consequently, when an
element is a load module (with multiple footprints), ACM does not capture all of the footprints for
display on the component list.
Similarly, Quick-Edit invokes ACMQ to determine element dependencies when it displays the initial
text edit panel. It communicates the results of the query using ISPF ‘note’ lines. The additional
messages appear after the ‘fetched from location’ information note lines, if the element is being
fetched to the edit inventory location.
You can view "where-used" information against the ACM component data by utilizing the ACM Query
Facility. To activate this facility, see Using CA Endevor Software Change Manager ACM (see page 74).
The ACMQ command is used to perform online queries or SCL generation against the root and cross-
reference data sets.
Start ACMQ
You can start the ACMQ facility at any time to manage, through advanced automated technology, the
interrelationships between software components.
04-May-2018 93/1109
CA Endevor® SCM - 17.0
1. Execute a CLIST that allocates the library that contains the C1DEFLTS table and the CA
Endevor® SCM product libraries.
To refresh the component data that the facility uses in its searches, exit the ACMQ facility and then
re-enter it.
Circular References
A circular reference is an element that uses the same element as an input component. For example,
element A that uses element A as an input component. Another example, is element B that uses
element C, which uses element B. Circular references are, by default, included in ACMQ results and
are identified in ACMQ results by a C character following the level number.
ACMQ can identify circular references regardless of the number of elements between the first and
second occurrence of the same element.
A circular reference for a specific element is listed only once on every level. When a circular reference
for the same element exists on multiple levels (for example, A-B-A as well as A-C-D-A) then it is listed
on every level where it appears.
04-May-2018 94/1109
CA Endevor® SCM - 17.0
Indirect References
An indirect reference is an element whose name and type are the same as a previously found
element, but whose location is different. Indirect relationships can result when an element is moved,
but not generated, using a Move processor. By default, indirect references appear in ACMQ results
and are marked by an asterisk (*) following the level number.
The location of the indirect reference must be mapped with its model (the previously found
element). For where-used queries, indirect references are taken from locations lower in the map
from their model. For components used queries, indirect references are taken from locations higher
in the map from their model.
The purpose of indirect references is to find relations that may have been lost while using Move
processors. An indirect reference that adds no new relations to the ACMQ report, other than itself, is
not listed on the ACMQ report.
COPYA, PGMB, and PGMC exist in the same environment (ENV1) and stage (STG 1).
Suppose that all three of the elements listed in the previous report are moved to the next stage (STG
2) using a Move processor, meaning that the component list data has been copied, but not rebuilt by
a Generate processor. In this case, a where-used query on COPYA would result in the following
output:
LVL ELEMENT TYPE ENVIRON SYSTEM SUBSYS STG
1 COPYA CPY ENV1 .. .. 1
2 PGMB COBOL ENV1 .. .. 2
2* PGMB COBOL ENV1 .. .. 1
3* PGMC LNK ENV1 .. .. 2
The first of the two elements that are marked with an asterisk (*) has the same name and type as an
element that is known to contain direct references to COPYA. However, because this element has
been moved to another CA Endevor® SCM location without being rebuilt, ACMQ cannot be sure that
it still contains references to COPYA. Therefore, ACMQ treats this element as having only an indirect
reference to the object of the query. In the report output, these indirect references are marked with
an asterisk and are displayed after the elements that definitely contain direct references to your
search.
Note also that elements that contain a reference to an indirect reference are themselves considered
indirect references, unless they also contain a direct reference to your search, or to an element that
directly references your search.
04-May-2018 95/1109
CA Endevor® SCM - 17.0
COPYA has no component list. Thus, when it is moved to the next stage, no component list
changes take place, nor do any ACMQ changes take place. Accordingly, ACMQ continues to
reference it in ENV1 / STG 1.
When PGMB COBOL is moved to the next stage, its component list is copied and becomes the
component list of PGMB COBOL in STG 2. However, because no changes have been made to the
list (other than copying it), the reference in PGMB COBOL in STG 2 to COPYA remains. ACMQ then
determines that PGMB COBOL in ENV1 / STG 1 is an indirect reference because it has the same
element name and type as PGMB COBOL in ENV1 / STG 2.
PGMC LNK in ENV1 / STG 1 had a reference to PGMB COBOL in ENV1 / STG 1. When it was moved,
it underwent the same changes as PGMB COBOL; thus, PGMC LNK in ENV1 / STG 2 continues to
reference PGMB COBOL in ENV1 / STG 1. Because PGMC LNK refers to an indirect reference
(PGMB COBOL in ENV1 / STG 1), ACMQ considers it to be an indirect reference.
A related reference is an element whose relationship to another element is identified using the
extended processor CONRELE utility, which includes entities related to an element in a component
list when generating component list reports and when using the LIST action. Related references
appear in ACMQ results, by default, and are marked by an R character following the level number.
Indirect references of these CONRELE related references are marked by an *R (R preceded by an
asterisk) following the level number.
ACMQ distinguishes between references created by the ACM Component Monitor and references
created using the CONRELE utility. The references created with the CONRELE utility appear in ACMQ
reports marked with an R character following the level number. ACMQ also searches for indirect
references of these CONRELE utility related references. If found they are marked by an *R (R
preceded by an asterisk) on the report.
If you have thousands of related comments or related objects, you may want to enable the option
ACMQ_CMNT_QUERY_PERF=ON in the Optional Features Table (ENCOPTBL). When this feature is
enabled, the search string is matched with the beginning of each comment or object record. By
default the option is disabled, which allows searching throughout the entire string.
Option
Specifies the type of query to be performed. Choose one of the following values:
04-May-2018 96/1109
CA Endevor® SCM - 17.0
O - Where-Used Object Query: Displays WHEre-used Object relationships that have been
manually defined using the CONRELE utility in a processor. Use the Comment/Object field to
specify the data. This field is case-sensitive.
Element/Member
Specifies the name of the element or member object of the query. Valid for options blank or M.
Query Options
Specifies the type of query to be performed. Choose one of the following values:
Note: "COM" is valid for Element queries only, as Members, Comments, and Objects
do not have component lists.
Foreground/Batch Mode: Directs ACMQ either to submit a JOB for batch processing or to
perform the query processing in foreground mode. (If batch mode is specified, a secondary
panel is displayed to allow entry of a JOBCARD.)
Create Generate SCL: Directs ACMQ to create standard CA Endevor® SCM GENERATE SCL
syntax. A secondary panel is displayed to allow entry of GENERATE action-related options.
04-May-2018 97/1109
CA Endevor® SCM - 17.0
Exclude circular references: Specifies whether to exclude circular references. Valid values are
Y or N:
Y - Exclude circular relationships records from the output data returned
N - Include circular relationships records from the output data returned.
Exclude indirect: Specifies whether to exclude indirect references. Valid values are Y or N:
Y - Exclude indirect relationships records from the output data returned
N - Include indirect relationships records from the output data returned.
Exclude related: Specifies whether to exclude related references. Valid values are Y or N:
Y - Exclude related relationships records from the output data returned
N - Include related relationships records from the output data returned.
ACTION OPTIONS
The CCID field allows you to specify any 12-character CCID. This CCID is not validated until the
built SCL is actually executed. The Comment field is available for you to define a comment of up
to 40 characters. No validation is done on the Comment field.
Either Copyback or NoSource can be set to Y, but not both. The Copyback and NoSource options
use the inventory specified on this panel. If neither Copyback nor NoSource is specified, then the
default option is Generate In Place. For the Generate in Place option, Inventory is invalid and
cannot be specified.
STOPRC
Use this field to insert a SET STOPRC value. Valid values range from 4 to 16. CA Endevor® SCM will
stop processing actions when a previous action has a return code equal to or higher than the
defined STOPRC.
04-May-2018 98/1109
CA Endevor® SCM - 17.0
Note: If you append SCL to existing SCL and the existing SCL already contains a SET STOPRC
card, this option will not modify the existing SET STOPRC card.
The utility accepts SCL as input. Depending on the list syntax you include in BC1JACMQ, the utility
produces one of the following types of reports.
The List Using Components For Element action produces a components-used report that lists
elements that use the component you specify.
The List Used Components For Element action produces a where-used report that lists
components that are used by the element you specify.
If the Set Build Action Generate statement is coded in the SCL prior to one of the list actions, then
generate action SCL statements are created, instead of a report.
The utility offers equivalent functionality to the online ACM query facility and has some extra filtering
options that are not available in foreground.
1. Add a valid job card at the front of the BC1JACMQ job stream.
2. Change the data set names and other variables to the appropriate values for your installation.
a. Edit the Set Build Action Generate statement. For more information, see Set Build
Action Generate.
b. After the Set Build Action Generate statement, include one of following List
statements.
04-May-2018 99/1109
3.
To build SCL statements limited to elements that use a specified component, use
the SCL for List Using Components for Elements. (see page 102)
The utility will build SCL statements for generate actions for the elements identified by the
List statement.
4. Edit BC1JACMQ to change the ACMOUT statement to allocate, or to point to, an existing 80-
character file.
►──┬─────────────────────────────────────────────────────────┬──────────►
└─ FROm ─┤ LOC ├ ┬── COPyback ─┬────────────┬──┬──────────┘
│ └─ SEArch ◄ ─┘ │
└─ NOSOurce ──────────────────┘
►─ ¤ ─┬───────────────────────────────────────────┬─ ¤ ─ . ─────────────►◄
├─ CCId ─ ccid ─────────────────────────────┤
└─ COMment ─ comment ───────────────────────┘
Expansion of LOC
├── ¤ ─┬─ ENVironment ─ environment-name ─┬─ ¤ ─────────────────────────┤
├─ SYStem ─ sys-name ──────────────┤
├─ SUBsystem ─ subsys-name ────────┤
└─ STAge NUMber ─ stage-number ────┘
Parameters
COPYBACK SEARCH
(Optional) Causes the current level of the element to be copied back to the FROM stage
before the element is generated. CA Endevor® SCM first copies the current level of the
element back to the FROM stage, then generates the element. CA Endevor® SCM searches
for the element first in the current environment, then in other stages along the map.
If the element currently exists in the FROM stage, CA Endevor® SCM ignores the
COPYBACK option and simply generates the element.
SEARCH is only valid with the COPYBACK option. NOSEARCH is no longer valid on the
04-May-2018 100/1109
CA Endevor® SCM - 17.0
SEARCH is only valid with the COPYBACK option. NOSEARCH is no longer valid on the
COPYBACK clause. COPYBACK implies SEARCH. It is not necessary to specify SEARCH.
COPYBACK cannot be used with NOSOURCE.
NOSOurce
(Optional) When the target location has a sourced element, the element is generated in
place.
When the target location has a sourceless element, the element is generated at the target
location using the source of the first occurance of the element found up the map.
When the element does not exist at the target location, the element is generated at the
target location using the source of the first occurance of the element found up the map.
The source is not fetched to the target. The MCF element created at the target location
will contain data similiar to a fetched back element except that the element base and
delta name fields will be blank and the record will be marked as a sourceless element.
NOSOURCE cannot be used with COPYBACK. It is not necessary to specify the SEARCH
option with NOSOURCE, because NOSOURCE implies SEARCH.
CCID ccid
(Optional) Specifies a 1- to 12-character CCID to be included in each of the generate action
SCL statements. If your site's system definitions requires a CCID, you must specify this option.
If you do not provide a required CCID, then when the generate action SCL statements are
executed, the generate action will fail. The generate with copyback action uses the CCID to:
COMMENT comment-text
(Optional) Specifies the 1- to 70-character comment to be included in the SCL generate
actions. If your site's system definitions requires a comment, you must specify this option. If
you do not provide a required comment, then when the generate action SCL statements are
executed, the generate action will fail. The generate with copyback action uses the comment
to:
LOC
Identifies the location to which the elements are copied before the elements are generated. This
is the location from which the element is generated. If you use the FROM keyword, you must at
least specify the environment and stage. In addition, you can also specify system, subsystem, or
both, but environment and stage are always required.
ENVironment environment-name
Specifies the one- to eight-character name of the environment in which you want to perform
your query.
04-May-2018 101/1109
CA Endevor® SCM - 17.0
SYStem system-name
Specifies the one- to eight-character name of the system in which you want to perform your
query.
SUBsystem subsystem-name
Specifies the one- to eight-character name of the subsystem in which you want to perform
your query.
1. Add a valid job card at the front of the BC1JACMQ job stream.
2. Change the data set names and other variables in BC1JACMQ to the appropriate values for
your installation.
a. To produce a components-used report, use the SCL for List Using Components For
Element. (see page 102)
b. To produce a where-used report, use the SCL for List Used Components For Element.
(see page 104)
4. (Optional) Edit BC1JACMQ to change the ACMOUT file format, depending on the type of
report layout you prefer.
To return the data in report format, which includes headings and page numbers, code this
statement:
//ACMOUT DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0)
//ACMOUT DD DSN=uprfx.uqual.file-name,RECFM=FB,LRECL=80
To return the data in panel display format, which includes the same data shown in report
format, except it does not include headings or page numbers and is shown in 80-character
layout, code this statement:
04-May-2018 102/1109
CA Endevor® SCM - 17.0
├─ MEMber ─ member ──────────────┤
├─ OBJect ─ objecttext ──────────┤
└─ COMment ─ Comment text ───────┘
►─┬─────────────────────────────────────────────────────────┬─ . ─────►◄
└─ OPTions ─ ¤ ─┬───────────────────────────────────┬─ ¤ ─┘
├─ FILTer COMPonents WITh ─┤ LOC ├──┤
├─ EXClude CIRculars ───────────────┤
├─ EXClude INDirect ────────────────┤
└─ EXClude RELated ─────────────────┘
Expansion of LOC
├── ¤ ─┬─ ENVironment ─ environment-name ─┬─ ¤ ─────────────────────────┤
├─ SYStem ─ sys-name ──────────────┤
├─ SUBsystem ─ subsys-name ────────┤
├─ TYPe ─ type-name ───────────────┤
└─ STAge NUMber ─ stage-number ────┘
Parameters
MEMber member
Specifies a component that matches the specified 1- to 10-character member name. Name
masking is allowed.
DSName 'dsname'
(Optional) Specifies the 1- to 44-character data set name for the specified member. Enclose
the data set name in single quotes. Name masking is allowed.
Object object-text
Specifies the object text string. Name masking is not allowed. Each object record in the ACM
query data sets is matched with the specified text string. If the string is found anywhere in the
text, the record is used.
Comment comment-text
Specifies the comment text string. Name masking is not allowed. Each comment record in the
ACM query datasets is matched with the specified text string. If the string is found anywhere
in the text, the record is used. For example, if the ACMQ content is “Will ACMQ find this
comment string”, then a query using “this*” will not find the string. However, a search for
“this comm” will result in a match. ACMQ respects uppercase and lowercase letters if the
option MONOCASE_SEARCH is activated in the optional features table ENCOPTBL.
04-May-2018 103/1109
CA Endevor® SCM - 17.0
OPTions
(Optional) Specifies various options.
EXClude CIRculars
Filters the ACM data to exclude elements that have a circular relationship to the object of
your search.
EXClude INDirect
Filters the ACM data to exclude indirectly related components.
EXClude RELated
Filters the ACM data to exclude related components.
LOC
The location fields further qualify the element query object. You can specify the location by the
environment, system, subsystem, or type.
ENVironment environment-name
Specifies the one- to eight-character name of the environment in which you want to perform
your query.
SYStem system-name
Specifies the one- to eight-character name of the system in which you want to perform your
query.
SUBsystem subsystem-name
Specifies the one- to eight-character name of the subsystem in which you want to perform
your query.
TYPe type-name
Specifies the type of the elements for which you are searching. The type name can be one to
eight characters in length.
Specifies the number of the stage in which you want to perform your query.
►─┬─────────────────────────────────────────────────────────┬─ . ───────►◄
└─ OPTions ─ ¤ ─┬───────────────────────────────────┬─ ¤ ─┘
├─ FILTer COMPonents WITh ─┤ LOC ├ ─┤
├─ EXClude CIRculars ───────────────┤
├─ EXClude INDirect ────────────────┤
└─ EXClude RELated ─────────────────┘
Expansion of LOC
04-May-2018 104/1109
CA Endevor® SCM - 17.0
Expansion of LOC
├── ¤ ─┬─ ENVironment ─ environment-name ─┬─ ¤ ──────────────────────────┤
├─ SYStem ─ sys-name ──────────────┤
├─ SUBsystem ─ subsys-name ────────┤
├─ TYPe ─ type-name ───────────────┤
└─ STAge NUMber ─ stage-number ────┘
Parameters
OPTions
EXClude CIRculars
Filters the ACM data to exclude components that have a circular relationship to the object of
your search.
EXClude INDirect
Filters the ACM data to exclude indirectly related components.
EXClude RELated
Filters the ACM data to exclude related components.
LOC
The location fields further qualify the element query object. You can specify the location by the
environment, system, subsystem, or type.
ENVironment environment-name
Specifies the one- to eight-character name of the environment in which you want to perform
your query.
SYStem system-name
Specifies the one- to eight-character name of the system in which you want to perform your
query.
SUBsystem subsystem-name
Specifies the one- to eight-character name of the subsystem in which you want to perform
your query.
TYPe type-name
Specifies the type of the elements for which you are searching. The type name can be one to
eight characters in length.
04-May-2018 105/1109
CA Endevor® SCM - 17.0
This section describes the various SCL statements that can be used with ACM.
Note: For more information about SCL, see SCL Reference (https://docops.ca.com/display/CE17
/SCL+Reference).
LIST Action
This action scans elements or members in the Master Control File or a library, and generates a list of
elements/members that meet your specific selection criteria.
The CA Endevor® SCM LIST action invokes ACMQ to satisfy simple, component name, inventory
location, “WHERE [INPUT | OUTPUT]” components criteria. Additional criteria such as CCID or
historical dependencies (“ALL” parameter) require CA Endevor® SCM to search its base / delta
libraries to perform the search. CA Endevor® SCM defaults to using ACMQ whenever possible to
perform component-related list processing.
The LIST action includes several clauses that pertain specifically to ACM. You can use these clauses to
limit selection criteria as it applies to component lists.
WHERE Clauses
WHERE clauses instruct CA Endevor® SCM to generate a list of elements or members where specific
criteria is met. Within the WHERE clause of the LIST action are two sections that pertain specifically
to ACM:
You can also indicate that a specific range of components be considered, using the THROUGH
04-May-2018 106/1109
CA Endevor® SCM - 17.0
You can also indicate that a specific range of components be considered, using the THROUGH
component-name clause with the WHERE component spec clause.
If the component is footprinted, you can specify the following additional selection criteria:
Version and/or level of the component. When you specify a version number, only those
elements with components matching that number is selected for the LIST action.
Similarly, if you specify a level number here, only those elements with components matching
that level is selected.
Component location information (environment, system, subsystem, type, and stage, or file or
dsname).
WHERE ACM component spec Lets you set compound criteria, when component lists must
contain one component and another or either one component or another. You can also specify
that a component list that does not contain one component and another or either one
component or another be selected.
Build Clauses
Indicate specific information to be applied to each action statement. Within the BUILD clause are two
sections that apply to CA Endevor® SCM ACM:
BUILD LEVEL
Indicates whether you want the version and level of the specified element to appear on the
action cards generated by the LIST request. Three options are available when coding this clause:
CURRENT
If the WHERE component spec clause has not been coded for the action, or no component list
exists, CA Endevor® SCM defaults to the current level of the element.
NONE
Indicates that the current version and level are not to be listed for the element.
ACTUAL
Indicates that the level of the component as recorded in the component list, rather than the
current level of the element as recorded in the Master Control File, should be used when
building the action statement.
Print Action
This action prints selected information about an elements) or library members, depending on the
criteria entered.
04-May-2018 107/1109
CA Endevor® SCM - 17.0
When you select the COMPONENTS option, CA Endevor® SCM prints all component information
(element, processor, input, and output data) relating to the element specified. You can code this
option alone or with the following PRINT options: BROWSE, CHANGE, HISTORY, SUMMARY, or
MASTER.
CA Endevor® SCM prints as much information as is available for the component list. For example, if
you request the COMPONENT CHANGES option but there are no changes to the output components
section, that section would not appear on the associated listing.
SET BUILD LEVEL CURRENT defaults to the current level of the element if the WHERE component-
spec clause has not been coded for the action or if no component list exists.
SET BUILD NONE indicates that the current version and level are not to be listed for the element.
SET BUILD LEVEL ACTUAL indicates that the actual level of the component should be used when
building the request.
SET BUILD WITH COMPONENTS indicates that action cards should be generated for every input
component associated with the designated element.
ONLY COMPONENTS (used with the DELETE action) allows you to delete the component lists for
an element, but not the element itself.
COMPONENT (used with the PRINT action) provides printed output pertaining to component list
information for the element specified. You can use this option alone, or in combination with one
of the following PRINT options: BROWSE, CHANGE, HISTORY, SUMMARY, or MASTER.
WHERE component-spec
04-May-2018 108/1109
CA Endevor® SCM - 17.0
Clear Statements
CLEAR statements clear the information that has been designated by the related SET statements.
CLEAR BUILD clears like information you have entered in the SET BUILD statement.
CLEAR OPTIONS clears like information you have entered in the SET OPTIONS statement. Note,
however, that to clear the SET OPTIONS COMPONENT statement, you must enter the statement
CLEAR OPTIONS PRINT.
CLEAR WHERE clears the like information you have entered in a SET WHERE statement.
Note: The Autogen action option provides a more efficient way to propagate component
changes. When specified on an Add, Update, or Generate action for a component
element, Autogen automatically generates the elements that use the component element.
Autogen requires that ACM be enabled at your site. For a more detailed description of
Autogen, see Autogen Action Option (see page 113). For more information about Autogen,
see the scenario-based knowledge document , in the .
Note: The Validate action is a more efficient way to validate components. The SCL
statement Validate lets you verify that all components exist and are valid. Valdiate
requires that ACM be enabled at your site. For more information, see Validate
Components (see page 116).
This example uses ACM to determine why element FINAPP01 experienced a production outage.
04-May-2018 109/1109
CA Endevor® SCM - 17.0
2. Submit the job for batch execution and view the resulting report.
By coding:
FROM ENVIRONMENT
Further specifies the production stage (STAGE P) of the ACCTPAY subsystem within the FINANCE
system.
Since no TO statement has been coded, CA Endevor® SCM uses the default TO C1PRINT to print
the element.
How to Submit the Job for Batch Execution and View the Resulting Report
Once the SCL has been coded, submit the job for batch execution using the batch processing
capabilities. The SCL commands are now automatically applied to the information collected and
stored by ACM.
After submitting the job, you can view the batch execution results.
ACM lets to analyze system behavior and quickly determine the changes that might have caused our
production failure.
04-May-2018 110/1109
CA Endevor® SCM - 17.0
Note: The Autogen action option provides a more efficient way to propagate component
changes. When specified on an Add, Update, or Generate action for a component element,
Autogen automatically generates the elements that use the component element. Autogen
requires that ACM be enabled at your site. For a more detailed description of Autogen, see
Autogen Action Option (see page 113). For more information about Autogen, see the
scenario-based knowledge document , in the .
When changes are made to a component, it is necessary to propagate those changes to all programs
containing that component.
In the example that follows, copybook COPYREC needs to be changed in order to complete a change
request for program C1PRTX00. Once the change is completed and tested in program C1PRTX00, the
change to copybook COPYREC is propagated to all programs in which it is used.
If you are not using AUTOGEN, propagating component changes to all affected programs requires the
following steps:
By coding:
04-May-2018 111/1109
CA Endevor® SCM - 17.0
By coding:
LIST ELEMENTS *
Instruct ACM to look at all elements, regardless of name.
FROM ENVIRONMENT
Restrict the search of elements to the production stage (STAGE P) of the Personnel system
(SYSTEM PERSONEL), regardless of subsystem and type.
TO DSNAME
Instruct ACM to write out the list of elements which meet the search criteria for the data set BST.
C1DEMO.SRCLIB. Since no member name was coded in the OPTIONS statement, a default
member name (TEMPNAME) is created. If member TEMPNAME exists, it is not replaced, and this
instance causes an error that stops execution of the LIST command.
However, if member TEMPNAME does not exist, it is created and SCL statements are written
identifying every element that meets the WHERE conditions.
WHERE
Instruct ACM to look at every element with a component list, and to search the component list
for an input component of COPYREC. Every element that contains INPUT COMPONENT = COPYREC
will have an SCL action statement written out to the member TEMPNAME in the BST.C1DEMO.
SRCLIB data set.
By coding:
SET ACTION
Instruct ACM to change all of the &&ACTION statements to GENERATE. ("&&ACTION" appears on
the action cards generated for each element/component when you do not specify an action in the
LIST request.) The GENERATE action executes the generate processor (compile) for all programs
which use the copybook COPYREC.
SET OPTION
By setting the COPYBACK option, ACM copies back the current version/level of each program to
the entry stage. (if it does not exist in the entry stage) before executing the generate processor.
04-May-2018 112/1109
CA Endevor® SCM - 17.0
Autogen is available in batch only for the Add, Update, and Generate actions and cannot be used in
packages. CCIDs and comments from the original generated element are used. Autogen generates
only those using elements that are found at the same inventory location as the target component or
are found higher up the logical map. To generate using elements located across Systems or
Subsystems, you can use the Autogen Span options. For more information about the Span options,
see Administrating (see page 36).
If you specify the Autogen option on any one of a group of statements, all of those statements are
resolved based on the current inventory contents before any statement is executed. Statements such
as GENERATE ELEMENT * create actions based on the location and options of the Generate action.
During processing, duplicate Generate actions are eliminated, and the NoSource option is enabled for
all the Generate actions built by Autogen.
Autogen improves processing by eliminating duplicate processing of components and reduces the
work that is required of users, who no longer must use the Automated Configuration Manager Query
facility (ACMQ) to create additional Generate actions for element components and run another batch
job to process them.
You can run Autogen in simulation mode, to preview the effects of an Autogen request.
Autogen requires Global Type Sequencing so that the elements that use a component are
generated after all of the components have been processed (for example, macros before source,
source before load modules).
Autogen only acts on components whose Types are listed in the Global Type Sequencing table. If
the component's Type is not listed in the Global Type Sequencing table, the Autogen request is
ignored.
Your site must have purchased and activated the option CA Endevor SCM Automated
Configuration. You can use the Display Site panel to determine if this option is activated (ASCM=Y)
at your site.
04-May-2018 113/1109
CA Endevor® SCM - 17.0
Autogen cannot be specified on actions that are included in a package, because approvers must
see the SCL statements that they are approving.
Autogen and the bypass generate element (GENERATE ELEMENT=N) options are mutually
exclusive.
Note: The Validate action is a more efficient way to validate components. The SCL
statement Validate lets you verify that all components exist and are valid. Valdiate requires
that ACM be enabled at your site. For more information, see Validate Components (see
page 116).
In this example, many changes have gone into production. Many common routines have changed
which, in turn, have affected programs. ACM lets you confirm that all programs are using
components (copybooks, CALLed routines) that are at the right version/level.
By coding:
LIST ELEMENTS *
Instruct ACM to search for all (*) elements as specified by the FROM statement
FROM ENVIRONMENT
Restrict the search to the production stage (STAGE P) of the Personnel system (SYSTEM
PERSONEL), regardless of subsystem and type.
TO DSNAME
04-May-2018 114/1109
CA Endevor® SCM - 17.0
TO DSNAME
Instruct ACM to write out the list of elements which meet the search criteria to the data set BST.
C1DEMO.SRCLIB.
WHERE COMPONENTS = *
Instruct ACM to select each element with a component list in the Personnel system in Stage P.
There are two outputs: an Execution Report and List-generated SCL. You always receive an Execution
Report, but this time ACM produces a larger Execution Report because of the DETAIL REPORT option.
The report information is sorted and sent to the indicated member. All inconsistencies are identified
within the member PVALID.
The second section of the Execution Report details each action generated for the original LIST SCL
statement that meets the WHERE selection criteria. Each action is listed because of the OPTIONS
DETAIL REPORT clause in the SCL. If this option had not been specified, only one action -- LIST
ELEMENT * -- would be generated and, consequently, CA Endevor® SCM would search for matches
that meet the WHERE selection criteria.
SET FROM ENVIRONMENT DEMO SYSTEM PERSONEL SUBSYSTEM EMPMAINT
TYPE COPY STAGE NUMBER 2.
&&ACTION ELEMENT C1CLINK VERSION 01 LEVEL 00.
&&ACTION ELEMENT WSWITCH VERSION 01 LEVEL 00.**DUPLICATE**
04-May-2018 115/1109
CA Endevor® SCM - 17.0
&&ACTION ELEMENT WSWITCH VERSION 01 LEVEL 00.**DUPLICATE**
&&ACTION ELEMENT WSWITCH VERSION 01 LEVEL 01.
SET FROM ENVIRONMENT DEMO SYSTEM PERSONEL SUBSYSTEM EMPMAINT
TYPE INCLUDES STAGE NUMBER 2.
&&ACTION ELEMENT FDPRINT VERSION 01 LEVEL 03.
&&ACTION ELEMENT FDPRINTS VERSION 01 LEVEL 02.
&&ACTION ELEMENT PDSTOP VERSION 01 LEVEL 02.**DUPLICATE**
&&ACTION ELEMENT PDSTOP VERSION 01 LEVEL 03.
SET FROM DSNAME BST.QATEST.LOADLIB2 .
&&ACTION ELEMENT C1CALLER .
&&ACTION ELEMENT C1SUB01 .
&&ACTION ELEMENT C1SUB02 .
By viewing the generated SCL for asterisks (*), you can see that there are two components with
duplicate version/levels. See the Execution Report in Step 2 and find the elements that have the
inconsistent components (noted by arrows).
For example, to find the element using the input component PDSTOP Version 01 Level 02, scan the
Execution Report for all occurrences of that component. Check the list action data to determine
which elements are using the older level of PDSTOP. In this example, the element in question is
C1SUB02.
Validate Components
The SCL statement Validate lets you verify that all components exist and are valid. This feature is
implemented as a batch element action. You can build the SCL statement in foreground and submit it
directly from foreground or schedule it for later execution. The Validate Elements panel is where you
specify the location of the element and indicate what type of validation you want to perform.
1. Allocate a partitioned or sequential data set. This is the data set to which you plan to write
the action request.
3. Specify the data set name in the Request Data Set field. This is the data set to which you want
to write the action requests. This data set must be a partitioned data set or a sequential file,
and must be allocated prior to referencing it on this panel. As an alternative, you can use the
OTHER PARTITIONED OR SEQUENTIAL DATA SET field. Select option 1, BUILD SCL and press
Enter.
The SCL Generate panel opens. This panel allows you to select the type of action request you
want to generate, or to request an element display. The request data set and append
information defined on the Batch Options Menu appear at the bottom of the screen.
5. Enter VE. The element must exist at the location you specify, although you can use full or
partial name masking on all the FROM LOCATION fields.
04-May-2018 116/1109
CA Endevor® SCM - 17.0
Note: The Validate statement can only be performed in batch. For more information about
the SCL statement, see Validate Statement (https://docops.ca.com/display/CE17
/Validate+Statement).
By coding:
FROM ENVIRONMENT
Restrict the search to the production stage (STAGE P) of the ACCTPAY subsystem within the
FINANCE system.
04-May-2018 117/1109
CA Endevor® SCM - 17.0
TO DSNAME
Instruct ACM to write out the list of elements which meet the search criteria for the data set BST.
C1DEMO.SRCLIB.
SET FROM ENVIRONMENT DEMO SYSTEM FINANCE SUBSYSTEM ACCTPAY
TYPE COPY STAGE NUMBER 2.
&&ACTION ELEMENT HEADER1 VERSION 01 LEVEL 00.
&&ACTION ELEMENT PAGING VERSION 01 LEVEL 01.
By viewing the component list from May 1, 2001 at 12:50 p.m., you can see that:
Thus, we see that elements FINAPP01, HEADER1, and PAGING have all been changed since May 1,
2001.
Now, we edit this SCL by coding RETRIEVE and ADD actions as follows:
SET ACTION RETRIEVE
SET TO FILE TMPPDS.
SET OPTIONS COMMENT ‘RETRIEVE FINAPP01’ CCID ‘EMG0195’.
SET FROM ENVIRONMENT DEMO SYSTEM FINANCE SUBSYSTEM ACCTPAY
TYPE COBOL STAGE NUMBER 2 .
&&ACTION ELEMENT FINAPP01 VERSION 01 LEVEL 00
SET FROM ENVIRONMENT DEMO SYSTEM FINANCE SUBSYSTEM ACCTPAY
TYPE COBOL STAGE NUMBER 2 .
&&ACTION ELEMENT HEADER1 VERSION 01 LEVEL 00
&&ACTION ELEMENT PAGING VERSION 01 LEVEL 01 .
CLEAR TO ALL
CLEAR FROM ALL.
SET FROM ENVIRONMENT DEMO SYSTEM FINANCE SUBSYSTEM ACCTPAY
TYPE COBOL STAGE NUMBER 1
&&ACTION ELEMENT FINAPP01 VERSION 01 LEVEL 00 .
SET FROM ENVIRONMENT DEMO SYSTEM FINANCE SUBSYSTEM ACCTPAY
TYPE COBOL STAGE NUMBER 1 .
&&ACTION ELEMENT HEADER1 VERSION 01 LEVEL 00 .
&&ACTION ELEMENT PAGING VERSION 01 LEVEL 01 .
04-May-2018 118/1109
CA Endevor® SCM - 17.0
Note: The ADD action would create levels that eliminate intervening levels (regression). An
alternative would be not to add to the entry stage, but to compile and test in test libraries.
When you finish editing the SCL, resubmit the request for batch processing.
In the following example, we are about to move a CCID from the entry stage to the next mapped
stage. This CCID is an Application System Request (ASR#053010). When moving this CCID, we also
want to move all related components.
The scenario for moving the CCID and its related components from the entry stage to the next
mapped stage involves four steps:
2. Run a batch execution (to generate SCL using the LIST action).
To begin moving CCID ASR#053010 from the entry stage to the next mapped stage, code the SCL as
follows:
LIST ELEMENTS *
FROM ENVIRONMENT DEMO
SYSTEM PERSONEL
SUBSYSTEM *
TYPE *
STAGE D
TO DSNAME ‘BST.C1DEMO.REQDSN’
WHERE CCID EQUALS ‘ASR#053010’
INPUT COMPONENTS EQUAL ‘*’
BUILD WITH COMPONENTS LEVEL ACTION MOVE
OPTIONS MEMBER ‘ASR53010’.
By coding:
LIST ELEMENTS *
Instruct ACM to list all (*) the elements from the PERSONEL system within the DEMO
environment. Specify all (*) subsystems and types, and identify the stage as 'D' (the entry stage).
04-May-2018 119/1109
CA Endevor® SCM - 17.0
TO DSNAME
Instruct ACM to write out the SCL request TO a data set named ‘BST.C1DEMO.REQDSN’.
OPTIONS
Specify that the member for the requested data set, BST.C1DEMO.REQDSN, be named
‘ASR53010’.
In the example, the outcome is a list of all elements for the CCID (ASR#053010) and their related
input components (programs, copybooks, INCLUDE modules).
SET FROM ENVIRONMENT DEMO SYSTEM PERSONNEL SUBSYSTEM EMPMAINT
TYPE COBOL STAGE NUMBER 1.
&&MOVE. ELEMENT C1CALLER VERSION 01 LEVEL 00 .
&&MOVE. ELEMENT C1SUB01 VERSION 01 LEVEL 00 .
&&MOVE. ELEMENT C1SUB02 VERSION 01 LEVEL 00 .
SET FROM ENVIRONMENT DEMO SYSTEM PERSONNEL SUBSYSTEM EMPMAINT
TYPE COPY STAGE NUMBER 1.
&&MOVE. ELEMENT C1CLINK VERSION 01 LEVEL 00 .
&&MOVE. ELEMENT WSWITCH VERSION 01 LEVEL 00 .
SET FROM ENVIRONMENT DEMO SYSTEM PERSONNEL SUBSYSTEM EMPMAINT
TYPE INCLUDES STAGE NUMBER 1.
&&MOVE. ELEMENT FDPRINT VERSION 01 LEVEL 03 .
&&MOVE. ELEMENT FDPRINTS VERSION 01 LEVEL 02 .
&&MOVE. ELEMENT PDSTOP VERSION 01 LEVEL 02 .
SET FROM DSNAME BST.QATEST.LOADLIB1 .
&&MOVE. ELEMENT C1SUB01 .
&&MOVE. ELEMENT C1SUB02 .
These load modules have source inside of CA Endevor® SCM, and that source has been selected by
LIST as noted by elements 2 and 3 in the first SET command. You can now delete this SET statement
and associated MOVE ELEMENT statements.
04-May-2018 120/1109
CA Endevor® SCM - 17.0
CONRELE accepts user syntax from the ENDVRIPT DD statement. After the parsing process is
complete the data is formatted as special component record types and processed with the rest of the
component list. The related data portion is appended to the end of the component list. You are not
required to store the input in CA Endevor® SCM.
You must include the CONRELE utility as a processor step and you must provide the input. Use the
following sample processor to execute CONRELE:
//STEPxx EXEC PGM=CONRELE
//NDVRIPT DD DSN=&user.data.set,DISP=shr
You must use the extended form of the CONWRITE utility to extract component list records.
CONWRITE reads WRITE ELEMENT control statements from the CONWIN DD statement to determine
which component list records to extract.
You can write the component list record to an external data set or you can pass the component list
record to a user specified exit program. The following is sample JCL for using the CONWIN DD
statement to extract a component list with the extended form of CONWRITE:
//WRITE EXEC PGM=CONWRITE
//COMPOUT DD DSN=&user.data.set,DISP=PASS,UNIT=SYSDA,
// SPACE=(TRK,(3,5),RLSE),
// DCB=(RECFM=VB,LRECL=80,BLKSIZE=6160,DSORG=PS)
//CONWIN DD *
WRITE ELEMENT &c1element
FROM ENV &c1envmnt SYSTEM &c1system SUBSYSTEM &c1subsys
TYPE &c1eltype STAGE &c1stgid
TO DDN COMPOUT
OPTION COMPONENT.
/*
04-May-2018 121/1109
CA Endevor® SCM - 17.0
CA Roscoe Interface
Start the Roscoe Interface (see page 122)
Commands and Function Keys (see page 122)
TSO and Roscoe (see page 122)
Name Masking (see page 123)
Display List Processing (see page 123)
3. Select the processing you want to use by typing one of the option numbers in the OPTION
field and pressing ENTER.
PF3 or CLEAR
Ends a panel and returns you to the previous panel.
PF4
Returns you to the Main Menu.
PF7
Scrolls forward through a list or display.
PF8
Scrolls backward through a list or display.
There is no ISPF Library with project, library, and type on each panel. FROM (and TO)
04-May-2018 122/1109
CA Endevor® SCM - 17.0
There is no ISPF Library with project, library, and type on each panel. FROM (and TO)
PARTITIONED OR SEQUENTIAL DATA SET options are provided on the panel, however.
Each screen, where applicable, supports the THRU option for an element. A THRU field is listed on
the panel for each action that provides the option.
The Append and Include JCL settings are saved from session to session, rather than reset to N (the
default) upon entry to CA Endevor® SCM.
When you leave a field blank and the request is generated, an asterisk (*) is returned in that field,
reflecting that an asterisk was entered in this field in the SCL for the request.
The Roscoe Interface is set up to recognize a data set name of ROSCOE and write it out as
DDNAME ROSCOE.
Name Masking
Many of the field descriptions contain references to a name mask. A name mask is represented by an
asterisk, and allows you to specify all names, or all names beginning with a particular series of letters,
to be considered when performing an action.
To use a name mask, simply code an asterisk (*) as the last or only character in any of the eligible
fields (eligibility is noted in each field description). Code only one asterisk; if you enter more than one
asterisk, you receive an error message. Note the following examples:
If you enter the element name ABC* for the Add action, the system adds all elements beginning
with the letters "ABC" (and meeting the rest of the criteria entered).
Similarly, if you enter just an asterisk as the element name for the Add action, the system adds all
elements (provided the remaining criteria is met).
This concept applies to all fields in which you can use a name mask.
04-May-2018 123/1109
CA Endevor® SCM - 17.0
If you select an element display option, you can review detail information about the elements for
which you are specifying the request. These panels include the Summary of Levels panel, the Element
Master panel, the Element Changes panel, the Element Browse panel, and the Element History panel.
An Element Selection List is also available if you leave the ELEMENT field blank or use a name mask.
Because this list is unique to each action, it is illustrated and explained with each action.
Similarly, a Type Selection List and a Processor Group Selection List appear during some actions.
Again, since the lists are unique to an action, they are illustrated and explained with their respective
actions.
Environment
Name of the environment.
Environment Title
Descriptive title for the environment.
Stage 1
Alphanumeric ID and name for the stage.
Stage 2
Alphanumeric ID and name for the stage.
Entry ID
Environment's entry stage ID.
The System Selection List presents the systems defined to the environment specified, and is limited
to those names that match the characters specified in the SYSTEM name mask.
04-May-2018 124/1109
CA Endevor® SCM - 17.0
Selection (untitled)
Select the system you want to use by typing an S in this column, next to the appropriate system.
Environment
Name of the environment you are using.
System
System name.
System Title
Descriptive title for the system.
Selection (untitled)
Select the subsystem you want by typing an S in the column to the left of the appropriate
subsystem.
Environment
Name of the environment you are using.
System
Name of the system being processed.
Subsystem
Subsystem name.
Subsystem Title
Descriptive title for the subsystem.
04-May-2018 125/1109
CA Endevor® SCM - 17.0
CCID
Enter a valid CCID for this action. The CCID you enter here remains as the required CCID until you
change it or until the end of this particular work session.
Comment
Enter a comment for this action. The comment you enter here remains as the required comment
until you change it or until the end of this particular work session.
Getting Started
Contents
3. Select the processing you want to use by typing one of the option numbers in the OPTION
field and pressing ENTER.
PF3 or CLEAR
Ends a panel and returns you to the previous panel.
PF4
Returns you to the Main Menu.
PF7
Scrolls forward through a list or display.
PF8
Scrolls backward through a list or display.
04-May-2018 126/1109
CA Endevor® SCM - 17.0
There is no ISPF Library with project, library, and type on each panel. FROM (and TO)
PARTITIONED OR SEQUENTIAL DATA SET options are provided on the panel, however.
Each screen, where applicable, supports the THRU option for an element. A THRU field is listed on
the panel for each action that provides the option.
The Append and Include JCL settings are saved from session to session, rather than reset to N (the
default) upon entry to CA Endevor® SCM.
When you leave a field blank and the request is generated, an asterisk (*) is returned in that field,
reflecting that an asterisk was entered in this field in the SCL for the request.
The Roscoe Interface is set up to recognize a data set name of ROSCOE and write it out as
DDNAME ROSCOE.
Name Masking
Many of the field descriptions contain references to a name mask. A name mask is represented by an
asterisk, and allows you to specify all names, or all names beginning with a particular series of letters,
to be considered when performing an action.
To use a name mask, simply code an asterisk (*) as the last or only character in any of the eligible
fields (eligibility is noted in each field description). Code only one asterisk; if you enter more than one
asterisk, you receive an error message. Note the following examples:
If you enter the element name ABC* for the Add action, the system adds all elements beginning
with the letters "ABC" (and meeting the rest of the criteria entered).
Similarly, if you enter just an asterisk as the element name for the Add action, the system adds all
elements (provided the remaining criteria is met).
This concept applies to all fields in which you can use a name mask.
04-May-2018 127/1109
CA Endevor® SCM - 17.0
If you select an element display option, you can review detail information about the elements for
which you are specifying the request. These panels include the Summary of Levels panel, the Element
Master panel, the Element Changes panel, the Element Browse panel, and the Element History panel.
An Element Selection List is also available if you leave the ELEMENT field blank or use a name mask.
Because this list is unique to each action, it is illustrated and explained with each action.
Similarly, a Type Selection List and a Processor Group Selection List appear during some actions.
Again, since the lists are unique to an action, they are illustrated and explained with their respective
actions.
Environment
Name of the environment.
Environment Title
Descriptive title for the environment.
Stage 1
Alphanumeric ID and name for the stage.
Stage 2
Alphanumeric ID and name for the stage.
Entry ID
Environment's entry stage ID.
The System Selection List presents the systems defined to the environment specified, and is limited
to those names that match the characters specified in the SYSTEM name mask.
04-May-2018 128/1109
CA Endevor® SCM - 17.0
Selection (untitled)
Select the system you want to use by typing an S in this column, next to the appropriate system.
Environment
Name of the environment you are using.
System
System name.
System Title
Descriptive title for the system.
Selection (untitled)
Select the subsystem you want by typing an S in the column to the left of the appropriate
subsystem.
Environment
Name of the environment you are using.
System
Name of the system being processed.
Subsystem
Subsystem name.
Subsystem Title
Descriptive title for the subsystem.
04-May-2018 129/1109
CA Endevor® SCM - 17.0
CCID
Enter a valid CCID for this action. The CCID you enter here remains as the required CCID until you
change it or until the end of this particular work session.
Comment
Enter a comment for this action. The comment you enter here remains as the required comment
until you change it or until the end of this particular work session.
Once you identify the element and the information you want to display, press ENTER. The panel that
appears next depends on the values in the BYPASS SYS/SBS SEL LIST field.
04-May-2018 130/1109
CA Endevor® SCM - 17.0
Once you have selected the elements for which you want to display information, press Enter. The
interface returns the appropriate display panel either:
Each of these displays, as well as the Display Elements panel, are discussed in detail in subsequent
sections.
If you select elements using selection lists, press PF3 when you are finished reviewing the information
displayed. Alternatively:
From the Element Selection List, you can request any of the element-display options available
from the Display Elements panel, for one or more elements.
From the Summary of Levels panel, you can request the Element Browse, Element Changes, or
Element History panel for a specific level of the element.
Use either of these panels to identify the element and processing option desired. Press ENTER to
continue.
To identify the element you want, specify the environment, system, subsystem, element name, type,
and stage, as requested by the panel. If you identify the element(s) fully on this panel, a panel with
the information you have requested appears when you press Enter. If you do not fully identify the
element(s), processing depends on the value in the BYPASS SYS/SBS SEL list field. The following
section describes Display Element panel fields.
S -- Retrieves a Summary of Levels panel, showing a summary of change history for the element
requested. From this panel you can select a specific level of the element for display, using option
B, C, or H
04-May-2018 131/1109
CA Endevor® SCM - 17.0
M -- Retrieves an Element Master panel, showing Master Control File (MCF) information related
to the element requested.
B -- Retrieves an Element Browse panel, showing all statements in the current level of the
element, and the level at which each statement was inserted.
C -- Retrieves an Element Changes panel, showing all inserts and deletions made to the element
as of the current level.
H -- Retrieves an Element History panel, showing all statements in all levels of the element, from
the base level through the current level. The display shows the level at which each insert/deletion
occurred.
Note: For elements of log delta format, options H and C are not valid, and option B can
only be used on the current (last) level of the element. For elements of image delta
format, H and C are not valid
Environment -- Name of the environment under which the element is defined. Displays initially as
the current environment. Fill in a new name if the element is in another environment.
Element -- Name of the element for which you want to display information.
Stage -- ID of the stage in which the element resides. This must be one of the values shown to the
right of the field (unless you are changing environments).
Where CCID Eq -- A CCID can be specified in this field to limit the selection list to only those
elements whose last CCID is equal to the specified CCID. If omitted, the WHERE CCID EQ field is
not used to limit the selection list.
Where Proc Grp Eq -- A processor group can be specified in this field to limit the selection list to
only those elements to which the processor group has been assigned. If omitted, the WHERE
PROC GRP EQ field is not used to limit the selection list.
Bypass SYS/SBS Sel List -- Indicates whether you want to go directly to the Element Selection List
from the Display Elements panel:
04-May-2018 132/1109
CA Endevor® SCM - 17.0
Use N to provide individual selection lists as required by your entries on this panel.
Environment
Name of the environment.
Environment Title
Descriptive title for the environment.
Stage 1
Alphanumeric ID and name for the stage.
Stage 2
Alphanumeric ID and name for the stage.
Entry ID
Environment's entry stage ID.
04-May-2018 133/1109
CA Endevor® SCM - 17.0
Selection (untitled)
Field used to select the system you want. Place an S in this column, to the left of the appropriate
system name.
Environment
Name of the environment.
System
Name of the system.
System Title
Descriptive title for the system.
Environment
Name of the current environment.
System
Name of the system for the subsystems displayed.
Selection (untitled)
Place an S in this column to the left of the subsystem name you want to select.
04-May-2018 134/1109
CA Endevor® SCM - 17.0
Subsystem
Name of the subsystem.
Subsystem Title
Descriptive title for the subsystem.
The Element Selection List you see depends on the values indicated in the panel fields, as
well as on the panel sequence.
Note: If you do not specify a stage on the Display Elements panel, the Element Selection
List will include the elements in both stages for the environment specified. The stage
identifier appears between the TYPE and the VVLL fields on the panel.
Use the Element Selection List panel to select the elements for which you want more information. Fill
in an option value to the left of each element you want, to indicate the information you want ( M, S,
B, C , or H); then press Enter. To view component list information with the CA Endevor SCM
Automated Configuration option, append an "X" to options S, B, C, or H.
If you do not want to request more information, press PF3 when you are finished reviewing the
information shown. The following section describes the panel fields.
Environment
Name of the current environment.
System
Name of the system under which the element is defined.
Subsystem
Name of the subsystem under which the element is defined.
Stg
ID of the stage for the element.
04-May-2018 135/1109
CA Endevor® SCM - 17.0
Element Name
Name of the element.
Type
Name of the element type.
NS
Indicates whether the element is a sourceless element. A value of Y indicates it is sourceless and
the display options S, B, C, and H cannot be used. If blank, the element is not sourceless.
VVLL
Current version/level for the element, within this stage.
Current Date
Level date for the current level. Format ddMMMyy.
Generate Date
Generate processor date. This field is blank if the element has not yet been processed. See the
proc rc field on the Element Master Info panel for information about maxrc and Restore/Transfer
as they relate to this date. Format ddMMMyy.
RC PROC
Processor return code. Stored for the element on the Master Control File.
NDVR RC
CA Endevor® SCM return code. Stored for the element on the Master Control File.
Last Action
Last action recorded for the element.
Note: This panel can also be requested during footprint display processing and functions
identically as described here. For more information, see Displaying Footprint Information
(see page 148).
The top part of this panel displays identification information about the element. The bottom part
provides a summary of the element-level (source-level) history, listing each level of the element in
the stage requested and information appropriate to that level.
Use this panel to view the summary information and, optionally, to request additional information for
one or more of the levels listed at the bottom of the panel. To request further information, type B, C
or H (as described above for the Display Elements panel) to the left of the levels about which you
want information. Then press ENTER.
04-May-2018 136/1109
CA Endevor® SCM - 17.0
If you do not want to request additional information, press PF3 when you are finished with this panel.
The following Identification Fields specify the CA Endevor® SCM location of the element. All fields are
display-only.
Environment
Current environment.
System
Name of the system under which the element is defined.
Subsystem
Name of the subsystem under which the element is defined.
Element
Name of the element for which summary information is displayed.
Type
Name of the type for the element.
Stage
ID of the stage for which element information is shown.
The following Source Level Information Fields display summary information about all levels of this
element. All fields except the SELECTION field are display-only.
VVLL
Version/level for which information is shown to the right (in VVLL format).
User
Level user ID.
Date
Level date (in ddMMMyy format).
Time
Level time (in hh:mm format).
Stmts
Number of statements in this level.
Inserts
Number of statements inserted for the level.
Deletes
Number of statements deleted for the level.
04-May-2018 137/1109
CA Endevor® SCM - 17.0
Sync
Indicates whether this level is a sync level.
Display Elements panel when you request option M and uniquely qualify the element you want.
Library Selection List panel. For more information, see Displaying Footprint Information (see page
148).
Use the Element Master panels to review the information shown, and then press PF3 when you are
finished.
To view the second Element Master panel, press ENTER. Press PF3 when you are finished.
Identification Fields
The Identification Fields identify the element for which the Master Control File information appears.
Element
Name of the element.
Environment (Env)
Environment in which the element is defined.
System (Sys)
System in which the element is defined.
Subsystem (Sub)
Subsystem in which the element is defined.
Type
Type to which the element has been assigned.
Stage (Stg)
Stage in which this element resides.
Version/level (VVLL)
Version and level of this element.
Last Action
Last action performed against this element.
Description
Description of the last action. This information comes from the comment associated with the last
action.
04-May-2018 138/1109
CA Endevor® SCM - 17.0
Signout ID
User ID of the person to whom the element is signed out.
Package ID (Source)
ID of the package that last affected the source form of this element. (Applies only to package
processing.)
Package ID (Output)
ID of the package that created the current generated (or output) form of this element. (Applies
only to package processing.)
Note: Backing out and backing in packages can affect the value that appears in this field.
For example, assume this element is part of two packages, PKG1 and PKG2. The following
table shows the effect of four activities involving these packages on the PKG ID (SOURCE)
and the PKG ID (OUTPUT) fields.
Backing out PKG2 caused the output form of this element to revert to its state in PKG1. Subsequently
backing in PKG2 then caused the output form of this element to revert to its state in PKG2.
Keep in mind, however, that package actions (package backing in/out) are not available in the
interface. These fields may indicate the above conditions created through CA Endevor® SCM.
Userid
User ID of person who requested the action.
Date/Time
Date and time of the action.
CCID
CCID specified for the action.
04-May-2018 139/1109
CA Endevor® SCM - 17.0
Comment
Comment specified for the action.
Action
Name of the CA Endevor® SCM action that was performed.
Processor
Name of the processor invoked by the action.
Note: For a description of the USERID, DATE/TIME, CCID, and Comment fields, see Last
Element Modification Fields (see page 139).
DELTA FMT
Indicates whether the element changes are stored in forward (F) or reverse (R) delta format.
Generate Fields
These fields provide information about the last action run against this element that caused output to
be generated.
Note: For a description of the USERID, DATE/TIME, CCID, and Comment fields, see Last
04-May-2018 140/1109
CA Endevor® SCM - 17.0
Note: For a description of the USERID, DATE/TIME, CCID, and Comment fields, see Last
Element Modification Fields (see page 139).
1. Press ENTER.
The second Element Master Panel appears.
Retrieve Fields
These fields provide information only when the last action performed against this element was
Retrieve. Otherwise the fields will be empty.
Note: For a description of the USERID, DATE/TIME, CCID, and Comment fields, see Last Element
Modification Fields (see page 139).
RETRIEVE TO DSN
Identifies the target data set for the Retrieve action.
Base Fields
These fields provide information about the base level of this element. They show the user ID of the
person who created the base level, the date and time that the base level was created, and the
comment that was entered for the Add action that created the base level.
Note: For a description of these fields, see Identification Fields (see page 138).
Display Elements panel when you request option B and uniquely qualify the element you want.
Library Selection List panel. For more information, see Displaying Footprint Information (see page
148).
04-May-2018 141/1109
CA Endevor® SCM - 17.0
Note: Sourceless elements cannot be browsed. For elements of log delta format, only the
current (last) level of the element can be browsed.
The Element Browse panel displays all the statements in the level of the element requested, and
identifies the level at which each statement was first inserted. If the panel is returned from the
Display Elements panel or the Library Selection List, the level requested is assumed to be the current
level. To browse a previous level of the element, first request the Summary of Levels panel, then
specify the level you want (and option B) using that panel.
Review the information shown, then press PF3 when you are finished.
VVLL
Number that identifies the level of the element described on this line (in VVLL format).
User
Level user ID.
Date
Level date (in ddMMMyy format).
Time
Level time (in hh:mm format).
Stmts
Number of statements in this level.
CCID
Level change control ID.
Comment
Level comment.
GENERATED
Information about the last run of the generate processor for any level of the element. This data
includes the ID of the user who requested the associated action, the date and time of the
Generate action, the number of statements processed, and CCID and comments associated with
the action, if any.
If the generate processor has not been run for the element, this line reads: THIS ELEMENT HAS
NOT BEEN PROCESSED.
If the element has been restored (or transferred to CA Endevor® SCM from an archive data set),
but has not yet been generated, this line reads: PROCESS?? (instead of GENERATED). This
indicates that the status of the generate processor information taken from the archive data set
during the Restore (or Transfer) may be out of sync with the current processor output, if any. For
04-May-2018 142/1109
CA Endevor® SCM - 17.0
during the Restore (or Transfer) may be out of sync with the current processor output, if any. For
example, if you deleted the element at the time it was last archived, the processor output was
deleted as well. The processor information in the archive data set for the element remained,
however, and was restored/transferred along with the other information for the element.
RETRIEVED
Information to describe the last time any level of the element was retrieved. This data includes
the ID of the user responsible, date and time of the Retrieve action, and any comments
associated with the processing.
If an element has been moved, signed in (using the Signin action), restored, or transferred to CA
Endevor® SCM from an archive data set since the last Retrieve, any information related to the last
Retrieve is blanked out and is not reflected here.
Element Statements
This area lists each statement in the element as of the level requested. For each statement, it
identifies the level at which the statement was inserted (and deleted, as appropriate). A percent (%)
sign marks those statements that were inserted as of the level displayed.
Display Elements panel when you request option C and uniquely qualify the element you want.
Note: You cannot browse element changes for sourceless elements or elements of log or
image delta format.
The Element Changes panel displays all inserts and deletions made to the element for the level
requested (that is, between the level immediately preceding and this level). If the panel is returned
from the Display Elements panel or the Library Selection List, the level requested is assumed to be
the current level. To view the changes to a previous level of the element, first request the Summary
of Levels panel, then specify the level you want (and option C) using that panel.
Review the information shown, then press PF3 when you are finished.
04-May-2018 143/1109
CA Endevor® SCM - 17.0
Environment
Name of the environment in which the element is defined.
System
Name of the system under which the element is defined.
Subsystem
Name of the subsystem under which the element is defined.
Element
Name of the element.
Type
Element type.
Stage
ID of the stage in which the element resides.
VVLL
Number that identifies the element level described on this line (in VVLL format).
User
Level user ID.
Date
Level date (in ddMMMyy format).
Time
Level time (in hh:mm format).
Stmts
Number of statements in this level.
CCID
Level change control ID.
Comment
Level comment.
04-May-2018 144/1109
CA Endevor® SCM - 17.0
GENERATED
Information to describe the last time the generate processor was run for any level of the element.
This data includes the ID of the user who requested the associated action, the date and time of
the Generate action, the number of statements processed, and CCID and comments associated
with the action, if any.
If the generate processor has not been run for the element, this line reads: THIS ELEMENT HAS
NOT BEEN PROCESSED.
If the element has been restored (or transferred to CA Endevor® SCM from an archive data set),
but has not yet been generated, this prompt reads: PROCESS?? (instead of GENERATED). This
indicates that the status of the generate processor information taken from the archive data set
during the Restore (or Transfer) may be out of sync with the current processor output, if any. For
example, if you deleted the element at the time it was last archived, the processor output would
have been deleted as well. The processor information in the archive data set for the element
remained, however, and was restored/transferred along with the other information for the
element.
RETRIEVED
Information to describe the last time any level of the element was retrieved. This data includes
the ID of the user responsible, date and time of the Retrieve action, and any comments
associated with the processing. If an element has been moved, signed in (using the Signin action),
restored, or transferred to CA Endevor® SCM from an archive data set since the last Retrieve, any
information related to the last Retrieve is blanked out and is not reflected here.
Element Statements
This area lists each statement in the element that changed as of the requested level. For statements
that were deleted, this area indicates the level at which the previous form of the statement was
inserted. These fields are display-only.
Display Elements panel when you request option H and uniquely qualify the element you want.
Library Selection List panel. For more information, see Displaying Footprint Information (see page
148).
04-May-2018 145/1109
CA Endevor® SCM - 17.0
Note: You cannot browse element history for sourceless elements or elements of log or
image delta format.
The Element History panel displays all statements that ever existed in the element, from the base
level through the level requested. For each statement, the display identifies the level at which the
statement was first inserted and the level at which it was deleted (using an Update action), if
appropriate.
If the panel is returned from the Display Elements panel or the Library Selection List, the level
requested is assumed to be the current level. To view the history of the element as of a previous
level, first request the Summary of Levels panel, then specify the level you want (and option H) using
that panel.
Review the information shown, then press PF3 when you are finished.
Environment
Name of the environment in which the element is defined.
System
Name of the system under which the element is defined.
Subsystem
Name of the subsystem under which the element is defined.
Element
Name of the element.
Type
Element type.
Stage
ID of the stage in which the element resides.
VVLL
Number that identifies the element level described on this line (in VVLL format).
User
Level user ID.
Date
04-May-2018 146/1109
CA Endevor® SCM - 17.0
Date
Level date (in ddMMMyy format).
Time
Level time (in hh:mm format).
Stmts
Number of statements in this level.
CCID
Level change control ID.
Comment
Level comment.
GENERATED
Information to describe the last time the generate processor was run for any level of the element.
This data includes the ID of the user who requested the associated action, the date and time of
the Generate action, the number of statements processed, and CCID and comments associated
with the action, if any.
If the generate processor has not been run for the element, this line reads: THIS ELEMENT HAS
NOT BEEN PROCESSED.
If the element has been restored (or transferred to CA Endevor® SCM from an archive data set),
but has not yet been generated, this prompt reads: PROCESS?? (instead of GENERATED). This
indicates that the status of the generate processor information taken from the archive data set
during the Restore (or Transfer) may be out of sync with the current processor output, if any. For
example, if you deleted the element at the time it was last archived, the processor output would
have been deleted as well. The processor information in the archive data set for the element
remained, however, and was restored/transferred along with the other information for the
element.
RETRIEVED
Information to describe the last time any level of the element was retrieved. This data includes
the ID of the user responsible, date and time of the Retrieve action, and any comments
associated with the processing. If an element has been moved, signed in (using the Signin action),
restored, or transferred to CA Endevor® SCM from an archive data set since the last Retrieve, any
information related to the last Retrieve is blanked out and is not reflected here.
Element Statements
This area lists each statement in the element that changed as of the requested level. For statements
that were deleted, this area indicates the level at which the previous form of the statement was
inserted. These fields are display-only.
04-May-2018 147/1109
CA Endevor® SCM - 17.0
A footprint includes the following information related to the associated element, in encrypted
format: site ID, environment name, stage number, system name, subsystem name, element name,
element type, element version/level, and the date and time the footprint was assigned.
Footprints are recorded automatically in the CA Endevor® SCM libraries during action processing.
Depending on the type of data set used for the library, footprints are stored as follows: for a PDS, in
the user data area of the directory; for CA Librarian, as a history record; for CA Panvalet, as a
COMMENT field. Through processors, footprints can also be added to output source, object, and load-
module data sets for an element, to associate those data sets with the element. In this case,
footprints are stored as described above, with the exception of load-module data sets. In load-
module data sets, the footprint is stored separately for each CSECT, in the user IDR record for the
load module.
Option 2 on the Roscoe Interface Primary Options Menu allows you to access CA Endevor® SCM
footprints stored in PDS, CA Librarian, or CA Panvalet libraries. Specifically, you can:
Display a list of members in a library, including the footprint information for each nonload
member (for those members that have been footprinted).
Display a list of CSECTs for a specific load member, including the footprint information for each
CSECT.
Request a browse panel for a nonload member in an output or listing library, including the source
output library, generate processor output library, or move processor output library. In order to
request the browse, the member in the output or listing library must be footprinted.
Request any of the element displays for a particular member or CSECT. These are the Summary of
Levels panel, Element Browse panel, Element History panel, Element Changes panel, and the
Element Master Info panel. If the element does not exist at the location defined by the footprint,
the request is executed against the first element located higher up in the map. This option is only
available for members/CSECTs that are footprinted.
Note: You cannot display a footprint in a member that resides in a Roscoe library or in the
Roscoe workspace (AWS).
04-May-2018 148/1109
CA Endevor® SCM - 17.0
OPTION
Specify the information you want to see. This field can contain the following values:
Blank
Displays a Library Selection List of members in the specified library, including the footprint
information for each nonload member, if available. This panel does not include footprint
information for load library members, because there is a separate footprint for each CSECT.
The MEMBER and THRU MEMBER fields can be inserted, optionally, to define the range of
members you want listed. The interface returns the Library Selection List panel, showing all
members in the library (within the range requested, if applicable).
I
Displays footprint information for a specific load module. Before selecting this option, make
sure you identify the library and member in which the load module is stored. The interface
returns the CA Endevor® SCM Load Module IDR Display panel for the member selected,
showing the footprint for each (footprinted) CSECT. Any CSECTs that are not footprinted
appear in the list, with the footprint area blank.
L
Displays the contents of a specific nonload library member. In order to use this option, the
member must be footprinted. Before selecting option L, make sure you identify the library
and member you want to display.
The interface returns a browse panel showing the member requested. Press PF3 when you are
finished with the browse panel.
Thru Member
Applicable when the OPTION field is blank. Name that defines the last member in the range to
be listed. You can use a name mask to specify the MEMBER name or the THRU MEMBER
name.
On the Library Selection List, the library displayed is identified under the panel title:
04-May-2018 149/1109
CA Endevor® SCM - 17.0
LIBRARY: library-name
You can select one or more members for additional information from the Library Selection List. Place
the appropriate character to the left of each member you want and press Enter. You can request the
following displays: the Load Module IDR Display (I), a browse display (L), or any of the standard
element displays (S, B, H, C, or M).
Selection (untitled)
Use this field to select a member for additional information. Select any number of members for
additional information by placing the appropriate character in this column. Except for option I,
the footprint information must be displayed for a member in order to request one of these
displays.
I
CA Endevor® SCM Load Module IDR Display, showing the footprint for each (footprinted)
CSECT.
L
Browse panel showing the contents of the library member.
S, B, H, C, M
One of the reports described earlier in this section. These are the Summary of Levels (S) panel,
the Element Browse (B) panel, the Element History (H) panel, the Element Changes (C) panel,
or the Element Master Info (M) panel. You cannot issue S,B,H,or C against a sourceless
element. If you do, you will receive an error. For elements of log delta format, options H and C
are not valid and option B can only be used on the current (last) level of the element. For
elements of image delta format, H and C are not valid.
Member
The member field displays the name of the library member for which footprint information is
provided.
Footprint
Display-only. These fields show information stored in the footprint for source, object, and
processor output members.
System
Name of the system under which the element is defined.
Subsystem
Name of the subsystem under which the element is defined.
Element
Name of the element that corresponds to the member.
Type
Name of the element type.
S
Stage in which the element was processed to create this member.
VVLL
04-May-2018 150/1109
CA Endevor® SCM - 17.0
VVLL
Version/level of the element processed to create this member (VVLL).
Date
Date the member was footprinted (ddMMMyy).
Time
Time the member was footprinted (hh:mm).
LD
An “LD” appears in this field to show that this footprint was created by the CA Endevor® SCM
load utility. Load utility footprints cannot be used to verify element integrity. They indicate
only the location to which the element was loaded, and the date and time the load took place.
The library and member for which the information is displayed are identified under the panel title:
LIBRARY: library-name
MEMBER: member-name
From this panel, either press PF3 to return to the previous display or fill in a character to the left of a
specific footprinted CSECT to request an element display. The following list describes the panel fields.
Selection (untitled)
Use this field to select a CSECT for additional information. Select any number of CSECTs by placing
the appropriate character in this column. You can enter:
S, B, H, C, M
Enter a value to display the Summary of Levels (S) panel, the Element Browse (B) panel, the
Element History (H) panel, the Element Changes (C) panel, or the Element Master Info (M) panel.
You cannot issue S,B,H,or C against a sourceless element. If you do, you will receive an error. For
elements of log delta format, options H and C are not valid, and option B can only be used on the
current (last) level of the element. For elements of image delta format, H and C are not valid.
CSECT
Displays the name of the CSECT for which footprint information is shown. If no information is
displayed, the CSECT has not been footprinted.
Footprint
Display-only. These fields show information stored in the CSECT's footprints.
System
Name of the system under which the corresponding element is defined.
Subsystem
Name of the subsystem under which the element is defined.
Element
Name of the CA Endevor® SCM element that corresponds to the CSECT.
Type
04-May-2018 151/1109
CA Endevor® SCM - 17.0
Type
Name of the element type.
S
ID of the stage in which the element was processed to create this CSECT.
VVLL
Version/level of the element processed to create this CSECT (VVLL).
Date
Date the CSECT was footprinted (ddMMMyy).
Time
LD
An “LD” appears in this field to show that this footprint was created by the CA Endevor® SCM load
utility. Load utility footprints cannot be used to verify element integrity. They indicate only the
location to which the element was loaded, and the date and time the load took place.
You access the Roscoe Interface Foreground Retrieve Panel by selecting the RETRIEVE option (4) from
the Roscoe Interface Primary Options Menu.
Note: Be careful when retrieving more than one element at a time. If you perform multiple
retrieves, you could exceed your AWS line limit.
The Roscoe Interface Foreground Retrieve Panel has the following fields:
Option
Use this field to specify the processing you wish to perform.
04-May-2018 152/1109
CA Endevor® SCM - 17.0
Blank
Display a selection list, optionally restricted according to any specifications provided
(environment, system name, etc.).
R
Retrieve the specified element to a user library.
S
Display the Summary of Levels panel. You can use this panel to retrieve a prior level. You can
only retrieve the current (last) level for elements of log delta format.
M, B, C, H
Display one of the following element information panels: Element Master Info (M), Element
Browse (B), Element Changes (C), or Element History (H).
Note: You cannot issue the R action or the B, C, H, or S display options against sourceless
elements. If you do, you will receive an error. For elements of log delta format, options H
and C are not valid, and option B can only be used on the current (last) level of the
element. For elements of image delta format, H and C are not valid.
From Location
Enter information defining the element being retrieved.
Environment
Name of the current environment. Enter a different name to retrieve an element from
another environment.
System
Name of the system under which the element is defined. You can use a name mask to indicate
that all systems, or only those matching the characters specified, be considered in this
request.
Subsystem
Name of the subsystem under which the element is defined. You can use a name mask to
indicate that all subsystems, or only those matching the characters specified, be considered in
this request.
Element
The name of the element (up to 10 characters) to be retrieved. If the TO DATA SET is a library,
you can leave this field blank; the member name in that library automatically becomes the
element name. You also can use a name mask to indicate that all elements, or only those
matching the characters specified, be considered in this request.
Element names can include only the following characters: A-Z, 0-9, @, #, and $
Type
The element type, such as COBOL, COPYLIB, etc. You can use a name mask to indicate that all
types, or only those matching the characters specified, be considered in this request.
04-May-2018 153/1109
CA Endevor® SCM - 17.0
Stage
Enter the ID of the stage from which you want to retrieve the element. Use one of the IDs
listed to the right of this field. You also can use a name mask with this field.
Comment
Enter any comments describing this request. Depending upon the system specified for the
request, comments may be required.
To Roscoe Library
Specify a member name in this field if you want the Retrieve action to create a member with that
name.
Member
Enter the desired Roscoe Library member name. If an element list is generated, the Roscoe
member name field is ignored and the element name or the RENAME value is used.
Action
These options provide additional information for the Retrieve request.
CCID
Specify a CCID to be associated with the element when it is retrieved.
Expand Includes
This option allows you to expand ++INCLUDE statements when the element is retrieved. Enter
Y to expand INCLUDE statements. Enter N to indicate that INCLUDE statements should not be
expanded. This is the default value.
No Signout
This option applies only if signin/signout is in effect for the system. NO SIGNOUT allows you to
retrieve the element without signing it out to your user ID. This option enables another user
to retrieve the element at the same time you are working with it. Similarly, you can retrieve a
copy of an element currently in use by another user if that user has specified the NO SIGNOUT
option. Enter Y to retrieve the element but not sign it out to your user ID. Enter N to retrieve
the element and sign it out to your user ID. This is the default value.
Override Signout
This option applies only if the element to be retrieved is currently signed out. Enter Y to
indicate that the element can be processed, even if it is not signed out to you. CA Endevor®
SCM signs the element out to you if you specify this option. Enter N to indicate that
processing is not allowed unless the element is signed out. This is the default value.
Replace Member
This option applies only if the to data set is a library. If you retrieve an element to a library,
the system checks whether that element (member) currently resides in the library. If it does,
the request normally is rejected. The REPLACE MEMBER option, however, allows you to
replace a member currently in the library with the retrieved element. Enter Y to replace the
member in the library. Enter N to reject the request if the member currently resides in the
library. This is the default value.
List
These options allow you to specify the information you want to list.
Display List
04-May-2018 154/1109
CA Endevor® SCM - 17.0
Display List
This option is always set to Y.
Where CCID EQ
List only elements that match the specified CCID
Select one or more elements to be retrieved, by placing an R to the left of each element you
want, and/or
Request a detailed element display for one or more elements, by placing S, M, B, C, or H to the
left of each element name.
Note: You cannot issue the R action or the B, C, H, or S display options against sourceless
elements. If you do, you will receive an error. For elements of log delta format, options H
and C are not valid, and option B can only be used on the current (last) level of the
element. For elements of image delta format, H and C are not valid.
When you press Enter, the interface processes the requested elements and returns the panel with
appropriate messages.
From
Indicates the environment, system, and subsystem for the listed elements.
Element
Display-only. Name of the element.
Stg
ID of the stage in which the element resides.
Type
Name of the type associated with the element.
NS
04-May-2018 155/1109
CA Endevor® SCM - 17.0
NS
Indicates whether the element is a sourceless element. A value of Y indicates it is sourceless. If
blank, the element is not sourceless.
VVLL
The current version/level for the element, at the stage shown.
A newname column appears on this panel. The user may enter a new member name here. If not, the
element name will be the default.
Also, the panel's message area is at the same location as the newname. After the element is
retrieved, *RETRIEVED will be displayed.
Use the Batch Option Menu to select the type of processing you want to use. Additional information
may be required, depending on the processing you choose. The sections that follow describe the
requirements for each option.
To make a selection from the Batch Options Menu, enter the option number in the OPTION field of
the display and press Enter.
04-May-2018 156/1109
CA Endevor® SCM - 17.0
1 BUILD SCL
Create action requests and place them in a request data set. When you select this option, you
must enter additional information on the panel; this information is described later in this section.
2 EDIT
Edit a request data set, either to change existing requests or add new requests.
3 SUBMIT
Submit a job that executes the action requests in batch. Before submitting the job, you can use
option 5 to provide any additional JCL that should be included with this job.
4 VALIDATE
This option is not available with CA Endevor SCM CA Roscoe Interface 3.6 or later.
5 BUILD JCL
Define JCL (generally DD statements) to include with the JCL submitted with option 3.
Build SCL
Use option 1, BUILD SCL, to generate action requests and place them in a request data set.
The fields in the Batch Options Menu panel are described as follows:
DSNAME
Defines the appropriate data set name.
Note: If you prefer to create SCL requests within your CA Roscoe IE workspace (AWS), you
can enter the keyword ROSCOE, and a member name. You can place the member name in
brackets immediately following the keyword, or in the MEMBER field.
Member
Defines the name of the member in which you want to place your action requests.
Append
Specifies whether you want to add the new requests to the end of an existing data set (enter Y) or
write over any existing information in the data set (enter N). This field is required with the BUILD
SCL option.
Include JCL
Specifies whether you want to include JCL. You do not need to fill in this field when using the
BUILD SCL option.
04-May-2018 157/1109
CA Endevor® SCM - 17.0
Press ENTER after you fill in all necessary information. The SCL Generation panel returns.
To request the action you want, fill in the option number that corresponds to the action type and
press Enter. The action performed by each option is described next:
1 Display
Displays element information before writing action requests for the element.
2 ADD/UPDATE
Adds or updates an element.
3 RETRIEVE
Copies an element to a user data set.
4 GENERATE
Generates an element.
5 MOVE
Moves an element from one map location to another.
6 DELETE
Removes an element and/or element component lists from either stage.
7 PRINT Element
Prints any of several detailed element reports showing element source, the history of the
element, changes made to the element, summary of levels for the element, or Master Control File
information about the element.
8 SIGNIN
Removes signout IDs from elements.
9 TRANSFER
Moves an element from a map location to a location not on the map.
10 PRINT Member
Prints or browses footprinted members from a library.
11 LIST Element
Lists elements from the Master Control File, where the list takes the form of action requests.
04-May-2018 158/1109
CA Endevor® SCM - 17.0
12 LIST Member
Lists or browses footprinted members from a library. Again, the list takes the form of action
requests.
13 ARCHIVE
Writes the current version of an element to a sequential file (known as an archive data set),
generally deleting it following the ARCHIVE.
After pressing ENTER, the action panel for the selected option is returned.
Note: For more information about display element processing, see Displaying Element
Information in the Foreground (see page 130).
Add an element to the environment's entry stage for the first time.
Add an element to stage 1 (when it is the entry stage), for the first time, that currently resides in
Stage 2.
Add an element to the entry stage of the environment after it has been removed from that stage
by a Move, Delete, Transfer, or Archive action.
Update an element in the entry stage, creating a new level of the element.
Option
Indicates the processing you wish to perform. The following options are available:
Blank
Displays a list of members in the source library. You can select one or more members to add
or update.
A
Adds an element, either for the first time or after the prior version was deleted by a Delete,
Move, Archive or Transfer action. Note that you can add an element only to the entry stage.
04-May-2018 159/1109
CA Endevor® SCM - 17.0
U
Updates an element in the entry stage to create a new level of the element.
To Location
Enter information defining the element being added or updated. The following options are
available:
Environment
Name of the current environment. Enter a different name to add or update an element in
another environment.
System
Name of the system under which the element is (to be) defined.
Subsystem
Name of the subsystem under which the element is (to be) defined.
Element
The name of the element (up to 10 characters) to be added or updated. If the from data set is
a library, you can leave this field blank; the member name in that library automatically
becomes the element name. You also can use a name mask to indicate that all elements, or
only those matching the characters specified, should be considered in this request.
Element names can include only the following characters: A-Z, 0-9, @, #, and $
Type
The element type, such as COBOL, COPYLIB, etc. This is a required field for an Add or Update
action.
Action
These options provide additional information for the request. The following options are available:
Comment
Enter any comments describing this request. Depending upon the system specified for this
request, comments may be required.
CCID
You can enter a CCID (up to 12 characters) to further define the element. Depending upon the
system specified for this request, a CCID may be required.
04-May-2018 160/1109
CA Endevor® SCM - 17.0
Note: You cannot use this option to delete a member from the CA Roscoe IE library.
New Version
This option applies to an Add action only. By default, the element is assigned a version
number of 1 if it is a new element, or the Stage 2 version number if the element currently
exists in Stage 2. You can assign a different version number, however, by entering a number
from 1 to 99 in this field.
Leave this field blank to apply the appropriate default value.
Override Signout
This option applies when adding an element currently in Stage 2 or when updating an element
with signin/signout in effect.
Enter Y to indicate that the element can be added or updated, even if it is not signed out
to you. CA Endevor® SCM signs the element out to you if you specify this option.
Enter N to indicate that processing is not allowed unless the element is signed out to you.
This is the default value.
Processor Group
This is the name of the processor group to be used. If you leave this field blank and are adding
a new element, the system uses the default processor group for the element type. If you leave
this field blank and are adding an existing element or updating an element, the system
defaults to the processor group last used for this element. You can also type a processor
group name in this field or a name mask to access a list of processor groups from which to
select.
Update if Present
This option applies to an Add action only. It allows you to add the element, even if it currently
exists in the entry stage, by treating the action as an Update action.
Enter Y to indicate that the element should be added even if it already exists in the entry
stage.
Enter N to indicate that the element should not be added to the entry stage if it currently
exists there. This is the default.
Member
Enter the appropriate member name; you can enter either the full name or use a name mask.
If you leave this field blank, the member name defaults to the element name.
04-May-2018 161/1109
CA Endevor® SCM - 17.0
Thru Member
Use this field to specify a range of members in the data set. The member name entered here
indicates the last member in the range, with the name specified in the MEMBER field
considered as the first name in the range. You can enter either a full member name or use a
name mask.
As an alternative, you can add a member from a CA Roscoe IE data set. The interface:
Builds the SCL for the request as: From DDNAME ROSCOE.
Appends an IEBUPDTE step to the beginning of the skeleton JCL to transfer the CA Roscoe IE
member to a temporary data set. This temporary data set is then passed to a CA Endevor® SCM
step under DDNAME ROSCOE.
List Options:
You leave both the ELEMENT and MEMBER fields blank or you use a name mask in either field.
The Member Selection List displays all the members in the source library (which includes the Roscoe
library), optionally restricted according to any name mask and/or THRU MEMBER specified on the Add
/Update Elements panel.
The FROM and TO information for the request are displayed at the top of the panel, above the
member listing. The rest of the panel presents the members in the FROM data set.
Select one or more members to be added, by placing an A to the left of each member you want,
and/or
Select one or more members to be updated, by placing a U to the left of each member you want.
The TYPE, COMMENT, and NEW VERSION fields are initially filled in for each member, according to
the information provided on the Add/Update Elements panel. You can override the information in
these fields before you select a member(s) for processing. You can also provide the element name, if
it is different than the member name.
When you press Enter, the Roscoe Interface builds SCL for the Add/Update action, and then returns
the panel with an appropriate message next to each member selected.
04-May-2018 162/1109
CA Endevor® SCM - 17.0
From
Display-only. Indicates the FROM data set for the Add/Update request, as specified on the Add
/Update Elements panel.
To
Display-only. Indicates the environment, system, subsystem, and stage under which the element
is being added or updated.
Member
Display only. This is the name of the member(s) in the from data set.
Element
Name of the element (1-10 characters) being added or updated from the corresponding member.
If you leave this field blank, the element name defaults to the member name.
If you are entering a new element, the name can include only the following characters: A-Z, 0-9,
@, #, and $.
This field is also used to display the message “*WRITTEN.”
Type
Type associated with the element to be added. This field is required; you can either use the
existing data or enter a new type. You can add members to multiple types using one panel.
Comment
Comments describing the action requested. Depending on the system specified, comments may
be required. You can either use the existing comment or enter a different one.
New Version
Applicable for an Add action only. This is the version number (vv) under which the element is
being added. If you leave this field blank, the version number defaults to 01, if this is a new
element, or to the Stage 2 version number, if the element currently exists in Stage 2. You can use
a different version number if you want, from 01-99.
Select the type you want by entering an S to the left of the type name. Then press Enter.
Environment
04-May-2018 163/1109
CA Endevor® SCM - 17.0
Environment
Name of the environment you are using.
System
Name of the system under which the type is defined.
Stage
ID of the stage under which the type is defined.
Type
Name of the type.
Type Description
Description of the type.
Environment
Name of the environment you are using.
System
Name of the system for which the processor groups are listed.
Stage
Name of the stage for which the processor groups are listed.
Type
Name of the type to which the processor group(s) applies.
Processor Group
Name of the processor group.
04-May-2018 164/1109
CA Endevor® SCM - 17.0
Retrieving Elements
The Retrieve action copies an element from CA Endevor® SCM to a user data set. Use the Retrieve
Elements panel to identify the element being retrieved. Enter information in the following fields. You
can retrieve a sourceless element in batch mode. CA Endevor® SCM will use the source from the next
sourced element up the map providing that the last level timestamps between the sourceless and
sourced elements are the same.
Note: Be careful when retrieving more than one element at a time. If you perform multiple
retrieves, you could exceed your AWS line limit.
Option
Use this field to specify the processing you wish to perform. The following options are available:
Blank
Display a selection list, optionally restricted according to any specifications provided
(environment, system name, etc.).
R
Retrieve the specified element to a user library.
S
Display the Summary of Levels panel. You can use this panel to retrieve a prior level. This
command is not valid when used against a sourceless element. For elements of log delta
format, you can only retrieve the current (last) level.
M, B, C, H
Display one of the following element information panels: Element Master Info (M), Element
Browse (B), Element Changes (C), or Element History (H). The B, C, and H display options are
not valid when used against sourceless elements. For elements of log delta format, options H
and C are not valid, and option B can only be used on the current (last) level of the element.
For elements of image delta format, H and C are not valid.
From Location
Enter information defining the element being retrieved. The following options are available:
Environment
Name of the current environment. Enter a different name to retrieve an element from
another environment.
04-May-2018 165/1109
CA Endevor® SCM - 17.0
System
Name of the system under which the element is defined. You can use a name mask to indicate
that all systems, or only those matching the characters specified, be considered in this
request.
Subsystem
Name of the subsystem under which the element is defined. You can use a name mask to
indicate that all subsystems, or only those matching the characters specified, be considered in
this request.
Element
The name of the element (up to 10 characters) to be retrieved. If the TO DATA SET is a library,
you can leave this field blank; the member name in that library automatically becomes the
element name. You also can use a name mask to indicate that all elements, or only those
matching the characters specified, be considered in this request.
Element names can include only the following characters: A-Z, 0-9, @, #, and $
Type
The element type, such as COBOL, COPYLIB, etc. You can use a name mask to indicate that all
types, or only those matching the characters specified, be considered in this request.
Stage
Enter the ID of the stage from which you want to retrieve the element. Use one of the IDs
listed to the right of this field. You also can use a name mask with this field.
Comment
Enter any comments describing this request. Depending upon the system specified for the
request, comments may be required.
Action
These options provide additional information for the Retrieve request. The following options are
available:
CCID
This is the name of the CCID associated with the request. The interface will set the retrieve
CCID field to this value when it executes this request. A CCID may be required depending on
the system being used.
Expand Includes
This option allows you to expand INCLUDE statements when the element is retrieved.
Enter N to indicate that INCLUDE statements should not be expanded. This is the default
value.
No Signout
This option applies only if signin/signout is in effect for the system. NO SIGNOUT allows you to
retrieve the element without signing it out to your user ID. This option enables another user
to retrieve the element at the same time you are working with it. Similarly, you can retrieve a
copy of an element currently in use by another user if that user has specified the NO SIGNOUT
option.
04-May-2018 166/1109
CA Endevor® SCM - 17.0
Enter Y to retrieve the element but not sign it out to your user ID.
Enter N to retrieve the element and sign it out to your user ID. This is the default value.
Override Signout
This option applies only if the element to be retrieved is currently signed out.
Enter Y to indicate that the element can be processed, even if it is not signed out to you.
CA Endevor® SCM signs the element out to you if you specify this option.
Enter N to indicate that processing is not allowed unless the element is signed out. This is
the default value.
Replace Member
This option applies only if the TO DATA SET is a library. If you retrieve an element to a library,
the system checks whether that element (member) currently resides in the library. If it does,
the request normally is rejected. The REPLACE MEMBER option, however, allows you to
replace a member currently in the library with the retrieved element.
Enter N to reject the request if the member currently resides in the library. This is the
default value.
Member -- Enter the appropriate member name; you can enter either the full name or use a
name mask. If you leave this field blank, the member name defaults to the element name.
As an alternative, you can retrieve an element to a Roscoe data set. The following describes this
retrieval action:
To retrieve to your Roscoe data set, enter 'ROSCOE' in the data set name field.
The following ROSDATA JCL will be generated to import the member to your Roscoe data set:
//ROSCOE DD DSN=&&TEMP.,UNIT=SYSDA,SPACE=(TRK,(5,5,15))
// DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB),DISP=(,PASS)
// EXEC ROSDATA,PARM='ROSCOE.CONTROL'
//STEPLIB DD DSN=ROSCOE.ROSLIB,DISP=SHR
//SYSPRINT DD SYSOUT=A
//ROSLIB00 DD DSN=ROSCOE.ROSLIB00,DISP=SHR
//ROSLIB01 DD DSN=ROSCOE.ROSLIB01,DISP=SHR
//ROSLIB02 DD DSN=ROSCOE.ROSLIB02,DISP=SHR
//FROMDD1 DD DSN=&&TEMP.,DISP=(OLD,DELETE)
//SYSIN DD DD*
$ADD MEMBER=membername, KEY=keyname
$FROM FROMDD1 (membername)
List Options:
Where CCID EQ -- A CCID can be specified in this field to limit the selection list to only those
04-May-2018 167/1109
CA Endevor® SCM - 17.0
Where CCID EQ -- A CCID can be specified in this field to limit the selection list to only those
elements whose last CCID is equal to the specified CCID. If omitted, the WHERE CCID EQ field
is not used to limit the selection list.
Where PROC GRP EQ -- A processor group can be specified in this field to limit the selection
list to only those elements to which the processor group has been assigned. If omitted, the
WHERE PROC GRP EQ field is not used to limit the selection list.
Leave the ELEMENT field and MEMBER field blank, or use a name mask for either of these fields,
or
The Element Selection List shows all elements that match the criteria specified on the Retrieve
Elements panel. The FROM and TO information is displayed at the top of the panel, above the
element listing.
Select one or more elements to be retrieved, by placing an R to the left of each element you
want.
Request a detailed element display for one or more elements, by placing the appropriate
character (S, M, B, C, or H) to the left of each sourced element name. S, B, C and H are invalid
display options for sourceless elements. For elements of log delta format, options H and C are not
valid, and option B can only be used on the current (last) level of the element. For elements of
image delta format, H and C are not valid.
The COMMENT field is initially filled in for each element, according to the information provided on
the Retrieve Elements panel. You can override this entry before you select an element(s) for
processing. If the output data set is a library, you can enter a NEWNAME, which then becomes the to
MEMBER name.
When you press Enter, the Roscoe Interface performs the processing requested and returns the panel
with the message “*WRITTEN” next to each element retrieved.
From
Display-only. Indicates the environment, system, and subsystem for the element being retrieved.
To
Display-only. Indicates the to data set for the Retrieve action, as specified on the Retrieve
Elements panel.
04-May-2018 168/1109
CA Endevor® SCM - 17.0
Element
Display-only. Name of the element.
Newname
Applicable for a Retrieve action if the output data set is a library. This is the name to be used as
the output member name. If you leave this field blank, the output member name defaults to the
element name. This field is also used to display the message “*WRITTEN.”
Stg
Display-only. ID of the stage in which the element resides.
Type
Display-only. Name of the type associated with the element.
NS
Indicates whether the element is a sourceless element. A value of Y indicates it is sourceless. If
blank, the element is not sourceless.
VVLL
Display-only. This is the current level for the element, within the stage shown. By default, this is
the level that is retrieved.
To retrieve a different level, access the Summary of Levels panel by placing an S to the left of the
appropriate element (in the selection field). When that panel is returned, select the level you
want to use. For more information, see Retrieving Prior Versions (see page 169).
The Summary of Levels panel appears when you enter the option next to a particular element on the
Retrieve Element Selection List.
Retrieving prior versions of an element using the Summary of Levels panel can only be done on
sourced elements.
Generating Elements
The Generate action executes the generate processor for the current level of a CA Endevor® SCM
element. Use the Generate Elements panel to identify the element being generated.
04-May-2018 169/1109
CA Endevor® SCM - 17.0
Option
Use this field to specify the processing you wish to perform. The following options are available:
Blank
Display a selection list, optionally restricted according to any specifications provided
(environment, system name, etc.).
G
Execute the generate processor for the element.
S, M, B, C, H
Display one of the following element information panels:
Note: S, B, C, and H are invalid display options for sourceless elements. For elements of log
delta format, options H and C are not valid, and option B can only be used on the current
(last) level of the element. For elements of image delta format, H and C are not valid.
From Location
Enter information defining the element being generated. The following options are available:
Environment
Name of the current environment. Enter a different name to generate an element from
another environment.
System
Name of the system under which the element is defined. You can use a name mask to indicate
that all systems, or only those matching the characters specified, be considered in this
request.
Subsystem
Name of the subsystem under which the element is defined. You can use a name mask to
indicate that all subsystems, or only those matching the characters specified, be considered in
this request.
Element
The name of the element (up to 10 characters) to be generated. You can use a name mask to
indicate that all elements, or only those matching the characters specified, be considered in
this request. Element names can include only the following characters: A-Z, 0-9, @, #, and $
Type
04-May-2018 170/1109
CA Endevor® SCM - 17.0
Type
The element type, such as COBOL, COPYLIB, etc. You can use a name mask to indicate that all
types, or only those matching the characters specified, be considered in this request.
Stage
Enter the ID of the stage from which you want to generate the element. Use one of the IDs
listed to the right of this field. You also can use a name mask with this field.
Comment
Enter any comments describing this request. Depending upon the system specified for the
request, comments may be required.
Action
These options provide additional information for the Generate request. The following options are
available:
CCID
You can enter a CCID (up to 12 characters) to further define the element(s) being generated.
Depending on the system specified for this request, a CCID may be required.
Copyback
COPYBACK copies the current level of the source stage element back into the target stage,
and then generates the element in the target stage. If the target stage has been specified in
the request (that is, if the element currently resides in the target stage), however, the
COPYBACK option cannot be used.
When COPYBACK = Y, if you attempt to generate an element in the target stage that does
not exist in that stage, the element is copied from source stage and then generated in the
target stage. In this situation, the element remains unchanged in the source stage, and the
version/level assigned in the target stage is the same as the version/level in the source
stage.
When COPYBACK = N, the element is generated in the stage you specify, providing the
element exists in that stage.
You cannot specify COPYBACK = Y when you use a name mask in the stage field or when the
source stage. is used.
The Element Selection List is affected by how you set COPYBACK:
If COPYBACK = Y, stage must be 1 but the Element Selection List displays applicable
elements from both stages.
If COPYBACK = N, the Element Selection List displays elements from the stage specified on
the Generate Elements panel.
Override Signout
This option applies only when signin/signout is in effect for the specified system.
Enter Y to process the element even if it is not signed out to you. CA Endevor® SCM signs
the element out to you if you specify this option.
Enter N to indicate that processing is not allowed unless the element is signed out to you.
This is the default value.
04-May-2018 171/1109
CA Endevor® SCM - 17.0
Processor Group
This is the name of the processor group to be used. If you leave this field blank, the system
defaults to the processor group last used for this element.
You can also type a processor group name in this field or use a name mask for a list of
processor groups from which you can select.
List
The following list options are available:
Display List
This option is always set to Y.
Where CCID EQ
A CCID can be specified in this field to limit the selection list to only those elements whose last
CCID is equal to the specified CCID. If omitted, the WHERE CCID EQ field is not used to limit
the selection list.
Select one or more elements to be generated, by placing a G to the left of each element you
want, and/or
Request a detailed element display for one or more elements, by placing an appropriate character
( S, M, B, C, or H) to the left of each element name. S, B, C and H are invalid display option for
sourceless elements. For elements of log delta format, options H and C are not valid, and option B
can only be used on the current (last) level of the element. For elements of image delta format, H
and C are not valid.
When you press Enter, the Roscoe Interface generates the SCL required for processing and returns
the panel with an appropriate message next to any generated element(s).
From
Display-only. Indicates the environment, system, and subsystem for the element being generated.
Element
Display-only. Name of the element.
04-May-2018 172/1109
CA Endevor® SCM - 17.0
Stg
Display-only. ID of the stage in which the element resides.
Type
Display-only. Name of the type associated with the element.
NS
Indicates whether the element is a sourceless element. A value of Y indicates it is sourceless. If
blank, the element is not sourceless.
VVLL
Display-only. The current version/level for the element, within the stage shown.
Comment
Comments describing the Generate request. You can either use this comment or enter a different
one.
Moving Elements
The Move action moves an element from one inventory location (the FROM CA Endevor® SCM
location) to the next location on a map route. You can move elements either with history or without
history.
Option
Use this field to specify the processing you wish to perform. The following options are available:
Blank
Display a selection list, optionally restricted according to any specifications provided
(environment, system name, etc.).
O
Move the element from the source stage to the target stage.
S, M, B, C, H
Display one of the following element information panels:
04-May-2018 173/1109
CA Endevor® SCM - 17.0
Note: S, B, C, and H are invalid display options for sourceless elements. For elements of log
delta format, options H and C are not valid, and option B can only be used on the current
(last) level of the element. For elements of image delta format, H and C are not valid.
From Location
Enter information defining the element being moved. The following options are available:
Environment
Name of the current environment. Enter a different name to move an element in another
environment.
System
Name of the system under which the element is defined. You can use a name mask to indicate
that all systems, or only those matching the characters specified, be considered in this
request.
Subsystem
Name of the subsystem under which the element is defined. You can use a name mask to
indicate that all subsystems, or only those matching the characters specified, be considered in
this request.
Element
The name of the element (up to 10 characters) to be moved. You can use a name mask to
indicate that all elements, or only those matching the characters specified, be considered in
this request. Element names can include only the following characters: A-Z, 0-9, @, #, and $
Type
The element type, such as COBOL, COPYLIB, etc. You can use a name mask to indicate that all
types, or only those matching the characters specified, be considered in this request.
Stage
This field is for display only, and contains the ID of the stage where the element resides. For a
Move request, the ID always reflects the entry stage.
Comment
Comments describing the Move request. You can either use the existing comment or enter a
different one.
Action
These options provide additional information about the Move request. The following options are
available:
CCID
You can enter a CCID (up to 12 characters) to further define the element(s) being generated.
Depending upon the system specified for this request, a CCID may be required.
SYNC
Normally, if the element(s) exists in both stages but the source location of the move base level
differs from the target location of the move current level, the Move request is rejected. This
happens because during the Add action CA Endevor® SCM verifies that the source location of the
move base and the target location of the move current level are the same. The SYNC option
04-May-2018 174/1109
CA Endevor® SCM - 17.0
move base and the target location of the move current level are the same. The SYNC option
enables you to perform the request, however, by allowing a new level to be created in the target
location of the move even though the source location of the move base level is not equal to the
target location of the move current level. It is advisable to research this condition before using
the SYNC option.
Enter Y to use the SYNC option. Exercise caution when using this option, as you could regress
changes when the Move action is performed.
Enter N to indicate that the Move should not be performed if the source location of the move
base level is different than the target location of the move current level. This is the default
value.
With History
The WITH HISTORY option preserves the source location of the move change history. If you
request a MOVE WITH HISTORY, the system first ensures that the target location of the move
current level is the same as the source location of the move base level. All levels of the element
are then moved from the source location of the move to the target location of the move, and the
source location of the move change history is appended to the target location of the move
change history.
If you do not specify this option and differences exist between the source location of the move
current level and the target location of the move current level, these differences are combined
and recorded as a new level in the target location of the move.
Enter Y to append the source location of the move change history to the target location of the
move change history.
Enter N to combine all the source location of the move change levels into one level to be
moved into the target location of the move. This is the default value.
Retain Signout
This option tells CA Endevor® SCM to retain the source location signouts for all elements at the
target location. This option applies only if the element was signed out at the target before the
MOVE. If the element was signed out at the target before the MOVE, it will be signed out to that
same ID at the target after the MOVE. If the element was not signed out at the target before the
MOVE, it will not be signed out at the target after the MOVE. If you do not use this option, the
element at the target location is not signed out, regardless of whether it was signed out at the
target before the MOVE took place.
Signout To
This option tells CA Endevor® SCM to sign all elements out to the specified user ID at the target
stage.
04-May-2018 175/1109
CA Endevor® SCM - 17.0
List
Display List
This option is always set to Y.
Where CCID EQ
A CCID can be specified in this field to limit the selection list to only those elements whose last
CCID is equal to the specified CCID. If omitted, the WHERE CCID EQ field is not used to limit the
selection list.
Select one or more elements to be moved, by placing an O to the left of each element you want,
and/or
Request a detailed element display for one or more elements, by placing the appropriate
character (S, M, B, C , or H) to the left of each element name. S, B, C, and H are invalid display
options for sourceless elements. For elements of log delta format, options H and C are not valid,
and option B can only be used on the current (last) level of the element. For elements of image
delta format, H and C are not valid.
When you press Enter, the Roscoe Interface generates the SCL required for processing and returns
the panel with an appropriate message next to each moved element.
From
Indicates the environment, system, subsystem, and stage for the element being moved.
04-May-2018 176/1109
CA Endevor® SCM - 17.0
Element
Name of the element.
Type
Name of the type associated with the element.
NS
Indicates whether the element is a sourceless element. A value of Y indicates it is sourceless. If
blank, the element is not sourceless.
VVLL
The current version/level for the element, within the stage shown. This is the level that is moved.
Dates
These dates describe the processing related to the element (ddMMMyy format):
Generate -- The generate processor date. This field is blank if the generate processor has not
yet been run for the element.
Last Action
The last action recorded for the element.
NDVR RC
The CA Endevor® SCM return code stored in the Master Control File for the element.
Deleting Elements
The Delete action deletes all levels of an element. Use the Delete Elements panel to identify the
element being deleted.
Option
Use this field to specify the processing you wish to perform. The following options are available:
Blank
Display a selection list, optionally restricted according to any specifications provided
(environment, system name, etc.).
04-May-2018 177/1109
CA Endevor® SCM - 17.0
#
Delete the element.
S, M, B, C, H
Display one of the following element information panels:
Note: S, B, C, and H are invalid display options for sourceless elements. For elements of log
delta format, options H and C are not valid, and option B can only be used on the current
(last) level of the element. For elements of image delta format, H and C are not valid.
From Location
Enter information defining the element being deleted. The following options are available:
Environment
Name of the current environment. Enter a different name to delete an element in another
environment.
System
Name of the system under which the element is defined. You can use a name mask to indicate
that all systems, or only those matching the characters specified, be considered in this
request.
Subsystem
Name of the subsystem under which the element is defined. You can use a name mask to
indicate that all subsystems, or only those matching the characters specified, be considered in
this request.
Element
The name of the element (up to 10 characters) to be deleted. You can use a name mask to
indicate that all elements, or only those matching the characters specified, be considered in
this request. Element names can include only the following characters: A-Z, 0-9, @, #, and $
Type
The element type, such as COBOL, COPYLIB, etc. You can use a name mask to indicate that all
types, or only those matching the characters specified, be considered in this request.
Stage
Enter the ID of the stage from which you want to delete the element. Use one of the IDs listed
to the right of this field. You also can use a name mask with this field.
04-May-2018 178/1109
CA Endevor® SCM - 17.0
Comment
Enter any comments describing this request. Depending upon the system specified for the
request, comments may be required.
Action
These options provide additional information about the Delete action. The following options are
available:
CCID
You can enter a CCID (up to 12 characters) to further define the element(s) being generated.
Depending upon the system specified for this request, a CCID may be required.
Override Signout
This option applies only when signin/signout is in effect for the specified system.
Enter Y to delete the element even if it is not signed out to you. CA Endevor® SCM signs
the element out to you if you specify this option.
Enter N to indicate that processing is not allowed unless the element is signed out to you.
This is the default value.
Only Component
Applicable for CA Endevor® SCM ACM users only. Indicates whether you want to delete both
the element component list and the element, or the element component list only.
Enter N to delete the element as well as the element component list. This is the default
value.
List
The following List options are available:
Display List
This option is always set to Y.
Where CCID EQ
A CCID can be specified in this field to limit the selection list to only those elements whose last
CCID is equal to the specified CCID. If omitted, the WHERE CCID EQ field is not used to limit
the selection list.
04-May-2018 179/1109
CA Endevor® SCM - 17.0
Select one or more elements to be deleted, by placing a # to the left of each element you want,
and/or
Request a detailed element display for one or more elements, by placing the appropriate
character (S, M, B, C, or H) to the left of each element. The S, B, C, and H display options are
invalid for sourceless elements. For elements of log delta format, options H and C are not valid,
and option B can only be used on the current (last) level of the element. For elements of image
delta format, H and C are not valid.
When you press Enter, the Roscoe Interface generates the SCL required for processing and returns
the panel with an appropriate message next to each deleted element.
From
Indicates the environment, system, and subsystem from which the element is being deleted.
Element
Name of the element.
Stg
ID of the stage for the element.
Type
Name of the type associated with the element.
NS
Indicates whether the element is a sourceless element. A value of Y indicates it is sourceless. If
blank, the element is not sourceless.
VVLL
This is the current version/level for the element, within the stage shown.
Dates
These dates describe the processing related to the element (ddMMMyy format):
Generate -- The generate processor date. This field is blank if the generate processor has not
yet been run for the element.
04-May-2018 180/1109
CA Endevor® SCM - 17.0
Last Action
This is the last action recorded for the element.
Printing Elements
The Print Elements action prints selected information about an element(s), in report format. Use this
panel to identify the element for which you want information, as well as to select the type of report
you want to print.
Option
Enter the appropriate code to receive the information/report you want. The following options are
available:
Blank
Display a selection list, optionally restricted according to any specifications provided
(environment, system name, etc.).
P Print element
Prints a browse report, which shows all statements in the current level of the element, as well
as the level at which each statement was inserted. This is the default entry. This option is
invalid for sourceless elements. For elements of log delta format, this option is only valid on
the current (last) level of the element.
S, M, B, C, H
Display one of the following element information panels:
04-May-2018 181/1109
CA Endevor® SCM - 17.0
Note: S, B, C, and H are invalid display options for sourceless elements. For elements
of log delta format, options H and C are not valid, and option B can only be used on the
current (last) level of the element. For elements of image delta format, H and C are not
valid.
From Location
Enter information defining the element to be printed. The following options are available:
Environment
Name of the current environment. Enter a different name to print an element from another
environment.
System
Name of the system under which the element is defined. You can use a name mask to indicate
that all systems, or only those matching the characters specified, be considered in this request.
Subsystem
Name of the subsystem under which the element is defined. You can use a name mask to indicate
that all subsystems, or only those matching the characters specified, be considered in this
request.
Element
The name of the element (up to 10 characters) to be printed. You can use a name mask to
indicate that all elements, or only those matching the characters specified, be considered in this
request. Element names can include only the following characters: A-Z, 0-9, @, #, and $
Type
The element type, such as COBOL, COPYLIB, etc. You can use a name mask to indicate that all
types, or only those matching the characters specified, be considered in this request.
Stage
Enter the ID of the stage from which you want to print the element. Use one of the IDs listed to
the right of this field. You also can use a name mask with this field.
List
Display List
This option is always set to Y.
Where CCID EQ
A CCID can be specified in this field to limit the selection list to only those elements whose last
CCID is equal to the specified CCID. If omitted, the WHERE CCID EQ field is not used to limit the
selection list.
04-May-2018 182/1109
CA Endevor® SCM - 17.0
Select one or more elements to be printed, by placing a P, PC, PS, PM, or PH (depending on the
report you want) to the left of each element you want. When you press ENTER, the Roscoe
Interface generates the SCL required for processing and returns the panel with an appropriate
message next to each element queued for print. P, PC, PS, and PH are invalid actions for
sourceless elements.
Request a detailed element display for one or more elements, by placing an appropriate character
(S, M, B, C, or H) to the left of each element you want. Press PF3 to return to the previous panel.
S, B, C, and H are invalid display options for sourceless elements. For elements of log delta
format, options H and C are not valid, and option B can only be used on the current (last) level of
the element. For elements of image delta format, H and C are not valid.
From
Identification of the environment, system, and subsystem from which the element is being
printed.
Element
Name of the element.
Stg
ID of the stage for the element.
Type
Name of the type for the element.
NS
04-May-2018 183/1109
CA Endevor® SCM - 17.0
NS
Indicates whether the element is a sourceless element. A value of Y indicates it is sourceless. If
blank, the element is not sourceless.
VVLL
Current version/level for the element, within the stage shown.
Dates
Dates that describe the processing related to the element (in ddMMMyy format):
Generate -- Generate processor date. This field is blank if the generate processor has not
been run yet for the element.
Last Action
Last action recorded for the element.
Signin Elements
The Signin action removes a user signout associated with a particular CA Endevor® SCM element,
allowing another user to access the element without overriding the signout. This action is available
only for systems where signin/signout is in effect. Use the Signin Elements panel to identify the
element being signed in.
Option
Use this field to specify the processing you wish to perform. The following options are available:
Blank
Display a selection list, optionally restricted according to any specifications provided
(environment, system name, etc.).
SI
Sign in the element.
S, M, B, C, H
Display one of the following element information panels:
Note: S, B, C, and H are invalid display options for sourceless elements. For elements of log
04-May-2018 184/1109
CA Endevor® SCM - 17.0
Note: S, B, C, and H are invalid display options for sourceless elements. For elements of log
delta format, options H and C are not valid, and option B can only be used on the current
(last) level of the element. For elements of image delta format, H and C are not valid.
From Location
Enter information defining the element to be signed in. The following options are available:
Environment
Name of the current environment. Enter a different name to sign in an element in another
environment.
System
Name of the system under which the element is defined. You can use a name mask to indicate
that all systems, or only those matching the characters specified, be considered in this
request.
Subsystem
Name of the subsystem under which the element is defined. You can use a name mask to
indicate that all subsystems, or only those matching the characters specified, be considered in
this request.
Element
The name of the element (up to 10 characters) to be signed in. You can use a name mask to
indicate that all elements, or only those matching the characters specified, be considered in
this request. Element names can include only the following characters: A-Z, 0-9, @, #, and $
Type
The element type, such as COBOL, COPYLIB, etc. You can use a name mask to indicate that all
types, or only those matching the characters specified, be considered in this request.
Stage
This field is for display only, and contains the ID of the stage where the element resides.
Action
These options provide additional information about the Signin request. The following options are
available:
Override Signout
This option applies only when signin/signout is in effect for the specified system.
Enter Y to sign in the element even if it is not signed out to you. CA Endevor® SCM signs
the element out to you if you specify this option.
Enter N to indicate that processing is not allowed unless the element is signed out to you.
This is the default value.
Signout To
Used to sign out the element to another user. CA Endevor® SCM uses this user ID to set the
SIGNOUT ID field (on the Element Master panel) for this element.
List
The following List options are available:
04-May-2018 185/1109
CA Endevor® SCM - 17.0
Display List
This option is always set to Y.
Where CCID EQ
A CCID can be specified in this field to limit the selection list to only those elements whose last
CCID is equal to the specified CCID. If omitted, the WHERE CCID EQ field is not used to limit
the selection list.
Where User EQ
A signout user ID can be specified in the WHERE USER EQ field to limit the selection list to only
those elements whose user ID is equal to the specified SIGNOUT USER ID.
Select one or more elements to be signed in, by placing an SI to the left of each element name,
and/or
Request a detailed element display for one or more elements, by placing the appropriate
character (S, M, B, C, or H) to the left of each element you want. S, B, C, and H are invalid display
options for sourceless elements. For elements of log delta format, options H and C are not valid,
and option B can only be used on the current (last) level of the element. For elements of image
delta format, H and C are not valid.
When you press Enter, the Roscoe Interface generates the SCL required for processing and returns
the panel with an appropriate message next to each element that is signed in.
From
Identification of the environment, system, and subsystem for the element being signed in.
Element
Name of the element.
04-May-2018 186/1109
CA Endevor® SCM - 17.0
Stg (Stage)
Stage where the element resides.
Type
Name of the element type.
NS
Indicates whether the element is a sourceless element. A value of Y indicates it is sourceless. If
blank, the element is not sourceless.
VVLL
Current version/level for the element, within the stage shown.
Signout User ID
ID of the user to whom the element is currently signed out.
Transferring Elements
The Transfer action transfers elements from one CA Endevor® SCM location to another. Use the
Transfer Elements panel to identify the element being transferred. The Transfer action cannot be
done against a sourceless element.
If you want to transfer an element to or from an archive data set, you must manually code the SCL for
the action.
Note: For more information about manually coding the SCL, see Edit the Request Data Set
(see page 204).
If you manually code a Transfer request to an archive data set, you cannot use “ROSCOE” as the
archive (TO) data set. If you assign “ROSCOE” as the TO data set name, you receive an error message.
Option
Use this field to specify the processing you wish to perform. The following options are available:
Blank
Display a selection list, optionally restricted according to any specifications provided
(environment, system name, etc.).
T
Generate an action request to transfer a sourced element from the From Location to the To
Location.
04-May-2018 187/1109
CA Endevor® SCM - 17.0
S, M, B, C, H
Display one of the following element information panels:
Note: S, B, C, and H are invalid display options for sourceless elements. For elements of log
delta format, options H and C are not valid, and option B can only be used on the current
(last) level of the element. For elements of image delta format, H and C are not valid.
From Location
Define the location from which the element is being transferred. The following options are
available:
Environment
Name of the current environment. Enter a different name to transfer an element from
another environment.
System
Name of the system under which the element is currently defined. You can use a name mask
to indicate that all systems, or only those matching the characters specified, be considered in
this request.
Subsystem
Name of the subsystem under which the element is currently defined. You can use a name
mask to indicate that all subsystems, or only those matching the characters specified, be
considered in this request.
Element
The name of the element (up to 10 characters) to be transferred. You can use a name mask to
indicate that all elements, or only those matching the characters specified, be considered in
this request. Element names can include only the following characters: A-Z, 0-9, @, #, and $
Type
The element type, such as COBOL, COPYLIB, etc. You can use a name mask to indicate that all
types, or only those matching the characters specified, be considered in this request.
Stage
Enter the ID of the stage from which you want to transfer the element. Use one of the IDs
listed to the right of this field. You also can use a name mask with this field.
04-May-2018 188/1109
CA Endevor® SCM - 17.0
To Location
Define the To Location for the element being transferred. The following options are available:
Note: You cannot use name masks with the To Location fields.
Note: You can enter a new element name here only if you coded a full element name as
the FROM element name. Element names can include only the following characters: A-Z, 0-
9, @, #, and $
Type
Name of the to element type (such as COBOL, COPYLIB, etc.). If you leave this field blank,
the type defaults to the FROM type entry.
Stage
The stage ID for the TO element. If you leave this field blank, the stage ID defaults to the
FROM stage.
Comment
Enter any comments describing this request. Depending upon the system specified for the
request, comments may be required.
List
The following List options are available:
Display List
This option is always set to Y.
Where CCID EQ
A CCID can be specified in this field to limit the selection list to only those elements whose last
CCID is equal to the specified CCID. If omitted, the WHERE CCID EQ field is not used to limit
the selection list.
Action
These provide additional information about the Transfer request. The following options are
available:
CCID
You can enter a CCID (up to 12 characters) to further define the element. Depending upon the
system specified for this request, a CCID may be required.
04-May-2018 189/1109
CA Endevor® SCM - 17.0
Enter Y to retain the element after it is transferred. This is the default value.
Enter Y to bypass (that is, not execute) the generate processor for the element after it is
transferred. This is the default value.
Enter N to execute the generate processor for the element after the Transfer action is
completed.
Override Signout
This option applies only when signin/signout is in effect for the FROM system.
Enter Y to transfer the element even if it is not signed out to you. CA Endevor® SCM signs
the element out to you if you specify this option.
Enter N to indicate that processing is not allowed unless the element is signed out to you.
This is the default value.
Processor Group
The name of the processor group to be used. If you leave this field blank, the system defaults
to the processor group last used for this element. You can also type a processor group name
in this field or use a name mask to access a list of processor groups from which you can select.
Synchronize
This option applies when the element already exists in the To Location. The SYNCHRONIZE
option is used in conjunction with the WITH HISTORY option. When you want to transfer an
element with history, and the current level of the To Location element differs from the base
level of the From Location element, you normally receive an error message and the transfer is
not performed.
If you use this option, however, the system creates an intermediate level known as the
synchronized level which contains the differences between the base level of the From
Location element and the current level of the To Location element. All levels (change history)
associated with the From Location element are then appended to the To Location element
and renumbered.
Enter Y if you want the Transfer action to be performed even though the base level of the
FROM element differs from the current level of the TO element.
Enter N if you do not want the Transfer action to be performed when the base level of the
FROM element differs from the current level of the TO element. This is the default value.
With History
04-May-2018 190/1109
CA Endevor® SCM - 17.0
With History
The WITH HISTORY option preserves From Location change history. If you request a TRANSFER
WITH HISTORY, the system first ensures that the current level of the To Location element is
the same as the current level of the From Location element. All levels of the element are then
moved from the From Location to the To Location, and the From Location change history is
appended to the To Location change history.
If you do not specify this option and differences exist between the current levels of the From
Location element and the To Location element, these differences are combined and recorded
as a new level in the To Location.
Enter N to combine ALL From Location change levels into one level to be moved into the
To Location. This is the default value.
Retain Signout
This option tells CA Endevor® SCM to retain the source location signouts for all elements at
the target location. This option applies only if the element was signed out at the source
before the TRANSFER.
If the element was signed out at the source before the TRANSFER, it will be signed out to
that same ID at the target after the TRANSFER.
If the element was not signed out at the source before the TRANSFER, it will not be signed
out at the target after the TRANSFER.
If you do not use this option, the element at the target location is not signed out,
regardless of whether it was signed out at the target before the TRANSFER took place.
Signout To
This option tells CA Endevor® SCM to sign all elements out to the specified user ID at the
target stage.
Select one or more elements to be transferred, by placing a T to the left of each sourced element
you want, and/or
Request a detailed element display for one or more elements, by placing an appropriate character
(S, M, B, C, or H) to the left of each element you want.
Note: All fields except the SELECTION and TO NAME fields are display-only.
04-May-2018 191/1109
CA Endevor® SCM - 17.0
From
Identification of the FROM environment, system, and subsystem for the element being
transferred.
To
Identification of the TO environment, system, subsystem, and stage for the element being
transferred.
Note: S, B, C, and H are invalid display options for sourceless elements. For elements of log
delta format, options H and C are not valid, and option B can only be used on the current
(last) level of the element. For elements of image delta format, H and C are not valid.
Element
Name of the FROM element.
To Name
Name of the TO element. This name defaults to the from element name.
Stg
Stage ID for the from element.
Type
Name of the element type for the from element.
NS
Indicates whether the element is a sourceless element. A value of Y indicates it is sourceless. If
blank, the element is not sourceless.
VVLL
Current version/level for the element, within the stage shown.
Dates
Dates that describe the processing related to the element (in ddMMMyy format):
Generate -- Generate processor date. This field is blank if the generate processor has not
been run yet for the element.
Last Action
Last action recorded for the element.
04-May-2018 192/1109
CA Endevor® SCM - 17.0
Printing Members
The Print Members action prints information about library members. Use the Print Members panel to
identify the library member.
Option
Use this field to specify the processing you wish to perform. The following options are available:
Blank
Display a member list for the library named.
B
Show a Browse panel with the contents of a specific library member.
P
Generate an action request to print the member specified.
Member
Enter the appropriate member name; you can use a name mask.
Thru Member
The name entered here indicates the last in the range, with the name specified in the
MEMBER field considered as the first name in the range. You can enter a full member name or
use a name mask.
List Options
The Display List option is always set to Y.
The Member Selection List panel shows the library being processed (FROM DATA SET). It lists each
member in the library down the left-hand column, and the footprint information for that member (if
any) to the right. This footprint information includes the system and subsystem for the associated CA
Endevor® SCM element, the element name itself, the type for the element, the version and level of
the element associated with this member, and the date/time the footprint was written.
Select one or more members to be printed, by placing a P to the left of each member you want,
and/or
Select one or more members to be browsed, by placing a B to the left of each member you want.
04-May-2018 193/1109
CA Endevor® SCM - 17.0
Select one or more members to be browsed, by placing a B to the left of each member you want.
If you request BROWSE (B), the Roscoe Interface returns a Browse panel for the member. Press PF3
when you are through browsing the member, to return to the Member Selection List.
Listing Elements
The List Element action scans elements in the Master Control File and creates a list of elements that
meet the criteria you enter on the List Element Action panel. This list takes the form of action
requests for the elements. Use the List Element action panel to identify those elements to be listed.
You also can list elements from an archive data set. However, you must manually code the SCL for
this action using the Edit screen.
Note: For more information about manually coding the SCL, see Edit the Request Data Set (see page
204) and the SCL Reference Manual.
In addition, you can create action requests to list members from a library. A separate panel List
Members is used to perform this action; this panel is discussed in the next section of this chapter.
Option
Use this field to specify the processing you wish to perform. The following options are available:
Blank
Display a selection list.
L
Generate an action request to list the element(s) identified on the screen.
S, M, B, C, H
Display one of the following element information panels: Summary of Levels (S), Element
Browse (B), Element History (H), Element Changes (C), or Element Master Info (M).
Note: S, B, C, and H are invalid display options for sourceless elements. For elements of log
delta format, options H and C are not valid, and option B can only be used on the current
(last) level of the element. For elements of image delta format, H and C are not valid.
From Location
Enter information defining the element to be listed. The following options are available:
Environment
Name of the current environment. Enter a different name to list an element from another
environment.
System
04-May-2018 194/1109
CA Endevor® SCM - 17.0
System
Name of the system under which the element is defined. You can use a name mask to indicate
that all systems, or only those matching the characters specified, be considered in this
request.
Subsystem
Name of the subsystem under which the element is defined. You can use a name mask to
indicate that all subsystems, or only those matching the characters specified, be considered in
this request.
Element
The name of the element (up to 10 characters) to be listed. You can use a name mask to
indicate that all elements, or only those matching the characters specified, be considered in
this request. Element names can include only the following characters: A-Z, 0-9, @, #, and $.
Type
The element type, such as COBOL, COPYLIB, etc. You can use a name mask to indicate that all
types, or only those matching the characters specified, be considered in this request.
Stage
Enter the ID of the stage for the element. Use one of the IDs listed to the right of this field.
You also can use a name mask with this field.
List
The following List options are available:
Display List
This option is always set to Y.
Where CCID EQ
A CCID can be specified in this field to limit the selection list to only those elements whose last
CCID is equal to the specified CCID. If omitted, the WHERE CCID EQ field is not used to limit
the selection list.
Text String
This option allows you to specify that only those elements containing a particular character string
(as defined in this field) can be selected for the List action request. Enter the text string for which
you want to search; you can code up to 70 characters. Enclose the string in quotes if it contains
blanks or special characters.
If you use the SCAN COLUMNS option, you can restrict the search to specific columns only.
Scan Columns
This option applies only if you specify a text string. You can indicate that only a particular range of
columns is to be searched for the text string indicated. For example, you may want to list only
those elements with a specific character string contained within columns 25-45. If the text cannot
be found within these columns, the element will not be selected for the list.
If you use this option, you must enter both a starting and an ending column. Enter the
appropriate column numbers in the START and END fields on the panel.
04-May-2018 195/1109
CA Endevor® SCM - 17.0
&&ACTION -- Use this to specify actions at run time rather than when the list is first
generated.
ADD
ARCHIVE
COPY
DELETE
GENERATE
LIST
MOVE
RESTORE
RETRIEVE
SIGNIN
TRANSFER
UPDATE
Where Component EQ
A component can be specified in the WHERE COMPONENT EQ field to limit the selection list to
only those elements containing the component(s) indicated.
04-May-2018 196/1109
CA Endevor® SCM - 17.0
Select one or more elements to be listed, by placing an L to the left of each element you want, and
/or
Request a detailed element display for one or more elements, by placing an appropriate
character (S, M, B, C, or H) to the left of each element you want.
Note: S, B, C, and H are invalid display options for sourceless elements. For elements of log
delta format, options H and C are not valid, and option B can only be used on the current
(last) level of the element. For elements of image delta format, H and C are not valid.
From
Identification of the environment for the element being listed.
System
Identification of the system under which the element is defined.
Subsystem
Identification of the subsystem under which the element is defined.
Stage
Identification of the stage for the element.
Element
Name of the element.
Type
Name of the element type.
NS
Indicates whether the element is a sourceless element. A value of Y indicates it is sourceless. If
blank, the element is not sourceless.
VVLL
Current version/level for the element, within the stage shown.
04-May-2018 197/1109
CA Endevor® SCM - 17.0
Dates
Dates that describe the processing related to the element (in ddMMMyy format):
Generate -- The generate processor date. This field is blank if the generate processor has not
yet been run for the element.
Last Action
Last action recorded for the element.
NDVR
CA Endevor® SCM return code for the element.
If, however, you specify WRITE LIST TO OUTPUT DATA SET = Y on the List Elements panel, the Roscoe
Interface returns the List Output panel.
Option
Leave this field blank.
Member
Enter the appropriate member name; you can specify either the full name or use a name mask.
Listing Members
The List Members action scans members in a library and lists the members that meet the remaining
criteria entered in the List Members panel. This list takes the form of action requests for the
members. Use the List Members panel to identify those members to be listed.
You also can list members from a library external to CA Endevor® SCM. However, you must manually
code the SCL for this action using the Edit screen.
You can also create action requests which list elements from the Master Control File. A separate
panel List Element action is used to perform this action; this panel is discussed in the previous section
of this chapter.
Option
Use the OPTION field to specify the processing you want to perform. The following options are
available:
04-May-2018 198/1109
CA Endevor® SCM - 17.0
Blank
Display a Member Selection List for the library named, optionally restricted according to any
member name mask provided.
B
Return a Browse panel showing the contents of a specific library member.
L
Generate an action request to list the member specified.
Member
Enter the appropriate member name; you can specify either the full name or use a name
mask.
Thru Member
Use this field to print a range of members in the data set. The member name entered here
indicates the last member in the range, with the name specified in the MEMBER field
considered as the first name in the range. You can enter either a full member name or use a
name mask.
List
The Display List option is always set to Y.
Text String
Use this option to specify that only those members containing a particular character string (as
defined in this field) can be selected for the List request. Enter the text string for which you want
to search; you can code up to 70 characters. Enclose the string in quotes if it contains blanks or
special characters.
If you use the SCAN COLUMNS option, you can restrict the search to specific columns only.
Scan Columns
This option applies only if you specify a text string. You can indicate that only a particular range of
columns is to be searched for the text string indicated. For example, you may want to list only
those members with a specific character string contained within columns 25-45. If the text cannot
be found within these columns, the member is not selected for the list.
If you use this option, you must enter both a starting and an ending column. Enter the
appropriate column numbers in the START and END fields on the panel.
&&ACTION -- Use this to specify actions at run time rather than when the list is first
generated.
ADD
04-May-2018 199/1109
CA Endevor® SCM - 17.0
ADD
ARCHIVE
COPY
DELETE
GENERATE
LIST
MOVE
RESTORE
RETRIEVE
SIGNIN
TRANSFER
UPDATE
The Member Selection List shows the library being processed (FROM DATA SET). Each member in the
library is listed in the left-hand column, and the footprint information for that member (if any) is
listed to the right of the member name. Footprint information includes the system and subsystem for
the associated CA Endevor® SCM element, the element name itself, the element type, the version
and level of the element associated with this member, and the date and time the footprint was
written.
Select one or more members to be listed, by placing an L to the left of each member you want,
and/or
Select one or more members to be browsed, by placing a B to the left of each member you want.
04-May-2018 200/1109
CA Endevor® SCM - 17.0
Archiving Elements
The Archive action writes the current version (including the base level and all change levels) of a CA
Endevor® SCM element to a sequential file, known as an archive data set. Use the Archive Elements
panel to identify the element(s) being archived.
Option
Use this field to specify the processing you want to perform. The following options are available:
Blank
Display a selection list, optionally restricted according to any specifications provided
(environment, system name, etc.).
V
Generate an action request to archive the element(s) identified on the screen. The archive
action is invalid for sourceless element. If you attempt to archive a sourceless element you
will receive an error.
S, M, B, C, H
Display one of the following element information panels:
Note: S, B, C, and H are invalid display options for sourceless elements. For elements of log
delta format, options H and C are not valid, and option B can only be used on the current
(last) level of the element. For elements of image delta format, H and C are not valid.
From Location
Enter information defining the element to be archived. The following options are available:
Environment
Name of the current environment. Enter a different name to archive an element from another
environment.
System
Name of the system under which the element is defined. You can use a name mask to indicate
that all systems, or only those matching the characters specified, be considered in this
request.
Subsystem
04-May-2018 201/1109
CA Endevor® SCM - 17.0
Subsystem
Name of the subsystem under which the element is defined. You can use a name mask to
indicate that all subsystems, or only those matching the characters specified, be considered in
this request.
Element
The name of the element (up to 10 characters) to be archived. You also can use a name mask
to indicate that all elements, or only those matching the characters specified, be considered in
this request. Element names can include only the following characters: A-Z, 0-9, @, #, and $
Type
The element type, such as COBOL, COPYLIB, etc. You can use a name mask to indicate that all
types, or only those matching the characters specified, should be considered in this request.
Stage
Enter the ID of the stage from which you want to archive the element. Use one of the IDs
listed to the right of this field. You also can use a name mask with this field.
Comment
Enter any comments describing this request. Depending upon the system specified for this
request, comments may be required.
Action
These provide additional information about the Archive request. The following options are
available:
CCID
You can enter a CCID (up to 12 characters) to further define the element. Depending upon the
system specified for this request, a CCID may be required.
Override Signout
This option applies only when signin/signout is in effect for the FROM system.
Enter Y to archive the element even if it is not signed out to you. CA Endevor® SCM signs
the element out to you if you specify this option.
Enter N to indicate that processing is not allowed unless the element is signed out to you.
This is the default value.
To File
Enter the DDNAME for the archive data set. Be sure to include the JCL for this data set when you
submit the batch job for execution (specify Y in the INCLUDE JCL field on the Batch Options Menu).
The DCB must specify variable blocked records (RECFM=VB), and the DSORG should be PS. The
minimum LRECL should be the greater of 3 times the maximum MCF-record length or the TYPE-
LENGTH plus (+) 14. When archiving to disk, the recommended block size is one-half a track, and
04-May-2018 202/1109
CA Endevor® SCM - 17.0
LENGTH plus (+) 14. When archiving to disk, the recommended block size is one-half a track, and
the recommended LRECL is one-half a track minus (-) 4 unless the previous rule requires a bigger
LRECL/BLKSIZE. When archiving to tape, the recommended block size is 32760 and the
recommended LRECL is 32756.
Note: You cannot archive an element to ROSCOE. If you assign ROSCOE as the TO data set
name, you receive an error message.
List
The following List options are available:
Display List
This option is always set to Y.
Where CCID EQ
A CCID can be specified in this field to limit the selection list to only those elements whose last
CCID is equal to the specified CCID. If omitted, the WHERE CCID EQ field is not used to limit
the selection list.
Select one or more sourced elements to be archived, by placing a V to the left of each element
you want, and/or
Request a detailed element display for one or more elements, by placing an appropriate character
to the left of each element for which you want to display information. The characters are S
(display), M (element master), B (element browse), C (changes), or H (history).
From
Environment, system, and subsystem for the element being archived.
To
DDNAME for the to archive data set.
04-May-2018 203/1109
CA Endevor® SCM - 17.0
Note: S, B, C, and H are invalid display options for sourceless elements. For elements of log
delta format, options H and C are not valid, and option B can only be used on the current
(last) level of the element. For elements of image delta format, H and C are not valid.
Element
Name of the element.
Stg
ID of the stage for the element.
Type
Name of the type for the element.
NS
Indicates whether the element is a sourceless element. A value of Y indicates it is sourceless. If
blank, the element is not sourceless.
VVLL
Current version/level for the element, within the stage shown.
When you select this option, you must provide the following information in addition to the option
number:
DSNAME
Enter the appropriate data set name.
Member
Enter the name of the member in which you want to place your action requests.
04-May-2018 204/1109
CA Endevor® SCM - 17.0
Note: If you prefer to create SCL requests within your Roscoe workspace (AWS), you may
enter the keyword ROSCOE. You must also enter a member name. You can place the
member name in this field, in brackets immediately following the keyword, or in the
MEMBER field on the next line.
You do not need to fill in the remaining fields on the Batch Options Menu when using the EDIT
option.
Press ENTER when you have filled in the necessary information. Roscoe returns a panel to display the
contents of the action request data set.
Use the panel to review the action requests in the data set, or to modify the data set.
When you select this option, you must provide the following information in addition to the option
number.
DSNAME
Enter the appropriate data set name.
Member
Enter the name of the member in which you want to place your action requests.
Note: If you prefer to create SCL requests within your Roscoe workspace (AWS), you may
enter the keyword ROSCOE. You must also enter a member name. You can place the
member name in this field, in brackets immediately following the keyword, or in the
MEMBER field on the next line.
Append
Indicate whether you want to add new requests to the end of an existing data set or library
member (Y) or overwrite any data currently in the data set or library member (N).
Include JCL
Indicates whether you want to include supplementary JCL with this job. This field is required with
the SUBMIT option.
Enter Y to add JCL to the standard execution JCL. If you select this option, you must have
previously defined the additional JCL (using option 5 on the Batch Options Menu).
04-May-2018 205/1109
CA Endevor® SCM - 17.0
In the Batch Options menu, type 5 in the OPTION field and press Enter. Then, fill in the JCL (complete
statements) you want to include with the batch job execution, and then press PF3 to return to the
Batch Options Menu.
04-May-2018 206/1109
CA Endevor® SCM - 17.0
The Roscoe Interface dialog driver, program C1RPUSER, is a Roscoe ETSO application that interacts
with the Roscoe Interface user to perform CA Endevor® SCM functions.
The Roscoe Interface server is a set of routines that the dialog driver uses to perform CA Endevor®
SCM specific functions. The number of active servers is defined by the SERVERS= parameter on the
Roscoe Interface configuration macro, C1RMCNFG.
Note: For more information about building the configuration module, see How the Roscoe
Installation Works (see page ).
When the dialog driver requires a CA Endevor® SCM service, it will pass the request to the first
available server. The dialog driver and the server will be tied together only for the duration of the
request. If a server is not available, the request will be queued until a server becomes available and
the Roscoe Interface user will be placed in a “wait” condition. If a large number of users will be active
concurrently, it is important that you define a sufficient number of servers to process the dialog
requests in order to reduce the amount of time spent waiting.
If you issue the Roscoe Interface QUIE command, message C1R119I will indicate the number of times
a Roscoe Interface user had to wait for a server. You can use this value to determine if a sufficient
number of servers have been defined. A large WAIT count indicates that the number of servers
should be increased.
The fixed storage requirement for the CA Endevor® SCM and interface reentrant programs is 900K
(24 bit addressable).
The variable storage requirement for the interface server dynamic storage and non-reentrant
programs (per defined server) is 70K (24 bit addressable).
The variable storage requirement for the interface dialog driver (per active user) is 20K (31 bit
addressable), plus selection list storage. The amount of storage required for the CA Endevor®
SCM selection list depends on the size of the list and the type of the list. A formula, therefore,
cannot be easily provided. All selection lists, however, are allocated from 31 bit addressable
storage. Storage for a selection list is released after the table has been processed by the user.
In this example, assume that the C1RMCNFG macro specified that 25 users will concurrently use the
interface. The estimated variable storage requirement to support this configuration is the following:
For 25 dialogs at 20K for each dialog, the estimated requirement is 500K (31 bit)
04-May-2018 207/1109
CA Endevor® SCM - 17.0
For 25 dialogs at 20K for each dialog, the estimated requirement is 500K (31 bit)
Note: Remember that the storage for the dialogs does not include the selection list
requirements. In addition, these are estimates only and the actual storage requirements
may vary depending on the maintenance level of the CA Endevor® SCM and interface
products that you are executing.
04-May-2018 208/1109
CA Endevor® SCM - 17.0
C1R1001
Activating the CA Roscoe 14.0 Interface
Reason:
The CA Endevor SCM CA Roscoe Interface initialization task is beginning to activate the interface.
Action:
None.
C1R101I
CA Roscoe Interface initialized with count servers
Reason:
The CA Endevor SCM CA Roscoe Interface initialization task has completed and the number of
interface servers specified have been created.
Action:
None.
C1R102E
IDENTIFY of C1RPCTR2 failed
Reason:
04-May-2018 209/1109
CA Endevor® SCM - 17.0
Reason:
The interface initialization task, C1RPCTRL, received a non-zero return code from the MVS IDENTIFY
service. The initialization task will terminate with a return code of four.
Action:
Reinitialize the interface by restarting the Roscoe region. If the problem persists, contact Technical
Support at http://ca.com/support (http://www.ca.com/support).
C1R103E
CA Roscoe Interface server execution failed with code return code
Reason:
A interface server unexpectedly terminated while processing a CA Endevor® SCM request. The return
code identifies the return code placed in the TCB when the server terminated.
Action:
If more than one server was defined in the interface configuration then no action is necessary. Any
CA Endevor® SCM requests will be processed by the remaining servers. For assistance, contact
Technical Support at http://ca.com/support (http://www.ca.com/support).
C1R104E
CA Roscoe Interface server initialization failed with code return code
Reason:
A interface server abended during initialization. The return code identifies the return code that was
placed in the server TCB for the server.
Action:
Check the CA Roscoe IE message log for any error messages that may have been issued during the
server initialization and take the corrective action specified for the message. Reinitialize the interface
by restarting the CA Roscoe IE region. If the problem persists, contact Technical Support at http://ca.
com/support (http://www.ca.com/support).
C1R105E
Identify of C1RDGCT failed
Reason:
04-May-2018 210/1109
CA Endevor® SCM - 17.0
The interface initialization task, C1RPCTRL, received a non-zero return code from the MVS IDENTIFY
service. The initialization task will terminate with a return code of four.
Action:
Reinitialize the interface by restarting the CA Roscoe IE region. If the problem persists, contact
Technical Support at http://ca.com/support (http://www.ca.com/support).
C1R106E
Unable to load the C1DEFLTS table
Reason:
The interface initialization task, C1RPCTRL, was unable to load the CA Endevor® SCM C1DEFLTS table.
The interface will terminate with a return code 16.
Action:
Verify that the C1DEFLTS table is in the CONLIB DD data set specified in the Roscoe execution JCL.
Also, refer to the CA Roscoe IE message log to determine if the MVS program manager issued any
error messages and take the corrective action associated with the message.
C1R107E
Unable to load C1RPLINK
Reason:
The interface initialization task, C1RPCTRL, was unable to load module C1RPLINK. The interface will
terminate with a return code 16.
Action:
Verify that module C1RPLINK is in the STEPLIB/JOBLIB DD data set specified in the Roscoe execution
JCL. Also, refer to the CA Roscoe IE message log to determine if the MVS program manager issued any
error messages and take the corrective action associated with the message.
C1R108E
Unable to load C1RPCNFG
Reason:
The interface initialization task, C1RPCTRL, was unable to load module C1RPCNFG. The interface will
terminate with a return code 16.
Action:
04-May-2018 211/1109
CA Endevor® SCM - 17.0
Action:
Verify that module C1RPCNFG is in the STEPLIB/JOBLIB DD data set specified in the Roscoe execution
JCL. Also, refer to the interface message log to determine if the MVS program manager issued any
error messages and take the corrective action associated with the message. If the module is not
found, verify that the interface installation job C1RPCNFG executed without any errors.
C1R109E
A valid ETSOLIB DCB address was not provided
Reason:
The ETSOLIB declaration may not have been made when your site's JCL brought up the Roscoe
application.
Action:
Check your site's JCL for bringing up the Roscoe application. Insure that the ETSOLIB declaration has
been made. Once the declaration has been made, reinitialize the interface by restarting the Roscoe
region.
C1R110E
Load of ENDEVOR service routine failed
Reason:
The interface initialization task, C1RPCTRL, was unable to load one or more CA Endevor® SCM
programs. The interface will terminate with a return code 16.
Action:
Refer to the Roscoe message log to determine the program that could not be executed. Verify that
the Roscoe execution JCL contains the appropriate CA Endevor® SCM and interface libraries in the
JOBLIB/STEPLIB/ETSOLIB concatenation.
C1R115E
Attach of the CA Roscoe Interface server failed
Reason:
The interface initialization task, C1RPCTRL, was unable to attach one of the interface server tasks. The
interface will terminate with a return code 16.
Action:
Verify that program C1RPSRVR is in the STEPLIB/JOBLIB concatenation. If not, update the Roscoe
04-May-2018 212/1109
CA Endevor® SCM - 17.0
Verify that program C1RPSRVR is in the STEPLIB/JOBLIB concatenation. If not, update the Roscoe
execution JCL to include the appropriate interface load library.
C1R118E
CA Roscoe Interface has been forced unavailable
Reason:
The interface has been disabled because all of the defined CA Endevor® SCM servers have
unexpectedly terminated. Message C1R103E is issued when a server terminates abnormally.
Action:
In order to reestablish the interface, the interface will have to be reinitialized by restarting the
Roscoe region.
C1R119I
CA Roscoe Interface session statistics: Users connected=count, Server dispatches=count Max
servers used=count Server ABENDs=count WAITs for server=count WAITs for dispatch queue=count
Reason:
The interface has received and processed the QUIE command. The message identifies interface server
statistics. The statistics can be used to tune the number of interface servers defined by the
C1RMCNFG configuration macro.
Action:
C1R120E
No CA Roscoe Interface servers requested. The interface is not available
Reason:
The number of servers specified on the C1RMCNFG macro SERVERS parameter was zero. Without any
servers defined, the interface cannot perform any work.
Action:
Rebuild the interface configuration module by reassembling the C1RMCNFG macro. Refer to
installation job C1RPCNFG. Specify at least one server on the SERVER macro parameter. Reinitialize
the interface.
04-May-2018 213/1109
CA Endevor® SCM - 17.0
C1R122I
CA Roscoe Interface shutdown complete
Reason:
The interface SHUT command was entered. The interface servers have completed shutdown
processing. The interface is no longer available.
Action:
C1R201E
No storage available for the Server control block
Reason:
An error occurred initializing the CA Endevor® SCM environment. Program C1BMINIT passed a non-
zero return code. The interface server initialization will terminate with an error code of 202.
Action:
Refer to the Roscoe message log for any other error messages that may have been issued by CA
Endevor® SCM. Refer to the corrective action for those messages. Restart the Roscoe region to
reinitialize the interface. If the problem persists, contact Technical Support at http://ca.com/support (
http://www.ca.com/support).
C1R202E
Error in C1BMINIT initializing the server
Reason:
An error occurred in C1BMINIT while initializing the CA Endevor® SCM environment. Program
C1BMINIT passed a non-zero return code. The interface server initialization will terminate with an
error code of 202.
Action:
Refer to the Roscoe message log for any other error messages that may have been issued by the CA
Endevor® SCM initialization program. Refer to the corrective action for those messages. If cause
cannot be determined, contact Technical Support at http://ca.com/support (http://www.ca.com/support
).
04-May-2018 214/1109
CA Endevor® SCM - 17.0
C1R203E
Error initializing access to the CA Roscoe library
Reason:
The interface server received a non-zero return code from the Roscoe LIBI INITX service. The
interface server initialization will terminate with an error code of 203.
Action:
Refer to the Roscoe message log for any other error messages that may have been issued by the
Roscoe library service routines. Refer to the corrective action for those messages. Restart the Roscoe
region to reinitialize the interface. If the problem persists, contact Technical Support at http://ca.com
/support (http://www.ca.com/support).
C1R205E
CIRPSRV2 abend-code ABEND occurred
Reason:
The interface server abended while processing a request. The server was able to recover from the
action.
Action:
C1R301E
Error occurred during ETSO function-name request. R14 (register 14), R12 (register 12), R15
(register 15)
Reason:
The interface dialog driver program CIRPUSER encountered a problem while executing a Roscoe ETSO
function. The dialog driver will terminate with an error code 4.
Action:
Retry the function that caused the message. If the problem persists, contact Technical Support at
http://ca.com/support (http://www.ca.com/support).
04-May-2018 215/1109
CA Endevor® SCM - 17.0
C1R302E
Error occurred during C1RPLINK service name request of request name
Reason:
The internal PSILINK service returned a non-zero return code while processing the service identified.
The interface will terminate.
Action:
Retry the function that caused the message. If the problem persists, contact Technical Support at
http://ca.com/support (http://www.ca.com/support).
C1R303E
Error connecting to the Endevor server
Reason:
The interface dialog driver program, C1RPUSER, was unable to connect to an interface server. The
dialog driver will terminate with an error code 12.
Action:
Check the Roscoe message log to verify that the interface servers initialized. Message C1R101I will
indicate the number of servers that initialized. If the servers failed to initialized, perform the
corrective action associated with any server initialization error messages.
C1R304E
The Endevor server ABENDed during processing
Reason:
The interface server abended while processing a request from the dialog driver. Message C1R103E
should appear in the Roscoe message log to identify the ABEND code. The dialog driver will terminate
with an error code of 16.
Action:
Refer to the corrective action for message C1R103E and retry the function that caused the error. If
the problem persists, contact Technical Support at http://ca.com/support (http://www.ca.com/support)
.
04-May-2018 216/1109
CA Endevor® SCM - 17.0
C1R305E
No storage available for the UCT
Reason:
The interface dialog driver was unable to acquire the storage needed for an internal data structure.
Each active dialog user requires approximately 12K of 31 bit addressable storage for the UCT. The
dialog driver will terminate with an error code of 20.
Action:
Increase the REGION size assigned to the Roscoe task and restart the region in order to reinitialize the
interface.
C1R306E
Error during Endevor Environment processing
Reason:
An internal error occurred while processing the CA Endevor® SCM Environment supplied on a dialog
panel. The dialog driver will terminate with an error code of 24.
Action:
Verify that the Environment name specified is valid and retry the function that generated the error
message. If the problem persists, contact Technical Support at http://ca.com/support (http://www.ca.
com/support).
C1R307E
Error during Endevor System processing
Reason:
An internal error occurred while processing the CA Endevor® SCM System supplied on a dialog panel.
The dialog driver will terminate with an error code of 28.
Action:
Verify that the System name specified is valid and retry the function that generated the error
message. If the problem persists, contact Technical Support at http://ca.com/support (http://www.ca.
com/support).
04-May-2018 217/1109
CA Endevor® SCM - 17.0
C1R308E
Error during Endevor Subsystem processing
Reason:
An internal error occurred while processing the CA Endevor® SCM Subsystem supplied on a dialog
panel. The dialog driver will terminate with an error code of 32.
Action:
Verify that the Subsystem name specified is valid and retry the function that generated the error
message. If the problem persists, contact Technical Support at http://ca.com/support (http://www.ca.
com/support).
C1R309E
Internal error code occurred. Execution has terminated
Reason:
An internal logic error occurred while processing a dialog selection panel. The code value identifies
the type of error that occurred. The dialog driver will terminate with an error code of 36.
Action:
Retry the function that generated the error message. If the problem persists, contact Technical
Support at http://ca.com/support (http://www.ca.com/support).
C1R311E
The CA Roscoe Interface server interface has not been initialized
Reason:
The interface dialog has determined that the interface servers have not been initialized in the Roscoe
region. The dialog will terminate with an error code of 40.
Action:
Verify that the interface control task, C1RPCTRL, has been properly installed. If the interface has been
properly installed, refer to the Roscoe message log to determine if any error messages were issued
during the server initialization process and perform the corrective action associated with those
messages.
04-May-2018 218/1109
CA Endevor® SCM - 17.0
C1R312E
Error during Endevor Element processing
Reason:
An internal error occurred while processing the CA Endevor® SCM Element supplied on a dialog
panel. The dialog driver will terminate with an error code of 44.
Action:
Verify that the Element name specified is valid and retry the function that generated the error
message. If the problem persists, contact Technical Support at http://ca.com/support (http://www.ca.
com/support).
C1R313E
Error during Endevor Level processing
Reason:
An internal error occurred while processing a CA Endevor® SCM Summary of Levels request. The
dialog driver will terminate with an error code of 48.
Action:
Retry the function that generated the error message. If the problem persists, contact Technical
Support at http://ca.com/support (http://www.ca.com/support).
C1R314E
Error during BROWSE processing. RC=return code
Reason:
An internal error occurred while processing the BROWSE request. The return code field identifies the
return code passed by the interface server BROWSE function. The dialog driver will terminate with an
error code of 32.
Action:
Retry the BROWSE function. If the problem persists, contact Technical Support at http://ca.com
/support (http://www.ca.com/support).
04-May-2018 219/1109
CA Endevor® SCM - 17.0
C1R316E
Error during member processing. RC=return code
Reason:
An internal error occurred while processing the member request on behalf of the dialog driver. The
return code field identifies the return code passed by the interface server function. The dialog driver
will terminate with an error code of 60.
Action:
Refer to the Roscoe message log for any other error messages. If the problem cannot be resolved,
contact Technical Support at http://ca.com/support (http://www.ca.com/support).
C1R318E
The CA Roscoe Interface is not available
Reason:
Action:
Check the Roscoe message log for any errors that might indicate the cause. Reinitialize the interface
by restarting the CA Roscoe region. If the problem persists, contact Technical Support at http://ca.
com/support (http://www.ca.com/support).
C1R319E
Error during Endevor element type processing
Reason:
An internal error occurred while processing a Type List request. The dialog driver will terminate with
an error code of 72.
Action:
Retry the function that generated the error message. If the problem persists, contact Technical
Support at http://ca.com/support (http://www.ca.com/support).
C1R320E
Error during Endevor processor group processing
04-May-2018 220/1109
CA Endevor® SCM - 17.0
Reason:
An internal error occurred while processing a Processor Group request. The dialog driver will
terminate with an error code of 76.
Action:
Retry the function that generated the error message. If the problem persists, contact Technical
Support at http://ca.com/support (http://www.ca.com/support).
C1R502E
The CA Roscoe Interface was not quiesced
Reason:
The REST command was entered but a previous QUIE command had not been entered. The dialog will
terminate with an error code of 72.
Action:
None.
C1R503I
The CA Roscoe Interface posted to restart
Reason:
The interface REST command was entered. The dialog has requested each server to restart
processing. The interface servers will begin accepting service requests.
Action:
None.
C1R507I
The CA Roscoe Interface posted to shutdown
Reason:
The interface SHUT command was entered and has been successfully processed. The interface
servers have been told to stop processing.
Action:
None. Message C1R122I will be issued when the servers have stopped processing.
04-May-2018 221/1109
CA Endevor® SCM - 17.0
C1R504E
The CA Roscoe Interface is not active
Reason:
The interface QUIE, SHUT or REST command was specified but the interface has not been initialized in
the Roscoe region. The dialog will terminate with an error code of 76.
Action:
Verify that the interface control task, C1RPCTRL, has been properly installed. If the interface has been
properly installed, refer to the Roscoe message log to determine if any error messages were issued
during the server initialization process and perform the corrective action associated with those
messages.
C1R505I
CA Roscoe Interface has been marked unavailable
Reason:
The QUIE command was entered and has been successfully processed. The interface servers will not
accept any more requests.
Action:
C1R506E
Invalid command specified. No action was taken
Reason:
The interface was started with an optional command specified on the command line. The command
entered is invalid. The dialog will terminate with an error code 80.
Action:
Reinvoke the dialog with a valid command. Valid commands are REST, QUIE and SHUT or by not
specifying a command on the command line.
04-May-2018 222/1109
CA Endevor® SCM - 17.0
Contents:
The CA Endevor CA Roscoe Interface lets you perform CA Endevor SCM functions in a CA Roscoe
Interactive Environment. You can display and retrieve elements, display the footprints in source,
object or load libraries, and build batch requests using the CA Endevor SCM Software Control
Language (SCL). You can also edit batch requests, build JCL and submit jobs.
The interface is initialized with other user applications during CA Roscoe IE startup, and remains
ready for use until the CA Roscoe IE application is terminated by an operator command from the
console.
All applications that are to be executed under ETSO must be defined in a load library known to ETSO
and the Eligible Program List (EPL).
You are using release 6.0 or later of Advantage CA Roscoe Interactive Environment.
04-May-2018 223/1109
CA Endevor® SCM - 17.0
5. Modify ROSXINIT.
SERVERS= Must be set to 1. If another number is used, at initialization time, the server number is
reset back down to 1.
PPFX= Indicates the prefix of the Roscoe panel library. The default is ' C1'. You should change this to
the prefix used for the Roscoe execution library that exists at your site.
SPFX= Indicates the scratchpad work area prefix. The SPFX parameter is optional. If it is not specified,
or specified as blank, the scratchpad work area will be allocated in the user's directory. If specified, it
must be two or three characters long and must identify a prefix whose work area can be updated by
any Roscoe user.
The initialization user exit is called C1RPUX00. This module is loaded into memory during the startup
phase of the interface. The exit is responsible for providing the Roscoe Interface user interface
program with an eight character, blank padded user ID that is associated with the current Roscoe
user. CA provides the following three sample user exits in the iprfx.iqual.CSIQOPTN.
C1RPUX00. This exit can be used if your installation is running Roscoe with the EXTSEC=RACF or
EXTSEC=TOPSECRET enabled. The routine returns the security ID that is located in the ACEE
associated with the current Roscoe user. No changes have to be made to the exit if your
installation meets these criteria.
C1RPUX01. This is a dummy exit that must be coded if C1RPUX00 cannot be used in your
installation. The exit contains only the entrance and exit linkage code. You must add the
necessary logic to extract the appropriate user ID, then save the user ID in the area provided for
the exit. If you code your own exit, rename C1RPUX01 to C1RPUX00 and make the appropriate
changes.
04-May-2018 224/1109
CA Endevor® SCM - 17.0
C1RPUX02. This exit can be used if your installation is running Roscoe with ACF2 enabled. The
routine returns the logon ID found in the SCBACFB field. This field is initialized by ACF$ EXIT (ACF2
EXIT). If this exit meets your installation needs, re-name C1RPUX02 to C1RPUX00.
The installation user exit passes the address of a one word parameter list in register 1. The parameter
list points to an eight byte field into which the exit places the user ID associated with the current
Roscoe user. The user ID must be padded to the right with spaces if it is less than eight characters
long.
The exit passes one of the following return codes in register 15:
R15 = 0, if the exit has placed the user ID in the output field provided.
R15 = 4, if the exit was unable to place the user ID in the output field provided.
If the exit routine passes a non-zero return code or if the user ID provided by the exit is blanks, the
Roscoe Interface will disable the foreground Retrieve action. If a user attempts to perform a
foreground Retrieve when the action has been disabled, you receive the following message:
'RETRIEVE disabled by the user exit'.
The user exit CSECT must be called C1RPUX00. The routine must be reentrant and reusable and able
to execute in AMODE(31).
To assemble and link the user exit, use the JCL located in data set iprfx.iqual.CSIQJCL in member
BC1JRXIT.
Note: If you are on ACF2 release 6.1 or greater, C1RPUX02 is not required, use C1RPUX00.
Add the following entries to the EPL for your site. Remember that each EPL entry must be in
alphabetical order. They are listed by column, contents and comments.
04-May-2018 225/1109
CA Endevor® SCM - 17.0
Note: Memory allocations can be reduced if your system is storage constrained. If a value specified is
too small, the interface user may experience an out of memory condition when building large CA
Endevor SCM selection lists. In addition, CA Endevor SCM acquires most of its storage from above the
16 MB line.
By default, ETSO expects all of the applications called by the terminal user to be located in the load
library assigned to the DDNAME ETSOLIB. However, if the Roscoe JCL contains ETSSRCH=ALL, the
application load modules may be located in ETSOLIB (or a data set concatenated to it), JOBLIB or
STEPLIB (or a data set concatenated to it), the Link Pack Area or a data set defined in the linklist
concatenation.
Note: For more information, see the Roscoe System Reference Manual SR-40-10-AO.
1. If not running from a LINKLIST, update the JCL for the Roscoe application at your site by
adding the following CONLIB or STEPLIB statements before the ETSOLIB declaration:
//STEPLIB DD DSN=iprfx.iqual.CSIQAUTU,DISP=SH
// DD DSN=iprfx.iqual.CSIQAUTH,DISP=SHR
// DD DSN=uprfx.uqual.RSCOLOAD,DISP=SHR
// DD DSN=iprfx.iqual.CSIQLOAD,DISP=SHR
.
.
.
//CONLIB DD DSN=uprfx.uqual.RSCOLOAD,DISP=SHR
// DD DSN=iprfx.iqual.CSIQLOAD,DISP=SHR
04-May-2018 226/1109
CA Endevor® SCM - 17.0
Specify the name of the CONLIB you created in the step Populate SMP/E and CA Endevor SCM
for Roscoe Install Data Sets, and the name of the CA Endevor SCM CONLIB for your site.
2. Define the Roscoe Interface load modules to Roscoe by adding the following loadlib
statements within the ETSOLIB declaration:
// DD DSN=iprfx.iqual.CSIQAUTU
// DD DSN=iprfx.iqual.CSIQAUTH
// DD DSN=uprfx.uqual.RSCOLOAD
// DD DSN=iprfx.iqual.CSIQLOAD
Modify ROSXINIT
In this step, you modify the ROSXINIT macro. You must indicate that the interface control module
C1RPCTRL must be executed upon startup of the Roscoe application. To do this, include the following
entry in the ROSXINIT macro. Then reassemble this macro into the Roscoe loadlib for your site.
Note: The MON option is omitted, causing ROSXINIT to always attempt to execute C1RPCTRL. No
corresponding entry in ROSXTERM is required. Due to storage considerations, it is recommended that
C1RPCTRL be placed near the top of the initialization list in ROSXINIT.
Edit NDVR
Before moving the RPFs, you must edit the NDVR members to indicate your site-specific Roscoe index
and system libraries in the included ROSDATA step. The number of these libraries is site-specific and
may be more than the five files shown in bold next.
You must also edit RPF NDVRRPF and NDVRROSC to indicate the name of the panel library (iprfx.iqual.
CSIQPENU) you created in the step Populate SMP/E and CA Endevor SCM for Roscoe Install Data Sets.
04-May-2018 227/1109
CA Endevor® SCM - 17.0
FILL 10 255 / /
DELX 1 3 /C1R/
R 1 1
For NDVRROSC, edit the lines shown in bold next to conform to your site's requirements:
'//ROSCOPY EXEC PGM=ROSCOPY,PARM=''' &lor. S.KEY &lor. ''' '
'//STEPLIB DD DISP=SHR,DSN=uprfx.ROSLIB '
'//ROSLIB00 DD DISP=SHR,DSN=uprfx.ROSLIBOO '
'//ROSLIB01 DD DISP=SHR,DSN=uprfx.ROSLIBO1 '
'//ROSLIB02 DD DISP=SHR,DSN=uprfx.ROSLIBO2 '
'//ROSLIB03 DD DISP=SHR,DSN=uprfx.ROSLIBO3 '
'//SYSPRINT DD SYSOUT=* ' '//*SYSLIST DD SYSOUT=* '
'//SYSOUT DD DSN=&&NDVRADD('&lor.L6&lor.')'
'// DISP=(OLD,PASS) '
After editing is complete, move the RPFs to the execution/public RPF library. The share options of
these RPFs should be execute-only.
Sign on to the execution/public library and execute the RPF NDVRRPF. This RPF will import all
interface panels from the partitioned data set iprfx.iqual.CSIQPENU to the ROSCOE execution/public
library.
Note: If the message above is not seen in the z/OS Console log, then the interface server is not
available. Return to the step Modify ROSXINIT and check the output for error messages.
This procedure requires Roscoe administrator authority. You must use the Roscoe control account
(R0) to logon to Roscoe. The Roscoe logon screen appears.
1. Type NDVR and press Enter. The Primary Options Menu appears.
2. Type 5 (SYSTEM PROFILE) and press Enter. (Only authorized administrators receive the full
panel with the 5 option.) The interface System Profile Maintenance menu appears.
3. Type the following data set name and then press Enter. Be sure to include the member name
C1SB300R.
04-May-2018 228/1109
3. CA Endevor® SCM - 17.0
iprfx.iqual.CSIQJCL(C1SB300R)
4. Review the batch JCL to make sure that it conforms to your site specifications, updating the
variables as noted in the step Allocate and Initialize the SMP/E Environment and CA Endevor
SCM Data Sets.
You can make Roscoe quiescent to keep users who are not logged on from starting the interface.
All users who are logged on are allowed to finish the session.
Important! To bring up the interface after a shutdown, you must recycle the Roscoe application.
1. Use the CA Roscoe IE control account (RO) to logon to Roscoe. The CA Roscoe IE logon screen
appears.
2. Type NDVR QUIE and press Enter. You receive the following message:
3. To restart CA Roscoe IE, type NDVR REST and press ENTER. You receive the following
message:
1. Use the Roscoe control account (RO) to logon to Roscoe. The Roscoe logon screen appears.
2. Type NDVR QUIE and press Enter. You receive the following message:
3. Type NDVR SHUT and press Enter. This command terminates the interface. You receive the
following message:
You also receive a console message when the shutdown is complete. Once you issue the
'SHUT' command, session statistics are written to the operator console. To view the statistics,
access the system log. The log will contain statistics similar to the following:
04-May-2018 229/1109
CA Endevor® SCM - 17.0
4. To bring up the interface after a shutdown, recycle the Roscoe application according to the
procedures used at your site.
04-May-2018 230/1109
CA Endevor® SCM - 17.0
How to Enable and Secure Concurrent Action Processing (see page 231)
Review Prerequisites (see page 233)
Concurrent Action Processing Overview (see page 235)
Enable Spawn Parameters for CAP (see page 239)
Enable the CAICCI Spawn Facility for CAP (see page 240)
Verify CA Common Services are Running (see page 243)
Setting Up Security for CAP (see page 243)
How to Activate Concurrent Action Processing (see page 247)
How to Monitor Concurrent Action Processing (see page 251)
To enable CAP, the CA Endevor® SCM administrator requires the assistance of the following roles:
CA Common Services (CCS) administrator (or systems programmer): This role is required to
enable the CCS Common Communications Interface (CAICCI) Spawn facility for CAP.
Security administrator: This role is required to configure your site security software to allow the
spawn facility to function for CAP. This role is also required if you want to limit who can activate
CAP.
To set up this feature, you need your CCS administrator (or systems programmer) and your site
security administrator. Optionally, you can limit who can use CAP.
This diagram shows how you enable CAP and, optionally, how you secure user access to CAP.
04-May-2018 231/1109
CA Endevor® SCM - 17.0
3. Ask your CCS administrator to perform the task Enable the CAICCI Spawn Facility for CAP.
Also, ask them to let you know when they have completed this task.
4. Ask your Security administrator to perform the task Enable Spawn for CAP in Security
Software. Also, ask them to let you know when they have completed this task.
CCS administrator
This role completes the following steps:
04-May-2018 232/1109
CA Endevor® SCM - 17.0
2. Inform the CA Endevor® SCM administrator that the CAICCI Spawn Facility for CAP task is
done.
Security administrator
This role completes the following steps:
1. Enable the spawn facility for CAP in your security software. Depending on the security
software in use at your site, complete one of the following tasks:
2. Inform the CA Endevor® SCM administrator that your site security software is configured to
enable the spawn facility CAP.
Optionally, you can limit who can use CAP. To secure user access to CAP, the following roles and tasks
are involved:
2. Ask your security administrator to enable user access to CAP in your security software. Also,
ask them to let you know when they have completed this task.
Security administrator
This role completes the following steps:
1. Enable users read access to CAP in your security software -- The security administrator
enables user access in the site security software to the pseudo data set that the CA
Endevor® SCM administrator defined as the security checkpoint for CAP. Details on how to
enable access to a data set are not included in the CA Endevor® SCM documentation,
because this is a usual procedure.
2. Inform the CA Endevor® SCM administrator that the task to enable user access to the CAP
data set is done.
Review Prerequisites
Before users can submit batch jobs or packages for Concurrent Action Processing, the following
prerequisites are required:
processed simultaneously. Global Type sequencing is required when using CAP. You can make
04-May-2018 233/1109
CA Endevor® SCM - 17.0
processed simultaneously. Global Type sequencing is required when using CAP. You can make
CAP more efficient by including a category definition for Types that can be processed
simultaneously. For more information about Global Type Sequencing, see How Global Type
Sequencing Affects Concurrent Action Processing (https://docops.ca.com/display/CE17
/Global+Type+Sequencing#GlobalTypeSequencing-
HowGlobalTypeSequencingAffectsConcurrentActionProcessing). For more information about enabling
Global Type Sequencing, see the scenario How to Enable Global Type Sequencing.
Before enabling CAP, the CA Endevor® SCM administrator must understand how CAP works to
properly set the spawn parameters. Review the following topics, which explain CAP processing:
Verify that the following CCS components are installed and running on your z/OS mainframe that
hosts CA Endevor® SCM:
CAIENF
The Event Notification Facility enables concurrent action processing through the component
CAICCI Communication Interface. If your site is running CAIENF r12 or higher, a database is not
required for CAP.
CAICCI
The Common Communications Interface is required only if you want to use CAP, Web
Services, the Eclipsed-Based UI, or CA CMEW.
Note: CA Endevor® SCM uses the CCS Resource Initialization Manager (CAIRIM)
component for product license authorization. CAIRIM is mandatory to run CA Endevor®
SCM, whether your site uses CAP or CA CMEW. For information about how to determine if
the components are installed, see Verify CA Common Services are Running (see page 243).
(Optional) Enable IBM z/OS VSAM Record Level Sharing (RLS) facility to manage your CA Endevor®
SCM VSAM data sets. These data sets include all Master Control Files (MCFs), Element catalog and
EINDEX, and the package data set.
RLS improves VSAM performance and, so, improves the performance of CAP.
Ensure that the C1DEFLTS referenced in the routing region JCL is the same as the C1DEFLTS
referenced in the procedure JCL for the action request regions.
04-May-2018 234/1109
CA Endevor® SCM - 17.0
Certain requirements apply to the SCL requests in the jobs that are submitted for processing. Element
names cannot be wildcarded. Additionally, the To and From statements on all Add, Update, and
Retrieve actions must reference cataloged data sets. For more information about SCL requests, see
SCL Requirements for CAP (see page 250).
CAP uses Global Type Sequencing to determine which actions can be processed simultaneously. The
CAP facility processes certain element actions of the same type concurrently, and must complete the
processing of all actions of the same type before starting to process elements of the next type.
However, any action types that are not defined in the Global Type Sequence can be processed
concurrently with any other action. The following actions can be processed concurrently: ADD,
ALTER, UPDATE, RETRIEVE, MOVE, GENERATE, DELETE, SIGNIN, and TRANSFER CA Endevor® SCM to
CA Endevor® SCM. All other actions on the request are processed serially.
The administrator can specify whether CAP is allowed and how many additional started tasks a single
job can create for concurrent processing. These parameters are set in the C1DEFLTS table. Through
the External Security Interface, the administrator can limit who is authorized to use CAP. This method
of processing is not initiated automatically; users must request CAP at the job level.
Note: CAP with CA CM Enterprise Workbench is available only for packages and enterprise
packages, not for element actions.
1. Any actions that are wildcarded or masked, are expanded and the actions are sorted in type
sequence order to create a chain of element action requests.
04-May-2018 235/1109
1. CA Endevor® SCM - 17.0
Note: Only use wildcarding or masking when you are submitting one action (for
example, all Add actions) in the same job, to avoid unpredictable results.
2. Any actions that use an archive file as input, such as RESTORE, LIST from archive file, and
TRANSFER, are executed serially in the routing region. These actions run serially in the routing
region.
3. Before execution of other actions, CA Endevor® SCM determines whether CAP is enabled and
the user is authorized in the following order:
b. If Global Type Sequencing is enabled, the request JCL is examined for the presence of
an EN$CAP or EN$CAPnn DD card. These parameters indicate whether the JCL
requests Concurrent Action Processing.
c. If the JCL requests CAP, the C1DEFLTS parameters SPAWN and SPAWNCNT values are
checked to see if CAP is enabled.
d. A check is made through the External Security Interface to determine whether the user
is authorized to request Concurrent Action Processing.
If any of these conditions are not met, all actions are processed serially.
4. If CAP was requested and is permitted as verified in step 3, the chain of action requests that
remains from step 1 and 2 is examined. Any ADD, UPDATE, or RETRIEVE requests found in the
chain are then preprocessed as follows.
a. Any DDNAME is translated to a data set name; that is, the DDNAME is localized. These
data set names are created in the following manner.
However, in an action request region that is created for CAP, CA Endevor® SCM may
eliminate the DALDSNAM for some temporary data sets. This action causes a name to
be generated with the following form, which is unique:
04-May-2018 236/1109
CA Endevor® SCM - 17.0
Note: For temporary data sets created and deleted in the same processor
step (that is, allocated with DISP=(NEW,DELETE,DELETE), or with no DISP at
all), the DALDSNAM is not eliminated. This means that such data sets are
always generated as SYSyyddd.Thhmmss.RA000.jobname.dsname.Hnn,
even with Concurrent Action Processing. Therefore, contention is still
possible with such data sets.
b. The data set specified (using the DSNAME or DDNAME parameter) is checked to
determine if it is a cataloged data set. If any data set refers to an uncataloged file (for
example, a SYSIN/SYSOUT data set, a temporary data set or a non-SMS data set with a
disposition of NEW), CAP cannot be enabled, and the actions are processed serially.
Important: If you use exit 4 programs to alter input and output files before
the execution of an ADD, UPDATE, or RETRIEVE action, the data sets
specified in the SCL must be cataloged data sets. This requirement applies
even if the user has an exit 4 program that changes the data set names.
5. Action request regions are created equal to the SPAWNCNT value set in the C1DEFLTS table.
However, if the SPAWNCNT value was overridden on the job request, that value is used to
determine the maximum number of action request regions. The value can be changed for a
specific job in the following manner:
For batch requests, by using the EN$CAPnn DD card on a batch job request JCL.
For foreground requests, by using the Concurrent Number field on the Submit Package
panel or the Batch Options Menu.
Note: If CA Endevor® SCM is called from a processor, it will not create any servers. In addition,
if an action request region is created during concurrent action processing, it will not create
additional servers.
6. The actions ADD, ALTER, UPDATE, RETRIEVE, MOVE, GENERATE, DELETE, SIGNIN, and
TRANSFER (CA Endevor® SCM to CA Endevor® SCM) are dispatched to action request regions.
Actions that can be processed simultaneously are routed from the routing region of the
originating job to the action request regions and processed concurrently.
The routing region is the batch job, TSO session, or CA CM Enterprise Workbench session
that has requested that actions be processed concurrently.
Action request regions are the started tasks that are created to process the actions.
Multiple action request regions are created. They receive individual action requests from
the routing region, process them, and send the results back.
CAP uses Global Type Sequencing to determine which actions can be processed
simultaneously. Global Type Sequencing determines whether actions can be processed
concurrently. Elements in the same type sequence can be processed concurrently. Also,
elements that are not listed in the global type sequence can be processed concurrently with
any element. There is no guarantee that actions on elements in the same type sequence (or
04-May-2018 237/1109
CA Endevor® SCM - 17.0
any element. There is no guarantee that actions on elements in the same type sequence (or
on elements that are not type sequenced) are processed in the order in which they appear in
the SCL. However, actions against the same element name are processed serially and in the
order in which they appear in the SCL, provided the element names are explicit. One action
must complete before the next is dispatched.
Note: If you specify AUTOGEN, SCL requests are fully resolved based on current
inventory contents before any actions are processed. For example, suppose that
you have a GENERATE action with the AUTOGEN option and several MOVE actions
in the same request. The MOVE actions do not include any of the additional
elements that are copied back as a result of the GENERATE action.
7. After all other actions have completed processing, the actions PRINT, ARCHIVE, LIST, and
TRANSFER to archive data set are performed serially in the routing region.
Important: Specifying a category in the Global Type Sequencing table does not affect how
sequenced Type and nonsequenced Type requests are built and sorted. The category only
affects how the actions are dispatched by Concurrent Action Processing.
1. When CA Endevor® SCM is dispatching element actions to process concurrently, it refers both
to the Type and to the category associated with the Type when deciding which action
requests to dispatch.
a. If the next request in the sequenced Type chain contains the same category value as
the previous request, that element action can be dispatched to an available STC.
With categories, CA Endevor® SCM continues dispatching element actions from the
sequenced Type chain as long as the category value matches the previous request.
Available STCs only have to wait if sequenced Type requests from one category value
are still processing and there are no non-sequenced Type requests to process.
b. If the next request does not have the same category value, CA Endevor® SCM attempts
to dispatch a request from the nonsequenced Type chain.
Without categories, element actions of the next sequenced Type number have to wait
until all actions of the previous sequenced Type have completed processing.
Nonsequenced Type element actions are then dispatched as STCs become available or
after all the sequenced Type requests are dispatched. Available STCs remain idle if
there are sequenced Type requests still processing, and there are no requests from the
nonsequenced Type chain to process.
04-May-2018 238/1109
CA Endevor® SCM - 17.0
2. When all the requests have been processed for a particular sequenced Type and category, CA
Endevor® SCM begins processing requests for the next sequenced Type.
3. When all requests from the sequenced Type chain have been completed, any remaining
requests from the nonsequenced Type chain are then dispatched.
SPAWNCNT=n
Specifies the default number of spawned regions that are started when CAP is used. Valid
values are 2 through 99, but it cannot exceed the value of the parameter SPAWNMAX. The
field can also be set to 0 to disable CAP when SPAWN=Y. If SPAWN=N, SPAWNCNT must
be set to 0.
SPAWNMAX=n
Specifies the maximum number of tasks that a single job can spawn. Valid values are 2
through 99. The field can also be set to 0 to disable CAP if SPAWN=Y. If SPAWN=N,
SPAWNMAX must be set to 0.
SPAWNPROC=CAP_server_name
Specifies the one to eight-character name of the CAP server. This name must be a CAICCI
SERVICE definition service_name and a started task procedure name. A name is only
required if the SPAWN=Y.
If SPAWN=Y and SPAWNCNT=0, CAP is disabled. However, users can override the SPAWNCNT
value for a specific job by using the EN$CAPnn DDNAME on the job request JCL. However,
users cannot override the SPAWNMAX value.
Press End.
Your changes to C1DEFLTS are saved. The spawn parameters are set according to your
preferences. The Edit session ends and the Edit Entry Panel opens.
4.
04-May-2018 239/1109
CA Endevor® SCM - 17.0
4. Complete the fields to select the BC1JTABL member located in the installation library iprfx.
iqual.CSIQJCL. Press Enter.
The sample JCL BC1JTABL opens in an ISPF Edit panel.
5. Edit the sample JCL BC1JTABL found in iprfx.iqual.CSIQJCL to your installation standards.
Execute the job.
The Defaults table is assembled, link-edited, and stored as member C1DEFLTS in your
authorized user library, iprfx.iqual.CSIQAUTU. The spawn parameters are enabled for CAP
processing. However, CAP cannot be used until the CAICCI Spawn Facility is enabled for CAP.
Note: Instead of steps 4 and 5, you can assemble and link-edit C1DEFLTS using an SMP/E
USERMOD.
In this example, the C1DEFLTS table's spawn parameters are set to enable CAP. The spawn facility for
CAP is activated, because SPAWN=Y. When CAP is used, CAICCI uses the spawn procedure ENDEVOR.
Eight spawn regions are started and one job can spawn a maximum of 99 address spaces.
SPAWN=Y ACTIVATE THE SPAWN FACILITY
SPAWNCNT=8, SPAWN COUNT
SPAWNMAX=99, MAXIMUM SPAWN COUNT
SPAWNPROC=ENDEVOR, NAME OF SPAWN PROC
Note: Ask your CA Common Services administrator (or systems programmer) to enable the CAICCI
Spawn Facility for CAP. Also ask the administrator to let you know when they have successfully
completed this task.
Ask your CCS administrator (or systems programmer) to enable the CAICCI Spawn Facility for CAP.
Also, ask the administrator to let you know when they have completed this task.
A CAP spawn parameter definition file must be appended to the SPNPARMS DD in the CA Event
Notification Facility (CAIENF) procedure.
The spawn parameter file must be customized. The customization specifies the started task to
enable the spawn facility to spawn address spaces in the z/OS environment where CA Endevor®
SCM is installed.
04-May-2018 240/1109
1.
CA Endevor® SCM - 17.0
Note: If CAIENF is not in the CAI.CAIPROC library, your system administrator could
have copied the CAIENF member to your system PROCLIB.
2. Append the CAP spawn parameter file definition named SPNPARMS DD to the CAIENF
procedure JCL. For example, in the sample JCL below, you add and customize the two lines in
bold.
//ENF PROC OPTLIB='SYS2.CA90S.PARMLIB',
// ENFDB='SYS2.CA31.ENFDB',
// ENFPARM=ENFPRM31,
// SPNPAR1=SPWNSNMP,
// SPNPARn=ndvspawn,
// CCIPARM=CCIPCA31,
// ENFCMDS=ENFCMD31,
//ENF EXEC PGM=CAS9MNGR,TIME=1440
//CASRT01 DD UNIT=SYSDA,SPACE=(CYL,(5,1))
//CASRT02 DD UNIT=SYSDA,SPACE=(CYL,(5,1))
//CASRT03 DD UNIT=SYSDA,SPACE=(CYL,(5,1))
//CASRT04 DD UNIT=SYSDA,SPACE=(CYL,(5,1))
//CASRT05 DD UNIT=SYSDA,SPACE=(CYL,(5,1))
//SPNPARMS DD DISP=SHR,DSN=&OPTLIB(&SPNPAR1)
// DD DISP=SHR,DSN=&OPTLIB(&SPNPARn)
//SPNPRINT DD SYSOUT=X
//SPNDEBUG DD SYSOUT=X
//SRVDEBUG DD SYSOUT=X
//ENFDB DD DISP=SHR,DSN=&ENFDB
//ENFPARMS DD DISP=SHR,DSN=&OPTLIB(&ENFPARM)
// DD DISP=SHR,DSN=&OPTLIB(&CCIPARM)
//ENFCMDS DD DISP=SHR,DSN=&OPTLIB(&ENFCMDS)
//SYSPRINT DD SYSOUT=X
SPNPARn
Specifies a symbolic for a CAIENF parameter member. The value for n must be the next
sequential number in the list of parameter files for the spawn function.
ndvspawn
Specifies the spawn parameter file for CAP. Throughout this procedure, this file is named
ndvspawn. When you save the member in step 4, you can name the member as
appropriate for your site. However, ensure that you substitute that name wherever
ndvspawn is referenced in this procedure, including here in the SPNPARMS DD statement.
Press End.
Your changes are saved. The CAP spawn parameter file is defined to the CAIENF procedure for
CAICCI. The Edit session closes, and the Edit Entry panel opens.
3. Open the CAPCCI member, which is located in the installation source library iprfx.iqual.
CSIQOPTN, in an ISPF Edit panel.
4. Customize the spawn parameters by editing the following CAICCI SERVICE and PROCESS
statements in the CAPCCI file. Verify that the procname and the task name are the same. Keep
the statements in the exact format provided in the sample file, maintaining spaces and
column alignments.
********************************************************************
* CCI SERVICE STATEMENTS FOR ENDEVOR
********************************************************************
ENDEVOR SERVICE SERVER_NAME=MVS_START_SERVER,
DEALLOCATE=TERMINATE,
LOST_CLIENT=DEALLOCATE,
04-May-2018 241/1109
CA Endevor® SCM - 17.0
LOST_CLIENT=DEALLOCATE,
MAX#_SERVICES=100,
MAX#_CLIENTS=1,
MAX#_PROCESSES=100,
SERVICE_UNAVAILABLE=START_SERVICE,
START=SPAWN_ONLY,
SIGNON/NOPASSCHK=SERVICE
********************************************************************
* CCI PROCESS STATEMENTS FOR ENDEVOR
********************************************************************
PROCESS PROCESS_TYPE=MVS_STC,
PROCNAME=ENDEVOR,
SERVICE statement
Specifies the host application.
PROCESS statement
Specifies the JCL procedure that executes CA Endevor® SCM.
PROCNAME=procname
Specifies the name of the started task procedure that the Spawn facility initiates. For
example, PROCNAME=ENDEVOR.
Enter the Save command and specify a name for the spawn parameter file for CAP
(ndvspawn).
The CAP spawn parameter file (ndvspawn) is customized to specify the started task procedure
that CAICCI can use to spawn address spaces for CAP. Your changes are saved. The Edit
session closes, and the Edit Entry panel opens.
5. Save the customized file in your CAI.PARMLIB data set as the member ndvspawn.
The file is now saved in a location where CAICCI can use it to spawn address spaces for CAP.
6. Open the ENDEVOR member, which is located in the CSIQJCL library that is delivered with CA
Endevor® SCM, in an ISPF Edit panel.
7. Edit the sample ENDEVOR started task procedure as appropriate for your site. Enter Copy on
the command line and specify the PROCLIB defined to JES where you want to copy the file.
Your changes are saved. The started task procedure ENDEVOR is available to spawn the
address spaces where multiple element actions can be processed simultaneously. The Edit
session closes, and the Edit Entry panel opens.
Note: If you use a PROC name other than ENDEVOR, update the other locations where the
PROC name is used. Verify the SPAWNPROC parameter in the C1DEFLTS table and the
CAICCI Service name and CAICCI PROC in the PROCLIB member all contain the same value.
This parameter is also the same name as the PROCNAME= value specified in the CAICCI
definitions.
04-May-2018 242/1109
CA Endevor® SCM - 17.0
You have now enabled the CAP to speed the processing of batch jobs and packages.
Inform your CA Endevor® SCM administrator to let them know that the CAICCI SPAWN facility is in
effect for CAP.
Note: If you do not see ENF* active on your system, contact your systems
programmer to start it.
2. If the job is running, select it and search for (Find) CAICCI within the job.
If you do not find CAICCI, check your site CAI.CAIPROC library to see if the ENF member
has been modified to run CAICCI at your site.
If the ENF member does not exist, contact your CCS administrator (or systems
programmer) to determine the status of CAIRIM, CAIENF, and CAICCI on your system.
04-May-2018 243/1109
CA Endevor® SCM - 17.0
Important: In the following description ENDEVOR is used as both the SPAWNPROC started
task name and its corresponding user ID. If your site already has user ID ENDEVOR defined
as the alternate user ID, do not use ENDEVOR for your task name or task user ID. Instead,
select a different value. The alternate ID (ALTID) is defined in the C1DEFLTS table as
RACFUID=ENDEVOR.
1. Define a new facility name ENDEVOR for CAP. To do so, add the following definitions to the
Top Secret Security parameter file (specified by the PARMFIELD DD statement):
* USERnn FACILITY FOR
*
FAC(USERnn=NAME=ENDEVOR)
FAC(ENDEVOR=xxxx)
Where xxxx is any other facility control options to be set other than the defaults. The facility
can be defined dynamically using the TSS MODIFY command. For example:
TSS MODIFY(FAC(USERnn=NAME=ENDEVOR))
TSS MODIFY(FAC(ENDEVOR=xxxx))
The TSS MODIFY command is only valid until the next recycle of CA Top Secret.
CA Top Secret recommends that all started task (STC) ACIDs be given a password and that
OPTIONS(4) be set in the CA Top Secret parameter file. OPTIONS(4) eliminates the prompt for
a password when the STC starts. However, if someone tries to log on with the STC ACID, that
person must know the password.
The NODSNCHK, NORESCHK, and NOSUBCHK bypass attributes on the ENDEVOR ACID may be
required. If not, verify that the ACID is authorized to access all the files and resources it
requires.
4. Assign userid ENDEVOR as the default ACID for the CAICCI spawned task ENDEVOR:
TSS ADD(STC) PROCNAME(ENDEVOR) ACID(ENDEVOR)
5. Grant each user of CA SCM for Mainframe access to the ENDEVOR facility:
TSS ADD(USER-ID) FAC(ENDEVOR
Note: For more information about defining a new facility, see CA Top Secret Control
Options. For more information about the CRE and ADD commands, see CA Top
Secret Command Functions.
04-May-2018 244/1109
CA Endevor® SCM - 17.0
Important: In the following description ENDEVOR is used as both the SPAWNPROC started
task name and its corresponding user ID. If your site already has user ID ENDEVOR defined
as the alternate user ID, do not use ENDEVOR for your task name or task user ID. Instead,
select a different value. The alternate ID (ALTID) is defined in the C1DEFLTS table as
RACFUID=ENDEVOR.
1. Create an STC logon ID named ENDEVOR for the Concurrent Action Processing Started task:
ACF
INSERT ENDEVOR NAME(ENDEVOR) STC
2. Verify that the ENDEVOR logon ID is defined with site-specific logon ID fields such as those
fields used to create the UID string.
3. Verify that the ENDEVOR logon ID has access to all the data sets in the ENDEVOR task by
writing CA ACF2 security ACCESS rules for the logon ID.
Note: For more information about configuring CA ACF2, see the CA ACF2 Security
Administration Guide.
Important: In the following description ENDEVOR is used as both the SPAWNPROC started
task name and its corresponding user ID. If your site already has user ID ENDEVOR defined
as the alternate user ID, do not use ENDEVOR for your task name or task user ID. Instead,
select a different value. The alternate ID (ALTID) is defined in the C1DEFLTS table as
RACFUID=ENDEVOR.
04-May-2018 245/1109
CA Endevor® SCM - 17.0
To customize IBM RACF to let the CAP started task initialize correctly:
2. Assign a RACF user ID to the started task xxxxxxxx and assign the user ID to a RACF group
authorized to initiate started procedures. To define a RACF user ID for xxxxxxxx, use the
ADDUSER command and associate it with your existing started task RACF group, as follows:
ADDUSER user_name DFLTGRP(default_group) OWNER(default_group) NOPASSWORD
user_name
Specifies the name of the new RACF user ID. This name should be the same as the name of
the started task member in your PROCLIB that CAP uses.
default_group
Specifies the default group that contains all system started tasks; for example, STCGROUP.
Note: This command is only an example. For more information about using the
ADDUSER command, see your RACF administrator.
If you do not know the name of the default group, see your RACF administrator. For
detailed information to implement the RACF STARTED class or to modify the started
task table (ICHRIN03), see the IBM RACF Security Administrator Guide.
The security control checkpoint works with your site security software to determine whether users
have authority to use CAP. Your security software must allow users read access to the pseudo data
set to authorize users to use CAP. If a user does not have authority to use CAP, actions are processed
in the order they are defined for Global Type Sequencing.
1. Open the External Security Interface (ESI) Name Equates Table, member BC1TNEQU, located
in your iprfx.iqual.CSIQSRC installation library.
04-May-2018 246/1109
2.
NAMEQU CONCURRENT_ACT_PROC
Specifies the pseudo data set name that the RACROUTE macro uses to secure CAP
processing. Set the following values:
L1
Specifies the high-level qualifier for the data set.
L2
Specifies the next-level qualifier for the data set. We recommend that you specify a
value of CAP to make it easy to understand the purpose of pseudo data set.
Press End.
Your changes are saved. A pseudo data set name is defined in your ESI Name Equates Table to
act as a security checkpoint for CAP. The Edit session closes, and the Edit Entry panel opens.
Note: Ask your security administrator to grant read access to the pseudo data set for the
users you want to have access to CAP. Also, ask the security administrator to let you know
when they have completed this task.
In this example, the Name Equates table includes the following entry.
NAMEQU CONCURRENT_ACT_PROC.
L1=('C1'),
L2=('CAP')
Users who have read authority to the data set library C1.CAP have authority to request CAP.
To add the DD statement and activate CAP, use one of the following methods:
Activate CAP for Batch Jobs Submitted in Foreground (see page 250)
04-May-2018 247/1109
CA Endevor® SCM - 17.0
For more information about SCL requirements, see SCL Requirements for CAP (see page 250).
All elements are fully qualified; wildcarding is not used for elements.
On any Add, Update, or Request statements, the referenced data sets are cataloged data
sets.
Note: For more information about SCL requirements, see SCL Requirements for CAP
(see page 250).
2. Add an EN$CAP or EN$CAPnn DD statement in the job step that executes CA Endevor® SCM.
Note: When you submit a job or package for batch processing from foreground
panels, the option to specify concurrent action processing is provided on the panel.
When you select this option, the EN$CAPnn DD statement is automatically included
in the submitted JCL.
//EN$CAP DD SYSOUT=*
Specifies that the number of CAP processors that are allowed for this job is equal to the
SPAWNCNT value in C1DEFLTS. For Concurrent Action Processing to occur, SPAWN=Y must be
coded in C1DEFLTS and SPAWNCNT must be greater than 1.
//EN$CAPnn DD SYSOUT=*
nn
Specifies the maximum number of action request regions that are allowed for a j
ob. This parameter limits the Extended Common Storage Area (ECSA) that is used
by CAP.
00 - Concurrent action processing will not be used and actions will be proces
sed sequentially.
02-nn - Indicates the maximum number of action request regions that are allow
ed per job. This value overrides the SPAWNCNT value in C1DEFLTS, but does not ov
erride the SPAWNMAX value in C1DEFLTS. SPAWN=Y must be coded in C1DEFLTS to ena
ble Concurrent Action Processing. To determine what nn value to specify, use the
following formulas. Where x in the formula is the same as the nn value for EN$
CAPnn.
To determine the minimum amount of ECSA that must be free before CAP is started,
use the following formula:
Minimum ECSA = 3.6K*x + 3.2K
To determine the maximum amount of ECSA that a CAP job can use, use the followi
ng formula:
Maximum ECSA = 40.1K*x + 3.2K
To determine the size of the ECSA storage area that a CAP job can use that will
04-May-2018 248/1109
CA Endevor® SCM - 17.0
To determine the size of the ECSA storage area that a CAP job can use that will
not use all the ECSA free storage, add 20% to the maximum value, as follows:
Maximum ECSA plus 20% = (40.1K*x + 3.2K)1.20
Your processing preferences are set. When you submit the job, it is processed according to
your preferences. If more than one EN$CAPnn card is included in the JCL for the job step, only
the first one is used.
All elements are fully qualified; wildcarding is not used for elements.
On any Add, Update, or Request statements, the referenced data sets are cataloged data
sets.
Note: For more information about SCL requirements, see SCL Requirements for CAP
(see page 250).
Note: If CAP is not enabled, the following options are dimmed on the panel.
Concurrent Number
Specify the number of concurrent actions that are to be processed. The default is the
SPAWNCNT value set in C1DEFLTS. If you overwrite the default but decide you want to use
the default, type in the default value or blank out this field. Valid values are 02 through
the Max number that is shown on the panel. The Max number is the value of SPAWNMAX
specified in the C1DEFLTS.
Your processing preferences are set. When you submit the job, it is processed according to
your preferences.
04-May-2018 249/1109
CA Endevor® SCM - 17.0
All elements are fully qualified; wildcarding is not used for elements.
On any Add, Update, or Request statements, the referenced data sets are cataloged data
sets.
Note: For more information about SCL requirements, see SCL Requirements for CAP
(see page 250).
Concurrent Number
Specify the number of concurrent actions that are to be processed. The default is the
SPAWNCNT value set in C1DEFLTS. If you overwrite the default but decide you want to use
the default, type in the default value or blank out this field. Valid values are 02 through
the Max number that is shown on the panel. The Max number is the value of SPAWNMAX
specified in the C1DEFLTS.
Your processing preferences are set. When you submit the job, it is processed according to
your preferences.
Use explicit element names in SCL, if you plan to submit different actions in the same job.
If you use wildcards in the element or member names, actions against the same element may not
be processed in statement order. For example, if you code the following, with the GEN following
the ADD statement, the ADD may not complete before the GEN begins:
ADD ‘*’ TO ENV ‘TESTENV’ SYSTEM ‘TESTSYS’ SUBSYSTEM ‘TESTSBS’ TYPE ‘TESTTYPE’…
GEN ‘*’ FROM ENV ‘TESTENV’ SYSTEM ‘TESTSYS’ SUBSYSTEM ‘TESTSBS’ TYPE ‘TESTTYPE’ …
You can use wildcards or masking, if you submit one action per job. For example, you can use
wildcards when submitting multiple Add actions in the same job.
04-May-2018 250/1109
CA Endevor® SCM - 17.0
Examine your SCL requests. If your job will use CAP, check all ADD, UPDATE, and RETRIEVE actions
ensuring that all data sets referenced by the TO FILE, TO DSNAME, TO DDNAME and FROM FILE,
FROM DSNAME, and FROM DDNAME are cataloged data sets. They cannot be uncatalogued,
temporary, or JES2 file data sets.
If your site uses exit 4 programs to alter input or output files before the execution of an ADD,
UPDATE, or RETRIEVE, ensure that the data sets specified in the SCL are cataloged data sets, even
if the exit 4 program changes the data set names.
D[ISP] STAT
D[ISP] STATS
D[ISP] STATISTICS
Displays statistics.
A display statistics command returns the following response:
Number of Completed Requests nnnnnn
Number of Executing Requests nn
Number of Action Request regIons nn
Max Elapsed Time so far nnnnnn Act# num Stmt #num action element type
Min Elapsed Time so far nnnnnn Act #num Stmt #num action element type
Total Elapsed Time collected so far nnnnnn
D[ISP] SERVERS
Display the status of spawned servers. If the server is busy processing a request, information
about the request appears. This parameter returns the following response:
REGION jobname jobnumber cci-id status [ACT# nnnn STMT# nnnn action element-type]
The cci-id status is BUSY, AVAILABLE, or UNINITIALIZED. If the action request region is BUSY, the
action number, statement number, action being performed, element being acted upon and the
element type are displayed.
04-May-2018 251/1109
CA Endevor® SCM - 17.0
Load Modules
Contents
You can place the following modules under the control of CA Endevor® SCM:
Source data with a record length of up to 32,000 bytes. CA Endevor® SCM controls the actual
source in base, delta, and source output libraries.
Load modules. When you add a member defined as RECFM=U, CA Endevor® SCM checks for the
presence of linkage editor information. If this information is present, CA Endevor® SCM
recognizes the member as a load module. CA Endevor® SCM creates a summary of the
information contained in the load module, allowing you to track changes to the load module. This
summary, not the actual load module, is placed in CA Endevor® SCM-controlled libraries.
This ability to track load modules lets you put, for example, vendor code, which is often distributed in
load module format only, under CA Endevor® SCM control.
04-May-2018 252/1109
CA Endevor® SCM - 17.0
The load module generate processor can copy the load module from the external library to a load
library for the target stage.
Note: For more information about generate processors for load modules, see How to Track
Changes to Load Modules (see page ).
The Summary of Levels and Element Master panels for load module summary elements are the same
as those for other elements. The Browse, Changes, and History panels differ slightly as shown in the
following sections.
04-May-2018 253/1109
CA Endevor® SCM - 17.0
Link date
Date when the load module was last link edited.
Linkage editor
Identifier for the linkage editor used to link edit the load module.
Size
Size of the load module, in decimal bytes.
EP
Identifies the entry point CSECT.
CSECT
CSECT name and date when it was last generated.
Size
Size of the CSECT, in decimal bytes.
Translator
Identifier for the compiler that performed the translation.
CSECT
CSECT name.
Environ
Footprint environment.
System
Footprint system.
Subsystem
Footprint subsystem.
Element
Footprint element name.
Type
Footprint type.
S
Footprint stage.
VVLL
Footprint version and level for the element.
Date
Footprint date.
04-May-2018 254/1109
CA Endevor® SCM - 17.0
Note: For more information about how ZAP information is displayed, see The Changes
Panel (see page 255).
Attributes
Load module attributes assigned by the linkage editor.
The load module has been re-linked, using a more recent version of the same linkage editor.
ZAP to CSECT
Name of CSECT to which a ZAP was applied.
Date
Date the ZAP was applied to the CSECT.
ID
User-defined ZAP ID.
Define a type to associate with load module summaries. This type can have a maximum
LRECL=80, and should specify a compare range of 1-80. A source output library need not be
specified.
Write a generate processor for ADD, UPDATE, and TRANSFER actions, and a move processor that
copies the load module from one load library to another without using the summary of
information element.
04-May-2018 255/1109
CA Endevor® SCM - 17.0
Note: When writing a generate processor for load modules, verify that none of the job
steps executes for the GENERATE action. Because the generate processor only copies the
load module from one external load library to another, changes made to an original load
module could be copied into a target load module by the generate processor, causing the
target load module to become out of sync with the summary of information element
stored in CA Endevor® SCM.
When coding generate processors for use with load modules, include an EXECIF clause to
prevent the use of that generate processor for the GENERATE action.
user.stg1.loadlib
User-defined Stage 1 load library
ndvr.input.loadlib
Load library associated with the from location of the transfer.
ndvr.output.loadlib
Load library associated with the to location of the transfer.
04-May-2018 256/1109
CA Endevor® SCM - 17.0
04-May-2018 257/1109
CA Endevor® SCM - 17.0
1. Analyze existing types to determine which are likely to benefit from conversion.
6. Adjust the definitions of these types to reflect the conversion. Make the necessary changes to
the library names on the Type Definition panel.
Elements are stored in the new storage format after the first source UPDATE following the
conversion.
Component lists are stored in the new storage format after the first GENERATE action is executed
against the element following either a change in an input component or a source update.
The current delta format for an element appears on panel 1 of the Element Master display.
04-May-2018 258/1109
CA Endevor® SCM - 17.0
Normally need a source output library but do not need to be backed out (CA Endevor SCM does
not backout/backin base/delta libraries).
Need to be kept in standard PDS format for utilities, such as Advantage CA File Master.
Types that can benefit from the reverse delta storage format include the following:
Copybooks
JCL
Source
Plan the library structure first. Keep a record of the plan for use when updating type definitions.
Confirm that LRECL, BLKSIZE, and RECFM parameters are appropriate to the type being converted
(see the existing source output libraries).
Plan for and allocate new base libraries for every type within a system. Confirm that the new
libraries map properly to stage and type requirements.
When planning for workstation types, remember that most mainframe compilers require
LRECL=80.
04-May-2018 259/1109
CA Endevor® SCM - 17.0
The CONWRITE step, when used, needs to be modified to take account of revised Include
libraries.
Processors can read the base library directly when reverse deltas are being used.
SOURCE LENGTH, COMPARE FROM, and COMPARE TO fields to the desired values.
Library definitions as necessary to reflect new base libraries and optional changes to include and
source output libraries. Use the information recorded in Step 2.
04-May-2018 260/1109
CA Endevor® SCM - 17.0
If types are mapped with different delta formats, the WITH HISTORY option may or may not be an
option. The following table shows when the WITH HISTORY option can be used for a MOVE or
TRANSFER when types with different delta formats are mapped together:
Source Target MOVE with MOVE without TRANSFER with TRANSFER without
Format Format history history history history
Full-image Full-image Yes Yes Yes Yes
Full-image Reverse No Yes No Yes
Full-image Forward No Yes No Yes
Reverse Full-image No Yes No Yes
Forward Full-image No Yes No Yes
You can use the Restore action to convert elements to different storage formats as follows:
04-May-2018 261/1109
CA Endevor® SCM - 17.0
1. Use the Transfer to Archive action with the Bypass Delete Processor option to archive the
elements you want to change.
This archives the element and component base and delta files in their current formats, deletes
them from CA Endevor SCM, but leaves the elements outputs.
2. Change the Type definition to Log on the elements in their current location.
3. Use the Restore action with the Bypass Generate Processor to restore the elements from the
archive to the element's current location.
The element delta type is changed to log format and the outputs are not changed.
Note: To retain the MCF generate information, also specify the Retain Generate
History option. Without the Retain Generate History option, the Restore action
reinitializes the generate MCF information and the prior information is lost.
04-May-2018 262/1109
CA Endevor® SCM - 17.0
Notification
Contents
Email Notification
Email notification within CA Endevor SCM is enabled by creating the mainframe ID and email ID table,
ESMTPTBL. This table maps mainframe user IDs to email IDs or group names. When an email
notification event occurs, the invoked program scans the ESMTPTBL table for an appropriate match.
The program searches the table for a matching mainframe ID. If a match is found, an email addressed
to the associated email ID is sent. If no match is found, no email is sent.
However, if you code the DFTID=USERID parameter in the ESMTPTBL, instead of bypassing unlisted
IDs, CA Endevor SCM will construct an email address with the CA Endevor SCM user ID suffixed with
the default domain. If your site has defined email aliases for all your mainframe user IDs, coding of
DFTID=USERID allows you to reduce the size of the ESMTPTBL and makes it easier to maintain.
The email interface utility BC1PMLIF allows you to write simple email programs without having an in-
depth knowledge of the NOTIFY block or the ESMTP table lookup.
$ESMTP
Macro that builds a table (ESMTPTBL) that maps mainframe IDs to email IDs.
ESMTPTBL
Table created by the macro $ESMTP to map mainframe IDs to email IDs.
BC1JTABL
Sample JCL used to assemble and link any of the Tables, including the ESMTPTBL table.
The JCL to assemble and link this macro is located in iprfx.iqual.CSIQJCL. The resulting load module,
04-May-2018 263/1109
CA Endevor® SCM - 17.0
The JCL to assemble and link this macro is located in iprfx.iqual.CSIQJCL. The resulting load module,
ESMTPTBL, must reside in the CA Endevor SCM authorized library (uprfx.uqual or iprfx.iqual.
CSIQAUTH).
ATSIGN
Use this field to specify the byte value that replaces the @ sign in email addresses. You can
specify any value, except 00 and 40. For example, ATSIGN=80. The default value is 7C.
HOSTNAME
NJE node name of the z/OS system where SMTP is running.
DFTDOMAIN
Domain name to be used in email addresses. You can override this field in the mainframe ID
section.
MAILFROM
Defines a default MAIL FROM value. The value is free form and CA Endevor SCM neither does
syntax checking on the parameter nor appends a hostname to it.
The MAIL FROM value can be defined in several ways. The value that is used is the one that is
found first in the following search order:
2. NOTFROM@
3. MAILFROM
DFTURL
URL where CA CMEW is running. You can override this field in the mainframe ID section.
DFTID=USERID
If CA Endevor SCM cannot find the USERID in ESMTPTBL and DFTID=USERID is coded, CA Endevor
SCM attempts to send an email to the mainframe user ID by constructing an email address with
the CA Endevor SCM user ID suffixed with the default domain. Without DTFID=USERID, CA
Endevor SCM does not send an email if it cannot find the mainframe user ID in ESMTPTBL. This
parameter does not override email addresses in ESMTPTBL. If an invalid address is found in
ESMTPTBL, no email is sent to that user ID.
To enable the default ID feature, only one value is permitted (DFTID=USERID). If the value is
omitted, or coded as null (DFTID=), then the parameter has no effect.
SMTPTASKNAME
The name of the SMTP address space. The default is SMTP and is rarely subject to change.
SMTPCLASS
The SYSOUT CLASS associated with the SMTP task. The default is B and is rarely subject to change.
04-May-2018 264/1109
CA Endevor® SCM - 17.0
HOSTNAME
NJE node name of the z/OS system where SMTP is running.
MFID
The mainframe user ID or package approver group name. This field can contain up to 16
character.
EMAILID
The portion of the email ID that precedes the @. This field size is unlimited.
DOMAIN
The portion of the email ID that follows the @. If not specified, the global default domain is used.
This parameter supports an environment where email IDs might be defined in multiple domains.
URL
The URL where CA CMEW is running. If not specified, the global default URL is used. This
parameter enables you to point users to different implementations of CA CMEW.
Sample ESMTPTBL
A sample ESMTPTBL table is provided in the Tables library. The sample ESMTPTBL includes the
DFTID=USERID parameter, which enables CA Endevor SCM to construct email addresses from the CA
Endevor SCM user ID and the default domain. If your ESMTPTBL includes DFTID=USERID, when a
package is cast requiring an approval from one or more users not defined in the table, for example
peter01 and sally02, CA Endevor SCM will send an email to [email protected] (mailto:
[email protected]) and [email protected] (mailto:[email protected]), in addition to emails to
users defined in the table.
Sample BC1JTABL
The JCL that can be used to assemble and link-edit tables, including ESMTPTBL, is located in member
BC1JTABL, provided in the JCL library (iprfx.iqual.CSIQJCL). An alternative is to employ an SMP/E
USERMOD to accomplish this.
Synchronization Notification
The Synchronization Notification feature immediately sends an email to the element change owner,
when an element is changed or added higher in the software lifecycle map and is found to be out-of-
sync with the element located lower in the map.
Out-of-sync elements are instances of the same element with the element at the higher location in
04-May-2018 265/1109
CA Endevor® SCM - 17.0
Out-of-sync elements are instances of the same element with the element at the higher location in
the software lifecycle map having change levels that are not reflected in the element located lower in
the map. These elements are out of synchronization (out of sync).
A source sync check occurs whenever an element is changed or arrives at a new location in the
lifecycle map. All instances of that element located lower in the software lifecycle map are checked to
determine if the newly changed or added element is out of synchronization (out of sync) with the
elements located lower in the map. The source sync check verifies the last level time stamp of the
element at the higher lifecycle location against the base level time stamp of the lower elements. If
the dates do not match, a source management's synchronization check function is invoked for these
elements to determine if they are actually out of sync.
Provided Synchronization Notification has been enabled by the administrator, it is initiated by the
following activities:
The element actions: Add, Update, Move, Restore, Transfer C1-C1, and Transfer from Archive.
For each out-of-sync element found, an email is sent to the owner associated with the last source
change level of the element located lower in the map than the newly changed or added element.
However, if a change level does not exist yet, the email is sent to the last element action user ID. In
addition, a message is written to the action log to record the out-of-sync elements. In foreground, if
an action causes out-of-sync elements, the "route sync problem" text appears on the action's panel,
unless this message is suppressed by the administrator.
Note: If email notification is not already set up at your site, the administrator must set it up
in order for this feature to work.
Note: If email notification is not already set up at your site, the administrator must set it up
in order for this feature to work. For details, see Email Notification.
1. In the Type=Main section of the C1DEFLTS table, set the SYNC@CHK parameter to Y as
follows:
SYNC@CHK=Y,
04-May-2018 266/1109
1.
CA Endevor® SCM - 17.0
SYNC@CHK=Y,
Note: To turn off source synchronization, set one of the following. (SYNC@CHK=, is
the default.)
SYNC@CHK=N,
SYNC@CHK=,
2. Set the severity level of the out-of-sync messages written to the action log, by setting
SYNC@MSV= parameter in the C1DEFLTS table to one of the options.
SYNC@MSV=[I,W,C],
I-Informational message.
W-Warning message.
C-Caution message.
Blank-Default. If no option is specified (for example, SYNC@MSV=,) then the option
defaults to I for informational message.
When an out-of-sync element is added, a message with the severity level you specify is
written to the action log.
3. Mark an environment as the starting location in the software lifecycle where you want source
sync checks to be performed. In the Type=Environment section of the C1DEFLTS table, set the
SYNC@BLOC parameter to Y (SYNC@BLOC=Y,) for this environment. The options for this
parameter are as follows:
SYNC@BLOC=[Y,N],
Y-The environment is a source synchronization location.
N-Default. The environment is not a source synchronization location.
Blank-If no option is specified (for example, SYNC@BLOC=,) then the option defaults to N.
Specifies whether the Environment, Stage location is a source synchronization location. If
SYNC@BLOC=Y, when an action adds or moves an element to this location, or to any
location higher up the map, a sync check is performed. If an element located lower in the
map is not in sync with the new element, a synchronization notification email is sent to
the owner of the out-of-sync element at the lower location. If more than one SYNC@BLOC
is specified in C1DEFLTS, regardless of its specification (SYNC@BLOC=, SYNC@BLOC=N, or
SYNC@BLOC=Y,) all SYNC@BLOC parameters after the first one in the map are ignored.
Assume that your site's C1DEFLTS table maps environment DEV to QA1, maps QA1 to QA2, and maps
QA2 to PRD. If the C1DEFLTS table definition of QA2 has SYNC@BLOC set to Y, then QA2 and PRD are
synchronization locations. It is not necessary to mark PRD.
04-May-2018 267/1109
CA Endevor® SCM - 17.0
To see if source sync checking is enabled and what severity level is assigned to the action log
messages, you can check the site options using either of the following methods:
See the panel Site Information from C1DEFLTS. The Function Control section of the panel
includes the following fields: Sync Sev Msg and Sourc Sync Check.
Run a Site Options Settings report, which lists the Source Sync Chk and Sync Sev Msg fields in
the C1DEFLTS section of the report.
To see if an environment is an active source synchronization location, you can use either of the
following methods:
Use the CSV utility's List Environment function and view the SYNC LOC field in the returned
data.
If your site uses the API, the API List Site and List Environment requests return Source Notification
settings.
Your program can call BC1PMLIF at exit points or in processors with an easy to use parameter list.
04-May-2018 268/1109
CA Endevor® SCM - 17.0
Your program can call BC1PMLIF at exit points or in processors with an easy to use parameter list.
BC1PMLIF formats the required internal control blocks and calls the existing CA Endevor® SCM email
interface modules. The following parameter list is passed to BC1PMLIF. The first two parameters are
mandatory, and the others are optional.
MYSMTP-USERID (8 bytes)
Mainframe USERID used to lookup the email address in ESMTPTBL
MYSMTP-TEXT
Two byte counter followed by nn lines of data. Up to 99 lines of 133 bytes are allowed. Email line
count, Email text area.
MYSMTP-URL (1 byte)
Includes the default URL value of ESMTPTBL in the email. If no default URL is coded in ESMTPTBL
(DFTURL=,) then no URL is included in the email. Can contain Y or any other 1-byte value; the
content of the passed value is not important.
BC1PMLIF uses the CA Endevor® SCM ESMTPTBL to translate the Mainframe User ID name into an
email address. Then it formats the message and sends it to the email server. If BC1PMLIF detects any
errors during execution, it sets a non-zero return code and posts an error message in the Error
Message area.
Note: A sample COBOL program that uses BC1PMLIF is provided as member CALLMLIF in
the installation source library.
SMTP (email)
TSO
TPX
XMIT
04-May-2018 269/1109
CA Endevor® SCM - 17.0
Several sample user exit programs are provided with CA Endevor® SCM. The source for these exit
programs is located in the iprfx.iqual.CSIQOPTN library.
1. Modify the exit program to pass the values for the universal parameters to the control block.
2. Modify the exit program to pass the values for the protocol-specific parameters to the control
block.
Universal Parameters
Regardless of which protocol you use to send the notification, the exit program always needs to pass
certain parameters to the control block. The following table describes these parameters. Information
is given for both assembler and COBOL. Copybooks and Dsects are provided in iprfx.iqual.CSIQOPTN
for use in your programs. See members $NOTIFY and NOTIFYDS for assembler and COBOL.
NOTFTYPE (assembler)
NOTI-NOTIFY-TYPE (COBOL)
Specifies the protocol you want to use to send the message. The possible values are:
SMTP
TSO
TPX
XMIT
NOTMSGTX (assembler)
NOTI-MESSAGE-TEXT (COBOL)
80-character text field used to specify the message.
Note: If you select a value of V for the NOTMSGVF parameter, this field is not used.
NOTFUSER (assembler)
04-May-2018 270/1109
CA Endevor® SCM - 17.0
NOTI-USER (COBOL)
The ID of the user or users that will receive the notification. The type of ID depends on the
protocol used to send the message.
Protocol-specific Parameters
Depending on which protocol you want to use to send the notification to your users and package
approvers, the exit program must pass certain protocol-specific parameters to the control block, in
addition to the universal parameters discussed in the previous section.
SMTP-specific Parameters
If you are using the SMTP protocol to inform your users and package approvers of a CA Endevor®
SCM event, use the following information for the SMTP-specific parameters that the exit program
must pass to the control block. Information is provided for assembler.
NOTATSIGN
This field allows you to override the default character used to construct email addresses. When
no value is entered, CA Endevor® SCM uses the default value, which can be @ sign, or the value
coded in $ESMTP table. Specify one byte hexadecimal value, or leave the field blank if you do not
want to override the default value. :
NOTMSGVF
Indicates whether the message text format is fixed or variable length. The possible values are:
Note: If you select F, or do not select a value, use the NOTMSGTX parameter to specify the
message text. Do not use the NOTSMTPM parameter.
V-Variable length.
NOTSIZE
Indicates the size field in the $NOTIFY control block.
NOTMSGMX
Indicates the maximum message length. Required only if the value of NOTMSGVF is V.
NOTSMTPM
The address of the email text. The text must be in the following format:
LLLLmessage-text
NOTSMTPS
04-May-2018 271/1109
CA Endevor® SCM - 17.0
NOTSMTPS
50-character text field used for the email's subject field.
NOTMSGLP
Text field used to specify the message.
If NOTMSGVF is F, then the data string is treated as a string of fixed records. Fixed records are
84 bytes long, with a 4-byte address of the next record (zero - end), and 80 bytes of text
content.
If NOTMSGVF is V, then the data string is treated as a string of variable records, instead of as a
string of a single variable record. The variable record format is a 4-byte address of the next
record (zero - end), a 2-byte length of string, and nn bytes of string content (up to 32K bytes).
NOTFROM
A four-byte field that allows you to specify a FROM USER for the emails that are sent. The field
should contain the address of an area of up to 50 bytes containing the FROM-ID that is to be used
in emails. No spaces are allowed in the FROM-USER field. If the address is zeros, CA Endevor®
SCM uses a default FROM USER definition.
For a sample exit program that illustrates how to use these parameters, see XIT7MAIL in the iprfx.
iqual.CSIQOPTN library.
Note: For more information about XIT7MAIL, see the API and Exits.
TSO-specific Parameters
If you are using the TSO protocol to inform your users and package approvers of a CA Endevor® SCM
event, refer to the following table for the TSO-specific parameters that the exit program must pass to
the control block. Information is provided for both assembler and COBOL.
NTSOALLU (assembler)
NOTI-SET-ALL-USER-OPT (COBOL)
Specifies whether you want to send the message to all TSO users. The possible values are:
N-Do not send the message to all TSO users. This is the default setting.
NTSOLOGN (assembler)
NOTI-SET-LOGON-OPT (COBOL)
Specifies when users receive the message. The possible values are:
Y-Users receive the message when they log in to TSO. This is the default setting.
NTSOSAVE (assembler)
04-May-2018 272/1109
CA Endevor® SCM - 17.0
NTSOSAVE (assembler)
NOTI-SET-SAVE-OPT (COBOL)
Specifies whether you want to save the message in a broadcast set. The possible values are:
TPX-specific Parameters
If you are using the TPX protocol to inform your users and package approvers of a CA Endevor® SCM
event, refer to the following table for the TPX-specific parameters that the exit program must pass to
the control block. Information is provided for both assembler and COBOL.
NTPXJOBN (assembler)
NOTI-TPX-JOB-NAME (COBOL)
The site-specific name of the TPX started task. This is a required entry.
NTPXTYPE (assembler)
NOTI-USERID-OPTION (COBOL)
Specifies the type of TPX call to issue. The possible values are:
U-(Default) USERID.L-LISTID
T-TERMID
A-APPLID
S-SESSION ID
Note: If you want to send the message to all TPX users, this field must be left blank.
NTPXALL (assembler)
NOTI-ALL-OPTION (COBOL)
Specifies whether you want to send the message to all TPX users. The possible values are:
NTPXSAVE (assembler)
NOTI-SAVE-OPTION (COBOL)
Specifies whether the message will be saved for the user. The possible values are:
NTPXBREK (assembler)
04-May-2018 273/1109
CA Endevor® SCM - 17.0
NOTI-BREAK-IN-OPTION (COBOL)
Specifies whether you want users in an active TPX session to receive messages immediately. The
possible values are:
N-(Default) The Notification utility does not interrupt active TPX sessions.
Y-The Notification utility interrupts active TPX sessions and will display the message. The user can
then decide to save or delete the message before returning to the session.
XMIT-specific Parameters
If you are using the XMIT protocol to inform your users and package approvers of a CA Endevor® SCM
event, refer to the following table for the XMIT-specific parameters that the exit program must pass
to the control block. Information is provided for both assembler and COBOL.
NXMTNODE (assembler)
NOTI-NJE-NODE (COBOL)
The site-specific NJE target node name. This is a required entry
NOTERMSG (assembler).
NOTI-XMIT-MESSAGE (COBOL)
The Notification utility fills in this field if there has been an error. This field should be moved to
the exit block error message field.
For example, with this facility you can notify a CA Endevor SCM administrator when a CA Endevor
SCM package has been denied by one of the package approvers or if an attempt to move an element
into the production environment fails.
Let's look at the following message to understand how events issued from CA Endevor SCM can be
used by CCS Event Manager. Let's assume this message appears on the Event Console:
%CATD_I_060, SNMPTRAP: -c public 791 172.24.255.255
<productname>.machine.name (http://machine.name) 6 1 00:00:00 1 OID:
machine.public.name (http://machine.public.name) 6 1 00:00:00 1 OID:
1.3.6.1.4.1.791.2.7.3.1
&per.iso.org (http://per.iso.org).dod.internet.private.enterprises.791.2.7.3.1 VALUE:
ENF00000 THIS IS A TEST OF CA ENDEVOR MESSAGING
04-May-2018 274/1109
CA Endevor® SCM - 17.0
The bold portion of the message is the value submitted by user code and the non-bold part was
added by CCS Event Management routines. Let's assume this message is associated with a rule that
looks for the unique trap id, 1.3.6.1.4.1.791.2.7.3, of all client-defined CA Endevor SCM messages.
When it encounters this message id, it routes the messages to a secondary console that logs and
prints each message for later review.
CA Endevor SCM administrator to structuresd the contents of their messages in a way that allows the
message to be trapped and forwarded by CCS Event Manager.
CCS allows a 102-byte message field to be displayed on the Event Console. When you construct a
message to be sent to CCS, consider including the following information:
A severity code
You should also try to delimit message components with a space or a standard character to simplify
forming events and rules.
04-May-2018 275/1109
CA Endevor® SCM - 17.0
This diagram shows how CA Endevor SCM sends messages to the CCS Event Manager.
The CCS Event Manager takes the free-format 102-byte message and adds control and system
information before routing the entire message composite to the indicated consoles. Once the
message is received at each console, CCS Event Management detects messages based upon string
content and takes action using the message action facilities of Event Management.
Procedures for calling the interface from a user exit or from a processor are described next, followed
by information about creating the CCS IP address table.
The BC1PTRPO user exit interface program requires the following two parameters:
04-May-2018 276/1109
CA Endevor® SCM - 17.0
The BC1PTRPO user exit interface program requires the following two parameters:
Message
A102 byte message field which is passed 'as-is' to the Event Console.
Result-area
An 80-byte field into which BC1PTRPO returns the result of the Event submission. If the Event
submission is successful, it contains "OK" as the first two characters, padded with spaces.
Otherwise, it contains the reason for the Event submission failure.
The user exit must build the message and interrogate the result area. Writing user exits assumes you
have a working knowledge of CA Endevor SCM user exit architecture. A sample user exit is delivered
as member XIT3MSG, in the iprfx.iqual.CSIQOPTN library.
The BC1PTRAP REXX procedure interface program is an assembler program which is called with one
parameter and returns a result message to the REXX procedure. It requires the following parameters:
Message
A 102 byte message field which is passed 'as-is' to the Event Console.
Result-area
A field where BC1PTRAP returns the result of the Event submission. If the Event submission is
successful, it contains "*-ok" as the first four characters, padded with spaces. Otherwise, it
contains the reason for the Event submission failure.
The REXX procedure must build the message and interrogate the result area.
//******************************************************
//* CREATE TEMPORARY INPUT FILE TO SEND A MESSAGE *
//******************************************************
//MSGBLD EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSUT2 DD
// DSN=BC1USERID..TEMPMSG,DCB=(RECFM=FB,LRECL=80,BLKSIZE=8000),
// SPACE=(TRK,2,1)
//SYSUT1 DD *
EX 'uprfx.uqual.ISRCLIB(ENFSAMP)' 'ENF00000 &C1ACTION. &C1ELEMENT'.
//SYSIN DD DUMMY
//******************************************************
//* SEND A UNICENTER TNG EVENT IN FOREGROUND**
//* NOTE: ATTEMPTING TO RUN THIS STEP IN BG**
//* WILL RESULT IN RC=5**
//******************************************************
04-May-2018 277/1109
CA Endevor® SCM - 17.0
//******************************************************
//SMSGFG EXEC PGM=BC1PTMP0,MAXRC=5,
// PARM='BC1USERID..TEMPMSG'
//STEPLIB DD DSN=iprfx.iqual.CSIQAUTU,DISP=SHR
// DD DSN=iprfx.iqual.CSIQLOAD,DISP=SHR
//SYSTERM DD DSN=&&PARMLIST.,DISP=(OLD,PASS)
//SYSTSPRT DD DSN=&&PARMLIST.,DISP=(OLD,PASS)
//SYSPRINT DD DSN=&&PARMLIST.,DISP=(OLD,PASS)
//SYSOUT DD DSN=&&PARMLIST.,DISP=(OLD,PASS)
//*****************************************************
//* SEND A UNICENTER TNG EVENT IN BACKGROUND *
//*****************************************************
//SMSGBG EXEC PGM=IKJEFT01,
// COND=((5,NE,SMSGFG),(5,LT)),MAXRC=7
//SYSTSPRT DD DSN=&&PARMLIST.,DISP=(OLD,PASS)
//SYSTSIN DD DSN=&&TEMPMSG.,DISP=OLD
04-May-2018 278/1109
CA Endevor® SCM - 17.0
Extended Processors
Contents
CA Endevor® SCM allows you to create and maintain processors. Coded using standard JCL,
processors instruct CA Endevor® SCM to modify, move, verify, delete, or create executable forms of
elements. There are three types of processors:
The term extended processor refers to a user-written processor that is defined to CA Endevor® SCM.
It supplies functionality beyond writing or deleting a member in an output library.
Processor Groups
Processors may be specified in processor groups. A processor group consists of the following:
One generate, one delete, and one move processor, or any combination thereof. (For example, a
non-executable element may require only a move processor in its processor group. You cannot,
however, have multiple processors of the same type in a processor group.)
Processor groups allow you to handle common variations among the members of a particular type
quickly and easily. If you create a single set of processors using symbolic parameters, you can create
different processor groups using the same set of processors but containing different default symbolic
overrides. For example, your site has applications coded in COBOL and COBOL/370. You could define
a single type, COBOL, and have two processor groups, one for COBOL II and another processor group
for COBOL/370.
04-May-2018 279/1109
CA Endevor® SCM - 17.0
You add processors to CA Endevor® SCM in the same manner as other elements. They must be added
to type Process, or they are not executable.
Because CA Endevor® SCM processors get translated into load modules, they should not be
named the same as any programs you may be executing within a processor. For example,
do not name a processor CONWRITE or IEWL.
Add
Invokes the Generate processor and provides the following options:
Processor group
Archive
Invokes the Delete processor and provides the Bypass element delete option.
Delete
Invokes the Delete processor and provides the Bypass element delete option.
Generate
Invokes the Generate processor (and Delete processor if processor group changes) and provides
the Processor group option.
Move
Invokes the Move (default) or Generate, and Delete processors and provides the Bypass element
delete option.
Restore
Invokes the Generate processor and provides the following options:
Processor group
Transfer
Invokes the Generate (default) or Move processor, and Delete processor and provides the
following options:
Processor group
04-May-2018 280/1109
CA Endevor® SCM - 17.0
Update
Invokes the Generate processor and provides the following options:
Processor group
The COPY, DISPLAY, LIST, PRINT, RETRIEVE, and SIGNIN actions do not invoke processors.
Writing Processors
Contents
04-May-2018 281/1109
CA Endevor® SCM - 17.0
Processors are coded using standard JCL syntax and are converted to a CA Endevor® SCM executable
form. Processor statements specify which programs/utilities are run, the order in which they are run,
and any special conditions required. (They are similar to JCL statements.)
CA Endevor® SCM provides several keywords, symbolic parameters, and utilities for use in coding
processors. While CA Endevor® SCM supplies many of its own utilities, user-coded or third-party
utilities or programs can be used within a processor as well.
All DD statements allocated for a CA Endevor® SCM processor step are de-allocated at processor step
termination. This means if a processor step uses a previously allocated DD statement such as
SYSPROC, it is allocated for the processor step and subsequently de-allocated at processor step
termination.
Note: For an explanation and illustration of the various types and uses of processors, see
Sample Processors (see page 385).
Processor Names
Processor names can have up to eight characters. The following table provides abbreviations that do
not represent a complete list, and are offered as guidelines only, shown by character position and
then description:
G = generate processor
D = delete processor
M = move processor
2-4 Language type or utility; for example:
ASM = ASSEMBLER
CLI = CLIST
CII = COBOL
EAS = EASYTRIEVE
FOR = FORTRAN
JCL = JCL
04-May-2018 282/1109
CA Endevor® SCM - 17.0
PLI = PLI
RPG = RPG
TEL = TELON
TRA = TRANSFORM
5 Data base environment; for example:
D = DB2/DL1
S = IDMS
I = IMS
N = None
6 Operating environment; for example:
B = Batch
C = CICS
S = IDMS-DC
I = IMS-DC
N = None
7 Output type:
L = Load Module
O = Object
P = PDS
R = Report(s)
N = None
8 Stage ID
04-May-2018 283/1109
CA Endevor® SCM - 17.0
Processor Features
For the most part, CA Endevor® SCM processors are written using standard OS JCL syntax. CA
Endevor® SCM supports most JCL parameters.
Note: For a complete list of unsupported JCL parameters, see Unsupported Parameters
(see page 425).
If a DD statement or a library needs to run with a true DISP=OLD, you must enable the
ENHOPTDD feature in the CA Endevor® SCM Options table (ENCOPTBL).
CA Endevor® SCM provides the following additional features and capabilities within processors:
CC
DDA
DDB
JCL
PGM
SYM
SIN
04-May-2018 284/1109
CA Endevor® SCM - 17.0
PRITE
FLD
Processor Keywords
The following keywords are specific to CA Endevor® SCM processor statements:
FOOTPRNT
Causes CA Endevor® SCM footprints to be created or verified.
MAXRC
Specifies the maximum acceptable return code for a job step.
EXECIF
Permits execution of a specific step only if the specified conditions are met.
BACKOUT
Allows you to maintain backout information on a library by library basis, if you are using package
processing.
MONITOR
Allows monitoring of input and output components as a part of Configuration Management.
ALTID
ALTID=N enables you to disable the CA Endevor® SCM alternate user ID during execution of the
processor step.
ALLOC
Indicates whether the DD statement is to be expanded into a concatenation of data sets based on
the map.
04-May-2018 285/1109
CA Endevor® SCM - 17.0
Note: The processor keyword FOOTPRNT cannot be specified on DD statements that refer
to USS path and file names.
FOOTPRNT=CREATE
Footprints a member in an output data set, to associate that member with the element being
processed.
If the output is written by a CA Endevor® SCM action, such as RETRIEVE, to a specific PDS (or ELIB)
member, or if you are using the CONWRITE or CONLIST utilities, the member is footprinted
automatically, regardless of whether you use the FOOTPRNT keyword.
If you are using BSTCOPY, the output is directed to a PDS by a non-CA Endevor® SCM utility (such
as a user program), or the output is a sequential object module, you must specify
FOOTPRNT=CREATE for the member to be footprinted.
To footprint a load module, you must specify FOOTPRNT=CREATE on the SYSLMOD DD statement
for the load module, shown as follows:
//LKED EXEC PGM=IEWL,COND=((0,NE,CONWRITE),(4,LT,COMPILE)),
// PARM='PARMLNK',MAXRC=4
//SYSLIN DD DSN=&&SYSLIN,DISP=(OLD,DELETE)
//SYSLMOD DD DSN=&LOADLIB(&MEMBER).,FOOTPRNT=CREATE,
// MONITOR=&MONITOR.,DISP=SHR
//SYSLIB DD DSN=&LSYSLIB1.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&LSYSLIB2.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&COBLIB.,
// DISP=SHR
//SYSUT1 DD UNIT=&WRKUNIT.,SPACE=(CYL,(1,1))
//SYSPRINT DD DSN=&&LNKLIST,DISP=(OLD,PASS)
To footprint an object deck, CA Endevor® SCM locates the first, named CSECT within the
object deck, and uses that name to build a linkage-editor identify control card. If there is no
named CSECT in the object deck, the footprinting action fails.
You cannot footprint object modules that do not contain CSECT names.
The library member name must match the name of the element to which it corresponds.
FOOTPRNT=VERIFY
Verifies the footprint in an existing library member corresponds to the current level of the
element being processed. This statement is generally used in the move processor to verify the
element against the CA Endevor® SCM Master Control File before the element is moved or
transferred.
An error during the footprint verification step causes the job to fail because it is a CA Endevor®
SCM error. To override this default, the VFY_FP_FAILURES feature must be activated in the CA
Endevor® SCM Options table (ENCOPTBL). With this option, the footprint verification return code
becomes a step return code instead of a CA Endevor® SCM return code.
04-May-2018 286/1109
CA Endevor® SCM - 17.0
//STEPNAME EXEC PGM=IEBCOPY
//SYSPRINT DD SYSOUT=*
//IN DD DSN=STAGE1.COPYLIB,DISP=SHR,FOOTPRNT=VERIFY
//OUT DD DSN=STAGE2.COPYLIB,DISP=SHR
MAXRC Keyword
MAXRC defines the highest acceptable step return code for a processor. It is coded on the EXEC
statement for the corresponding job step and affects only the current element action. The syntax for
the MAXRC parameter follows:
MAXRC=nnn
nnn
Use the Element Master Info display to confirm the processor-failed flag is set for an element. The
literal “FAILED” appears next to the processor return code when the flag is set. If the processor-failed
flag is set for an element in either stage, CA Endevor® SCM does not allow a MOVE or TRANSFER
action against the element.
You can bypass executing one or more steps, by coding the COND or EXECIF parameters on the steps
or using IF/THEN/ELSE processor logic.
MAXRC Scenario
There is a processor containing three steps:
1. Compile
2. Link-edit
3. CONLIST
Regardless of the return codes in the first two steps, you always want the CONLIST step to execute
and store the listings.
MAXRC Example
04-May-2018 287/1109
CA Endevor® SCM - 17.0
MAXRC Example
A COBOL compile with warnings has a return code of 04. To allow warnings but prohibit serious
problems, specify MAXRC=04 on the compile EXEC statement. Return codes greater than 04 set the
CA Endevor® SCM processor-failed flag for the element.
//STEPNAME EXEC PGM=IKFCBL00,MAXRC=04,COND=(0,NE)
All remaining steps are executed unless the COND, EXECIF or IF/THEN/ELSE logic specifies otherwise.
EXECIF Keyword
EXECIF lets you define conditions under which a processor step is executed. Using the EXECIF
keyword, you can create a single processor containing the steps that are conditionally required. You
can, therefore, write one processor instead of executing multiple processors.
EXECIF is a truth statement, and in its simplest format its syntax is:
EXECIF=(value1,operator,value2)
value1
The user specified value for the truth statement. It can be a literal, a CA Endevor® SCM, user, or
site symbol.
operator
The required condition between value1 and value2. Valid values are as follows:
EQ-equal to
GT-greater than
NE-not equal to
LT-less than
value2
The user specified value for the truth statement. It can be a literal, a CA Endevor® SCM symbol, or
a user symbol.
The EXECIF statement can contain as many value clauses as required, if you have the appropriate
number of parentheses (that is, nested parentheses). For example:
EXECIF=((value1,EQ,value1A),(value2,EQ,value2A),(value3,EQ,value3A))
Note: When you use multiple clauses in the EXECIF statement, all clauses must be true for
the step to be executed.
The following example illustrates the use of the EXECIF keyword to allow a single generate processor
04-May-2018 288/1109
CA Endevor® SCM - 17.0
The following example illustrates the use of the EXECIF keyword to allow a single generate processor
to be used for DLI COBOL and IDMS COBOL. The generate data coded is the same for each type of
COBOL, but different TRANSLATE steps are required by each to execute.
//DLI EXEC PGM=DFHECP1$,COND=(0,NE),
// EXECIF=(&C1PRGRP.,EQ,DLI),
// PARM='&PRM1'.
//SYSPRINT DD DSN=&&TRNLIST,DISP=(OLD,PASS)
//SYSPUNCH DD DSN=&&TRN,DISP=(NEW,PASS,DELETE),
// UNIT=SYSDA,SPACE=(CYL,(2,1),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=4000),
// MONITOR=COMPONENTS
//SYSIN DD DSN=&&SRC,DISP=(OLD,PASS)
//********************************************************
//IDMS EXEC PGM=IDMSDMLC,COND=(0,NE),MAXRC=04,
// EXECIF=(&C1PRGRP.,EQ,IDMS),
// PARM='SDMLC-IDMS-STEP',DBNAME='MINI'
//DBRUNLOG DD DSN=CA.DBRUNLOG,DISP=SHR
//STEPLIB DD DSN=CA.LOAD.TEST,DISP=SHR
// DD DSN=CA.LOAD.CV1,DISP=SHR
//SYSDDL DD DSN=CA.NQ.DDA01.CV1,DISP=SHR
//SYSIPT DD DSN=CA.READONLY.DMLC,DISP=SHR
// DD DSN=&&SRC,DISP=(OLD,PASS)
//SYSJRNL DD DUMMY
//SYSLST DD DSN=&&TRNLIST,DISP=(OLD,PASS)
//SYSPCH DD DSN=&&TRN,DISP=(NEW,PASS,DELETE),
// UNIT=SYSDA,SPACE=(CYL,(2,1),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=4000),
You can also use the EXECIF statement in generate processors for use with load modules, to make
sure that a GENERATE action against the load module does not execute the generate processor.
BACKOUT Keyword
If you are using package processing, BACKOUT allows you to maintain backout information on a
library by library basis.
When you use packages, CA Endevor® SCM, by default, maintains backout information for PDS
members that are created, changed, or deleted during processor execution. If you do not want this
information maintained for a library, code BACKOUT=N in the DD statement for the library.
//LKED EXEC PGM=IEWL,COND=((0,NE,CONWRITE),(4,LT,COMPILE)),
// PARM='PARMLNK',MAXRC=4
//SYSLIN DD DSN=&&SYSLIN,DISP=(OLD,DELETE)
//SYSLMOD DD DSN=&LOADLIB(&MEMBER).,FOOTPRNT=CREATE,BACKOUT=N,
// MONITOR=&MONITOR.,DISP=SHR
//SYSLIB DD DSN=&LSYSLIB1.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&LSYSLIB2.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&COBLIB.,
// DISP=SHR
//SYSUT1 DD UNIT=&WRKUNIT.,SPACE=(CYL,(1,1))
//SYSPRINT DD DSN=&&LNKLIST,DISP=(OLD,PASS)
MONITOR Keyword
Component monitoring is a feature of the CA Endevor® SCM Automated Configuration Manager
(ACM). You can use the keyword MONITOR to monitor selected library data sets for component
relationships.
04-May-2018 289/1109
CA Endevor® SCM - 17.0
The processor keyword MONITOR cannot be specified on DD statements that refer to USS path and
file names.
ALTID Keyword
If a CA Endevor® SCM alternate ID is defined in the C1DEFLTS table, then a processor step executes
under the security context of the CA Endevor® SCM alternate ID. However, you can override this
behavior by specifying ALTID=N on the EXEC statement of the processor. If ALTID=N is specified, then
the processor step runs under the security context of the user ID associated with the job.
If ALTID=N is specified, then CA Endevor® SCM does not use the alternate user ID during execution of
that processor step, the value of the INTRDR_ALTID option in the CA Endevor® SCM Options Table is
ignored, and any jobs submitted to the internal reader run under the security context of the user ID.
If you are using CA Top Secret and you want CA Endevor® SCM to submit JOBs to the INTRDR using
the credentials of the CA Endevor® SCM user ID, you must set the CA Top Secret global option JES
(VERIFY). If the JES(VERIFY) option is not set, CA Top Secret attempts to build the USER= JOBCARD
parameter with the CA Endevor® SCM Alternate ID as the USER parameter value. This causes the
submitted JOB to fail, because users typically do not have the authority to specify the CA Endevor®
SCM Alternate ID on their JOBCARD. For more information about the internal reader, see The Internal
Reader (see page ).
The security context used for USS file access in processor steps is determined by the ALTID keyword.
The IBM APAR OA39558 allows processors to run under either the credentials of the user, or under
the Alternate ID, so that USS outputs (created, copied, compiled) have the Alternate ID as the owner
or group owner.
ALLOC Keyword
Use the ALLOC keyword to implement the processor map allocation feature. The ALLOC clause
indicates whether a DD statement is to be expanded into a concatenation of data sets based on the
map. The allocation of the DD statement for map processing includes all data sets in a concatenation
starting from the current location until the end of the map. The following fields are used to
determine the map, starting from the CA Endevor® SCM location at which the processor is being
executed: environment, stage, system, subsystem, and type. If system, subsystem, or type are not
defined at any point in the map, map allocation stops at the last stage where they are all defined.
This option simplifies processor maintenance, especially for work area (sandbox) implementations.
For more information, see Processor Map Allocation (see page 291).
LMAP
Bases the concatenation on the logical map.
PMAP
Bases the concatenation on the physical map.
STD
Standard allocation. No special map processing is done. This is the default when ALLOC is not
specified.
04-May-2018 290/1109
CA Endevor® SCM - 17.0
Note: Certain symbols must be used to specify location information for a data set name
that varies based on the map. These symbols, when specified with ALLOC={LMAP|PMAP},
varies for each location in the map. For more information, see Implement Processor Map
Allocation (see page 291).
This feature provides the ability to code a varying concatenation of data sets to a single DD statement
based on the map using location (environment, stage, system, subsystem) information provided by
symbol within the data set name, eliminating the need to use if-then-else logic. It facilitates in the
implementation of private work spaces by eliminating the need for alias data set names when system
or subsystem names change across environments.
The use of segregated private work areas is most easily implemented by using a private work area
identifier (usually a user ID) as the subsystem name in the lowest environment in the life cycle.
However, because the file names for source, copy, macro and header libraries contain the subsystem
name, the processors definitions must be defined with many if-then-else statements to
accommodate different file name formats. This precludes the use of symbolic variables to build the
file names. The processor map allocation enhancement eliminates the need for conditional
statements like if-then-else when concatenation allocations vary by life cycle location.
Processor map allocation works for data sets whose names follow the mapping structure of the
location from which the processor is executing. Processors do not have to be generated after a
change to the mapping structure.
You cannot use the processor map allocation feature for data sets that do not follow the current
mapping structure, as in data sets that are from a different CA Endevor® SCM implementation. This
feature does not allow a concatenation of interspersed data set names based on the map.
Implement Processor Map Allocation
To simplify processors, when system or subsystem names change across environments, you can use
the processor map allocation feature, which lets you code a varying concatenation of data sets to a
single DD statement.
1. Write a processor DD statement that includes the ALLOC= clause to indicate whether the DD
statement is to be expanded into a concatenation of data sets based on the logical or physical
map.
ALLOC=LMAP
Bases the concatenation on the logical map.
ALLOC=PMAP
Bases the concatenation on the physical map.
04-May-2018 291/1109
CA Endevor® SCM - 17.0
The allocation of the DD statement for map processing includes all data sets in a
concatenation starting from the current location until the end of the map.
2. Use the following symbols for the location specifications in the DD statement.
These symbols, when specified with ALLOC={LMAP|PMAP}, vary for each location in the map.
Other symbols are allowed, but remain the same for all data sets in the concatenation.
Assume the logical map to be D1=>D2=>Q2=>P2, with the physical map including Q1 and P1 prior to
Q2 and P2, respectively.
Start with the following DD statement in your processor, where &LIB=MACLIB is specified in the
processor:
SYSLIB DD DSN=BST.MORMI08.&LIB,DISP=SHR
DD DSN=BST.CSCRE.&C1SY..&C1SU..&C1EN(1,1)&C1S#..&LIB,
DISP=SHR,ALLOC=LMAP
If executing the processor in DEV stage 1, system NDVR, subsystem MORMI08, the logical map
allocation would be generated as follows:
SYSLIB DD DSN=BST.MORMI08.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.NDVR.MORMI08.D1.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.NDVR.MORMI08.D2.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.NDVR.BASE.Q2.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.NDVR.BASE.P2.MACLIB,DISP=SHR
If the prior DD’s were coded with ALLOC=PMAP, the following physical map allocations would result:
SYSLIB DD DSN=BST.MORMI08.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.NDVR.MORMI08.D1.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.NDVR.MORMI08.D2.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.NDVR.BASE.Q1.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.NDVR.BASE.Q2.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.NDVR.BASE.P1.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.NDVR.BASE.P2.MACLIB,DISP=SHR
04-May-2018 292/1109
CA Endevor® SCM - 17.0
SYSLIB DD DSN=BST.MORMI08.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.NDVR.BASE.Q2.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.NDVR.BASE.P1.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.NDVR.BASE.P2.MACLIB,DISP=SHR
In addition, if the DD statements were coded as follows, with the subsystem symbol &SUBSYS, and
where &SUBSYS=&C1SU.. is specified in the processor, the same respective allocation results as
above would apply :
SYSLIB DD DSN=BST.MORMI08.&LIB,DISP=SHR
DD DSN=BST.CSCRE.&C1SY..&SUBSYS&C1EN(1,1)&C1S#..&LIB,
DISP=SHR,ALLOC={LMAP|PMAP}
Assume the logical map to be D1=>D2=>Q2=>P2, with the physical map including Q1 and P1 prior to
Q2 and P2, respectively.
This enhancement does not provide the capability of interspersing datasets in a concatenation based
on the map.
If executing a processor in DEV stage 1, system NDVR, subsystem MORMI08, with a DD statement,
after symbolic substitution, that would be allocated as follows (with alternating NDVR and EA data
sets), you would have to make a choice as to which set of data sets needs to be first in the
concatenation, if you want to take advantage of map allocation.
SYSLIB DD DSN=BST.CSCRE.NDVR.MORMI08.D1.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.EA.BASE.D1.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.NDVR.MORMI08.D2.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.EA.BASE.D2.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.NDVR.BASE.Q2.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.EA.BASE.Q2.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.NDVR.BASE.P2.MACLIB,DISP=SHR
DD DSN=BST.CSCRE.EA.BASE.P2.MACLIB,DISP=SHR
If this would not work for your situation, then you would not be able to take advantage of processor
map allocation.
04-May-2018 293/1109
CA Endevor® SCM - 17.0
Symbolic Parameters
Symbolic parameters (symbols) provide a powerful means of writing processors for your
environment. The processors treat the symbols in the same manner as OS JCL treats parameters. A
specific value is substituted for a variable embedded in the JCL. This option lets you write one
processor for multiple environments, systems, subsystem, or stage. You can write one processor to
perform many functions.
User symbols
Site symbols
Additionally, CA Endevor® SCM provides capabilities not available with standard JCL. For example:
You can use a symbol as the numeric operand (portion) in the COND parameter of an execution
statement.
CA Endevor® SCM supports symbolic substitution, using CA Endevor® SCM, site, or user symbols,
within in-stream data.
Note: If your symbol uses double ampersands, then you would specify only one period.
When a statement containing a symbol requires a period after the symbol, the symbol itself must
04-May-2018 294/1109
CA Endevor® SCM - 17.0
When a statement containing a symbol requires a period after the symbol, the symbol itself must
end with one of the following:
. , / ' ) ( * & + - = " or space
When using a symbol for a data set, do not include the member name as part of the symbol or
you get an allocation error. Use two symbols, for example:
//SYSLIB DD DSN=&LIB1(&C1ELEMENT)
When using concatenated symbols to create a symbol, use an intermediate symbol instead or you
get a translation error. For example, if you combine the symbols into a single symbol as shown in
the following sample, the result is an undefined symbol error for the &H&C1SY:
DSN=&H&C1SY..&L1TSTL
However, the following sample does not result in an undefined symbol error, provided that
DISTLQ='&H&C1SY..' is how the intermediate symbol is defined:
DSN=&DISTLQ..&L1TSTL
Symbols Guidelines
When using symbols in CA Endevor® SCM processors, remember that:
When referencing any symbol, an ampersand (&) must be appended to the beginning of the
symbol name.
A user symbol name can consist of any character, except for any of the following terminating
characters: . , / ' ( ) * + - = " or space
User-defined symbolic parameters must be defined in PROC statements at the beginning of the
processor.
You can specify symbols only on the right side of keyword parameters.
For data set allocation, one symbol must replace only one subparameter. For example, to use
symbolic substitution in the statement SPACE=(TRK,(1,1),RLSE), you might code SPACE=(&UNITS,
(&PRIM,&SECD),RLSE). It would be incorrect to code SPACE=(&TRAK,RLSE), because this
statement merges three subparameters (TRK, 1 and 1) into the single symbol &TRAK.
Note: In this case, (1,1) is considered to be two subparameters. Thus, defining a single
symbol to be '1,1' and substituting that symbol in the SPACE statement results in an
allocation error.
Processor symbols are not validated until execution time. Therefore, ensure that user symbols
have valid default values in the processor or valid override values in the processor group
definition.
04-May-2018 295/1109
CA Endevor® SCM - 17.0
When a character string contains symbols, the symbol names must be terminated by a
terminating character. The terminating character is not considered part of the symbol name. It is
just the character at which CA Endevor® SCM stops when searching for symbol names in the
string.
Valid terminating characters are:
period '.'
comma ','
quote '''
asterisk '*'
ampersand '&'
plus '+'
minus '-'
equal '='
If the symbolics are coded as follows, then during resolution CA Endevor® SCM will recognize the
symbolic name &ABC because the name is terminated by a "<". CA Endevor® SCM will recognize the
symbolic name &DEF because it is terminated by a quote character "'". The resolved character string
will be: UVW<ACTIONXYZ
//TEST PROC ABC=UVW,
// DEF=XYZ
//STEP EXEC PGM=IEFBR14,PARM='&ABC<ACTION&DEF'
If &ABC is not terminated by a terminating character, it would not be recognized as a symbolic. The
following coding would resolve the character string to: &ABCAACTIONXYZ
//TEST PROC ABC=UVW,
04-May-2018 296/1109
CA Endevor® SCM - 17.0
//TEST PROC ABC=UVW,
// DEF=XYZ
//STEP EXEC PGM=IEFBR14,PARM='&ABCAACTION&DEF'
User Symbols
User symbols are specific to your site and requirements. As mentioned above, these symbols must be
defined in PROC statements that may be specified in the processor.
Processors treat user symbols in the same manner as does standard JCL-as a specific value is
substituted for a variable embedded in the JCL code. You can override the symbol default values
initially established in the PROC statement. The user symbol override function is part of the processor
group definition procedure.
Note: For more information, see The Processor Group Definition Panel (see page ).
By changing the parameters established for a particular processor, you can use that processor to
perform different functions. The above values are used whenever the processor GCIIDBL is used.
Site Symbols
Site symbols can be used wherever CA Endevor® SCM symbols are used. At execution time, site
symbols referenced by a processor are stored with the processor symbols in the component data. If a
site symbol is also specified as a processor symbol, the processor symbol (and the processor symbol
override) take precedence.
When CA Endevor® SCM is initialized, the site symbols are placed into memory and when CA
Endevor® SCM is terminated, the site symbol storage is released.
To implement site symbols, the symbol and its data value are defined in a table that is assembled and
linked into an authorized load library. Once this is complete, the table is associated with the
appropriate environment by updating SYMBOLTBL parameter in the C1DEFLTS table with the name of
the site symbols table. These actions are described in the following sections.
Note: Site symbols are required if you are using USS path name specifications for element
type base or source output file definitions.
04-May-2018 297/1109
CA Endevor® SCM - 17.0
Assume that your site uses the following site symbols and values:
#ENDPRE -- CA
#MIDDLE -- 'QA&C1SY..S1'
#SITESYM -- 'QA&&#ENDPRE..S1'
If the current system value is ADMIN and the current type value is ASMMAC at runtime, then the
following values would be used:
//IN DD DISP=SHR,DSN=CA.R40.SRCLIB
//OUT DD DISP=SHR,DSN=CA.QAADMIN.S1.OBJLIB
//DUMMY DD DISP=SHR,DSN=CA.QAADMIN.S1.ASMMAC
Site symbol names can contain up to twelve characters, including the "#".
Site symbols are referenced with an ampersand preceding the symbol name. For example, site
symbol #VENDORLB is referenced as:
&#VENDORLB.
1. Define the symbol and its data value. This is the syntax for the site symbols table:
$ESYMBOL SYMNAME=#symbolname,SYMDATA=symbolvalue
04-May-2018 298/1109
1.
symbolname
The symbol name is 2 to 12 characters long and its first character must be a #. The #
indicates that the symbol is defined in the site-defined symbols table.
symbolvalue
The data value associated with the site symbol is 1 to 70 characters in length, with no
restrictions on the content of the data. If you do not specify a data value for a symbol, CA
Endevor® SCM treats it as a null variable.
2. Assemble and link-edit the symbols table. Use JCL member BC1JTABL in iprfx.iqual.CSIQJCL to
assemble and link-edit the site defined symbols table. An alternative is to use an SMP/E
USERMOD to accomplish this.
3. Update C1DEFLTS to associate the site symbols to the CA Endevor® SCM environment.
By using the Site Information panel, you can determine if site symbols are defined in your CA
Endevor® SCM Environment.
Note: A site symbol may contain references to CA Endevor® SCM symbols, or other
site symbols. In such cases, the value of SYMDATA contains the name of the CA
Endevor® SCM or site symbols preceded by a double ampersand (&&). For example,
$ESYMBOL SYMNAME=#H,SYMDATA='BST.CSCRE'
$ESYMBOL SYMNAME=#BASEPRFX,SYMDATA='&&#H..&&C1SY..&&C1EN(1,1)&&C1S#.'
The Site Information from C1DEFLTS panel indicates if site symbols are installed. The name of
the site symbols file is displayed in the SYMBOLICS Table field when symbols are used.
Note: To display your site symbols and the associated values, from the CA Endevor®
SCM Primary Options Menu select the option for Display. Select S to display the site
symbols and values defined in your CA Endevor® SCM environment.
When CA Endevor® SCM encounters a CA Endevor® SCM symbol immediately followed by a period, it
takes one of the following actions:
If the symbol begins with a single ampersand (&), CA Endevor® SCM does not include the period
in the resolved statement.
04-May-2018 299/1109
CA Endevor® SCM - 17.0
If the symbol begins with a double ampersand (&&), CA Endevor® SCM retains the period in the
resolved statement.
For example, assume the symbol &C1SYSTEM is set to TEST, and the following DD statements are
encountered in the processor:
//DD1 DD DSN=&C1SYSTEM..TEST.DATASET,DISP=OLD
//DD2 DD DSN=&&C1SYSTEM..PROD.DATASET,DISP=OLD
As this example shows, if you want a period to follow a CA Endevor® SCM symbol, you must specify
two consecutive periods if your symbol uses a single ampersand, and only one period if your symbol
uses double ampersands.
The symbolic parameters are listed next along with a description of what the symbol is replaced by in
the processor. The numbers in parenthesis following each symbol name indicate the maximum length
of the value to be substituted at execution time.
Note: The symbols in italics beginning with &C1S in the following list should be used only
for the source location of Move or Transfer actions made using the move/generate
processor. The symbols in italics beginning with &C1T in the following list should be used
only for the target location of Move or Transfer actions made using the move/generate
processor. For all other actions that execute a generate processor and actions that execute
a delete processor, CA Endevor® SCM assigns these symbols the same values as those
assigned to the corresponding symbol beginning with &C1.
&C1ACTION (8)
Action currently being executed.
Note: If action is ADD with update option turned on and element exists on store, the
C1ACTION resolves to UPDATE.
&C1ADDMMMYY (7)
Date in the format DDMMMYY. For example: 15JUN01
&C1ADDMMYY (6)
Date in the format DDMMYY. For example: 150601
&C1ADDMMYYYY (8)
Date in the format DDMMYYYY. For example: 15062001
&C1ADD (2)
Date in the format DD. For example: 15
04-May-2018 300/1109
CA Endevor® SCM - 17.0
&C1AMM (2)
Date in the format MM. For example: 06
&C1AMMM (3)
Date in the format MMM. For example: JUN
&C1AYY (2)
Date in the format YY. For example: 01
&C1AYYYY (4)
Date in the format YYYY. For example: 2001
&C1AHHMMSS (6)
Time in the format HHMMSS. For example: 125930
&C1AHHMM (4)
Time in the format HHMM. For example: 1259
&C1AHH (2)
Time in the format HH. For example: 12
&C1ATMM (2)
Time in the format MM. For example: 59
&C1ASS (2)
Time in the format SS. For example: 30
&C1BASELIB (44)
Contains the resolved base library name definition for the current element.
&C1SBASLIB (44)
Base data set name on the Type definition for the action source location. Any embedded symbolic
variables are resolved before the action is performed on the element by source management.
&C1TBASLIB (44)
Base data set name on the Type definition for the action target location. Any embedded symbolic
variables are resolved before any action is performed on the element by source management.
&C1CCID (12)
Last-specified CCID for the element.
&C1ELMCHG (1)
One character used to indicate whether the source manager detected changes to this element;
Y=Yes, N=No.
&C1ELMNOSRC (1)
04-May-2018 301/1109
CA Endevor® SCM - 17.0
&C1ELMNOSRC (1)
Indicates whether this is a NoSource element.Y = Yes, the element is sourceless. N=No, the
element has source.
&C1SELMNOSRC (1)
One character indicating whether the element is Nosource at the source location prior to being
executed by a Move or Transfer action. Y = Yes, the element is sourceless. N=No, the element has
source. The symbol is resolved before the action is performed on the element by source
management.
&C1TELMNOSRC (1)
One character indicating whether the element is Nosource at the target location prior to being
executed by a Move or Transfer action. Y = Yes, the element is sourceless. N=No, the element has
source. The symbol is resolved before the action is performed on the element by source
management.
&C1EUDATA (80)
Up to 80 bytes of user data.
&C1FOOTPRT (64)
Footprint of the element being processed.
&C1LEV (2)
Level number for the element being processed.
&C1SLEV (2)
Element level at the source location prior to being executed by a Move or Transfer action.
&C1TLEV (2)
Element level at the target location prior to being executed by a Move or Transfer action.
&C1MACLIB (44)
Value of MACDSN defined in the C1DEFLTS table.
&C1PKGID (16)
Name of the package being executed. Blank if no package is being executed.
04-May-2018 302/1109
CA Endevor® SCM - 17.0
Note: &C1PRGRP cannot be used as part of the base or delta library data set specification.
&C1PRTYPE (8)
Function of the current processor (generate, move, or delete).
&C1SITE (1)
Current site ID.
&C1SYSID (8)
System ID of the current system the processor is running on.
&C1SARCFIL (1)
Indicates if the source is an archive file. The value can be Y or N.
&C1SELEMENT (8)
Element name at the source of MOVE or TRANSFER actions that execute a move/generate
processor.
04-May-2018 303/1109
CA Endevor® SCM - 17.0
&C1SELMNT10 (10)
CA Panvalet element name at the source of MOVE or TRANSFER actions that execute a move
/generate processor.
&C1SELMNT255 (255)
1-255 character name for elements at the source location of actions such as move and transfer.
Note: When using this symbol within a processor, consider using the processor symbolic
substringing feature. For example, &C1SELMNT255 (10,100).
&C1SELTYPE (8)
Element type at the source of MOVE or TRANSFER actions that execute a move/generate
processor.
&C1SENVMNT (8)
Environment name at the source of MOVE or TRANSFER actions that execute a move/generate
processor.
&C1SPRGRP (8)
Processor group name at the source of MOVE or TRANSFER actions that execute a move/generate
processor.
&C1SSTAGE (8)
Stage name at the source of MOVE or TRANSFER actions that execute a move/generate
processor.
&C1SSTAGE1 (8)
Stage 1 name at the source of MOVE or TRANSFER actions that execute a move/generate
processor.
&C1SSTAGE2 (8)
Stage 2 name at the source of MOVE or TRANSFER actions that execute a move/generate
processor.
&C1SSTGID (1)
Stage ID at the source of MOVE or TRANSFER actions that execute a move/generate processor.
&C1SSTGID1 (1)
Stage 1 ID at the source of MOVE or TRANSFER actions that execute a move/generate processor.
&C1SSTGID2 (1)
Stage 2 ID at the source of MOVE or TRANSFER actions that execute a move/generate processor.
&C1SSTGNUM (1)
Stage number at the source of MOVE or TRANSFER actions that execute a move/generate
processor.
&C1SSUBSYS (8)
Subsystem name at the source of MOVE or TRANSFER actions that execute a move/generate
processor.
04-May-2018 304/1109
CA Endevor® SCM - 17.0
&C1SSYSTEM (8)
System name at the source of MOVE or TRANSFER actions that execute a move/generate
processor.
&C1USERID (8)
User ID associated with the current action.
&C1USRDSN (44)
Data set name of the source for ADD or UPDATE requests.
&C1USRFILE (255)
Source USS file names for the ADD or UPDATE requests.
Note: When using this symbol within a processor, consider using the processor symbolic
substringing feature. For example, &C1USRFILE (5,150).
&C1USRMBR (10)
Source member name for the ADD or UPDATE requests.
&C1USRPATH (768)
USS path name of the source for the ADD or UPDATE requests.
Note: When using this symbol within a processor, consider using the processor symbolic
substringing feature. For example, &C1USRPATH(720,48).
&C1VER (2)
Version number of the element being processed.
&C1SVER (2)
Element version at the source location prior to being executed by a Move or Transfer action.
&C1TVER (2)
Element version at the target location prior to being executed by a Move or Transfer action.
&C1XLANG (8)
External language for the element type.
Note: The &&C1VIOUNIT variable is taken from the VIOUNIT value in the C1DEFLTS table
and used throughout the CA Endevor® SCM process. This value is only obtained by the
initialization program BC1PINIT and set for use throughout the product.
Substringing
CA Endevor® SCM lets you substring symbolic variables. Substringing lets you use portions of the
symbol value in the processor. A substring expression is identified as follows:
&SYMBOLIC(start,length,pad)
04-May-2018 305/1109
CA Endevor® SCM - 17.0
In this expression:
start
The position within the symbol where substringing is to begin.
Default: 1.
length
Indicates the length of the substituted value.
Default: Length of the symbol.
pad
A single character used for padding.
Default: Blank.
If the start length is greater than the maximum symbol length, CA Endevor® SCM does not perform
the substring substitution. If the length of the substring exceeds the length of the symbol, CA
Endevor® SCM substitutes the specified characters and the remainder of the substring is filled with
the pad character.
For example, your data set names are prefixed with a special two-character code denoting your
department. When you use the data set name in a processor, however, you want to exclude the
department identification. Therefore, you might code a statement similar to the following:
DSN=&dsname(3,3).LOADLIB
In this example, (3,3) indicates that you want to begin with the third character of the substitution
value and you want the substituted entry to consist of the third, fourth, and fifth characters of the
substituted value.
In this example, the data set name to be used for &dsname is APNDVR01. Using the above substring
statement, the characters AP are ignored and the substituted value begins with the third character (N
). Because you have indicated a length of 3, CA Endevor® SCM substitutes only three characters, N, D,
and V. The result of the substitution is:
DSN=NDV.LOADLIB
If you want to designate a specific character, rather than blanks, to pad the substituted value,
simply include that character in the substring. In the above example, assume you want to use
dollar signs ($) to pad the substituted value. This particular substring is coded as (3,7,$), and the
substituted value is NDVR01$.
You can indicate the substring start position, length, and pad character as symbolic parameters. For
example, you may assign:
04-May-2018 306/1109
CA Endevor® SCM - 17.0
DSN = &dsname(&S,&L,&P).LOADLIB
When you use several symbolic parameters (nested symbols), CA Endevor® SCM begins substitution
with the innermost parentheses. The following example illustrates the principles discussed in this
section:
DSN = &LIB(&C1ELEMENT(&S,&L,&P))
where:
&LIB = CA.LIB
&C1ELEMENT = ABC
&S = 1
&L = 8
&P = $
CA Endevor® SCM resolves this statement by substituting the values for the following:
the starting position (&S), length (&L), and padding character (&P):
DSN = &LIB(&C1ELEMENT(1,8,$))
&C1ELEMENT:
DSN = &LIB(ABC$$$$)
&LIB:
DSN = CA.LIB
When CA Endevor® SCM finishes resolving the statement, the result is:
DSN = CA.LIB(ABC$$$$$)
Note: When using a substring within an IF statement in a processor, you must put a set of
single quotes around the substringing part of the statement. For example:
IF(('&C1ELEMENT(1,3)'='ACC'))
In-Stream Data
CA Endevor® SCM supports in-stream data (DD*/DD DATA), which are coded according to JCL syntax.
04-May-2018 307/1109
CA Endevor® SCM - 17.0
Columns 73 through 80 are unpredictable within processor data. If any symbolic parameters are
present, substitution occurs only between columns 1 and 72 of the input statement. Each line is
truncated or padded to 72 characters.
To turn on wrapping for a symbolic that is longer than 72 characters (a long-name symbolic), the
parameter C1WRAP must be set to Y on the processor PROC statement. If C1WRAP is set to
anything else, or is absent, no wrapping occurs.
When wrapping is turned on by C1WRAP, long-name symbolics are split on several lines in the
following ways:
If there are blank characters in columns 72 through 80 and a long-name symbolic is used,
substitution occurs and the line is split on several lines with a length of 72. If spaces exist in
the substituted line, CA Endevor SCM tries to split it on the space character if that is possible.
If SCL syntax is used in the in-stream data, CA Endevor SCM joins lines without space characters if
the split is in the middle of a name in apostrophes. Therefore, if the name contains spaces, split it
manually with a substring to keep the spaces in the correct positions.
BPXBATCH uses a different approach to joining more lines in the in-stream data. It joins them
with an additional space character between them. Because of this, you need to edit this string to
remove those space characters to get the original string (if it did not contain spaces).
The whole name is sent to SED program, which substitutes all space characters with empty
characters. After that, the substituted name is sent to XARGS which constructs an
argument list and run a command (for example, in this case it is ls - l).
04-May-2018 308/1109
CA Endevor® SCM - 17.0
Use of symbolic variables and IF-THEN-ELSE statements to control the inclusion (or exclusion) of
complete DD statements and input in-stream data.
At run time, the IF-THEN-ELSE statement is evaluated and then the appropriate statements are
selected for inclusion. Consequently, the processor JCL can be customized at each run without
causing intervening modifications to the processor.
The CA Endevor® SCM IF-THEN-ELSE statement is similar to the COND and EXECIF keywords function.
However, the IF-THEN-ELSE statement provides the following advantages over the COND and EXECIF
keywords:
One-time coding.
COND and EXECIF keywords must be coded on each applicable EXEC statement.
CA Endevor® SCM allows selection of steps and DD statements using not only condition codes from
prior steps but also values of CA Endevor® SCM symbols and processor symbols. This allows the
customer more control of the processor execution.
The basic syntax of IF-THEN-ELSE follows the syntax of most JCL statements, but also has some
idiosyncrasies. Columns 1 and 2 must contain slashes "//". An optional name may be placed in
Column 3, can be up to eight characters long, and must be followed by a blank.
Note: We recommend that you specify a name. This action helps in the debugging process.
Syntax example
//TEST1 IF keyword operator value THEN
//
.
.
.
statements
//ELSE1 ELSE
//
.
.
04-May-2018 309/1109
CA Endevor® SCM - 17.0
.
statements
//ENDIF1 ENDIF
keyword
RC
ABENDCC
ABEND
¬ABEND
RUN
¬RUN
operator
EQ or =
GT or >
NE or ¬=
LE
LT or <
GE
Note: For more information about these operators, see The EXECIF Keyword (see page )
.
value
Values are:
1- to 16-characters in length
Alphanumeric
Numerics. Numeric values must always be enclosed in quotes. There is one exception to this rule,
04-May-2018 310/1109
CA Endevor® SCM - 17.0
Numerics. Numeric values must always be enclosed in quotes. There is one exception to this rule,
if the numeric value is compared to the RC keyword, quotes are not required.
statements
Represents any valid JCL statements inserted between the IF-THEN-ELSE statements.
The entire statement must be coded within the IF-THEN-ELSE structure. If a JCL statement is
continued on multiple lines, it must be completed before an intervening IF-THEN-ELSE is
encountered.
04-May-2018 311/1109
CA Endevor® SCM - 17.0
If the return code of STEP1 is equal to 0, STEP2 and STEP3 are executed. STEP4 is not
executed.
If &STAGE is equal to PRD when STEP2 is executed, then DD1, DD2, and DD3 are included in
the step definition. DD4 is not included in the step definition.
04-May-2018 312/1109
CA Endevor® SCM - 17.0
If &STAGE is equal to PRD when STEP2 is executed, datasets INPUT1, INPUT2, INPUT3 are
included in the dataset concatenation defined by DD1. The INPUT4 dataset is not included.
An IF-THEN-ELSE IF specification may extend over multiple statements. The specification must
be within columns 1 - 71 of each statement. Column 72 may contain an X to indicate a
continuation of the line, but it is not mandatory.
Example (An IF statement extending over multiple statements, without an 'X' in column 72)
CC CC
1 72
//TESTIF IF ((&STG. EQ PRD1) OR (&STG. EQ PRD2)
// OR (&STG. EQ PRD3) OR (&STG. EQ PRD4)
// OR (&STG. EQ PRD5)) THEN
Example (An IF statement extending over multiple statements, with an 'X' in column 72)
CC CC
1 72
//TESTIF IF ((&STG. EQ PRD1) X
// OR (&STG. EQ PRD2) X
// OR (&STG. EQ PRD3) X
// OR (&STG. EQ PRD4) X
// OR (&STG. EQ PRD5)) THEN
The THEN clause may be on the same statement as the preceding IF definition or it can be specified
on a subsequent statement. All text to the right of the THEN clause is treated as comments.
The syntax in this IF-THEN-ELSE definition is rejected at translation time because anything on the first
statement following the THEN clause is treated as a comment.
IF-THEN-ELSE specifications can be nested, however. The above could have been coded in the
following manner.
//T1 IF(&SYS. EQ ACC)
// THEN
//T2 IF(&SUB. EQ REC)
// THEN
04-May-2018 313/1109
CA Endevor® SCM - 17.0
// THEN
//STEP EXEC PGM=COBOL1
//T2 ELSE
//STEP EXEC PGM=COBOL2
//T2 ENDIF
//T1 ELSE
//STEP EXEC PGM=COBOL3
//T1 ENDIF
DD statements related to an EXEC must be included within the IF-THEN-ELSE block for that step. CA
Endevor® SCM has no way of knowing that DD statements following an EXEC statement belong to a
prior statement. In short, the step must be complete as if IF-THEN-ELSE were not coded. As an
example, this processor is invalid:
//IF IF (&COBOL='1'). THEN
//STEP1 EXEC PGM=COBOL1
// ELSE
//STEP1 EXEC PGM=COBOL2
// ENDIF
//SYSIN DD DISP=SHR,DSN=INPUT.SOURCE
//SYSLIN DD DISP=SHR,DSN=OBJECT.OUTPUT
//...
It is desirable to associate the DD statements with program COBOL1 or program COBOL2. However,
in this case the DD statements are only associated with program COBOL2. If the IF-THEN-ELSE
statements are removed, the DDs are allocated to the COBOL2 program. Internally, DD statements
are associated with the prior exec statement. To associate the DD statements with the first exec
statement, they must be duplicated in that step. This example is valid:
// IF (&COBOL='1') THEN
//STEP1 EXEC PGM=COBOL1
//SYSIN DD DISP=SHR,DSN=INPUT.SOURCE
//SYSLIN DD DISP=SHR,DSN=OBJECT.OUTPUT
//...
// ELSE
//STEP1 EXEC PGM=COBOL2
//SYSIN DD DISP=SHR,DSN=INPUT.SOURCE
//SYSLIN DD DISP=SHR,DSN=OBJECT.OUTPUT
//...
// ENDIF
The relational expression of the IF statement tests six IBM-defined possible expressions and the CA
Endevor® SCM symbolic variables and literals. The six IBM expressions are:
RC
ABENDCC
ABEND
¬ABEND
RUN
¬RUN
¬RUN
04-May-2018 314/1109
CA Endevor® SCM - 17.0
RC Expression
Indicates the relational expression tests a return code. Evaluate a return code by coding RC, a
comparison operator, and a numeric value.
IF(RC=8)
Tests for a return code equal to 8 from any previous step.
IF(stepname.RC>=10)
Tests for a return code greater than or equal to 10 from a specified step.
IF(ABENDCC=Sxx)
Tests true when most recent system abend is equal to Sxx.
IF(ABENDCC=Uxxxx)
Tests true when most recent user abend is equal to Uxxxx.
IF(stepname.ABENDCC=Sxxx)
Tests true when a specific step abends with Sxxx.
ABEND Expression
Indicates the relational expression tests for an abend condition that occurred during processing of a
prior job step.
IF(ABEND)
Tests true if an abend occurs on any previous step.
IF(stepname.ABEND)
Tests true if an abend occurred on a specific step.
ABEND Expression
Indicates the relational expression verifies an abend condition did not occur during the execution of a
prior job step.
IF(¬ABEND)
Tests true when no abend occurred on any previous step.
IF(¬stepname.ABEND)
Tests true when no abend occurred on a specific step.
04-May-2018 315/1109
CA Endevor® SCM - 17.0
IF(stepname.RUN)
IF(stepname.RUN=TRUE)
Include the following ddname in your CA Endevor® SCM JCL to activate the trace.
//EN$TRITE DD DUMMY
The following is extracted from an output listing of an action with tracing activated:
C1G0249I //T01 IF ((&C1SY. EQ 'SYSTEM')AND(&C1SU. NE 'SUB1'))
C1G0249I // OR((&C1SY. EQ 'SYSTEM2')AND(&C1SU. EQ 'SUB1'))
C1G0249I // OR((&C1SY. NE 'SYSTEM2')AND(&C1SU. EQ 'SUB3')))
C1G0249I //T01 THEN
C1G0249I //T02 IF(('&C1ELEMENT(1.,3)'='ACC'))
C1G0249I //T02 THEN
C1G0249I //STEP1 EXEC PGM=COBOL1
C1G0249I //T02 ELSE
C1G0249I //STEP2 EXEC PGM=COBOL2
C1G0249I //T02 ENDIF
C1G0249I //T01 ELSE
C1G0249I //STEP3 EXEC PGM=COBOL3
C1G0249I //T03 IF (&C1TY='JCL').
C1G0249I //T03 THEN
C1G0249I //DD1 DD DSN=SYS2.PROCLIB,DISP=SHR
C1G0249I //DD2 DD DSN=SYS2.LINKLIB,DISP=SHR
C1G0249I //T03 ELSE
C1G0249I //T03 ENDIF
C1G0249I //T01 ENDIF
C1G0011I PROCESSOR SYMBOLIC SUBSTITUTION OCCURRED-
C1G0009I ORIGINAL :&C1SY.
C1G0009I SUBSTITUTED:GIKSYS
C1G0009I ORIGINAL :&C1SU.
C1G0009I SUBSTITUTED:GIKSUB
C1G0009I ORIGINAL :&C1SY.
C1G0009I SUBSTITUTED:GIKSYS
C1G0009I ORIGINAL :&C1SU.
C1G0009I SUBSTITUTED:GIKSUB
C1G0009I ORIGINAL :&C1SY.
C1G0009I SUBSTITUTED:GIKSYS
C1G0009I ORIGINAL :&C1SU.
C1G0009I SUBSTITUTED:GIKSUB
C1G0009I ORIGINAL :&C1ELEMENT(1.,3)
C1G0009I SUBSTITUTED:T01
C1G0009I ORIGINAL :&C1TY.
C1G0009I SUBSTITUED:JCL
C1X0000I ITE(T01 )Expression: GIKSYS EQ SYSTEM1 Result: FALSE
C1X0000I ITE(T01 )Expression: GIKSUB NE SUB1 Result: TRUE
C1X0000I ITE(T01 )Connecting: FALSE AND TRUE, Result: FALSE
C1X0000I ITE(T01 )Expression: GIKSYS EQ SYSTEM2 Result: FALSE
C1X0000I ITE(T01 )Expression: GIKSUB EQ SUB1 Result: FALSE
C1X0000I ITE(T01 )Connecting: FALSE AND FALSE, Result: FALSE
04-May-2018 316/1109
CA Endevor® SCM - 17.0
C1X0000I ITE(T01 )Connecting: FALSE AND FALSE, Result: FALSE
C1X0000I ITE(T01 )Expression: GIKSYS NE SYSTEM2 Result: TRUE
C1X0000I ITE(T01 )Expression: GIKSUB EQ SUB3 Result: FALSE
C1X0000I ITE(T01 )Connecting: TRUE AND FALSE, Result: FALSE
C1X0000I ITE(T01 )Connecting: FALSE OR FALSE, Result: FALSE
C1X0000I ITE(T01 )Connecting: FALSE OR FALSE, Result: FALSE
C1X0000I ITE(T01 )ITE IF encountered, truth set to FALSE
C1X0000I ITE(T02 )Expression: T01 EQ ACC Result: FALSE
C1X0000I ITE(T02 )ITE IF encountered, truth set to FALSE
C1X0000I ITE(T02 )ITE ELSE encountered, truth set to TRUE
C1X0000I C1GP2000: Step STEP2 selected for execution by ITE
C1X0012I STEP STEP2 INVOKING PROGRAM COBOL2
C1X0010I STEP STEP2 PROGRAM COBOL2 COMPLETED, RC=0000
C1X0000I C1GP2000: Step STEP2 has completed, RC(0000)
C1X0000I ITE(T02 ) ITE ENDIF encountered, truth set to FALSE
C1X0000I ITE(T01 ) ITE ELSE encountered, truth set to TRUE
C1X0000I C1GP2000: step STEP3 selected for execution by ITE
C1X0000I ITE(T03 ) Expression: JCL EQ JCL Result: TRUE
C1X0000I ITE(T03 ) ITE IF encountered, truth set to TRUE
C1X0000I DD DD1 included by ITE
C1X0000I DD DD2 included by ITE
C1X0012I STEP STEP3 INVOKING PROGRAM COBOL3
C1X0010I STEP STEP3 PROGRAM COBOL3 COMPLETED, RC=0000
C1X0000I C1GP2000: Step STEP3 has completed, RC(0000)
Note: For more information, see Trace Facilities (see page 1107).
Some user programs in a processor dynamically allocate data sets. Typical examples are IKJEFT01 and
EDCPRLK. When these programs read or write members to the data sets, the user has no control over
the following parameters:
MONITOR=COMPONENTS
BACKOUT=N
FOOTPRNT=CREATE
As a result, the default values for these parameters are used. Therefore, by default:
04-May-2018 317/1109
CA Endevor® SCM - 17.0
You can change these defaults, even though the file allocations are beyond your control, by
specifying special DDNAMES for the data sets that receive special treatment. Any DDNAME starting
with EN$DYN can be used to specify one or more data set names with their monitor, backout, and
footprint specification.
CA Endevor® SCM does not support FOOTPRNT=CREATE on a concatenated data set. Therefore, if
FOOTPRNT=CREATE is required, more than one statement is required.
In the following example, no backout records are written to the file &SYSLIB1, even if IKJEFT01
allocates it and writes members to &SYSLIB1. Similarly, all members created in SYSLIB2 are
footprinted.
//STEP1 EXEC PGM=IKJEFT01
//EN$DYN00 DD DISP=SHR,DSN=&SYSLIB1.,BACKOUT=NO
//EN$DYNM DD DISP=SHR,DSN=&SYSLIB2.,FOOTPRNT=CREATE
In the following example, components are monitored from all files in the SYSLIB concatenation, even
if EDCPRLK reallocates each file separately under another DDNAME.
//PRELINK EXEC PGM=EDCPRLK
//SYSLIB DD DISP=SHR,DSN=&SYSLIB1.,MONITOR=COMPONENTS
// DD DISP=SHR,DSN=&SYSLIB2.,MONITOR=COMPONENTS ETC.
//EN$DYNDS DD DISP=SHR,DSN=&SYSLIB1.,MONITOR=COMPONENTS
// DD DISP=SHR,DSN=&SYSLIB2.,MONITOR=COMPONENTS ETC.
Note: In the previous example, you can remove the MONITOR=COMPONENTS statements
from the SYSLIB concatenation. This is because the MONITOR=COMPONENTS statements
on the EN$DYNDS DD statement cause all components to be monitored, regardless of
whether each file is reallocated separately under another DDNAME.
Internal Reader
By default, any job submitted to the internal reader by a processor step runs under the security
credentials of the user ID. You can override this by specifying INTRDR_ALTID=ON in the CA Endevor®
SCM options table. When this value is specified, jobs submitted to the internal reader run under the
security context of the alternate ID.
However, if you code ALTID=N on the EXEC statement of a processor, then any jobs submitted to the
internal reader run under the security credentials of the user ID, regardless of the setting of
INTRDR_ALTID.
If you are using CA Top Secret for z/OS, the CA Top Secret global option of JES(VERIFY)
should be set if you want CA Endevor® SCM to submit JOBs to the INTRDR, using the
credentials of the CA Endevor® SCM User ID. If JES(VERIFY) is not specified, CA Endevor®
SCM's default behavior for CA Top Secret is to submit jobs to the internal reader using the
alternate ID.
04-May-2018 318/1109
CA Endevor® SCM - 17.0
Processor Utilities
Including Processor Utilities in Processor Logic (see page 319)
BC1PDSIN Utility (see page 321)
BC1PTMP0 Utility (see page 322)
BC1PXFPI Utility (see page 325)
BSTCOPY Utility (see page 326)
C1BM3000 Utility (see page 330)
C1PRMGEN Utility (see page 332)
CONAPI Utility (see page 333)
CONDELE Utility (see page 334)
CONLIST Utility (see page 335)
CONPARMX Utility (see page 341)
CONRELE Utility (see page 349)
CONSCAN Utility (see page 353)
CONWRITE Utility (see page 364)
ENUSSUTL Utility (see page 370)
LEXTRCTR and BC1PCCSP Utilities (see page 370)
BC1PDSIN
(No) Initializes any number of allocated data sets that begin with ddname C1INIT. This utility is
generally used to allocate list data sets.
BC1PTMP0
(Yes) Executes TSO commands, once a TSO environment has been created. This program accepts
as input a parameter defining the data set containing the TSO commands to be called. BC1PTMP0
acts as a terminal monitor program and command processor, calling one program (EXEC) to place
the commands in a TSO stack, then issuing GETLINE requests to extract the commands from the
TSO stack.
BC1PXFPI
(No) Installs “transportable” footprints in object modules generated under z/OS, VSE, or z/VM.
Note: For more information about "transportable" footprints, see Administrating (see
page 36).
04-May-2018 319/1109
CA Endevor® SCM - 17.0
BC1PMVCL
(No) Provides the ability to update the component list to reflect the location of the output
components as the result of the move processor. (The Delta library, where the component list is
stored, cannot be a USS file.)
BSTCOPY
(No) Copies members from one partitioned data set to another. BSTCOPY allows for the use of
MONITOR=COMPONENTS and backout.
C1BM3000
(Yes) Executes CA Endevor® SCM from within a processor.
C1PRMGEN
(No) Creates 80-column (card-image) statements from a parameter passed to the utility. These
statements, once expanded, are passed as input control statements to subsequent job steps.
C1PRMGEN expands any CA Endevor® SCM symbolic parameters contained in the statements,
allowing you to vary the input control specifications based on the values of CA Endevor® SCM
symbolic parameters.
CONAPI
(Yes) Invokes a program which issues API calls through a processor.
CONDELE
(Yes) Removes a member from a user library or USS directory, after verifying the footprint for the
member.
CONLIST
(No) Manages output listings generated by the processors: store (and footprint) new members in
listing libraries, print listings stored as sequential files or as members in listing libraries, or copy a
member from one listing library to another (optionally after appending one or more listings at the
end of the member).
CONPARMX
(Yes) Reduces processor complexity and the number of CA Endevor® SCM Processor Groups. The
primary use of CONPARMX is to support varying program (for example: compiler or linkage
editor) options without having to create and update large numbers of processors or processor
groups by allowing different levels of Options members (Default, Processor Group, Element) to be
included at execution time.
CONRELE
(Yes) Includes entities related to an element in a component list when generating component list
reports and when using the LIST action.
CONSCAN
(No) Creates ACM relationships between a CA Endevor® SCM ELEMENT and scanned values from
the content of the ELEMENT. It then applies parsing rules to the ELEMENT content, and passes
these as standard CONRELE syntax to the CONRELE step as exemplified in the CONSCAN
prototype.
04-May-2018 320/1109
CA Endevor® SCM - 17.0
CONWRITE
(Yes) Combines all levels of an element, optionally expands INCLUDE statements and writes the
merged source to a user-specified data set or USS directory. Can be used as input to a specified
program.
Writes a component list to an external data set for further processing.
ENBX1000
(Yes) For more information, see Expand Includes Utility (see page 1060).
ENUSSUTL
(Yes) Collects package backout information for USS processor output files.
LEXTRCTR
To parse and capture all the pieces of a CSP application when the user is managing at the
application rather than the component level.
BC1PCCSP
Attaches the compiler for each piece of the application identified by LEXTRCTR.
ENBS1000-Text Search-and-Replace
Important! ELIB utilities, BC1PNLIB, NCPY, and NLST cannot be used within a processor.
BC1PDSIN Utility
BC1PDSIN can be used to initialize sequential data sets. For example, in a processor with COMPILE,
LINK, and CONLIST steps (where CONLIST uses temporary listing data sets created by the COMPILE
and LINK steps), an allocation error would occur in the CONLIST step if the COMPILE or LINK did not
run thereby not creating the needed temporary data sets. If you use BC1PDSIN, however, it allocates
temporary data sets, so CONLIST has the files it needs to execute.
BC1PDSIN initializes all data sets that are allocated by the C1INIT or C1LIST DD statements. If you
specify more than one C1INIT or C1LIST data sets, assign the ddnames sequentially. For example,
C1LIST01, C1LIST02 and so forth, or C1INIT01, C1INIT02, and so forth.
04-May-2018 321/1109
CA Endevor® SCM - 17.0
DSORG=PO
To allocate but not initialize an entire temporary PDS, use a DDNAME that does not begin with
//C1INIT. For example, //C2INIT, //TEMPPDS, or //C1INTPO. This allocates the library in the same
manner as IEFBR14.
Sample JCL
BC1PTMP0 Utility
BC1PTMP0 allows TSO commands to be executed once a TSO environment has been created. The
program accepts as input a parameter that defines the data set containing the TSO commands to be
called. This program is usually used for processors that are executed under the CA Endevor® SCM
ISPF dialog.
Note: BC1PTMP0 issues TSO command processor STACK services using the BARRIER option.
Only releases of TSO that support the BARRIER option can use this utility.
Note: If using a REXX EXEC instead of a TSO CLIST, a PUSH END statement must be coded at
the end of the EXEC.
BC1PTMP0 first checks whether a TSO environment is present and performs the following actions:
Note: For more information about return codes, see Return Codes (see page 323).
04-May-2018 322/1109
CA Endevor® SCM - 17.0
If a TSO environment is present, BC1PTMP0 acts as a terminal monitor program and command
processor. BC1PTMP0 calls the program EXEC, which then places the commands (specified in the
data set coded on the PARM= parameter) in the TSO stack. BC1PTMP0 issues GETLINE requests to
extract those commands from the TSO stack.
TSO does not allow the program IKJEFT01, a TSO program, to be executed once TSO processing has
started. (That is, TSO does not allow TSO to run under it.) Executing BC1PTMP0 in a processor rather
than executing IKJEFT01 allows TSO commands to be executed within a CA Endevor® SCM processor.
The CA Endevor® SCM for DB2 product requires the use of BC1PTMP0.
You can code a BC1PTMP0 step and a IKJEFT01 step in a processor, so that BC1PTMP0 executes, if the
processor is running under TSO, and IKJEFT01 executes, if the processor is running in batch mode.
Use the following steps to implement this technique.
//TSOMODE EXEC PGM=BC1PTMP0
//XX
//BATMODE EXEC PGM=IKJEFT01,COND=(5,NE,TSOMODE)
//XX
Important! ISPF services cannot be invoked in a TMP. CA Endevor® SCM is using ISPF
services to invoke the processor and an attached TMP (BC1PTMP0) can not start another
ISPF service in the same TSO address space. ISPF services (ISPEXEC, ISPSTART, etc.) cannot
be invoked via BC1PTMP0.
PARM=
The name of the data set containing the commands to be executed by BC1PTMP0.
uprfx.uqual.CLISTLIB
The name of the CLIST library containing the commands that you want to execute.
clist
The name of the CLIST that you want to execute.
iprfx.iqual.CSIQLOAD
The CA Endevor® SCM installation load library containing the program BC1PTMP0. (For DB2
processors, you may need to add your DB2 load library.)
Return Codes
BC1PTMP0 utility can return any of the following return codes:
04-May-2018 323/1109
CA Endevor® SCM - 17.0
0
All commands were successfully processed.
5
TSO (that is, program IKJEFT01) currently is not active. This step within the processor was
executed, however.
6
No parameter was specified in the PARM= statement within the JCL, or a data set name greater
than 56 characters was specified.
7
A command specified in the CLIST was not found. BC1PTMP0 attempts to load all programs prior
to issuing an ATTACH. If the load fails, this return code is passed back to.
8
The PARM= specification on the EXEC card was coded incorrectly, for example:
Parameter does not end with a pair of parentheses surrounding a member name
9
A GETMAIN failed for the command buffer required by attached programs. BC1PTMP0 attempted
to acquire a command buffer in subpool 78 and the GETMAIN failed.
Any program or command invoked by BC1PTMP0 can issue any return code for their own reasons.
This includes return codes 5,6,7,8,9 and any other return code. BC1PTMP0 simply returns the return
code passed by those programs. For example, a command invoked by BC1PTMP0 may return a RC=8
when it gets an allocation error. A different command invoked by BC1PTMP0 may return a RC=8
when a program is not found.
Assume that a processor running in foreground is executing BC1PTMP0 which invokes a CLIST or a
REXX exec to execute a DB2 Bind. A STEPLIB in the BC1PTMP0 step defines the library containing the
DB2 DSNxxxxx programs. In this case, the STEPLIB is ignored and an 806 occurs. The error occurs if
the following processor step and CLIST are coded:
04-May-2018 324/1109
CA Endevor® SCM - 17.0
The problem occurs due to the way the program DSN is invoked internally by BC1PTMP0. To correct
this, the REXX exec or CLIST must be invoked by a different method. To use this method, code a DD
statement with the name EN$SELCT in the BC1PTMP0 definitions. Also, the library containing the
REXX exec must be a member of the SYSPROC dd definition. In the following corrected processor
step, the clist library 'PROD.CLIST' was defined to the SYSPROC DD concatenation.
If this method is used, then the STEPLIB is passed through to the invocation of the DB2 DSN
programs.
BC1PXFPI Utility
The BC1PXFPI utility installs “transportable” footprints in object modules generated under z/OS, VSE,
or z/VM. Transportable footprints provide footprint audit trails for software that executes in non-z
/OS environments (VSE and z/VM).
Note: For more information about transportable footprints, see Footprint Synchronization
(see page 438). (This facility is for non-z/OS environments only).
BC1PMVCL Utility
The BC1PMVCL utility provides the ability to update the component list to reflect the location of the
output components as the result of the move processor.
A move processor typically copies the outputs of the generate processor from their libraries to the
next stage's output libraries. Once the outputs have been copied, the move processor typically also
copies the existing component list to the new inventory area. The utility to move component lists is a
pseudo processor program called BC1PMVCL.
04-May-2018 325/1109
CA Endevor® SCM - 17.0
When using BC1PMVCL, the existing component data does not get updated so all the input and
output components in the component list reflect the data sets used at generate time. If, in a move
processor, MONITOR=COMPONENTS is coded on the output files, and BC1PMVCL is part of the
processor (as the last step), CA Endevor® SCM :
Technically, the BC1PMVCL does not have to be the last step; however, it must execute after all
monitored components. If components have been monitored in a move processor (prior to the
execution of BC1PMVCL), then all of the gathered output components is used to replace all existing
output components in the existing component list. These gathered output components are
subsequently removed from the storage lists in which they were collected to avoid subsequent
update at the end of the processor execution.
This causes output component lists to be generated by a move if a move processor has collected new
output components prior to the execution of BC1PMVCL. The output components replace all output
in the existing components list.
BC1PMVCL provides the ability to update the component list to reflect the location of the output
components as the result of the move processor.
The move processor utility BC1PMVCL now can dynamically replace old Endevor output components
with the new output components at the end of the move processor execution. By using BC1PMVCL in
your move processor, Quick Edit commands LL and LO function after a move.
BSTCOPY Utility
The BSTCOPY utility offers a limited subset of the functionality provided by IEBCOPY.
You must use BSTCOPY instead of IEBCOPY if you use the CA Endevor® SCM Automated Configuration
Manager (ACM), or if package backout has been enabled for the output library. This is because CA
Endevor® SCM cannot determine which members are changed by IEBCOPY.
BSTXCOPY is a CA Endevor® SCM utility that performs the same functions as the CA Endevor® SCM
processor utility BSTCOPY. However, you can use BSTXCOPY to perform these functions outside of a
CA Endevor® SCM processor.
BSTCOPY can copy aliases, but the alias must be explicitly requested. To copy an alias, the original
loadlib member must be copied first. For more information about aliases, see BSTCOPY and Aliases
(see page 327).
Copying from a PDSE load library to a PDS may result in errors, depending on whether the PDSE
04-May-2018 326/1109
CA Endevor® SCM - 17.0
Copying from a PDSE load library to a PDS may result in errors, depending on whether the PDSE
contains any program object members which cannot be converted back to load modules. This
includes program objects which are greater than 16 megabytes in size, or which included mixed-case,
extended names, or contain more than 32K of external symbols.
Note: For more information about the conversion restrictions, see the program
management manuals for DFSMS/MVS 1.1 or higher.
BSTCOPY is not intended to replace IEBCOPY. Rather, it is provided to support simple member copy
operations from one library to another.
When a PDS load module is copied to a PDSE, CA Endevor® SCMinframe load module footprint
information is retained only if the CA Endevor® SCM processor utility BSTCOPY is used. Other utilities,
such as IEBCOPY, do not have the capability to copy the *LOADMOD footprint. For more information,
see TEC316937, How to Convert AllFusion Endevor Change Manager Load Libraries between PDS and
PDSe Formats, on ca.com/support.
Important! Spaces before or after the comma between COPY INDD and OUTDD results in a
syntax error.
To bring loadonly software under CA Endevor® SCM control, use the following method, which
requires two steps in the Generate processor:
A BSTCOPY step to copy all the results into the final target PDSE library. This latter step
ensures that the CA Endevor® SCM Automated Configuration option output components are
monitored, while preserving the aliases.
04-May-2018 327/1109
CA Endevor® SCM - 17.0
To copy aliases of load modules or program objects inside a Move processor, use the following
method. The temporary library and the source library for IEBCOPY must be the same library type
(PDS or PDSE). Otherwise IEBCOPY might not copy the *LOADMOD Footprint.
The following Move Processor example uses this method:
//IF2 IF (&C1ACTION=TRANSFER) OR (&C1ACTION=MOVE) THEN
//********FIRST IEBCOPY COPYGRP TO PRESERVE ALIAS***********************
//TRCOPY1 EXEC PGM=IEBCOPY,MAXRC=04
//SYSPRINT DD SYSOUT=*
//FCOPYOFF DD DUMMY
//SYSUT3 DD UNIT=&WRKUNIT,SPACE=(TRK,(1,1))
//SYSUT4 DD UNIT=&WRKUNIT,SPACE=(TRK,(1,1))
//INDD DD DSN=&LOADLIB1,DISP=SHR
//OUTDD DD DSN=&&TMPDSN,DISP=(,PASS),UNIT=SYSDA,
// SPACE=(CYL,(5,5,44)),DSNTYPE=LIBRARY,
// DCB=(LRECL=0,BLKSIZE=32760,RECFM=U,DSORG=PO)
//SYSIN DD *
COPYGRP OUTDD=OUTDD,INDD=INDD
SELECT MEMBER=&C1ELEMENT
//********NOW COPY ALL IN TEMPORARY TO TARGET PDSE**********************
//TRCPY2 EXEC PGM=BSTCOPY,MAXRC=04
//SYSPRINT DD SYSOUT=*
//SYSUT3 DD UNIT=&WRKUNIT,SPACE=(TRK,(1,1))
//SYSUT4 DD UNIT=&WRKUNIT,SPACE=(TRK,(1,1))
//OUTDD DD DSN=&LOADLIB2,DISP=SHR,MONITOR=COMPONENTS
//INDD DD DSN=&&TMPDSN,DISP=SHR,FOOTPRNT=VERIFY
//SYSIN DD *
COPY OUTDD=OUTDD,INDD=((INDD,R))
//********NOW MOVE THE COMPONENT LIST..must be the LAST step ***
//BC1PMVCL EXEC PGM=BC1PMVCL,COND=(0,NE)
//END2 ENDIF
04-May-2018 328/1109
CA Endevor® SCM - 17.0
Copy load modules that have the linkage editor OVERLAY attribute.
Reblock load modules when the BLKSIZE of the input library is greater than that of the output
library.
Support splitting a SELECT statement on multiple lines. A SELECT statement must be specified on
one physical input record.
One solution is to relink the load modules. If the load modules are vendor-supplied, however, and
relinking may jeopardize ongoing vendor support, another solution is to write a two-step processor.
Follow these steps to create the new processor:
1. Create a dummy module and execute a BSTCOPY step that copies it and renames it to the
name of the OVERLAY module. This bypasses the system's security and renames the target
module, creating a backout.
2. Code an IEBCOPY step that copies the real module in, overlaying the dummy module. Because
IEBCOPY cannot be screened, backouts are not affected.
C I=IN,O=OUT
04-May-2018 329/1109
CA Endevor® SCM - 17.0
C I=IN,O=OUT
S M=((&C1ELEMENT.,,R)) <===COPY REAL MEMBER
1. Using the PDSMAN $IEBCOPY statement, BSTCOPY can be replaced with the PDSMAN utility
FASTCOPY. Specify NAME=BSTCOPY on the $IEBCOPY statement to enable this support.
Package shipment jobs and processors coded to run BSTCOPY in this situation execute
FASTCOPY instead.
3. For CA Endevor® SCM Automated Configuration Option users, when executing FASTCOPY,
input components are not collected. Output components are collected and package backout
members and data are collected.
5. Set the $IEBCOPY operand STORFAIL= to the value TERMINATE when using FASTCOPY
substitution for BSTCOPY.
RECFM=VBA
LRECL=121
BLKSIZE=125
C1BM3000 Utility
The C1BM3000 utility lets you execute CA Endevor® SCM actions from within a processor.
You must pass the SCLIN (SCL input) and MSGOUT1 (output messages) parameters to the C1BM3000
utility. Optionally, if you want:
A package ID associated with this execution, you must pass the PACKAGE parameter.
CA Endevor® SCM to write the Action Summary report to a separate file, you must pass the
MSGOUT2 parameter.
Important! When a package action executes a processor that invokes C1BM3000, the
actions run by the C1BM3000 step are considered non-package actions. If the actions
update an inventory area that has approver relations, the C1BM3000 utility issues a
C1U0900E error (package processing required). Also, backout information is not created for
actions run in a C1BM3000 step.
04-May-2018 330/1109
CA Endevor® SCM - 17.0
Sample JCL for the C1BM3000 utility is shown next. This JCL specifies a SCL input file, and the
messages and Action Summary report are written to SYSOUT. A package ID is not specified, as
indicated by the two commas between MSGOUT1 and MSGOUT2. The two commas are required.
//C1BM3000 EXEC PGM=C1BM3000,PARM='SCLIN,MSGOUT1,,MSGOUT2'
//STEPLIB DD DSN=iprfx.iqual.CSIQAUTH,
// DISP=SHR
//MSGOUT1 DD SYSOUT=*
//MSGOUT2 DD SYSOUT=*
//SYSABEND DD SYSOUT=*
//SCLIN DD DSN=uprfx.uqual.SCL,DISP=SHR
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160,DSORG=PS)
//
Note: You need not specify the CONLIB DD statement, because the library has been
specified by the batch job or by the logon procedure in foreground.
BSTIPT01 for SCLIN, the name is reserved by CA Endevor® SCM for input SCL.
C1MSGS1 for MSGOUT1, the name is reserved by CA Endevor® SCM for batch execution report
messages.
C1MSGS2 for MSGOUT2, the name is reserved by CA Endevor® SCM for the Action Summary
report.
C1WORK01-06 DD Statements
When you use the C1BM3000 utility to TRANSFER an element, the datasets are dynamically allocated
to process data. The dynamically allocated datasets may not be sufficient, if a large element is
transferred, and the System abort B37 error may occur. In this case, you can use the C1WORK01-
C1WORK06 DD statements to override the standard dynamic allocation of datasets, and run the
TRANSFER action again. These DD statements override the following records during the TRANSFER
action:
04-May-2018 331/1109
CA Endevor® SCM - 17.0
You can code any or all of the previous DD statements. If you code one C1WORK DD statement, then
it overrides the equivalent dynamic allocation of datasets. For example, if a very large element is
transferred the regular dynamic allocation of datasets may not be sufficient for storing element base,
element delta, and merged element records. In this case, you can code the C1WORK04, C1WORK05
and C1WORK06 statements to override the dynamic allocation of datasets.
C1PRMGEN Utility
The C1PRMGEN utility creates 80-column (card-image) statements from a parameter passed to it.
These statements are passed as input control statements to subsequent job steps.
To create card-image data, you can include CA Endevor® SCM symbols in the parameter passed to
C1PRMGEN. If you do this, the utility expands the symbols as it creates the output statements,
allowing you to vary the input control statements passed to subsequent job steps based on the
values of CA Endevor® SCM symbolic parameters. This is illustrated next, where C1PRMGEN creates
two control statements for use by the IBM IEBCOPY utility.
To use C1PRMGEN, pass the data to be expanded in the PARM= parameter of the EXEC statement. To
create more than one card-image statement, separate the statements using a vertical bar ( |) in the
PARM= value, as illustrated in the following sample JCL:
//STEPNAME EXEC PGM=C1PRMGEN,
// PARM=' C I=I,O=O| S M=((&&C1ELEMENT.,,R))'
//PARMOUT DD DSN=&&CPYPARM,DISP=(,PASS,DELETE)
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=80)
04-May-2018 332/1109
CA Endevor® SCM - 17.0
PARM=
The statement to be expanded, enclosed in single quotes or parentheses. This statement can be 1-
100 characters in length. Once expanded, it is output in card-image format starting in column 1.
To output more than one card-image statement, use the separator character (|) in the PARM
statement, as shown above.
If the statement contains more than 72 characters (up to 100 characters are allowed), you can
add a second line to the parameter by coding the statement as follows:
In position 72, type any non-blank character (except a single quote), and continue entering
your data on the next line.
Type a (single) quote only at the end of the entire statement. Note the example below:
Col Col1
72PARM='abcd...............................................
...zx// z.................................................a'
To include a quotation mark within the card-image data, specify two contiguous quotes: ' '.
You can include an unbalanced parentheses, with the restriction that you must use single
quotes as the surrounding delimiters in this case. You cannot include unbalanced parentheses
when the enclosing characters are parentheses, however.
PARMOUT
The data set to which the expanded statement is written.
In the previous example, the output written to PARMOUT, assuming that the current element is
NDVR, is as follows:
Col
1
C I=I,O=O
S M=((NDVR,R))
CONAPI Utility
The CONAPI utility lets you execute a program that issues API calls through a processor.
A program that issues API calls CANNOT be executed from a processor directly. You must use this
utility passing it the name of your program through the PARM= parameter on the EXEC statement. If
your program requires parameter data, you may append it to the parameter string using a comma to
separate the program name from your parameter data.
Note: For more information about the API interface, see API and User Exits Reference (
https://docops.ca.com/display/CE17/API+and+User+Exits+Reference).
04-May-2018 333/1109
CA Endevor® SCM - 17.0
//STEPNAME EXEC PGM=CONAPI,PARM='APIPROG1,1,22,333'
CONAPI invokes program APIPROG1. On entry to APIPROG1, register 1 contains an address which
points to an address for the parameter data. The first two bytes of parameter data contains the
length after which follows the data.
CONDELE Utility
The CONDELE utility removes a member (load module, listing, etc.) from an output library. The output
library can be any of the following:
USS directory
PARM=
Indicates an alternate member name (mbr-name) for the element. You have the option of
overriding the default member name. To specify all output components (including object
modules, load modules, and listings) instead of an individual member name, specify
'PARM=*COMPONENTS'. CONDELE accesses the component list at the current location and
deletes all output components from that list.
Important! CONDELE does not verify the component list was generated at the current
location. You need to verify this independently before using the PARM=*COMPONENTS
parameter.
C1LIB
Specifies the library or USS directory containing the member targeted for deletion. The member
name is the name of the element being processed (generally moved, deleted, or archived).
04-May-2018 334/1109
CA Endevor® SCM - 17.0
CONLIST Utility
The CONLIST utility is a multi-purpose utility used to manage output listings. Specify one of the
following options on the PARM= statement on the EXEC card. You can also specify the MBR option
with any of these options, except for the PRINT option.
STORE
Consolidates and compresses one or more temporary list data sets into a member in the output
library defined by the DD statement C1LLIBO. CONLIST converts the data sets to the record
format of the output library, and uses the member name as the element name. The output library
can be a PDS with record size and record format appropriate for listings (RECFM=VBA is
recommended), or a ELIB data set which is stored as if RECFM=VBA. You can optionally generate a
banner page and store it at the front of the member.
Note: RECFM=VBA forces the listing to be stored in compressed format. To store the
listing in uncompressed (human readable) format, allocate the library with RECFM=FBA
instead.
If more than one file is input, CONLIST concatenates the files before storing them.
The listing files must be sequential; they cannot be PDS members. If you use a PDS, you receive an
error message stating the member cannot be found in the directory.
PRINT
Default. Prints a temporary list data set, optionally generating a banner page before the listing. If
more than one file is input, CONLIST concatenates the files before printing them.
PRTMBR
Decompresses then prints a member from a listing library.
COPY
Copies a member from an input listing library to an output listing library (generally from Stage 1
to Stage 2), after optionally appending one or more temporary list data sets at the end of the
member. You can optionally store a banner at the front of the member in the output library.
DELETE
Deletes a member from the output library.
MBR (mbr-name)
Overrides the default member name (that is, the element name) used by CONLIST. This option
can be used with the STORE, PRTMBR, COPY, and DELETE options.
Banner Pages
You can request a banner when using the STORE, PRINT, and COPY options. Banner pages are defined
with a C1BANNER DD statement. This statement must specify LRECL=121.
The banner is useful for scanning listings and browsing stored members. The banner includes the
following items:
04-May-2018 335/1109
CA Endevor® SCM - 17.0
A summary of the processor being run (user ID, date, return code, stage, and so on).
An itemization of each processor step, up to but not including the CONLIST step, with the return
code from each.
Error conditions are reflected in the banner; for example, an error may have occurred within a
processor step, or steps were not executed because of condition-code testing.
STORE Option
The STORE option consolidates and compresses one or more temporary list data sets into a member
in the output library defined by the DD statement C1LLIBO.
//STEPNAME EXEC PGM=CONLIST,PARM='STORE'
//C1BANNER DD DISP=(,PASS,DELETE),
// UNIT=SYSDA,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171,DSORG=PS)
//C1LLIBO DD DSN=&C1STAGE.LISTINGS,DISP=SHR
//LIST01 DD DSN=&&COBLST,DISP=(OLD,DELETE)
//LIST02 DD DSN=&&LNKLST,DISP=(OLD,DELETE)
C1BANNER
Requests a banner (as illustrated above) be included at the front of the stored member. Omit this
statement if you do not want the banner included.
C1LLIBO
Identifies the output listing library to which the new member is written. The output member
name is the name of the element being processed. If a member by this name currently exists, it is
replaced.
LISTnn
Identifies a listing data set to be stored in C1LLIBO. If you specify more than one LISTnn library,
assign the ddnames sequentially (LIST01, LIST02, and so forth). LISTnn data sets are concatenated
before they are stored, in order by the nn suffix.
Note: You must specify at least one LISTnn DD statement.
Note: You can override the default member (element) name for the STORE option, using
the MBR (mbr-name) option.
04-May-2018 336/1109
CA Endevor® SCM - 17.0
PRINT Option
The PRINT option prints a temporary list data set, optionally generating a banner page before the
listing.
//STEPNAME EXEC PGM=CONLIST,PARM='PRINT'
//C1BANNER DD DSN=&&BANNER,DISP=(,PASS,DELETE),
// UNIT=SYSDA,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171,DSORG=PS)
//C1PRINT DD SYSOUT=*,
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0,DSORG=PS)
//LIST01 DD DSN=&&COBLST,DISP=(OLD,DELETE)
//LIST02 DD DSN=&&LNKLST,DISP=(OLD,DELETE)
C1BANNER
Requests a banner page (as illustrated above). Omit this statement if you do not want the banner
to print.
C1PRINT
The output print file.
LISTnn
Identifies a listing data set to be printed. If you specify more than one LIST nn data set, assign the
ddnames sequentially (LIST01, LIST02, and so forth). LISTnn data sets are concatenated before
they are printed, in order by the nn suffix.
Note: You must specify at least one LISTnn DD statement.
C1LLIBI
Identifies the input listing library from which a member is being printed. The name of the
member to be printed is the name of the element being processed.
C1PRINT
The output print file.
Note: You can override the default member (element) name for the PRTMBR option, using
the MBR (mbr-name) option. For example, to specify member mbrname in data set prtmbr.
mbr, you would code:
//STEPNAME EXEC PGM=CONLIST,PARM='PRTMBR.MBR(mbr-name)'
04-May-2018 337/1109
CA Endevor® SCM - 17.0
C1BANNER
Requests a banner page. Omit this statement if you do not want the banner included in the
output member.
C1LLIBI
Identifies the input listing library from which a member is being copied. The member being
copied has the name of the element being processed.
C1LLIBO
Identifies the output listing library to which the copied member is being written (after appending
any LISTnn files at the end of the member). The member name is the element name.
LISTnn
Identifies a listing data set to be concatenated at the end of the C1LLIBI member before it is
written to C1LLIBO. If you specify more than one LISTnn data set, assign the ddnames sequentially
(LIST01, LIST02, and so forth). LISTnn data sets are concatenated (in order by the nn suffix) before
they are appended to the member.
Note: Specifying a LISTnn DD statement is optional for the COPY option.
Note: You can override the default member (element) name for the COPY option, using the
MBR (mbr-name) option.
DELETE Option
The DELETE option deletes a member from the output library.
//STEPNAME EXEC PGM=CONLIST,PARM='DELETE'
//C1LLIBI DD DSN=STAGE1.LISTINGS,DISP=SHR
C1LLIBI
Identifies the input listing library from which a member is to be deleted. The name of the member
to be deleted is the name of the element being processed.
04-May-2018 338/1109
CA Endevor® SCM - 17.0
Note: You can override the default member (element) name for the DELETE option, using
the MBR (mbr-name) option. For example, to specify member mbrname in data set delete.
mbr, you would code:
//STEPNAME EXEC PGM=CONLIST,PARM='DELETE.MBR(mbrname)'
1. Writing the listings to a data set other than SYSOUT during the processor step
2. Running the CA Endevor® SCM CONLIST utility at the end of the job to combine all the listings
into a single member of a listing library.
To do this:
1. Initialize each listing data set before you write to it, to ensure that there is a listing to open in
the final (CONLIST) step. You need one such data set for each utility that outputs listings. The
utility that initializes data sets is BC1PDSIN.
2. In the JCL for the processor utilities, write to the appropriate listing data set--not to SYSOUT.
3. Use the CA Endevor® SCM CONLIST utility to condense and combine the listings from all the
job steps, and store them in a designated listing library or print them.
Note: In the following examples, Userinfo represents information you must supply.
//INITLST EXEC PGM=BC1PDSIN,COND=EVEN
//C1INIT01 DD DSN=&&COBLST,DISP=(,PASS,DELETE),UNIT=SYSDA,
// SPACE=(TRK,(1,2),RLSE)
//C1INIT02 DD DSN=&&LNKLST,DISP=(,PASS,DELETE),UNIT=SYSDA,
// SPACE=(TRK,(1,2),RLSE)
//WRITE EXEC PGM=CONWRITE,PARM='EXPINCL(N)'
//ELMOUT DD DSN=&&SYSIN,DISP=(,PASS,DELETE),userinfo
//*
//*
//COMPILE EXEC PGM=IGYCRCTL,COND=(0,NE),PARM=mmm,MAXRC=04
//SYSLIB DD DSN=userinfo
//SYSIN DD DSN=userinfo
//SYSLIN DD DSN=&&SYSLIN,DISP=(,PASS,DELETE),userinfo
//SYSUT1 DD UNIT=SYSDA,userinfo
//*
//SYSUT6 DD UNIT=SYSDA,userinfo
//SYSPRINT DD DSN=&&COBLST,DISP=(OLD,PASS,DELETE),
// UNIT=SYSDA,SPACE=(TRK,(5,10),RLSE),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0,DSORG=PS)
//*
//LINK EXEC PGM=IEWL,PARM='userinfo,COND=userinfo,MAXRC=0
//SYSLIN DD DSN=&&SYSLIN,DISP=(OLD,PASS)
//SYSLMOD DD DSN=userinfo
04-May-2018 339/1109
CA Endevor® SCM - 17.0
//SYSLMOD DD DSN=userinfo
//SYSUT1 DD UNIT=SYSDA,userinfo
//SYSPRINT DD DSN=&&LNKLST,DISP=(OLD,PASS,DELETE),
// UNIT=SYSDA,SPACE=(TRK,(5,3),RLSE),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0)
//*
//CONLIST EXEC PGM=CONLIST,PARM=STORE,COND=EVEN,MAXRC=0
//C1LLIBO DD DSN=STAGE1.LISTINGS,DISP=SHR
//C1BANNER DD DSN=&&BANNER,userinfo
//LIST01 DD DSN=&&COBLST,DISP=(OLD,DELETE)
//LIST02 DD DSN=&&LNKLST,DISP=(OLD,DELETE)
//
BC1PDSIN initializes a listing library for use in the COMPILE and LINK steps.
CA Endevor® SCM CONWRITE utility creates a source file by merging all levels of the element.
COBOL compile writes listings to the file initialized in the INITCOB step.
CA Endevor® SCM CONLIST utility creates a CA Endevor® SCM banner page and combines the
compile and link-edit listings and stores them as a single member in the Stage 1 listings library.
One Alternative
As an alternative, you can write the listings to SYSOUT. If you are running the processor in batch,
SYSOUT=* data sets are attached to the message class (MSGCLASS) assigned in the jobcard for the
corresponding batch job.
Note: If you are running in foreground, SYSOUT=* data sets are attached to the default
SYSOUT class assigned for your user ID. TSO allocates the SYSOUT file when it is first
opened, and does not free it until you log off from TSO or issue an explicit TSO FREE
command for the file.
This approach is illustrated by the compile and link-edit processor shown next:
//*
//WRITE EXEC PGM=CONWRITE,PARM='EXPINCL(N)'
//ELMOUT DD DSN=&&SYSIN,DISP=(,PASS,DELETE),userinfo
//*
//COMPILE EXEC PGM=IGYCRCTL,COND=(0,NE),PARM=mmm
//SYSLIB DD DSN=userinfo
//SYSIN DD DSN=userinfo
//SYSLIN DD DSN=&&SYSLIN,DISP=(,PASS,DELETE),userinfo
//SYSUT1 DD UNIT=SYSDA,userinfo
//*
//SYSUT6 DD UNIT=SYSDA,userinfo
//SYSPRINT DD SYSOUT=*
//*
//*
//LINK EXEC PGM=IEWL,PARM='userinfo,COND=userinfo,
//SYSLIN DD DSN=&&SYSLIN,DISP=(OLD,PASS)
//SYSLMOD DD DSN=userinfo
//SYSUT1 DD UNIT=SYSDA,userinfo
//SYSPRINT DD SYSOUT=*
//*
CA Endevor® SCM CONWRITE utility creates a source file by merging all levels of the element.
04-May-2018 340/1109
CA Endevor® SCM - 17.0
CA Endevor® SCM CONWRITE utility creates a source file by merging all levels of the element.
Another Alternative
This approach is similar to the recommended approach but uses the PRINT option of the CONLIST
utility, so the listings are printed instead of stored. The JCL for this approach is the same as that for
the recommended approach with the exception of the CONLIST step, which is shown below.
//*
//*
//CONLIST EXEC PGM=CONLIST,PARM=PRINT,COND=EVEN,MAXRC=0
//C1PRINT DD SYSOUT=*,
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0,DSORG=PS)
//C1BANNER DD DSN=&&BANNER,userinfo
//LIST01 DD DSN=&&COBLST,DISP=(OLD,DELETE)
//LIST02 DD DSN=&&LNKLST,DISP=(OLD,DELETE)
*
CONPARMX Utility
The CONPARMX utility lets administrators reduce processor complexity and the number of processor
groups. CONPARMX dynamically builds execution parameters for processor programs such as
compilers or the linkage editor. The build process uses the symbols defined in the processor and one
or more of the following groups of options, which may or may not be concatenated:
Default options
Element options
Using this utility avoids the need to create and update large numbers of processors or processor
groups with different input parameters.
Create the options members referenced by CONPARMX's PARM= parameters. Follow the syntax
rules when you create the options members.
Note: We recommend that you store the options members in CA Endevor® SCM and
monitor the members as part of an element's input component list.
04-May-2018 341/1109
CA Endevor® SCM - 17.0
The processor step JCL for the CONPARMX utility is shown next.
//CONP EXEC PGM=CONPARMX,MAXRC=n,
// PARM=(parm1,'(parm2)',parm3,parm4,parm5,
// '(parm6)','parm7','parm8')
//STEPLIB DD DSN=xxxxxx.loadlib.if.required,DISP=SHR
//PARMSDEF DD DISP=SHR,DSN=&PFX..PARMS,
// MONITOR=COMPONENTS,ALLOC=PMAP
//PARMS DD DSN=&&PPARMS,DISP=(,PASS),
// SPACE=(CYL,(1,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160)
//PARMSMSG DD SYSOUT=*
//* Additional DD statements as required by the parm1 program
The JCL statements and variables used by the CONPARMX utility are as follows:
MAXRC=n
Specifies the maximum return code value for the parm1 value. If the parm1 program is not
called by CONPARMX, the MAXRC should be set to 0.
PARM=
Specifies the parameters the utility used. The total length of the output options string using all
options values for CONPARMX parm2 through parm6 can be no more than 512 characters (the
CONPARMX limit). This limit is the limit supported by the parm1 program. If CONPARMX is not going
to invoke the parm1 program (parm8 = Y), the 512 characters limit is suppressed.
PARM=
Specifies the parameters the utility used. The total length of the output options string using all
options values for CONPARMX parm2 through parm6 can be no more than 512 characters (the
CONPARMX limit). This limit is the limit supported by the parm1 program.
parm1
Specifies a program name for which the options parameter string is to be built. This program name is
used to find the options values within the options members. It can be any value up to eight
characters. If CONPARMX is going to invoke the program (parm8 = N), this value must also be the
name of the program to be run.
When IGYCRCTL is passed as the program name, the parameters have the prefix CBL. This is to allow
those parameters to be passed through SYSIN DD. If this is not wanted, use another program name.
04-May-2018 342/1109
CA Endevor® SCM - 17.0
parm2
(Optional) Specifies the processor symbolic that identifies the options to be included first in the
output options string. This value must be within parentheses in the CONPARMX parameter list.
Parm2 is usually specified with a processor symbolic and can contain 0 to n options. Its value is
placed first and is always included in the output options string. The parentheses are not included
in the output.
parm3
Specifies the default options member name. The options values found in this member to match
the parm1 value (the program name) are added in the output parameter string after the parm2
options values. This member is read from the PARMSDEF DD statement.
Parm7 determines whether the options members are concatenated. For more information, see
parm7.
parm4
Specifies the processor group options member name. A processor group options member can be
created for each processor group. In the member, only the options that are to be overridden for a
particular processor group should be included, unless parm7 is set to N. This member is read from
the PARMSDEF DD statement.
Parm7 determines whether the options members are concatenated. For more information, see
parm7.
parm5
Specifies the element options member name. An element options member can be created for any
element in the CA Endevor SCM inventory. In this member, only the options that are to be
overridden specifically for this element should be included, unless parm7 is set to N. This member
is read from the PARMSDEF DD statement.
Parm7 determines whether the options members are concatenated. For more information, see
parm7.
parm6
(Optional) Specifies the processor symbolic that identifies the options to be included last in the
output parameter string. This value must be specified within parentheses in the CONPARMX
parameter list. Parm6 can contain 0 to n options and its value is placed last and always is included
in the output options string. The parentheses are not included in the output.
parm7
(Optional) Specifies whether to concatenate the options values in the output parameter string.
Valid values follow:
Y - (Default) Specifies that the contents of parm2 through parm6 are to be concatenated.
N - Specifies that the content of parm5, parm4, or parm3 are to be included between parm2 and
parm6. The first options member found to have a record that matches the parm1 program name
is used. The options members are searched until the match is found beginning with parm5, then
parm4, and then parm3.
parm8
(Optional) Specifies whether to build a parameter string to a file. Valid values follow.
Y - Writes the parameter string to the PARMS DD statement and the parm1 program is not
invoked. This data set can be used as input to a program step that follows. This option suppresses
the 512 characters limit for the output options string.
N - (Default) Passes the parameter string to the parm1 program and invokes the program. The
parameter string is not written to the PARMS DD statement.
04-May-2018 343/1109
CA Endevor® SCM - 17.0
STEPLIB DD DSN=xxxxxx.loadlib.if.required,DISP=SHR
Specifies the library that should be searched for the parm1 program executed by CONPARMX.
Required only if parm8=N indicating that the parm1 program is to be invoked.
PARMSDEF DD DISP=SHR,DSN=&PFX..PARMS,
MONITOR=COMPONENTS,ALLOC=PMAP
Specifies a concatenation of one or more FB-80 PDS or PDSE data sets. The parm3, parm4, and parm5
values point to options members in this data set. Options members do not have to exist or can exist
in one or more of the concatenated data sets. The first found options member is used. During
processing, if an options member does not exist, it is skipped and processing continues.
MONITOR=COMPONENTS
(Optional) Instructs the CA Endevor® SCM Automated Configuration option to monitor the &PRX..
PARMS data set for input or output components and to build a component list with the
information captured.
ALLOC=PMAP
(Optional) The ALLOC=PMAP processor DD statement parameter can be specified to indicate that
this data set concatenation varies with the CA Endevor® SCM location from which the processor is
being executed.
PARMS DD DSN=&&PPARMS,DISP=(,PASS),
SPACE=(CYL,(1,1)),
DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160)
Specifies the data set name to which the parameter string built by the utility is written. The PARMS
DD statement is only required if the parm8 value in the CONPARMX parameter string is set to Y.
Note: For program ASMA90, this data set is read from the ASMAOPT DD statement. For
COBOL and PL/I compiler programs, place this data set first within the SYSIN DD statement.
PARMSMSG DD SYSOUT=*
Specifies that the output options string value is written to this data set for diagnostic purposes. The
PARMSMSG DD statement is not required. The data set DCB attributes are FB-80-32720.
If parm8=N, the output options string is written to the data set 72 bytes per line until the string is
exhausted. A maximum of 512 bytes of data (the maximum size of the output options string) or eight
lines (7 x 72 = 504 bytes plus 8 bytes on the eighth line) are written to the data set.
If parm8=Y, the output options string is written to the data set exactly as it appears in the PARMS DD
output. The 512 bytes limit is suppressed in this case.
04-May-2018 344/1109
CA Endevor® SCM - 17.0
The following parameters can be specified for CONPARMX. These parameters are passed to
CONPARMX on the EXEC statement using the PARM keyword as follows:
//STEP001 EXEC PGM=CONPARMX,PARM=(parm1,parm2,parm3,parm4,parm5,parm6,parm7,parm8)
CONPARMX produces an output options string from the options values in parm2 through parm6,
subject to the following parameters:
Parm1 specifies the processor program for which the parameters are built.
Parm7 is optional and specifies if the parameters are concatenated. The default forces
concatenation.
Parm8 is optional and specifies whether the parm1 processor program is invoked or if the
parameters are stored for a future processor step. The default invokes the program.
The PARMSDEF DD statement on the CONPARMX JCL reads the options members whose names
are coded in parm3, parm4, and parm5. PARMSDEF finds the matching record in each options
member by matching the record to the name of the program specified in parm1. The options
members contains records that start with a program name followed by a parameter string. For
example, the following record matches parm1 IGYCRCTL and specifies the parameters COBOL,
LANGLVL(2), and NOSOURCE:
IGYCRCTL ‘COBOL3,LANGLVL(2),NOSOURCE’
For parm3, parm4, and parm5, only the options in the matching records are used as input to
building the output parameter string. Whether the options for parm3, parm4, or parm5 are
included in the output parameter string depends on the parm7 concatenation specification.
Sample processor step JCL for the CONPARMX utility is shown next. This JCL invokes program
ASMA90 and passes a parameter string to the program.
Then $$$$DFLT is read and the program name ASMA90 is searched for within the member. If
there is a match for ASMA90, the options values are added to the output options string.
The options values for &PARMZ are added last in the output options string.
//CONP EXEC PGM=CONPARMX,MAXRC=4,
// PARM=(ASMA90,'(&PARMA)',$$$$DFLT,&C1PRGRP,&C1ELEMENT,
// '(&PARMZ)','Y','N')
//STEPLIB DD DSN=ASMA90.loadlib.if.required,DISP=SHR
//PARMSDEF DD DISP=SHR,DSN=&PFX..PARMS,
// MONITOR=COMPONENTS
04-May-2018 345/1109
CA Endevor® SCM - 17.0
// MONITOR=COMPONENTS
//PARMS DD DSN=&&PPARMS,DISP=(,PASS),
// SPACE=(CYL,(1,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160)
//PARMSMSG DD SYSOUT=*
//* Additional DD statements as required by the parm1 program
This example JCL builds a parameter string and writes it to PARM DD for the program IGYCRCTL.
In the JCL, see the comments to the right that identify parm1, parm2, parm6, parm7, and parm8:
//COBPROC PROC PARMTAIL=XYZ
//STEP001 EXEC PGM=CONPARMX,
// PARM=(IGYCRCTL, (invocation pgm name)
// (‘ABC’), (parm2 - constant parm data)
// $$$$DFLT, &C1PRGRP.P, &C1ELEMENT.P,
// '(&PARMTAIL)', (parm6 - last parm)
// 'Y','Y') (parm7/8 directions)
//PARMSDEF DD DSN=input.parameter.pds,DISP=SHR
//PARMS DD DSN=&&parmout,DISP=(NEW,PASS),…
Parm4, &C1PRGRP.P, is the member that contains the processor group override parameters.
Parm5, &C1ELEMENT.P, is the member that contains the element override parameters.
This example JCL results in a PARMS output DD that contains the following parameter string for
IGYCRCTL:
ABC
COBOL3,LANGLVL(2),NOSOURCE
Parameters defined by the Processor member
Parameters defined by the Element member
XYZ
Parameters defined by the Processor member - The actual parameters defined by parm4,
&C1PRGRP.P, would depend on the record found to match IGYCRCTL.
Parameters defined by the Element member - The actual parameters defined by parm5,
&C1ELEMENT.P, would depend on the record found to match IGYCRCTL.
04-May-2018 346/1109
CA Endevor® SCM - 17.0
If parm8 in this example was N, instead of Y, the parameter string would not have been written to the
PARMS output DD. Instead, IGYCRCTL would have been invoked directly with the following parameter
string:
//CONPARMX EXEC PGM=IGYCRCTL,
// PARM=‘ABC,COBOL3,LANGLVL(2),NOSOURCE,
// procgrp-parms, elm-parms, XYZ’
0
Processing successful.
16
WTO message issued with specific error condition.
All other return codes are issued by the parm1 program when called.
program
Specifies a program name and must begin in column 1.
options values
Specifies the options values that can be passed by the PARM parameter to the CONPARMX utility.
The following rules apply to options values:
The options values can be enclosed within single or double quotes, can span multiple lines,
and optionally end with a comma (,).
A plus sign (+) or dash (-) at the end of a line indicates continuation of the options values on
the next line. Only enter one of the continuation characters.
A blank in column 1 is treated as a comment line, unless the previous line contains a
continuation character.
Single or double quotes can be used to enclose the options member’s options values. If an
04-May-2018 347/1109
CA Endevor® SCM - 17.0
Single or double quotes can be used to enclose the options member’s options values. If an
options value requires single quotes, enclose the value in double quotes. For example:
********************************* Top of Data **************************
----+----1----+----2----+----3----+----4----+----5----+----6----+----7--
CCNDRVR = 'ARCH(5),EXPMAC,RENT,'+
"SEARCH(//'SYS1.SIEAHDR.H'),"+
'RENT,'
******************************** Bottom of Data ************************
The total length of the output options string using all options values coded for CONPARMX
parm2 through parm6 must be less than 512 characters (CONPARMX limit) or the limit that is
supported by the parm1 program, whichever is less.
This defaults options member would display this options string for ASMA90:
RENT,TERM,XREF(SHORT),USING(MAP,WARN(13)),LIST(133)
This example assumes that the parm7 value is set to Y. When parm7 is set to Y (default), for the
processor group options member, the utility only includes options that are overridden from the
default options member. For the element options member, the utility only includes options that are
overridden from the processor group, default options members, or both.
Note: When parm7 is set to N, the utility includes all necessary options values. The options
values that are first found to match the program name are used and placed in the output
options string.
IEWL = 'LIST,MAP,RENT,REUS,NOLET,XREF,SIZE=(256K,64K),'
04-May-2018 348/1109
CA Endevor® SCM - 17.0
IEWL = 'LIST,MAP,RENT,REUS,NOLET,XREF,SIZE=(256K,64K),'
******************************** Bottom of Data ************************
This example assumes this member is the processor group options member:
********************************* Top of Data **************************
----+----1----+----2----+----3----+----4----+----5----+----6----+----7--
ASMA90 = 'NORENT,'
******************************** Bottom of Data ************************
Using this default options member with this processor group options member would result in the
following output options string for ASMA90:
RENT,TERM,XREF(SHORT),USING(MAP,WARN(13)),LIST(133),NORENT
ASMA90 and most compiler programs use the last option specified if conflicting options are
used. Consequently, in this example, the NORENT option overrides the RENT option
specified earlier in the options list.
CONRELE Utility
The CONRELE utility allows you to include entities related to an element in a component list. The
entities can be data sets, CASE entities, JCL, parameter list members, documentation members, etc.
The entities do not have to be CA Endevor® SCM elements.
The CONRELE utility parses and processes input data. CONRELE accepts user syntax from the
NDVRIPT DD statement. After the parsing process is complete the data is formatted as special
component record types and processed with the rest of the component list. The related data portion
is appended to the end of the component list. You are not required to store the input in.
Note: You must use the CONRELE utility with an active component list (the component list
for the element being processed).
You must include the CONRELE utility as a processor step and you must provide the input. You can
include the optional NOECHO parameter to suppress CONRELE messages from appearing in C1MSGS1
output. The following sample processor JCL executes CONRELE and suppresses the CONRELE
messages:
//STEPxx EXEC PGM=CONRELE,PARM='NOECHO'
//NDVRIPT DD DSN=&user.data.set,DISP=SHR
04-May-2018 349/1109
CA Endevor® SCM - 17.0
SET ERROR RETURN CODE-Returns an error code when the CONRELE utility finds errors in the
input syntax (default 8).
element-name
The name of the element, maximum length of 10.
LOCATION
(Optional) Location of the element-name. If you do not include the location in your syntax the
location defaults to the target location of the current CA Endevor® SCM element.
INPUT
Input component
OUTPUT
Output component
VALIDATE
Verifies the elements' presence at the specified location in. This is optional.
If the element doesn't exist, the RELATEd element is rejected.
If you specify the VALIDATE option and the validation fails, the return code is set according to the
SET ERROR RETURN CODE syntax.
When the VALIDATE option is specified, the location names (environment, system, etc.)
cannot be wildcarded. If they are omitted, the location names associated with the target
element are used.
When the VALIDATE option is NOT specified, CONRELE stores the location information "as
specified". Omitted location information is taken from the target element's location.
04-May-2018 350/1109
CA Endevor® SCM - 17.0
Note: Package component validation only validates RELATED ELEMENTS, (not members,
objects or comments) which were related using the CONRELE VALIDATE option.
member-name
The name of the member in a data set, the maximum member-name length is 10. A blank
member is valid.
data set-name
The name of the data set that contains the member-name.
INPUT
Input component
OUTPUT
Output component
VALIDATE
CA Endevor® SCM determines whether the specified data set exists. This is optional.
If you specify the VALIDATE option, CA Endevor® SCM determines whether or not the data set
exists.
If the validation fails the default SET ERROR RETURN CODE is displayed. If you do not specify the
VALIDATE option no validation occurs.
INCLUDE FOOTPRINTS
(Optional) If the member is footprinted, the footprint is stored in the component list.
object-data
The name of object-data. The object-data name is a maximum length of 70 bytes. The object-data
is not verified. Related objects are stored in a first-in-first-out (FIFO) sequence.
Comment-data
The comments should be enclosed in quotations marks and are stored in a first-in-first-out (FIFO)
sequence. You can include an unlimited number of comments. The comments are not verified but
you can search on the text.
04-May-2018 351/1109
CA Endevor® SCM - 17.0
error-return-code
Specifies the error return code when the Validate option fails.
Default: 8.
RELATE ELEMENT BGSQL723
LOCATION
ENVIRONMENT = TEST
SYSTEM = FINANCE
SUBSYSTEM = AP
TYPE = BGLOAD3
STAGE = 1
INPUT.
RELATE ELEMENT BGSQL601
LOCATION
ENVIRONMENT = TEST
SYSTEM = FINANCE
SUBSYSTEM = AP
TYPE = BGLOAD2
STAGE = 1
OUTPUT.
RELATE ELEMENT BGSQL64
LOCATION
ENVIRONMENT = TEST
SYSTEM = FINANCE
SUBSYSTEM = AP
TYPE = DB2COB3
STAGE = 1
OUTPUT.
RELATE ELEMENT BGSQL65
LOCATION
ENVIRONMENT = TEST
SYSTEM = FINANCE
SUBSYSTEM = AP
TYPE = DB2COB
STAGE = 1
OUTPUT
VALIDATE.
RELATE MEMBER BC1PSQL1
dataset = 'JSMITH.SRCLIB'
INPUT.
RELATE MEMBER BGSQL60
dataset = 'DA1BG10.DBRMLIB'
INPUT
04-May-2018 352/1109
CA Endevor® SCM - 17.0
INPUT
VALIDATE
INCLUDE FOOTPRINTS.
RELATE MEMBER BC1PSQL3
dataset = 'JSMITH.SRCLIB'
OUTPUT.
RELATE MEMBER BGSQL70
dataset = 'DA1BG10.DBRMLIB'
INPUT
VALIDATE
INCLUDE FOOTPRINTS.
RELATE OBJECT 'D;\ENDEVOR\TEMP.DOC'.
RELATE OBJECT 'D;\ENDEVOR\TEMP.DOC2'.
RELATE OBJECT 'D;\ENDEVOR\TEMP.DOC3'.
RELATE OBJECT 'D;\ENDEVOR\TEMP.DOC4'.
RELATE OBJECT 'D;\ENDEVOR\TEMP.DOC5'.
RELATE OBJECT 'D;\ENDEVOR\TEMP.DOC6'.
RELATE OBJECT 'D;\ENDEVOR\TEMP.DOC7'.
RELATE OBJECT 'D;\ENDEVOR\TEMP.DOC8'.
RELATE OBJECT
'<--------------------------------------------------------------.'
.
RELATE COMMENT 'THIS IS A FREE FORM TEST'.
RELATE COMMENT 'THIS IS A FREE FORM TEST2'.
RELATE COMMENT 'THIS IS A FREE FORM TEST3'.
RELATE COMMENT 'THIS IS A FREE FORM TEST4'.
RELATE COMMENT 'THIS IS A FREE FORM TEST5'.
RELATE COMMENT 'THIS IS A FREE FORM TEST6'.
RELATE COMMENT 'THIS IS A FREE FORM TEST7'.
RELATE COMMENT 'THIS IS A FREE FORM TEST8'.
RELATE COMMENT 'THIS IS A FREE FORM TEST9'.
RELATE COMMENT 'THIS IS A FREE FORM TEST10'.
RELATE COMMENT 'THIS IS A FREE FORM TEST11'.
CONSCAN Utility
The CONSCAN utility lets you identify additional Automated Configuration Management (ACM)
relationships between CA Endevor® SCM Elements and objects contained within the element, such as
data set or program names contained within a JCL jobstream or dynamic program call statements
within a COBOL program.
User-defined selection criteria and scan rules are applied against the element source and CONRELE
control statements are produced by the CONSCAN utility. These statements can be passed to the
CONRELE utility, which updates the ACM component data for an element.
Note: For more information about the CONRELE utility, see The CONRELE Utility (see page
).
Once these relationships are established, the element display component options or the ACMQ
facility can be used to view this information in addition to standard ACM input and output
component data.
04-May-2018 353/1109
CA Endevor® SCM - 17.0
This parameter data set contains selection criteria and scan rules. It is recommended you create one
PARMSCAN member in this library for each element TYPE that utilizes the CONSCAN utility.
All lines with an asterisk in column 1 are considered comments and are ignored.
Positions 2-72 are used for control statement syntax in free format.
Literals that contain special characters must be enclosed within single quotes.
CONSCAN validates all the PARMSCAN input for proper syntax. If a syntax error is detected, a return
code of 8 is returned and error messages are written to the report file.
CONSCAN does not scan any source until all the statements in the PARMSCAN input pass the syntax
checking rules.
04-May-2018 354/1109
CA Endevor® SCM - 17.0
COMMENT
Indicates the beginning of an exclusion group.
FIND1
Indicates the beginning of the FIND statement.
STRING=
Indicates to scan this record for a string. The search is case sensitive; the search only finds a string
value with a matching case.
'string',
Specified string. One to eight characters can be specified.
POS
Identifies the position to search for the delimiter string.
ANY
The specified string may occur anywhere in the source.
nn
The specified string must occur after this position in the source.
END1
END1 Indicates the end of an exclusion group.
CARD
Ignore from the FIND POS to the end of the source record.
STRING
Delimiter for the data to be ignored.
'string',
Indicates to include any characters following this string. 1-8 characters can be specified.
POS
Identifies the position to search for the delimiter string.
ANY
The specified string may occur anywhere in the source.
nn
The specified string must occur after this position in the source.
Example 1: In this assembler example, CONSCAN searches for source records containing an asterisk
'*' in position 1. If found, the remainder of this record is ignored.
COMMENT
04-May-2018 355/1109
CA Endevor® SCM - 17.0
COMMENT
FIND1 STRING='*',POS=1
END1 CARD
Example 2: In this JCL example, CONSCAN searches for source records containing '//*' starting in
position 1. If found, the remainder of the record is ignored.
COMMENT
FIND1 STRING='//*',POS=1
END1 CARD
Example 3: In this example, CONSCAN searches for source records containing a '/*' followed by a '*/'
in any position of the record. If found, these characters and any characters in between are ignored.
COMMENT
FIND1 STRING='/*',POS=ANY
END1 STRING='*/',POS=ANY
2. FIND-Defines the element source selection criteria. One FIND statement (FIND1) is required
and an optional second FIND statement (FIND2) can be specified per group. If FIND1 and
FIND2 are present, both conditions must be true (treated as an AND condition) for the source
data to be selected.
3. START- Follows the last FIND statement and identifies the location of the data to extract and is
placed on the generated CONRELE control statement. Only one START statement is allowed.
4. END-Must follow the START statement to terminate the extracted string and to terminate the
selection group. One END statement is required (END1) and an optional second END
statement (END2) can be specified per group. If END1 and END2 are present, either condition
can be true (treated as an OR condition) for the termination to take place.
If a match is found against the FIND criteria, the data specified by the START criteria is extracted.
There can be more than one match per input record. CONRELE control statements are generated for
each match found. These control parameters are written to the data set specified on the ACMRELE
DD statement and to the report file, SCANPRT.
SCANTYPE
Indicates the beginning of a selection group.
04-May-2018 356/1109
CA Endevor® SCM - 17.0
type
Identifies the type of relationship and is used to generate the CONRELE RELATE control
statements. Valid values are:
MEMBER
ELEMENT
OBJECT
COMMENT
CONSCAN attempts to determine the type of relationship existing in the data. You may have specified
a type of OBJECT, but the control statements are generated with a type of COMMENT. If you specify
the type MEMBER and the FIND string is 'DSN=' several checks are performed. If no member exists in
the extracted string, CONSCAN determines the length of the data set name and the CONRELE control
statements are generated with a type of OBJECT.
FIND
Indicates the beginning of a FIND statement.
n
The valid values for n are 1 or 2. FIND2 cannot exist unless FIND1 exists.
keyword
Optional keywords used to identify additional information related to the string. Only one keyword
is allowed:
AFTER
Used in conjunction with the POS parameter. Directs CONSCAN to begin the search for the string
after POS=nn.
WORD
The string must be a word surrounded by spaces, parentheses () or greater than/less than
symbols >< or preceded or followed by one of the following symbols:.,;+-/*.
REJECT
Specified on a FIND2 statement. Allows the user to code a FIND1 and not FIND2 condition. If
FIND1 and FIND2 match and REJECT is present on the FIND2 statement, the source data is
ignored. For REJECT to work properly, two selection groups are required and the FIND1 statement
must be identical.
STRING=
Indicates to start scanning this record for a string. The search is case sensitive; the search only
finds a string value with a matching case.
'string',
Specified string. One to eight characters can be specified.
POS
Identifies the position to search for the delimiter string.
ANY
The specified string may occur anywhere in the source.
04-May-2018 357/1109
CA Endevor® SCM - 17.0
START
Defines where to start the collection of data when the FIND criteria is true. If two FIND
statements are specified and both match, the start criteria are relative to the FIND2 statement.
TYPE=
Identifies the direction of the start collection. Valid values are:
FORW
BACK
STRG
DFLT
PARM=
Works in conjunction with the TYPE keyword.
parm
PARM defines the position to start the collection of data characters as follows:
After the last character found by the FIND statements when TYPE is FORW.
Before the first character found by the FIND statements when TYPE is BACK.
END
Indicates the START collection string delimiter. When this condition is met, the string
collection is terminated.
The valid values are 1 and 2. END2 cannot be specified unless END1 is specified. Code all END
statements after the START statement. If END1 and END2 are present, they are treated as an
OR condition.
TYPE=
Identifies the type of delimiter.
type
Works in conjunction with the PARM keyword. Valid values are:
CHAR
LENG
SPAC
STRG
PARM=
04-May-2018 358/1109
CA Endevor® SCM - 17.0
PARM=
Works in conjunction with the TYPE keyword.
parm
Specifies:
If TYPE is STRG, specifies the number of additional strings to collect after the initial string before
termination of the collection. Each string must be separated by a space. For example, if a START
string is detected and PARM=3 is specified, the initial string plus three additional strings are
collected. CONRELE control statements are generated for each of the four strings.
In this JCL example, CONSCAN searches for source records containing data set or member names. The
data set name begins in the first position after the FIND string (DSN=) and is terminated by a space or
a comma.
POS=ANY INPUT.
04-May-2018 359/1109
CA Endevor® SCM - 17.0
END2 TYPE=CHAR,
PARM=','
Example 2
In this COBOL example, CONSCAN searches for source records containing dynamically called
programs. The program name is the next word following the search string of CALL and terminated by
a space or a comma.
PARM='.' INPUT.
Example 3
In this JCL example, CONSCAN searches for source records containing PROC names. This requires two
selection groups. The first selection group ensures program names are not selected. The second
selection group selects the processors. In both cases, the search is terminated by a space.
04-May-2018 360/1109
CA Endevor® SCM - 17.0
SCANTYPE ELEMENT
FIND1 STRING='EXEC',
POS=ANY
START TYPE=DFLT
END1 TYPE=SPAC
Example 4
In this assembler example, CONSCAN searches for source records containing links to other programs.
Two FIND statements are required to identify these programs. Both conditions must be true to be
selected. The search is terminated when a blank space or a comma is detected.
PARM=','
Example 5
In this COBOL example, CONSCAN searches for source records containing calls to program XYZ. This
program requires three parameters. The goal is to capture the data associated with each parameter
and generate a RELATE control statement for each. The extract is terminated after the third
parameter or when the closing ')' is detected.
04-May-2018 361/1109
CA Endevor® SCM - 17.0
FIND1 STRING='XYZ,(',
POS=ANY
START TYPE=DFLT
END1 TYPE=STRG,
PARM=1
END2 TYPE=CHAR,
PARM=')'
Example 6
In this COBOL example, CONSCAN searches for source records containing object names which are
followed by a special comment denoting the type of object. The object name begins in the 20
positions before the FIND string (object), is 16 characters in length and is terminated by a space.
FIND1 AFTER,
POS=7,
STRING=' OBJ'
FIND2 AFTER,
POS=7,
STRING='OBJECT'
START TYPE=BACK,
PARM=20
END1 TYPE=LENG,PARM=16
04-May-2018 362/1109
CA Endevor® SCM - 17.0
If you want your input records to be applied against all the selection groups, regardless of the
outcome of previous selection groups, code APPLY ALL as the first line of your PARMSCAN control
statements. This causes the input record to be applied against each selection group within the
PARMSCAN library. Therefore, CONRELE control statements may be generated for one input record
by more than one selection group.
Note: The SYSPRINT DD is required when running the CONSCAN JCL in a CA Endevor® SCM
processor or in a batch job.
04-May-2018 363/1109
CA Endevor® SCM - 17.0
CONWRITE Utility
You can use the CONWRITE utility to write component list data or the current level of any element to
an external location such as a data set or a database.
The standard form of CONWRITE writes the current element to a user specified data set.
Processes WRITE ELEMENT control statements to write user specified elements to an external
data set or USS directory.
Both forms of CONWRITE can expand INCLUDE statements embedded in the element.
You can code a CONWRITE step anywhere in any processor. For example, you can code a CONWRITE
step within a move processor. The default location of the component list is the target location of the
MOVE action, but you can override this default.
Note: You should be aware when retrieving an active component list that the entire
component list is not available until all steps are complete.
Input components
Output components
Symbolics
Related objects
Related comments
04-May-2018 364/1109
CA Endevor® SCM - 17.0
Note: Use the CONRELE utility to create related input components, related output
components, related objects, and related comments before using the CONWRITE utility.
Output Format
The output format of the extracted component list data does not contain binary data. Assembler
DSECTS and COBOL copy statements are provided in the output source file of the install process. In
addition, COBOL layouts for the data are provided in &uprfx.SOURCE(COBCOMP), and an example of
a COBOL program displaying records field by field is provided in &uprfx.SOURCE(COBCOMPX). See the
following elements for the layout of external component list records:
$COMPDS ASMMAC
Assembler layouts for component list data
COMPRECS EXAMPLE
COBOL copy statements for component list data
CONCOMP EXAMPLE
COBOL program which displays fields within component list data.
Note: The standard form of CONWRITE does not support the extraction of a component
list.
The following JCL is an example of the standard form of the CONWRITE utility:
//WRITE EXEC PGM=CONWRITE,PARM='EXPINCL(N)'
//ELMOUT DD DSN=&&SYSIN,DISP=(NEW,PASS,DELETE)
04-May-2018 365/1109
CA Endevor® SCM - 17.0
You create copies of more than one element or component list record using the CONWIN DD
statement. You can also use this statement to pass the individual element or component list records
to a user exit program.
Sample JCL for using the CONWIN DD statement to extract a component list with the extended form
of CONWRITE is shown next:
//WRITE EXEC PGM=CONWRITE
//COMPOUT DD DSN=&user.data.set,DISP=(NEW,PASS),UNIT=SYSDA,
// SPACE=(TRK,(3,5),RLSE),
// DCB=(RECFM=VB,LRECL=256,BLKSIZE=0,DSORG=PS)
//CONWIN DD *
WRITE ELEMENT &c1element
FROM ENV &c1envmnt SYSTEM &c1system SUBSYSTEM &c1subsys
TYPE &c1eltype STAGE &c1stgid
TO DDN COMPOUT
OPTION COMPONENT.
/*
user.loadlib
The load library where a user exit program resides.
program-name
The name of a user exit program invoked for each element record. If the CONWLIB DD statement
is specified the program is loaded from the library specified in the DD statement.
On entry to the user program, R1 points to this parameter list:
+0-Address of a 256 byte work area. The area is initialized to zeroes for the first invocation of
the exit.
04-May-2018 366/1109
CA Endevor® SCM - 17.0
+12-Address of a 100 byte message area. The message area is set to blanks before each user
program call.
+16-Address of the parameter specified on the 'program parm =' statement. The parameter is
a halfword length field followed by the parameter string. If a 'program parm =' statement was
not specified, the halfword length is set to zero.
parameter
A 1- to 70-character parameter passed to the user program.
Note: When you include a CONWIN DD statement in a CONWRITE step, CONWRITE ignores
PARM information in the EXEC statement for that step.
There is no limit to the number of WRITE ELEMENT statements that can be included in the CONWIN
DD statement.
If a syntax error is detected in the CONWIN DD input stream, CONWRITE issues an error message. All
remaining WRITE ELEMENT statements are syntax-checked, but they are not executed.
For example, if link-edit control cards are separate from programs, and you want to use these control
cards in a processor, you can fetch the control cards using the extended form of CONWRITE. The
following example shows how the control cards can be processed:
Note: This example uses OPTION SEARCH to fetch the current version of LINKCARD's
source.
//*********************************************************************
//** EXAMPLE OF CONWRITE EXECUTION JCL WITH CONWIN DD STMT INPUT **
//*********************************************************************
//CONWRITE EXEC PGM=CONWRITE
//*
//* ELMSRC IS A TEMPORARY DATA SET USED TO CONTAIN ELM SOURCE CODE
//*
//ELMSRC DD DSN=&&ELMSRC,DISP=(,PASS),
// UNIT=VIO,SPACE=(TRK,5,1),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=0,DSORG=PS)
//*
//* LNKSRC IS A TEMPORARY DATA SET USED TO CONTAIN ELM LINK-EDIT STMTS
//*
//LNKSRC DD DSN=&&LNKSRC,DISP=(,PASS),
// UNIT=VIO,SPACE=(TRK,1,1),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=0,DSORG=PS)
//CONWIN DD *
WRITE ELEMENT &C1ELEMENT.
FROM ENV &C1ENVMNT. SYSTEM &C1SYSTEM. SUBSYSTEM &C1SUBSYS.
TYPE &C1ELTYPE. STAGE &C1STGID.
TO DDN ELMSRC
OPTION EXPAND INCLUDES.
04-May-2018 367/1109
CA Endevor® SCM - 17.0
OPTION EXPAND INCLUDES.
WRITE ELEMENT &C1ELEMENT.
FROM ENV &C1ENVMNT. SYSTEM &C1SYSTEM. SUBSYSTEM &C1SUBSYS.
TYPE LINKCARD STAGE &C1STGID.
TO DDN LNKSRC
OPTION SEARCH.
//*
//*********************************************************************
//** PERFORM COMPILE **
//*********************************************************************
//COMPILE EXEC...
//SYSIN DD DSN=&&ELMSRC,DISP=(OLD,DELETE)
//*
//*********************************************************************
//** PERFORM LINK-EDIT **
//*********************************************************************
//LINKEDIT EXEC PGM=IEWL
//SYSLIN DD DSN=&&LNKSRC,DISP=(OLD,DELETE)
PARM=EXPINCL( ) Clause
Specify PARM=EXPINCL(Y) to expand INCLUDE members; specify PARM=EXPINCL(N) if you do not
want to expand the INCLUDE members. The default is PARM=EXPINCL(N).
//STEPNAME EXEC PGM=CONWRITE,PARM=EXPINCL(Y)
//DDNAME DD DSN=&&WRITEOUT,DISP=PASS,UNIT=SYSDA,
// SPACE=(TRK,(3,5),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=0,DSORG=PS)
Note: CONWIN DD statements and PARM clauses are mutually exclusive. If you code a
CONWIN DD statement, CONWRITE ignores any PARM clauses in the EXEC statement for
the step.
By default, CONWRITE searches the environment map for INCLUDE members in the default INCLUDE
libraries for specified types. This means that when expanding INCLUDEs for a Stage 1 element,
CONWRITE looks first in the Stage 1 INCLUDE library for the member, then in INCLUDE libraries in
successive stages on the map. When processing a Stage 2 element, CONWRITE looks for the INCLUDE
member first in the Stage 2 library, then in successive stages on the map.
Alternatively, you can use C1INCL DD statements to specify up to 99 INCLUDE libraries within the
CONWRITE step of a processor. When you do this, CA Endevor® SCM accesses these statements in
ascending order based on their DD names. The example below shows how to write C1INCL DD
statements.
//STEPNAME EXEC PGM=CONWRITE,PARM=EXPINCL(Y)
04-May-2018 368/1109
CA Endevor® SCM - 17.0
//STEPNAME EXEC PGM=CONWRITE,PARM=EXPINCL(Y)
//C1INCL01 DD DSN=include.library1,DISP=SHR
//C1INCL02 DD DSN=include.library2,DISP=SHR
//DDNAME DD DSN=&&WRITEOUT,DISP=(NEW,PASS),
// UNIT=SYSDA,SPACE=(TRK,(3,5),RLSE),
Note: These search rules are mutually exclusive. If you use C1INCL DD statements,
CONWRITE does not search in the default INCLUDE libraries for the specified types. Also, all
C1INCL DD statements must precede the CONWRITE output data set statement.
CONWRITE passes the user exit a five-word parameter list for each data record. Register 1 points to
the parameter list. The parameter list and all parameters are in 24-bit addressable storage. The
parameter list points to these fields:
A 256-byte program work area. The work area is double word aligned and is initialized to binary
zeroes for the first exit call. The work area is not reinitialized between exit calls or between WRITE
ELEMENT statements within a step.
A 100-byte area in which the user program can place a message. The area is initialized to blanks
prior to each invocation of the exit. The message is printed if the exit sets a return code of four or
eight and the message area contains non-blank data.
The program parameter specified in the OPTION PROGRAM PARM EQ statement. The parameter
is a halfword length field followed by the parameter specified. If the PROGRAM PARM EQ
statement was not specified, CONWRITE sets the halfword length field to zero.
After CONWRITE processes all of the element data records, it calls the exit a final time with the
record length field and the record address parameter set to zero. CONWRITE expects one of the
following return codes from the user program. The return code is passed back in Register 15.
0
Normal completion. CONWRITE continues processing the element.
4
Terminate the current WRITE ELEMENT operation. CONWRITE continues with the next WRITE
ELEMENT statement.
04-May-2018 369/1109
CA Endevor® SCM - 17.0
8
Terminate CONWRITE processing. CONWRITE immediately terminates with a return code of 12. If
an invalid return code is received, CONWRITE immediately terminates the current step with a
return code of 12.
ENUSSUTL Utility
The ENUSSUTL processor utility collects package backout information for USS processor output files.
This backout information consists of backout records and backout files.
Package outputs for USS files can be transmitted to other sites using the Package Ship utility.
However, the output cannot be shipped unless package backout information for USS files is available.
To collect this information, the processor that is associated to the element type must include the
ENUSSUTL utility to collect and associate the backout files to an element. When this utility is
executed under Package processing, the utility enables these files for Package Backout and Package
Ship. For more information about ENUSSUTL, see How to Enable USS Supported Files for Package Ship
(see page 814).
The purpose of LEXTRCTR is to parse and capture all the pieces of a CSP application when the user is
managing at the application versus the component level. BC1PCCSP then attaches the compiler for
each piece of the application identified by LEXTRCTR.
Note: For an example of the use of LEXTRCTR and BC1PCCSP, see Sample Processors (see
page 385).
04-May-2018 370/1109
CA Endevor® SCM - 17.0
For elements of type PROCESS, CA Endevor® SCM reserves a processor group, also called PROCESS.
Type PROCESS has a predefined set of processors-GPPROCSS and DPPROCSS-- which are defined
automatically in this processor group:
GPPROCSS
The generate and move processor in Stage 1 and Stage 2. It checks the processor syntax and
creates an executable form of the processor in the processor load library. If a processor contains
syntax errors, GPPROCSS does not create the executable form. In this situation, refer to the listing
created by GPPROCSS in the processor listing library, to check your errors.
DPPROCSS
The delete processor in Stage 1 and Stage 2. It deletes the executable form of the processor,
should you delete the processor source from CA Endevor® SCM.
After defining the type 'process', you can perform any CA Endevor® SCM action against the type
'process'.
Implement Processors
Follow these steps:
1. Define a system, for example ADMIN, in your production environment, specifying ENDEVOR.
EMER.PRCSLOAD as the Stage 1 processor load library and ENDEVOR.PROD.PRCSLOAD as the
Stage 2 processor load library for system. Remember to define the required processor type,
PROCESS, to this system. Allocating listing libraries is optional.
2. Define a subsystem, for example PROCESS, within system ADMIN. Use subsystem PROCESS to
store and maintain all your processors. The following diagram shows the resulting
configuration:
04-May-2018 371/1109
CA Endevor® SCM - 17.0
04-May-2018 372/1109
CA Endevor® SCM - 17.0
Maintain Processors
To maintain processors managed according to the previous example:
2. Modify the PRCSLOAD and LIST entries in the test system definitions.
4. Add the processor to the test system and run your test programs.
5. After the tests have completed successfully, transfer the processor to your administration
system.
Identifies the delete, generate, and move processor that CA Endevor® SCM should use to process
a particular element type. (A processor group can identify less than three processors if a
particular element type does not require all of them. For example, a non-executable element type
may only require a move processor, so its processor group can omit a generate and delete
processor.)
04-May-2018 373/1109
CA Endevor® SCM - 17.0
Note: For more information about symbols, see Symbols Parameters (see page 294).
You can associate any number of processor groups with a given element type. This is useful when
elements of one type may require slightly different processing. For example, a site may have COBOL
programs coded in batch COBOL and CICS COBOL. In this case, the processor group capability of CA
Endevor® SCM allows you to create a single COBOL type with two processor groups, one to handle
each variation of COBOL code. Furthermore, symbols allow you to use the same processor for both
types, changing only the symbolic overrides in the two processor groups.
If the stage 1 is the entry stage, then the processor group must be defined to both stage 1 and stage
2. If stage 2 is the entry stage (ENTRYSTG#=2 in C1DEFLTS) then it is only necessary to define the
processor group in stage 2.
1-3
Language Type
ASM = Assembler
COB = COBOL
CII = COBOL 2
EAS = Easytrieve
FOR = Fortran
PLI = PL-1
RPG = RPG
TRA = Transform
UTL = Utility
4
Database environment
D = DB2/DL1
S = IDMS
I = IMS
N = None
04-May-2018 374/1109
CA Endevor® SCM - 17.0
5
Operating environment
B = Batch
C = CICS
S = IDMS-DC
I = IMS-DC
N = None
6
Output type
L = Load module
O = Object module
N = None
P = PDS
R = Reports
S = Listing
7, 8
User-defined. Can be used for sequence number, stage identifier, option, etc.
Example
The example later in this section discusses two processor groups: COBNBL and COBNBL01. The
identifier COBNBL indicates that the processor group processes COBOL elements (COB), that the
elements do not have a database type (N), that the processor is for batch execution (B), and that the
output of processor will be a load module (L). The identifier 01 in processor group COBNBL01 is a
sequence number indicating that COBNBL is a default processor group, with processor COBNBL01 as
a derivative processor group.
User-Defined Symbols
CA Endevor® SCM supports user-defined symbols in processors. The symbols defined for each
processor in a processor group appear on the Processor Group Symbolics panel. You can use this
panel to view and/or override user-defined symbols for this processor group.
04-May-2018 375/1109
CA Endevor® SCM - 17.0
To specify a default processor group for an element type, enter the group's name in the DFLT PROC
GRP field on the Type Definition panel. After that, each element of that type that you create is
automatically associated with the type's symbolic overrides. If the element requires special
processing, however, you can override the default symbols at execution time.
Note: For more information, see Change or Display Processor Group Symbols (see page 377
).
Change the definition of a processor group by selecting option 6 from the Environment Options
Menu.
Change the default processor group for a given type, or assign a new processor group to a new
type, by changing the value in the DFLT PROC GRP field on a Type Definition panel.
1. Select option 6 and press Enter. CA Endevor® SCM displays the Processor Group Request
panel.
A stage ID.
Press ENTER.
04-May-2018 376/1109
3.
Processor Group Selection List, select a processor group and press ENTER. You can:
Display information about the group by typing an S to the left of the group's name.
Update information about the group by typing a U to the left of the group's name.
Note: For more information about this panel, see The Processor Group Definition
Panel (see page ).
Create, Update, and Display Processor Group Information (Type Definition Panel)
Follow these steps:
1. Access the Type Definition panel in update or create mode by selecting option C or U from the
Type Request panel. For details, see Defining Inventory Structure (https://docops.ca.com/display
/CE17/Defining+Inventory+Structures).
2. Change the DFLT PROC GRP value and press Enter. CA Endevor® SCM displays the Processor
Group Definition panel, in either create or update mode.
3. Type or change information as necessary on the Processor Group Definition panel and press
Enter. CA Endevor® SCM displays the message GROUP CREATED in the upper right corner.
Note: For more information about this panel, see The Processor Group Definition
Panel (see page ).
You can change the value in the -/O (Default/Override) and VALUE fields when the processing mode
of this panel is Update.
If the value in the -/O field is - (dash), you can change the default value of the symbol by typing O
in the --/O field, and typing new information in the VALUE field, and pressing ENTER.
04-May-2018 377/1109
CA Endevor® SCM - 17.0
Enter a new override value by typing it in the VALUE field and pressing ENTER.
Restore the default value for the symbol by typing - (dash) in the -/O field and pressing
ENTER.
Once you have established a default value and an override value for a symbol you can toggle back
and forth between them by typing -- (dash) or O in the -/O field and pressing ENTER.
Note: If the dash is specified the symbols original value is restored when you end your CA
Endevor® SCM session.
2. When you create type COBOL, override the default value *NOPROC* in the DFLT PROC GRP
field of the Type Definition panel with the name you have selected for the processor group
that stores listings, in this case COBNBL.
When you press Enter, a Processor Group Definition panel is displayed.
3. Create the default processor group by typing the following information on the Processor
Group Definition panel:
The element names for the generate, move, and/or delete processors that will make up
the processor group.
4. To view a list of the symbols for any of these processors, type S next to a processor and press
Enter.
6.
04-May-2018 378/1109
CA Endevor® SCM - 17.0
6. To create the second processor group that you need for your COBOL inventory, access a
Processor Group Definition panel through option 6 of the Environment Options Menu. Specify
the name of the second processor group (COBNBL01) on the Processor Group Request panel.
Type the information for the new processor group on the Processor Group Definition panel.
Note: We have used the same generate, move, and delete processors for both
processor groups.Type U (update symbolics) next to the generate processor
(GCIINBL) on the Processor Group Definition panel and press Enter. On the
Processor Group Symbolics panel, type O in the -/O field next to the symbol LISTLIB,
then type new information in the VALUE field for this symbol.
7. Press ENTER. You have created a second processor group to print compile listings by simply
changing the symbols referenced by the GCIINBL processor.
Display Processors
You can access the Processor Display panel from the Processor Group Definition panel by typing L
(List) in the selection field next to the processor in which you are interested, then pressing ENTER.
Note: For more information about this panel, see Processor Display Panel (see page ).
The panel fields are described, except for SELECTION, they are display-only.
Current Env
Name of the current environment.
Stage ID
Name of the current stage.
System
Name of the current system.
Type
Name of the type to which the processor group(s) apply.
Next Env
Name of the environment in the next map location.
Stage ID
04-May-2018 379/1109
CA Endevor® SCM - 17.0
Stage ID
Name of the stage at the next map location.
System
Name of the system at the next map location.
Type
Name of the type at the next map location.
Processor Group
Name of the processor group.
The fields that appear on a Processor Group Definition panel depend on the type to which the
processor group applies and the processing option that you have selected.
Processor Group Definition panels for CREATE and UPDATE provide three output management
information options (S--browse symbolics, U--update symbolics, L--list processor) and allow you
to enter information in the DESCRIPTION, PROCESSOR, and FOREGROUND EXECUTION fields.
Processor Group Definition panels for DISPLAY and DELETE provide two output management
information options (S--browse symbolics, L--list processor), and do not allow you to enter
information in any fields.
Processor Group Definition panels for type PROCESS and for the default processor group
*NOPROC* provide no output management information options and allow you to enter
information only in the DESCRIPTION and FOREGROUND EXECUTION fields. The PROCESSOR O/P
TYPE field is available for the default proc group: *NOPROC*
Note: In effect, there is only one processor group for type PROCESS. These “processors that
process processors” (GPPROCSS and DPPROCSS) are hard coded in CA Endevor® SCM. The
only allowed update actions against this processor group are changing the description of
the processor group and/or allowing the processors to run in foreground.
If you run an action in foreground that normally would result in a processor being executed, but that
processor cannot be run in foreground, you receive a message stating that fact. In this situation, you
must submit the job in batch.
04-May-2018 380/1109
CA Endevor® SCM - 17.0
The remaining information in this section relates to the Processor Group Definition panel.
The use of the Processor Group Definition panel varies by processing option:
Display
Display a processor group definition.
Delete
View a processor group definition and verify that you want to delete it. To cancel the request,
press End.
Create
Define a new processor group. To cancel the request, press End.
Update
Modify a processor group definition. To cancel the request, press END.
After you have entered the necessary information on the panel, press ENTER to perform the
requested processing.
Identification Fields
The first six fields on this panel identify the processor group. If you have accessed this panel to
display, delete, or update this processor group, information appears in all six fields. If you have
accessed this panel to create a processor group, you must type information in the DESCRIPTION field.
Current Env
Display-only. Name of the current environment.
Stage ID
Display-only. Name of the stage in which the processor groups on the list are defined.
System
Display-only. Name of the system in which the processor groups on the list are defined.
Type
Display-only. Name of the type to which the processor group applies.
Next Env
Display-only. Name of the environment at the next map location.
Stage ID
Display-only. Name of the stage at the next map location.
System
Display-only. Name of the system at the next map location.
Type
Name of the type at the next map location. You can change the type name when you access this
panel in create or update mode.
Processor Group
Name of the processor group.
04-May-2018 381/1109
CA Endevor® SCM - 17.0
Description
Description of the processor group.
After release 3.6 was installed, the processor group name appears in this field.
Updated
Identifies the date, time, and user ID of the last user to update the processor group definition.
When creating a new processor group definition this field is blank.
The TRANSFER action executes a generate processor at the target location. If you want to transfer
component lists as part of the TRANSFER action, specify M in the PROCESSOR TO USE FOR TRANSFER
ACTION field, to tell CA Endevor® SCM to execute the move, not the generate, processor.
Note: You can select either a move or a generate processor only when transferring from
one CA Endevor® SCM location to another. When transferring from an archive data set to
CA Endevor® SCM, or when using a move processor with a TRANSFER action, CA Endevor®
SCM does not allow you to rename elements at the target location.
04-May-2018 382/1109
CA Endevor® SCM - 17.0
Option Fields
The options that appear on Processor Group Definition panels may be used as indicated next. These
options are not available for type Process or for processor groups named *NOPROC*.
S-Browse Symbolics
Appears on Processor Group Definition panels for display, delete, create, and update processing.
Used to access a Processor Group Symbolics panel.
L-List Processor
Appears on Processor Definition panels for display, delete, create, and update processing. Used to
access a Processor Display panel.
U-Update Symbolics
Appears on Processor Definition panels for create and update processing only. Used to access a
Processor Group Symbolics panel.
If you have accessed this panel to display, delete, or update a processor group, information
displays in these fields.
If you have accessed this panel to create a new processor group, you must type the names of the
processors that you want to include in this new group in these fields.
If these fields contain processor names when you access the Processor Group Definition panel in
create mode, you can override these names with new values. If you want to use one or more of
the processors that appear on this panel, first make sure that they are defined for the system and
stage for which you are creating the processor group.
Note: These are required fields. If you do not want to identify one or more processors in
this processor group, you must enter the value *NOPROC* in those fields. (CA Endevor®
SCM converts one or more blanks in these fields to *NOPROC*.)
04-May-2018 383/1109
CA Endevor® SCM - 17.0
When a processor runs as part of a package, the package foreground execution flag (PKGTSO= in the
C1DEFLTS Table) overrides the foreground execution flag in the processor group. This means that if a
package can be executed in foreground, all processors in that package will execute, regardless of the
value in the foreground execution field for the processor group.
Identification Fields
The first eight fields on this panel identify the inventory area to which the processor group is defined
(CURRENT ENV, STAGE ID, SYSTEM, and TYPE), the processor group (PROCESSOR GROUP and
DESCRIPTION), a processor within the group (PROCESSOR), and where it is stored (LOAD LIBRARY).
Immediately below the identification fields there are three lines of instructions for working with this
panel.
Symbolic
Name of the symbol in the PROC statement of the processor.
- (dash)/O
Indicates the status of the value of the symbol.
- (dash)-Default value for the symbol. This is the value assigned to the symbol in the PROC
statement contained in the processor.
O-Override value for the symbol.
Value
Value to be assigned to the symbol during the next run of the processor.
Note that the ISPF browse facility is used to display processors, so you can use ISPF browse
commands on the COMMAND line.
PROCESSOR FOOTPRINT fields, which provide footprint information about the processor.
A processor listing.
04-May-2018 384/1109
CA Endevor® SCM - 17.0
A processor listing.
Sample Processors
Contents
The processor examples in this article demonstrate the use of CA Endevor® SCM utilities, keywords,
and user-defined symbols within the processors. These capabilities let you easily convert your JCL and
PROCs into CA Endevor® SCM processors. User-defined symbols can then be overridden by the
administrator during processor group definition.
EXPINC=N
04-May-2018 385/1109
CA Endevor® SCM - 17.0
EXPINC=N
If you do not want to expand ++INCLUDE or -INC statements.
EXPINC=Y
If you want to expand ++INCLUDE and -INC statements.
MONITOR= COMPONENTS
If you want to monitor selected data sets in order to build component lists.
MONITOR=NONE
If you do not have ACM or do not want the data set monitored.
f. Ensure that all user symbols are defined on the PROC statement.
Generate Processors
This section contains sample generate processors. Samples are provided in iprfx.iqual.CSIQSAMP.
These processors are:
GASMNBL
An Assembler compile and link-edit processor.
GCIIDBL
A processor that performs a DB2 pre-compile, compiles, link-edits a COBOL II program, and binds
the DB2 plan.
04-May-2018 386/1109
CA Endevor® SCM - 17.0
GCIINBL
A COBOL II and COBOL/370 compile and link-edit processor.
GLNKNBL
A link-edit-only processor (composite link).
LOADONLY
This processor handles “sourceless” load modules or binary files that you want CA Endevor® SCM
to manage It is used as a generate process for ADD and UPDATE, and a move process for MOVE
and TRANSFER.
These processors are designed to execute at Stage 1. To use a processor at Stage 2, override during
processor group definition the &CSYSLIB1, &LSYSLIB1, &LISTLIB and &LOADLIB symbols with the
appropriate Stage 2 data set names.
For ACM users, each processor is coded to monitor the appropriate data sets. This option has been
coded using the MONITOR=&MONITOR syntax. The MONITOR symbol defaults to COMPONENTS as
defined on each PROC statement. If you do not have or use ACM, you can override the value for the
MONITOR symbol to read NONE.
These processors also offer two alternatives for handling listings. If you override the value of the
LISTLIB parameter to read no, the listings will be printed rather than stored.
The names of the sample processors in this appendix reflect the conventions discussed (on page xx).
Each sample is introduced with an expansion of its identifier. For example, GCIINBL is introduced as G
enerate COBOL II, No database, for Batch, and create a Load module.
04-May-2018 387/1109
CA Endevor® SCM - 17.0
//* ALLOCATE TEMPORARY LISTING DATASETS *
//**********************************************************************
//INIT EXEC PGM=BC1PDSIN,MAXRC=0
//C1INIT01 DD DSN=&&ASMLIST,DISP=(,PASS),
// UNIT=&WRKUNIT.,SPACE=(TRK,(100,100),RLSE),
// DCB=(RECFM=FBA,LRECL=125,BLKSIZE=0,DSORG=PS)
//C1INIT02 DD DSN=&&LNKLIST,DISP=(,PASS),
// UNIT=&WRKUNIT.,SPACE=(TRK,(10,10),RLSE),
// DCB=(RECFM=FBA,LRECL=125,BLKSIZE=0,DSORG=PS)
//*********************************************************************
//* READ SOURCE AND EXPAND INCLUDES *
//*********************************************************************
//CONWRITE EXEC PGM=CONWRITE,COND=(0,LT),MAXRC=0,
// PARM='EXPINCL(&EXPINC)'.
//ELMOUT DD DSN=&&ELMOUT,DISP=(,PASS),
// UNIT=&WRKUNIT.,SPACE=(TRK,(100,100),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=0),
// MONITOR=&MONITOR.
//*******************************************************************
//* ASSEMBLE THE ELEMENT **
//*******************************************************************
//ASM EXEC PGM=ASMA90,COND=(0,LT),MAXRC=4,
// PARM='&PARMASM'.
//SYSLIB DD DSN=&MACLIB1.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&MACLIB2.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&MACLIB3.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&MACLIB4.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&MACLIB.,
// DISP=SHR
//SYSIN DD DSN=&&ELMOUT,DISP=(OLD,DELETE)
//SYSLIN DD DSN=&&SYSLIN,DISP=(,PASS,DELETE),
// UNIT=&WRKUNIT.,SPACE=(TRK,(100,100),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=0),
// FOOTPRNT=CREATE
//SYSPUNCH DD DUMMY
//SYSUT1 DD UNIT=&WRKUNIT.,SPACE=(CYL,(1,1))
//SYSUT2 DD UNIT=&WRKUNIT.,SPACE=(CYL,(1,1))
//SYSUT3 DD UNIT=&WRKUNIT.,SPACE=(CYL,(1,1))
//SYSPRINT DD DSN=&&ASMLIST,DISP=(OLD,PASS)
//*******************************************************************
//* LINK EDIT THE ELEMENT **
//*******************************************************************
//LKED EXEC PGM=IEWL,COND=(4,LT),MAXRC=4,
// PARM='&PARMLNK'.
//SYSLIN DD DSN=&&SYSLIN,DISP=(OLD,DELETE)
//SYSLMOD DD DSN=&LOADLIB(&MEMBER).,
// MONITOR=&MONITOR.,
// FOOTPRNT=CREATE,
// DISP=SHR
//SYSLIB DD DSN=&LSYSLIB1.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&LSYSLIB2.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&LSYSLIB3.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&LSYSLIB4.,
// MONITOR=&MONITOR.,
// DISP=SHR
//SYSUT1 DD UNIT=&WRKUNIT.,SPACE=(CYL,(1,1))
//SYSPRINT DD DSN=&&LNKLIST,DISP=(OLD,PASS)
//*******************************************************************
04-May-2018 388/1109
CA Endevor® SCM - 17.0
//*******************************************************************
//* STORE THE LISTINGS IF: &LISTLIB=LISTING. LIBRARY NAME *
//*******************************************************************
//STORLIST EXEC PGM=CONLIST,MAXRC=0,PARM=STORE,COND=EVEN,
// EXECIF=(&LISTLIB.,NE,NO)
//C1LLIBO DD DSN=&LISTLIB.,DISP=SHR,
// MONITOR=&MONITOR.
//C1BANNER DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=0)
//LIST01 DD DSN=&&ASMLIST,DISP=(OLD,DELETE)
//LIST02 DD DSN=&&LNKLIST,DISP=(OLD,DELETE)
//*******************************************************************
//* PRINT THE LISTINGS IF: &LISTLIB=NO. *
//*******************************************************************
//PRNTLIST EXEC PGM=CONLIST,MAXRC=0,PARM=PRINT,COND=EVEN,
// EXECIF=(&LISTLIB.,EQ,NO)
//C1BANNER DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=0,DSORG=PS)
//C1PRINT DD SYSOUT=&SYSOUT.,
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0,DSORG=PS)
//LIST01 DD DSN=&&ASMLIST,DISP=(OLD,DELETE)
//LIST02 DD DSN=&&LNKLIST,DISP=(OLD,DELETE)
04-May-2018 389/1109
CA Endevor® SCM - 17.0
//INIT EXEC PGM=BC1PDSIN,MAXRC=0
//C1INIT01 DD DISP=(,PASS),DSN=&&DB2PLIST,
// UNIT=&WRKUNIT.,SPACE=(TRK,(10,10)),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0)
//C1INIT02 DD DISP=(,PASS),DSN=&&COBLIST,
// UNIT=&WRKUNIT.,SPACE=(TRK,(10,10)),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0)
//C1INIT03 DD DISP=(,PASS),DSN=&&LNKLIST,
// UNIT=&WRKUNIT.,SPACE=(TRK,(10,10)),
// DCB=(RECFM=FBA,LRECL=125,BLKSIZE=0)
//C1INIT04 DD DISP=(,PASS),DSN=&&PARMLIST,
// UNIT=&WRKUNIT.,SPACE=(TRK,(10,10)),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0)
//*********************************************************************
//* READ SOURCE AND EXPAND INCLUDES *
//*********************************************************************
//CONWRITE EXEC PGM=CONWRITE,COND=(0,LT),MAXRC=0,
// PARM='EXPINCL(&EXPINC)'.
//C1INCL01 DD DSN=&CSYSLIB1.,DISP=SHR,
// MONITOR=&MONITOR.
//C1INCL02 DD DSN=&CSYSLIB2.,DISP=SHR,
// MONITOR=&MONITOR.
//C1INCL03 DD DSN=&CSYSLIB3.,DISP=SHR,
// MONITOR=&MONITOR.
//C1INCL04 DD DSN=&CSYSLIB4.,DISP=SHR,
// MONITOR=&MONITOR.
//ELMOUT DD DSN=&&ELMOUT,DISP=(,PASS),
// UNIT=&WRKUNIT.,SPACE=(TRK,(10,10),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=0),
// MONITOR=&MONITOR.
//*********************************************************************
//* DB2 PRECOMPILIER PROCESSING *
//*********************************************************************
//PRECOMP EXEC PGM=DSNHPC,COND=(0,NE),MAXRC=4,
// PARM='&PARMPC'.
//STEPLIB DD DSN=&DB2LOADL.,DISP=SHR
//DBRMLIB DD DSN=&DBRMLIB(&MEMBER).,DISP=SHR,
// MONITOR=&MONITOR.,
// FOOTPRNT=CREATE
//SYSIN DD DSN=&&ELMOUT,DISP=OLD
//SYSCIN DD DSN=&&PREOUT,DISP=(,PASS),
// UNIT=&WRKUNIT.,SPACE=(TRK,(10,10),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=0)
//SYSLIB DD DSN=&CSYSLIB1.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&CSYSLIB2.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&CSYSLIB3.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&CSYSLIB4.,
// MONITOR=&MONITOR.,
// DISP=SHR
//SYSTERM DD SYSOUT=&SYSOUT.
//SYSPRINT DD DSN=&&DB2PLIST,DISP=(OLD,PASS)
//SYSUT1 DD UNIT=&WRKUNIT.,SPACE=(CYL,(1,1))
//SYSUT2 DD UNIT=&WRKUNIT.,SPACE=(CYL,(1,1))
//*******************************************************************
//** COMPILE THE ELEMENT **
//*******************************************************************
//COMPILE EXEC PGM=IGYCRCTL,COND=(0,LT),MAXRC=4,
// PARM='&PARMCOB'.
//* TEST PROCESSOR GROUP IF CIINBL THEN ALLOCATE COBOL2 LIBRARIES
//* IF CLENBL ALLOCATE COBOL/MVS RUNTIME LIBS
// IF &C1PRGRP=CIINBL. THEN
//STEPLIB DD DSN=&CIICOMP.,DISP=SHR
// DD DSN=&CIILIB.,DISP=SHR
// ELSE
//* PROCESSOR GROUP IS COBOL/LE
//STEPLIB DD DSN=&CLECOMP.,DISP=SHR
04-May-2018 390/1109
CA Endevor® SCM - 17.0
//STEPLIB DD DSN=&CLECOMP.,DISP=SHR
// DD DSN=&CLERUN.,DISP=SHR
// ENDIF
//*******************************************************************
//* COPYLIB CONCATENATIONS **
//*******************************************************************
//SYSLIB DD DSN=&CSYSLIB1.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&CSYSLIB2.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&CSYSLIB3.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&CSYSLIB4.,
// MONITOR=&MONITOR.,
// DISP=SHR
//SYSIN DD DSN=&&PREOUT,DISP=(OLD,DELETE)
//SYSLIN DD DSN=&&SYSLIN,DISP=(,PASS,DELETE),
// UNIT=&WRKUNIT.,SPACE=(TRK,(10,10),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=0),
// FOOTPRNT=CREATE
//SYSUT1 DD UNIT=&WRKUNIT.,SPACE=(CYL,(5,3))
//SYSUT2 DD UNIT=&WRKUNIT.,SPACE=(CYL,(5,3))
//SYSUT3 DD UNIT=&WRKUNIT.,SPACE=(CYL,(5,3))
//SYSUT4 DD UNIT=&WRKUNIT.,SPACE=(CYL,(5,3))
//SYSUT5 DD UNIT=&WRKUNIT.,SPACE=(CYL,(5,3))
//SYSUT6 DD UNIT=&WRKUNIT.,SPACE=(CYL,(5,3))
//SYSUT7 DD UNIT=&WRKUNIT.,SPACE=(CYL,(5,3))
//SYSPRINT DD DSN=&&COBLIST,DISP=(OLD,PASS)
//*******************************************************************
//** LINK EDIT THE ELEMENT **
//*******************************************************************
//LKED EXEC PGM=IEWL,COND=(4,LT),MAXRC=4,
// PARM='&PARMLNK'.
//SYSLIN DD DSN=&&SYSLIN,DISP=(OLD,DELETE)
//SYSLMOD DD DSN=&LOADLIB(&MEMBER).,
// MONITOR=&MONITOR.,
// FOOTPRNT=CREATE,
// DISP=SHR
//SYSLIB DD DSN=&LSYSLIB1.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&LSYSLIB2.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&LSYSLIB3.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&LSYSLIB4.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&DB2LOADL.,
// DISP=SHR
//* IF PROCESSOR GROUP IS CIINBL THEN ALLOC COB2 CALL LIBRARY COB2LIB
// IF &C1PRGRP=CIINBL. THEN
// DD DSN=&CIILIB.,
// DISP=SHR
// ELSE
//* IF PROCESSOR GROUP IS COBOL/LE THEN ALLOC LE CALL LIBRARY SCEELKED
// DD DSN=&CLELKED.,
// DISP=SHR
// ENDIF
//SYSUT1 DD UNIT=&WRKUNIT.,SPACE=(CYL,(1,1))
//SYSPRINT DD DSN=&&LNKLIST,DISP=(OLD,PASS)
//*********************************************************************
//* BIND APPLICATION PLAN IF EXECUTING IN FOREGROUND
//* NOTE: ATTEMPTING TO RUN THIS STEP IN BG WILL RESULT IN RC=5
//*********************************************************************
//BINDFG EXEC PGM=BC1PTMP0,MAXRC=5,COND=(4,LT),
// PARM='&PARMLIB(&C1ELEMENT)'.
04-May-2018 391/1109
CA Endevor® SCM - 17.0
// PARM='&PARMLIB(&C1ELEMENT)'.
//STEPLIB DD DSN=&DB2LOADL.,DISP=SHR
//DBRMLIB DD DSN=&DBRMLIB.,DISP=SHR
//SYSUDUMP DD SYSOUT=&SYSOUT.
//*********************************************************************
//* BIND APPLICATION PLAN IF EXECUTING IN BACKGROUND *
//*********************************************************************
//BINDBG EXEC PGM=IKJEFT01,COND=((5,NE,BINDFG),(5,LT)),MAXRC=7
//STEPLIB DD DSN=&DB2LOADL.,DISP=SHR
//DBRMLIB DD DSN=&DBRMLIB.,DISP=SHR
//SYSTSPRT DD DSN=&&PARMLIST,DISP=(OLD,PASS)
//SYSTSIN DD DSN=&PARMLIB(&C1ELEMENT).,DISP=(OLD,PASS)
//*******************************************************************
//* STORE THE LISTINGS IF: &LISTLIB=LISTING. LIBRARY NAME *
//*******************************************************************
//STORLIST EXEC PGM=CONLIST,MAXRC=0,PARM=STORE,COND=EVEN,
// EXECIF=(&LISTLIB.,NE,NO)
//C1LLIBO DD DSN=&LISTLIB.,DISP=SHR,
// MONITOR=&MONITOR.
//C1BANNER DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171)
//LIST01 DD DSN=&&DB2PLIST,DISP=(OLD,DELETE)
//LIST02 DD DSN=&&COBLIST,DISP=(OLD,DELETE)
//LIST03 DD DSN=&&LNKLIST,DISP=(OLD,DELETE)
//LIST04 DD DSN=&&PARMLIST,DISP=(OLD,DELETE)
//*******************************************************************
//* PRINT THE LISTINGS IF: &LISTLIB=NO. *
//*******************************************************************
//PRNTLIST EXEC PGM=CONLIST,MAXRC=0,PARM=PRINT,COND=EVEN,
// EXECIF=(&LISTLIB.,EQ,NO)
//C1BANNER DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171,DSORG=PS)
//C1PRINT DD SYSOUT=&SYSOUT.,
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=1330,DSORG=PS)
//LIST01 DD DSN=&&DB2PLIST,DISP=(OLD,DELETE)
//LIST02 DD DSN=&&COBLIST,DISP=(OLD,DELETE)
//LIST03 DD DSN=&&LNKLIST,DISP=(OLD,DELETE)
//LIST04 DD DSN=&&PARMLIST,DISP=(OLD,DELETE)
//**
CII-COBOL II
CLE-COBOL/LE
// CSYSLIB1='&PROJECT..&GROUP.&C1ST..COPYLIB',
04-May-2018 392/1109
CA Endevor® SCM - 17.0
// CSYSLIB1='&PROJECT..&GROUP.&C1ST..COPYLIB',
// CSYSLIB2='&PROJECT..&GROUP.&C1ST2..COPYLIB',
// CSYSLIB3='&PROJECT..&GROUP.&STG3..COPYLIB',
// CSYSLIB4='&PROJECT..&GROUP.&STG4..COPYLIB',
// EXPINC=N,
// LOADLIB='&PROJECT..&GROUP.&C1ST..LOADLIB',
// LSYSLIB1='&LOADLIB'.,
// LSYSLIB2='&PROJECT..&GROUP.&C1ST2..LOADLIB',
// LSYSLIB3='&PROJECT..&GROUP.&STG3..LOADLIB',
// LSYSLIB4='&PROJECT..&GROUP.&STG4..LOADLIB',
// MEMBER=&C1ELEMENT.,
// MONITOR=COMPONENTS,
// PARMCOB='LIB,NOSEQ,OBJECT,APOST,',
// PARMLNK='LIST,MAP,XREF',
// SYSOUT=*,
// WRKUNIT=TDISK
//**********************************************************************
//* ALLOCATE TEMPORARY LISTING DATASETS *
//**********************************************************************
//INIT EXEC PGM=BC1PDSIN,MAXRC=0
//C1INIT01 DD DSN=&&COBLIST,DISP=(,PASS),
// UNIT=&WRKUNIT.,SPACE=(TRK,(10,10)),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0,DSORG=PS)
//C1INIT02 DD DSN=&&LNKLIST,DISP=(,PASS),
// UNIT=&WRKUNIT.,SPACE=(TRK,(10,10)),
// DCB=(RECFM=FBA,LRECL=125,BLKSIZE=0,DSORG=PS)
//*********************************************************************
//* READ SOURCE AND EXPAND INCLUDES *
//*********************************************************************
//CONWRITE EXEC PGM=CONWRITE,COND=(0,LT),MAXRC=0,
// PARM='EXPINCL(&EXPINC)'.
//ELMOUT DD DSN=&&ELMOUT,DISP=(,PASS),
// UNIT=&WRKUNIT.,SPACE=(TRK,(100,100),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=0),
// MONITOR=&MONITOR.
//*******************************************************************
//** COMPILE THE ELEMENT **
//*******************************************************************
//COMPILE EXEC PGM=IGYCRCTL,COND=(0,LT),MAXRC=4,
// PARM='&PARMCOB'.
//* TEST PROCESSOR GROUP IF CIINBL THEN ALLOCATE COBOL2 LIBRARIES
//* IF CLENBL ALLOCATE COBOL/MVS RUNTIME LIBS
// IF &C1PRGRP=CIINBL. THEN
//STEPLIB DD DSN=&CIICOMP.,DISP=SHR
// DD DSN=&CIILIB.,DISP=SHR
// ELSE
//* PROCESSOR GROUP IS COBOL/LE
//STEPLIB DD DSN=&CLECOMP.,DISP=SHR
// DD DSN=&CLERUN.,DISP=SHR
// ENDIF
//*******************************************************************
//* COPYLIB CONCATENATIONS **
//*******************************************************************
//SYSLIB DD DSN=&CSYSLIB1.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&CSYSLIB2.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&CSYSLIB3.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&CSYSLIB4.,
// MONITOR=&MONITOR.,
// DISP=SHR
//SYSIN DD DSN=&&ELMOUT,DISP=(OLD,PASS)
//SYSLIN DD DSN=&&SYSLIN,DISP=(,PASS,DELETE),
// UNIT=&WRKUNIT.,SPACE=(TRK,(100,100),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=0),
// FOOTPRNT=CREATE
//SYSUT1 DD UNIT=&WRKUNIT.,SPACE=(CYL,(5,3))
//SYSUT2 DD UNIT=&WRKUNIT.,SPACE=(CYL,(5,3))
04-May-2018 393/1109
CA Endevor® SCM - 17.0
//SYSUT2 DD UNIT=&WRKUNIT.,SPACE=(CYL,(5,3))
//SYSUT3 DD UNIT=&WRKUNIT.,SPACE=(CYL,(5,3))
//SYSUT4 DD UNIT=&WRKUNIT.,SPACE=(CYL,(5,3))
//SYSUT5 DD UNIT=&WRKUNIT.,SPACE=(CYL,(5,3))
//SYSUT6 DD UNIT=&WRKUNIT.,SPACE=(CYL,(5,3))
//SYSUT7 DD UNIT=&WRKUNIT.,SPACE=(CYL,(5,3))
//SYSPRINT DD DSN=&&COBLIST,DISP=(OLD,PASS)
//*******************************************************************
//** LINK EDIT THE ELEMENT **
//*******************************************************************
//LKED EXEC PGM=IEWL,COND=(4,LT),MAXRC=4,
// PARM='&PARMLNK'.
//SYSLIN DD DSN=&&SYSLIN,DISP=(OLD,DELETE)
//SYSLMOD DD DSN=&LOADLIB(&MEMBER).,
// MONITOR=&MONITOR.,
// FOOTPRNT=CREATE,
// DISP=SHR
//SYSLIB DD DSN=&LSYSLIB1.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&LSYSLIB2.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&LSYSLIB3.,
// MONITOR=&MONITOR.,
// DISP=SHR
// DD DSN=&LSYSLIB4.,
// MONITOR=&MONITOR.,
// DISP=SHR
//* IF PROCESSOR GROUP IS CIINBL THEN ALLOC COB2 CALL LIBRARY COB2LIB
// IF &C1PRGRP=CIINBL. THEN
// DD DSN=&CIILIB.,
// DISP=SHR
// ELSE
//* IF PROCESSOR GROUP IS COBOL/LE THEN ALLOC LE CALL LIBRARY SCEELKED
// DD DSN=&CLELKED.,
// DISP=SHR
// ENDIF
//SYSUT1 DD UNIT=&WRKUNIT.,SPACE=(CYL,(1,1))
//SYSPRINT DD DSN=&&LNKLIST,DISP=(OLD,PASS)
//*******************************************************************
//* STORE THE LISTINGS IF: &LISTLIB=LISTING. LIBRARY NAME *
//*******************************************************************
//STORLIST EXEC PGM=CONLIST,MAXRC=0,PARM=STORE,COND=EVEN,
// EXECIF=(&LISTLIB.,NE,NO)
//C1LLIBO DD DSN=&LISTLIB.,DISP=SHR,
// MONITOR=&MONITOR.
//C1BANNER DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=0)
//LIST01 DD DSN=&&COBLIST,DISP=(OLD,DELETE)
//LIST02 DD DSN=&&LNKLIST,DISP=(OLD,DELETE)
//*******************************************************************
//* PRINT THE LISTINGS IF: &LISTLIB=NO. *
//*******************************************************************
//PRNTLIST EXEC PGM=CONLIST,MAXRC=0,PARM=PRINT,COND=EVEN,
// EXECIF=(&LISTLIB.,EQ,NO)
//C1BANNER DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=0,DSORG=PS)
//C1PRINT DD SYSOUT=&SYSOUT.,
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0,DSORG=PS)
//LIST01 DD DSN=&&COBLIST,DISP=(OLD,DELETE)
//LIST02 DD DSN=&&LNKLIST,DISP=(OLD,DELETE)
//**
04-May-2018 394/1109
CA Endevor® SCM - 17.0
//** LINK-EDIT ONLY PROCESSOR (COMPOSITE LINK) FOR TYPE LINKCARD **
//** (USING ASSEMBLER OR COBOL OBJECT MODULES) **
//** **
//*******************************************************************
//*
//GLNKNBL PROC LISTLIB='&PROJECT..&GROUP.&STG1..LISTLIB',
// LOADLIB='&PROJECT..&GROUP.&STG1..LOADLIB',
// CII='C??',
// CIILIB='SYSCIILIB', **COB2LIB
// CLELIB='SYSCLELIB', **SCEELKED
// EXPINC=N,
// PROJECT='IPRFX.IQUAL',
// GROUP='SMPL',
// LSYSLIB1='&PROJECT..&GROUP.&C1ST..LOADLIB',
// LSYSLIB2='&PROJECT..&GROUP.&C1ST2..LOADLIB',
// LSYSLIB3='&PROJECT..&GROUP.&STG3..LOADLIB',
// LSYSLIB4='&PROJECT..&GROUP.&STG4..LOADLIB',
// STG3='EMER',
// STG4='PROD',
// MEMBER=&C1ELEMENT.,
// MONITOR=COMPONENTS,
// OBJLIB1='&PROJECT..&GROUP.&C1ST..OBJLIB',
// OBJLIB2='&PROJECT..&GROUP.&C1ST2..OBJLIB',
// OBJLIB3='&PROJECT..&GROUP.&STG3..OBJLIB',
// OBJLIB4='&PROJECT..&GROUP.&STG4..OBJLIB',
// PARMLNK='LIST,MAP,XREF',
// WRKUNIT=TDISK
//**********************************************************************
//* ALLOCATE TEMPORARY LISTING DATASETS *
//**********************************************************************
//INIT EXEC PGM=BC1PDSIN,MAXRC=0
//C1INIT01 DD DSN=&&LNKLIST,DISP=(,PASS),
// UNIT=&WRKUNIT.,SPACE=(CYL,(1,2),RLSE),
// DCB=(RECFM=FBA,LRECL=125,BLKSIZE=0,DSORG=PS)
//*******************************************************************
//** LINK EDIT THE ELEMENT **
//*******************************************************************
//LKED EXEC PGM=IEWL,COND=(0,LT),MAXRC=0,
// PARM='&PARMLNK'.
//SYSPRINT DD DSN=&&LNKLIST,DISP=(OLD,PASS)
//SYSUT1 DD UNIT=TDISK,SPACE=(CYL,(1,1))
//SYSLIB DD DSN=&LSYSLIB1.,DISP=SHR,
// MONITOR=COMPONENTS
// DD DSN=&LSYSLIB2.,DISP=SHR,
// MONITOR=COMPONENTS
// DD DSN=&LSYSLIB3.,DISP=SHR,
// MONITOR=COMPONENTS
// DD DSN=&LSYSLIB4.,DISP=SHR,
// MONITOR=COMPONENTS
// IF &CII=CII. THEN
// DD DSN=&CIILIB.,DISP=SHR
// ELSE
// DD DSN=&CLELIB.,DISP=SHR
// ENDIF
//OBJLIB DD DSN=&OBJLIB1.,DISP=SHR,
// MONITOR=COMPONENTS
// DD DSN=&OBJLIB2.,DISP=SHR,
// MONITOR=COMPONENTS
// DD DSN=&OBJLIB3.,DISP=SHR,
// MONITOR=COMPONENTS
// DD DSN=&OBJLIB4.,DISP=SHR,
// MONITOR=COMPONENTS
//SYSLIN DD DSN=&C1BASELIB(&C1ELEMENT).,DISP=SHR
//SYSLMOD DD DSN=&LOADLIB.,DISP=SHR,
// FOOTPRNT=CREATE,
// MONITOR=COMPONENTS
//*******************************************************************
//* STORE THE LISTINGS IF: &LISTING=LISTING. LIBRARY NAME *
//*******************************************************************
//STORLIST EXEC PGM=CONLIST,MAXRC=0,PARM=STORE,COND=EVEN,
// EXECIF=(&LISTLIB.,NE,NO)
//C1LLIBO DD DSN=&LISTLIB.,DISP=SHR,
04-May-2018 395/1109
CA Endevor® SCM - 17.0
//C1LLIBO DD DSN=&LISTLIB.,DISP=SHR,
// MONITOR=&MONITOR.
//C1BANNER DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171)
//LIST01 DD DSN=&&LNKLIST,DISP=(OLD,DELETE)
//*******************************************************************
//* PRINT THE LISTINGS IF: &LISTING=NO. *
//*******************************************************************
//PRNTLIST EXEC PGM=CONLIST,MAXRC=0,PARM=PRINT,COND=EVEN,
// EXECIF=(&LISTLIB.,EQ,NO)
//C1BANNER DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171,DSORG=PS)
//C1PRINT DD SYSOUT=*,
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0,DSORG=PS)
//LIST01 DD DSN=&&LNKLIST,DISP=(OLD,DELETE)
//*
Generate-Copies the requested element, file, or member from the user's file into and CA
Endevor® SCM managed library.
Move-Copies the member from one stage's output library to the next stage's output library.
//**********************************************************************
//* *
//* COPY SOURCELES LOAD MODULES FROM USER DATA SETS TO STAGE1 *
//* *
//**********************************************************************
//*
//LOADONLY PROC LISTLIB='&PROJECT..&GROUP.SMPL&C1ST..LISTLIB',
// LOADLIB1='&PROJECT..&GROUP.SMPL&C1ST..LOADLIB',
// LOADLIB2='&PROJECT..&GROUP.SMPL&STG2..LOADLIB',
// PROJECT='IPRFX',
// GROUP='IQUAL',
// STG2='&C1SSTAGE.', FROM STAGE FOR TRANSFER/MOVE
// MONITOR=COMPONENTS,
// SYSOUT=*,
// WRKUNIT=TDISK
//**********************************************************************
//* ALLOCATE TEMPORARY LISTING DATASETS *
//**********************************************************************
//INIT EXEC PGM=BC1PDSIN
//C1INIT01 DD DSN=&©LIST,
// DISP=(NEW,PASS,DELETE),
// UNIT=&WRKUNIT.,
// SPACE=(CYL,(1,2),RLSE),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0,DSORG=PS)
//**********************************************************************
//* *
//* ONLY PERFORM COPY FROM USER LOADLIB WHEN ADD OR UPDATE IS REQUESTED*
//* *
//**********************************************************************
//IF1 IF ((&C1ACTION=ADD). OR (&C1ACTION=UPDATE)). THEN
//ADD EXEC PGM=BSTCOPY,MAXRC=04
//SYSPRINT DD DSN=&©LIST,DISP=(OLD,PASS)
//SYSUT3 DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1))
//SYSUT4 DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1))
//INDD DD DSN=&C1USRDSN.,DISP=SHR
//OUTDD DD DSN=&LOADLIB1.,DISP=SHR,FOOTPRNT=CREATE
//SYSIN DD *
COPY I=INDD,O=OUTDD
SELECT MEMBER=((&C1USRMBR.,&C1ELEMENT.,R))
//END1 ENDIF
//**********************************************************************
//* *
04-May-2018 396/1109
CA Endevor® SCM - 17.0
//* *
//* IF TRANSFER,COPY FROM SOURCE LOADLIB TO CURRENT LOADLIB *
//* *
//**********************************************************************
//IF2 IF (&C1ACTION=TRANSFER). OR (&C1ACTION=MOVE). THEN
//TRANSFER EXEC PGM=BSTCOPY,MAXRC=04
//SYSPRINT DD DSN=&©LIST,DISP=(OLD,PASS)
//SYSUT3 DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1))
//SYSUT4 DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1))
//INDD DD DSN=&LOADLIB1.,DISP=SHR,FOOTPRNT=VERIFY
//OUTDD DD DSN=&LOADLIB2.,DISP=SHR,FOOTPRNT=CREATE
//SYSIN DD *
COPY I=INDD,O=OUTDD
SELECT MEMBER=((&C1ELEMENT.,,R))
//END2 ENDIF
//*******************************************************************
//* STORE THE LISTINGS IF: &LISTLIB=LISTING. LIBRARY *
//*******************************************************************
//STORLIST EXEC PGM=CONLIST,PARM='STORE',COND=EVEN,
// EXECIF=(&LISTLIB.,NE,NO)
//C1LLIBO DD DSN=&LISTLIB.,DISP=SHR
//C1BANNER DD DSN=&&BANNER,DISP=(,PASS,DELETE),
// UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=0,DSORG=PS)
//LIST01 DD DSN=&©LIST,DISP=(OLD,DELETE)
//*******************************************************************
//* PRINT THE LISTINGS IF: &LISTLIB=NO. *
//*******************************************************************
//PRNTLIST EXEC PGM=CONLIST,MAXRC=0,PARM=PRINT,COND=EVEN,
// EXECIF=(&LISTLIB.,EQ,NO)
//C1BANNER DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=0,DSORG=PS)
//C1PRINT DD SYSOUT=&SYSOUT.,
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0,DSORG=PS)
//LIST01 DD DSN=&©LIST,DISP=(OLD,DELETE)
//*
//**
Delete Processors
Delete processors clean up (delete) what generate processors create. Since most generate processors
create a load module and possibly a listing, delete processors can be generic. A single delete
processor can be used to clean up the work created by several generate processors.
This section contains two sample delete processors. Samples are provided in the iprfx.iqual.
CSIQSAMP. These processors are:
DLODDNL
Delete Load modules, for DB2, No (All) operating environments, No (All) output types.
DLODNNL
Delete Load modules, No (All) databases, No (All) operating environments, No (All) output types.
These processors can be used as Stage 1 or Stage 2 delete processors. To change the PROC
statement symbol values, override the data set names during processor group definition.
If you do not want to store listings, change the &LISTLIB symbol to NO.
//**********************************************************************
04-May-2018 397/1109
CA Endevor® SCM - 17.0
//**********************************************************************
//* *
//* DELETE COBOL LOAD AND LISTING MODULES & DBRM *
//* *
//**********************************************************************
//*
//DLODDNL PROC DBRMLIB='&PROJECT..&GROUP.&STG1..DBRMLIB',
// LISTLIB='&PROJECT..&GROUP.&STG1..LISTLIB',
// LOADLIB='&PROJECT..&GROUP.&STG1..LOADLIB',
// PROJECT='IPRFX.IQUAL',
// GROUP='SMPL',
// STG1='&C1STAGE.' CURRENT STAGE
//*
//DELLOD EXEC PGM=CONDELE,MAXRC=12
//C1LIB DD DSN=&LOADLIB.,DISP=SHR
//*
//DELDBRM EXEC PGM=CONDELE,MAXRC=12
//C1LIB DD DSN=&DBRMLIB.,DISP=SHR
//*
//DELLIST EXEC PGM=CONLIST,PARM='DELETE',MAXRC=12,COND=EVEN,
// EXECIF=(&LISTLIB.,NE,NO)
//C1LLIBI DD DSN=&LISTLIB.,DISP=SHR
Move Processors
Move processors are used during a MOVE action to create the appropriate outputs at the target
stage. This can be accomplished by:
Copying the outputs (load modules and listings) from the source to the target stage. This section
includes two sample move processors that accomplish this.
Recreating the load module at the target stage. This occurs when a generate processor is used as
a move processor.
To use a generate processor as a move processor, make sure to specify G in the PROCESSOR TO
USE FOR THE MOVE ACTION field on the definition panel for the APPROPRIATE PROCESSOR
GROUP.
04-May-2018 398/1109
CA Endevor® SCM - 17.0
Note: Do not re-create load modules at the target stage by coding a compile and link step
in a move processor, this causes the load module footprint to become out of sync with
Master Control File information for the element.
This section contains two sample move processors that are provided in iprfx.iqual.CSIQSAMP. These
processors copy load modules, and their associated component lists and listings, from a source to a
target stage. By using symbolic overrides for LOADLIB1 and LOADLIB2, these processors can be used
for almost every type in your inventory structure. If the &LISTLIB2 symbol is overridden during
processor group definition to read NO, CA Endevor® SCM copies the load modules and component
lists, but prints the listings, instead of copying them to the target stage.
If ACM is not installed, or if you do not wish to copy component lists to the target stage, you can
override the MONITOR symbol with any value except components.
04-May-2018 399/1109
CA Endevor® SCM - 17.0
//**********************************************************************
//BSTCOPY EXEC PGM=BSTCOPY,MAXRC=04,COND=(0,LT)
//SYSPRINT DD DSN=&©1LST,DISP=OLD
//SYSUT3 DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1))
//SYSUT4 DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1))
//INDD DD DSN=&LOADLIB1.,DISP=SHR
//OUTDD DD DSN=&LOADLIB2.,DISP=SHR,MONITOR=&MONITOR.
//SYSIN DD *
COPY O=OUTDD,I=INDD
SELECT MEMBER=((&C1ELEMENT.,,R))
//**********************************************************************
//* COPY THE DBRM MODULE *
//**********************************************************************
//BSTCOPY EXEC PGM=BSTCOPY,MAXRC=04,COND=(4,LT)
//SYSPRINT DD DSN=&©2LST,DISP=OLD
//SYSUT3 DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1))
//SYSUT4 DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1))
//INDD DD DSN=&DBRMLIB1.,DISP=SHR
//OUTDD DD DSN=&DBRMLIB2.,DISP=SHR,MONITOR=&MONITOR.
//SYSIN DD *
COPY O=OUTDD,I=INDD
SELECT MEMBER=((&C1ELEMENT.,,R))
//**********************************************************************
//* MOVE THE COMPONENT LIST *
//**********************************************************************
//*
//*
//**********************************************************************
//* BIND APPLICATION PLAN IF EXECUTING IN FOREGROUND
//* NOTE: ATTEMPTING TO RUN THIS STEP IN BG WILL RESULT IN RC=5
//*********************************************************************
//BINDFG EXEC PGM=BC1PTMP0,MAXRC=5,COND=(4,LT),
// PARM='&PARMLIB(&C1ELEMENT)'.
//STEPLIB DD DSN=&DB2LOADL.,DISP=SHR
//DBRMLIB DD DSN=&DBRMLIB2.,DISP=SHR
//SYSTSPRT DD DSN=&&PARMLIST,DISP=(OLD,PASS)
//SYSUDUMP DD SYSOUT=&SYSOUT.
//*********************************************************************
//* BIND APPLICATION PLAN IF EXECUTING IN BACKGROUND *
//*********************************************************************
//BINDBG EXEC PGM=IKJEFT01,COND=((5,NE,BINDFG),(5,LT)),MAXRC=7
//STEPLIB DD DSN=&DB2LOADL.,DISP=SHR
//DBRMLIB DD DSN=&DBRMLIB2.,DISP=SHR
//SYSTSPRT DD DSN=&&PARMLIST,DISP=(OLD,PASS)
//SYSTSIN DD DSN=&PARMLIB(&C1ELEMENT).,DISP=(OLD,PASS)
//**********************************************************************
//* FOOTPRINT DB2 PLAN *
//**********************************************************************
//FOOTDB2 EXEC PGM=BC1PCAF,COND=(8,LE),MAXRC=0,
// PARM='&DB2SYS.,BC1PSQL1,BC1PDBFP'
//STEPLIB DD DSN=&EDB2AUTH.,DISP=SHR
// DD DSN=&EDB2CONL.,DISP=SHR
//DBRMLIB DD DSN=&DBRMLIB2.,DISP=SHR
//BSTIPT DD DSN=&PARMLIB(&C1ELEMENT).,DISP=(OLD,PASS)
//*******************************************************************
//* COPY THE LISTINGS IF: &LISTING=LISTING. LIBRARY NAME *
//*******************************************************************
//CONLIST EXEC PGM=CONLIST,MAXRC=0,PARM=COPY,COND=EVEN,
// EXECIF=(&LISTLIB.,NE,NO)
//C1LLIBI DD DSN=&LISTLIB1.,DISP=SHR
//C1LLIBO DD DSN=&LISTLIB2.,DISP=SHR,MONITOR=&MONITOR.
//C1BANNER DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171)
//LIST01 DD DSN=&©1LST,DISP=(OLD,DELETE)
//LIST02 DD DSN=&©2LST,DISP=(OLD,DELETE)
//LIST03 DD DSN=&&PARMLIST,DISP=(OLD,DELETE)
//*******************************************************************
//* PRINT THE LISTINGS IF: &LISTING=NO. *
//*******************************************************************
//PRNTLIST EXEC PGM=CONLIST,MAXRC=0,PARM=PRINT,COND=EVEN,
// EXECIF=(&LISTLIB.,EQ,NO)
//C1BANNER DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
04-May-2018 400/1109
CA Endevor® SCM - 17.0
//C1BANNER DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171)
//C1PRINT DD SYSOUT=&SYSOUT.,
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=1330,DSORG=PS)
//LIST01 DD DSN=&©1LST,DISP=(OLD,DELETE)
//LIST02 DD DSN=&©2LST,DISP=(OLD,DELETE)
//LIST03 DD DSN=&&PARMLIST,DISP=(OLD,DELETE)
//MOVECL EXEC PGM=BC1PMVCL,MAXRC=04,COND=(4,LT)
//*
_
04-May-2018 401/1109
CA Endevor® SCM - 17.0
//C1BANNER DD UNIT=&WRKUNIT.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171,DSORG=PS)
//C1PRINT DD SYSOUT=&SYSOUT.,
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=1330,DSORG=PS)
//LIST01 DD DSN=&©LIST,DISP=(OLD,DELETE)
//**********************************************************************
//* UPDATE THE COMPONENT LIST WITH THE NEW OUTPUT COMPONENTS *
//* AND MOVE THE COMPONENT LIST TO THE NEXT STAGE
//**********************************************************************
//MOVECL EXEC PGM=BC1PMVCL,COND=(0,NE)
//*
Other Processors
These processors are provided as an example of how to manage other types of source. Use these
processors as a guide. The following samples are provided in the iprfx.iqual.CSIQSAMP.
ALIASMOV
Moves alias load modules associated with the current element
BINDPLAN
Stand-alone Generate processor for bind cards
CICSMAP
Generate processor for CICS maps and copybooks
EASYTRIE
Generate processor for CA Easytrieve IQ Online Query
GCPYIMP
Ascertains a copybook's impact by executing a list action (using ACMQ) and providing a list of
elements using the copybook
IDEAL01
Sample processor for CA Ideal for CA Datacom
IMSDBD
Sample IMS processor
JCLCHK
Sample processor for Unicenter CA JCLCheck
JOBSCAN
Sample JOBSCAN Processor
SDFIIMAP
Generate Processor for SDF II maps
CSP Processors
This appendix contains examples of Generate processors that use the LEXTRCTR and BC1PCCSP
utilities.
GELCL
04-May-2018 402/1109
CA Endevor® SCM - 17.0
GELCL
GELPCLB
GELTCL
GELPTCLB
04-May-2018 403/1109
CA Endevor® SCM - 17.0
//*
//INITLIST EXEC PGM=BC1PDSIN,MAXRC=0
//C1INIT01 DD DSN=&&EZECOUT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(5,5)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171)
//C1INIT02 DD DSN=&&EZEPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(5,5)),
// DCB=(RECFM=VBA,LRECL=654,BLKSIZE=6000)
//C1INIT03 DD DSN=&&COBPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(30,15)),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)
//C1INIT04 DD DSN=&&CB2PRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(5,5)),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)
//C1INIT05 DD DSN=&&LNKPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(5,5)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=3630)
//*
//COBGEN EXEC PGM=BC1PDCGB,COND=(0,NE),MAXRC=4
//*-----------------------
//* LOADLIB AND MESSAGE FILES
//*-----------------------
//STEPLIB DD DISP=SHR,DSN=&CRS..SELALMD
// DD DISP=SHR,DSN=&CSP..SEZELMD
//* DD DISP=SHR,DSN=EDC.SEDCLINK
//* DD DISP=SHR,DSN=PLI.SIBMLINK
// DD DISP=SHR,DSN=&COBLIB.
// DD DISP=SHR,DSN=&CONLIB.
//*
//EZECOMM DD DISP=SHR,DSN=&CSPVSAM..&NLS..EZECOMM
//*
//*----------------------------------------------------------
//* THE FOLLOWING MESSAGE FILES SHOULD BE PRE-ALLOCATED
//*----------------------------------------------------------
//*EZEDMSG DD DISP=SHR,DSN=&CSPVSAM..FZEMSG
//*EZEEMSG DD DISP=SHR,DSN=&CSPVSAM..&NLS..EZEMSG
//*EZETES DD DISP=SHR,DSN=&CSPVSAM..&NLS..FZETUTOR
//*EZEMAP DD DISP=SHR,DSN=&CSPVSAM..&NLS..FZEMAPDS
//*-----------------------
//* WORK FILES
//*-----------------------
//EZEWORK DD DISP=OLD,DSN=&CSPUSER..EZEWORK
//EZEWRK1 DD UNIT=tdisk,SPACE=(CYL,(2,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3200)
//*-----------------------
//* COMMAND AND LOG FILES
//*-----------------------
//EZECOUT DD DSN=&&EZECOUT,DISP=(OLD,PASS)
//*-----------------------
//* PRINT FILES
//*-----------------------
//EZEPRINT DD DSN=&&EZEPRINT,DISP=(OLD,PASS)
//EZECPRT DD SYSOUT=&SOUT.
//SYSPRINT DD SYSOUT=&SOUT.
//*-----------------------
//* COBOL GENERATION CONTROL FILES
//*-----------------------
//EZEOPT DD DISP=SHR,DSN=&CSPCUST..PDS.EZEOPT
//*EZEOPT DD DISP=SHR,DSN=&CSPVSAM..VSAM.EZEOPT
//EZEJTMP DD DISP=SHR,DSN=&CSPCUST..EZESAMP
//EZEWORD DD DISP=SHR,DSN=&CSPCUST..EZESAMP(EZEWORDS)
//EZESNAP DD SYSOUT=&SOUT.
//*-----------------------
//* INTERNAL READER FILE FOR PREPARATION JCL SUBMISSION
//*-----------------------
//EZEJCL DD DSN=&&EZEJCL,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160)
//*-----------------------
//*-----------------------
//* ENVIRONMENT DEPENDENT CONTROL AND OUTPUT FILES
//*
04-May-2018 404/1109
CA Endevor® SCM - 17.0
//*
//* THE FOLLOWING FILES MAY OR MAY NOT BE REQUIRED, DEPENDING
//* ON FUNCTIONS USED AT SPECIFIC INSTALLATIONS. THE DD CARDS
//* ARE SHOWN AS COMMENTS IN THE PROCEDURE. THE GENERATOR USES
//* DYNAMIC ALLOCATION TO ALLOCATE EXISTING DATA SETS WITH THE
//* NAMES AS SHOWN IN THE DD CARDS, WHERE &CGHLQ. IS THE DATA SET
//* QUALIFIER FROM THE USERID COBOL GENERATION OPTION AND &ENV.
//* IS THE TARGET EXECUTION ENVIRONMENT.
//*
//* TO USE DATA SETS WITH OTHER NAMES, MODIFY THE PROCEDURE OR THE
//* JCL TO ALLOCATE THE DATA SETS WITH THE APPROPRIATE DD NAMES
//* AS SHOWN BELOW. THE GENERATOR CHECKS TO SEE IF A DATA SET
//* HAS ALREADY BEEN ALLOCATED TO THE DD NAME BEFORE ATTEMPTING TO
//* DYNAMICALLY ALLOCATE A DATA SET WITH THE STANDARD NAME.
//*
//*-----------------------
//* COBOL SOURCE FILE
//*-----------------------
//EZESRC DD DISP=(NEW,PASS),DSN=&&EZESRC,
// UNIT=tdisk,SPACE=(CYL,(5,5,10),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160)
//*
//EZEDUMMY DD DUMMY,DISP=SHR,DSN=&CGHLQ..&ENV..EZEDUMMY
//*-----------------------
//*-----------------------
//* USER DEFINED LINK EDIT CONTROL STATEMENTS
//*-----------------------
//EZELINK DD DUMMY
//*-----------------------
//* USER DEFINED BIND CONTROL STATEMENTS
//*-----------------------
//EZEBIND DD DUMMY
//*--------------------------
//* IMS COBOL COPY LIBRARY
//*--------------------------
//*EZECOPY DD DISP=SHR,DSM=&CGHLQ..&ENV..EZECOPY
//*-----------------------
//* OBJECT LIBRARIES FOR GENERATED MAP GROUPS
//*-----------------------
//EZEFOBJ DD DISP=(NEW,PASS),DSN=&&EZEFOBJ,
// UNIT=tdisk,SPACE=(TRK,(5,5,1),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//*EZEPOBJ DD DISP=SHR,DSN=&CGHLQ..&ENV..EZEPOBJ
//*-----------------------
//* TSO CLIST LIBRARY
//*-----------------------
//EZECLST DD DISP=SHR,DSN=NULLFILE
//*-----------------------
//* PARTS LIST LIBRARY
//*-----------------------
//EZEPCTL DD DISP=SHR,DSN=NULLFILE
//*-----------------------
//* MFS SOURCE LIBRARY
//*-----------------------
//*EZEMFS DD DISP=SHR,DSN=&CGHLQ..&ENV..EZEMFS
//*-----------------------
//* JCL LIBRARIES
//*-----------------------
//*EZEJCLX DD DISP=SHR,DSN=&CGHLQ..&ENV..EZEJCLX
//*EZEJCLP DD DISP=SHR,DSN=&CGHLQ..&ENV..EZEJCLP
//USR1MSL DD DISP=SHR,DSN=&USR1MSL.
//USR2MSL DD DISP=SHR,DSN=&USR2MSL.
//NDVRIPT DD *
M=USR1MSL ROMSL=USR2MSL CMDIN=EZECIN CMDOUT=EZECOUT
//EZECIN DD *
GENERATE MEMBER(&C1ELEMENT). SYSTEM(&ENV).
TABLES(&TABLE). MAPS(&MAP). BATCH(NO) ;
//EZEPARM DD UNIT=tdisk,SPACE=(TRK,1),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=80)
//*
//**********************************************************************
//* EXTRACT THE LINKAGE-EDITOR CONTROL STATEMENTS FROM
04-May-2018 405/1109
CA Endevor® SCM - 17.0
//* EXTRACT THE LINKAGE-EDITOR CONTROL STATEMENTS FROM
//* THE SEQUENTIAL FILE CREATED BY THE GENERATE STEP
//**********************************************************************
//*
//EXTRLNK EXEC PGM=LEXTRCTR,COND=(5,LT),MAXRC=0
//STEPLIB DD DISP=SHR,DSN=&CONLIB.
//INPUT DD DSN=&&EZEJCL,DISP=(OLD,PASS)
//OUTPUT DD DSN=&&CONTROL,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//*
//**********************************************************************
//** ELACL - COBOL COMPILE AND LINK-EDIT
//**********************************************************************
//*
//*
//**********************************************************************
//* COMPILE THE COBOL PROGRAM
//**********************************************************************
//*
//C EXEC PGM=IGYCRCTL,COND=(4,LT),MAXRC=4,
// PARM=(NOSEQ,QUOTE,OFFSET,LIB,RES,RENT,NODYNAM,DBCS,OPT,
// 'TRUNC(BIN)','NUMPROC(NOPFD)',NOCMPR2,'DATA(&DATA)').
//STEPLIB DD DISP=SHR,DSN=&COBCOMP.
//SYSIN DD DISP=(OLD,PASS),DSN=&&EZESRC(&C1ELEMENT)
//SYSLIB DD DISP=SHR,DSN=&CRS..SELACOPY,MONITOR=COMPONENTS
//SYSLIN DD DISP=(NEW,PASS),DSN=&&LOADSET(&C1ELEMENT),
// UNIT=tdisk,SPACE=(800,(&WSPC.,&WSPC.,10)),
// FOOTPRNT=CREATE,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//SYSPRINT DD DSN=&&COBPRINT,DISP=(OLD,PASS)
//SYSUT1 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT2 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT3 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT4 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT5 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT6 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT7 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//*
//**********************************************************************
//* COMPILE ANY ADDITIONAL MAPS AND TABLES *
//**********************************************************************
//*
//C2 EXEC PGM=BC1PCCSP,COND=(4,LT),MAXRC=4,
// PARM=(NOSEQ,QUOTE,OFFSET,LIB,RES,RENT,NODYNAM,DBCS,OPT,
// 'TRUNC(BIN)','NUMPROC(NOPFD)',NOCMPR2,'DATA(&DATA)').
//COBCOMP DD DISP=SHR,DSN=&COBCOMP.
//SYSLIB DD DISP=SHR,DSN=&CRS..SELACOPY,MONITOR=COMPONENTS
//SYSIN DD UNIT=tdisk,SPACE=(6400,(&WSPC.,&WSPC)).,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6400)
//SYSLIN DD UNIT=tdisk,SPACE=(3120,(&WSPC.,&WSPC)).,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//SYSPRINT DD UNIT=tdisk,SPACE=(3630,(&WSPC.,&WSPC)).,
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)
//GENCNTL DD DISP=(OLD,PASS),DSN=&&CONTROL
//EZESRC DD DISP=(OLD,PASS),DSN=&&EZESRC
//OBJLIB DD DISP=(OLD,PASS),DSN=&&LOADSET
//PRINTLIB DD DISP=(OLD,PASS),DSN=&&CB2PRINT
//GENINFO DD *
ELEMENT=&C1ELEMENT. KEEP THESE CARDS IN ORDER,
COMPILER=IGYCRCTL LEFT JUST WITH NO BLANKS
//SYSUT1 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT2 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT3 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT4 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT5 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT6 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT7 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//*
//**********************************************************************
//* LINK-EDIT THE COBOL PROGRAM AND ANY MAPS/TABLES *
//* IF THE RETURN CODE ON ALL PREVIOUS STEPS IS 4 OR LESS *
04-May-2018 406/1109
CA Endevor® SCM - 17.0
//* IF THE RETURN CODE ON ALL PREVIOUS STEPS IS 4 OR LESS *
//**********************************************************************
//*
//L EXEC PGM=IEWL,COND=(5,LT),MAXRC=0,
// PARM='RENT,REUS,LIST,XREF,MAP,AMODE(31),RMODE(ANY)'
//SYSLIB DD DISP=SHR,DSN=&COBLIB.,MONITOR=COMPONENTS
//* DD DISP=SHR,DSN=&RESLIB.,MONITOR=COMPONENTS
//OBJLIB DD DISP=(OLD,DELETE),DSN=&&LOADSET,MONITOR=COMPONENTS
// DD DISP=(OLD,DELETE),DSN=&&EZEFOBJ,MONITOR=COMPONENTS
//SELALMD DD DISP=SHR,DSN=&CRS..SELALMD,MONITOR=COMPONENTS
//SYSLMOD DD DISP=SHR,DSN=&LOADLIB.,
// FOOTPRNT=CREATE,MONITOR=COMPONENTS
//SYSPRINT DD DSN=&&LNKPRINT,DISP=(OLD,PASS)
//SYSUT1 DD SPACE=(1024,(&WSPC.,&WSPC)).,UNIT=tdisk
//SYSLIN DD DSN=&&CONTROL,DISP=(OLD,DELETE)
//*
//*********************************************************************
//* STORE OUTPUT LISTINGS IN LIST LIBRARY *
//*********************************************************************
//CONLIST EXEC PGM=CONLIST,PARM=STORE,MAXRC=0,COND=EVEN
//C1LLIBO DD DSN=&LISTLIB.,DISP=SHR,MONITOR=COMPONENTS
//C1BANNER DD UNIT=tdisk,SPACE=(TRK,1),
// DCB=(RECFM=FBA,LRECL=121)
//LIST01 DD DSN=&&EZECOUT,DISP=(OLD,DELETE)
//LIST02 DD DSN=&&EZEPRINT,DISP=(OLD,DELETE)
//LIST03 DD DSN=&&EZEJCL,DISP=(OLD,DELETE)
//LIST04 DD DSN=&&COBPRINT,DISP=(OLD,DELETE)
//LIST05 DD DSN=&&CB2PRINT,DISP=(OLD,DELETE)
//LIST06 DD DSN=&&LNKPRINT,DISP=(OLD,DELETE)
//*
04-May-2018 407/1109
CA Endevor® SCM - 17.0
//* CSP = CSP/370AD HIGH LEVEL QUALIFIER
//* CSPVSAM = HIGH LEVEL QUALIFIER FOR VSAM DATA SETS
//* CSPCUST = HIGH LEVEL QUALIFIER FOR CUSTOMIZED LIBRARIES
//* CSPUSER = CSP/370AD USER WORK DATA SET HIGH LEVEL QUALIFIER
//* DATA = COMPILE OPTION FOR PLACING WORKING STORAGE
//* ABOVE 16M LINE
//* DSNEXIT = DB2 DSNEXIT LIBRARY
//* DSNLOAD = DB2 DSNLOAD LIBRARY
//* ENV = COBOL GENERATION USER DATA SET ENVIRONMENT QUALIFIER
//* (SHOULD BE EQUAL TO GENERATION TARGET ENVIRONMENT)
//* MAP = NONE/ALL - FOR APPLICATION, GEN MAPS WITH APPL
//* NLS = NLS CODE (NATIONAL LANGUAGE DATA SET QUALIFIER)
//* RESLIB = IMS RESLIB LIBRARY
//* SOUT = SYSOUT ASSIGNMENT
//* TABLE = NONE/ALL - FOR APPLICATION, GEN TABLES WITH APPL
//* WSPC = PRIMARY AND SECONDARY SPACE ALLOCATION
//*
//* Endevor PARMS: (PARM VALUES SHOULD BE SPECIFIED VIA PROC GROUPS)
//*
//* BINDDSN = 'PERMANENTLY-ALLOCATED' TEMPORARY BIND CNTL CARD LIB
//* CONLIB = Endevor RUN TIME LIBRARY
//* DBRMLIB = DB2 DBRMLIB LIBRARY
//* LISTLIB = Endevor/CSP LISTINGS LIBRARY
//* LOADLIB = Endevor/CSP OUTPUT LOAD LIBRARY
//* USR1MSL = READ/WRITE MSL
//* USR2MSL = READ-ONLY MSL
//*
//*********************************************************************
//* INITIALIZE GENERATE/COMPILE/LINK-EDIT LISTING DATA SETS *
//*********************************************************************
//*
//INITLIST EXEC PGM=BC1PDSIN,MAXRC=0
//C1INIT01 DD DSN=&&EZECOUT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(5,5)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171)
//C1INIT02 DD DSN=&&EZEPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(5,5)),
// DCB=(RECFM=VBA,LRECL=654,BLKSIZE=6000)
//C1INIT03 DD DSN=&&PRPPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(15,5)),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)
//C1INIT04 DD DSN=&&COBPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(15,5)),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)
//C1INIT05 DD DSN=&&CB2PRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(15,5)),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)
//C1INIT06 DD DSN=&&LNKPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(5,5)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=3630)
//C1INIT07 DD DSN=&&BNDPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(5,2)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171)
//*********************************************************************
//* INVOKE IDCAMS TO ENSURE THE BIND CNTL CARD O/P DATA SET IS DELETED*
//*********************************************************************
//IDCAMS EXEC PGM=IDCAMS
//SYSPRINT DD DUMMY
//SYSIN DD *
DELETE '&BINDDSN'.
SET MAXCC = 0
//COBGEN EXEC PGM=BC1PDCGB,COND=(0,NE),MAXRC=4
//*-----------------------
//* LOADLIB AND MESSAGE FILES
//*-----------------------
//STEPLIB DD DISP=SHR,DSN=&CRS..SELALMD
// DD DISP=SHR,DSN=&CSP..SEZELMD
//* DD DISP=SHR,DSN=EDC.SEDCLINK
//* DD DISP=SHR,DSN=PLI.SIBMLINK
// DD DISP=SHR,DSN=&COBLIB.
// DD DISP=SHR,DSN=&CONLIB.
//*
04-May-2018 408/1109
CA Endevor® SCM - 17.0
//*
//EZECOMM DD DISP=SHR,DSN=&CSPVSAM..&NLS..EZECOMM
//*
//*----------------------------------------------------------
//* THE FOLLOWING MESSAGE FILES SHOULD BE PRE-ALLOCATED
//*----------------------------------------------------------
//*EZEDMSG DD DISP=SHR,DSN=&CSPVSAM..FZEMSG
//*EZEEMSG DD DISP=SHR,DSN=&CSPVSAM..&NLS..EZEMSG
//*EZETES DD DISP=SHR,DSN=&CSPVSAM..&NLS..FZETUTOR
//*EZEMAP DD DISP=SHR,DSN=&CSPVSAM..&NLS..FZEMAPDS
//*-----------------------
//* WORK FILES
//*-----------------------
//EZEWORK DD DISP=OLD,DSN=&CSPUSER..EZEWORK
//EZEWRK1 DD UNIT=tdisk,SPACE=(CYL,(2,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3200)
//*-----------------------
//* COMMAND AND LOG FILES
//*-----------------------
//EZECOUT DD DSN=&&EZECOUT,DISP=(OLD,PASS)
//*-----------------------
//* PRINT FILES
//*-----------------------
//EZEPRINT DD DSN=&&EZEPRINT,DISP=(OLD,PASS)
//EZECPRT DD SYSOUT=&SOUT.
//SYSPRINT DD SYSOUT=&SOUT.
//*-----------------------
//* COBOL GENERATION CONTROL FILES
//*-----------------------
//EZEOPT DD DISP=SHR,DSN=&CSPCUST..PDS.EZEOPT
//*EZEOPT DD DISP=SHR,DSN=&CSPVSAM..VSAM.EZEOPT
//EZEJTMP DD DISP=SHR,DSN=&CSPCUST..EZESAMP
//EZEWORD DD DISP=SHR,DSN=&CSPCUST..EZESAMP(EZEWORDS)
//EZESNAP DD SYSOUT=&SOUT.
//*-----------------------
//* INTERNAL READER FILE FOR PREPARATION JCL SUBMISSION
//*-----------------------
//EZEJCL DD DSN=&&EZEJCL,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160)
//*EZEJCL DD SYSOUT=(,INTRDR)
//*-----------------------
//*-----------------------
//* ENVIRONMENT DEPENDENT CONTROL AND OUTPUT FILES
//*
//* THE FOLLOWING FILES MAY OR MAY NOT BE REQUIRED, DEPENDING
//* ON FUNCTIONS USED AT SPECIFIC INSTALLATIONS. THE DD CARDS
//* ARE SHOWN AS COMMENTS IN THE PROCEDURE. THE GENERATOR USES
//* DYNAMIC ALLOCATION TO ALLOCATE EXISTING DATA SETS WITH THE
//* NAMES AS SHOWN IN THE DD CARDS, WHERE &CGHLQ. IS THE DATA SET
//* QUALIFIER FROM THE USERID COBOL GENERATION OPTION AND &ENV.
//* IS THE TARGET EXECUTION ENVIRONMENT.
//*
//* TO USE DATA SETS WITH OTHER NAMES, MODIFY THE PROCEDURE OR THE
//* JCL TO ALLOCATE THE DATA SETS WITH THE APPROPRIATE DD NAMES
//* AS SHOWN BELOW. THE GENERATOR CHECKS TO SEE IF A DATA SET
//* HAS ALREADY BEEN ALLOCATED TO THE DD NAME BEFORE ATTEMPTING TO
//* DYNAMICALLY ALLOCATE A DATA SET WITH THE STANDARD NAME.
//*
//*-----------------------
//* COBOL SOURCE FILE
//*-----------------------
//EZESRC DD DISP=(NEW,PASS),DSN=&&EZESRC,
// UNIT=tdisk,SPACE=(CYL,(5,5,10),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160)
//*
//EZEDUMMY DD DUMMY,DISP=SHR,DSN=&CGHLQ..&ENV..EZEDUMMY
//*-----------------------
//*-----------------------
//* USER DEFINED LINK EDIT CONTROL STATEMENTS
//*-----------------------
//EZELINK DD DUMMY
04-May-2018 409/1109
CA Endevor® SCM - 17.0
//EZELINK DD DUMMY
//*-----------------------
//* USER-DEFINED BIND CONTROL STATEMENTS
//*-----------------------
//EZEBIND DD DSN=&BINDDSN.,DISP=(,CATLG,DELETE),
// UNIT=tdisk,SPACE=(TRK,(1,1,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//*--------------------------
//* IMS COBOL COPY LIBRARY
//*--------------------------
//*EZECOPY DD DISP=SHR,DSM=&CGHLQ..&ENV..EZECOPY
//*-----------------------
//* OBJECT LIBRARIES FOR GENERATED MAP GROUPS
//*-----------------------
//EZEFOBJ DD DISP=(NEW,PASS),DSN=&&EZEFOBJ,
// UNIT=tdisk,SPACE=(TRK,(5,5,1),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//*EZEPOBJ DD DISP=SHR,DSN=&CGHLQ..&ENV..EZEPOBJ
//*-----------------------
//* TSO CLIST LIBRARY
//*-----------------------
//EZECLST DD DISP=SHR,DSN=NULLFILE
//*-----------------------
//* PARTS LIST LIBRARY
//*-----------------------
//EZEPCTL DD DISP=SHR,DSN=NULLFILE
//*-----------------------
//* MFS SOURCE LIBRARY
//*-----------------------
//*EZEMFS DD DISP=SHR,DSN=&CGHLQ..&ENV..EZEMFS
//*-----------------------
//* JCL LIBRARIES
//*-----------------------
//*EZEJCLX DD DISP=SHR,DSN=&CGHLQ..&ENV..EZEJCLX
//*EZEJCLP DD DISP=SHR,DSN=&CGHLQ..&ENV..EZEJCLP
//USR1MSL DD DISP=SHR,DSN=&USR1MSL.
//USR2MSL DD DISP=SHR,DSN=&USR2MSL.
//NDVRIPT DD *
M=USR1MSL ROMSL=USR2MSL CMDIN=EZECIN CMDOUT=EZECOUT
//EZECIN DD *
GENERATE MEMBER(&C1ELEMENT). SYSTEM(&ENV).
TABLES(&TABLE). MAPS(&MAP). BATCH(NO) ;
//EZEPARM DD UNIT=tdisk,SPACE=(TRK,1),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=80)
//*
//**********************************************************************
//* EXTRACT THE LINKAGE-EDITOR CONTROL STATEMENTS FROM **
//* THE SEQUENTIAL FILE CREATED BY THE GENERATE STEP **
//**********************************************************************
//*
//EXTRLNK EXEC PGM=LEXTRCTR,COND=(5,LT),MAXRC=0
//STEPLIB DD DISP=SHR,DSN=&CONLIB.
//INPUT DD DSN=&&EZEJCL,DISP=(OLD,PASS)
//OUTPUT DD DSN=&&CONTROL,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//**********************************************************************
//** ELAPCLB - COBOL PRECOMPILE/COMPILE AND LINK-EDIT **
//**********************************************************************
//*
//*****************************************************************
//* PRECOMPILE THE COBOL PROGRAM **
//*****************************************************************
//*
//P EXEC PGM=DSNHPC,MAXRC=4,
// PARM=('HOST(COB2),APOSTSQL,QUOTE')
//STEPLIB DD DISP=SHR,DSN=&DSNEXIT.
// DD DISP=SHR,DSN=&DSNLOAD.
//DBRMLIB DD DISP=OLD,DSN=&DBRMLIB.(&C1ELEMENT).
//SYSCIN DD DISP=(NEW,PASS),DSN=&&DSNHOUT,UNIT=tdisk,
// SPACE=(800,(&WSPC.,&WSPC)).
//SYSLIB DD DISP=SHR,DSN=&CRS..SELACOPY,MONITOR=COMPONENTS
04-May-2018 410/1109
CA Endevor® SCM - 17.0
//SYSLIB DD DISP=SHR,DSN=&CRS..SELACOPY,MONITOR=COMPONENTS
//SYSPRINT DD DSN=&&PRPPRINT,DISP=(OLD,PASS)
//SYSUT1 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT2 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSIN DD DISP=(OLD,PASS),DSN=&&EZESRC(&C1ELEMENT)
//*
//*
//**********************************************************************
//* COMPILE THE COBOL PROGRAM **
//**********************************************************************
//*
//C EXEC PGM=IGYCRCTL,COND=(4,LT),MAXRC=4,
// PARM=(NOSEQ,QUOTE,OFFSET,LIB,RES,RENT,NODYNAM,DBCS,OPT,
// 'TRUNC(BIN)','NUMPROC(NOPFD)',NOCMPR2,'DATA(&DATA)').
//STEPLIB DD DISP=SHR,DSN=&COBCOMP.
//SYSIN DD DISP=(OLD,DELETE),DSN=&&DSNHOUT
//SYSLIB DD DISP=SHR,DSN=&CRS..SELACOPY,MONITOR=COMPONENTS
//SYSLIN DD DISP=(NEW,PASS),DSN=&&LOADSET(&C1ELEMENT),UNIT=tdisk,
// SPACE=(800,(&WSPC.,&WSPC.,10)),FOOTPRNT=CREATE,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//SYSPRINT DD DSN=&&COBPRINT,DISP=(OLD,PASS)
//SYSUT1 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT2 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT3 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT4 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT5 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT6 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT7 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//*
//**********************************************************************
//* COMPILE ANY ADDITIONAL MAPS AND TABLES **
//**********************************************************************
//*
//C2 EXEC PGM=BC1PCCSP,COND=(4,LT),MAXRC=4,
// PARM=(NOSEQ,QUOTE,OFFSET,LIB,RES,RENT,NODYNAM,DBCS,OPT,
// 'TRUNC(BIN)','NUMPROC(NOPFD)',NOCMPR2,'DATA(&DATA)').
//COBCOMP DD DISP=SHR,DSN=&COBCOMP.
//SYSLIB DD DISP=SHR,DSN=&CRS..SELACOPY,MONITOR=COMPONENTS
//SYSIN DD UNIT=tdisk,SPACE=(6400,(&WSPC.,&WSPC)).,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6400)
//SYSLIN DD UNIT=tdisk,SPACE=(3120,(&WSPC.,&WSPC)).,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//SYSPRINT DD UNIT=tdisk,SPACE=(3630,(&WSPC.,&WSPC)).,
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)
//GENCNTL DD DISP=(OLD,PASS),DSN=&&CONTROL
//EZESRC DD DISP=(OLD,PASS),DSN=&&EZESRC
//OBJLIB DD DISP=(OLD,PASS),DSN=&&LOADSET
//PRINTLIB DD DISP=(OLD,PASS),DSN=&&CB2PRINT
//GENINFO DD *
ELEMENT=&C1ELEMENT. KEEP THESE CARDS IN ORDER,
COMPILER=IGYCRCTL LEFT JUST WITH NO BLANKS
//SYSUT1 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT2 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT3 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT4 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT5 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT6 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT7 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//*
//**********************************************************************
//* LINK-EDIT THE COBOL PROGRAM **
//* IF THE RETURN CODE ON ALL PREVIOUS STEPS IS 4 OR LESS **
//**********************************************************************
//*
//L EXEC PGM=IEWL,COND=(5,LT),MAXRC=0,
// PARM='RENT,REUS,LIST,XREF,MAP,AMODE(31),RMODE(ANY)'
//SYSLIB DD DISP=SHR,DSN=&COBLIB.,MONITOR=COMPONENTS
//* DD DISP=SHR,DSN=&RESLIB.,MONITOR=COMPONENTS
// DD DISP=SHR,DSN=&DSNLOAD.,MONITOR=COMPONENTS
//OBJLIB DD DISP=(OLD,DELETE),DSN=&&LOADSET,MONITOR=COMPONENTS
// DD DISP=(OLD,DELETE),DSN=&&EZEFOBJ,MONITOR=COMPONENTS
//SELALMD DD DISP=SHR,DSN=&CRS..SELALMD,MONITOR=COMPONENTS
04-May-2018 411/1109
CA Endevor® SCM - 17.0
//SELALMD DD DISP=SHR,DSN=&CRS..SELALMD,MONITOR=COMPONENTS
//SYSLMOD DD DISP=SHR,DSN=&LOADLIB.,
// FOOTPRNT=CREATE,MONITOR=COMPONENTS
//SYSPRINT DD DSN=&&LNKPRINT,DISP=(OLD,PASS)
//SYSUT1 DD SPACE=(1024,(&WSPC.,&WSPC)).,UNIT=tdisk
//SYSLIN DD DSN=&&CONTROL,DISP=(OLD,DELETE)
//*
//**********************************************************************
//* BIND APPLICATION PLAN IN FOREGROUND **
//* NOTE: ATTEMPTING TO RUN THIS STEP IN BG WILL RESULT IN RC=5 **
//**********************************************************************
//BINDFG EXEC PGM=BC1PTMP0,COND=(8,LT),MAXRC=5,
// PARM='&BINDDSN(&C1ELEMENT)'.
//STEPLIB DD DISP=SHR,DSN=&DSNLOAD.
//DBRMLIB DD DISP=SHR,DSN=&DBRMLIB.,MONITOR=COMPONENTS
// DD DISP=SHR,DSN=&CRS..SELADBRM,MONITOR=COMPONENTS
//SYSTSPRT DD DISP=(OLD,PASS),DSN=&&BNDPRINT
//**********************************************************************
//* BIND APPLICATION PLAN IN BACKGROUND *
//**********************************************************************
//BINDBG EXEC PGM=IKJEFT01,COND=((8,LT),(5,NE,BINDFG)),MAXRC=0
//STEPLIB DD DISP=SHR,DSN=&DSNLOAD.
//SYSTSIN DD DISP=SHR,DSN=&BINDDSN.(&C1ELEMENT).
//DBRMLIB DD DISP=SHR,DSN=&DBRMLIB.,MONITOR=COMPONENTS
// DD DISP=SHR,DSN=&CRS..SELADBRM,MONITOR=COMPONENTS
//SYSTSPRT DD DISP=(OLD,PASS),DSN=&&BNDPRINT
//**********************************************************************
//* FOOTPRINT DB2 PLAN *
//**********************************************************************
//FOOTDB2 EXEC PGM=BC1PCAF,COND=(8,LT),MAXRC=0,
// PARM='DB2T,BC1PSQL1,BC1PDBFP'
//STEPLIB DD DISP=SHR,DSN=&DSNLOAD.
//DBRMLIB DD DISP=SHR,DSN=&DBRMLIB.
// DD DISP=SHR,DSN=&CRS..SELADBRM
//BSTIPT DD DISP=SHR,DSN=&BINDDSN.(&C1ELEMENT).
//*********************************************************************
//* INVOKE IDCAMS TO ENSURE THE BIND CNTL CARD O/P DATA SET IS DELETED*
//*********************************************************************
//IDCAMS EXEC PGM=IDCAMS
//SYSPRINT DD DUMMY
//SYSIN DD *
DELETE '&BINDDSN'.
SET MAXCC = 0
//*********************************************************************
//* STORE OUTPUT LISTINGS IN LIST LIBRARY *
//*********************************************************************
//CONLIST EXEC PGM=CONLIST,PARM=STORE,MAXRC=0,COND=EVEN
//C1LLIBO DD DSN=&LISTLIB.,DISP=SHR,MONITOR=COMPONENTS
//C1BANNER DD UNIT=tdisk,SPACE=(TRK,1),
// DCB=(RECFM=FBA,LRECL=121)
//LIST01 DD DSN=&&EZECOUT,DISP=(OLD,DELETE)
//LIST02 DD DSN=&&EZEPRINT,DISP=(OLD,DELETE)
//LIST03 DD DSN=&&EZEJCL,DISP=(OLD,DELETE)
//LIST04 DD DSN=&&PRPPRINT,DISP=(OLD,DELETE)
//LIST05 DD DSN=&&COBPRINT,DISP=(OLD,DELETE)
//LIST06 DD DSN=&&CB2PRINT,DISP=(OLD,DELETE)
//LIST07 DD DSN=&&LNKPRINT,DISP=(OLD,DELETE)
//LIST08 DD DSN=&&BNDPRINT,DISP=(OLD,DELETE)
//*
04-May-2018 412/1109
CA Endevor® SCM - 17.0
// CRS='CRS210',
// CSP='CSP410',
// CSPVSAM='CSP410',
// CSPCUST='CSP410',
// CSPUSER='CSPUSER',
// DATA='31',
// DBCS=,
// DFHLOAD='SYS5.CICS212.LOADLIB',
// ENV='MVSCICS',
// LISTLIB=NULLFILE,
// LOADLIB=NULLFILE,
// MAP='NONE',
// NLS='ENU',
// RESLIB='IMSVS.RESLIB', (UNCOMMENT BELOW IF NECESSARY)
// SOUT='*',
// SP=,
// SUFF=1$,
// TABLE='NONE',
// USR1MSL=NULLFILE,
// USR2MSL=NULLFILE,
// WSPC=500
//*
//*
//* CSP PARMS: (PARM VALUES SHOULD BE SPECIFIED VIA PROC GROUPS)
//*
//* CGHLQ = COBOL GENERATION USER DATA SET HIGH-LEVEL QUALIFIER
//* COBCICS = COBOL CICS RUN TIME LIBRARY
//* COBCOMP = COBOL COMPILER LIBRARY
//* COBLIB = COBOL RUN TIME LIBRARY
//* CRS = CSP/370RS HIGH LEVEL QUALIFIER
//* CSP = CSP/370AD HIGH LEVEL QUALIFIER
//* CSPVSAM = HIGH LEVEL QUALIFIER FOR VSAM DATA SETS
//* CSPCUST = HIGH LEVEL QUALIFIER FOR CUSTOMIZED LIBRARIES
//* CSPUSER = CSP/370AD USER WORK DATA SET HIGH LEVEL QUALIFIER
//* DATA = COMPILE OPTION FOR PLACING WORKING STORAGE
//* ABOVE 16M LINE
//* DBCS = DOUBLE BYTE CHARACTER SUPPORT
//* DFHLOAD = CICS TRANSLATOR LIBRARY
//* ENV = COBOL GENERATION USER DATA SET ENVIRONMENT QUALIFIER
//* (SHOULD BE EQUAL TO GENERATION TARGET ENVIRONMENT)
//* MAP = NONE/ALL - FOR APPLICATION, GEN MAPS WITH APPL
//* NLS = NLS CODE (NATIONAL LANGUAGE DATA SET QUALIFIER)
//* RESLIB = IMS RESLIB LIBRARY
//* SOUT = SYSOUT ASSIGNMENT
//* SP = CICS/ESA SYSTEM PROGRAMMING TRANSLATOR OPTION
//* SUFF = CICS TRANSLATOR PROGRAM NAME SUFFIX
//* TABLE = NONE/ALL - FOR APPLICATION, GEN TABLES WITH APPL
//* WSPC = PRIMARY AND SECONDARY SPACE ALLOCATION
//*
//* Endevor PARMS: (PARM VALUES SHOULD BE SPECIFIED VIA PROC GROUPS)
//* CONLIB = Endevor RUN TIME LIBRARY
//* LISTLIB = Endevor/CSP LISTINGS LIBRARY
//* LOADLIB = Endevor/CSP OUTPUT LOAD LIBRARY
//* USR1MSL = READ/WRITE MSL
//* USR2MSL = READ-ONLY MSL
//*
//*********************************************************************
//* INITIALIZE GENERATE/COMPILE/LINK-EDIT LISTING DATA SETS *
//*********************************************************************
//*
//INITLIST EXEC PGM=BC1PDSIN,MAXRC=0
//C1INIT01 DD DSN=&&EZECOUT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(5,5)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171)
//C1INIT02 DD DSN=&&EZEPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(5,5)),
// DCB=(RECFM=VBA,LRECL=654,BLKSIZE=6000)
//C1INIT02 DD DSN=&&TRNPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(15,5)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171)
//C1INIT04 DD DSN=&&COBPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(15,5)),
04-May-2018 413/1109
CA Endevor® SCM - 17.0
// UNIT=tdisk,SPACE=(TRK,(15,5)),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)
//C1INIT05 DD DSN=&&CB2PRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(15,5)),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)
//C1INIT06 DD DSN=&&LNKPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(5,5)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=3630)
//*
//COBGEN EXEC PGM=BC1PDCGB,COND=(0,NE),MAXRC=4
//*-----------------------
//* LOADLIB AND MESSAGE FILES
//*-----------------------
//STEPLIB DD DISP=SHR,DSN=&CRS..SELALMD
// DD DISP=SHR,DSN=&CSP..SEZELMD
//* DD DISP=SHR,DSN=EDC.SEDCLINK
//* DD DISP=SHR,DSN=PLI.SIBMLINK
// DD DISP=SHR,DSN=&COBLIB.
// DD DISP=SHR,DSN=&CONLIB.
//*
//EZECOMM DD DISP=SHR,DSN=&CSPVSAM..&NLS..EZECOMM
//*
//*----------------------------------------------------------
//* THE FOLLOWING MESSAGE FILES SHOULD BE PRE-ALLOCATED
//*----------------------------------------------------------
//*EZEDMSG DD DISP=SHR,DSN=&CSPVSAM..FZEMSG
//*EZEEMSG DD DISP=SHR,DSN=&CSPVSAM..&NLS..EZEMSG
//*EZETES DD DISP=SHR,DSN=&CSPVSAM..&NLS..FZETUTOR
//*EZEMAP DD DISP=SHR,DSN=&CSPVSAM..&NLS..FZEMAPDS
//*-----------------------
//* WORK FILES
//*-----------------------
//EZEWORK DD DISP=OLD,DSN=&CSPUSER..EZEWORK
//EZEWRK1 DD UNIT=tdisk,SPACE=(CYL,(2,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3200)
//*-----------------------
//* COMMAND AND LOG FILES
//*-----------------------
//EZECOUT DD DSN=&&EZECOUT,DISP=(OLD,PASS)
//*-----------------------
//* PRINT FILES
//*-----------------------
//EZEPRINT DD DSN=&&EZEPRINT,DISP=(OLD,PASS)
//EZECPRT DD SYSOUT=&SOUT.
//SYSPRINT DD SYSOUT=&SOUT.
//*-----------------------
//* COBOL GENERATION CONTROL FILES
//*-----------------------
//EZEOPT DD DISP=SHR,DSN=&CSPCUST..PDS.EZEOPT
//*EZEOPT DD DISP=SHR,DSN=&CSPVSAM..VSAM.EZEOPT
//EZEJTMP DD DISP=SHR,DSN=&CSPCUST..EZESAMP
//EZEWORD DD DISP=SHR,DSN=&CSPCUST..EZESAMP(EZEWORDS)
//EZESNAP DD SYSOUT=&SOUT.
//*-----------------------
//* INTERNAL READER FILE FOR PREPARATION JCL SUBMISSION
//*-----------------------
//EZEJCL DD DSN=&&EZEJCL,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160)
//*EZEJCL DD SYSOUT=(,INTRDR)
//*-----------------------
//*-----------------------
//* ENVIRONMENT DEPENDENT CONTROL AND OUTPUT FILES
//*
//* THE FOLLOWING FILES MAY OR MAY NOT BE REQUIRED, DEPENDING
//* ON FUNCTIONS USED AT SPECIFIC INSTALLATIONS. THE DD CARDS
//* ARE SHOWN AS COMMENTS IN THE PROCEDURE. THE GENERATOR USES
//* DYNAMIC ALLOCATION TO ALLOCATE EXISTING DATA SETS WITH THE
//* NAMES AS SHOWN IN THE DD CARDS, WHERE &CGHLQ. IS THE DATA SET
//* QUALIFIER FROM THE USERID COBOL GENERATION OPTION AND &ENV.
//* IS THE TARGET EXECUTION ENVIRONMENT.
//*
04-May-2018 414/1109
CA Endevor® SCM - 17.0
//*
//* TO USE DATA SETS WITH OTHER NAMES, MODIFY THE PROCEDURE OR THE
//* JCL TO ALLOCATE THE DATA SETS WITH THE APPROPRIATE DD NAMES
//* AS SHOWN BELOW. THE GENERATOR CHECKS TO SEE IF A DATA SET
//* HAS ALREADY BEEN ALLOCATED TO THE DD NAME BEFORE ATTEMPTING TO
//* DYNAMICALLY ALLOCATE A DATA SET WITH THE STANDARD NAME.
//*
//*-----------------------
//* COBOL SOURCE FILE
//*-----------------------
//EZESRC DD DISP=(NEW,PASS),DSN=&&EZESRC,
// UNIT=tdisk,SPACE=(CYL,(5,5,10),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160)
//*
//EZEDUMMY DD DUMMY,DISP=SHR,DSN=&CGHLQ..&ENV..EZEDUMMY
//*-----------------------
//*-----------------------
//* USER DEFINED LINK EDIT CONTROL STATEMENTS
//*-----------------------
//EZELINK DD DUMMY
//*-----------------------
//* USER DEFINED BIND CONTROL STATEMENTS
//*-----------------------
//EZEBIND DD DUMMY
//*--------------------------
//* IMS COBOL COPY LIBRARY
//*--------------------------
//*EZECOPY DD DISP=SHR,DSM=&CGHLQ..&ENV..EZECOPY
//*-----------------------
//* OBJECT LIBRARIES FOR GENERATED MAP GROUPS
//*-----------------------
//EZEFOBJ DD DISP=(NEW,PASS),DSN=&&EZEFOBJ,
// UNIT=tdisk,SPACE=(TRK,(5,5,1),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//*EZEPOBJ DD DISP=SHR,DSN=&CGHLQ..&ENV..EZEPOBJ
//*-----------------------
//* TSO CLIST LIBRARY
//*-----------------------
//EZECLST DD DISP=SHR,DSN=NULLFILE
//*-----------------------
//* PARTS LIST LIBRARY
//*-----------------------
//EZEPCTL DD DISP=SHR,DSN=NULLFILE
//*-----------------------
//* MFS SOURCE LIBRARY
//*-----------------------
//*EZEMFS DD DISP=SHR,DSN=&CGHLQ..&ENV..EZEMFS
//*-----------------------
//* JCL LIBRARIES
//*-----------------------
//*EZEJCLX DD DISP=SHR,DSN=&CGHLQ..&ENV..EZEJCLX
//*EZEJCLP DD DISP=SHR,DSN=&CGHLQ..&ENV..EZEJCLP
//USR1MSL DD DISP=SHR,DSN=&USR1MSL.
//USR2MSL DD DISP=SHR,DSN=&USR2MSL.
//NDVRIPT DD *
M=USR1MSL ROMSL=USR2MSL CMDIN=EZECIN CMDOUT=EZECOUT
//EZECIN DD *
GENERATE MEMBER(&C1ELEMENT). SYSTEM(&ENV).
TABLES(&TABLE). MAPS(&MAP). BATCH(NO) ;
//EZEPARM DD UNIT=tdisk,SPACE=(TRK,1),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=80)
//*
//**********************************************************************
//* EXTRACT THE LINKAGE-EDITOR CONTROL STATEMENTS FROM **
//* THE SEQUENTIAL FILE CREATED BY THE GENERATE STEP **
//**********************************************************************
//*
//EXTRLNK EXEC PGM=LEXTRCTR,COND=(5,LT),MAXRC=0
//STEPLIB DD DISP=SHR,DSN=&CONLIB.
//INPUT DD DSN=&&EZEJCL,DISP=(OLD,PASS)
//OUTPUT DD DSN=&&CONTROL,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(1,1)),
04-May-2018 415/1109
CA Endevor® SCM - 17.0
// UNIT=tdisk,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//*
//**********************************************************************
//** ELATCL - CICS TRANSLATE, COBOL COMPILE AND LINK-EDIT **
//**********************************************************************
//T EXEC PGM=DFHECP&SUFF.,MAXRC=4,
// PARM='COBOL2,QUOTE,NOSEQ&SP&DBCS'.
//STEPLIB DD DISP=SHR,DSN=&DFHLOAD.
//SYSPRINT DD DSN=&&TRNPRINT,DISP=(OLD,PASS)
//SYSPUNCH DD DSN=&&SYSCIN,DISP=(,PASS),
// UNIT=tdisk,SPACE=(800,(&WSPC.,&WSPC)).
//SYSIN DD DSN=&&EZESRC(&C1ELEMENT),DISP=(OLD,PASS)
//*
//**********************************************************************
//* COMPILE THE COBOL PROGRAM **
//**********************************************************************
//*
//C EXEC PGM=IGYCRCTL,COND=(4,LT),MAXRC=4,
// PARM=(NOSEQ,QUOTE,OFFSET,LIB,RES,RENT,NODYNAM,DBCS,OPT,
// 'TRUNC(BIN)','NUMPROC(NOPFD)',NOCMPR2,'DATA(&DATA)').
//STEPLIB DD DISP=SHR,DSN=&COBCOMP.
//SYSIN DD DISP=(OLD,DELETE),DSN=&&SYSCIN
//SYSLIB DD DISP=SHR,DSN=&CRS..SELACOPY,MONITOR=COMPONENTS
//SYSLIN DD DISP=(NEW,PASS),DSN=&&LOADSET(&C1ELEMENT),UNIT=tdisk,
// SPACE=(800,(&WSPC.,&WSPC.,10)),FOOTPRNT=CREATE,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//SYSPRINT DD DSN=&&COBPRINT,DISP=(OLD,PASS)
//SYSUT1 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT2 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT3 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT4 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT5 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT6 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT7 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//*
//**********************************************************************
//* COMPILE ANY ADDITIONAL MAPS AND TABLES **
//**********************************************************************
//*
//C2 EXEC PGM=BC1PCCSP,COND=(4,LT),MAXRC=4,
// PARM=(NOSEQ,QUOTE,OFFSET,LIB,RES,RENT,NODYNAM,DBCS,OPT,
// 'TRUNC(BIN)','NUMPROC(NOPFD)',NOCMPR2,'DATA(&DATA)').
//COBCOMP DD DISP=SHR,DSN=&COBCOMP.
//SYSLIB DD DISP=SHR,DSN=&CRS..SELACOPY,MONITOR=COMPONENTS
//SYSIN DD UNIT=tdisk,SPACE=(6400,(&WSPC.,&WSPC)).,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6400)
//SYSLIN DD UNIT=tdisk,SPACE=(3120,(&WSPC.,&WSPC)).,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//SYSPRINT DD UNIT=tdisk,SPACE=(3630,(&WSPC.,&WSPC)).,
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)
//GENCNTL DD DISP=(OLD,PASS),DSN=&&CONTROL
//EZESRC DD DISP=(OLD,PASS),DSN=&&EZESRC
//OBJLIB DD DISP=(OLD,PASS),DSN=&&LOADSET
//PRINTLIB DD DISP=(OLD,PASS),DSN=&&CB2PRINT
//GENINFO DD *
ELEMENT=&C1ELEMENT. KEEP THESE CARDS IN ORDER,
COMPILER=IGYCRCTL LEFT JUST WITH NO BLANKS
//SYSUT1 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT2 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT3 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT4 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT5 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT6 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT7 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//*
//*
//**********************************************************************
//* LINK-EDIT THE COBOL PROGRAM **
//* IF THE RETURN CODE ON ALL PREVIOUS STEPS IS 4 OR LESS **
//**********************************************************************
//*
04-May-2018 416/1109
CA Endevor® SCM - 17.0
//*
//L EXEC PGM=IEWL,COND=(5,LT),MAXRC=0,
// PARM='RENT,REUS,LIST,XREF,MAP,AMODE(31),RMODE(ANY)'
//SYSLIB DD DISP=SHR,DSN=&DFHLOAD.,MONITOR=COMPONENTS
// DD DISP=SHR,DSN=&COBCICS.,MONITOR=COMPONENTS
// DD DISP=SHR,DSN=&COBLIB.,MONITOR=COMPONENTS
//* DD DISP=SHR,DSN=&RESLIB.,MONITOR=COMPONENTS
//OBJLIB DD DISP=(OLD,DELETE),DSN=&&LOADSET,MONITOR=COMPONENTS
// DD DISP=(OLD,DELETE),DSN=&&EZEFOBJ,MONITOR=COMPONENTS
//SELALMD DD DISP=SHR,DSN=&CRS..SELALMD,MONITOR=COMPONENTS
//SYSLMOD DD DISP=SHR,DSN=&LOADLIB.,
// FOOTPRNT=CREATE,MONITOR=COMPONENTS
//SYSPRINT DD DSN=&&LNKPRINT,DISP=(OLD,PASS)
//SYSUT1 DD SPACE=(1024,(&WSPC.,&WSPC)).,UNIT=tdisk
//SYSLIN DD DSN=&&CONTROL,DISP=(OLD,DELETE)
//*********************************************************************
//* STORE OUTPUT LISTINGS IN LIST LIBRARY **
//*********************************************************************
//CONLIST EXEC PGM=CONLIST,PARM=STORE,MAXRC=0,COND=EVEN
//C1LLIBO DD DSN=&LISTLIB.,DISP=SHR,MONITOR=COMPONENTS
//C1BANNER DD UNIT=tdisk,SPACE=(TRK,1),
// DCB=(RECFM=FBA,LRECL=121)
//LIST01 DD DSN=&&EZECOUT,DISP=(OLD,DELETE)
//LIST02 DD DSN=&&EZEPRINT,DISP=(OLD,DELETE)
//LIST03 DD DSN=&&EZEJCL,DISP=(OLD,DELETE)
//LIST04 DD DSN=&&TRNPRINT,DISP=(OLD,DELETE)
//LIST05 DD DSN=&&COBPRINT,DISP=(OLD,DELETE)
//LIST06 DD DSN=&&CB2PRINT,DISP=(OLD,DELETE)
//LIST07 DD DSN=&&LNKPRINT,DISP=(OLD,DELETE)
//*
04-May-2018 417/1109
CA Endevor® SCM - 17.0
//*
//* CGHLQ = COBOL GENERATION USER DATA SET HIGH-LEVEL QUALIFIER
//* COBCICS = COBOL CICS RUN TIME LIBRARY
//* COBCOMP = COBOL COMPILER LIBRARY
//* COBLIB = COBOL RUN TIME LIBRARY
//* CRS = CSP/370RS HIGH LEVEL QUALIFIER
//* CSP = CSP/370AD HIGH LEVEL QUALIFIER
//* CSPVSAM = HIGH LEVEL QUALIFIER FOR VSAM DATA SETS
//* CSPCUST = HIGH LEVEL QUALIFIER FOR CUSTOMIZED LIBRARIES
//* CSPUSER = CSP/370AD USER WORK DATA SET HIGH LEVEL QUALIFIER
//* DATA = COMPILE OPTION FOR PLACING WORKING STORAGE
//* ABOVE 16M LINE
//* DBCS = DOUBLE BYTE CHARACTER SUPPORT
//* DFHLOAD = CICS TRANSLATOR LIBRARY
//* DSNEXIT = DB2 DSNEXIT LIBRARY
//* DSNLOAD = DB2 DSNLOAD LIBRARY
//* ENV = COBOL GENERATION USER DATA SET ENVIRONMENT QUALIFIER
//* (SHOULD BE EQUAL TO GENERATION TARGET ENVIRONMENT)
//* MAP = NONE/ALL - FOR APPLICATION, GEN MAPS WITH APPL
//* NLS = NLS CODE (NATIONAL LANGUAGE DATA SET QUALIFIER)
//* RESLIB = IMS RESLIB LIBRARY
//* SOUT = SYSOUT ASSIGNMENT
//* SP = CICS/ESA SYSTEM PROGRAMMING TRANSLATOR OPTION
//* SUFF = CICS TRANSLATOR PROGRAM NAME SUFFIX
//* TABLE = NONE/ALL - FOR APPLICATION, GEN TABLES WITH APPL
//* WSPC = PRIMARY AND SECONDARY SPACE ALLOCATION
//*
//* Endevor PARMS: (PARM VALUES SHOULD BE SPECIFIED VIA PROC GROUPS)
//* BINDDSN = 'PERMANENTLY-ALLOCATED' TEMPORARY BIND CNTL CARD LIB
//* CONLIB = Endevor RUN TIME LIBRARY
//* DBRMLIB = DB2 DBRMLIB LIBRARY
//* LISTLIB = Endevor/CSP LISTINGS LIBRARY
//* LOADLIB = Endevor/CSP OUTPUT LOAD LIBRARY
//* USR1MSL = READ/WRITE MSL
//* USR2MSL = READ-ONLY MSL
//*
//*
//*********************************************************************
//* INITIALIZE GENERATE/COMPILE/LINK-EDIT LISTING DATA SETS *
//*********************************************************************
//*
//INITLIST EXEC PGM=BC1PDSIN,MAXRC=0
//C1INIT01 DD DSN=&&EZECOUT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(5,5)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171)
//C1INIT02 DD DSN=&&EZEPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(5,5)),
// DCB=(RECFM=VBA,LRECL=654,BLKSIZE=6000)
//C1INIT03 DD DSN=&&PRPPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(15,5)),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)
//C1INIT04 DD DSN=&&TRNPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(15,5)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171)
//C1INIT05 DD DSN=&&COBPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(15,5)),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)
//C1INIT06 DD DSN=&&CB2PRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(15,5)),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)
//C1INIT07 DD DSN=&&LNKPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(5,5)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=3630)
//C1INIT08 DD DSN=&&BNDPRINT,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(5,2)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171)
//*********************************************************************
//* INVOKE IDCAMS TO ENSURE THE BIND CNTL CARD O/P DATA SET IS DELETED*
//*********************************************************************
//IDCAMS EXEC PGM=IDCAMS
//SYSPRINT DD DUMMY
04-May-2018 418/1109
CA Endevor® SCM - 17.0
//SYSPRINT DD DUMMY
//SYSIN DD *
DELETE '&BINDDSN'.
SET MAXCC = 0
//COBGEN EXEC PGM=BC1PDCGB,COND=(0,NE),MAXRC=4
//*
//*-----------------------
//* LOADLIB AND MESSAGE FILES
//*-----------------------
//STEPLIB DD DISP=SHR,DSN=&CRS..SELALMD
// DD DISP=SHR,DSN=&CSP..SEZELMD
//* DD DISP=SHR,DSN=EDC.SEDCLINK
//* DD DISP=SHR,DSN=PLI.SIBMLINK
// DD DISP=SHR,DSN=&COBLIB.
// DD DISP=SHR,DSN=&CONLIB.
//*
//EZECOMM DD DISP=SHR,DSN=&CSPVSAM..&NLS..EZECOMM
//*
//*----------------------------------------------------------
//* THE FOLLOWING MESSAGE FILES SHOULD BE PRE-ALLOCATED
//*----------------------------------------------------------
//*EZEDMSG DD DISP=SHR,DSN=&CSPVSAM..FZEMSG
//*EZEEMSG DD DISP=SHR,DSN=&CSPVSAM..&NLS..EZEMSG
//*EZETES DD DISP=SHR,DSN=&CSPVSAM..&NLS..FZETUTOR
//*EZEMAP DD DISP=SHR,DSN=&CSPVSAM..&NLS..FZEMAPDS
//*-----------------------
//* WORK FILES
//*-----------------------
//EZEWORK DD DISP=OLD,DSN=&CSPUSER..EZEWORK
//EZEWRK1 DD UNIT=tdisk,SPACE=(CYL,(2,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3200)
//*-----------------------
//* COMMAND AND LOG FILES
//*-----------------------
//EZECOUT DD DSN=&&EZECOUT,DISP=(OLD,PASS)
//*-----------------------
//* PRINT FILES
//*-----------------------
//EZEPRINT DD DSN=&&EZEPRINT,DISP=(OLD,PASS)
//EZECPRT DD SYSOUT=&SOUT.
//SYSPRINT DD SYSOUT=&SOUT.
//*-----------------------
//* COBOL GENERATION CONTROL FILES
//*-----------------------
//EZEOPT DD DISP=SHR,DSN=&CSPCUST..PDS.EZEOPT
//*EZEOPT DD DISP=SHR,DSN=&CSPVSAM..VSAM.EZEOPT
//EZEJTMP DD DISP=SHR,DSN=&CSPCUST..EZESAMP
//EZEWORD DD DISP=SHR,DSN=&CSPCUST..EZESAMP(EZEWORDS)
//EZESNAP DD SYSOUT=&SOUT.
//*-----------------------
//* INTERNAL READER FILE FOR PREPARATION JCL SUBMISSION
//*-----------------------
//EZEJCL DD DSN=&&EZEJCL,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160)
//*EZEJCL DD SYSOUT=(,INTRDR)
//*-----------------------
//*-----------------------
//* ENVIRONMENT DEPENDENT CONTROL AND OUTPUT FILES
//*
//* THE FOLLOWING FILES MAY OR MAY NOT BE REQUIRED, DEPENDING
//* ON FUNCTIONS USED AT SPECIFIC INSTALLATIONS. THE DD CARDS
//* ARE SHOWN AS COMMENTS IN THE PROCEDURE. THE GENERATOR USES
//* DYNAMIC ALLOCATION TO ALLOCATE EXISTING DATA SETS WITH THE
//* NAMES AS SHOWN IN THE DD CARDS, WHERE &CGHLQ. IS THE DATA SET
//* QUALIFIER FROM THE USERID COBOL GENERATION OPTION AND &ENV.
//* IS THE TARGET EXECUTION ENVIRONMENT.
//*
//* TO USE DATA SETS WITH OTHER NAMES, MODIFY THE PROCEDURE OR THE
//* JCL TO ALLOCATE THE DATA SETS WITH THE APPROPRIATE DD NAMES
//* AS SHOWN BELOW. THE GENERATOR CHECKS TO SEE IF A DATA SET
//* HAS ALREADY BEEN ALLOCATED TO THE DD NAME BEFORE ATTEMPTING TO
04-May-2018 419/1109
CA Endevor® SCM - 17.0
//* HAS ALREADY BEEN ALLOCATED TO THE DD NAME BEFORE ATTEMPTING TO
//* DYNAMICALLY ALLOCATE A DATA SET WITH THE STANDARD NAME.
//*
//*-----------------------
//* COBOL SOURCE FILE
//*-----------------------
//EZESRC DD DISP=(NEW,PASS),DSN=&&EZESRC,
// UNIT=tdisk,SPACE=(CYL,(5,5,10),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160)
//*
//EZEDUMMY DD DUMMY,DISP=SHR,DSN=&CGHLQ..&ENV..EZEDUMMY
//*-----------------------
//*-----------------------
//* USER DEFINED LINK EDIT CONTROL STATEMENTS
//*-----------------------
//EZELINK DD DUMMY
//*-----------------------
//* USER-DEFINED BIND CONTROL STATEMENTS
//*-----------------------
//EZEBIND DD DSN=&BINDDSN.,DISP=(,CATLG,DELETE),
// UNIT=tdisk,SPACE=(TRK,(1,1,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//*--------------------------
//* IMS COBOL COPY LIBRARY
//*--------------------------
//*EZECOPY DD DISP=SHR,DSM=&CGHLQ..&ENV..EZECOPY
//*-----------------------
//* OBJECT LIBRARIES FOR GENERATED MAP GROUPS
//*-----------------------
//EZEFOBJ DD DISP=(NEW,PASS),DSN=&&EZEFOBJ,
// UNIT=tdisk,SPACE=(TRK,(5,5,1),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//*EZEPOBJ DD DISP=SHR,DSN=&CGHLQ..&ENV..EZEPOBJ
//*-----------------------
//* TSO CLIST LIBRARY
//*-----------------------
//EZECLST DD DISP=SHR,DSN=NULLFILE
//*-----------------------
//* PARTS LIST LIBRARY
//*-----------------------
//EZEPCTL DD DISP=SHR,DSN=NULLFILE
//*-----------------------
//* MFS SOURCE LIBRARY
//*-----------------------
//*EZEMFS DD DISP=SHR,DSN=&CGHLQ..&ENV..EZEMFS
//*-----------------------
//* JCL LIBRARIES
//*-----------------------
//*EZEJCLX DD DISP=SHR,DSN=&CGHLQ..&ENV..EZEJCLX
//*EZEJCLP DD DISP=SHR,DSN=&CGHLQ..&ENV..EZEJCLP
//USR1MSL DD DISP=SHR,DSN=&USR1MSL.
//USR2MSL DD DISP=SHR,DSN=&USR2MSL.
//NDVRIPT DD *
M=USR1MSL ROMSL=USR2MSL CMDIN=EZECIN CMDOUT=EZECOUT
//EZECIN DD *
GENERATE MEMBER(&C1ELEMENT). SYSTEM(&ENV).
TABLES(&TABLE). MAPS(&MAP). BATCH(NO) ;
//EZEPARM DD UNIT=tdisk,SPACE=(TRK,1),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=80)
//*
//**********************************************************************
//* EXTRACT THE LINKAGE-EDITOR CONTROL STATEMENTS FROM **
//* THE SEQUENTIAL FILE CREATED BY THE GENERATE STEP **
//**********************************************************************
//*
//EXTRLNK EXEC PGM=LEXTRCTR,COND=(5,LT),MAXRC=0
//STEPLIB DD DISP=SHR,DSN=&CONLIB.
//INPUT DD DSN=&&EZEJCL,DISP=(OLD,PASS)
//OUTPUT DD DSN=&&CONTROL,DISP=(,PASS),
// UNIT=tdisk,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//*
04-May-2018 420/1109
CA Endevor® SCM - 17.0
//*
//**********************************************************************
//** ELAPCLB - COBOL PRECOMPILE/COMPILE AND LINK-EDIT **
//**********************************************************************
//*
//*****************************************************************
//* PRECOMPILE THE COBOL PROGRAM **
//*****************************************************************
//*
//P EXEC PGM=DSNHPC,MAXRC=4,
// PARM=('HOST(COB2),APOSTSQL,QUOTE')
//STEPLIB DD DISP=SHR,DSN=&DSNEXIT.
// DD DISP=SHR,DSN=&DSNLOAD.
//DBRMLIB DD DISP=OLD,DSN=&DBRMLIB.(&C1ELEMENT).
//SYSCIN DD DISP=(NEW,PASS),DSN=&&DSNHOUT,UNIT=tdisk,
// SPACE=(800,(&WSPC.,&WSPC)).
//SYSLIB DD DISP=SHR,DSN=&CRS..SELACOPY,MONITOR=COMPONENTS
//SYSPRINT DD DSN=&&PRPPRINT,DISP=(OLD,PASS)
//SYSUT1 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT2 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSIN DD DISP=(OLD,PASS),DSN=&&EZESRC(&C1ELEMENT)
//*
//**********************************************************************
//** ELATCL - CICS TRANSLATE, COBOL COMPILE AND LINK-EDIT **
//**********************************************************************
//T EXEC PGM=DFHECP&SUFF.,MAXRC=4,
// PARM='COBOL2,QUOTE,NOSEQ&SP&DBCS'.
//STEPLIB DD DISP=SHR,DSN=&DFHLOAD.
//SYSPRINT DD DSN=&&TRNPRINT,DISP=(OLD,PASS)
//SYSPUNCH DD DSN=&&SYSCIN,DISP=(,PASS),
// UNIT=tdisk,SPACE=(800,(&WSPC.,&WSPC)).
//SYSIN DD DSN=&&DSNHOUT,DISP=(OLD,DELETE)
//*
//*
//**********************************************************************
//* COMPILE THE COBOL PROGRAM **
//**********************************************************************
//*
//C EXEC PGM=IGYCRCTL,COND=(4,LT),MAXRC=4,
// PARM=(NOSEQ,QUOTE,OFFSET,LIB,RES,RENT,NODYNAM,DBCS,OPT,
// 'TRUNC(BIN)','NUMPROC(NOPFD)',NOCMPR2,'DATA(&DATA)').
//STEPLIB DD DISP=SHR,DSN=&COBCOMP.
//SYSIN DD DISP=(OLD,DELETE),DSN=&&SYSCIN
//SYSLIB DD DISP=SHR,DSN=&CRS..SELACOPY,MONITOR=COMPONENTS
//SYSLIN DD DISP=(NEW,PASS),DSN=&&LOADSET(&C1ELEMENT),UNIT=tdisk,
// SPACE=(800,(&WSPC.,&WSPC.,10)),FOOTPRNT=CREATE,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//SYSPRINT DD DSN=&&COBPRINT,DISP=(OLD,PASS)
//SYSUT1 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT2 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT3 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT4 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT5 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT6 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT7 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//
* **********************************************************************
//* COMPILE ANY ADDITIONAL MAPS AND TABLES **
//**********************************************************************
//*
//C2 EXEC PGM=BC1PCCSP,COND=(4,LT),MAXRC=4,
// PARM=(NOSEQ,QUOTE,OFFSET,LIB,RES,RENT,NODYNAM,DBCS,OPT,
// 'TRUNC(BIN)','NUMPROC(NOPFD)',NOCMPR2,'DATA(&DATA)').
//COBCOMP DD DISP=SHR,DSN=&COBCOMP.
//SYSLIB DD DISP=SHR,DSN=&CRS..SELACOPY,MONITOR=COMPONENTS
//SYSIN DD UNIT=tdisk,SPACE=(6400,(&WSPC.,&WSPC)).,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6400)
//SYSLIN DD UNIT=tdisk,SPACE=(3120,(&WSPC.,&WSPC)).,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)
//SYSPRINT DD UNIT=tdisk,SPACE=(3630,(&WSPC.,&WSPC)).,
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6251)
//GENCNTL DD DISP=(OLD,PASS),DSN=&&CONTROL
04-May-2018 421/1109
CA Endevor® SCM - 17.0
//GENCNTL DD DISP=(OLD,PASS),DSN=&&CONTROL
//EZESRC DD DISP=(OLD,PASS),DSN=&&EZESRC
//OBJLIB DD DISP=(OLD,PASS),DSN=&&LOADSET
//PRINTLIB DD DISP=(OLD,PASS),DSN=&&CB2PRINT
//GENINFO DD *
ELEMENT=&C1ELEMENT. KEEP THESE CARDS IN ORDER,
COMPILER=IGYCRCTL LEFT JUST WITH NO BLANKS
//SYSUT1 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT2 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT3 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT4 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT5 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT6 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//SYSUT7 DD SPACE=(800,(&WSPC.,&WSPC).,,,ROUND),UNIT=tdisk
//*
//*
//**********************************************************************
//* LINK-EDIT THE COBOL PROGRAM **
//* IF THE RETURN CODE ON ALL PREVIOUS STEPS IS 4 OR LESS **
//**********************************************************************
//*
//L EXEC PGM=IEWL,COND=(5,LT),MAXRC=0,
// PARM='RENT,REUS,LIST,XREF,MAP,AMODE(31),RMODE(ANY)'
//SYSLIB DD DISP=SHR,DSN=&DFHLOAD.,MONITOR=COMPONENTS
// DD DISP=SHR,DSN=&COBCICS.,MONITOR=COMPONENTS
// DD DISP=SHR,DSN=&COBLIB.,MONITOR=COMPONENTS
// DD DISP=SHR,DSN=&DSNLOAD.,MONITOR=COMPONENTS
//* DD DISP=SHR,DSN=&RESLIB.,MONITOR=COMPONENTS
//OBJLIB DD DISP=(OLD,DELETE),DSN=&&LOADSET,MONITOR=COMPONENTS
// DD DISP=(OLD,DELETE),DSN=&&EZEFOBJ,MONITOR=COMPONENTS
//SELALMD DD DISP=SHR,DSN=&CRS..SELALMD,MONITOR=COMPONENTS
//SYSLMOD DD DISP=SHR,DSN=&LOADLIB.,
// FOOTPRNT=CREATE,MONITOR=COMPONENTS
//SYSPRINT DD DSN=&&LNKPRINT,DISP=(OLD,PASS)
//SYSUT1 DD SPACE=(1024,(&WSPC.,&WSPC)).,UNIT=tdisk
//SYSLIN DD DSN=&&CONTROL,DISP=(OLD,DELETE)
//*
//**********************************************************************
//* BIND APPLICATION PLAN IN FOREGROUND **
//* NOTE: ATTEMPTING TO RUN THIS STEP IN BG WILL RESULT IN RC=5 **
//**********************************************************************
//BINDFG EXEC PGM=BC1PTMP0,COND=(8,LT),MAXRC=5,
// PARM='&BINDDSN(&C1ELEMENT)'.
//STEPLIB DD DISP=SHR,DSN=&DSNLOAD.
//DBRMLIB DD DISP=SHR,DSN=&DBRMLIB.,MONITOR=COMPONENTS
// DD DISP=SHR,DSN=&CRS..SELADBRM,MONITOR=COMPONENTS
//SYSTSPRT DD DISP=(OLD,PASS),DSN=&&BNDPRINT
//**********************************************************************
//* BIND APPLICATION PLAN IN BACKGROUND **
//**********************************************************************
//BINDBG EXEC PGM=IKJEFT01,COND=((8,LT),(5,NE,BINDFG)),MAXRC=0
//STEPLIB DD DISP=SHR,DSN=&DSNLOAD.
//SYSTSIN DD DISP=SHR,DSN=&BINDDSN.(&C1ELEMENT).
//DBRMLIB DD DISP=SHR,DSN=&DBRMLIB.,MONITOR=COMPONENTS
// DD DISP=SHR,DSN=&CRS..SELADBRM,MONITOR=COMPONENTS
//SYSTSPRT DD DISP=(OLD,PASS),DSN=&&BNDPRINT
//**********************************************************************
//* FOOTPRINT DB2 PLAN **
//**********************************************************************
//FOOTDB2 EXEC PGM=BC1PCAF,COND=(8,LT),MAXRC=0,
// PARM='DB2T,BC1PSQL1,BC1PDBFP'
//STEPLIB DD DISP=SHR,DSN=&DSNLOAD.
//DBRMLIB DD DISP=SHR,DSN=&DBRMLIB.
// DD DISP=SHR,DSN=&CRS..SELADBRM
//BSTIPT DD DISP=SHR,DSN=&BINDDSN.(&C1ELEMENT).
//*********************************************************************
//* INVOKE IDCAMS TO ENSURE THE BIND CNTL CARD O/P DATA SET IS DELETED*
//*********************************************************************
//IDCAMS EXEC PGM=IDCAMS
//SYSPRINT DD DUMMY
//SYSIN DD *
DELETE '&BINDDSN'.
04-May-2018 422/1109
CA Endevor® SCM - 17.0
DELETE '&BINDDSN'.
SET MAXCC = 0
//*********************************************************************
//* STORE OUTPUT LISTINGS IN LIST LIBRARY **
//*********************************************************************
//CONLIST EXEC PGM=CONLIST,PARM=STORE,MAXRC=0,COND=EVEN
//C1LLIBO DD DSN=&LISTLIB.,DISP=SHR,MONITOR=COMPONENTS
//C1BANNER DD UNIT=tdisk,SPACE=(TRK,1),
// DCB=(RECFM=FBA,LRECL=121)
//LIST01 DD DSN=&&EZECOUT,DISP=(OLD,DELETE)
//LIST02 DD DSN=&&EZEPRINT,DISP=(OLD,DELETE)
//LIST03 DD DSN=&&EZEJCL,DISP=(OLD,DELETE)
//LIST04 DD DSN=&&PRPPRINT,DISP=(OLD,DELETE)
//LIST05 DD DSN=&&TRNPRINT,DISP=(OLD,DELETE)
//LIST06 DD DSN=&&COBPRINT,DISP=(OLD,DELETE)
//LIST07 DD DSN=&&CB2PRINT,DISP=(OLD,DELETE)
//LIST08 DD DSN=&&LNKPRINT,DISP=(OLD,DELETE)
//LIST09 DD DSN=&&BNDPRINT,DISP=(OLD,DELETE)
//*
04-May-2018 423/1109
CA Endevor® SCM - 17.0
//SYSPRINT DD DISP=(OLD,PASS),DSN=&&AMSLST
//SYSIN DD *
DELETE '&CSPUSER..EZEWORK' PURGE
SET MAXCC=0
DEFINE CLUSTER (NAME('&CSPUSER..EZEWORK') -
VOL(&vvolser). -
CYLINDERS(02 01) -
KEYS(14 0) -
RECORDSIZE(272 272) -
SHR (3 3) -
INDEXED ) -
DATA (NAME('&CSPUSER..EZEWORK.DATA')) -
INDEX (NAME('&CSPUSER..EZEWORK.INDEX'))
//**********************************************************************
//* STEP4 - INVOKE CSP/AD VIA E/CSP UTILITY TO PERFORM CSP COMMAND **
//**********************************************************************
//IMPORT EXEC PGM=BC1PDCGB,COND=(0,LT),MAXRC=8
//STEPLIB DD DISP=SHR,DSN=&CRS..SELALMD
// DD DISP=SHR,DSN=&CSP..SEZELMD
//* DD DISP=SHR,DSN=EDC.SEDCLINK
//* DD DISP=SHR,DSN=PLI.SIBMLINK
// DD DISP=SHR,DSN=&COBLIB.
// DD DISP=SHR,DSN=&CONLIB.
//**********************************************************************
//* CSP MESSAGE AND TUTORIAL FILES **
//**********************************************************************
//EZECOMM DD DISP=SHR,DSN=&CSPVSAM..&NLS..EZECOMM
//*----------------------------------------------------------
//* THE FOLLOWING MESSAGE FILES SHOULD BE PRE-ALLOCATED
//*----------------------------------------------------------
//*EZEDMSG DD DISP=SHR,DSN=&CSPVSAM..FZEMSG
//*EZEEMSG DD DISP=SHR,DSN=&CSPVSAM..&NLS..EZEMSG
//*EZETES DD DISP=SHR,DSN=&CSPVSAM..&NLS..FZETUTOR
//*EZEMAP DD DISP=SHR,DSN=&CSPVSAM..&NLS..FZEMAPDS
//**********************************************************************
//* STAGE MEMBER SPECIFICATION LIBRARY (R/W MSL) **
//**********************************************************************
//USR1MSL DD DISP=SHR,DSN=&USR1MSL.
//USR2MSL DD DISP=SHR,DSN=&USR2MSL.
//*********************************************************************
//* CSP TEMPORARY WORK FILE
//*********************************************************************
//EZEWORK DD DISP=SHR,DSN=&CSPUSER..EZEWORK
//EZEWRK1 DD UNIT=&WORKDISK.,SPACE=(CYL,(2,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3200)
//*********************************************************************
//* CSP ESF SERIAL FILE **
//*********************************************************************
//TEMPSRC DD DISP=(OLD,DELETE),DSN=&&TEMPSRC
//*********************************************************************
//* CSP INVOCATION PARAMETER **
//*********************************************************************
//NDVRIPT DD *
M=USR1MSL ROMSL=USR2MSL CMDIN=EZECIN CMDOUT=EZECOUT
/*
//*********************************************************************
//* CSP LOG AND LISTINGS FILES **
//*********************************************************************
//EZECOUT DD DISP=(OLD,PASS),DSN=&&LOGLST
//EZEPRINT DD DISP=(OLD,PASS),DSN=&&CMDLST
//SYSPRINT DD SYSOUT=*
//*********************************************************************
//* CSP COMMAND INPUT **
//*********************************************************************
//EZECIN DD *
IMPORT SERIAL(TEMPSRC) REPLACE(Y);
/*
//**********************************************************************
//* STEP5 - STORE THE LISTINGS FROM THE PREVIOUS STEPS **
//**********************************************************************
//STRLST EXEC PGM=CONLIST,COND=EVEN,MAXRC=0,PARM=STORE
//C1LLIBO DD DSN=&LISTLIB.,DISP=SHR
04-May-2018 424/1109
CA Endevor® SCM - 17.0
//C1LLIBO DD DSN=&LISTLIB.,DISP=SHR
//C1BANNER DD UNIT=&WORKDISK.,SPACE=(TRK,(1,1)),
// DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171)
//LIST01 DD DISP=(OLD,DELETE),DSN=&&AMSLST
//LIST02 DD DISP=(OLD,DELETE),DSN=&&LOGLST
//LIST03 DD DISP=(OLD,DELETE),DSN=&&CMDLST
//*
Unsupported Parameters
Contents
General Restrictions
CA Endevor® SCM processors are written using standard OS JCL syntax, with a few restrictions. Most
JCL parameters are supported in CA Endevor® SCM processor statements.
Selected JCL parameters, and the JCL SET statement, are unsupported by CA Endevor® SCM and, if
used, are ignored by the system or cause as an error. A message is returned when CA Endevor® SCM
encounters one of these parameters:
The following JCL keyword parameters and the JCL SET statement and INCLUDE statement are not
supported by CA Endevor® SCM processors.
Except for the SET statement, which can appear anywhere in JCL, the invalid parameters are shown in
the following lists with the statement type (EXEC= or DD=) in which they are normally used.
SET Statement
The SET command cannot be used in a processor.
04-May-2018 425/1109
CA Endevor® SCM - 17.0
INCLUDE Statement
The JCL INCLUDE statement cannot be used in a processor. However, CA Panvalet and CA Librarian
include member parameters can be used.
DD Statement Parameters
CA Endevor® SCM processors support the DD statement, but they do not support backward reference
(REFERBACK), or these DD statement parameters:
ACCODE
AMP
BURST
CHARS
CHKPT
CNTL
DYNAM
SUBSYS=PANV
DCB Subparameters
CA Endevor® SCM processors support the DCB parameter. The following DCB subparameters that are
not supported.
BUFIN
BUFMAX
BUFOFF
BUFOUT
BUFSIZE
CODE
CPRI
04-May-2018 426/1109
CA Endevor® SCM - 17.0
CPRI
CYLOFL
FRID
FUNC
GNCP
INTVL
IPLTXID
MODE
NTM
PCI
PRTSP
RESERVE
RKP
STACK
THRESH
TRTCH
DDNAME Subparameters
CA Endevor® SCM processors support the DDNAME parameter. The following DDNAME
subparameters are not supported.
DSID
FLASH
MODIFY
MSVGP
OUTPUT
QNAME
REFDD
SPLIT
04-May-2018 427/1109
CA Endevor® SCM - 17.0
SUBALLOC
DDNAME
04-May-2018 428/1109
CA Endevor® SCM - 17.0
04-May-2018 429/1109
CA Endevor® SCM - 17.0
Note: In addition to the libraries referenced, you may also have INCLUDE libraries and user
libraries (copy libraries, macro libraries, JCL libraries) defined to processors. These libraries
are not specific to CA Endevor® SCM, and therefore are not described here.
If you are currently using OS PDS or PDS/Es for base, delta, and/or listing libraries, consider
converting these PDS or PDS/Es to ELIB self-reorganizing data sets.
Exploit 31-bit storage for VSAM-organized data sets, thereby reducing 24-bit storage contention.
These features eliminate most of the growth and compress problems involved with managing PDS or
PDS/Es. ELIB provides faster support for add, update, and delete activities due to its advanced
directory processing techniques.
Note: For more information about ELIB data sets, see ELIB Data Sets (see page 965).
04-May-2018 430/1109
CA Endevor® SCM - 17.0
For example, if you use reverse deltas, a regular PDS or PDS/E to be used to store element base, and
an ELIB dataset to store deltas. Base libraries can be HFS directories.
2. Specify the following DCB, assigning a block size appropriate to your disk device:
DCB=(RECFM=VB,LRECL=record length,BLKSIZE=block-size)
Where record length is the maximum record length that you anticipate storing in the PDS or
PDS/E plus the constant 4. Block-size is a number at least 4 greater than the LRECL length.
When specifying the number of directory blocks in each library, you have one directory block
for every four elements. For efficiency, directory blocks should be allocated in increments of
45 for a 3390-type device (whatever number can fit on a single track, if you are using another
type of device).
To calculate this number, divide the estimated number of elements (members) to be stored in
the library by 4. Round up to an even multiple of 45 (assuming a 3390-type device). The
number should be the same for the base and delta libraries.
Note: If the Automated Configuration Manager facility (CA Endevor® SCM ACM) is installed
at your site, increase the file size by 20 percent and double the number of directory blocks.
04-May-2018 431/1109
CA Endevor® SCM - 17.0
To allocate a new PDS or PDS/E, use ISPF/PDF option 3 (Utilities), option 2 (Data sets), or any suitable
IBM utility (such as IEFBR14). Specify the following DCB, assigning a block size appropriate to your
disk device:
DCB=(RECFM=VBA,LRECL=259,BLKSIZE=block-size)
Specify the number of directory blocks needed. There is one directory block for every four listing
members. For efficiency, directory blocks are allocated in increments of 45 (or whatever number can
fit on a single track, if you are using a device other than a 3390-type device).
To calculate this number, divide the expected number of listings by four and round up to an even
multiple of 45 (for a 3390-type device).
Note: For more information about allocating a new ELIB data set, see ELIB Data Sets (see
page 965).
To allocate the library, use ISPF/PDF option 3 (Utilities), option 2 (Data sets), or any suitable IBM
utility (for example, IEFBR14). Specify the following DCB, assigning a block size appropriate to your
disk device:
DCB=(RECFM=U,BLKSIZE=block-size)
Specify the number of directory blocks needed. There is one directory block for every four
processors. For efficiency, directory blocks are allocated in increments of 45 (or whatever number
can fit on a single track, if you are using a device other than a 3390-type device).
To calculate this number, divide the expected number of processors by four, then round up to an
even multiple of 45 (for a 3390-type device).
04-May-2018 432/1109
CA Endevor® SCM - 17.0
1. Use ISPF/PDF option 3 (Utilities), option 2 (Data sets), or any suitable IBM utility (such as
IEFBR14).
2. Specify the following DCB, assigning a block size appropriate to your disk device:
DCB=(RECFM=FB,LRECL=80,BLKSIZE=block-size) (fixed records)
or
DCB=(RECFM=VB,LRECL=rec-len,BLKSIZE=block-size)(variable records)
rec-len is the maximum record length (as specified when defining the element type(s) that use
this library), plus 4.
You must specify the number of directory blocks needed. There is one directory block for
every four source modules. For efficiency, directory blocks are allocated in increments of 45
(or whatever number can fit on a single track, if you are using a device other than a 3390-type
device).
To calculate this number, divide the expected number of source modules by four, then round
up to an even multiple of 45 (for a 3390-type device).
Note: For more information about the BC1PNLST utility, see ELIB Data Sets (see page 965).
04-May-2018 433/1109
CA Endevor® SCM - 17.0
04-May-2018 434/1109
CA Endevor® SCM - 17.0
Note: For more information about changing the secondary expansion quantity or the
directory size, see ELIB Data Sets (see page 965).
Each CA Endevor® SCM file is classified as critical or non-critical. Critical files, if lost, can only be
rebuilt from a backup. Critical files are the Master Control File, base library, and delta library. Non-
critical files include the source output library, processor listing library, and processor load library. Non-
critical files can be rebuilt by processing the elements. If the source output library is lost, for example,
the source can be recreated from the base and delta libraries.
A PDS or PDS/E
Use a standard IBM utility (for example, IEBCOPY), or any other appropriate utility in use at your
site.
04-May-2018 435/1109
CA Endevor® SCM - 17.0
Note: For more information about using this utility, see Unload, Reload, and Validate (see
page 986).
Important! Keep the source version of all changes made to critical files until a backup can
be made. Otherwise, you cannot reapply these updates.
The Footprint Exception Report (CONRPT83) identifies those members of an output library that are
out of sync with the MCF, and can be used to identify the members that must be added/updated in
the Master Control File. If allocated, the source output library can be used to assist in the recovery. In
the event that source code is lost prior to taking a backup of the critical files, the source output
library still contains a current copy of the source.
Rebuild the file by reprocessing the lost elements. Again, non-critical files include the source
output library, CA Endevor® SCM listing libraries, and processor load library.
If you have a backup copy of the file that is in sync with the critical files, you can recover directly
from the backup. If you do this, however, first ensure that the restored file matches the
information contained in the current MCF, base library, and delta library exactly.
04-May-2018 436/1109
CA Endevor® SCM - 17.0
04-May-2018 437/1109
CA Endevor® SCM - 17.0
Footprint Synchronization
A footprint is a set of encrypted data placed by CA Endevor SCM processors in generated source,
object, or load modules. Footprints contain location and event information from the Master Control
File record for the element:
Site ID
Environment
Stage Number
System
Subsystem
Type
Element Name
FOOTPRNT=VERIFY Statement
04-May-2018 438/1109
CA Endevor® SCM - 17.0
Including the FOOTPRNT=VERIFY statement in your processors automates footprint verification each
time the processor runs.
Footprint Reports
Running footprint reports on a regular basis helps you to monitor footprints. The following describes
the footprint reports:
Note: For more information about footprints (including sample reports), see Footprint
Reporting.
A list of CSECTs for a specific load module, with footprint information for each CSECT and for the
load module.
If a member, CSECT, or load module is footprinted, CA Endevor SCM lets you display information
(current source, change history, changes at the current level, summary of levels, Master Control File
information) about it from this selection list.
Produce all footprint reports at a remote site as if the remote load library existed on a central
machine.
04-May-2018 439/1109
CA Endevor® SCM - 17.0
Determine which load modules changed since they were shipped to a remote site by comparing
their footprints with Master Control File information at a host site.
Install the Remote Footprint Synchronization facility available in CA Endevor SCM. The installation
consists of the following steps:
1. Create a load library at the remote site that contains the footprint synchronization programs.
2. Create and placing a copy of the C1DEFLTS table in the load library at the remote site.
3. Create a JCL library at the remote site containing the JCL to execute the footprint extract
program, the data transmission utility program and, optionally, the report generator.
Load libraries
For the CA Endevor SCM for CA Panvalet Interface, it is stored as a COMMENT field.
04-May-2018 440/1109
CA Endevor® SCM - 17.0
For the CA Endevor SCM for CA Panvalet Interface, it is stored as a COMMENT field.
For a previously footprinted sequential data set (object deck only) that is stored in a PDS (using
FOOTPRNT=CREATE), there is a footprint (part of an IDENTIFY statement) at the end of the data set
and in the user data area of the directory. If the sequential data set (object deck only) and PDS
member are created by the same processor, they are in sync.
Note: CA Endevor SCM does not allow the footprinting of the load module PDS directory
because this would compromise the ability of the load module to execute. For PDS load
module footprints, a user update to the IDR or a zap applied to the load module
compromises the footprint.
04-May-2018 441/1109
CA Endevor® SCM - 17.0
Copy the C1DEFLTS table that was created during CA Endevor SCM installation at your base site from
your system linklist library to the newly created load library.
If ASCM is enabled at your site, the C1DEFLTS table must be changed. Disable this facility by removing
the ACMROOT and ACMXREF specified in the table and setting ASCM=N. Then reassemble and link
the new C1DEFLTS table into the CONLIB created in the previous step. This change is required to
prevent the remote footprint job from trying to allocate the ACMROOT and XREF files, which do not
exist in the remote site.
Note: If the RACF alternate user ID is enabled at your site, the C1DEFLTS table must be
changed. Disable this facility by removing the RACFUID specified in the table. Then
reassemble and link the new C1DEFLTS table into the CONLIB created in the previous step.
Note: For more information about sample jobstreams, see Sample JCL (see page 442).
Sample JCL
The sample JCL is provided in the iprfx.iqual.JCL library on the installation cartridge. You need to
customize each jobstream for your site.
04-May-2018 442/1109
CA Endevor® SCM - 17.0
BC1JFEXT
The footprint extract program, which excutes at the remote site and extracts footprints at the
remote site.
BC1JFNDM
The data transmission utility program for sites using the CONNECT:Direct data transmission
utility. BC1JFNDM transmits the remote footprint synchronization utility footprint extract data set
from the remote site to the central CA Endevor SCM site.
BC1JFNTV
The data transmission utility program for sites using the Tivoli NetView transmission utility.
BC1JFNTV transmits the remote footprint synchronization utility footprint extract data set from
the remote site to the central CA Endevor SCM site.
BC1JFBDT
The data transmission utility program for sites using the Bulk Data Transfer transmission utility.
BC1JFBDT transmits the remote footprint synchronization utility footprint extract data set from
the remote site to the central CA Endevor SCM site.
BC1JFRPT
The report generator program. BC1JFRPT generates the reports CONRPT80, CONRPT81, and
CONRPT82 at the central site.
BC1JFEXT
In the BC1JFEXT sample JCL, the analyze statement input refers to a coded ANALYZE statement.
Note: For more information about the coded ANALYZE statement, see Footprint Reporting
(see page 444).
The BC1PFOOT executable program does not have to be called by an authorized program. However, if
you are executing the non-authorized program, you must have the requisite security access to the CA
Endevor SCM data sets for the function requested. The caller's security profile must have sufficient
CA Top Secret, CA ACF2, or RACF, access to the CA Endevor SCM control files (catalog, master,
package, base, delta), because the CA Endevor SCM alternate ID facility is not available when running
in an unauthorized mode.
To call the footprint extract utility from a non-authorized program, specify the following:
EXEC PGM=BC1PFOOT
04-May-2018 443/1109
CA Endevor® SCM - 17.0
To determine if footprints at a remote site are synchronized with CA Endevor SCM location
information from the central location:
1. Run job BC1JFEXT at the remote site to extract footprint information and place it in a footprint
extract file.
3. Run job BC1JFRPT at the host site to determine if the remote load module footprints are
synchronized with the host inventory information.
CONRPT80
Library Member Footprint report
CONRPT81
Library CSECT Listing
CONRPT82
Library Zapped CSECT Profile
CONRPT83
Footprint Exception report
Note: Footprint reports and Package reports are mutually exclusive. If you need both types
of reports, submit two separate jobs, or two separate jobsteps in the same job.
How to Specify Data Extract Phase Selection Criteria (see page 445)
Syntax Examples for Generating Footprint Reports (see page 447)
Name Masking (see page 448)
1. The first phase extracts information for the requested members from a partitioned data set, a
CA Endevor SCM for CA Panvalet Interface library, or a CA Endevor SCM CA Librarian Interface
library, as appropriate to the report request (and defined by the BSTPDS DD statement).
04-May-2018 444/1109
1.
CA Endevor® SCM - 17.0
2. The second phase reads the sequential extract file and produces the reports requested.
To request the Footprint reports, execute the BC1JRPTS job after supplying appropriate Selection
Statements for each of the two phases of processing. Use the BSTIPT DD statement to specify
footprint selection criteria, and the BSTINP DD statement to specify the reports you want to produce.
With CA Endevor SCM, you can extract footprint data about specified data sets by running the
BC1JFEXT job. You can use BC1JFEXT alone to extract footprint data before editing and running the
report JCL job BC1JRPTS. After running BC1JFEXT, you reference the data set created by BC1JFEXT in
your report JCL syntax.
//BSTINP DD *
FOOTPRINT DDNAME footfile.
//FOOTFILE DD DSN=FOOTPRINT.FILE.DSN, DISP=SHR
Note: When running BC1JFEXT separately, no BSTIPT footprint selection criteria is needed
when running the subsequent footprint reports. Only the FOOTPRINT DDNAME statement
within the BSTINP input is required.
Using selection criteria, you define the members and CSECTs for which information should be
extracted, and the extent of detail you want to extract for each load member. Only the information
requested is available for reporting.
Any selection criteria specified apply across all Footprint reports (80-83). If you specify INCLUDE
MEMBERS AR*, for example, only the information for members beginning with AR is provided -- for
all Footprint reports requested.
The syntax is freeform when coding the BSTIPT DD input. It can be specified across any number of
cards, as long as each keyword or name is fully contained on one card.
04-May-2018 445/1109
CA Endevor® SCM - 17.0
ANALYZE/DIRECTORY
Indicates the level of detail you want to extract, as follows.
INCLUDE/EXCLUDE
Parameters used to restrict the extract to specific members, or CSECTs, or both. By default,
extraction occurs for all members and all CSECTs that are in the library being processed.
Specify INCLUDE to extract information for only the members or CSECTs identified by the
members/csects parameter. Specify EXCLUDE to exclude from the extract processing those
members or CSECTs referenced by the members/csects parameter.
You can have any number of INCLUDE or EXCLUDE statements, or both. All the INCLUDEs are
processed first; EXCLUDEs are then processed, first for members, then for CSECTs. The effect is to
first limit the extract to those members or CSECTs specifically included, and to then exclude --
from the included members or CSECTs -- those names referenced by the EXCLUDE statements.
04-May-2018 446/1109
CA Endevor® SCM - 17.0
THRU/TO member-csect-name
THRU defines the last member or CSECT in the range of names to be processed. If you include a
mask character (*) at the end of the THRU MEMBER/CSECT-NAME, the range includes all names
beginning with the characters specified.
TO defines the member or CSECT name to which processing should go, excluding itself. A name
mask is inappropriate (and is ignored) if it is used with a TO member/csect-name.
The use of the THRU/TO option is described above for the members/csects parameters.
Note: When you run Footprint reports, CA Endevor SCM returns a report that lists the
selection criteria used and the number of extract records written.
To extract DIRECTORY-level data for all members or CSECTs (or both) in the library:
DIRECTORY.
To extract full (ANALYSIS-level) detail for all members whose names begin with the characters C1:
ANALYZE INCLUDE MEMBERS C1*.
or
ANALYZE INCLUDE MEMBERS C1* TO D.
or
INCLUDE MEMBERS C1*.
or
INCLUDE MEMBERS C1* TO D.
EXCLUDE CSECTS ILB*.
To request only those members whose names start with A200, while excluding from those
selected members all CSECTs whose names start with ILB or $2:
INCLUDE MEMBERS A200*
EXCLUDE CSECTS ILB*
EXCLUDE CSECTS $2*.
Note: Remember that where CSECT detail is included in a footprint report, that detail is
04-May-2018 447/1109
CA Endevor® SCM - 17.0
Note: Remember that where CSECT detail is included in a footprint report, that detail is
available only if you specify ANALYZE to the Data Extract phase.
Name Masking
To help you more easily find information and process requests, you can use name masking. By
substituting a name with the asterisk wildcard character (*), a character with the percent sign
placeholder (%), or by using both together, it is much faster and easier to find information and
process requests.
2.Member name
Member
Name of the (load or non-load) library member for which footprint information is shown to the
right.
CSECT
Applicable for load members only. Name of the CSECT for which footprint information is shown to
the right. If no footprint information displays to the right, the CSECT was not footprinted.
Environ
Name of the environment under which the corresponding element is defined.
System
Name of the system under which the corresponding element is defined.
Subsys
Name of the subsystem under which the corresponding element is defined.
04-May-2018 448/1109
CA Endevor® SCM - 17.0
Element
Name of the CA Endevor SCM element that corresponds to this CSECT (for a load member) or
member (for a non-load member).
Type
Type for the element.
Stg
ID of the stage under which the corresponding element is defined.
VVLL
Current version and level for the element.
Date
Generate processor date for the element (ddMMMyy).
Time
Generate processor time for the element (hh:mm).
LD
An entry of Y indicates that the footprint was created by the load utility. A blank (no entry)
indicates that the footprint was created by a processor.
(no heading)
For CSECTs that were not footprinted, and for any CSECTs that had PTFs applied against them:
CSECT ZAPPED indicates that the CSECT had at least one PTF applied.
2.Member name
04-May-2018 449/1109
CA Endevor® SCM - 17.0
CSECT
Name of the CSECT for which information is shown to the right.
Member
Name of the load member for the CSECT.
Linked
Date the load module was last link-edited with this CSECT (ddMMMyy).
Compiled
Date the load module was last compiled (ddMMMyy).
Environ
Name of the environment under which the corresponding element is defined.
System
Name of the system under which the element is defined.
Subsys
Name of the subsystem under which the element is defined.
Element
Name of the element that corresponds to this CSECT.
Type
Type for the element.
Stg
ID of the stage for the element.
VVLL
Current version and level for the element.
Date
Generate processor date for the element (ddMMMyy).
Time
Generate processor time for the element (hh:mm).
LD
An entry of Y indicates that the footprint was created by the load utility. A blank (no entry)
indicates that the footprint was created by a processor.
(no heading)
For CSECTs that were not footprinted, and for any CSECTs that had PTFs applied against them:
CSECT ZAPPED indicates that the CSECT had at least one PTF applied.
2.Member name
CSECT
Name of the CSECT for which information is shown to the right.
Member
Name of the load member of which the CSECT is a part.
Compiled
Date the load module was last compiled (ddMMMyy).
Linked
Date the load module was last link-edited with this CSECT (ddMMMyy).
Environ
Name of the environment under which the corresponding element is defined.
System
Name of the system under which the corresponding element is defined.
Subsys
Name of the subsystem under which the element is defined.
Element
Name of the CA Endevor SCM element that corresponds to this CSECT.
Type
Type for the element.
Stg
ID of the stage for the element.
VVLL
Version and level of the element used to create this CSECT.
04-May-2018 451/1109
CA Endevor® SCM - 17.0
Date
Generate processor date for the element (ddMMMyy).
Time
Generate processor time for the element (hh:mm).
LD
An entry of Y indicates that the footprint was created by the load utility. A blank (no entry)
indicates that the footprint was created by a processor.
Cnt
Number of PTFs (ZAPs) that were applied against the CSECT.
Date
Date on which the PTF identified by the Info field (to the right) was applied. One date is included
for each PTF.
Info
IDRDATA assigned at the time the PTF was applied.
To determine whether the footprint information is out of sync with the MCF, CA Endevor SCM
compares the member or CSECT footprint against the corresponding element, within the
environment and stage specified using the Selection Statements.
For each member or CSECT, a message is included to the far right. This message indicates the reason
why the member or CSECT is included in the report.
04-May-2018 452/1109
CA Endevor® SCM - 17.0
CSECT
Applicable for load members only. Name of the CSECT for which footprint information or the
comment "* NO FOOTPRINT PRESENT" displays to the right.
Environ
Name of the environment under which the corresponding element is defined.
System
Name of the system under which the element is defined.
Subsys
Name of the subsystem under which the element is defined.
Element
Name of the element that corresponds to this CSECT (for a load member) or member (for a non-
load member).
Type
Type for the element.
Stg
ID of the stage under which the corresponding element is defined.
VVLL
Current version and level for the element.
Date
Generate processor date for the element (ddMMMyy).
Time
Generate processor time for the element (hh:mm).
LD
An entry of Y indicates that the footprint was created by the load utility. A blank (no entry)
indicates that the footprint was created by a processor.
Gen/MSTR Date
Generate processor date for the element (ddMMMyy) from the Master Control File (MCF) for this
member or CSECT.
MOVE/CMP Date
Move date for the element -- and its associated component list, if there is one -- (ddMMMyy)
from the MCF file for this member or CSECT.
VVLL
Current version and level for the element from the MCF file for this element or CSECT.
Message
Message number to describe why the member or CSECT is included in the report. The message
numbers and meanings are described on the final page of this report.
04-May-2018 453/1109
CA Endevor® SCM - 17.0
This section provides sample report JCL (z/OS and VSE/ESA) and EXECs (VM/ESA) used to run the
Executable Module Footprint Report. Use the JCL (or EXEC) appropriate to your installation when
running this report. Certain variable parameters, indicated by lowercase entries in the JCL or EXEC,
must be changed to meet your particular requirements.
04-May-2018 454/1109
CA Endevor® SCM - 17.0
04-May-2018 455/1109
CA Endevor® SCM - 17.0
InfoMan Interface
Contents
People familiar with how CA Endevor® SCM is used at your site, and in particular with CA
Endevor® SCM packages and exits.
The interface works with both native InfoMan and the InfoMan Interactive Facility (IIF).
In addition to managing the initialization and termination of InfoMan sessions under CA Endevor®
SCM, the interface implements package-level and action-level interaction between CA Endevor® SCM
and InfoMan. This allows you to:
Use the InfoMan approval process for moving packages into production, rather than the CA
Endevor® SCM process.
Produce lists of available CCIDs when requesting stand-alone actions in foreground or batch SCL
generation.
The interface does this by communicating directly from CA Endevor® SCM exit points with the
04-May-2018 456/1109
CA Endevor® SCM - 17.0
The interface does this by communicating directly from CA Endevor® SCM exit points with the
InfoMan API. The communication is accomplished through a user-defined rule set, called the E/INFO
table, created when the interface is implemented. You create the rule set with a batch utility
provided with the interface.
Before the existence of the InfoMan API, Terminal Simulation Programs (TSPs) were the only way to
get to InfoMan. The batch utility offers another, flexible way to build a custom rule set for
implementing InfoMan policies in CA Endevor® SCM, and getting data requirements and processing
logic from CA Endevor® SCM to InfoMan.
The batch utility allows this rule set to be independent of InfoMan invocation. Moreover, the utility
does not require extensive experience with either TSPs or assembler programming.
BEND--Interface Operation--OTH.PNG
As previously illustrated, the interface communicates directly with the InfoMan API at exit 5
(initialization) and exit 6 (termination). For exits 2 (before-action), 3 (after-action), and 7 (package
functions) the E/INFO table, the load module built using the batch utility, provides a bridge between
the CA Endevor® SCM exit facility and the InfoMan API. The rule set contained in the E/INFO table
determines how the interface acts.
04-May-2018 457/1109
CA Endevor® SCM - 17.0
Identifying InfoMan actions to be performed (Inquiry, Retrieve, Create, Update), and the PIDT
table needed for each function.
Establishing criteria on the CA Endevor® SCM or the InfoMan side for performing an action.
Specifying the CA Endevor® SCM information to be recorded in InfoMan, and the InfoMan fields
where the information is to be recorded.
As previously illustrated, the utility assembles the definition syntax into a load module, referred to in
this manual as the E/INFO table. The E/INFO table is loaded at CA Endevor® SCM initialization, and is
independent of InfoMan invocation. The rule set it contains determines how the interface uses the
InfoMan API.
When the table is invoked, CA Endevor® SCM builds a request for the InfoMan API using the
04-May-2018 458/1109
CA Endevor® SCM - 17.0
When the table is invoked, CA Endevor® SCM builds a request for the InfoMan API using the
information in the table. The InfoMan API executes the requested functions against the InfoMan
database.
The CA Endevor® SCM package is cross-referenced to an InfoMan change record, with the
package ID stored in the COREQUISITE field of the InfoMan record, and the InfoMan RNID stored
in the CORRELATION field of the CA Endevor® SCM package record.
For each unique CCID in the package action SCL records, the interface maintains a change activity
record in InfoMan, with the CA Endevor® SCM CCID stored in the ACTION NAME field in the
InfoMan record. Information about each action associated with the CCID can be stored as
freeform text in that activity record. The freeform text field is useful for this purpose because new
information is always appended to existing information in the field.
04-May-2018 459/1109
CA Endevor® SCM - 17.0
As previously illustrated, the package level of the InfoMan Interface allows sites that use InfoMan as
the mechanism for approving packages for production turnover to use the InfoMan approval process
instead of the approval process for CA Endevor® SCM packages.
The interface also provides an improved audit trail for packages, and better reporting on packages
than is currently available from CA Endevor® SCM.
Note: You can view package information stored in InfoMan using reports. For more
information, see Using CA Endevor SCM InfoMan Interface Reports. In addition, in
foreground you can view package correlation data from the Package Display panel.
04-May-2018 460/1109
CA Endevor® SCM - 17.0
As previously illustrated, you can either utilize the action level of the interface, or you can create
either a Problem or a Change record in InfoMan for each unique CCID.
Note: When using the action level of the CA Endevor SCM InfoMan Interface, the user is
allowed to wildcard the CCID field in CA Endevor® SCM when requesting the following
stand-alone actions in foreground and batch: ADD/UPDATE, MOVE, RETRIEVE, GENERATE,
DELETE, TRANSFER, and ARCHIVE. When a CCID value is fully specified, a list is not
produced. Processing proceeds normally, including processing specified by the interface. In
addition, wildcarding CCIDs is not allowed when building SCL in packages.
How CA Endevor SCM InfoMan Interface Installation Works (see page 462)
How to Install Basic InfoMan (see page 462)
How to Modify Basic InfoMan for the Interface (see page 464)
04-May-2018 461/1109
CA Endevor® SCM - 17.0
2. Refer to the appendix "InfoMan Information for Advanced Users," for considerations relevant
to customized InfoMan shops or advanced users. The person in charge of customizing the
InfoMan product needs to review the interface requirements in this appendix.
Note: CA Endevor SCM InfoMan Interface requires that the IBM Information Management
product, version 4.2 or higher, is installed at your site.
2. Make sure the Information Management Load Library data set is in LINKLST, or that you have
the data set name available.
3. Prepare a session parameter (BLGSESxx) module to reflect the database, data dictionary, read
04-May-2018 462/1109
CA Endevor® SCM - 17.0
3. Prepare a session parameter (BLGSESxx) module to reflect the database, data dictionary, read
panel, and RFT data sets that the interface uses when accessing the data base via the API.
4. Make sure that BLGISPFD, an InfoMan supplied ISPF panel, has been moved into your ISPPLIB
concatenation.
This session parameter is well documented in the InfoMan install manuals. It is required of standard
InfoMan. The naming standard is BLGSESxx where xx is the user's choice. This suffix is also required
for a CA Endevor® SCM start-up block assembly. Note that the same BLGSESxx member can be used
for the interface as well as standard access to InfoMan.
The suffix used to name the actual BLGSESxx module is required in Phase 3. The rest of this install
requires the data set names from the BLGSESxx module.
Note: The interface installation includes one modified Assisted Entry panel, which must be
copied into your read panel data set concatenation. You can either overlay the IBM version
of this data set, or provide a new read panel data set ahead of the standard IBM data set.
Either way, the result is that the RPANEL0 label points to the data set used in the install.
Sometimes this library is part of LINKLIST, and sometimes it is not. If this data set is not in LINKLST,
the person implementing the interface needs to know its name, and must put it into a STEPLIB in the
concatenation.
04-May-2018 463/1109
CA Endevor® SCM - 17.0
Dictionary DD name:
RFTDS DS name:
RPANEL0 name:
1. Copy interface report shells to the RFT data set identified in Phase 1. In this step, BC1JEI20 JCL
is used.
2. Copy CA Endevor® SCM version of BLG6CORQ into the RPANEL0 data set identified in Phase 1.
In this step, BC1JEI15 JCL is used.
4. Create the standard IBM PIDT and PIPT tables. In this step, BC1JEI45 JCL is used.
5. Build a rule set for driving the API using the interface batch utility. In this step, BC1JEI00 JCL is
used.
6. Assemble or copy the BLGSESxx module into your STEPLIB data set. In this step, BC1JEI05 JCL
is used.
EINTACH0
Action Change Record Summary
EINTACH1
Action Change Record Detail
04-May-2018 464/1109
CA Endevor® SCM - 17.0
EINTAPB0
Action Problem Record Summary
EINTAPB1
Action Problem Record Detail
EINTPKG0
Package Parent Record Summary
EINTPKG1
Package/Activity Record Summary
EINTPKG2
Package/Activity Record Detail
The modified panel is provided with the interface. Copy it into the RPANEL data set using the JCL in
member BC1JEI15 in the iprfx.iqual.CSIQJCL data set.
This job uses the BLGUT6F utility to copy a PDS member that has been created from a InfoMan panel
using BLGUT6.
This panel must reside above the IBM panel of the same name. The person who runs the job to copy
the modified panel needs only the data set name. You recorded the RPANEL0 data set name in the
worksheet at the end of Phase 1.
Important! Run this job only if you are installing basic InfoMan. If your site has customized
InfoMan, see the appendix "InfoMan Information for Advanced Users," for instructions on
updating the dictionary entry.
BC1JEI30 JCL is shown next. Before submitting this JCL, provide a job card, and confirm that iprfx.iqual
and uprfx.uqual are the correct data set qualifiers.
04-May-2018 465/1109
CA Endevor® SCM - 17.0
Use the BC1JEI45 member in iprfx.iqual.CSIQJCL. Before submitting this JCL, provide a job card and
confirm that the iprfx.iqual and uprfx.uqual are the correct data set qualifiers.
EISCRIP1
Batch utility input for stand-alone actions, using InfoMan Change records.
EISCRIP2
Batch utility input for stand-alone actions, using InfoMan Problem records.
EISCRIP3
Batch utility input for package functions and package actions. Next, create a rule set. It is
advisable to keep it simple at first. Do this by taking one or two actions or package functions and
writing utility syntax input for them. Then run the batch utility to create an initial rule set. The JCL
for executing the utility to build the rule set is in member BC1JEI00 of iprfx.iqual.CSIQJCL.
A successful run of the utility produces a load module called by a name you specify. This load module
name is used in Phase 3. Assemble this load module into a STEPLIB data set.
Remember:
To change what you use the interface for is a simple run of the utility. It requires no further
InfoMan or CA Endevor® SCM work to enhance the rule set.
If you point to any PIDT tables other than the defaults, verify that they reside in the RFTDS data
set pointed to in your BLGSESxx member.
The JCL for executing the utility to build the rule set is in member BC1JEI00 of iprfx.iqual.CSIQJCL.
Before submitting this JCL, provide a job card, confirm that iprfx.iqual and uprfx.uqual are the correct
data set qualifiers, confirm that tdisk is a valid unit name and, if necessary, change the size of the
WORK1 or WORK2 data sets.
04-May-2018 466/1109
CA Endevor® SCM - 17.0
Before submitting this JCL, provide a job card, confirm that iprfx.iqual and uprfx.uqual are the correct
data set qualifiers, confirm that tdisk is a valid unit name,and replace xx in the string BLGSESxx with a
session identifier.
This phase of the installation process involves setting up the InfoMan and CA Endevor® SCM sides of
the interface to work together, as described in the following.
4. Make sure that required panels are in the ISPPLIB data set.
5. Make sure that members INFO01 and PKMR02 are in your ISPMLIB data set.
The @EINFO macro, supplied with the interface, provides input to BC1TEI90. The macro can be found
embedded in member BC1JEI10 in iprfx.iqual.CSIQJCL. Edit this macro based on the information
contained in the Phase 1 checklist and your site standards.
ENTRY=START
Indicates the beginning of the BC1TEI90 table.
04-May-2018 467/1109
CA Endevor® SCM - 17.0
BLGSES=
InfoMan looks for session parameters in a module named BLGSESxx, where xx is a two-character
identifier for the module. This module is described in the InfoMan documentation. You recorded
the components of this module during Phase 1 of this installation, as well as the two-character
identifier for the module. When modifying the @EINFO macro supplied with the interface,
replace the default value 00 with the value you specified in Phase 1.
The default is 00. This is the same as standard InfoMan.
APISESID=
The API requires a session ID during initialization. This session can be called USERID or can be a
predefined InfoMan API ID.
The default is USERID. Leaving this default allows the same start-up module to be used by many
people, with the interface substituting the user ID of the caller for the literal USERID.
If you include this keyword, you must provide a value.
EPIDT=
This keyword contains the name of the assembled E/INFO table produced by the batch utility. The
default is Endevor.
If you include this keyword, you must provide a value.
INVCLASS=
InfoMan has its own security system. It is broken into classes with privileges. Every user or API ID
is assigned to at least one CLASS. The API requires a class name.
The default is MASTER.
WAITTIME=
The API allows the application to define how long it will wait for a response from the InfoMan API
server. If the user does not use this keyword, the default will be 300 seconds.
RECTYPE=
Users must select one kind of InfoMan record for recording information about stand-alone
actions. They can use either Change or Problem records. Display services also need this
information.
The default is CHANGE. If coded, it cannot be blank.
ENTRY=END
Required. This statement denotes the end of the BC1TEI90 table.
04-May-2018 468/1109
CA Endevor® SCM - 17.0
//SYSLMOD DD DISP=SHR,DSN=uprfx.uqual.LOADLIB(BC1TEI90)
//SYSUT1 DD UNIT=tdisk,SPACE=(CYL,(5,3))
//SYSPRINT DD SYSOUT=*
C1EILIST, CITILIST
CCID list panel and its associated tutorial panel.
C1SEIBRW, CITEIBRW
InfoMan record display for packages and stand-alone actions and its associated tutorial panel.
CSIQAUTH/CSIQAUTU
Load modules, as well as the following:
C1BMEI00
C1DEFLTS table. See Step 3. Reassemble C1DEFLTS with the InfoMan Password.
C1SM1000
04-May-2018 469/1109
CA Endevor® SCM - 17.0
BC1TEI90, the module containing user parameters, which you assembled in Step 2. Assemble
and Link BC1TEI90.
E/INFO table. This is the rule set that you build using the batch utility. See Step 5. Build a Rule
Set.
BLGSESxx, the module containing the InfoMan session parameters. See Step 2. Prepare a
Session Parameter Member.
CONLIB
The CA Endevor® SCM load modules installed from iprfx.iqual.CSIQLOAD. Make sure to save the
current copy of C1BEXITS before installing the new interface. This allows you to go back to the old
interface during testing.
RFTDS
EINTACH0, EINTACH1, EINTAPB0, EINTAPB1, EINTPKG0, EINTPKG1, EINTPKG2.
PIDT and PIPT tables. See the list in the next section. These panels are found in iprfx.iqual.
CSIQOPTN.
BLGISPFD, the InfoMan supplied ISPF panel.
RPANEL0
BLG6CORQ, the modified version of the Assisted Entry panel. See Step 3. Copy Dictionary Update.
DDICT
index RNCC/CCV15. This is the modified dictionary entry associated with the modified Assisted
Entry Panel. See Step 4. Create the Standard IBM PIDT and PIPT Tables.
iprfx.iqual. ISPPLIB
C1EILIST, C1SEIBRW, C1SP1000 ── C1SP7000 and the associated tutorials (CITILIST, CITEIBRW, and
CITP1000-CITP7000.
iprfx.iqual. ISPMLIB
INFO01, PKEX21, PKMR02.
iprfx.iqual. ISPSLIB
C1SB3000. The following shows how these modules tie the interface together, and indicates the
important members that should be at each location.
04-May-2018 470/1109
CA Endevor® SCM - 17.0
As previously illustrated, you can see how the modules tie the interface together and which
important members should be at each location.
There are three categories of PIDT/PIPT tables: Change, Change Activity, and Problem. These tables
are listed next, and can be found in iprfx.iqual.CSIQOPTN.
TS0B06A
Change record, Add, PIDT
TS0B06AP
Change record, Add, PIPT
TS0B06I
Change record, Inquiry, PIDT
TS0B06IP
Change record, Inquiry, PIPT
TS0B06C
Change record, Create, PIDT
TS0B06CP
04-May-2018 471/1109
CA Endevor® SCM - 17.0
TS0B06CP
Change record, Create, PIPT
TS0B06U
Change record, Update, PIDT
TS0B06UP
Change record, Update, PIPT
TS0B06R
Change record, Retrieve, PIDT
TS0B06RP
Change record, Retrieve, PIPT
TS0B07I
Change activity record, Inquiry, PIDT
TS0B07IP
Change activity record, Inquiry, PIPT
TS0B07C
Change activity record, Create, PIDT
TS0B07CP
Change activity record, Create, PIPT
TS0B07U
Change activity record, Update, PIDT
TS0B07UP
Change activity record, Update, PIPT
TS0B07R
Change activity record, Retrieve, PIDT
TS0B07RP
Change activity record, Retrieve, PIPT
TS0032I
Problem record, Inquiry, PIDT
TS0032IP
Problem record, Inquiry, PIPT
TS0032C
04-May-2018 472/1109
CA Endevor® SCM - 17.0
TS0032C
Problem record, Create, PIDT
TS0032CP
Problem record, Create, PIPT
TS0032U
Problem record, Update, PIDT
TS0032UP
Problem record, Update, PIPT
TS0032R
Problem record, Retrieve, PIDT
TS0032RP
Problem record, Retrieve, PIPT
The purpose of the E/INFO table is to provide a flexible, easy way to implement site InfoMan policy
through the InfoMan API. In particular, the E/INFO table allows the user to:
Establish criteria on the CA Endevor® SCM or the InfoMan side for performing an action.
04-May-2018 473/1109
CA Endevor® SCM - 17.0
Establish criteria on the CA Endevor® SCM or the InfoMan side for performing an action.
Specify the CA Endevor® SCM information to be recorded in InfoMan, and the InfoMan fields
where the information is to be recorded.
Identify InfoMan actions to be performed (Inquiry, Retrieve, Create, Update), and the PIDT table
needed for each action.
You build the E/INFO table during interface implementation using a batch utility provided with the
interface. This utility assembles the table into a load module that is invoked at the exit points defined
in the table.
When the table is invoked, CA Endevor® SCM builds a request for the InfoMan API using the
information in the table. The InfoMan API executes the requested actions against the InfoMan
database, using the requested PIDT tables.
1. Determine what kind of CA Endevor® SCM information you want to store in InfoMan:
package, package action, or stand-alone action information.
2. Be familiar with the necessary CA Endevor® SCM exit points and exit control blocks for the
kinds of information you plan to track.
3. Know which control block fields for the exit points you wish to utilize contain information
eligible for storage in InfoMan.
4. Decide which of the available control block fields you want to track in InfoMan.
5. Decide InfoMan fields you want to use to store the CA Endevor® SCM information.
After writing the table definition statement, submit it to the CA Endevor® SCM batch utility.
CTRL;
IACT (TS0B06I); /* Inquiry Change for actions */
RACT (TS0B06R); /* Retrieve Change for actions */
04-May-2018 474/1109
CA Endevor® SCM - 17.0
RACT (TS0B06R); /* Retrieve Change for actions */
CACT (TS0B06C); /* Create Change for actions */
UACT (TS0B06U); /* Update Change for actions */
ECTRL;
USE(ADD,BEFORE,STANDALONE);
NOTFOUND (CREATE,ADD0010);
FOUND (ADD0020);
LABEL ADD0010;
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=USER);
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
FIELD PANEL(BLG6DSAB) INDEX(S0E0F)
VALUE('API CREATED CHG RECORD');
EPOPULATE;
RC (0);
ELABEL;
LABEL ADD0020;
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
ECRITERIA;
POPULATE;
EPOPULATE;
CPASS ADDPASS;
CFAIL ADDFAIL;
ELABEL;
LABEL ADDPASS;
RC (0);
ELABEL;
LABEL ADDFAIL;
RC (8);
ELABEL;
EUSE;
USE(ADD,AFTER,STANDALONE);
FOUND (ADD0010);
NOTFOUND (RETURN);
LABEL ADD0010;
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT('PROCESSING COMPLETED FOR ELEMENT =EV2ELEMT ') -
('ACTION: =ACTION EXECUTED BY: =USER ' ) -
('ON =DATE =TIME');
EPOPULATE;
ELABEL;
EUSE;
ETABLE;
Table statement
One per table
Starts, names, and ends the table.
Use blocks
One or more per table
Identifies the exit points where the table is invoked and associate processing logic with each exit
point.
04-May-2018 475/1109
CA Endevor® SCM - 17.0
point.
Label blocks
One or more per Use block
Specify processing for an exit point.
Criteria blocks
One or more per Use block
Establish true/false conditions. When there is a true condition, the interface populates InfoMan
records with CA Endevor® SCM information.
Populate blocks
One or more per Use block
Identifies CA Endevor® SCM information to be recorded in InfoMan. The statements that can be
coded for each block are described later in this chapter.
The acceptable values for the variables are supplied in the discussion of the syntax.
Optional syntax components are enclosed in brackets. For example, in the syntax below the
components STANDALONE and PROBLEM are (Optional)
USE(function,{BEFORE|AFTER|ACTIVITY}[,STANDALONE][,PROBLEM])
Required syntax components for which there is more than one acceptable value are shown
enclosed in braces, with the acceptable values separated by vertical lines. For example, in the
syntax below the second argument between parentheses must be BEFORE, AFTER, or ACTIVITY.
USE(function,{BEFORE|AFTER|ACTIVITY}[,STANDALONE][,PROBLEM])
TABLE NAME
(Required) This must be the first statement in the E/INFO table syntax.
04-May-2018 476/1109
CA Endevor® SCM - 17.0
name
(Required) A 1- to 8-alphanumeric character name for the table. This name is also used as the
output member name of the load module that interacts with the InfoMan API.
Parentheses on the name are (Optional) The name must be followed by a semicolon.
ETABLE
(Required) This must be the final statement in the E/INFO table syntax. It must be followed by a
semicolon.
Example:
TABLE NAME (NDVR);
.
ETABLE;
The CTRL block must follow the TABLE statement. There must be a statement in this block for each
function that you want to perform against the InfoMan database. The statements in this block must
identify all the PIDT tables required by the requested functions.
Note: Users of standard InfoMan should always use the standard CTRL statements included
in the samples.
04-May-2018 477/1109
CA Endevor® SCM - 17.0
InfoMan Action
An InfoMan action is (Required) There must be at least one InfoMan action specified in a control
statement. Acceptable values are
I (Inquiry)
R (Retrieve)
C (Change)
U (Update)
A (Add)
Inquiry (I)
Check to see if an InfoMan record exists.
Retrieve (R)
Test a field in an InfoMan record for a specific value.
Create (C)
Create records in InfoMan based on criteria in the E/INFO table.
Update (U)
Update existing records in InfoMan.
Add (A)
Use the InfoMan Change Activity record type to store information about package actions. The
InfoMan action appears together with a CA Endevor® SCM entity to which it applies. See the next
section for a description of CA Endevor® SCM entities.
PIDT Name
A PIDT name is (Required) Each request clause must identify an InfoMan PIDT table. The InfoMan API
uses this table to log CA Endevor® SCM information in InfoMan.
Parentheses are (Optional) The PIDT table name must be followed by a semicolon.
ECTRL Statement
An ECTRL statement is required and must be the final line in the control statement. It must be
followed by a semicolon.
04-May-2018 478/1109
CA Endevor® SCM - 17.0
Possible Requests
The following API requests may be defined in this block.
AACT
Add activity record creations.
Package action exit points, Create Activity, and one or more Populate blocks.
CACT
Action Change or Problem record creations.
Action exit points and one or more populate blocks.
CPKG
Package Change record creations.
Package exit points and one or more Populate blocks.
CPKGA
Package Activity record creations.
Package action exit points and one or more Populate blocks.
IACT
Action Change or Problem record inquiries.
Stand-alone action exit points.
IPKG
Package exit points.
IPKGA
Package action exit points.
Create activity.
RACT
Action Change or Problem record retrievals.
Action exit points and one or more Criteria blocks.
RPKG
Package Change record retrievals.
Package exit points and one or more Criteria blocks.
RPKGA
Package Activity record retrievals.
Package action exit points and one or more Criteria blocks.
UACT
Action Change or Problem record updates.
Action exit points, the STANDALONE keyword and one or more Populate blocks.
UPKG
Package Change record updates.
Package exit points and one or more Populate blocks.
04-May-2018 479/1109
CA Endevor® SCM - 17.0
UPKGA
Package Activity record updates.
Package action exit points and one or more Populate blocks.
Create Activity and one or more Populate blocks.
This statement identifies four Change record PIDT tables (TS0B06I, TS0B06R, TS0B06C, TS0B06U), and
indicates that the table may request any of the available API actions (Inquiry, Retrieve, Create, or
Update).
To store and maintain package and package action information in InfoMan, use this CTRL statement:
CTRL;
IPKG (TS0B06I); /* Inquiry Change table for packages */
IPKGA (TS0B07I); /* Inquiry Activity table for package actions */
RPKG (TS0B06R); /* Retrieve Change table for packages */
RPKGA (TS0B07R); /* Retrieve Activity table for package actions */
CPKG (TS0B06C); /* Change Change table for packages */
CPKGA (TS0B07C); /* Change Activity table for package actions */
UPKG (TS0B06U); /* Update Change table for packages */
UPKGA (TS0B07U); /* Update Activity table for package actions */
ECTRL;
This statement tells the InfoMan API that this E/INFO table may request access to any of four Change
record PIDT tables (TS0B06I, TS0B06R, TS0B06C, TS0B06U) for storing package information, and four
Activity record tables (TS0B07I, TS0B07R, TS0B07C, TS0B07U) for storing package action information.
Use Blocks
A Use block identifies one or more exit points where the CA Endevor SCM InfoMan Interface is to be
invoked. A table definition can have multiple Use blocks.
All exit points at which you want to communicate with InfoMan must appear in a Use block. A single
USE block can refer to one, or more than one exit point. If a Use block refers to more than one exit
point, all exit points in the Use block must:
Be of the same kind. For example, a Use block can refer to multiple stand-alone action exit points
or multiple package exit points, but cannot refer to both stand-alone action exit points and
package exit points.
Utilize the same control blocks. Actions that can appear in the same Use block are:
RETRIEVE, ARCHIVE
04-May-2018 480/1109
CA Endevor® SCM - 17.0
TRANSFER, MOVE
GENERATE, DELETE
CREATE Activity
CREATE Before
CREATE After
PDELETE Before
PDELETE After
GENPKGID
A USE statement to identify one or more exit points where the E/INFO table is to be invoked. Each
USE statement has one or more required CTRL block statements.
A NOTFOUND statement to indicate what to do if an InfoMan record does not exist for this exit
point, and which points to a Label block that specifies processing.
A FOUND statement to indicate what to do if an InfoMan record exists for this exit point, and
which points to a Label block that specifies processing.
One or more Label blocks, to specify the processing associated with the exit points named in the
USE statement.
... (action,{BEFORE}[ .,STANDALONE][,PROBLEM]));
04-May-2018 481/1109
CA Endevor® SCM - 17.0
/After/Activity, uniquely identifies a CA Endevor® SCM exit point. Valid combinations are:
Action Subparameter
Backin Before/After
Backout Before/After
Cast Before/After
Commit Before/After
Confirm After
Create Before/After
Create Activity. This exit point builds activity records for package actions at after-cast time.
Pdelete Before/After (Package Delete)
Execute Before/After
GENPKGID Before/After
Modify Before/After
Reset Before/After
Review Before/After
Ship Before/After
Add Before/After
Update Before/After
Restore Before/After
Retrieve Before/After
Archive Before/After
Generate Before/After
Delete Before/After
Move Before/After
Transfer Before/After
This example indicates that the Use block refers to a before-action exit for ADD actions, and that the
ADD actions are performed in stand-alone mode (not as part of packages).
04-May-2018 482/1109
CA Endevor® SCM - 17.0
This example indicates that the Use block applies to the after-exit point for the named actions, when
the actions are included in a package.
Once an exit point is driven, a search is made to locate the InfoMan record from the database. This
statement instructs the interface how to proceed when the InfoMan record has not been created yet.
This statement is required for:
This statement is not valid when used with the package exit points for Backout, Backin, Commit,
Confirm, Create Activity, Execute, Reset, Review, and Ship.
NOTFOUND
(Required) NOTFOUND must be the first word in this statement.
CREATE
(Optional) The CREATE keyword tells the interface to create one of the following in InfoMan:
A package change record. If you want to do this, the CTRL block must contain a CPKG statement.
A change activity record for a package action. If you want to do this, the CTRL block must contain
CPKGA and AACT statements.
A change or problem record for a stand-alone action. If you want to do this, the CTRL block must
contain a CACT statement.
The criteria for populating the new InfoMan record are contained in the block identified by the
label parameter.
If you want to update existing InfoMan records, omit CREATE from the NOTFOUND statement,
and make sure that UPKG, UPKGA, or UACT statements are in the CTRL block.
label
(Optional) This identifies the label name where execution resumes when a NOTFOUND condition
occurs. Required if CREATE is the first parameter.
RETURN
(Optional) Instructs the interface to return to CA Endevor® SCM. Examples of NOTFOUND
statements appear in the section on FOUND statements.
04-May-2018 483/1109
CA Endevor® SCM - 17.0
FOUND
(Required) FOUND must be the first word in this statement.
DELETE
(Optional) This parameter is only valid on the Package Delete (PDELETE) After exit point. This
option deletes the Package Change record along with all its corresponding activity records.
If you use this parameter, make sure that PDELETE is the first parameter in the USE statement.
label
(Optional) This identifies the label name where execution resumes when a FOUND condition
occurs. Required if DELETE is the first parameter.
RETURN
(Optional) Instructs the interface to return to CA Endevor® SCM.
This example indicates that if the interface does not find a record on the InfoMan side, it is to create
that record. The information needed to create the record can be found later in the table at label
CMD0010.
The example also indicates that if the record is found in InfoMan, the interface should execute the
processing specified in label CMD0020.
This example indicates that if the record is not found, the interface is to execute the processing
specified in label ERR0010, and that if the record is found, the interface should return to CA Endevor®
SCM.
Example
04-May-2018 484/1109
CA Endevor® SCM - 17.0
Label Blocks
Label blocks specify processing that is to occur related to the exit point in a Use block. A Label block
must be within a Use block. Multiple Label blocks are allowed per exit point.
A LABEL statement
An ELABEL statement
CPASS/CFAIL statements
TSP statements
Populate blocks
Criteria blocks
The LABEL statement marks the beginning of the block. All statements within the Label block are
processed. Once the ELABEL statement is reached, control is returned to CA Endevor® SCM unless a
CPASS/CFAIL statement is included in the block.
LABEL
04-May-2018 485/1109
CA Endevor® SCM - 17.0
LABEL
(Required) LABEL must be the first word in a Label block.
name
(Required) A 1- to 8-character alphanumeric name for the label. The name must be followed by a
semicolon.
Example
This example shows the use of a comment with the LABEL statement:
LABEL GEN0010; /* Change Record not found: Create one. */
CPASS/CFAIL Statements
Use CPASS/CFAIL statements to pass control to another Label block when the current block's ELABEL
statement is reached, based on the conditions set by the Criteria block. The syntax is:
{CPASS|CFAIL} label-name;
The following are descriptions of syntax components:
CPASS
Indicates a true condition.
CFAIL
Indicates a false condition.
label name
The up to eight character name of the label where processing resumes when the true or false
condition has been met. There can be one CPASS/CFAIL statement per Label block. The CPASS and
CFAIL statement may exist anywhere in the block, but the condition is only tested and the branch
occurs just prior to the ELABEL.
In order to code these statements, a Criteria and a Populate block must be present in the Label block.
CPASS represents a true condition and CFAIL represents a false condition. CPASS and CFAIL may be
coded independently.
Coding a null Criteria block sets a CPASS condition. However, if you want to pass control to another
Label block, you must still code the CPASS statement, specifying the Label block to which you want to
pass control.
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
04-May-2018 486/1109
CA Endevor® SCM - 17.0
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
ECRITERIA;
POPULATE;
EPOPULATE;
CFAIL ARC0022;
ELABEL;
In this example, a PIDT field in InfoMan would be checked for the value OPEN. The CFAIL statement
tells CA Endevor® SCM to execute the processing specified in Label block ARC0022 if the field does
not contain the value OPEN.
In this example, the interface first executes the processing in this Label block to create a change
record in InfoMan. The CPASS statement instructs CA Endevor® SCM to execute the processing
specified in Label block CST0020, because a null Criteria block sets a true condition.
You can use CPASS and CFAIL statements together when you want to test a CA Endevor® SCM or an
InfoMan field for the presence of a value, then execute one Label block if the value exists, and
another Label block if the value does not exist.
LABEL CRT0020; /* LOOKING FOR ACTION: ADD */
CRITERIA;
FIELD (=PACTACTN) VALUE('ADD ');
ECRITERIA;
POPULATE;
EPOPULATE;
CPASS GRP0010;
CFAIL CRT0025;
ELABEL;
In this example, CA Endevor® SCM tests the PACTACTN field for the presence of the value ADD. The
CPASS statement instructs CA Endevor® SCM to continue processing at Label block GRP0010 if ADD is
the value in this field. The CFAIL statement instructs CA Endevor® SCM to resume processing at Label
block CRT0025 if ADD is not the value in the field.
TSP Statements
There can be one TSP statement per Label block. A TSP statement must be placed before any Criteria
or Populate blocks. The syntax is:
TSP;
A TSP statement instructs the InfoMan API to invoke a TSP. The user is responsible for developing this
04-May-2018 487/1109
CA Endevor® SCM - 17.0
A TSP statement instructs the InfoMan API to invoke a TSP. The user is responsible for developing this
TSP. The TSP is invoked within the InfoMan TSP driver BLGAPI00. The user must update the InfoMan
TSP driver to include his/her TSP by including a LINK statement for transaction 111. For more
information regarding TSPs and the InfoMan see the IBM Tivoli Information Management Application
Program Interface Guide SC34-4592-00.
A TSP statement can appear only in the initial Label block of a chain of Label blocks. TSP statements
cannot be coded in a block to which control has been passed by a CPASS or CFAIL statement.
The TSP statements in this example are allowed, because LABEL (ABC) and LABEL (CDE) each start a
chain of Label blocks and therefore can each contain a TSP statement.
NOTFOUND (ABC);
FOUND (CDE);
.
LABEL ABC;
TSP;
.
CPASS FGH;
ELABEL;
LABEL CDE;
TSP;
.
CPASS KLM;
ELABEL;
The TSP statement in LABEL (CDE) below is not allowed, because LABEL (CDE) is the second block in a
chain, pointed to by the CFAIL statement in LABEL (ABC).
NOTFOUND (ABC);
FOUND (CDE);
.
LABEL ABC;
TSP;
.
CFAIL CDE;
ELABEL;
LABEL CDE;
TSP;
.
CPASS KLM;
ELABEL;
Comments
You can put comments anywhere within the E/INFO table.
A comment must begin with the character string /* and must end with the character string */.
Comments can span multiple lines. The terminating character string, */, must be on the same line.
04-May-2018 488/1109
CA Endevor® SCM - 17.0
CTRL;
IACT (TS0B06I); /* INQUIRY CHANGE FOR ACTIONS */
RACT (TS0B06R); /* RETRIEVE CHANGE FOR ACTIONS */
CACT (TS0B06C); /* CREATE CHANGE FOR ACTIONS */
UACT (TS0B06U); /* UPDATE CHANGE FOR ACTIONS */
ECTRL;
In this example, the starting string (/*) and the ending string (*/) of the comment are shown in bold.
The comment below is invalid because it appears between the end of the statement and the
semicolon that ends the statement.
CTRL;
IACT (TS0B06I) /* INQUIRY CHANGE FOR ACTIONS */; T
RC Statements
Use RC statements to specify a return code back to CA Endevor® SCM. This statement may appear
anywhere within a Label block. The syntax is:
RC (return code);
Acceptable return code values are 0 (success) or 8 (failure). If the interface returns an “8” on a before-
action or before-package exit, CA Endevor® SCM aborts the function.
Multiple RC statements are allowed within the same block. When multiple RC statements are used,
the interface returns the highest value.
04-May-2018 489/1109
CA Endevor® SCM - 17.0
POPULATE;
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=USER);
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
FIELD PANEL(BLG6DSAB) INDEX(S0E0F)
VALUE('API CREATE CHG RECORD')
EPOPULATE;
RC(0);
ELABEL;
In both cases, the RC statement instructs the interface to send a return code of 0 back to CA
Endevor® SCM when it has completed the processing specified in the Label block.
MSG Statements
Use message (MSG) statements to include a message in the CA Endevor® SCM Execution Report. This
statement may appear anywhere within a Label block. Multiple occurrences are allowed.
Note: CA Endevor® SCM keywords can be included in message text. The report prints with
the corresponding CA Endevor® SCM term. For example:
MSG ('ACTIVITY RECORD FOR CCID: =CCID MISSING');
When this message prints on the execution report, =CCID is replaced with the value of the CCID for
which the record was not found.
Example
04-May-2018 490/1109
CA Endevor® SCM - 17.0
Criteria Blocks
Use a Criteria block to specify a test that will result in a true/false condition. A test is established by
including FIELD statements in this block. If a true condition prevails, the interface populates the
InfoMan record with information from other FIELD statements, found in the Populate block.
When no test is specified in the Criteria block, a true condition is assumed to exist, and the Populate
block FIELD statements are executed automatically.
Criteria blocks are (Optional) One Criteria block is allowed per Label block.
CRITERIA
(Required) CRITERIA must be the first word in a Criteria block, and must be followed by a
semicolon.
FIELD statements
FIELD statements establish the conditions for populating InfoMan records. FIELD statements are
described in a later section.
IFYES/IFNO statements
Valid only in Criteria block FIELD statements. Used to specify processing when the test established
in the FIELD statement is true (IFYES) or false (IFNO). IFYES/IFNO statements are described in a
later section.
ECRITERIA
(Required) ECRITERIA must be the last word in a Criteria block, and must be followed by a
semicolon. If you want to populate an InfoMan record at this exit point without testing any fields,
you must code a null Criteria block. A null Criteria block looks like this:
CRITERIA;
ECRITERIA;
When coding Criteria blocks, keep in mind that the interface supports storing information only in
InfoMan X-type records (freeform text) and R-type records (Response records). Of these two record
types, the interface allows you to retrieve for scanning only the R-type records. This means that FIELD
statements in Criteria blocks should examine only InfoMan fields that contain R-type records.
Note: For more information about X-type records and R-type records, see your InfoMan
documentation.
Here is an example when there is no criteria, but the user wants to populate an InfoMan record. This
04-May-2018 491/1109
CA Endevor® SCM - 17.0
Here is an example when there is no criteria, but the user wants to populate an InfoMan record. This
use of the CRITERIA statement is common within a Label block associated with a NOTFOUND
statement, as shown below.
USE (ARCHIVE, BEFORE, STANDALONE);
NOTFOUND (CREATE,ARC0010);
FOUND (ARC0020);
LABEL ARC0010; /* CHANGE RECORD NOT FOUND: CREATE ONE */
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=USER);
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
FIELD PANEL(BLG6DSAB) INDEX(S0E0F)
VALUE('API CREATE CHG RECORD');
EPOPULATE;
RC(0);
ELABEL;
Here is an example of FIELD statements in both the Criteria and Populate blocks.
LABEL CFM0010; /* SHIP CONFIRM AFTER - LOG SECTION */
CRITERIA;
FIELD (=PECBSFNM) VALUE ('CONFIRM ');
ECRITERIA;
POPULATE;
/***************************************
* PREQDEST: SHIP DESTINATION *
* PREQSCNF: SHIP CONFIRMATIN TYPE *
* PREQSRES: SHIP CONFIRMATION RESULTS *
* PREQSRCV: SHIP CONFIRM RC VALUE *
****************************************/
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('SHIP: DESTINATION =PREQDEST CONFIRM TYPE =PREQS CNF') -
(' CONFIRMATION RESULTS =PREQSRES =PREQSRCV');
EPOPULATE;
ELABEL;
Here is an example that includes IFYES/IFNO conditions in the Criteria block, in addition to FIELD
statements.
LABEL RET0022; /* STATUS NOT OPEN - CHECK FOR INITIAL */
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('INITIAL');
IFNO;
RC (8);
MSG ('INVALID STATUS - MUST BE INITIAL OR OPEN');
EIF;
ECRITERIA;
POPULATE;
EPOPULATE;
ELABEL;
04-May-2018 492/1109
CA Endevor® SCM - 17.0
One Populate block is allowed per Label block, and must follow the Criteria block. If you include a
Populate block, you must also include a Criteria block.
POPULATE
(Required) POPULATE must be the first word in a Populate block, and must be followed by a
semicolon
FIELD statements
FIELD statements establish the information to be recorded in InfoMan records. FIELD statements
are described in a later section.
EPOPULATE
(Required) EPOPULATE must be the last word in a Criteria block, and must be followed by a
semicolon. If you do not want to populate an InfoMan record at this exit point, you must code a
null Populate block. A null populate block looks like this:
POPULATE;
EPOPULATE;
Note: The interface supports only InfoMan X-type records (freeformtext) and R-type
records (Response records). This means that when coding FIELD statements in a Populate
block, you can refer only to InfoMan fields that store X-type or R-type information.
Note: For more information about X-type records and R-type records, see your InfoMan
documentation.
04-May-2018 493/1109
CA Endevor® SCM - 17.0
EIF;
ECRITERIA;
POPULATE;
EPOPULATE;
ELABEL;
FIELD Statements
FIELD statements may only appear in Criteria and Populate blocks.
The interface uses Criteria block FIELD statements to determine a true or false condition. A true
condition results in the execution of the Populate Block.
When FIELD statements appear in the Populate block, the interface uses them to update an
InfoMan database record.
04-May-2018 494/1109
CA Endevor® SCM - 17.0
LABEL CRT0010; /* MAINLINE - ALL PKG ACTION POINTS. */
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=PECBUSER);
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
FIELD PANEL(BLG6DSAB) INDEX(S0E0F)
TEXT('CCID: =PACTCCID IN PACKAGE: =PECBPKID');
FIELD PANEL(BLG6PTYP) INDEX(S0C09) VALUE('PKG/ACT');
EPOPULATE;
CPASS CRT0020;
ELABEL;
Note: You cannot specify FIELD statements in a Criteria block associated with a Create
Activity Use block.
04-May-2018 495/1109
CA Endevor® SCM - 17.0
FIELD PANEL(pname) INDEX(s-word) [LENGTH(length)]
VALUE({CA Endevor® SCM field|'literals'|=DATE|=TIME}); or
FIELD PANEL(pname) INDEX(s-word) TEXT(text);
Note: Population of CA Endevor® SCM field control blocks is not allowed. The syntax
components are explained in the next section.
When used in a Criteria block FIELD statement, this identifies the field against which the string in
the VALUE clause is tested.
When used in a Populate block FIELD statement, this identifies the field to be populated by the
string in the VALUE or TEXT clause.
The Pname identifies the InfoMan panel containing the field to be updated. The S-word identifies the
field to be updated. These fields must also be defined in the appropriate PIDT table.
The following table shows how the MOVE action and compare logic use the length value.
If the LENGTH value is Then the MOVE action or compare logic uses
Greater than the target The target length
Less than the target The LENGTH value, with any remaining fields padded with blanks.
Omitted The smaller of source or target
Note: When CA Endevor® SCM fields are converted from binary to character form, all
leading zeros are stripped. For example, 'x0010' becomes C'16'. During a compare
operation between an InfoMan field and a CA Endevor® SCM field that has undergone a
binary to character conversion, all leading zeros in the InfoMan field are stripped before
the comparison.
04-May-2018 496/1109
CA Endevor® SCM - 17.0
Literal
Alphanumeric values enclosed in single quotes. For example: VALUE ('UPDATE ')
Blanks
Use this value to test whether the field is empty. A true condition exists when the field contains
blanks.
Nonblank
Use this value to test for the presence of information in a field. A true condition exists when the
field contains any non-blank characters.
Literal
Alphanumeric values enclosed in single quotes. For example: VALUE ('UPDATE ')
=DATE
Represents the current date. When used, the current date is retrieved to populate an InfoMan
database field. Format: mm/dd/yy.
=TIME
Represents the current time. When used, the current time is retrieved to populate an InfoMan
database field. Format: hh:mm.
The IFYES statement is invoked when the test of the InfoMan or CA Endevor® SCM field results in
a true condition.
The IFNO statement is invoked when the test of the InfoMan or CA Endevor® SCM field results in
a false condition.
04-May-2018 497/1109
CA Endevor® SCM - 17.0
TEXT Clauses
Use TEXT clauses to specify information to be used to populate InfoMan fields. You must use this
format against InfoMan fields defined as freeform text fields. This format is allowed against other
field types.
The text data must be enclosed in single quotes. You can specify text to continue on the same line.
For example:
TEXT ('This is an example of a free form text build setup ') -
('statement line one')
You can include a CA Endevor® SCM field equate in specified message text:
TEXT('CCID: =PACTCCID IN PACKAGE: =PECBPKID');
The text recorded in InfoMan for this example includes the CCID for the package action in place of
the =PACTCCID equate, and the ID of the associated package in place of the =PECBPKID equate.
Actions that can appear together in Use blocks $ENVDS $ELMDS $FILDS $ECBDS $REQPDS
src tgt src tgt src tgt src tgt src tgt
ADD, UPDATE x x x x x
RETRIEVE, ARCHIVE x x x x x
GENERATE, DELETE x x x x
04-May-2018 498/1109
CA Endevor® SCM - 17.0
Actions that can appear together in Use blocks $ENVDS $ELMDS $FILDS $ECBDS $REQPDS
src tgt src tgt src tgt src tgt src tgt
MOVE, TRANSFER, RESTORE xx xx x x
The sections that follow explain the specific fields from each control block, and the equate values
used in the E/INFO table syntax to reference these fields.
This $ENVDS field Contains this source or target information And has these equate values
ENVSITE CA Endevor® SCM site ID EV1SITE (source)
EV2SITE (target)
ENVENVM Environment name EV1ENV (source)
EV2ENV (target)
ENVSYSTM System name EV1SYS (source)
EV2SYS (target)
ENVSUBSY Subsystem name EV1SUB (source)
EV2SUB (target)
ENVTYPE Type name EV1TYP (source)
EV2TYP (target)
ENVSTAGE Stage name EV1STAGE (source)
EV2STAGE (target)
ENVSTGID Stage number for the action (1 or 2) EV1STG# (source) EV2STG#
(target)
ENVSTGCD Stage ID EV1STGID (source)
EV2STGID (target)
ENVELEMT Name of the element EV1ELM (source)
EV2ELM (target)
ENVEVER Version number for the element EV1VER (source)
EV2VER (target)
ENVELVL Level for the element EV1LVL (source)
EV2LVL (target)
04-May-2018 499/1109
CA Endevor® SCM - 17.0
This $ENVDS field Contains this source or target information And has these equate values
ENVSPEC Indicates the kind of location. The location can EV1LOC (source)
be:
EV2LOC (target)
A CA Endevor® SCM environment
EV2ELMLN (target)
ENVEAOFF Full element name EV1ELMFN (source)
EV2ELMFN (target)
This Contains this source or target information And has these equate
$ELMDS values
field
ELMNAME First ten characters of the element name EL1NAME (source)
EL2NAME (target)
ELMMVERS Element version EL1VER (source)
EL2VER (target)
ELMMLLVL Element level EL1LVL (source)
EL2LVL (target)
ELMM1STL Base level of the element at this location EL1BASE (source)
EL2BASE (target)
ELMMINS Number of inserts EL1INS (source)
EL2INS (target)
ELMMDEL Number of deletes EL1DEL (source)
EL2DEL (target)
ELMCCID CCID associated with the element EL1CCID (source)
EL2CCID (target)
ELMMBTOT Number of statements in the base level of the element EL1BTOT (source)
EL2BTOT (target)
04-May-2018 500/1109
CA Endevor® SCM - 17.0
This Contains this source or target information And has these equate
$ELMDS values
field
ELMMBDTE Date associated with the base level EL1BDATE (source)
EL2BDATE (target)
ELMMBTIM Time associated with the base level EL1BTIME (source)
EL2BTIME (target)
ELMBCOM Comment associated with the base level EL1BCOM (source)
EL2BCOM (target)
ELMBUSID User ID associated with the base level EL1BUSER (source)
EL2BUSER (target)
ELMNOSRC Element NoSource indicator flag EL1NOSRC (source)
EL2NOSRC (target)
ELMPUSID User ID associated with the last generate of the element EL1GUSER (source)
EL2GUSER (target)
ELMPDSTP Date the element was last generated EL1GDATE (source)
EL2GDATE (target)
ELMPTSTP Time the element was last generated EL1GTIME (source)
EL2GTIME (target)
ELMPRFLG Last processor executed against the element: EL1PFG (source)
1--processor failed
EL2PDATE (target)
ELMLPROT Time of last processor execution EL1PTIME (source)
EL2PTIME (target)
ELMLPROU User ID associated with last processor executed against the EL1PUSER (source)
element
04-May-2018 501/1109
CA Endevor® SCM - 17.0
This Contains this source or target information And has these equate
$ELMDS values
field
EL2PUSER (target)
ELMLPRON Name of the processor last run against the element EL1PNAME (source)
EL2PNAME (target)
ELMMPRC Processor return code EL1PRC (source)
EL2PRC (target)
ELMPCOM Comment associated with the last action that generated the EL1PCOM (source)
element
EL2PCOM (target)
ELMMRC CA Endevor® SCM return code (NDVR RC) for the last execution EL1CRC (source)
of a processor against the element
EL2CRC (target)
ELMFDSN Name of the data set from which the element was last added, EL1DSN (source)
updated, or restored
EL2DSN (target)
ELMFMBR Member name of the element before it was last added, EL1MBR (source)
updated, or restored
EL2MBR (target)
ELMMVDTE Date element was last moved EL1MDATE (source)
EL2MDATE (target)
ELMMVTIM Time element was last moved EL1MTIME (source)
EL2MTIME (target)
ELMMUSID User ID associated with the last move of the element EL1MUSER (source)
EL2MUSER (target)
ELMRDSTP Date element was last retrieved EL1RDATE (source)
EL2RDATE (target)
ELMRTSTP Time element was last retrieved EL1RTIME (source)
EL2RTIME (target)
ELMRIID User ID associated with the last retrieve of the element EL1RUSER (source)
EL2RUSER (target)
ELMRCOM Comment associated with the last retrieve of the element EL1RCOM (source)
EL2RCOM (target)
ELMTDSN Name of the data set to which the element was last retrieved EL1RDSN (source)
EL2RDSN (target)
04-May-2018 502/1109
CA Endevor® SCM - 17.0
This Contains this source or target information And has these equate
$ELMDS values
field
ELMTMBR Member name of the element at the target data set of the last EL1RMBR (source)
retrieve
EL2RMBR (target)
ELMCCOM Current level comment for the element EL1CCOM (source)
EL2CCOM (target)
ELMMLDTE Date associated with the current level of the element EL1LDATE (source)
EL1LDATE (target)
ELMMLTME Time associated with the current level of the element EL1LTIME (source)
EL2LTIME (target)
ELMLUSID User ID associated with the current level of the element EL1LUSER (source)
EL2LUSER (target)
ELMMLACT Most recent action against the element EL1LACT (source)
EL2LACT (target)
ELMMLTOT Total number of source statements in the current level of the EL1LTOT (source)
element
EL2LTOT (target)
ELMRCCID CCID associated with the last RETRIEVE action against the EL1RCCID (source)
element
EL2RCCID (target)
ELMGCCID CCID associated with the last GENERATE action against the EL1GCCID (source)
element
EL2GCCID (target)
ELMODACT Last action executed against the element that modified the EL1LMACT (source)
element
EL2LMACT (target)
ELMLCCID CCID associated with the last action that modified the element EL1LCCID (source)
EL2LCCID (target)
ELMLCOMM Comment associated with the last action that modified the EL1LCOMM (source)
element
EL2LCOMM (target)
ELMLADT Date associated with the last action that modified the element EL1MLADT (source)
EL2MLADT (target)
ELMLATM Time associated with the last action that modified the element EL1MLATM (source)
EL2MLATM (target)
ELMLUID User ID associated with the last action that modified the EL1MLUID (source)
element
04-May-2018 503/1109
CA Endevor® SCM - 17.0
This Contains this source or target information And has these equate
$ELMDS values
field
EL2MLUID (target)
ELMUPDT Element name in the delta library EL1NUPDT (source)
EL2NUPDT (target)
ELMBASE Element name in the base library EL1NBASE (source)
EL2NBASE (target)
ELMIPCTG Percentage of inserts deleted EL1IPCTG (source)
EL2IPCTG (target)
ELMDPCTG Percentage of deletes inserted. EL1DPCTG (source)
EL2DPCTG (target)
ELMFPESD Name of footprinted object (ESD) module EL1FPESD (source)
EL2FPESD (target)
ELMEDFMT Delta format for the element EL1EDFMT (source)
EL2EDFMT (target)
ELMLPROV Version number of last processor used against this element. EL1LPROV (source)
EL2LPROV (target)
ELMPROL Level number of last processor used against this element EL1PROL (source)
EL2PROL (target)
ELMFMID Record format ID EL1FMID (source)
EL2FMID (target)
ELMXDNAM Component list delta member name EL1XDNAM (source)
EL2XDNAM (target)
ELMXBVER Component list delta version number EL1XBVER (source)
EL2XBVER (target)
ELMXBTOT Component list base total EL1XBTOT (source)
EL2XBTOT (target)
ELMXLTOT Component list last level total EL1XLTOT (source)
EL2XLTOT (target)
ELMXBLVL Component list base level number EL1XBLVL (source)
EL2XBLVL (target)
04-May-2018 504/1109
CA Endevor® SCM - 17.0
This Contains this source or target information And has these equate
$ELMDS values
field
ELMXLLVL Component list last level number EL1XLLVL (source)
EL2XLLVL (target)
ELMXINS Inserts at last level EL1XINS (source)
EL2XINS (target)
ELMXDLS Deletes at last level EL1XDLS (source)
EL2XDLS (target)
ELMXRGIN Component list regression insert percent EL1XRGIN (source)
EL2XRGIN (target)
ELMXRGDL Component list regression delete percent EL1XRGDL (source)
EL2XRGDL (target)
ELMXBDTE Component list base date EL1XBDTE (source)
EL2XBDTE (target)
ELMXBTIM Component list base time EL1XBTIM (source)
EL2XBTIM (target)
ELMXLDTE Component list last level date EL1XLDTE (source)
EL2XLDTE (target)
ELMXLTIM Component list last level time EL1XLTIM (source)
EL2XLTIM (target)
ELMXFLAG Component list component status flag EL1XFLAG (source)
EL2XFLAG (target)
ELMXDFMT Component list delta format EL1XDFMT (source)
EL2XDFMT (target)
ELMXUPDT Indicates whether component list base is in delta library EL1XUPDT (source)
EL2XUPDT (target)
ELMSPKG ID of the last processed package that included the source for EL1SPKG (source)
this element
EL2SPKG (target)
ELMSPKGT Time stamp of the last processed package that included the EL1SPKGT (source)
source for this element
EL2SPKGT (target)
ELMOPKG ID of package associated with the outputs of this element EL1OPKG (source)
04-May-2018 505/1109
CA Endevor® SCM - 17.0
This Contains this source or target information And has these equate
$ELMDS values
field
EL2OPKG (target)
ELMOPKGT Time stamp of package associated with the outputs of this EL1OPKGT (source)
element
EL2OPKGT (target)
ELMPRGRP Processor group name EL1PRGRP (source)
EL2PRGRP (target)
ELMFFFLG From file type flag EL1FFFLG (source)
EL2FFFLG (target)
ELMTFFLG To file type flag EL1TFFLG (source)
EL2TFFLG (target)
ELMFPAOFF From path name length EL1FPALN (source)
EL2FPALN (target)
ELMFPAOFF From path name EL1FPANM (source)
EL2FPANM (target)
ELMFNAOFF From file name length EL1FFILN (source)
EL2FFILN (target)
ELMFNAOFF From file name EL1FFINM (source)
EL2FFINM (target)
ELMTPAOFF To path name length EL1TPALN (source)
EL2TPALN (target)
ELMTPAOFF To path name EL1TPANM (source)
EL2TPANM (target)
ELMTNAOFF To file name length EL1TFILN (source)
EL2TFILN (target)
ELMTNAOFF To file name EL1TFINM (source)
EL2TFINM (target)
ELMEAOFF Element name length EL1ELMLN (source)
EL2ELMLN (target)
ELMEAOFF Full element name EL1ELMFN (source)
EL2ELMFN (target)
04-May-2018 506/1109
CA Endevor® SCM - 17.0
This Contains this source or target information And has these equate
$ELMDS values
field
ELMBVERS Element base version number EL1BVERS(source)
EL2BVERS (target)
ELMXLVER Component last version level EL1XLVER(source)
EL2XLVER(target)
This $FILDS Contains this source or target information And has these equate
field values
FILDSN Data set name of the external file used by the current FI1DSN (source)
action
FI2DSN (target)
FILDSMEM Member name of the element associated with the FI1MBR (source)
current action
FI2MBR (target)
FILDDN DDname associated with the data set named above FI1DDN (source)
FI2DDN (target)
FILDSTY The kind of data set (DA, PSU, PO, IS, and the like) FI1DTY (source)
FI2DTY (target)
FILPAOFF Path name length FI1PALN (source)
FI2PALN (target)
FILNAOFF File name length FI1PANM (source)
FI2PANM (target)
FILPAOFF File name FI1PANM (source)
FI2PANM (target)
04-May-2018 507/1109
CA Endevor® SCM - 17.0
Note: The EXITRC equate value maps to the ECBRTCD field in the $ECBDS control block.
This field is updated by the RC keyword value in the E/INFO table syntax.
04-May-2018 508/1109
CA Endevor® SCM - 17.0
Package actions that can appear together in Use blocks $PECBDS $PREQPDS $PHDRDS $PACTREQ
BACKIN, BACKOUT, CAST, COMMIT, EXECUTE, RESET, X X X
REVIEW, SHIP for before-exit and after-exit points
CREATE/MODIFY
before X X
after X X X
CREATE ACTIVITY X X X X
GENPKGID
before X X
after X X
PDELETE
before X X X
after X X
Not all the fields in the $PECBDS control block are available. Those fields that are available are shown
in the following list:
This $PECBDS field Contains this information And has this equate value
PECBPKID Package ID PECBPKID
PECBFNCD Package function code PECBFNCD
PECBSFCD Package subfunction code PECBFSCD
PECBBACD Package before/after code PECBBACD
PECBFNNM Package function literal PECBFNNM
04-May-2018 509/1109
CA Endevor® SCM - 17.0
This $PECBDS field Contains this information And has this equate value
PECBSFNM Package subfunction literal PECBSFNM
PECBBANM Package before/after literal PECBBANM
PECBACTE Action record existence flag PECBACTE
PECBAPPE Approver record existence flag PECBAPPE
PECBBODE Backout record existence flag PECBBODE
PECBNDRC CA Endevor® SCM high return code PECBNDRC
PECBNDAB CA Endevor® SCM abend code PECBNDAB
PECBNDMG CA Endevor® SCM message text PECBNDMG
PECBNDML CA Endevor® SCM message text length PECBNDML
PECBUSER TSO user or batch job name PECBUSER
PECBMODE Mode setting (online or batch) PECBMODE
The request for data flags (PECBACTR through PECBSCLR), as well as PECBRQRC, the return code
field for user requests for data.
The following fields are set by the E/INFO interface, through the table syntax:
PECBRTCD
PECBMGCD
PECBMGLN
PECBMSG
$PREQPDS
Use these equate values for $PREQPDS fields.
This $PREQPDS field Contains this information And has this equate value
PREQCOMM Package comment PREQCOMM
PREQBOEN Backout enabled flag PREQBOEN
PREQDEL Delete enabled flag PREQDEL
PREQPSHR Sharable package flag PREQPSHR
PREQPAPD Append package flag PREQPAPD
PREQEWSD Execution window start date PREQEWSD
PREQEWST Execution window start time PREQEWST
04-May-2018 510/1109
CA Endevor® SCM - 17.0
This $PREQPDS field Contains this information And has this equate value
PREQEWED Execution window end date PREQEWED
PREQEWET Execution window end time PREQEWET
PREQIPKG Source package ID (copy subfunction) PREQIPKG
PREQDEST Shipment destination PREQDEST
PREQSTYP Shipment type PREQSTYP
PREQSCMP Ship complementary data set flag PREQSCMP
PREQSCNF Ship confirmation type PREQSCNF
PREQSRES Ship confirmation result PREQSRES
PREQSRCV Ship confirmation return code PREQSRCV
PREQAPGP Override approver group PREQAPGP
PREQAPID Override approver ID PREQAPID
$PHDRDS
Use these equate values for $PHDRDS fields.
This $PHDRDS field Contains this information And has this equate value
PHDRTYPE Package type (standard or emergency). PHDRTYPE
PHDRSTAT Package status PHDRSTAT
PHDRBOST Package backout status PHDRBOST
PHDRCRD Package creation date PHDRCRD
PHDRCRT Package creation time PHDRCRT
PHDRXRC Package execution return code PHDRXRC
PHDRPUD Date of last update to package SCL PHDRPUD
PHDRPUT Time of last update to package SCL PHDRPUT
PHDRCD Cast date PHDRCD
PHDRCT Cast time PHDRCT
PHDRAD Final approval/denial date PHDRAD
PHDRAT Final approval/denial time PHDRAT
PHDRWSD Execution window start date PHDRWSD
PHDRWST Execution window start time PHDRWST
PHDRWED Execution window end date PHDRWED
PHDRWET Execution window end time PHDRWET
PHDRXD Execution date PHDRXD
PHDRXT Execution time PHDRXT
PHDRCMD Commit date PHDRCMD
PHDRCMT Commit time PHDRCMT
04-May-2018 511/1109
CA Endevor® SCM - 17.0
This $PHDRDS field Contains this information And has this equate value
PHDRBOD Backout date PHDRBOD
PHDRBOT Backout time PHDRBOT
PHDRBID Backin date PHDRBID
PHDRBIT Backin time PHDRBIT
PHDREXD Date when execution completed PHDREXD
PHDREXT Time when execution completed PHDREXT
$PACTREQ
Use these equate values for $PACTREQ fields.
04-May-2018 512/1109
CA Endevor® SCM - 17.0
04-May-2018 513/1109
CA Endevor® SCM - 17.0
An E/INFO Interface Syntax Errors report, listing any messages produced by the utility.
Note: For more information, consult InfoMan experts at your site, or IBM Tivoli
Information Management Application Program Interface Guide SC34-4592-00.
The InfoMan database consists of 16 record types. The interface uses the following four InfoMan
record types to store CA Endevor® SCM information.
Problem records, to record information about stand-alone actions. Stand-alone actions are
actions that are not associated with a package.
04-May-2018 514/1109
CA Endevor® SCM - 17.0
The Add Change Activity record, to relate package actions to a parent package record.
Four actions can be performed against each record: data can be created (Create), data can be
updated (Update), inquiries can be made against the record (Inquiry), and the record can be retrieved
(Retrieve). The CA Endevor SCM InfoMan Interface supports all these access modes.
InfoMan allows logical views of these records, in the form of Program Interface Data Table (PIDT)
tables. PIDT tables define data fields that can be passed between an application (in this case CA
Endevor® SCM) and the API.
InfoMan comes with a predefined PIDT table for each record type and use. For example, the Problem
record type has four PIDT tables: Problem record create, Problem record update, Problem record
inquiry, and Problem record retrieve. Each PIDT table provides a view of the problem record.
The InfoMan API uses PIDT tables to access or update data from the InfoMan database.
You can run the interface with the standard PIDT tables, or you can create your own. If you create
your own PIDT tables, you must do so for each record type/action that you intend to use, and each
custom table must contain certain required fields. These fields are listed later in this chapter.
These PIDT definition statements are fed into the InfoMan BLGUT8 batch utility. This utility produces
two machine-loadable data structures for each table definition: the PIDT (Program Interface Data
Table) and the Program Interface Pattern Table (PIPT). The PIPT defines the pattern validation criteria
for each field found in the PIDT.
Note: It may be necessary to obtain detail information from both the CA Endevor® SCM
and the InfoMan administrators.
2. Decide which InfoMan record type you want to use to record stand-alone action information:
Problem records or Change records.
3. Make sure that all InfoMan fields required by the interface are available.
4. Decide which functions you want to perform against the record types you have selected:
04-May-2018 515/1109
CA Endevor® SCM - 17.0
1. After making these decisions, build PIDT tables for the record types and functions that you
plan to use. For example, if you decide to record CA Endevor® SCM package information in
InfoMan, you would create PIDT tables for:
If you are not using the standard PIDT tables, first complete the checklist in the previous section. You
must then build PIDT tables for the record types (Problem, Change, or Change Activity) that you want
to use, and the actions (Inquiry, Create, Update, Retrieve) that you want the interface to perform.
NotFor more information about building PIDT tables, see IBM Tivoli Information
Management Application Program Interface Guide SC34-4592-00.
Certain fields must appear in these PIDT tables. These required fields are listed in this section, for
each possible record type and use.
NotA four-character (for example IACT) or five-character (for example CPKGA) identifier
appears in the following lists. These identifiers are used in the Control block of the batch
utility syntax to build the E/INFO table. These identifiers are explained in Chapter 3,
"Setting Up the CA Endevor® SCM INFO Table."
04-May-2018 516/1109
CA Endevor® SCM - 17.0
04-May-2018 517/1109
CA Endevor® SCM - 17.0
04-May-2018 518/1109
CA Endevor® SCM - 17.0
04-May-2018 519/1109
CA Endevor® SCM - 17.0
The syntax template described in this chapter is contained in member EISCRIP1 in iprfx.iqual.
CSIQOPTN. The table built using this syntax updates/references InfoMan Change records. A syntax
template for utilizing Problem records is provided in member EISCRIP2 in iprfx.iqual.CSIQOPTN.
If you have not modified standard InfoMan, you can use these syntax templates as-is. Consider,
however, reviewing the syntax, editing it as necessary, before submitting it to the Batch Utility.
This sample table syntax uses fields that exist in both Change and Problem record types. If you
customize this sample syntax, do not assume that all Change record fields are also defined within
Problem records.
The following pages contain a walk-through of EISCRIP1. Even if you want to use InfoMan Problem
records (EISCRIP2), studying the walk-through will be beneficial.
The TABLE NAME clause starts the table, and names it. In this case the name of the table is ENDEVO2.
Note: For more information, see The Table Statement (see page 476).
CTRL;
IACT (TS0B06I); /* INQUIRY CHANGE FOR ACTIONS */
RACT (TS0B06R); /* RETRIEVE CHANGE FOR ACTIONS */
CACT (TS0B06C); /* CREATE CHANGE FOR ACTIONS */
UACT (TS0B06U); /* UPDATE CHANGE FOR ACTIONS */
ECTRL;
This Control block indicates that CA Endevor® SCM may request the InfoMan API to:
04-May-2018 520/1109
CA Endevor® SCM - 17.0
Note: For more information, see The Control Block (see page 477).
USE(ADD,BEFORE,STANDALONE);
This USE statement indicates that the processing in this Use block applies to the before-exit point for
stand-alone ADD actions.
Note: For more information, see Use Blocks (see page 480).
NOTFOUND (CREATE,ADD0010);
FOUND (ADD0020);
If there is no Change record in InfoMan for the CCID associated with an ADD action, the interface
is to create a record, using the processing specified in Label block ADD0010.
If there is a record in InfoMan for the CCID associated with an ADD action, the interface is to
execute the processing specified in Label block ADD0020.
Note: For more information, see The FOUND Statement (see page 484).
LABEL ADD0010; /* CHANGE RECORD NOT FOUND: CREATE ONE */
This LABEL statement starts the Label block referred to by the NOTFOUND statement earlier in the
syntax.
Note: For more information, see Label Blocks (see page 485).
CRITERIA;
ECRITERIA;
Even if there are no criteria for populating an InfoMan record, there must be a Criteria block within a
Label block, if that block also contains a POPULATE statement. When there are no criteria, code the
Criteria block this way.
04-May-2018 521/1109
CA Endevor® SCM - 17.0
Note: For more information, see Criteria Blocks (see page 491).
POPULATE;
This statement starts a Populate block. The FIELD and INDEX statements in a Populate block specify
the fields to be populated in InfoMan. The VALUE statements specify the values to use to populate
those fields.
Note: For more information, see The Populate Block (see page 492).
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=USER);
This statement tells the InfoMan API to populate the BLG6REQN field (index S0B59) with the CA
Endevor® SCM user ID.
Note: For more information, see FIELD Statements (see page 494).
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
This statement tells the InfoMan API to populate the BLG6STAT field (index S0BEE) with the literal
OPEN.
FIELD PANEL(BLG6DSAB) INDEX(S0E0F)
VALUE('API CREATE CHG RECORD');
This statement tells the InfoMan API to populate the BLG6DSAB field (index S0E0F) with the text API
CREATE CHG RECORD.
Note: For more information, see FIELD Statements (see page 494).
EPOPULATE;
Note: For more information, see The Populate Block (see page 492).
RC(0);
04-May-2018 522/1109
CA Endevor® SCM - 17.0
This statement tells the API to send a return code of zero back to CA Endevor® SCM after successfully
executing the processing in this Label block.
ELABEL;
Note: For more information, see Label Blocks (see page 485).
LABEL ADD0020; /* CHANGE RECORD FOUND */
This statement starts the label block referenced in the FOUND statement earlier in the syntax.
Note: For more information, see Label Blocks (see page 485).
RC (0);
This statement tells the API to send a return code of zero back to CA Endevor® SCM after successfully
executing the processing in this Label block.
CRITERIA;
This is a required statement to start a Criteria block for this Label block.
Note: For more information, see Criteria Blocks (see page 491).
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
This statement tells the interface to query field BLG6STAT (index S0BEE) in the InfoMan Change
record associated with the CCID for this ADD action. If the value in the field is the literal OPEN, the
criteria block is considered true. In this case, this means that it considers the record as found.
04-May-2018 523/1109
CA Endevor® SCM - 17.0
Note: For more information, see FIELD Statements (see page 494).
ECRITERIA;
Note: For more information, see Criteria Blocks (see page 491).
POPULATE;
EPOPULATE;
Even if you do not wish to populate an InfoMan record when a Criteria block is true, you must include
a Populate block with that Criteria block. This is the way to code a null Populate block.
Note: For more information, see The Populate Block (see page 492).
CFAIL ADD0022;
This CFAIL statement tells the interface to execute the processing specified in Label block ADD0022 if
the Criteria block is false. This would be the case in this example if the InfoMan field BLG6STAT (index
S0BEE) did not contain the value OPEN.
Note: For more information, see CPASS/CFAIL Statements (see page 486).
ELABEL;
Note: For more information, see The ELABEL Statement (see page 486).
LABEL ADD0022; /* STATUS NOT OPEN - CHECK FOR INITIAL */
Note: For more information, see Label Blocks (see page 485).
04-May-2018 524/1109
CA Endevor® SCM - 17.0
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('INITIAL');
IFNO;
RC (8);
MSG ('INVALID STATUS - MUST BE INITIAL OR OPEN');
EIF;
ECRITERIA;
This Criteria block tells the interface to query field BLG6STAT (index S0BEE) in the InfoMan Change
record associated with the CCID for this ADD action.
If the value in the field is INITIAL, the criteria block is considered true, and processing continues
with the POPULATE statement.
If the value in the field is not INITIAL, the interface executes the IFNO statement, passing a return
code of 8 back to CA Endevor® SCM and issuing the message INVALID STATUS - MUST BE INITIAL
OR OPEN.
POPULATE;
EPOPULATE;
Even if you do not wish to populate an InfoMan record when a Criteria block is true, you must include
a Populate block with that Criteria block. This is the way to code a null Populate block.
Note: For more information, see The Populate Block (see page 492).
ELABEL;
Note: For more information, see The ELABEL Statement (see page 486).
EUSE;
This statement ends the Use block for the before-exit point for stand-alone ADD actions.
Note: For more information, see The EUSE Statement (see page 484).
USE (ADD, AFTER, STANDALONE);
This USE statement starts another Use block. The processing in this Use block is to be invoked for the
after-exit point for stand-alone ADD actions.
Note: For more information, see The USE Statement (see page 481).
04-May-2018 525/1109
CA Endevor® SCM - 17.0
Note: For more information, see The USE Statement (see page 481).
FOUND (ADD0010);
NOTFOUND (RETURN);
If there is a record in InfoMan for the CCID associated with an ADD action, the interface is to
execute the processing specified in Label block ADD0010.
If there is no Change record in InfoMan for the CCID associated with an ADD action, the interface
is to return to CA Endevor® SCM.
Note: For more information, see The FOUND Statement (see page 484).
LABEL ADD0010;
This statement starts Label block ADD0010, referenced in the FOUND statement earlier in the Use
block.
Note: For more information, see Label Blocks (see page 485).
CRITERIA;
ECRITERIA;
Grouping the CRITERIA and ECRITERIA statements this way indicates that there are no criteria to be
satisfied after a record is found. This tells the interface to execute the processing specified in the
Populate block.
Note: For more information, see Criteria Blocks (see page 491).
POPULATE;
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('ACTION PROCESSING COMPLETED RC = =ACTRC')
TEXT ('ELEMENT: =EV2ENV / =EV2SYS / =EV2SUB ') -
('/ =EV2TYP / =EV2STAGE / =EV2ELMFN')
TEXT ('ACTION: =ACTION USER: =USER DATE: =DATE ') -
('TIME: =TIME');
EPOPULATE;
This POPULATE statement tells the InfoMan API to populate field BLG0C010 (index S0E01) with a
three-line message.
There is one TEXT statement for each line. Lines are continued by placing a hyphen as the last
04-May-2018 526/1109
CA Endevor® SCM - 17.0
There is one TEXT statement for each line. Lines are continued by placing a hyphen as the last
character in the first line. Also note that there is only one semicolon for all three TEXT statements,
located at the end of the last one.
The message is built using information from CA Endevor® SCM control blocks:
Line 2 uses the EV2ENV, EV2SYS, EV2SUB, EV2TYP, EV2STAGE, and EV2ELMFN fields from the
$ENVDS block.
Line 3 uses the ACTION, USER, DATE, and TIME fields from the $ENVDS block.
ELABEL;
Note: For more information, see The ELABEL Statement (see page 486).
EUSE; This statement ends the Use block for the after-exit point for stand-alone ADD actions.
Note: For more information, see The EUSE Statement (see page 484).
This concludes the annotated portion of the syntax example. Sample syntax for the remaining stand-
alone actions is shown on the following table.
USE(ADD, BEFORE, STANDALONE);
NOTFOUND (CREATE,ADD0010);
FOUND (ADD0020);
LABEL ADD0010; /* CHANGE RECORD NOT FOUND: CREATE ONE */
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=USER);
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
FIELD PANEL(BLG6DSAB) INDEX(S0E0F)
VALUE('API CREATE CHG RECORD');
EPOPULATE;
RC(0);
ELABEL;
LABEL ADD0020; /* CHANGE RECORD FOUND */
RC (0);
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
ECRITERIA;
POPULATE;
EPOPULATE;
CFAIL ADD0022;
ELABEL;
LABEL ADD0022; /* STATUS NOT OPEN - CHECK FOR INITIAL */
CRITERIA;
04-May-2018 527/1109
CA Endevor® SCM - 17.0
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('INITIAL');
IFNO;
RC (8);
MSG ('INVALID STATUS - MUST BE INITIAL OR OPEN');
EIF;
ECRITERIA;
POPULATE;
EPOPULATE;
ELABEL;
EUSE;
USE (ADD, AFTER, STANDALONE);
FOUND (ADD0010);
NOTFOUND (RETURN);
LABEL ADD0010;
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('ACTION PROCESSING COMPLETED RC = =ACTRC')
TEXT ('ELEMENT: =EV2ENV / =EV2SYS / =EV2SUB ') -
('/ =EV2TYP / =EV2STAGE / =EV2ELMFN')
TEXT ('ACTION: =ACTION USER: =USER DATE: =DATE ') -
('TIME: =TIME');
EPOPULATE;
ELABEL;
EUSE;
USE (UPDATE, BEFORE, STANDALONE);
NOTFOUND (CREATE,UPT0010);
FOUND (UPT0020);
LABEL UPT0010; /* CHANGE RECORD NOT FOUND: CREATE ONE */
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=USER);
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
FIELD PANEL(BLG6DSAB) INDEX(S0E0F)
VALUE('API CREATE CHG RECORD');
EPOPULATE;
RC(0);
ELABEL;
LABEL UPT0020; /* CHANGE RECORD FOUND */
RC (0);
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
ECRITERIA;
POPULATE;
EPOPULATE;
CFAIL UPT0022;
ELABEL;
LABEL UPT0022; /* STATUS NOT OPEN - CHECK FOR INITIAL */
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('INITIAL');
IFNO;
RC (8);
MSG ('INVALID STATUS - MUST BE INITIAL OR OPEN');
EIF;
ECRITERIA;
POPULATE;
EPOPULATE;
ELABEL;
EUSE;
04-May-2018 528/1109
CA Endevor® SCM - 17.0
USE (UPDATE, AFTER, STANDALONE);
FOUND (UPT0010);
NOTFOUND (RETURN);
LABEL UPT0010;
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('ACTION PROCESSING COMPLETED RC = =ACTRC')
TEXT ('ELEMENT: =EV2ENV / =EV2SYS / =EV2SUB ') -
('/ =EV2TYP / =EV2STAGE / =EV2ELMFN')
TEXT ('ACTION: =ACTION USER: =USER DATE: =DATE ') -
('TIME: =TIME');
EPOPULATE;
ELABEL;
EUSE;
USE (RESTORE,BEFORE, STANDALONE);
NOTFOUND (CREATE,RST0010);
FOUND (RST0020);
LABEL RST0010; /* CHANGE RECORD NOT FOUND: CREATE ONE */
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=USER);
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
FIELD PANEL(BLG6DSAB) INDEX(S0E0F)
VALUE('API CREATE CHG RECORD');
EPOPULATE;
RC(0);
ELABEL;
LABEL RST0020; /* CHANGE RECORD FOUND */
RC (0);
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
ECRITERIA;
POPULATE;
EPOPULATE;
CFAIL RST0022;
ELABEL;
LABEL RST0022; /* STATUS NOT OPEN - CHECK FOR INITIAL */
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('INITIAL');
IFNO;
RC (8);
MSG ('INVALID STATUS - MUST BE INITIAL OR OPEN');
EIF;
ECRITERIA;
POPULATE;
EPOPULATE;
ELABEL;
EUSE;
USE (RESTORE,AFTER, STANDALONE);
FOUND (RST0010);
NOTFOUND (RETURN);
LABEL RST0010;
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('ACTION PROCESSING COMPLETED RC = =ACTRC')
04-May-2018 529/1109
CA Endevor® SCM - 17.0
TEXT ('ACTION PROCESSING COMPLETED RC = =ACTRC')
TEXT ('SOURCE ELEMENT: =EV1ENV / =EV1SYS / =EV1SUB ') -
('/ =EV1TYP / =EV1STG# / =EV1ELMFN')
TEXT ('TARGET ELEMENT: =EV2ENV / =EV2SYS / =EV2SUB ') -
('/ =EV2TYP / =EV2STAGE / =EV2ELMFN')
TEXT ('ACTION: =ACTION USER: =USER DATE: =DATE ') -
('TIME: =TIME');
EPOPULATE;
ELABEL;
EUSE;
USE (GENERATE, BEFORE, STANDALONE);
NOTFOUND (CREATE,GEN0010);
FOUND (GEN0020);
LABEL GEN0010; /* CHANGE RECORD NOT FOUND: CREATE ONE */
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=USER);
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
FIELD PANEL(BLG6DSAB) INDEX(S0E0F)
VALUE('API CREATE CHG RECORD');
EPOPULATE;
RC(0);
ELABEL;
LABEL GEN0020; /* CHANGE RECORD FOUND */
RC (0);
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
ECRITERIA;
POPULATE;
EPOPULATE;
CFAIL GEN0022;
ELABEL;
LABEL GEN0022; /* STATUS NOT OPEN - CHECK FOR INITIAL */
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('INITIAL');
IFNO;
RC (8);
MSG ('INVALID STATUS - MUST BE INITIAL OR OPEN');
EIF;
ECRITERIA;
POPULATE;
EPOPULATE;
ELABEL;
EUSE;
USE (GENERATE ,AFTER, STANDALONE);
FOUND (GEN0010);
NOTFOUND (RETURN);
LABEL GEN0010;
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('ACTION PROCESSING COMPLETED RC = =ACTRC')
TEXT ('ELEMENT: =EV1ENV / =EV1SYS / =EV1SUB ') -
('/ =EV1TYP / =EV1STAGE / =EV1ELMFN')
TEXT ('ACTION: =ACTION USER: =USER DATE: =DATE ') -
('TIME: =TIME');
EPOPULATE;
ELABEL;
EUSE;
USE (RETRIEVE, BEFORE, STANDALONE);
04-May-2018 530/1109
CA Endevor® SCM - 17.0
USE (RETRIEVE, BEFORE, STANDALONE);
NOTFOUND (CREATE,RET0010);
FOUND (RET0020);
LABEL RET0010; /* CHANGE RECORD NOT FOUND: CREATE ONE */
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=USER);
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
FIELD PANEL(BLG6DSAB) INDEX(S0E0F)
VALUE('API CREATE CHG RECORD');
EPOPULATE;
RC(0);
ELABEL;
LABEL RET0020; /* CHANGE RECORD FOUND */
RC (0);
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
ECRITERIA;
POPULATE;
EPOPULATE;
CFAIL RET0022;
ELABEL;
LABEL RET0022; /* STATUS NOT OPEN - CHECK FOR INITIAL */
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('INITIAL');
IFNO;
RC (8);
MSG ('INVALID STATUS - MUST BE INITIAL OR OPEN');
EIF;
ECRITERIA;
POPULATE;
EPOPULATE;
ELABEL;
EUSE;
USE (RETRIEVE, AFTER, STANDALONE);
FOUND (RET0010);
NOTFOUND (RETURN);
LABEL RET0010;
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('ACTION PROCESSING COMPLETED RC = =ACTRC')
TEXT ('ELEMENT: =EV1ENV / =EV1SYS / =EV1SUB ') -
('/ =EV1TYP / =EV1STAGE / =EV1ELMFN')
TEXT ('ACTION: =ACTION USER: =USER DATE: =DATE ') -
('TIME: =TIME');
EPOPULATE;
ELABEL;
EUSE;
USE (ARCHIVE, BEFORE, STANDALONE);
NOTFOUND (CREATE,ARC0010);
FOUND (ARC0020);
LABEL ARC0010; /* CHANGE RECORD NOT FOUND: CREATE ONE */
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=USER);
04-May-2018 531/1109
CA Endevor® SCM - 17.0
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=USER);
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
FIELD PANEL(BLG6DSAB) INDEX(S0E0F)
VALUE('API CREATE CHG RECORD');
EPOPULATE;
RC(0);
ELABEL;
LABEL ARC0020; /* CHANGE RECORD FOUND */
RC (0);
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
ECRITERIA;
POPULATE;
EPOPULATE;
CFAIL ARC0022;
ELABEL;
LABEL ARC0022; /* STATUS NOT OPEN - CHECK FOR INITIAL */
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('INITIAL');
IFNO;
RC (8);
MSG ('INVALID STATUS - MUST BE INITIAL OR OPEN');
EIF;
ECRITERIA;
POPULATE;
EPOPULATE;
ELABEL;
EUSE;
USE (ARCHIVE, AFTER, STANDALONE);
FOUND (ARC0010);
NOTFOUND (RETURN);
LABEL ARC0010;
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('ACTION PROCESSING COMPLETED RC = =ACTRC')
TEXT ('ELEMENT: =EV1ENV / =EV1SYS / =EV1SUB ') -
('/ =EV1TYP / =EV1STAGE / =EV1ELMFN')
TEXT ('TARGET: =FI2DSN =FI2MBR')
TEXT ('ACTION: =ACTION USER: =USER DATE: =DATE ') -
('TIME: =TIME');
EPOPULATE;
ELABEL;
EUSE;
USE (DELETE, BEFORE, STANDALONE);
NOTFOUND (CREATE,DEL0010);
FOUND (DEL0020);
LABEL DEL0010; /* CHANGE RECORD NOT FOUND: CREATE ONE */
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=USER);
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
FIELD PANEL(BLG6DSAB) INDEX(S0E0F)
VALUE('API CREATE CHG RECORD');
EPOPULATE;
RC(0);
ELABEL;
LABEL DEL0020; /* CHANGE RECORD FOUND */
04-May-2018 532/1109
CA Endevor® SCM - 17.0
LABEL DEL0020; /* CHANGE RECORD FOUND */
RC (0);
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
ECRITERIA;
POPULATE;
EPOPULATE;
CFAIL DEL0022;
ELABEL;
LABEL DEL0022; /* STATUS NOT OPEN - CHECK FOR INITIAL */
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('INITIAL');
IFNO;
RC (8);
MSG ('INVALID STATUS - MUST BE INITIAL OR OPEN');
EIF;
ECRITERIA;
POPULATE;
EPOPULATE;
ELABEL;
EUSE;
USE (DELETE, AFTER, STANDALONE);
FOUND (DEL0010);
NOTFOUND (RETURN);
LABEL DEL0010;
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('ACTION PROCESSING COMPLETED RC = =ACTRC')
TEXT ('ELEMENT: =EV1ENV / =EV1SYS / =EV1SUB ') -
('/ =EV1TYP / =EV1STAGE / =EV1ELMFN')
TEXT ('ACTION: =ACTION USER: =USER DATE: =DATE ') -
('TIME: =TIME');
EPOPULATE;
ELABEL;
EUSE;
USE (MOVE, BEFORE, STANDALONE);
NOTFOUND (CREATE,MOV0010);
FOUND (MOV0020);
LABEL MOV0010; /* CHANGE RECORD NOT FOUND: CREATE ONE */
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=USER);
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
FIELD PANEL(BLG6DSAB) INDEX(S0E0F)
VALUE('API CREATE CHG RECORD');
EPOPULATE;
RC(0);
ELABEL;
LABEL MOV0020; /* CHANGE RECORD FOUND */
RC (0);
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
ECRITERIA;
POPULATE;
EPOPULATE;
CFAIL MOV0022;
ELABEL;
LABEL MOV0022; /* STATUS NOT OPEN - CHECK FOR INITIAL */
CRITERIA;
04-May-2018 533/1109
CA Endevor® SCM - 17.0
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('INITIAL');
IFNO;
RC (8);
MSG ('INVALID STATUS - MUST BE INITIAL OR OPEN');
EIF;
ECRITERIA;
POPULATE;
EPOPULATE;
ELABEL;
EUSE;
USE (MOVE, AFTER, STANDALONE);
FOUND (MOV0010);
NOTFOUND (RETURN);
LABEL MOV0010;
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('ACTION PROCESSING COMPLETED RC = =ACTRC')
TEXT ('SOURCE ELEMENT: =EV1ENV / =EV1SYS / =EV1SUB ') -
('/ =EV1TYP / =EV1STAGE / =EV1ELMFN')
TEXT ('TARGET ELEMENT: =EV2ENV / =EV2SYS / =EV2SUB ') -
('/ =EV2TYP / =EV2STAGE / =EV2ELMFN')
TEXT ('ACTION: =ACTION USER: =USER DATE: =DATE ') -
('TIME: =TIME');
EPOPULATE;
ELABEL;
EUSE;
USE (TRANSFER, BEFORE, STANDALONE);
NOTFOUND (CREATE,TRA0010);
FOUND (TRA0020);
LABEL TRA0010; /* CHANGE RECORD NOT FOUND: CREATE ONE */
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=USER);
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
FIELD PANEL(BLG6DSAB) INDEX(S0E0F)
VALUE('API CREATE CHG RECORD');
EPOPULATE;
RC(0);
ELABEL;
LABEL TRA0020; /* CHANGE RECORD FOUND */
RC (0);
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
ECRITERIA;
POPULATE;
EPOPULATE;
CFAIL TRA0022;
ELABEL;
LABEL TRA0022; /* STATUS NOT OPEN - CHECK FOR INITIAL */
CRITERIA;
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('INITIAL');
IFNO;
RC (8);
MSG ('INVALID STATUS - MUST BE INITIAL OR OPEN');
EIF;
ECRITERIA;
POPULATE;
EPOPULATE;
ELABEL;
04-May-2018 534/1109
CA Endevor® SCM - 17.0
ELABEL;
EUSE;
USE (TRANSFER, AFTER, STANDALONE);
FOUND (TRA0010);
NOTFOUND (RETURN);
LABEL TRA0010;
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('ACTION PROCESSING COMPLETED RC = =ACTRC')
TEXT ('SOURCE ELEMENT: =EV1ENV / =EV1SYS / =EV1SUB ') -
('/ =EV1TYP / =EV1STAGE / =EV1ELMFN')
TEXT ('TARGET ELEMENT: =EV2ENV / =EV2SYS / =EV2SUB ') -
('/ =EV2TYP / =EV2STAGE / =EV2ELMFN')
TEXT ('ACTION: =ACTION USER: =USER DATE: =DATE ') -
('TIME: =TIME');
EPOPULATE;
ELABEL;
EUSE;
ETABLE;
InfoMan Interactive Facility (IIF) users can find a syntax template for packages and package actions in
member EISCRXX3 in iprfx.iqual.CSIQOPTN.
TABLE NAME (ENDEV03);
This statement starts the table. The name of the table is ENDEV03. There must be an ETABLE
statement at the end of the table.
CTRL;
IPKG (TS0B06I); /* INQUIRY CHANGE TABLE FOR PACKAGES */
IPKGA(TS0B07I); /* INQUIRY ACTIVITY TABLE FOR PKG ACTIONS */
RPKG (TS0B06R); /* RETRIEVE CHANGE TABLE FOR PACKAGES */
RPKGA(TS0B07R); /* RETRIEVE ACTIVITY TABLE FOR PKG ACTIONS */
CPKG (TS0B06C); /* CREATE CHANGE TABLE FOR PACKAGES */
CPKGA(TS0B07C); /* CREATE ACTIVITY TABLE FOR PKG ACTIONS */
UPKG (TS0B06U); /* UPDATE CHANGE TABLE FOR PACKAGES */
UPKGA(TS0B07U); /* UPDATE ACTIVITY TABLE FOR PKG ACTIONS */
AACT (TS0B06A); /* ADD CHANGE ACTIVITY TABLE FOR PKG ACTION*/
ECTRL;
This Control block indicates that CA Endevor® SCM may request the InfoMan API to:
04-May-2018 535/1109
CA Endevor® SCM - 17.0
/************************************************
* EXIT POINTS: CREATE/AFTER MODIFY/ AFTER *
************************************************/
USE ((CREATE, AFTER),
(MODIFY, AFTER));
This USE statement indicates that the processing in this Use block applies to the after-exit point for
the CREATE PACKAGE and MODIFY PACKAGE actions.
NOTFOUND (CREATE,CMD0010);
FOUND (CMD0020);
If there is no Change record in InfoMan for a package, the interface is to create a record, using
the processing specified in Label block CMD0010.
If there is a record in InfoMan for the package, the interface is to execute the processing specified
in Label block CMD0020.
LABEL CMD0010; /* CHANGE RECORD NOT FOUND: CREATE ONE */
This LABEL statement starts the Label block referred to by the NOTFOUND statement earlier in the
syntax.
CRITERIA;
ECRITERIA;
Even if there are no criteria for populating an InfoMan record, there must be a Criteria block within a
Label block, if that block also contains a POPULATE statement. When there are no criteria, code the
Criteria block this way.
POPULATE;
/***************************************
* PECBUSER: CURRENT USER ID *
***************************************/
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=PECBUSER);
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
FIELD PANEL(BLG0C010) INDEX(S0E01)
VALUE('E/INFO CREATED CHANGE RECORD');
EPOPULATE;
This POPULATE block tells the InfoMan API what information to put in the Change record that it
creates. In this example the API populates three fields:
The BLG6REQN field (index S0B59) with the value in the PECBUSER field of the CA Endevor® SCM
package exit control block ($PECBDS).
The BLG0C010 field (index S0E01) with the value E/INFO CREATED CHANGE RECORD.
04-May-2018 536/1109
CA Endevor® SCM - 17.0
CPASS CMD0020;
The CPASS statement tells the interface to execute the processing specified in Label block CMD0020 if
the API populates the new record successfully.
ELABEL;
LABEL CMD0020;
This statement starts the label block referenced in the CPASS statement in the preceding Label block.
RC (0);
This statement tells the API to send a return code of zero back to CA Endevor® SCM after successfully
executing the processing in this Label block.
CRITERIA;
ECRITERIA;
Grouping the CRITERIA and ECRITERIA statements this way indicates that there are no criteria to be
satisfied. This tells the interface to execute the processing specified in the Populate block.
Note: For more information, see Criteria Blocks (see page 491).
POPULATE;
/******************************************
* PREQCOMM: PACKAGE COMMENT *
* PREQEWSD: EXECUTION WINDOW START DATE *
* PREQEWST: EXECUTION WINDOW START TIME *
* PREQEWED: EXECUTION WINDOW END DATE *
* PREQEWET: EXECUTION WINDOW END TIME *
* PECBUSER: CURRENT USER ID *
* PECBFNNM: PACKAGE FUNCTION *
* PECBBANM: BEFORE OR AFTER *
* PECBNDRC: NDVR HIGH RETURN CODE *
* PHDRSTAT: PACKAGE STATUS *
* PHDRCRD: PACKAGE CREATION DATE *
* PHDRCRT: PACKAGE CREATION TIME *
******************************************/
This POPULATE statement is followed by a multi-line comment expanding the names of the CA
Endevor® SCM control block fields used to populate InfoMan fields in the following FIELD and TEXT
statements.
Note: For more information, see The Populate Block (see page 492).
04-May-2018 537/1109
CA Endevor® SCM - 17.0
FIELD PANEL(BLG6DSAB) INDEX(S0E0F) VALUE(=PREQCOMM);
FIELD PANEL(BLG6SCHD) INDEX(S0C41) VALUE(=PREQEWSD);
FIELD PANEL(BLG6SCHT) INDEX(S0C6E) VALUE(=PREQEWST);
FIELD PANEL(BLG6TARD) INDEX(S0C42) VALUE(=PREQEWED);
FIELD PANEL(BLG6TART) INDEX(S0C6F) VALUE(=PREQEWET);
FIELD PANEL(BLG600CN) INDEX(S0B5C) VALUE(=PECBUSER);
FIELD PANEL(BLG6PHAC) INDEX(S0C0B) VALUE(=PECBFNNM);
These FIELD statements specify the InfoMan fields that are to contain CA Endevor® SCM information,
and the values that the API is to use to populate these fields. The comment earlier in the Populate
block identifies the information referred to by the equate value.
Note: For more information, see FIELD Statements (see page 494).
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('PACKAGE PROCESSING COMPLETED RC = =PECBNDRC')
TEXT ('INFO ACCESSED FROM PACKAGE EXIT =PECBBANM / =PECBFNNM')
TEXT ('PKG STATUS: =PHDRSTAT USER: =PECBUSER')
TEXT ('CREATE DATE: =PHDRCRD TIME: =PHDRCRT');
These TEXT statements tell the interface to populate field BLGC010 (index S0E01) with a four-line
message.
There is one TEXT statement for each line. Lines are continued by placing a hyphen as the last
character in the first line. Also note that there is only one semicolon for all three TEXT statements,
located at the end of the last statement.
The message is built using information from CA Endevor® SCM control blocks.
Line 2 uses the PECBBANM and PECBFNNM fields from the $PECBDS block.
Line 3 uses the PHDRSTAT field from the PHDRDS block and the PECBUSER field from the $PECBDS
block.
Line 4 uses the PHDRCRD and PHDRCRT fields from the PHDRDS block.
EPOPULATE;
ELABEL;
EUSE;
This statement ends the Use block for the after-exit point for the CREATE PACKAGE and MODIFY
PACKAGE actions.
USE (CAST, AFTER);
FOUND (CST0020);
04-May-2018 538/1109
CA Endevor® SCM - 17.0
FOUND (CST0020);
NOTFOUND (CREATE, CST0010);
LABEL CST0010; /* CHANGE RECORD NOT FOUND: CREATE ONE. */
CRITERIA;
ECRITERIA;
POPULATE;
/***************************************
* PECBUSER: CURRENT USER ID *
***************************************/
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=PECBUSER);
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
EPOPULATE;
CPASS CST0020;
ELABEL;
LABEL CST0020;
RC (0);
CRITERIA;
ECRITERIA;
POPULATE;
/******************************************
* PREQCOMM: PACKAGE COMMENT *
* PREQEWSD: EXECUTION WINDOW START DATE *
* PREQEWST: EXECUTION WINDOW START TIME *
* PREQEWED: EXECUTION WINDOW END DATE *
* PREQEWET: EXECUTION WINDOW END TIME *
* PECBUSER: CURRENT USER ID *
* PECBFNNM: PACKAGE FUNCTION *
* PECBBANM: BEFORE OR AFTER *
* PECBNDRC: NDVR HIGH RETURN CODE *
* PHDRSTAT: PACKAGE STATUS *
* PHDRCRD: PACKAGE CREATION DATE *
* PHDRCRT: PACKAGE CREATION TIME *
* PHDRCD: PACKAGE CAST DATE *
* PHDRCT: PACKAGE CAST TIME *
******************************************/
FIELD PANEL(BLG6DSAB) INDEX(S0E0F) VALUE(=PREQCOMM);
FIELD PANEL(BLG6SCHD) INDEX(S0C41) VALUE(=PREQEWSD);
FIELD PANEL(BLG6SCHT) INDEX(S0C6E) VALUE(=PREQEWST);
FIELD PANEL(BLG6TARD) INDEX(S0C42) VALUE(=PREQEWED);
FIELD PANEL(BLG6TART) INDEX(S0C6F) VALUE(=PREQEWET);
FIELD PANEL(BLG600CN) INDEX(S0B5C) VALUE(=PECBUSER);
FIELD PANEL(BLG6PHAC) INDEX(S0C0B) VALUE(=PECBFNNM);
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('PACKAGE PROCESSING COMPLETED RC = =PECBNDRC')
TEXT ('INFO ACCESSED FROM PACKAGE EXIT =PECBBANM / =PECBFNNM')
TEXT ('PKG STATUS: =PHDRSTAT USER: =PECBUSER')
TEXT ('CREATE DATE: =PHDRCRD TIME: =PHDRCRT')
TEXT ('CAST DATE: =PHDRCD TIME: =PHDRCT');
EPOPULATE;
ELABEL;
EUSE;
/************************************************
* EXIT POINT: CREATE/ACTIVITY. INVOKED AFTER *
* THE CAST AFTER EXIT. THIS INFO EXIT WILL *
* CREATE AN ACTIVITY RECORD PER PACKAGE ACTION *
* BY CCID. *
************************************************/
USE (CREATE, ACTIVITY);
LABEL CRT0010; /* MAINLINE - ALL PKG ACTION POINTS. */
CRITERIA;
ECRITERIA;
POPULATE;
/***************************************
* PECBUSER: CURRENT USER ID *
***************************************/
04-May-2018 539/1109
CA Endevor® SCM - 17.0
***************************************/
FIELD PANEL(BLG6REQN) INDEX(S0B59) VALUE(=PECBUSER);
FIELD PANEL(BLG6STAT) INDEX(S0BEE) VALUE('OPEN');
FIELD PANEL(BLG6DSAB) INDEX(S0E0F)
TEXT ('CCID: =PACTCCID IN PACKAGE: =PECBPKID');
EPOPULATE;
CPASS CRT0020;
ELABEL;
LABEL CRT0020; /* LOOKING FOR ACTION: ADD */
CRITERIA;
FIELD (=PACTACTN) VALUE('ADD ');
ECRITERIA;
POPULATE;
EPOPULATE;
CPASS GRP0010;
CFAIL CRT0025;
ELABEL;
LABEL CRT0025; /* LOOKING FOR ACTION: UPDATE */
CRITERIA;
FIELD (=PACTACTN) VALUE('UPDATE ');
ECRITERIA;
POPULATE;
EPOPULATE;
CPASS GRP0010;
CFAIL CRT0030;
ELABEL;
LABEL CRT0030; /* LOOKING FOR ACTION: RESTORE */
CRITERIA;
FIELD (=PACTACTN) VALUE('RESTORE ');
ECRITERIA;
POPULATE;
EPOPULATE;
CPASS GRP0010;
CFAIL CRT0035;
ELABEL;
LABEL CRT0035; /* LOOKING FOR ACTION: GENERATE */
CRITERIA;
FIELD (=PACTACTN) VALUE('GENERATE');
ECRITERIA;
POPULATE;
EPOPULATE;
CPASS GRP0020;
CFAIL CRT0040;
ELABEL;
LABEL CRT0040; /* LOOKING FOR ACTION: DELETE */
CRITERIA;
FIELD (=PACTACTN) VALUE('DELETE ');
ECRITERIA;
POPULATE;
EPOPULATE;
CPASS GRP0020;
CFAIL CRT0045;
ELABEL;
LABEL CRT0045; /* LOOKING FOR ACTION: RETRIEVE */
CRITERIA;
FIELD (=PACTACTN) VALUE('RETRIEVE');
ECRITERIA;
POPULATE;
EPOPULATE;
CPASS GRP0030;
04-May-2018 540/1109
CA Endevor® SCM - 17.0
CPASS GRP0030;
CFAIL CRT0050;
ELABEL;
LABEL CRT0050; /* LOOKING FOR ACTION: ARCHIVE */
CRITERIA;
FIELD (=PACTACTN) VALUE('ARCHIVE ');
ECRITERIA;
POPULATE;
EPOPULATE;
CPASS GRP0020;
CFAIL CRT0055;
ELABEL;
LABEL CRT0055; /* LOOKING FOR ACTION: MOVE */
CRITERIA;
FIELD (=PACTACTN) VALUE('MOVE ');
ECRITERIA;
POPULATE;
EPOPULATE;
CPASS GRP0040;
CFAIL CRT0060;
ELABEL;
LABEL CRT0060; /* LOOKING FOR ACTION: TRANSFER */
CRITERIA;
FIELD (=PACTACTN) VALUE('TRANSFER');
ECRITERIA;
POPULATE;
EPOPULATE;
CPASS GRP0040;
ELABEL;
LABEL GRP0010; /* FOR PACKAGE ACTION: ADD */
RC (0); /* UPDATE */
CRITERIA; /* RESTORE */
ECRITERIA;
POPULATE;
/******************************************
* PACTACTN: ACTION NAME *
* PACTCOMM: ACTION COMMENT *
* PACTSDSN: DATA SET NAME *
* PACTSMBR: MEMBER *
* PACTTENV: ENVIRONMENT NAME *
* PACTTSYS: SYSTEM NAME *
* PACTTSBS: SUBSYSTEM NAME *
* PACTTTYP: TYPE *
* PACTTSTG: STAGE NAME *
* PACTTELM: ELEMENT NAME *
******************************************/
FIELD PANEL(BLG0C030) INDEX(S0E01)
TEXT ('ACTION: =PACTACTN =PACTCOMM')
TEXT ('ELEMENT: =PACTTENV / =PACTTSYS / =PACTTSBS / ') -
('=PACTTTYP / =PACTTSTG / =PACTTELMFN ');
EPOPULATE;
CPASS GRP0050;
ELABEL;
LABEL GRP0020; /* FOR PACKAGE ACTIONS: GENERATE */
RC (0); /* DELETE */
CRITERIA; /* ARCHIVE */
ECRITERIA;
POPULATE;
/******************************************
* PACTACTN: ACTION NAME *
* PACTCOMM: ACTION COMMENT *
* PACTSENV: ENVIRONMENT NAME *
* PACTSSYS: SYSTEM NAME *
04-May-2018 541/1109
CA Endevor® SCM - 17.0
* PACTSSYS: SYSTEM NAME *
* PACTSSBS: SUBSYSTEM NAME *
* PACTSTYP: TYPE *
* PACTSSTG: STAGE NAME *
* PACTSELM: ELEMENT NAME *
******************************************/
FIELD PANEL(BLG0C030) INDEX(S0E01)
TEXT ('ACTION: =PACTACTN =PACTCOMM')
TEXT ('ELEMENT: =PACTSENV / =PACTSSYS / =PACTSSBS / ') -
('=PACTSTYP / =PACTSSTG / =PACTSELMFN ');
EPOPULATE;
ELABEL;
LABEL GRP0030; /* FOR PACKAGE ACTIONS: RETRIEVE */
RC (0); /* */
CRITERIA;
ECRITERIA;
POPULATE;
/******************************************
* PACTACTN: ACTION NAME *
* PACTCOMM: ACTION COMMENT *
* PACTTDSN: DATA SET NAME *
* PACTTMBR: MEMBER *
* PACTSENV: ENVIRONMENT NAME *
* PACTSSYS: SYSTEM NAME *
* PACTSSBS: SUBSYSTEM NAME *
* PACTSTYP: TYPE *
* PACTSSTG: STAGE NAME *
* PACTSELM: ELEMENT NAME *
******************************************/
FIELD PANEL(BLG0C030) INDEX(S0E01)
TEXT ('ACTION: =PACTACTN =PACTCOMM')
TEXT ('ELEMENT: =PACTSENV / =PACTSSYS / =PACTSSBS / ') -
('=PACTSTYP / =PACTSSTG / =PACTSELMFN ');
EPOPULATE;
CPASS GRP0070;
ELABEL;
LABEL GRP0040; /* FOR PACKAGE ACTIONS: MOVE */
RC (0); /* TRANSFER */
CRITERIA;
ECRITERIA;
POPULATE;
/******************************************
* PACTACTN: ACTION NAME *
* PACTCOMM: ACTION COMMENT *
* PACTSENV: ENVIRONMENT NAME *
* PACTSSYS: SYSTEM NAME *
* PACTSSBS: SUBSYSTEM NAME *
* PACTSTYP: TYPE *
* PACTSSTG: STAGE NAME *
* PACTSELM: ELEMENT NAME *
* PACTTENV: ENVIRONMENT NAME *
* PACTTSYS: SYSTEM NAME *
* PACTTSBS: SUBSYSTEM NAME *
* PACTTTYP: TYPE *
* PACTTSTG: STAGE NAME *
* PACTTELM: ELEMENT NAME *
******************************************/
FIELD PANEL(BLG0C030) INDEX(S0E01)
TEXT ('ACTION: =PACTACTN =PACTCOMM')
TEXT ('SOURCE: =PACTSENV / =PACTSSYS / =PACTSSBS / ') -
('=PACTSTYP / =PACTSSTG / =PACTSELMFN ')
TEXT ('TARGET: =PACTTENV / =PACTTSYS / =PACTTSBS / ') -
('=PACTTTYP / =PACTTSTG / =PACTTELMFN ');
EPOPULATE;
ELABEL;
LABEL GRP0050; /* ADD PATH INFO FOR ADD, UPDATE */
RC (0); /* */
CRITERIA;
04-May-2018 542/1109
CA Endevor® SCM - 17.0
CRITERIA;
FIELD (=PACTSFLAG) VALUE('P');
ECRITERIA;
POPULATE;
FIELD PANEL(BLG0C030) INDEX(S0E01)
TEXT ('SOURCE: =PACTSPANM =PACTSFINM ');
EPOPULATE;
CFAIL GRP0060;
ELABEL;
LABEL GRP0060; /* ADD DATA SET INFO FOR ADD, UPDATE */
RC (0); /* RESTORE */
CRITERIA;
FIELD (=PACTSDSN) VALUE(NONBLANK);
ECRITERIA;
POPULATE;
FIELD PANEL(BLG0C030) INDEX(S0E01)
TEXT ('SOURCE: =PACTSDSN =PACTSMBR ');
EPOPULATE;
ELABEL;
LABEL GRP0070; /* ADD PATH INFO FOR RETRIEVE */
RC (0); /* */
CRITERIA;
FIELD (=PACTTFLAG) VALUE('P');
ECRITERIA;
POPULATE;
FIELD PANEL(BLG0C030) INDEX(S0E01)
TEXT ('TARGET: =PACTTPANM =PACTTFINM ');
EPOPULATE;
CFAIL GRP0080;
ELABEL;
LABEL GRP0080; /* ADD DATA SET INFO FOR RETRIEVE */
RC (0); /* RESTORE */
CRITERIA;
FIELD (=PACTTDSN) VALUE(NONBLANK);
ECRITERIA;
POPULATE;
FIELD PANEL(BLG0C030) INDEX(S0E01)
TEXT ('TARGET: =PACTTDSN =PACTTMBR ');
EPOPULATE;
ELABEL;
EUSE;
/************************************************
* EXIT POINTS: REVIEW/AFTER EXECUTE/AFTER *
* SHIP/AFTER CONFIRM/AFTER *
* BACKOUT/AFTER BACKIN/AFTER *
* COMMIT/AFTER *
************************************************/
USE ((REVIEW, AFTER),
(EXECUTE, AFTER),
(SHIP, AFTER),
(CONFIRM, AFTER),
(BACKOUT,AFTER),
(BACKIN,AFTER),
(COMMIT,AFTER));
LABEL GRP0010; /* MAINLINE - ALL POINTS */
RC(0);
CRITERIA;
ECRITERIA;
POPULATE;
/******************************************
* PREQCOMM: PACKAGE COMMENT *
* PREQEWSD: EXECUTION WINDOW START DATE *
* PREQEWST: EXECUTION WINDOW START TIME *
04-May-2018 543/1109
CA Endevor® SCM - 17.0
* PREQEWST: EXECUTION WINDOW START TIME *
* PREQEWED: EXECUTION WINDOW END DATE *
* PREQEWET: EXECUTION WINDOW END TIME *
* PECBUSER: CURRENT USER ID *
* PECBFNNM: PACKAGE FUNCTION *
* PECBBANM: BEFORE OR AFTER *
* PECBNDRC: NDVR HIGH RETURN CODE *
* PHDRSTAT: PACKAGE STATUS *
******************************************/
FIELD PANEL(BLG6DSAB) INDEX(S0E0F) VALUE(=PREQCOMM);
FIELD PANEL(BLG6SCHD) INDEX(S0C41) VALUE(=PREQEWSD);
FIELD PANEL(BLG6SCHT) INDEX(S0C6E) VALUE(=PREQEWST);
FIELD PANEL(BLG6TARD) INDEX(S0C42) VALUE(=PREQEWED);
FIELD PANEL(BLG6TART) INDEX(S0C6F) VALUE(=PREQEWET);
FIELD PANEL(BLG600CN) INDEX(S0B5C) VALUE(=PECBUSER);
FIELD PANEL(BLG6PHAC) INDEX(S0C0B) VALUE(=PECBFNNM);
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('PACKAGE PROCESSING COMPLETED RC = =PECBNDRC')
TEXT ('INFO ACCESSED FROM PACKAGE EXIT =PECBBANM / =PECBFNNM')
TEXT ('PKG STATUS: =PHDRSTAT USER: =PECBUSER');
EPOPULATE;
CPASS EXE0010;
ELABEL;
LABEL EXE0010; /* EXECUTE AFTER - LOG SECTION */
CRITERIA;
FIELD (=PECBFNNM) VALUE ('EXECUTE ');
ECRITERIA;
POPULATE;
/******************************************
* PHDRXD: EXECUTION DATE *
* PHDRXT: EXECUTION TIME *
* PHDREEXD: END EXECUTION DATE *
* PHDREEXT: END EXECUTION TIME *
******************************************/
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('EXECUTION: =PHDRXD =PHDRXT')
TEXT ('END EXECUTION: =PHDREEXD =PHDREEXT');
EPOPULATE;
CFAIL BKO0010;
ELABEL;
LABEL BKO0010; /* BACKOUT AFTER - LOG SECTION */
CRITERIA;
FIELD (=PECBFNNM) VALUE ('BACKOUT ');
ECRITERIA;
POPULATE;
/******************************************
* PHDRBOST: BACKOUT STATUS *
* PHDRBOD: BACKOUT DATE *
* PHDRBOT: BACKOUT TIME *
******************************************/
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('BACKOUT: =PHDRBOD =PHDRBOT STATUS: =PHDRBOST');
EPOPULATE;
CFAIL BKI0010;
ELABEL;
LABEL BKI0010; /* BACKIN AFTER - LOG SECTION */
CRITERIA;
FIELD (=PECBFNNM) VALUE ('BACKIN ');
ECRITERIA;
POPULATE;
/******************************************
* PHDRBID: BACKIN DATE *
* PHDRBIT: BACKIN TIME *
******************************************/
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('BACKIN: =PHDRBID =PHDRBIT');
04-May-2018 544/1109
CA Endevor® SCM - 17.0
TEXT ('BACKIN: =PHDRBID =PHDRBIT');
EPOPULATE;
CFAIL COM0010;
ELABEL;
LABEL COM0010; /* COMMIT AFTER - LOG SECTION */
CRITERIA;
FIELD (=PECBFNNM) VALUE ('COMMIT ');
ECRITERIA;
POPULATE;
/******************************************
* PHDRCMD: COMMIT DATE *
* PHDRCMT: COMMIT TIME *
******************************************/
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('COMMIT: =PHDRCMD =PHDRCMT');
EPOPULATE;
CFAIL SHP0010;
ELABEL;
LABEL SHP0010; /* SHIP XMIT AFTER - LOG SECTION */
CRITERIA;
FIELD (=PECBSFNM) VALUE ('XMIT ');
ECRITERIA;
POPULATE;
/******************************************
* PREQDEST: SHIP DESTINATION *
* PREQSTYP: SHIPMENT TYPE *
* PREQSCMP: SHIP COMPLEMENTS (Y/N) *
******************************************/
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('SHIP: DESTINATION =PREQDEST TYPE =PREQSTYP ') -
('COMPLEMENTS =PREQSCMP');
EPOPULATE;
CFAIL CFM0010;
ELABEL;
LABEL CFM0010; /* SHIP CONFIRM AFTER - LOG SECTION */
CRITERIA;
FIELD (=PECBSFNM) VALUE ('CONFIRM ');
ECRITERIA;
POPULATE;
/******************************************
* PREQDEST: SHIP DESTINATION *
* PREQSCNF: SHIP CONFIRMATIN TYPE *
* PREQSRES: SHIP CONFIRMATION RESULTS *
* PREQSRCV: SHIP CONFIRM RC VALUE *
******************************************/
FIELD PANEL(BLG0C010) INDEX(S0E01)
TEXT ('SHIP: DESTINATION =PREQDEST CONFIRM TYPE =PREQSCNF') -
(' CONFIRMATION RESULTS =PREQSRES =PREQSRCV');
EPOPULATE;
ELABEL;
EUSE;
/************************************************
* EXIT POINTS: ADD/BEFORE UPDATE/BEFORE *
* RESTORE/BEFORE RETRIEVE/BEFORE *
* ARCHIVE/BEFORE GENERATE/BEFORE *
* DELETE/BEFORE MOVE/BEFORE *
* TRANSFER/BEFORE *
************************************************/
USE ((ADD, BEFORE),
(UPDATE, BEFORE),
04-May-2018 545/1109
CA Endevor® SCM - 17.0
(UPDATE, BEFORE),
(RESTORE, BEFORE),
(RETRIEVE, BEFORE),
(ARCHIVE, BEFORE),
(GENERATE, BEFORE),
(DELETE, BEFORE),
(MOVE, BEFORE),
(TRANSFER, BEFORE));
NOTFOUND (RETURN);
FOUND (RETURN); /* GREAT -- JUST RETURN */
EUSE;
/************************************************
* ON PACKAGE ACTIONS - JUST BEFORE EXECUTION. *
* PURPOSE: RECORD ACTION RETURN CODE ON *
* THE CCID ACTIVITY RECORD. *
************************************************/
USE ((ADD, AFTER),
(UPDATE, AFTER),
(RESTORE, AFTER),
(RETRIEVE, AFTER),
(ARCHIVE, AFTER),
(GENERATE, AFTER),
(DELETE, AFTER),
(MOVE, AFTER),
(TRANSFER, AFTER));
NOTFOUND (ERR0010);
FOUND (GRP0010);
LABEL GRP0010; /* ALL PKG ACTION POINTS */
RC(0);
CRITERIA;
ECRITERIA;
POPULATE;
FIELD PANEL(BLG0C030) INDEX(S0E01)
TEXT ('ACTION: =ACTION =DATE =TIME USER: =USER RC: =ACTRC')
TEXT ('COMMENT: =COMM');
EPOPULATE;
ELABEL;
LABEL ERR0010; /* TELL USER */
MSG ('ACTIVITY CCID =CCID RECORD NOT FOUND');
ELABEL;
EUSE;
/************************************************
* EXIT POINT: DELETE AFTER *
* PURPOSE: DELETE CHANGE AND ACTIVITY PKG *
* RECORDS, THEN RETURN. *
************************************************/
USE (PDELETE, AFTER);
NOTFOUND (RETURN);
FOUND (DELETE,RETURN);
EUSE;
ETABLE;
04-May-2018 546/1109
CA Endevor® SCM - 17.0
The InfoMan record display panel is the same for packages and for CCIDs. The information displayed
is basic and some fields may be blank when they are not used in a site's InfoMan policy.
ADD/UPDATE
MOVE
RETRIEVE
GENERATE
DELETE
TRANSFER
ARCHIVE
The interface searches the Change and Problem records in InfoMan and returns a list of CCIDs that
have an InfoMan type of ACTION, an InfoMan status other than CLOSED, and meet the wildcard
criteria.
04-May-2018 547/1109
CA Endevor® SCM - 17.0
Note: Wildcarding CCIDs is not allowed when building packages. When a CCID value is fully
specified, a list is not produced. If no InfoMan records meet the wildcard criteria, a CCID
prompt panel appears. The user can type either a fully specified CCID or a wildcarded CCID
on this panel. This search process can be repeated multiple times if necessary.
From the CCID list, you can either view InfoMan correlation information for one or more CCIDs on the
list, or select one of the CCIDs for the action being requested.
Important! If you use the CA Endevor SCM InfoMan Interface, make sure you set up all
your CA Endevor® SCM systems to require CCIDs. For more information, see Administrating
(see page 36).
When using the CA Endevor SCM InfoMan Interface, CA Endevor® SCM CCIDs must start
with an alpha character. In addition, InfoMan stores only the first eight characters of the
CA Endevor® SCM CCID.
S--SELECT
Type this option next to the desired CCID to choose that CCID from this list.
B--BROWSE
Use this option to tell CA Endevor® SCM to display the InfoMan record associated with this CCID.
RNID/CCID
This field displays InfoMan record IDs (RNIDs).
RECORD DESCRIPTION
This field displays the description associated with the InfoMan RNID.
The CCID provided on the prompt panel can also be wildcarded. If CCIDs on the InfoMan side meet
this wildcard criteria, a list selection list appears.
After a user selects a CCID, the interface returns the original action panel.
04-May-2018 548/1109
CA Endevor® SCM - 17.0
After a user selects a CCID, the interface returns the original action panel.
Package Display
Create/Modify Package
Cast Package
Review Package
Execute/Submit Package
Backout Package
If your site does not use InfoMan, or InfoMan correlation information does not exist, this option does
not appear on the panel.
The option appears on the appropriate panels if InfoMan is installed, regardless of whether
InfoMan is storing any package information.
If no correlation exists, the option and the text are shown in normal intensity.
If correlation information exists, the option is shown in high intensity when certain conditions are
met. These conditions are described below.
If the user selects the CI option when no correlation information exists, the ISPF short message
INVALID OPTION appears after you press Enter.
If the user creates the parent record in InfoMan using the CA Endevor® SCM scripts, then CI turns
to high intensity when the package is cast.
04-May-2018 549/1109
CA Endevor® SCM - 17.0
If the user creates the parent record directly in InfoMan, then CI turns to high intensity at the first
exit point invoked from CA Endevor® SCM after the Cast action.
This means that the CI option may stay at low intensity, and therefore unavailable, even when
package information exists in InfoMan. For example, if a user creates parent records for packages
directly in InfoMan, and builds an E/INFO table with only a (CREATE,AFTER) USE statement, the CI
option will not turn to high intensity.
When you type CI and press Enter, this correlation panel appears. Press PF3 to return to the package
panel from which you accessed the correlation information.
The following table contains the RFT streams that produce each report.
04-May-2018 550/1109
CA Endevor® SCM - 17.0
In this syntax, RFT name can be any of the RFT streams in the table in the preceding section. For
example, the following command generates the Action Change Record Summary:
REPORT,8,EINTACH0
InfoMan prompts you for the report destination if the session defaults for print, report, and for
customized report destination are not in your InfoMan profile. To update these fields in your profile
select option 2 (PROFILE) from the InfoMan Main Menu to set the values, or contact your site
InfoMan administrator.
Setting defaults in InfoMan for output destination and class for reports.
How to Set Defaults in InfoMan for Output Destination and Class for Reports
InfoMan stores user profile information, including default output destination and class information
for reports, in the BLG0PROF member in the ISPF profile data set.
Each user can set their own options by invoking an interactive InfoMan session and updating their
own BLG0PROF profile member.
The InfoMan administrator can set up a default profile member for all users.
04-May-2018 551/1109
CA Endevor® SCM - 17.0
To run the reports in batch, modify JCL member BC1JEI35 in the iprfx.iqual.CSIQJCL data set. The
default input stream is all reports. You can select the reports you want to run by modifying the input
stream.
Note: For more information about the InfoMan RFT facility, see your InfoMan
administrator.
Use this report as an inventory list of CCIDs, and to monitor the status of each CCID.
CCID
The CA Endevor® SCM CCID for the action, as recorded in the InfoMan RNID field.
Change Status
Change status of the action.
Approval Status
Approval status of the action.
04-May-2018 552/1109
CA Endevor® SCM - 17.0
Use this report as an audit trail of the actions associated with a particular CCID.
Use these reports the same way that you would use the Action Change Record reports: the Summary
report as an inventory list for CCIDs, and the Detail report as an audit trail for actions associated with
CCIDs.
CCID
The CA Endevor® SCM CCID. For action problem records, this is the same as the InfoMan RNID.
Description
The description of the action from the Populate block of the batch utility, recorded in the free
form text field in the InfoMan record.
Problem Status
The status of the problem.
Date entered
The date this problem record was created in InfoMan.
Assignee name
The person who has been assigned the problem.
Appears on the detail report only. Displays information about this action.
04-May-2018 553/1109
CA Endevor® SCM - 17.0
Curr Stat
Current status of the package change record.
InfoMan RNID
The InfoMan RNID associated with this change record. The RNID is cross referenced with the
correlation field in the package header in CA Endevor® SCM.
InfoMan update
The date when this InfoMan record was last updated.
User
The ID of the user who last updated the record.
Approval status
User-defined status of the approval process.
Description
Description of the package change record.
Package Information
This report contains the following package information:
Curr Stat
Current status of the package change record.
INFO RNID
04-May-2018 554/1109
CA Endevor® SCM - 17.0
INFO RNID
The InfoMan RNID associated with this change record. The RNID is cross referenced with the
CORRELATION field in the package header in CA Endevor® SCM.
InfoMan update
The date when this InfoMan record was last updated.
User
The ID of the user who last updated the record.
Approval status
User-defined status of the approval process.
Package status
Current status of the package in CA Endevor® SCM.
Description
Description of the package.
Activity Information
This report contains the following activity information:
RNID
RNID associated with this activity record.
CCID
CA Endevor® SCM CCID associated with this activity record.
Activity type
Always PKG/ACT for activity records.
Description
Description of the activity record.
04-May-2018 555/1109
CA Endevor® SCM - 17.0
Page 1 of the report contains the information for the parent package record. The report starts a new
page for each activity record.
The freeform text of activity records contains one entry for each action associated with the activity
record CCID.
Phase 2, Step 3 of the installation procedure documented in Step 3. Copy Dictionary Update explains
how to modify the BLG6CORQ panel if you are working with standard InfoMan.
InfoMan administrators at sites that have already modified their InfoMan panels should do the
following:
3. Update the BLG6CORQ panel to point to the index number you have assigned
The reports shown later in this section are standard InfoMan reports that provide the information
needed to modify the BLG6CORQ Panel to support the interface.
04-May-2018 556/1109
CA Endevor® SCM - 17.0
The second report in this section is a PWORD XREF report, and contains the PWORD dictionary entry
for the modified Assisted Entry panel.
This report is for the use of the InfoMan expert at a site that has already customized InfoMan. The
report provides the InfoMan technician with the information needed to customize the appropriate
dictionary entry.
04-May-2018 557/1109
CA Endevor® SCM - 17.0
04-May-2018 558/1109
CA Endevor® SCM - 17.0
04-May-2018 559/1109
CA Endevor® SCM - 17.0
The target audience for this section is those people who have a strong understanding of InfoMan IIF
records and a general knowledge of CA Endevor® SCM. The best combination of people to install the
interface is the site InfoMan administrator and the site CA Endevor® SCM administrator working
together.
04-May-2018 560/1109
CA Endevor® SCM - 17.0
Note: CA Endevor SCM InfoMan Interface requires that the IBM Information Management
product, version 4.2 or higher, is installed at your site.
2. Make sure the Information Management LOAD LIBrary data is in LINKLST or that you have its
data set name available.
3. Prepare a session parameter (BLGSESxx) module to reflect the database, data dictionary, read
panel, and RFT data sets that the interface uses when accessing the data base via the API.
4. Make sure that BLGISPFD, an InfoMan supplied ISPF panel, has been moved into your ISPPLIB
concatenation.
This session parameter is well documented in the InfoMan install manuals. It is required of standard
InfoMan. The naming standard is BLGSESxx where xx is the user's choice. This suffix is also required
for a CA Endevor® SCM start-up block assembly. Note that the same BLGSESxx member can be used
for the interface as well as standard access to InfoMan.
The suffix used to name the actual BLGSESxx module is required in Phase 3. The rest of this install
requires the data set names from the BLGSESxx module.
Note: The interface installation includes 15 modified panels, which must be copied into
your read panel data set concatenation. You can either overlay the IBM version of this data
set, or provide a new read panel data set ahead of the standard IBM data set. Either way,
the result is that the RPANEL0 label points to the data set used in the install.
Sometimes this library is part of LINKLIST, and sometimes it is not. If its data set is not in LINKLST, the
person implementing the interface needs to know the name, and must put it into a STEPLIB in the
concatenation.
04-May-2018 561/1109
CA Endevor® SCM - 17.0
Phase 1 Summary
In this phase of the implementation you have built a vanilla version of InfoMan IIF. At this point you
should have installed InfoMan on your system, assigned users to an InfoMan class, and defined a
BLGSESxx session parameter module. For future reference, record the following:
BLGSESxx:
Within BLGSESxx, you have defined:
Dictionary DD name:
RFTDS DS name:
RPANEL0 name:
1. Copy interface report shells to the RFT data set identified in Phase 1.
BC1JEI20
2. Copy the CA Endevor® SCM versions of the InfoMan IIF panels into the RPANEL0 data set
identified in Phase 1.
BC1JEX15
5. Build a rule set for driving the API using the interface batch utility.
BC1JEX00
6. Assemble or copy the BLGSESxx module into your STEPLIB data set.
BC1JEI05
Step 1. Copy Interface Report Shells into the RFT Data Set
Copy the interface report shells (RFTs) to your RFT data set. Do this using the BC1JEI20 member in
iprfx.iqual.CSIQJCL. Before submitting this JCL, provide a job card, confirm that iprfx.iqual and uprfx.
uqual are the correct data set qualifiers, and confirm that tdisk is a valid unit name.
04-May-2018 562/1109
CA Endevor® SCM - 17.0
EINTACH0
Action Change Record Summary
EINTACH1
Action Change Record Detail
EINTAPB0
Action Problem Record Summary
EINTAPB1
Action Problem Record Detail
EINTPKG0
Package Parent Record Summary
EINTPKG1
Package/Activity Record Summary
EINTPKG2
Package/Activity Record Detail
The modified panel and other CA Endevor® SCM IIF tailored panels are provided with the interface.
Copy them into the RPANEL data set using the JCL in member BC1JEX15 in the iprfx.iqual.CSIQJCL
data set.
This job uses the BLGUT6F utility to copy a PDS member that has been created from a InfoMan panel
using BLGUT6.
This panel must reside above the IBM panel of the same name. The person who runs the job to copy
the modified panel needs only the data set name. You recorded the RPANEL0 data set name in the
worksheet at the end of Phase 1.
Before submitting this JCL, provide a job card, and confirm that iprfx.iqual and uprfx.uqual are the
correct data set qualifiers.
Important! Run this job only if you are installing basic InfoMan. If your site has customized
04-May-2018 563/1109
CA Endevor® SCM - 17.0
Important! Run this job only if you are installing basic InfoMan. If your site has customized
InfoMan, see the appendix "InfoMan Information for Advanced Users (see page 556)" for
instructions on updating the dictionary entry.
Before submitting this JCL, provide a job card, and confirm that iprfx.iqual and uprfx.uqual are the
correct data set qualifier.
Use the BC1JEX45 member in iprfx.iqual.CSIQJCL. This JCL is shown next. Before submitting the JCL,
provide a job card and ensure that iprfx.iqual and uprfx.uqual are the correct data set qualifiers.
EISCRXX1
Batch utility input for stand-alone actions, using IIF InfoMan Change records.
EISCRXX2
Batch utility input for stand-alone actions, using IIF InfoMan Problem records.
EISCRXX3
Batch utility input for package functions and package actions under IIF InfoMan.
Next, create a rule set. It is advisable to keep it simple at first. Do this by taking one or two actions or
package functions and writing utility syntax input for them. Then run the batch utility to create an
initial rule set. The JCL for executing the utility to build the rule set is in member BC1JEX00 of iprfx.
iqual.CSIQJCL.
A successful run of the utility produces a load module called by a name you specify. This load module
name is used in Phase 3. Assemble this load module into a STEPLIB data set.
Remember:
To change what you use the interface for is a simple run of the utility. It requires no further
InfoMan or CA Endevor® SCM work to enhance the rule set.
If you point to any PIDT tables other than the defaults, verify that they reside in the RFTDS data
set pointed to in your BLGSESxx member.
04-May-2018 564/1109
CA Endevor® SCM - 17.0
The JCL for executing the utility to build the rule set is in member BC1JEX00 of iprfx.iqual.CSIQJCL.
Before submitting this JCL, provide a job card, confirm that iprfx.iqual and uprfx.uqual are the correct
data set qualifiers, confirm that tdisk is a valid unit name and, if necessary, change the size of the
WORK1 or WORK2 data sets.
Before submitting this JCL, provide a job card, confirm that uprfx.uqual are the correct data set
qualifiers, confirm that tdisk is a valid unit name, and replace xx in the string BLGSESxx with a session
identifier.
Phase 2 Summary
The pieces are now in place for the interface on both the InfoMan and the CA Endevor® SCM sides. In
Phase 3, these pieces are connected to enable the interface.
This phase of the installation process involves setting up the InfoMan and CA Endevor® SCM sides of
the interface to work together, as described:
4. Make sure that required panels are in the ISPPLIB data set.
5. Make sure that members INFO01 and PKMR02 are in your ISPMLIB data set.
6. Edit C1SB3000 skeleton JCL. These steps are described in the following sections.
The @EINFO macro, supplied with the interface, provides input to BC1TEI90. The macro can be found
embedded in member BC1JEI10 in iprfx.iqual.CSIQJCL. Edit this macro based on the information
contained in the Phase 1 checklist and your site standards. The @EINFO macro is shown next.
04-May-2018 565/1109
CA Endevor® SCM - 17.0
@EINFO ENTRY=START,
BLGSESS=00,
APISESID=USERID,
EPIDT=ENDEVOR,
INVCLASS=MASTER,
WAITTIME=300,
RECTYPE=CHANGE,<tab>
@EINFO ENTRY=END
ENTRY=START
Indicates the beginning of the BC1TEI90 table.
BLGSES=
InfoMan looks for session parameters in a module named BLGSESxx, where ‘xx’ is a two-character
identifier for the module. This module is described in the InfoMan documentation. You recorded
the components of this module during Phase 1 of this installation, as well as the two-character
identifier for the module. When modifying the @EINFO macro supplied with the interface,
replace the default value 00 with the value you specified in Phase 1.
The default is 00. This is the same as standard InfoMan.
APISESID=
The API requires a session ID during initialization. This session can be called USERID or can be a
predefined InfoMan API ID.
The default is USERID. Leaving this default allows the same start-up module to be used by many
people, with the interface substituting the user ID of the caller for the literal USERID.
If you include this keyword, you must provide a value.
EPIDT=
This keyword contains the name of the assembled E/INFO table produced by the batch utility. The
default is Endevor.
If you include this keyword, you must provide a value.
INVCLASS=
InfoMan has its own security system. It is broken into classes with privileges. Every user or API ID
is assigned to at least one CLASS. The API requires a class name.
The default is MASTER.
WAITTIME=
The API allows the application to define how long it will wait for a response from the InfoMan API
server. If the user does not use this keyword, the default will be 300 seconds.
RECTYPE=
Users must select one kind of InfoMan record for recording information about stand-alone
actions. They can use either Change or Problem records. Display services also need this
information.
The default is CHANGE. If coded, it cannot be blank.
ENTRY=END
(Required) This statement denotes the end of the BC1TEI90 table.
04-May-2018 566/1109
CA Endevor® SCM - 17.0
DB2=N, DB2 CONTROL OPTION X
ESSI=N, ESSI CONTROL OPTION X
INFO=N, INFOMAN CONTROL OPTION X
LIBENV=, LIBRARIAN (LB), PANVALET (PV) X
LIBENVP=N, LIBRARIAN/PANVALET OPTION X
LIBRPGM=, LIBRARIAN BATCH PROGRAM NAME X
LINESPP=60, LINES PER PAGE X
MACDSN='iprfx.iqual.CSIQOPTN', E/OS/390 SOURCE LIBRARY X
PKGDSN='UPRFX.UQUAL.PACKAGE', PACKAGE DATASET NAME X
PKGTSO=N, FOREGROUND PACKAGE EXEC (Y//N) X
PDM=N, PDM CONTROL OPTION X
PKGSEC=, PACKAGE SECURITY X
PKGCSEC=N, PACKAGE CAST SECURITY (Y/N) X
PKGCVAL=0, PKG COMPONENT VALIDATION (Y/O) X
PROC=N, PROCESSOR OPTION X
RACFUID=, E/OS/390 RACF USERID X
SITEID=0, E/OS/390 SITE ID X
SMFREC#=0, SMF RECORD NUMBER X
SPFEDIT=SPFEDIT, DEFAULT PDS RESERVE X
SYSIEWL=SYSIEWLP, DEFAULT PDS/LINK EDIT RESERVE X
UIDLOC=(1,7), UID/JOBNAME START/LENGTH POS X
VIOUNIT=TDISK, UNIT FOR VIO-ELIGIBLE ALLOC X
WRKUNIT=TDISK, UNIT NAME FOR WORK SPACE X
WORKVOL= VOL SER NUMBER FOR WRKUNIT
Use an SMP/E USERMOD to assemble and link-edit C1DEFLTS after it has been customized.
Alternatively, edit the sample JCL BC1JTABL and use it to assemble and link source module C1DEFLTS
outside of SMP/E. BC1JTABL is located in the installation library iprfx.iqual.CSIQJCL. This will store the
defaults table in iprfx.iqual.CSIQAUTU as member C1DEFLTS.
C1EILIST, CITILIST
CCID list panel and its associated tutorial panel.
C1SEIBRW, CITEIBRW
04-May-2018 567/1109
CA Endevor® SCM - 17.0
C1SEIBRW, CITEIBRW
InfoMan record display for packages and stand-alone actions and its associated tutorial panel.
CSIQAUTH/CSIQAUTU
Load modules, as well as the following:
C1BMEI00
C1DEFLTS table. See Step 3. Reassemble C1DEFLTS with the InfoMan Password.
C1SM1000
BC1TEI90, the module containing user parameters, which you assembled in Phase 3, Step 1.
E/INFO table. This is the rule set that you build using the batch utility. See Step 5. Build a Rule
Set.
BLGSESxx, the module containing the InfoMan session parameters. See Step 2. Prepare a
Session Parameter Member.
CONLIB
The CA Endevor® SCM load modules installed from iprfx.iqual.CSIQLOAD. Make sure to save the
current copy of C1BEXITS before installing the new interface. This allows you to go back to the old
interface during testing.
04-May-2018 568/1109
CA Endevor® SCM - 17.0
RFTDS
EINTACH0, EINTACH1, EINTAPB0, EINTAPB1.
EINTPKG0, EINTPKG1, EINTPKG2.
PIDT and PIPT tables. See the list in the next section. These panels are found in iprfx.iqual.
CSIQOPTN.
BLGISPFD, the InfoMan supplied ISPF panel.
RPANEL0
BLG6CORQ, the modified version of the Assisted Entry panel.
BLGAPI10, BLGAPI90, BLGAPI92, BLGAPI95, BLGAPI99.
BLGZAACP, BLGAAUP.
BTN0B100, BTN0C100, BTN0C101, BTN0L100, BTN0M100, BTN0S020, BTN6PTY1.
See Step 3. Copy Dictionary Update.
DDICT
index RNCC/CCV15. This is the modified dictionary entry associated with the modified Assisted
Entry Panel. See Step 4. Create the Standard IBM PIDT and PIPT Tables.
iprfx.iqual.CSIQPENU
C1EILIST, C1SEIBRW, C1SP1000 ── C1SP7000 and the associated tutorials (CITILIST, CITEIBRW, and
CITP1000-CITP7000.
iprfx.iqual.CSIQMENU
INFO01, PKEX21, PKMR02.
iprfx.iqual.CSIQSENU
C1SB3000.
The graphic displayed next shows how these modules tie the interface together and indicates the
important members that should be at each location.
04-May-2018 569/1109
CA Endevor® SCM - 17.0
As previously illustrated, the interfaces work based on how the modules tie them together.
There are three categories of PIDT/PIPT tables: Change, Change Activity, and Problem.
TS0B06A
Change record, Add, PIDT
TS0B06AP
Change record, Add, PIPT
TS0B06I
Change record, Inquiry, PIDT
TS0B06IP
Change record, Inquiry, PIPT
TS0B06C
Change record, Create, PIDT
04-May-2018 570/1109
CA Endevor® SCM - 17.0
TS0B06CP
Change record, Create, PIPT
TS0B06U
Change record, Update, PIDT
TS0B06UP
Change record, Update, PIPT
TS0B06R
Change record, Retrieve, PIDT
TS0B06RP
Change record, Retrieve, PIPT
TS0B07I
Change activity record, Inquiry, PIDT.
TS0B07IP
Change activity record, Inquiry, PIPT.
TS0B07C
Change activity record, Create, PIDT.
TS0B07CP
Change activity record, Create, PIPT.
TS0B07U
Change activity record, Update, PIDT.
TS0B07UP
Change activity record, Update, PIPT.
TS0B07R
Change activity record, Retrieve, PIDT.
TS0B07RP
Change activity record, Retrieve, PIPT.
TS0032I
Problem record, Inquiry, PIDT.
TS0032IP
Problem record, Inquiry, PIPT.
04-May-2018 571/1109
CA Endevor® SCM - 17.0
TS0032C
Problem record, Create, PIDT.
TS0032CP
Problem record, Create, PIPT.
TS0032U
Problem record, Update, PIDT.
TS0032UP
Problem record, Update, PIPT.
TS0032R
Problem record, Retrieve, PIDT.
TS0032RP
Problem record, Retrieve, PIPT.
04-May-2018 572/1109
CA Endevor® SCM - 17.0
Inventory Analyzer
Contents
This article introduces the CA Endevor® SCM Inventory Analyzer tool. The Inventory Analyzer
automatically classifies existing software components:
Physical classifications (types and processor groups), which can be used within CA Endevor® SCM.
Types and processor groups are product physical classification of components, such as JCL or
COBOL for DB2. The Inventory Analyzer provides a standard set of types and processor groups.
You can change the type and processor group names to meet the inventory naming conventions
you want to use.
Logical classifications (systems and subsystems). The Inventory Analyzer helps with this type of
classification by allowing you to take advantage of library and member naming standards.
Software components, which can reside in CA Librarian, CA Panvalet, or partitioned data sets. The
Inventory Analyzer can examine source, object, or load modules. Components that are not
compiled or translated (such as JCL, CLISTS, and so forth) are analyzed on a source-only basis.
When CA Endevor® SCM is initially implemented, the system creates an inventory structure that lets
you classify your source logically by application. CA Endevor® SCM creates the inventory structure by
examining the following components:
Existing component source and executables to determine component types. This is physical
classification.
Library naming conventions, or other grouping criteria, or both to determine your components'
logical classification.
Note: The Inventory Analyzer is not designed to categorize all of your software
components. For more information about the product inventory structure, see
Administrating (see page 36).
User Requirements
To use this product, you need a working knowledge of the mainframe environment, the z/OS
mainframe operating system, Time Sharing Option facility (TSO), and the Interactive System
Productivity Facility (ISPF). CA Endevor® SCM must be at your site.
04-May-2018 573/1109
CA Endevor® SCM - 17.0
Audience
Administrators and application developer managers benefit from using the Inventory Analyzer.
Administrators use the Inventory Analyzer to plan for and set up the logical and physical
components of your inventory structure.
Application Developer Managers use the Inventory Analyzer to help the administrator plan the
implementation of the inventory structure.
The following example shows the SCL generated by the Inventory Analyzer:
LOAD MEMBER APFLIST
FROM DSNAME 'BST.UTILS2.SOURCE'
TO ENVIRONMENT DEMO
SYSTEM FINANCE
SUBSYSTEM ACCTREC
TYPE ASSEM
OPTIONS CCID 'TESTCCID'
COMMENT 'TEST COMMENT'
PROCESSOR GROUP ASHNBL13
FOOTPRINT 'BST.UTILS2.LOADLIB'
LOAD MEMBER APNCO
FROM 'BST.UTILS2.SOURCE'
TO ENVIRONMENT DEMO
SYSTEM FINANCE
SUBSYSTEM ACCTREC
TYPE ASSEM
OPTIONS CCID 'TESTCCID'
COMMENT 'TEST COMMENT'
PROCESSOR GROUP ASHNBL47
FOOTPRINT 'BST.UTILS2.LOADLIB'
The environment, system, subsystem, CCID, and comment were all assigned in analysis requests
(in SET statements). The Request Syntax report reflects these request statements.
Note: For more information about the Request Syntax Report, see The Request Syntax
Report.
The library in which each member is to be footprinted defaults to the USING library in which the
member is found, as is indicated in the Output Model Definition Syntax Report by the line:
FOOTPRINT 'C1&USDN'
04-May-2018 574/1109
CA Endevor® SCM - 17.0
The Inventory Analyzer analyzes each of the USING data sets indicated in the analysis request until it
finds the member. The FROM data set is analyzed to determine whether the member exists there
also.
Note: For more information about the Load Utility, see Load Utility (see page 1091).
This illustration shows the roles of the Inventory Analyzer and the Load Utility in relation to the CA
Endevor® SCM inventory structure:
The Analysis Requests File provides the member names and library names to be examined and
analyzed by the Inventory Analyzer. Each member is individually processed, and can be specified
singly or as part of a group. Symbolics are assigned values to be included in the output data sets.
Global settings can be established and overridden on an individual request basis.
The Output Model Definition provides templates that define the format of SCL syntax that can be
used to load analyzed members into CA Endevor® SCM. Several templates can be identified within
one input file, each directed to a separate output DD statement.
Several reports are created that let you review selected portions of the analysis. In addition, the
04-May-2018 575/1109
CA Endevor® SCM - 17.0
Several reports are created that let you review selected portions of the analysis. In addition, the
Inventory Analyzer creates SCL that can be entered into CA Endevor® SCM. The Inventory
Analyzer produces reports that contain information pertinent to a particular part of the analysis
process. The following list shows the available Inventory Analysis reports:
Parameter Syntax
Request Syntax
Rule Syntax
Rule Analysis
Request Processing
Analysis Summary
Execution Summary
Note: You can review the Inventory Analysis reports using the following detail levels:
summary, detail, and all. You select the amount of data that you want to see by using a
control card that is part of your analysis request.
Use the SCL that is created to load the classified elements directly into CA Endevor® SCM. The
elements are loaded using the Load Utility.
04-May-2018 576/1109
CA Endevor® SCM - 17.0
1. Complete the Customize the Sample JCL (see page 577) procedure.
Determine which source and load libraries you want to analyze. You most likely will want
to analyze production load, source, JCL, and any other libraries containing elements that
lend themselves to use with CA Endevor® SCM. We recommend that you use load libraries
whenever possible, as load modules are more reliable when determining element type
and processor group.
Decide which members you want to analyze. You can use a name mask when specifying
member names.
Note: You can assign specific values to symbolics which reflect the system and
subsystem designations, as well as environment, CCID, and comment, at your site.
Using this statement in conjunction with member name masking, you can create
most of the SCL (load syntax) required for the load function.
For more information about creating (coding) the ANALYZE statements, see How to Use
Analysis Request Statements (see page 579).
2. Customize the Output Model Definition. The output model definition is used to generate SCL
that you can use to load analyzed members into CA Endevor® SCM. The Inventory Analyzer
contains a predefined output model definition. You can customize the output model
definition, as necessary.
You can create syntax to add to the SCL initially generated by the Inventory Analyzer. You can
also replace the SCL.
3. Decide which reporting level (summary, detail, or all) you want to use for the Inventory
Analyzer reports. In most cases, the reports produced by the summary level should be
sufficient for your needs.
4. Customize the JCL to point to the CA Endevor® SCM libraries containing the analysis rules, the
04-May-2018 577/1109
CA Endevor® SCM - 17.0
4. Customize the JCL to point to the CA Endevor® SCM libraries containing the analysis rules, the
output model definition, and the input ANALYZE statements. The rules are divided into several
members, one or more of which can be omitted (unless that member is required, as indicated
in the following list). For example, if your site does not use DB2, you may want to omit that
member.
The following indicates how rules are grouped in the source library:
DEFINES
Language Definitions (required)
NODBMS
Batch (required)
DB2DBMS
DB2 (optional)
IDMSDBMS
IDMS (optional)
IMSDBMS
IMS (optional)
TOTALDBM
TOTAL (optional)
OTHERS
OTHERS (required)
Important! A basic rule set is provided on your installation tape to analyze the
majority of your current data (source, object, and load). Do not modify this rule
set, except as specified in customizing the Inventory Analyzer. If you encounter
source, object, or load data that cannot be classified by the Inventory Analyzer (as
indicated by the Inventory Analysis reports), you can manually classify those
modules.
The most important information presented in the reports tells you the following:
How many members of each type and processor group were found. This information lets you
define the appropriate inventory structures to CA Endevor® SCM for eventual loading.
04-May-2018 578/1109
CA Endevor® SCM - 17.0
Which members could not be classified. "Failure" SCL is written for those members that could not
be uniquely classified. As much information as is available is provided in this SCL. You should
classify these members manually, by editing the load SCL with the appropriate remaining values.
Important! If load modules were examined, review the Load Module Summary Report to
ensure that all modules contain the same link attributes. If there are load modules of the
same type and processor group but with different attributes, the specified processor group
may have to be classified into one or more separate processor groups, to accommodate
the differences.
You need to decide whether you want to use this capability at this time.
If you want to use the Load Utility, you must first do the following:
Create the appropriate processors for the different types from within CA Endevor® SCM.
ANALYZE statements. These are the only request statements executed by the Inventory Analyzer.
Use ANALYZE statements to select members for analysis and to specify the libraries to be
referenced during analysis.
SET statements. These are global default statements that establish values for subsequent
ANALYZE statements. If a certain parameter is required (or used) but not coded in an ANALYZE
statement, the Inventory Analyzer looks for that information in a previous SET statement.
CLEAR statements. These statements clear the information designated by a related SET
statement.
EOF (EOJ) statement. This statement instructs the Inventory Analyzer to stop parsing the request
syntax at a point; that is, request processing is terminated. No other requests are read from the
request input file once the EOF (EOJ) statement is encountered.
04-May-2018 579/1109
CA Endevor® SCM - 17.0
The following section explains each statement. If you need help when coding the requests, see How
CA Endevor SCM Represents Syntax (https://docops.ca.com/display/CE17
/Parallel+Development#ParallelDevelopment-SCLStatementSyntaxConvention).
Note: If you specify the parameter SOURCE OPTIONAL in the execution JCL, you do not
need to code FROM or SET FROM information. For more information, see How the SET
ASSIGN Statement Assigns the Default CCID and Comment (see page 585) and How to Use
Additional SET ASSIGN Statements within Requests (see page 585).
For more information about coding data set names in this clause, see How to Enter Information in
the Data Set Clauses (see page 581).
04-May-2018 580/1109
CA Endevor® SCM - 17.0
DSNAME data.
The data sets can be any combination of object or load libraries. The following are the
recommended guidelines:
You specify load libraries before object libraries when both types of libraries are present. A
better analysis can be performed using load libraries.
The source and executable member names are different, but follow standard naming
conventions. You can customize an exit specific to the Inventory Analyzer to accommodate
the situation.
For more information about coding data set names in this clause, see How to Enter Information in
the Data Set Clauses (see page 581).
ASSIGN symbol-name=symbol-value
Optional. Indicates a user-defined symbolic to be used in building SCL, along with the value
associated with that symbolic. Specify as many user-defined symbolics that you need. You can
assign values to one or more of the following symbolics:
When building SCL to load the data classified by the Inventory Analyzer, an output model
definition template is used. When a user-defined symbolic is found in the template, the Inventory
Analyzer looks for a corresponding symbol-name in the ASSIGN clause of the request. Before
writing the SCL, the symbolic is replaced with the appropriate value, as defined by the ASSIGN
clause.
Specify one or more data sets, up to 1000 names. If you enter multiple data sets, separate the
names with blanks and enclose all names in a single set of parentheses. If you code only one data
set, you do not have to use parentheses.
Enclose each data set name in single or double quotes, and use the same convention for each
data set name in the list. Be sure each data set is cataloged in the system catalog.
The Inventory Analyzer checks each data set for members matching the selection criteria. The
order in which the data sets are specified becomes the search order. If a member is found in
more than one data set, the Inventory Analyzer selects the first occurrence of that member.
04-May-2018 581/1109
CA Endevor® SCM - 17.0
Note: This information also applies to the SET FROM DSNAME and SET USING DSNAME
statements.
The Inventory Analyzer first classifies members in the load library. Members classified successfully as
a result of the analysis of PROD.LOADLIB are bypassed in PROD.SOURCELIB. That is, those members
are not classified again in the source library. The load SCL created, however, loads the appropriate
members into CA Endevor® SCM from PROD.SOURCELIB.
The ASSIGN statements assign the specified values to the appropriate variables in the output model
definition. The SCL generated from this example can be used to load the analyzed members into the
following CA Endevor® SCM location: environment PROD, system GENERAL, and subsystem GENERAL.
The CCID LOAD and the comment 'INITIAL ENDEVOR LOAD' are assigned to each member.
How the Inventory Analyzer Analyzes All Members Using Different Selection Criteria
The following example is similar to the previous example in that the same libraries are to be analyzed
and the same symbolic values are assigned. However, the member selection criteria are different
(note the ANALYZE MEMBER . . .THROUGH . . .clause):
ANALYZE MEMBER FI?A?C
THROUGH FI?D?C
FROM DSN ('PROD.SOURCELIB' 'PROD.PANLIB')
USING DSN 'PROD.LOADLIB'
ASSIGN ENV='PROD'
SYS='FINANCE'
SBS='ACCTREC'
CCID='LOAD"
COMMENT='INITIAL CA Endevor® SCM LOAD'
The third and fifth positions of the member name, as indicated by the placeholder (?), may
contain any valid character (A-Z, 0-9, @, #, $).
The fourth position of the member name can only be A, B, C, or D. Any other character in this
position is not accepted.
04-May-2018 582/1109
CA Endevor® SCM - 17.0
FINARC
FI5C6C
FIND#C
The ASSIGN statements indicate the values to be assigned to the variables in the output model
definition. All members whose names begin with FINAR can be loaded into environment PROD,
system FINANCE, and subsystem ACCTREC in CA Endevor® SCM, and are assigned a CCID of LOAD and
the comment 'INITIAL ENDEVOR LOAD'.
A SET statement establishes default parameters for specific items that are omitted from subsequent
ANALYZE requests. If a parameter is required (or used) but not coded in a request, the information
can be obtained from a previous, corresponding SET statement.
For example, if you want to use one FROM data set for several requests, you can specify that data set
by:
Entering a SET FROM DSNAME statement. The data set specified is applied to every ANALYZE
request that follows that SET statement.
"Reissuing" a SET statement to change the default values as often as you need. SET statements
remain in effect until another (similar SET statement or a related CLEAR statement) is
encountered or processing ends.
04-May-2018 583/1109
CA Endevor® SCM - 17.0
If you code the SOURCE OPTIONAL parameter on the execution JCL, you do not need to include
FROM information in the ANALYZE request.
For example, you code a SET FROM DSNAME statement. In the first four ANALYZE requests following
the SET statement, you do not enter a FROM data set. In the fifth request, you enter a data set name.
The Inventory Analyzer applies the data set name from the SET statement for the first four requests.
For the fifth request, however, the Inventory Analyzer uses the value coded in the ANALYZE request.
The value in the SET statement is ignored.
SET ASSIGN applies to each request that uses, but does not contain, an ASSIGN clause. The SET
ASSIGN statement remains in effect until the system encounters another SET ASSIGN statement with
the same symbol or a CLEAR ASSIGN statement, or processing ends.
SET FROM and SET USING apply to each request that uses, but does not contain, a FROM DSNAME or
USING DSNAME clause respectively. The SET FROM statement remains in effect until the system
encounters another SET FROM statement or a CLEAR FROM statement, or processing ends. Similarly,
the SET USING statement remains in effect until the system encounters another SET USING statement
or a CLEAR USING statement, or processing ends.
The rules and processing for data sets apply to the data sets coded in these statements. For more
information, see How the Inventory Analyzer Analyzes All Members (see page 582).
SET REPORT LEVEL is a control card that lets you select the amount of information that you want to
receive as part of your reports (that is, which reports you want to see). If you want to use this
statement, code it with the ANALYZE request.
There are three levels (options) of information available. Each level provides a different set of
reports, as follows:
Summary
04-May-2018 584/1109
CA Endevor® SCM - 17.0
Summary
Parameter Syntax, Request Syntax, Output Model Definition, Final Request Interpretation,
Analysis Summary Report, Load Module Summary Report, Execution Summary Report.
Detail
Default. The reports listed in Summary, as well as the Request Processing report.
All
The reports listed in Summary, as well as the Rule Syntax, Rule Analysis, and Final Rule
Interpretation reports.
Note: For more information about reports, see Using the Inventory Analyzer Reports (see
page 595).
How the SET ASSIGN Statement Assigns the Default CCID and Comment
Use the following SET ASSIGN statement to assign the default CCID and comment to each member
analyzed, across all requests. This statement is based on the requests in How the Inventory Analyzer
Analyzes All Members, How the Inventory Analyzer Analyzes Specific Members, and How the
Inventory Analyzer Analyzes All Members Using Different Selection Criteria.
┌──,────────────────────────────┐
►►──SET ASSign──(─▼──symbol-name1 = symbol-value1─┴─)───.───────────────►◄
Using this statement, you could enter the three ANALYZE requests as follows:
SET ASSIGN CCID='LOAD' COMMENT='INITIAL CA Endevor® SCM LOAD'.
ANALYZE MEMBER *
FROM DSN 'PROD.SOURCELIB'
USING DSN 'PROD.LOADLIB'
ASSIGN ENV='PROD'
SYS='GENERAL'
SBS='GENERAL'
.
ANALYZE MEMBER FINAR*
FROM DSN ('PROD.SOURCELIB' 'PROD.PANLIB')
USING DSN 'PROD.LOADLIB'
ASSIGN ENV='PROD'
SYS='FINANCE'
SBS='ACCTREC'
.
ANALYZE MEMBER FI?A?C
THROUGH FI?D?C
FROM DSN ('PROD.SOURCELIB' 'PROD.PANLIB')
USING DSN 'PROD.LOADLIB'
ASSIGN ENV='PROD'
SYS='FINANCE'
SBS='ACCTREC'
04-May-2018 585/1109
CA Endevor® SCM - 17.0
The CCID and comment assigned at the beginning of the series of requests are still applied to the
second and third requests. Remember that all SET statements remain in effect until another
statement (a similar SET statement or a CLEAR statement) is encountered, or processing ends.
Note: CLEAR statements apply only to SET statements. Similar information entered in the
ANALYZE request is not affected by a CLEAR statement.
CLEAR ALL clears all information established by all previous SET statements. Make sure that you
specify all required information in subsequent ANALYZE requests, or code new SET statements for the
required information.
CLEAR ASSIGN clears all symbolics entered in previous SET ASSIGN statements.
CLEAR FROM and CLEAR USING clear information entered in previous SET FROM and SET USING
04-May-2018 586/1109
CA Endevor® SCM - 17.0
CLEAR FROM and CLEAR USING clear information entered in previous SET FROM and SET USING
statements.
Code EOF or EOJ, followed by a period. Use the term with which you are most comfortable.
If the member is not located in any FROM library, the request is terminated.
Note: If you specify the parameter SOURCE OPTIONAL in the execution JCL,
you do not have to code FROM or SET FROM information. For more
information, see Understanding the Execution JCL (see page 599).
Second None Searches for the member in a USING library, if that library is specified. Each
occurrence of the member is noted in the Request Processing report. The
first occurrence of the member is used for executable scanning.
If the member is not located in any USING library, the request is terminated.
04-May-2018 587/1109
CA Endevor® SCM - 17.0
Important! Do not modify any of the supplied Inventory Analyzer source members.
1. Complete How the Output Model Definition Input File Works (see page 588).
4. Complete How the Output Model Definition Template Works (see page 592).
04-May-2018 588/1109
CA Endevor® SCM - 17.0
ddname
Data set to which the template is written.
A single DDname can be referenced by one or more control cards, and each template is written to
that file when the conditions are met. If the DDname is not allocated, a warning message is
written to the Execution Report and processing continues. Be sure that the DDname referenced is
coded in the JCL executing the Inventory Analyzer.
COND=
Conditions under which the template is used: success only, failure only, or either. For more
information, see How Symbolics Work in the Output Model Definition Template (see page 593).
SCL template
Template (a combination of literals and symbolics) to be written to the DDname specified. For
more information, see How Symbolics Work in the Output Model Definition Template (see page
593).
When a symbolic parameter is followed by any character other than a special character (with the
exception of a period or a left parenthesis) the parameter must be followed by a period to separate it
from subsequent text. Special characters include the following: , / ' ) * & + - = .
To maintain a period in the text, you need to code two periods. For example, to include a period in a
data set name, you would code a statement similar to the following:
DSN=&dsname...LOADLIB
If you substitute the value PROD for &dsname, the resulting data set name appears as follows:
PROD.LOADLIB
1. Read the section, How User-defined Symbolics Work (see page 590).
2. Read the section, How CA Endevor SCM Symbolics Work (see page 589)
3. Read the section, How Symbolic Substringing Works (see page 591).
04-May-2018 589/1109
CA Endevor® SCM - 17.0
1. Define local symbolic values in each request statement using the ASSIGN statement.
3. Override a global value by entering the appropriate “like” data in an individual request.
You can assign values to one or more of the following symbolics (which are coded in the ASSIGN
statement of the ANALYZE request):
Symbolic Description
&ENV Defines an environment
&SYS Defines a system
&SBS Defines a subsystem
&CCID Specifies a CCID
&COMMENT Specifies a comment
When the Inventory Analyzer finds one of these entries, it substitutes the appropriate value in the
output model definition.
04-May-2018 590/1109
CA Endevor® SCM - 17.0
Data set symbolics have a NULL value when they are not applicable to a request. For example, if
you used a single source (FROM) data set but no output (USING) data set to analyze a member,
&C1FDSN contains the name of the source data set. The remaining data sets (&C1FDSN.xx,
&C1UDSN, and &C1UDSN.xx) are empty, or NULL.
&C1ELTYPE and &C1PRGRP contain type and processor group names when a unique solution has
been established.
If no solution is determined or multiple solutions are possible, a FAILURE condition results. In this
situation, &C1ELTYPE defaults to the user-defined symbolic "&TYPE" and &C1PRGRP defaults to
the user-defined symbolic "&PRGRP." This situation essentially allows you to assign default values
to the symbolics &C1ELTYPE and &C1PRGRP, by assigning the desired values to the symbolics
&TYPE and &PRGRP.
Important! You cannot define symbolics beginning with the characters C1. These
characters are reserved for use by CA Endevor® SCM. In addition, you cannot assign a
default value to a symbolic that begins with C1.
Commas are used to separate the arguments in the substring syntax. The following is the syntax for
symbolic substringing:
&symbolic(&S,&L,&P)
&S
Starting position of the substituted value.
&L
Length of the substituted value.
&P
Character to be used for padding blanks.
The following table contains examples for how substring processing works. Assume the symbolic SYS
contains the value ACCOUNTG.
Substring Generates
&SYS ACCOUNTG
&SYS(3) COUNTG
&SYS(3,5) COUNT
&SYS(7,4) TGbb (where b is a blank)
04-May-2018 591/1109
CA Endevor® SCM - 17.0
Substring Generates
&SYS(7,4,*) TG**
SUCCESS condition. When a member is analyzed and the type and processor group are uniquely
(successfully) identified, the first template is written to a DD statement called LOADSCL.
FAILURE condition. When a member is analyzed but the type and processor group are not
uniquely identified, the second template is written to the DD statement LOADSCL.
The following template illustrates how the output model definition produces SCL for use with the
Load Utility. This template is provided on the installation tape you receive as part of the installation
materials, in iprfx.iqual.CSIQOPTN (MODEL).
%DDNAME=LOADSCL,COND=SUCCESS
LOAD MEMBER &C1MEMBER
FROM DSNAME '&C1FDSN'
TO ENVIRONMENT &ENV
SYSTEM &SYS
SUBSYSTEM &SBS
TYPE &C1ELTYPE
OPTIONS CCID '&CCID'
COMMENT '&COMMENT'
PROCESSOR GROUP &C1PRGRP
FOOTPRINT '&C1UDSN'.
%DDNAME=LOADSCL,COND=FAILURE
LOAD MEMBER &C1MEMBER
FROM DSNAME '&C1FDSN'.
TO ENVIRONMENT &ENV
SYSTEM &SYS
SUBSYSTEM &SBS
TYPE &TYPE.
OPTIONS CCID '&CCID'
COMMENT '&COMMENT'
PROCESSOR GROUP PRGRP
FOOTPRINT '&C1UDSN'.
Both templates are written to the same DD file to allow you to manually correct any statements, as
necessary. If you want failures to be written to a separate DDname, change the DDname in the
COND=FAILURE template and include the appropriate JCL in member BC1JANLZ in the CA Endevor®
SCM library.
The FAILURE template references the symbolics &TYPE and &PRGRP rather than the CA Endevor®
SCM supplied symbolics &C1ELTYPE and &C1PRGRP. When &C1ELTYPE and &C1PRGRP cannot be
determined by the Inventory Analyzer, a FAILURE condition results. Change type and processor group
defaults to &TYPE and &PRGRP, to which values can be assigned.
&C1ELTYPE and &C1PRGRP must both be resolved to have a SUCCESS condition. Type cannot be
resolved without processor group and conversely, processor group cannot be resolved without type.
04-May-2018 592/1109
CA Endevor® SCM - 17.0
In a SUCCESS condition, when the appropriate values are substituted for both CA Endevor® SCM
symbolics and user-defined symbolics, the following load SCL is created:
LOAD MEMBER FINARP01
FROM DSNAME 'PROD.SRCLIB'
TO ENVIRONMENT CORP
SYSTEM FINANCE
SUBSYSTEM ACCTREC
TYPE COBOL
OPTIONS CCID 'TEST'
COMMENT 'ACCOUNTS RECEIVABLE ELEMENT'
PROCESSOR GROUP 'COBNBL01'
FOOTPRINT 'PROD.LOADLIB1' 'PROD.LOADLIB2'.
.
The Inventory Analyzer substitutes the appropriate values for the CA Endevor® SCM symbolics based
on the results of the analysis. The first member found matching the member name criteria is
FINARP01.
&C1FDSN is replaced by the FROM data set (PROD.SRCLIB) used by the Inventory Analyzer for the
analysis. The USING data sets used for analysis replace &C1USDN. The Inventory Analyzer was
able to determine unique values for the type and processor group (&C1ELTYPE and &C1PRGRP,
respectively). These values have been substituted into the SCL accordingly.
The values defined in the ASSIGN statement are substituted. FINARP01 is loaded into the
FINANCE system, ACCTREC subsystem, in environment CORP. The CCID TEST is designated for the
member, as well as the comment 'ACCOUNTS RECEIVABLE ELEMENT'.
Note: In the basic output model definition provided in the installation files, the symbolics
&ENV, &SYS, &SBS, &CCID, and &COMMENT are defined.
04-May-2018 593/1109
CA Endevor® SCM - 17.0
COMMENT 'ACCOUNTS RECEIVABLE ELEMENT'
PROCESSOR GROUP &PRGRP.
FOOTPRINT 'PROD.LOADLIB1' 'PROD.LOADLIB2'
.
You can edit this SCL by manually coding the missing information (type and processor group).
How the Same Template is Used for a SUCCESS and FAILURE Condition
In the following example, the same template is used for either a SUCCESS or FAILURE condition.
&C1ELTYPE and &C1PRGRP are used as the symbolics for type and processor group. In a FAILURE
condition, when &C1ELTYPE and &C1PRGRP cannot be resolved, these variables default to &TYPE and
&PRGRP, which default to their respective user-defined values.
%DDNAME=LOADSCL,COND=(SUCCESS,FAILURE)
LOAD MEMBER &C1MEMBER.
FROM DSNAME '&C1FDSN'.
TO ENVIRONMENT &ENV.
SYSTEM &SYS.
SUBSYSTEM &SBS.
TYPE &C1ELTYPE.
OPTIONS CCID '&CCID'
COMMENT '&COMMENT'
PROCESSOR GROUP &C1PRGRP.
FOOTPRINT 'C1UDSN'
.
NODBMS
OTHER
2. If you are using any of the following databases, edit the appropriate member in the CA
Endevor® SCM source library:
04-May-2018 594/1109
CA Endevor® SCM - 17.0
Important! To ensure the integrity of the information provided on the installation tape,
make a copy of the members to be modified. Make all changes to the copied members,
and refer to those members in the JCL. Do not change the original members supplied on
the installation tape.
To change the type or processor group names to meet your requirements, rewrite the ESTABLISH
statement. Use the global change function to ensure that all appropriate ESTABLISH statements are
modified.
In the following example, the type has been changed to CBL and the processor group to BCHLNK:
ESTABLISH TYPE CBL PROCESSOR GROUP BCHLNK
WHEN PRIMARY TRANSLATOR = "CBL-TRAN"
AND LINKAGE EDITOR = "8" .
Important! Modify only the type and processor group names in the ESTABLISH statement.
Do not change any other syntax. ESTABLISH statements are part of a complete set of logic
rules supplied with the Inventory Analyzer and, with the exception of types and processor
groups, should not be changed.
04-May-2018 595/1109
CA Endevor® SCM - 17.0
The Inventory Analyzer produces several reports, during and as a result of the analysis procedure.
These reports provide detailed information about specific portions of the analysis and summary
information for the entire procedure.
You should review these reports carefully, as they can clarify what transpired throughout the analysis
procedure and present concisely the results of the exercise.
Note: The three rule-based reports are not included in this section.
Report Options
Using the SET REPORT LEVEL statement in your ANALYZE requests, you indicate which reports you
want to view. The following report options are available:
Summary
Parameter Syntax, Request Syntax, Output Mwilodel Definition Syntax, Final Request
Interpretation, Analysis Summary Report, Load Module Summary Report, Execution Summary
Report.
Detail
Default report level. If you do not indicate a specific report level in the ANALYZE request, you
receive all the summary reports and the Request Processing Report.
All
All the reports provided by the DETAIL option and the Rule Syntax, Rule Analysis, and Final Rule
Interpretation reports.
Important! Do not use the All option unless you are working with Technical Support and
they instruct you to run this particular set of reports.
04-May-2018 596/1109
CA Endevor® SCM - 17.0
Note: For more information about required changes, see How to Customize the Output
Model Definition (see page 588).
A result of TRUE indicates that the member matched the type and processor group specified. A
single TRUE means that there is a unique type and processor group for the member.
A result of FALSE indicates that there is no match between the member and the type and
processor group combination.
A result of UNRESOLVED indicates that the analysis for this rule could not be performed. For
example, there may be conflicting attributes, such as when the same type has two different
processor groups and both rules prove TRUE.
In this and similar situations, review the rules. One of the attributes in the rule may be unclear. Or, all
attributes may be correct but the rule references another rule that does not exist. You can further
clarify the information needed to classify a member by editing the SCL manually.
Note: For more information about editing the SCL manually, see Customizing the Inventory
Analyzer (see page 588).
04-May-2018 597/1109
CA Endevor® SCM - 17.0
Note: A result of UNRESOLVED does not necessarily mean there is a problem. The rule
simply may not apply to the particular request, in which case it is ignored.
The attributes listed for each member are associated with the processor group indicated. Processors
need to be created accordingly, with link-edit parameters that should match those indicated on the
report. By reviewing the report, you can determine whether there are any inconsistencies within the
same processor group. If you find inconsistencies, you may need to create one or more new
processor groups to accommodate the different types of load modules within that particular group.
The first section of the report indicates the number of members that matched each type and
processor group combination.
The second section indicates the number of members both successfully processed and
unsuccessfully processed, and the DDname to which each set of members was directed.
The number of members that did not match any type and processor group combination.
The number of members that matched more than one type and processor group combination.
04-May-2018 598/1109
CA Endevor® SCM - 17.0
SOURCE OPTIONAL
04-May-2018 599/1109
CA Endevor® SCM - 17.0
SOURCE OPTIONAL
Indicates to the Inventory Analyzer that the FROM clause may be omitted from an ANALYZE
request. When the FROM clause is omitted, the USING clause must be specified. The analysis
proceeds based entirely on the members found in the USING data sets. Any WHEN clauses (in the
rules) that require source to be scanned are considered FALSE.
DDnames
Each of the five regular input and output data set DDnames can be customized using the PARM=
field. The DDnames defined within the output models, however, cannot be changed using this
field.
This table lists the default DDname and description for each parameter:
Note: You supply the first two DDnames in the parameter. The remaining DDnames are the
default values.
04-May-2018 600/1109
CA Endevor® SCM - 17.0
How the Inventory Analyzer Supports Type and Processor Group Combinations (see page 607)
Types and Processor Groups for NODBMS (see page 608)
Types and Processor Groups for DB2DBMS (see page 626)
Types and Processor Groups for IDMSDBMS (see page 645)
Types and Processor Groups for IMSDBMS (see page 663)
Types and Processor Groups for TOTALDBM (see page 681)
Types and Processor Groups for Non-3GL Type Items (see page 700)
This article lists the types and processor groups that are used within the base rule sets provided on
the CA Endevor® SCM installation tape-library iprfx.iqual.CSIQOPTN, members DB2DBMS, DEFINES,
IDMSDBMS, IMSDBMS, NODBMS, OTHERS, or TOTALDBM. The types and processor groups available
should meet all your requirements. Members not classified by the supplied rule set should be
classified manually, by customizing individual LOAD statements.
Use the following naming convention lists as a guideline. Although the list is extensive, it is not
complete. The information provided, however, should help you create the names.
The following section contains valid values for all categories (except the last one).
04-May-2018 601/1109
CA Endevor® SCM - 17.0
04-May-2018 602/1109
CA Endevor® SCM - 17.0
Processor Names
Processor names consist of eight characters. The following table contains the categories for processor
names.
The following section contains valid values for all categories (except the last one).
04-May-2018 603/1109
CA Endevor® SCM - 17.0
04-May-2018 604/1109
CA Endevor® SCM - 17.0
Note: For more information about symbolics, see How Symbolics Work (see page 589).
NODE1
User-defined System
NODE2
Stage ID
NODE3
MCF
NODE4
Index Data
Source Libraries
04-May-2018 605/1109
CA Endevor® SCM - 17.0
Source Libraries
NODE1
User-defined System
NODE2
Stage
NODE3
Base Delta System
NODE4
Base Delta
Output Libraries
NODE1
User-defined System
NODE2
Stage
NODE3
System Subsystem
NODE4
COPYLIB LOADLIB JCLLIB MACLIB OBJLIB PROCLIB SRCLIB
ASSM
NETRON
BASIC
PL/I
C
PROCS
CLISTS
RPG
COBOL
REPORTS
COPYBOOK
SORTCNTL
EASYTREV
SPECS
FORTRAN
TABLES
04-May-2018 606/1109
CA Endevor® SCM - 17.0
JCL
TELON
LINKCARD
TRNSFORM
MACROS
UTILITY
MARKV
CICS AMODE24 or 31
DB2 REUS
TOTAL RENT
IDMS EXEC
IMS ALIAS
04-May-2018 607/1109
CA Endevor® SCM - 17.0
The following items are also supported: KOM, EZTRIEVE, RPG, PROCS, JCL, MACROS, CA Endevor®
SCM Processor, IMS DBD, or PSB.
If your company has components that are not shown in these tables, classify these components
manually by preparing LOAD requests as input directly into the Load Utility.
ASFNBL00 LINKEDITED MODULE
ASFNBL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASFNBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASFNBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFNBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASFNBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASFNBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFNBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASFNBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFNBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASFNBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASFNBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFNBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASFNBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASFNBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFNBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASFNBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFNBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFNBL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASFNBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASFNBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFNBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASFNBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASFNBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFNBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASFNBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFNBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASFNBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASFNBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFNBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASFNBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASFNBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFNBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASFNBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFNBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFNCL00 LINKEDITED MODULE
ASFNCL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASFNCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
04-May-2018 608/1109
CA Endevor® SCM - 17.0
ASFNCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASFNCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFNCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASFNCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASFNCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFNCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASFNCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFNCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASFNCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASFNCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFNCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASFNCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASFNCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFNCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASFNCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFNCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFNCL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASFNCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASFNCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFNCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASFNCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASFNCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFNCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASFNCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFNCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASFNCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASFNCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFNCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASFNCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASFNCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFNCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASFNCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFNCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHNBL00 LINKEDITED MODULE
ASHNBL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASHNBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASHNBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHNBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASHNBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASHNBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHNBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASHNBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHNBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASHNBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASHNBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHNBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASHNBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASHNBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHNBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASHNBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHNBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHNBL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASHNBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASHNBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHNBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASHNBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASHNBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHNBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASHNBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHNBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASHNBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASHNBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHNBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASHNBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASHNBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHNBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASHNBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHNBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHNCL00 LINKEDITED MODULE
ASHNCL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASHNCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASHNCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 609/1109
CA Endevor® SCM - 17.0
ASHNCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHNCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASHNCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASHNCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHNCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASHNCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHNCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASHNCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASHNCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHNCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASHNCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASHNCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHNCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASHNCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHNCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHNCL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASHNCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASHNCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHNCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASHNCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASHNCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHNCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASHNCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHNCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASHNCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASHNCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHNCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASHNCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASHNCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHNCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASHNCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHNCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFNBOD7 OBJECT MODULE.
ASFNBOD8 CAOPT,OBJECT MODULE.
ASFNCOD7 OBJECT MODULE.
ASFNCOD8 CAOPT,OBJECT MODULE.
ASHNBOD7 OBJECT MODULE.
ASHNBOD8 CAOPT,OBJECT MODULE.
ASHNCOD7 OBJECT MODULE.
ASHNCOD8 CAOPT,OBJECT MODULE.
**************************************************************
**************************************************************
COBOL
COBNBL00 LINKEDITED MODULE
COBNBL01 EXEC,RENT,REUS,ALIAS,AMODE24
COBNBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
COBNBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBNBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBNBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBNBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBNBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBNBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBNBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBNBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBNBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBNBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBNBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBNBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBNBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBNBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBNBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBNBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBNBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
04-May-2018 610/1109
CA Endevor® SCM - 17.0
COBNBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBNBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBNBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNBL35 EXEC,RENT,REUS,ALIAS,AMODE31
COBNBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
COBNBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBNBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBNBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBNBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBNBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBNBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBNBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBNBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBNBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBNBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBNBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBNBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBNBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBNBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBNBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBNBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBNBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBNBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBNBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNCL00 LINKEDITED MODULE
COBNCL01 EXEC,RENT,REUS,ALIAS,AMODE24
COBNCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
COBNCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBNCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBNCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBNCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBNCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBNCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBNCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBNCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBNCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBNCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBNCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBNCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBNCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBNCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBNCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBNCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBNCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
04-May-2018 611/1109
CA Endevor® SCM - 17.0
COBNCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBNCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBNCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNCL35 EXEC,RENT,REUS,ALIAS,AMODE31
COBNCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
COBNCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBNCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBNCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBNCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBNCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBNCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBNCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBNCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBNCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBNCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBNCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBNCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBNCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBNCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBNCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBNCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBNCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBNCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBNCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIINBL00 LINKEDITED MODULE
CIINBL01 EXEC,RENT,REUS,ALIAS,AMODE24
CIINBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CIINBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIINBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIINBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIINBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIINBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIINBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIINBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIINBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIINBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIINBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIINBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIINBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIINBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIINBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIINBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CIINBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CIINBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIINBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIINBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIINBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIINBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIINBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIINBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIINBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIINBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIINBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIINBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIINBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIINBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 612/1109
CA Endevor® SCM - 17.0
CIINBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIINBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIINBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIINBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIINBL35 EXEC,RENT,REUS,ALIAS,AMODE31
CIINBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CIINBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIINBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIINBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIINBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIINBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIINBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIINBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIINBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIINBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIINBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIINBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIINBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIINBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIINBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIINBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CIINBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CIINBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIINBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIINBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIINBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIINBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIINBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIINBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIINBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIINBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIINBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIINBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIINBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIINBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIINBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIINBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIINBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIINCL00 LINKEDITED MODULE
CIINCL01 EXEC,RENT,REUS,ALIAS,AMODE24
CIINCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CIINCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIINCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIINCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIINCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIINCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIINCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIINCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIINCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIINCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIINCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIINCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIINCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIINCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIINCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIINCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CIINCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CIINCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIINCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIINCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIINCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIINCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIINCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIINCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIINCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIINCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIINCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIINCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIINCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIINCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIINCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIINCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
04-May-2018 613/1109
CA Endevor® SCM - 17.0
CIINCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIINCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIINCL35 EXEC,RENT,REUS,ALIAS,AMODE31
CIINCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CIINCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIINCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIINCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIINCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIINCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIINCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIINCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIINCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIINCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIINCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIINCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIINCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIINCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIINCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIINCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CIINCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CIINCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIINCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIINCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIINCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIINCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIINCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIINCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIINCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIINCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIINCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIINCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIINCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIINCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIINCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIINCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIINCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNBOD7 OBJECT MODULE.
COBNBOD8 CAOPT,OBJECT MODULE.
CIINBOD7 OBJECT MODULE.
CIINBOD8 CAOPT,OBJECT MODULE.
COBNCOD7 OBJECT MODULE.
COBNCOD8 CAOPT,OBJECT MODULE.
CIINCOD7 OBJECT MODULE.
CIINCOD8 CAOPT,OBJECT MODULE.
**********************************************************
**********************************************************
PL1
PL1NBL00 LINKEDITED MODULE
PL1NBL01 EXEC,RENT,REUS,ALIAS,AMODE24
PL1NBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
PL1NBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1NBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1NBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1NBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1NBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1NBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1NBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1NBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1NBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1NBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1NBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
04-May-2018 614/1109
CA Endevor® SCM - 17.0
PL1NBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1NBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1NBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1NBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1NBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NBL35 EXEC,RENT,REUS,ALIAS,AMODE31
PL1NBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
PL1NBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1NBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1NBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1NBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1NBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1NBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1NBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1NBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1NBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1NBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1NBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1NBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1NBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1NBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1NBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1NBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1NBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1NBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1NBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NCL00 LINKEDITED MODULE
PL1NCL01 EXEC,RENT,REUS,ALIAS,AMODE24
PL1NCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
PL1NCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1NCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1NCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1NCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1NCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1NCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1NCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1NCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1NCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1NCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1NCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1NCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1NCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 615/1109
CA Endevor® SCM - 17.0
PL1NCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1NCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1NCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NCL35 EXEC,RENT,REUS,ALIAS,AMODE31
PL1NCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
PL1NCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1NCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1NCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1NCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1NCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1NCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1NCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1NCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1NCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1NCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1NCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1NCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1NCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1NCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1NCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1NCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1NCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1NCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1NCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NBOD7 OBJECT MODULE.
PL1NBOD8 CAOPT,OBJECT MODULE.
PL1NCOD7 OBJECT MODULE.
PL1NCOD8 CAOPT,OBJECT MODULE.
******************************************************
******************************************************
C
CLTNBL00 LINKEDITED MODULE
CLTNBL01 EXEC,RENT,REUS,ALIAS,AMODE24
CLTNBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CLTNBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTNBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTNBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTNBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTNBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTNBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTNBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTNBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTNBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTNBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTNBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTNBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTNBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTNBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTNBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLTNBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLTNBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
04-May-2018 616/1109
CA Endevor® SCM - 17.0
CLTNBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTNBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTNBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTNBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTNBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTNBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTNBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTNBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTNBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTNBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTNBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTNBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTNBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTNBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTNBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTNBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTNBL35 EXEC,RENT,REUS,ALIAS,AMODE31
CLTNBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CLTNBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTNBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTNBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTNBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTNBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTNBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTNBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTNBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTNBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTNBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTNBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTNBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTNBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTNBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTNBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLTNBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLTNBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTNBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTNBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTNBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTNBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTNBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTNBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTNBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTNBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTNBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTNBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTNBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTNBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTNBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTNBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTNBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTNCL00 LINKEDITED MODULE
CLTNCL01 EXEC,RENT,REUS,ALIAS,AMODE24
CLTNCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CLTNCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTNCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTNCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTNCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTNCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTNCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTNCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTNCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTNCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTNCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTNCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTNCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTNCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTNCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTNCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLTNCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLTNCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTNCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTNCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 617/1109
CA Endevor® SCM - 17.0
CLTNCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTNCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTNCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTNCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTNCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTNCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTNCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTNCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTNCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTNCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTNCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTNCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTNCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTNCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTNCL35 EXEC,RENT,REUS,ALIAS,AMODE31
CLTNCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CLTNCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTNCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTNCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTNCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTNCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTNCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTNCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTNCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTNCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTNCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTNCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTNCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTNCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTNCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTNCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLTNCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLTNCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTNCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTNCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTNCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTNCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTNCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTNCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTNCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTNCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTNCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTNCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTNCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTNCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTNCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTNCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTNCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSNBL00 LINKEDITED MODULE
CSSNBL01 EXEC,RENT,REUS,ALIAS,AMODE24
CSSNBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CSSNBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSNBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSNBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSNBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSNBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSNBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSNBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSNBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSNBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSNBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSNBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSNBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSNBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSNBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSNBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSSNBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSSNBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSNBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSNBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSNBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSNBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
04-May-2018 618/1109
CA Endevor® SCM - 17.0
CSSNBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSNBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSNBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSNBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSNBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSNBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSNBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSNBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSNBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSNBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSNBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSNBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSNBL35 EXEC,RENT,REUS,ALIAS,AMODE31
CSSNBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CSSNBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSNBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSNBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSNBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSNBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSNBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSNBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSNBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSNBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSNBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSNBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSNBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSNBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSNBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSNBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSSNBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSSNBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSNBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSNBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSNBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSNBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSNBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSNBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSNBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSNBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSNBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSNBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSNBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSNBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSNBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSNBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSNBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSNCL00 LINKEDITED MODULE
CSSNCL01 EXEC,RENT,REUS,ALIAS,AMODE24
CSSNCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CSSNCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSNCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSNCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSNCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSNCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSNCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSNCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSNCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSNCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSNCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSNCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSNCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSNCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSNCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSNCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSSNCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSSNCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSNCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSNCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSNCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSNCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSNCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSNCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 619/1109
CA Endevor® SCM - 17.0
CSSNCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSNCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSNCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSNCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSNCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSNCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSNCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSNCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSNCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSNCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSNCL35 EXEC,RENT,REUS,ALIAS,AMODE31
CSSNCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CSSNCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSNCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSNCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSNCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSNCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSNCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSNCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSNCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSNCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSNCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSNCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSNCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSNCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSNCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSNCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSSNCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSSNCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSNCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSNCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSNCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSNCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSNCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSNCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSNCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSNCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSNCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSNCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSNCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSNCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSNCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSNCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSNCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTNBOD7 OBJECT MODULE.
CLTNBOD8 CAOPT,OBJECT MODULE.
CLTNCOD7 OBJECT MODULE.
CLTNCOD8 CAOPT,OBJECT MODULE.
CSSNBOD7 OBJECT MODULE.
CSSNBOD8 CAOPT,OBJECT MODULE.
CSSNCOD7 OBJECT MODULE.
CSSNCOD8 CAOPT,OBJECT MODULE.
**************************************************************
**************************************************************
FORTRAN
FORNBL00 LINKEDITED MODULE
FORNBL01 EXEC,RENT,REUS,ALIAS,AMODE24
FORNBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
FORNBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORNBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORNBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORNBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORNBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORNBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORNBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORNBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORNBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORNBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORNBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORNBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORNBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
04-May-2018 620/1109
CA Endevor® SCM - 17.0
FORNBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORNBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORNBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FORNBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FORNBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORNBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORNBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORNBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORNBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORNBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORNBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORNBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORNBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORNBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORNBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORNBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORNBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORNBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORNBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORNBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORNBL35 EXEC,RENT,REUS,ALIAS,AMODE31
FORNBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
FORNBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORNBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORNBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORNBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORNBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORNBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORNBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORNBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORNBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORNBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORNBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORNBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORNBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORNBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORNBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FORNBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FORNBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORNBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORNBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORNBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORNBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORNBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORNBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORNBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORNBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORNBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORNBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORNBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORNBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORNBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORNBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORNBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORNCL00 LINKEDITED MODULE
FORNCL01 EXEC,RENT,REUS,ALIAS,AMODE24
FORNCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
FORNCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORNCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORNCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORNCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORNCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORNCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORNCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORNCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORNCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORNCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORNCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORNCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORNCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORNCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORNCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
04-May-2018 621/1109
CA Endevor® SCM - 17.0
FORNCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FORNCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FORNCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORNCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORNCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORNCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORNCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORNCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORNCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORNCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORNCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORNCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORNCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORNCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORNCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORNCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORNCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORNCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORNCL35 EXEC,RENT,REUS,ALIAS,AMODE31
FORNCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
FORNCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORNCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORNCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORNCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORNCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORNCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORNCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORNCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORNCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORNCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORNCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORNCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORNCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORNCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORNCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FORNCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FORNCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORNCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORNCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORNCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORNCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORNCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORNCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORNCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORNCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORNCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORNCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORNCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORNCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORNCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORNCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORNCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORNBOD7 OBJECT MODULE.
FORNBOD8 CAOPT,OBJECT MODULE.
FORNCOD7 OBJECT MODULE.
FORNCOD8 CAOPT,OBJECT MODULE.
**************************************************************
**************************************************************
TELON
COBNBL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COBNBL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COBNBL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBNBL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBNBL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNBL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNBL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBNBL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBNBL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBNBL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBNBL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNBL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
04-May-2018 622/1109
CA Endevor® SCM - 17.0
COBNBL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNBL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBNBL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBNBL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNBL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNBL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBNBL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBNBL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBNBL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBNBL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNBL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNBL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBNBL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBNBL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBNBL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBNBL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNBL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNBL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBNBL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBNBL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNBLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNBLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNBLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNBLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COBNBLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COBNBLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBNBLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBNBLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNBLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNBLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBNBLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBNBLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBNBLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBNBLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNBLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNBLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBNBLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBNBLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNBLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNBLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBNBLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBNBLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBNBLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBNBLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNBLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNBLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBNBLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBNBLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBNBLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBNBLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNBLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNBLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBNBLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBNBLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNBLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNBLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNBLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNCL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COBNCL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COBNCL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBNCL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBNCL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNCL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNCL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBNCL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBNCL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBNCL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBNCL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNCL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNCL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBNCL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBNCL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
04-May-2018 623/1109
CA Endevor® SCM - 17.0
COBNCL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNCL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNCL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBNCL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBNCL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBNCL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBNCL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNCL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNCL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBNCL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBNCL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBNCL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBNCL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNCL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNCL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBNCL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBNCL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNCLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBNCLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNCLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBNCLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COBNCLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COBNCLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBNCLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBNCLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNCLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNCLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBNCLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBNCLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBNCLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBNCLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNCLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNCLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBNCLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBNCLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNCLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNCLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBNCLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBNCLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBNCLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBNCLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNCLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNCLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBNCLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBNCLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBNCLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBNCLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNCLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNCLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBNCLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBNCLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNCLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBNCLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNCLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NBL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL1NBL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL1NBL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1NBL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1NBL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1NBL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1NBL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NBL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NBL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1NBL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1NBL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NBL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NBL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1NBL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
04-May-2018 624/1109
CA Endevor® SCM - 17.0
PL1NBL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1NBL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1NBL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1NBL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1NBL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1NBL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1NBL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NBL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NBL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1NBL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1NBL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NBLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NBLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NBLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NBLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL1NBLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL1NBLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1NBLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1NBLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NBLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NBLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1NBLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1NBLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1NBLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1NBLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NBLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NBLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1NBLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1NBLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NBLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NBLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1NBLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1NBLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1NBLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1NBLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NBLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NBLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1NBLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1NBLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1NBLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1NBLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NBLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NBLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1NBLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1NBLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NBLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NBLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NBLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NCL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL1NCL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL1NCL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1NCL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1NCL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1NCL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1NCL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NCL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NCL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1NCL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1NCL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NCL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NCL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1NCL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1NCL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1NCL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1NCL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 625/1109
CA Endevor® SCM - 17.0
PL1NCL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1NCL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1NCL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1NCL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NCL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NCL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1NCL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1NCL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NCLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1NCLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NCLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1NCLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL1NCLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL1NCLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1NCLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1NCLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NCLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NCLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1NCLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1NCLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1NCLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1NCLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NCLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NCLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1NCLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1NCLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NCLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NCLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1NCLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1NCLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1NCLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1NCLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NCLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NCLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1NCLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1NCLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1NCLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1NCLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NCLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NCLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1NCLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1NCLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NCLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1NCLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1NCLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBNBOD9 TELON, OBJECT MODULE.
COBNBOE0 CAOPT,TELON,OBJECT MODULE.
CIINBOD9 TELON, OBJECT MODULE.
CIINBOE0 CAOPT,TELON,OBJECT MODULE.
PL1NBOD9 TELON, OBJECT MODULE.
PL1NBOE0 CAOPT,TELON,OBJECT MODULE.
COBNCOD9 TELON, OBJECT MODULE.
COBNCOE0 CAOPT,TELON,OBJECT MODULE.
CIINCOD9 TELON, OBJECT MODULE.
CIINCOE0 CAOPT,TELON,OBJECT MODULE.
PL1NCOD9 TELON, OBJECT MODULE.
PL1NCOE0 CAOPT,TELON,OBJECT MODULE.
ASF2BL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASF2BL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASF2BL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASF2BL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
04-May-2018 626/1109
CA Endevor® SCM - 17.0
ASF2BL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASF2BL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASF2BL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASF2BL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASF2BL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASF2BL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASF2BL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASF2BL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASF2BL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASF2BL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASF2BL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASF2BL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASF2BL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASF2BL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASF2BL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASF2BL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASF2BL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASF2BL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASF2BL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASF2BL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASF2BL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASF2BL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASF2BL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASF2BL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASF2BL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASF2BL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASF2BL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASF2BL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASF2BL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASF2BL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASF2BL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASF2CL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASF2CL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASF2CL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASF2CL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASF2CL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASF2CL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASF2CL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASF2CL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASF2CL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASF2CL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASF2CL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASF2CL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASF2CL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASF2CL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASF2CL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASF2CL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASF2CL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASF2CL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASF2CL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASF2CL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASF2CL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASF2CL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASF2CL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASF2CL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASF2CL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASF2CL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASF2CL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASF2CL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASF2CL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASF2CL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASF2CL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASF2CL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASF2CL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASF2CL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASH2BL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASH2BL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASH2BL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASH2BL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASH2BL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASH2BL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASH2BL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
04-May-2018 627/1109
CA Endevor® SCM - 17.0
ASH2BL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASH2BL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASH2BL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASH2BL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASH2BL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASH2BL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASH2BL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASH2BL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASH2BL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASH2BL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASH2BL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASH2BL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASH2BL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASH2BL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASH2BL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASH2BL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASH2BL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASH2BL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASH2BL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASH2BL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASH2BL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASH2BL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASH2BL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASH2BL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASH2BL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASH2BL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASH2BL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASH2BL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASH2CL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASH2CL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASH2CL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASH2CL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASH2CL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASH2CL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASH2CL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASH2CL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASH2CL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASH2CL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASH2CL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASH2CL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASH2CL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASH2CL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASH2CL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASH2CL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASH2CL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASH2CL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASH2CL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASH2CL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASH2CL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASH2CL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASH2CL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASH2CL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASH2CL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASH2CL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASH2CL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASH2CL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASH2CL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASH2CL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASH2CL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASH2CL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASH2CL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASH2CL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASF2BOD7 OBJECT MODULE.
ASF2BOD8 CAOPT,OBJECT MODULE.
ASF2COD7 OBJECT MODULE.
ASF2COD8 CAOPT,OBJECT MODULE.
ASH2BOD7 OBJECT MODULE.
ASH2BOD8 CAOPT,OBJECT MODULE.
ASH2COD7 OBJECT MODULE.
ASH2COD8 CAOPT,OBJECT MODULE.
**************************************************************
**************************************************************
04-May-2018 628/1109
CA Endevor® SCM - 17.0
**************************************************************
COBOL
COB2BL01 EXEC,RENT,REUS,ALIAS,AMODE24
COB2BL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
COB2BL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COB2BL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COB2BL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2BL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2BL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COB2BL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COB2BL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COB2BL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COB2BL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2BL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2BL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COB2BL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COB2BL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2BL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2BL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COB2BL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COB2BL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COB2BL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COB2BL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2BL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2BL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COB2BL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COB2BL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COB2BL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COB2BL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2BL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2BL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COB2BL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COB2BL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2BL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2BL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2BL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2BL35 EXEC,RENT,REUS,ALIAS,AMODE31
COB2BL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
COB2BL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COB2BL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COB2BL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2BL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2BL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COB2BL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COB2BL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COB2BL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COB2BL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2BL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2BL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COB2BL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COB2BL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2BL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2BL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COB2BL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COB2BL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COB2BL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COB2BL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2BL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2BL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COB2BL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COB2BL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COB2BL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COB2BL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2BL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2BL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COB2BL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COB2BL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2BL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2BL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2BL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2CL01 EXEC,RENT,REUS,ALIAS,AMODE24
04-May-2018 629/1109
CA Endevor® SCM - 17.0
COB2CL01 EXEC,RENT,REUS,ALIAS,AMODE24
COB2CL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
COB2CL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COB2CL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COB2CL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2CL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2CL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COB2CL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COB2CL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COB2CL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COB2CL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2CL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2CL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COB2CL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COB2CL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2CL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2CL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COB2CL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COB2CL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COB2CL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COB2CL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2CL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2CL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COB2CL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COB2CL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COB2CL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COB2CL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2CL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2CL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COB2CL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COB2CL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2CL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2CL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2CL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2CL35 EXEC,RENT,REUS,ALIAS,AMODE31
COB2CL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
COB2CL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COB2CL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COB2CL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2CL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2CL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COB2CL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COB2CL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COB2CL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COB2CL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2CL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2CL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COB2CL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COB2CL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2CL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2CL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COB2CL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COB2CL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COB2CL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COB2CL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2CL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2CL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COB2CL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COB2CL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COB2CL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COB2CL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2CL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2CL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COB2CL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COB2CL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2CL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2CL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2CL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CII2BL01 EXEC,RENT,REUS,ALIAS,AMODE24
CII2BL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CII2BL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CII2BL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
04-May-2018 630/1109
CA Endevor® SCM - 17.0
CII2BL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CII2BL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CII2BL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CII2BL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CII2BL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CII2BL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CII2BL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CII2BL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CII2BL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CII2BL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CII2BL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CII2BL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CII2BL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CII2BL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CII2BL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CII2BL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CII2BL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CII2BL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CII2BL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CII2BL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CII2BL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CII2BL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CII2BL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CII2BL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CII2BL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CII2BL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CII2BL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CII2BL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CII2BL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CII2BL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CII2BL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CII2BL35 EXEC,RENT,REUS,ALIAS,AMODE31
CII2BL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CII2BL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CII2BL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CII2BL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CII2BL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CII2BL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CII2BL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CII2BL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CII2BL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CII2BL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CII2BL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CII2BL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CII2BL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CII2BL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CII2BL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CII2BL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CII2BL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CII2BL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CII2BL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CII2BL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CII2BL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CII2BL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CII2BL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CII2BL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CII2BL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CII2BL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CII2BL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CII2BL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CII2BL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CII2BL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CII2BL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CII2BL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CII2BL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CII2CL01 EXEC,RENT,REUS,ALIAS,AMODE24
CII2CL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CII2CL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CII2CL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CII2CL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CII2CL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CII2CL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
04-May-2018 631/1109
CA Endevor® SCM - 17.0
CII2CL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CII2CL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CII2CL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CII2CL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CII2CL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CII2CL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CII2CL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CII2CL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CII2CL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CII2CL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CII2CL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CII2CL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CII2CL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CII2CL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CII2CL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CII2CL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CII2CL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CII2CL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CII2CL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CII2CL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CII2CL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CII2CL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CII2CL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CII2CL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CII2CL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CII2CL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CII2CL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CII2CL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CII2CL35 EXEC,RENT,REUS,ALIAS,AMODE31
CII2CL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CII2CL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CII2CL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CII2CL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CII2CL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CII2CL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CII2CL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CII2CL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CII2CL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CII2CL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CII2CL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CII2CL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CII2CL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CII2CL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CII2CL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CII2CL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CII2CL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CII2CL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CII2CL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CII2CL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CII2CL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CII2CL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CII2CL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CII2CL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CII2CL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CII2CL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CII2CL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CII2CL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CII2CL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CII2CL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CII2CL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CII2CL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CII2CL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2BOD7 OBJECT MODULE.
COB2BOD8 CAOPT,OBJECT MODULE.
CII2BOD7 OBJECT MODULE.
CII2BOD8 CAOPT,OBJECT MODULE.
COB2COD7 OBJECT MODULE.
COB2COD8 CAOPT,OBJECT MODULE.
CII2COD7 OBJECT MODULE.
CII2COD8 CAOPT,OBJECT MODULE.
**********************************************************
**********************************************************
04-May-2018 632/1109
CA Endevor® SCM - 17.0
**********************************************************
PL1
PL12BL01 EXEC,RENT,REUS,ALIAS,AMODE24
PL12BL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
PL12BL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL12BL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL12BL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12BL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12BL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL12BL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL12BL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL12BL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL12BL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12BL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12BL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL12BL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL12BL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12BL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12BL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL12BL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL12BL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL12BL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL12BL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12BL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12BL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL12BL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL12BL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL12BL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL12BL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12BL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12BL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL12BL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL12BL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12BL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12BL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12BL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12BL35 EXEC,RENT,REUS,ALIAS,AMODE31
PL12BL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
PL12BL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL12BL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL12BL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12BL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12BL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL12BL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL12BL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL12BL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL12BL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12BL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12BL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL12BL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL12BL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12BL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12BL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL12BL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL12BL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL12BL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL12BL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12BL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12BL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL12BL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL12BL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL12BL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL12BL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12BL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12BL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL12BL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL12BL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12BL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12BL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12BL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12CL01 EXEC,RENT,REUS,ALIAS,AMODE24
04-May-2018 633/1109
CA Endevor® SCM - 17.0
PL12CL01 EXEC,RENT,REUS,ALIAS,AMODE24
PL12CL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
PL12CL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL12CL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL12CL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12CL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12CL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL12CL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL12CL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL12CL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL12CL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12CL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12CL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL12CL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL12CL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12CL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12CL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL12CL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL12CL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL12CL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL12CL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12CL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12CL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL12CL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL12CL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL12CL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL12CL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12CL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12CL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL12CL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL12CL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12CL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12CL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12CL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12CL35 EXEC,RENT,REUS,ALIAS,AMODE31
PL12CL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
PL12CL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL12CL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL12CL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12CL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12CL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL12CL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL12CL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL12CL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL12CL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12CL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12CL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL12CL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL12CL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12CL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12CL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL12CL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL12CL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL12CL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL12CL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12CL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12CL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL12CL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL12CL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL12CL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL12CL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12CL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12CL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL12CL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL12CL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12CL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12CL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12CL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12BOD7 OBJECT MODULE.
PL12BOD8 CAOPT,OBJECT MODULE.
PL12COD7 OBJECT MODULE.
PL12COD8 CAOPT,OBJECT MODULE.
04-May-2018 634/1109
CA Endevor® SCM - 17.0
PL12COD8 CAOPT,OBJECT MODULE.
******************************************************
******************************************************
C
CLT2BL01 EXEC,RENT,REUS,ALIAS,AMODE24
CLT2BL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CLT2BL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLT2BL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLT2BL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLT2BL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLT2BL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLT2BL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLT2BL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLT2BL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLT2BL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLT2BL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLT2BL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLT2BL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLT2BL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLT2BL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLT2BL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLT2BL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLT2BL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLT2BL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLT2BL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLT2BL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLT2BL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLT2BL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLT2BL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLT2BL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLT2BL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLT2BL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLT2BL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLT2BL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLT2BL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLT2BL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLT2BL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLT2BL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLT2BL35 EXEC,RENT,REUS,ALIAS,AMODE31
CLT2BL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CLT2BL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLT2BL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLT2BL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLT2BL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLT2BL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLT2BL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLT2BL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLT2BL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLT2BL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLT2BL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLT2BL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLT2BL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLT2BL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLT2BL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLT2BL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLT2BL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLT2BL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLT2BL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLT2BL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLT2BL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLT2BL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLT2BL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLT2BL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLT2BL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLT2BL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLT2BL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLT2BL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLT2BL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLT2BL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLT2BL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLT2BL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
04-May-2018 635/1109
CA Endevor® SCM - 17.0
CLT2BL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLT2BL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLT2CL01 EXEC,RENT,REUS,ALIAS,AMODE24
CLT2CL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CLT2CL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLT2CL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLT2CL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLT2CL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLT2CL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLT2CL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLT2CL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLT2CL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLT2CL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLT2CL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLT2CL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLT2CL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLT2CL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLT2CL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLT2CL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLT2CL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLT2CL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLT2CL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLT2CL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLT2CL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLT2CL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLT2CL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLT2CL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLT2CL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLT2CL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLT2CL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLT2CL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLT2CL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLT2CL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLT2CL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLT2CL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLT2CL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLT2CL35 EXEC,RENT,REUS,ALIAS,AMODE31
CLT2CL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CLT2CL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLT2CL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLT2CL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLT2CL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLT2CL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLT2CL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLT2CL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLT2CL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLT2CL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLT2CL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLT2CL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLT2CL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLT2CL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLT2CL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLT2CL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLT2CL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLT2CL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLT2CL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLT2CL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLT2CL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLT2CL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLT2CL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLT2CL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLT2CL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLT2CL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLT2CL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLT2CL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLT2CL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLT2CL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLT2CL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLT2CL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLT2CL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSS2BL01 EXEC,RENT,REUS,ALIAS,AMODE24
CSS2BL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
04-May-2018 636/1109
CA Endevor® SCM - 17.0
CSS2BL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CSS2BL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSS2BL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSS2BL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSS2BL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSS2BL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSS2BL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSS2BL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSS2BL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSS2BL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSS2BL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSS2BL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSS2BL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSS2BL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSS2BL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSS2BL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSS2BL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSS2BL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSS2BL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSS2BL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSS2BL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSS2BL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSS2BL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSS2BL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSS2BL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSS2BL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSS2BL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSS2BL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSS2BL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSS2BL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSS2BL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSS2BL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSS2BL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSS2BL35 EXEC,RENT,REUS,ALIAS,AMODE31
CSS2BL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CSS2BL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSS2BL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSS2BL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSS2BL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSS2BL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSS2BL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSS2BL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSS2BL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSS2BL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSS2BL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSS2BL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSS2BL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSS2BL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSS2BL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSS2BL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSS2BL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSS2BL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSS2BL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSS2BL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSS2BL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSS2BL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSS2BL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSS2BL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSS2BL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSS2BL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSS2BL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSS2BL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSS2BL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSS2BL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSS2BL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSS2BL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSS2BL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSS2CL01 EXEC,RENT,REUS,ALIAS,AMODE24
CSS2CL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CSS2CL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSS2CL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSS2CL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 637/1109
CA Endevor® SCM - 17.0
CSS2CL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSS2CL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSS2CL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSS2CL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSS2CL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSS2CL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSS2CL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSS2CL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSS2CL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSS2CL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSS2CL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSS2CL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSS2CL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSS2CL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSS2CL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSS2CL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSS2CL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSS2CL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSS2CL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSS2CL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSS2CL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSS2CL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSS2CL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSS2CL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSS2CL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSS2CL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSS2CL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSS2CL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSS2CL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSS2CL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSS2CL35 EXEC,RENT,REUS,ALIAS,AMODE31
CSS2CL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CSS2CL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSS2CL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSS2CL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSS2CL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSS2CL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSS2CL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSS2CL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSS2CL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSS2CL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSS2CL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSS2CL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSS2CL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSS2CL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSS2CL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSS2CL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSS2CL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSS2CL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSS2CL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSS2CL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSS2CL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSS2CL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSS2CL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSS2CL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSS2CL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSS2CL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSS2CL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSS2CL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSS2CL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSS2CL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSS2CL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSS2CL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSS2CL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLT2BOD7 OBJECT MODULE.
CLT2BOD8 CAOPT,OBJECT MODULE.
CLT2COD7 OBJECT MODULE.
CLT2COD8 CAOPT,OBJECT MODULE.
CSS2BOD7 OBJECT MODULE.
CSS2BOD8 CAOPT,OBJECT MODULE.
CSS2COD7 OBJECT MODULE.
CSS2COD8 CAOPT,OBJECT MODULE.
04-May-2018 638/1109
CA Endevor® SCM - 17.0
CSS2COD8 CAOPT,OBJECT MODULE.
**************************************************************
**************************************************************
FORTRAN
FOR2BL01 EXEC,RENT,REUS,ALIAS,AMODE24
FOR2BL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
FOR2BL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FOR2BL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FOR2BL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FOR2BL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FOR2BL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FOR2BL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FOR2BL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FOR2BL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FOR2BL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FOR2BL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FOR2BL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FOR2BL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FOR2BL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FOR2BL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FOR2BL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FOR2BL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FOR2BL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FOR2BL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FOR2BL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FOR2BL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FOR2BL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FOR2BL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FOR2BL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FOR2BL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FOR2BL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FOR2BL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FOR2BL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FOR2BL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FOR2BL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FOR2BL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FOR2BL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FOR2BL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FOR2BL35 EXEC,RENT,REUS,ALIAS,AMODE31
FOR2BL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
FOR2BL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FOR2BL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FOR2BL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FOR2BL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FOR2BL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FOR2BL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FOR2BL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FOR2BL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FOR2BL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FOR2BL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FOR2BL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FOR2BL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FOR2BL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FOR2BL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FOR2BL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FOR2BL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FOR2BL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FOR2BL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FOR2BL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FOR2BL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FOR2BL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FOR2BL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FOR2BL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FOR2BL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FOR2BL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FOR2BL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FOR2BL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FOR2BL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FOR2BL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FOR2BL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FOR2BL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
04-May-2018 639/1109
CA Endevor® SCM - 17.0
FOR2BL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FOR2BL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FOR2CL01 EXEC,RENT,REUS,ALIAS,AMODE24
FOR2CL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
FOR2CL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FOR2CL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FOR2CL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FOR2CL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FOR2CL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FOR2CL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FOR2CL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FOR2CL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FOR2CL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FOR2CL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FOR2CL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FOR2CL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FOR2CL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FOR2CL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FOR2CL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FOR2CL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FOR2CL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FOR2CL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FOR2CL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FOR2CL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FOR2CL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FOR2CL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FOR2CL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FOR2CL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FOR2CL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FOR2CL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FOR2CL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FOR2CL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FOR2CL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FOR2CL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FOR2CL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FOR2CL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FOR2CL35 EXEC,RENT,REUS,ALIAS,AMODE31
FOR2CL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
FOR2CL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FOR2CL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FOR2CL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FOR2CL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FOR2CL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FOR2CL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FOR2CL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FOR2CL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FOR2CL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FOR2CL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FOR2CL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FOR2CL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FOR2CL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FOR2CL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FOR2CL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FOR2CL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FOR2CL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FOR2CL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FOR2CL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FOR2CL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FOR2CL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FOR2CL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FOR2CL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FOR2CL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FOR2CL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FOR2CL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FOR2CL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FOR2CL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FOR2CL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FOR2CL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FOR2CL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FOR2CL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FOR2BOD7 OBJECT MODULE.
FOR2BOD8 CAOPT,OBJECT MODULE.
04-May-2018 640/1109
CA Endevor® SCM - 17.0
FOR2BOD8 CAOPT,OBJECT MODULE.
FOR2COD7 OBJECT MODULE.
FOR2COD8 CAOPT,OBJECT MODULE.
**************************************************************
**************************************************************
TELON
COB2BL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COB2BL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COB2BL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COB2BL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COB2BL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2BL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2BL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COB2BL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COB2BL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COB2BL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COB2BL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2BL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2BL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COB2BL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COB2BL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2BL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2BL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COB2BL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COB2BL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COB2BL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COB2BL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2BL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2BL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COB2BL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COB2BL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COB2BL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COB2BL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2BL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2BL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COB2BL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COB2BL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2BLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2BLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2BLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2BLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COB2BLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COB2BLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COB2BLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COB2BLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2BLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2BLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COB2BLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COB2BLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COB2BLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COB2BLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2BLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2BLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COB2BLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COB2BLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2BLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2BLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COB2BLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COB2BLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COB2BLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COB2BLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2BLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2BLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COB2BLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COB2BLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COB2BLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COB2BLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2BLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2BLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COB2BLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COB2BLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
04-May-2018 641/1109
CA Endevor® SCM - 17.0
COB2BLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2BLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2BLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2BLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2CL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COB2CL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COB2CL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COB2CL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COB2CL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2CL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2CL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COB2CL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COB2CL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COB2CL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COB2CL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2CL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2CL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COB2CL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COB2CL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2CL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2CL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COB2CL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COB2CL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COB2CL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COB2CL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2CL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2CL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COB2CL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COB2CL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COB2CL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COB2CL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2CL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2CL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COB2CL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COB2CL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2CLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COB2CLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2CLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COB2CLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COB2CLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COB2CLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COB2CLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COB2CLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2CLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2CLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COB2CLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COB2CLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COB2CLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COB2CLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2CLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2CLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COB2CLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COB2CLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2CLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2CLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COB2CLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COB2CLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COB2CLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COB2CLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2CLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2CLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COB2CLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COB2CLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COB2CLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COB2CLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2CLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2CLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COB2CLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COB2CLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2CLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COB2CLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2CLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
04-May-2018 642/1109
CA Endevor® SCM - 17.0
COB2CLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12BL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL12BL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL12BL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL12BL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL12BL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12BL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12BL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL12BL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL12BL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL12BL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL12BL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12BL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12BL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL12BL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL12BL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12BL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12BL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL12BL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL12BL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL12BL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL12BL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12BL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12BL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL12BL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL12BL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL12BL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL12BL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12BL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12BL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL12BL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL12BL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12BLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12BLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12BLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12BLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL12BLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL12BLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL12BLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL12BLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12BLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12BLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL12BLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL12BLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL12BLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL12BLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12BLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12BLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL12BLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL12BLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12BLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12BLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL12BLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL12BLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL12BLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL12BLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12BLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12BLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL12BLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL12BLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL12BLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL12BLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12BLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12BLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL12BLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL12BLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12BLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12BLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12BLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12CL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL12CL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL12CL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
04-May-2018 643/1109
CA Endevor® SCM - 17.0
PL12CL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL12CL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL12CL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12CL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12CL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL12CL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL12CL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL12CL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL12CL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12CL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12CL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL12CL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL12CL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12CL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12CL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL12CL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL12CL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL12CL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL12CL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12CL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12CL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL12CL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL12CL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL12CL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL12CL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12CL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12CL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL12CL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL12CL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12CLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL12CLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12CLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL12CLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL12CLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL12CLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL12CLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL12CLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12CLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12CLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL12CLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL12CLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL12CLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL12CLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12CLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12CLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL12CLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL12CLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12CLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12CLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL12CLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL12CLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL12CLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL12CLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12CLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12CLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL12CLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL12CLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL12CLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL12CLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12CLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12CLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL12CLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL12CLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12CLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL12CLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL12CLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COB2BOD9 TELON, OBJECT MODULE.
COB2BOE0 CAOPT,TELON,OBJECT MODULE.
CII2BOD9 TELON, OBJECT MODULE.
CII2BOE0 CAOPT,TELON,OBJECT MODULE.
PL12BOD9 TELON, OBJECT MODULE.
PL12BOE0 CAOPT,TELON,OBJECT MODULE.
04-May-2018 644/1109
CA Endevor® SCM - 17.0
PL12BOE0 CAOPT,TELON,OBJECT MODULE.
COB2COD9 TELON, OBJECT MODULE.
COB2COE0 CAOPT,TELON,OBJECT MODULE.
CII2COD9 TELON, OBJECT MODULE.
CII2COE0 CAOPT,TELON,OBJECT MODULE.
PL12COD9 TELON, OBJECT MODULE.
PL12COE0 CAOPT,TELON,OBJECT MODULE.
**********************************************************************
ASFDCL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASFDCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASFDCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFDCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASFDCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASFDCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFDCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASFDCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFDCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASFDCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASFDCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFDCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASFDCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASFDCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFDCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASFDCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFDCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFDCL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASFDCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASFDCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFDCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASFDCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
04-May-2018 645/1109
CA Endevor® SCM - 17.0
ASFDCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASFDCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFDCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASFDCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFDCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASFDCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASFDCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFDCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASFDCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASFDCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFDCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASFDCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFDCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHDBL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASHDBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASHDBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHDBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASHDBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASHDBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHDBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASHDBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHDBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASHDBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASHDBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHDBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASHDBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASHDBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHDBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASHDBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHDBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHDBL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASHDBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASHDBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHDBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASHDBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASHDBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHDBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASHDBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHDBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASHDBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASHDBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHDBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASHDBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASHDBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHDBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASHDBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHDBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHDCL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASHDCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASHDCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHDCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASHDCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASHDCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHDCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASHDCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHDCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASHDCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASHDCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHDCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASHDCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASHDCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHDCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASHDCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHDCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHDCL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASHDCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASHDCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHDCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASHDCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASHDCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHDCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASHDCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
04-May-2018 646/1109
CA Endevor® SCM - 17.0
ASHDCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHDCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASHDCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASHDCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHDCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASHDCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASHDCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHDCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASHDCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHDCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFDBOD7 OBJECT MODULE.
ASFDBOD8 CAOPT,OBJECT MODULE.
ASFDCOD7 OBJECT MODULE.
ASFDCOD8 CAOPT,OBJECT MODULE.
ASHDBOD7 OBJECT MODULE.
ASHDBOD8 CAOPT,OBJECT MODULE.
ASHDCOD7 OBJECT MODULE.
ASHDCOD8 CAOPT,OBJECT MODULE.
**************************************************************
**************************************************************
COBOL
COBDBL01 EXEC,RENT,REUS,ALIAS,AMODE24
COBDBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
COBDBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBDBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBDBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBDBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBDBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBDBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBDBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBDBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBDBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBDBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBDBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBDBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBDBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBDBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBDBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBDBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBDBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBDBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBDBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDBL35 EXEC,RENT,REUS,ALIAS,AMODE31
COBDBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
COBDBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBDBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBDBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBDBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBDBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBDBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBDBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBDBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBDBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
04-May-2018 647/1109
CA Endevor® SCM - 17.0
COBDBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBDBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBDBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBDBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBDBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBDBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBDBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBDBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBDBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBDBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBDBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDCL01 EXEC,RENT,REUS,ALIAS,AMODE24
COBDCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
COBDCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBDCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBDCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBDCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBDCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBDCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBDCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBDCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBDCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBDCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBDCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBDCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBDCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBDCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBDCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBDCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBDCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBDCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBDCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDCL35 EXEC,RENT,REUS,ALIAS,AMODE31
COBDCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
COBDCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBDCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBDCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBDCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBDCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBDCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBDCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBDCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBDCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBDCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBDCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
04-May-2018 648/1109
CA Endevor® SCM - 17.0
COBDCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBDCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBDCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBDCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBDCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBDCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBDCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBDCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBDCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIDBL01 EXEC,RENT,REUS,ALIAS,AMODE24
CIIDBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CIIDBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIIDBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIIDBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIDBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIDBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIIDBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIIDBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIIDBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIIDBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIDBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIDBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIIDBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIIDBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIDBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIDBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CIIDBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CIIDBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIIDBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIIDBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIDBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIDBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIIDBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIIDBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIIDBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIIDBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIDBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIDBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIIDBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIIDBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIDBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIDBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIDBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIDBL35 EXEC,RENT,REUS,ALIAS,AMODE31
CIIDBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CIIDBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIIDBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIIDBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIDBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIDBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIIDBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIIDBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIIDBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIIDBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIDBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIDBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIIDBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIIDBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIDBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIDBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CIIDBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CIIDBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIIDBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIIDBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIDBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
04-May-2018 649/1109
CA Endevor® SCM - 17.0
CIIDBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIDBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIIDBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIIDBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIIDBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIIDBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIDBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIDBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIIDBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIIDBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIDBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIDBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIDBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIDCL01 EXEC,RENT,REUS,ALIAS,AMODE24
CIIDCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CIIDCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIIDCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIIDCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIDCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIDCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIIDCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIIDCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIIDCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIIDCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIDCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIDCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIIDCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIIDCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIDCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIDCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CIIDCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CIIDCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIIDCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIIDCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIDCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIDCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIIDCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIIDCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIIDCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIIDCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIDCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIDCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIIDCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIIDCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIDCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIDCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIDCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIDCL35 EXEC,RENT,REUS,ALIAS,AMODE31
CIIDCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CIIDCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIIDCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIIDCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIDCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIDCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIIDCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIIDCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIIDCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIIDCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIDCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIDCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIIDCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIIDCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIDCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIDCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CIIDCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CIIDCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIIDCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIIDCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIDCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIDCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIIDCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIIDCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
04-May-2018 650/1109
CA Endevor® SCM - 17.0
CIIDCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIIDCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIIDCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIDCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIDCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIIDCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIIDCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIDCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIDCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIDCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDBOD7 OBJECT MODULE.
COBDBOD8 CAOPT,OBJECT MODULE.
CIIDBOD7 OBJECT MODULE.
CIIDBOD8 CAOPT,OBJECT MODULE.
COBDCOD7 OBJECT MODULE.
COBDCOD8 CAOPT,OBJECT MODULE.
CIIDCOD7 OBJECT MODULE.
CIIDCOD8 CAOPT,OBJECT MODULE.
**********************************************************
**********************************************************
PL1
PL1DBL01 EXEC,RENT,REUS,ALIAS,AMODE24
PL1DBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
PL1DBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1DBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1DBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1DBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1DBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1DBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1DBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1DBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1DBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1DBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1DBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1DBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1DBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1DBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1DBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DBL35 EXEC,RENT,REUS,ALIAS,AMODE31
PL1DBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
PL1DBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1DBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1DBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1DBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1DBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1DBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1DBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1DBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1DBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
04-May-2018 651/1109
CA Endevor® SCM - 17.0
PL1DBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1DBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1DBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1DBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1DBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1DBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1DBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1DBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1DBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1DBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1DBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DCL01 EXEC,RENT,REUS,ALIAS,AMODE24
PL1DCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
PL1DCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1DCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1DCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1DCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1DCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1DCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1DCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1DCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1DCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1DCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1DCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1DCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1DCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1DCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1DCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DCL35 EXEC,RENT,REUS,ALIAS,AMODE31
PL1DCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
PL1DCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1DCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1DCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1DCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1DCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1DCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1DCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1DCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1DCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1DCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1DCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
04-May-2018 652/1109
CA Endevor® SCM - 17.0
PL1DCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1DCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1DCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1DCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1DCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1DCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1DCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1DCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1DCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DBOD7 OBJECT MODULE.
PL1DBOD8 CAOPT,OBJECT MODULE.
PL1DCOD7 OBJECT MODULE.
PL1DCOD8 CAOPT,OBJECT MODULE.
******************************************************
******************************************************
C
CLTDBL01 EXEC,RENT,REUS,ALIAS,AMODE24
CLTDBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CLTDBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTDBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTDBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTDBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTDBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTDBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTDBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTDBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTDBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTDBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTDBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTDBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTDBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTDBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTDBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLTDBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLTDBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTDBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTDBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTDBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTDBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTDBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTDBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTDBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTDBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTDBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTDBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTDBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTDBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTDBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTDBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTDBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTDBL35 EXEC,RENT,REUS,ALIAS,AMODE31
CLTDBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CLTDBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTDBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTDBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTDBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTDBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTDBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTDBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTDBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTDBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTDBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTDBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTDBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
04-May-2018 653/1109
CA Endevor® SCM - 17.0
CLTDBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTDBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTDBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTDBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLTDBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLTDBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTDBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTDBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTDBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTDBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTDBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTDBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTDBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTDBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTDBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTDBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTDBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTDBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTDBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTDBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTDBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTDCL01 EXEC,RENT,REUS,ALIAS,AMODE24
CLTDCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CLTDCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTDCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTDCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTDCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTDCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTDCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTDCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTDCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTDCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTDCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTDCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTDCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTDCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTDCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTDCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLTDCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLTDCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTDCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTDCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTDCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTDCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTDCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTDCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTDCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTDCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTDCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTDCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTDCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTDCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTDCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTDCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTDCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTDCL35 EXEC,RENT,REUS,ALIAS,AMODE31
CLTDCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CLTDCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTDCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTDCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTDCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTDCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTDCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTDCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTDCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTDCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTDCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTDCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTDCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTDCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTDCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTDCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
04-May-2018 654/1109
CA Endevor® SCM - 17.0
CLTDCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLTDCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLTDCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTDCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTDCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTDCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTDCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTDCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTDCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTDCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTDCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTDCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTDCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTDCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTDCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTDCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTDCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTDCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSDBL01 EXEC,RENT,REUS,ALIAS,AMODE24
CSSDBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CSSDBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSDBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSDBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSDBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSDBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSDBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSDBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSDBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSDBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSDBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSDBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSDBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSDBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSDBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSDBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSSDBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSSDBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSDBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSDBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSDBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSDBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSDBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSDBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSDBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSDBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSDBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSDBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSDBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSDBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSDBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSDBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSDBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSDBL35 EXEC,RENT,REUS,ALIAS,AMODE31
CSSDBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CSSDBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSDBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSDBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSDBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSDBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSDBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSDBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSDBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSDBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSDBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSDBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSDBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSDBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSDBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSDBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSSDBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSSDBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSDBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
04-May-2018 655/1109
CA Endevor® SCM - 17.0
CSSDBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSDBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSDBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSDBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSDBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSDBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSDBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSDBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSDBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSDBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSDBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSDBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSDBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSDBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSDBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSDCL01 EXEC,RENT,REUS,ALIAS,AMODE24
CSSDCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CSSDCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSDCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSDCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSDCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSDCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSDCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSDCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSDCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSDCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSDCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSDCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSDCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSDCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSDCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSDCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSSDCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSSDCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSDCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSDCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSDCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSDCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSDCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSDCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSDCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSDCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSDCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSDCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSDCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSDCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSDCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSDCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSDCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSDCL35 EXEC,RENT,REUS,ALIAS,AMODE31
CSSDCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CSSDCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSDCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSDCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSDCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSDCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSDCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSDCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSDCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSDCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSDCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSDCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSDCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSDCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSDCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSDCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSSDCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSSDCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSDCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSDCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSDCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSDCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
04-May-2018 656/1109
CA Endevor® SCM - 17.0
CSSDCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSDCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSDCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSDCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSDCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSDCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSDCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSDCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSDCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSDCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSDCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSDCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTDBOD7 OBJECT MODULE.
CLTDBOD8 CAOPT,OBJECT MODULE.
CLTDCOD7 OBJECT MODULE.
CLTDCOD8 CAOPT,OBJECT MODULE.
CSSDBOD7 OBJECT MODULE.
CSSDBOD8 CAOPT,OBJECT MODULE.
CSSDCOD7 OBJECT MODULE.
CSSDCOD8 CAOPT,OBJECT MODULE.
**************************************************************
**************************************************************
FORTRAN
FORDBL01 EXEC,RENT,REUS,ALIAS,AMODE24
FORDBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
FORDBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORDBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORDBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORDBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORDBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORDBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORDBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORDBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORDBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORDBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORDBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORDBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORDBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORDBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORDBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FORDBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FORDBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORDBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORDBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORDBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORDBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORDBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORDBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORDBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORDBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORDBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORDBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORDBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORDBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORDBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORDBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORDBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORDBL35 EXEC,RENT,REUS,ALIAS,AMODE31
FORDBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
FORDBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORDBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORDBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORDBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORDBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORDBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORDBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORDBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORDBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORDBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORDBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORDBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
04-May-2018 657/1109
CA Endevor® SCM - 17.0
FORDBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORDBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORDBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORDBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FORDBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FORDBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORDBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORDBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORDBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORDBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORDBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORDBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORDBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORDBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORDBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORDBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORDBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORDBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORDBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORDBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORDBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORDCL01 EXEC,RENT,REUS,ALIAS,AMODE24
FORDCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
FORDCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORDCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORDCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORDCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORDCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORDCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORDCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORDCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORDCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORDCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORDCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORDCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORDCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORDCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORDCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FORDCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FORDCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORDCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORDCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORDCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORDCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORDCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORDCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORDCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORDCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORDCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORDCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORDCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORDCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORDCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORDCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORDCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORDCL35 EXEC,RENT,REUS,ALIAS,AMODE31
FORDCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
FORDCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORDCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORDCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORDCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORDCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORDCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORDCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORDCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORDCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORDCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORDCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORDCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORDCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORDCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORDCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
04-May-2018 658/1109
CA Endevor® SCM - 17.0
FORDCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FORDCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FORDCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORDCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORDCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORDCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORDCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORDCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORDCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORDCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORDCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORDCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORDCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORDCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORDCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORDCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORDCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORDCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORDBOD7 OBJECT MODULE.
FORDBOD8 CAOPT,OBJECT MODULE.
FORDCOD7 OBJECT MODULE.
FORDCOD8 CAOPT,OBJECT MODULE.
**************************************************************
**************************************************************
TELON
COBDBL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COBDBL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COBDBL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBDBL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBDBL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDBL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDBL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBDBL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBDBL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBDBL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBDBL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDBL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDBL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBDBL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBDBL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDBL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDBL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBDBL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBDBL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBDBL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBDBL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDBL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDBL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBDBL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBDBL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBDBL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBDBL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDBL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDBL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBDBL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBDBL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDBLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDBLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDBLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDBLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COBDBLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COBDBLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBDBLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBDBLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDBLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDBLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBDBLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBDBLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBDBLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBDBLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDBLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
04-May-2018 659/1109
CA Endevor® SCM - 17.0
COBDBLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDBLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBDBLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBDBLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDBLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDBLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBDBLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBDBLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBDBLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBDBLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDBLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDBLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBDBLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBDBLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBDBLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBDBLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDBLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDBLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBDBLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBDBLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDBLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDBLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDBLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDCL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COBDCL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COBDCL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBDCL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBDCL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDCL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDCL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBDCL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBDCL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBDCL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBDCL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDCL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDCL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBDCL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBDCL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDCL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDCL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBDCL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBDCL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBDCL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBDCL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDCL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDCL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBDCL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBDCL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBDCL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBDCL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDCL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDCL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBDCL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBDCL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDCLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBDCLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDCLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBDCLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COBDCLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COBDCLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBDCLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBDCLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDCLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDCLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBDCLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBDCLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBDCLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBDCLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDCLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDCLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBDCLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBDCLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
04-May-2018 660/1109
CA Endevor® SCM - 17.0
COBDCLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDCLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDCLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBDCLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBDCLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBDCLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBDCLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDCLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDCLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBDCLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBDCLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBDCLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBDCLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDCLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDCLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBDCLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBDCLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDCLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBDCLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDCLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DBL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL1DBL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL1DBL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1DBL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1DBL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1DBL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1DBL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DBL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DBL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1DBL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1DBL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DBL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DBL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1DBL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1DBL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1DBL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1DBL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1DBL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1DBL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1DBL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DBL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DBL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1DBL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1DBL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DBLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DBLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DBLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DBLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL1DBLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL1DBLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1DBLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1DBLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DBLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DBLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1DBLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1DBLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1DBLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1DBLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DBLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DBLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1DBLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1DBLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DBLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DBLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1DBLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
04-May-2018 661/1109
CA Endevor® SCM - 17.0
PL1DBLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1DBLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1DBLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1DBLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DBLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DBLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1DBLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1DBLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1DBLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1DBLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DBLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DBLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1DBLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1DBLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DBLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DBLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DBLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DCL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL1DCL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL1DCL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1DCL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1DCL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1DCL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1DCL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DCL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DCL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1DCL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1DCL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DCL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DCL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1DCL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1DCL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1DCL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1DCL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1DCL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1DCL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1DCL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DCL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DCL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1DCL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1DCL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DCLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1DCLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DCLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1DCLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL1DCLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL1DCLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1DCLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1DCLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DCLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DCLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1DCLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1DCLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1DCLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1DCLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DCLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DCLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1DCLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1DCLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DCLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DCLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1DCLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1DCLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1DCLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1DCLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
04-May-2018 662/1109
CA Endevor® SCM - 17.0
PL1DCLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DCLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DCLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1DCLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1DCLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1DCLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1DCLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DCLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DCLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1DCLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1DCLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DCLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1DCLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1DCLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBDBOD9 TELON, OBJECT MODULE.
COBDBOE0 CAOPT,TELON,OBJECT MODULE.
CIIDBOD9 TELON, OBJECT MODULE.
CIIDBOE0 CAOPT,TELON,OBJECT MODULE.
PL1DBOD9 TELON, OBJECT MODULE.
PL1DBOE0 CAOPT,TELON,OBJECT MODULE.
COBDCOD9 TELON, OBJECT MODULE.
COBDCOE0 CAOPT,TELON,OBJECT MODULE.
CIIDCOD9 TELON, OBJECT MODULE.
CIIDCOE0 CAOPT,TELON,OBJECT MODULE.
PL1DCOD9 TELON, OBJECT MODULE.
PL1DCOE0 CAOPT,TELON,OBJECT MODULE.
**********************************************************************
ASFIBL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASFIBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASFIBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFIBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASFIBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASFIBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFIBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASFIBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFIBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASFIBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASFIBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFIBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASFIBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASFIBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFIBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASFIBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFIBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFIBL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASFIBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASFIBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFIBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASFIBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASFIBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFIBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASFIBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFIBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASFIBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASFIBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFIBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASFIBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASFIBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFIBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASFIBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFIBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFICL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASFICL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASFICL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 663/1109
CA Endevor® SCM - 17.0
ASFICL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFICL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASFICL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASFICL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFICL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASFICL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFICL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASFICL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASFICL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFICL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASFICL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASFICL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFICL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASFICL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFICL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFICL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASFICL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASFICL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFICL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASFICL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASFICL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFICL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASFICL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFICL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASFICL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASFICL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFICL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASFICL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASFICL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFICL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASFICL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFICL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHIBL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASHIBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASHIBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHIBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASHIBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASHIBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHIBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASHIBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHIBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASHIBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASHIBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHIBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASHIBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASHIBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHIBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASHIBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHIBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHIBL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASHIBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASHIBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHIBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASHIBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASHIBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHIBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASHIBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHIBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASHIBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASHIBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHIBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASHIBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASHIBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHIBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASHIBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHIBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHICL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASHICL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASHICL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHICL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASHICL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASHICL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
04-May-2018 664/1109
CA Endevor® SCM - 17.0
ASHICL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHICL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASHICL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHICL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASHICL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASHICL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHICL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASHICL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASHICL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHICL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASHICL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHICL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHICL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASHICL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASHICL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHICL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASHICL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASHICL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHICL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASHICL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHICL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASHICL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASHICL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHICL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASHICL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASHICL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHICL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASHICL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHICL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFIBOD7 OBJECT MODULE.
ASFIBOD8 CAOPT,OBJECT MODULE.
ASFICOD7 OBJECT MODULE.
ASFICOD8 CAOPT,OBJECT MODULE.
ASHIBOD7 OBJECT MODULE.
ASHIBOD8 CAOPT,OBJECT MODULE.
ASHICOD7 OBJECT MODULE.
ASHICOD8 CAOPT,OBJECT MODULE.
**************************************************************
**************************************************************
COBOL
COBIBL01 EXEC,RENT,REUS,ALIAS,AMODE24
COBIBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
COBIBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBIBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBIBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBIBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBIBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBIBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBIBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBIBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBIBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBIBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBIBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBIBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBIBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBIBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBIBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBIBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBIBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBIBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBIBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBIBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBIBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBIBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBIBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBIBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBIBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBIBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBIBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBIBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBIBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 665/1109
CA Endevor® SCM - 17.0
COBIBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBIBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBIBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBIBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBIBL35 EXEC,RENT,REUS,ALIAS,AMODE31
COBIBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
COBIBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBIBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBIBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBIBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBIBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBIBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBIBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBIBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBIBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBIBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBIBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBIBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBIBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBIBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBIBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBIBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBIBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBIBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBIBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBIBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBIBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBIBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBIBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBIBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBIBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBIBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBIBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBIBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBIBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBIBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBIBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBIBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICL01 EXEC,RENT,REUS,ALIAS,AMODE24
COBICL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
COBICL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBICL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBICL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBICL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBICL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBICL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBICL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBICL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBICL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBICL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBICL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBICL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBICL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBICL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBICL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBICL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBICL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBICL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBICL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBICL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBICL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBICL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBICL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBICL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBICL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBICL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBICL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBICL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBICL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBICL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 666/1109
CA Endevor® SCM - 17.0
COBICL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBICL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBICL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBICL35 EXEC,RENT,REUS,ALIAS,AMODE31
COBICL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
COBICL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBICL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBICL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBICL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBICL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBICL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBICL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBICL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBICL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBICL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBICL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBICL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBICL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBICL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBICL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBICL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBICL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBICL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBICL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBICL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBICL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBICL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBICL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBICL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIIBL01 EXEC,RENT,REUS,ALIAS,AMODE24
CIIIBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CIIIBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIIIBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIIIBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIIBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIIBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIIIBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIIIBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIIIBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIIIBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIIBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIIBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIIIBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIIIBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIIBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIIBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CIIIBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CIIIBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIIIBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIIIBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIIBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIIBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIIIBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIIIBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIIIBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIIIBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIIBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIIBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIIIBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIIIBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIIBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIIBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIIBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIIBL35 EXEC,RENT,REUS,ALIAS,AMODE31
CIIIBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CIIIBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
04-May-2018 667/1109
CA Endevor® SCM - 17.0
CIIIBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIIIBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIIIBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIIBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIIBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIIIBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIIIBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIIIBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIIIBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIIBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIIBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIIIBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIIIBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIIBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIIBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CIIIBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CIIIBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIIIBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIIIBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIIBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIIBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIIIBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIIIBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIIIBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIIIBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIIBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIIBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIIIBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIIIBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIIBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIIBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIIBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIICL01 EXEC,RENT,REUS,ALIAS,AMODE24
CIIICL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CIIICL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIIICL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIIICL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIICL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIICL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIIICL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIIICL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIIICL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIIICL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIICL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIICL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIIICL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIIICL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIICL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIICL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CIIICL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CIIICL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIIICL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIIICL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIICL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIICL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIIICL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIIICL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIIICL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIIICL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIICL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIICL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIIICL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIIICL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIICL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIIICL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIICL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIIICL35 EXEC,RENT,REUS,ALIAS,AMODE31
CIIICL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CIIICL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIIICL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIIICL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIICL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
04-May-2018 668/1109
CA Endevor® SCM - 17.0
CIIICL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIICL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIIICL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIIICL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIIICL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIIICL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIICL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIICL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIIICL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIIICL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIICL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIICL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CIIICL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CIIICL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIIICL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIIICL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIICL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIICL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIIICL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIIICL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIIICL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIIICL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIICL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIICL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIIICL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIIICL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIICL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIIICL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIIICL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBIBOD7 OBJECT MODULE.
COBIBOD8 CAOPT,OBJECT MODULE.
CIIIBOD7 OBJECT MODULE.
CIIIBOD8 CAOPT,OBJECT MODULE.
COBICOD7 OBJECT MODULE.
COBICOD8 CAOPT,OBJECT MODULE.
CIIICOD7 OBJECT MODULE.
CIIICOD8 CAOPT,OBJECT MODULE.
**********************************************************
**********************************************************
PL1
PL1IBL01 EXEC,RENT,REUS,ALIAS,AMODE24
PL1IBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
PL1IBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1IBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1IBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1IBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1IBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1IBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1IBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1IBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1IBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1IBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1IBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1IBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1IBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1IBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1IBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1IBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1IBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1IBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1IBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1IBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1IBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 669/1109
CA Endevor® SCM - 17.0
PL1IBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1IBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1IBL35 EXEC,RENT,REUS,ALIAS,AMODE31
PL1IBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
PL1IBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1IBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1IBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1IBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1IBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1IBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1IBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1IBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1IBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1IBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1IBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1IBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1IBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1IBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1IBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1IBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1IBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1IBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1IBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1IBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1IBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1IBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1IBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1IBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1IBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1IBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1IBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1IBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1IBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1IBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1IBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1IBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1ICL01 EXEC,RENT,REUS,ALIAS,AMODE24
PL1ICL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
PL1ICL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1ICL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1ICL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1ICL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1ICL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1ICL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1ICL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1ICL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1ICL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1ICL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1ICL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1ICL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1ICL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1ICL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1ICL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1ICL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1ICL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1ICL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1ICL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1ICL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1ICL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1ICL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
04-May-2018 670/1109
CA Endevor® SCM - 17.0
PL1ICL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1ICL35 EXEC,RENT,REUS,ALIAS,AMODE31
PL1ICL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
PL1ICL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1ICL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1ICL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1ICL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1ICL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1ICL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1ICL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1ICL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1ICL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1ICL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1ICL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1ICL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1ICL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1ICL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1ICL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1ICL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1ICL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1ICL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1ICL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1ICL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1ICL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1ICL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1ICL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1ICL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1ICL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1ICL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1ICL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1ICL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1ICL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1ICL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1ICL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1ICL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1IBOD7 OBJECT MODULE.
PL1IBOD8 CAOPT,OBJECT MODULE.
PL1ICOD7 OBJECT MODULE.
PL1ICOD8 CAOPT,OBJECT MODULE.
******************************************************
******************************************************
C
CLTIBL01 EXEC,RENT,REUS,ALIAS,AMODE24
CLTIBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CLTIBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTIBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTIBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTIBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTIBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTIBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTIBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTIBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTIBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTIBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTIBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTIBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTIBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTIBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTIBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLTIBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLTIBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTIBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTIBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTIBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTIBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTIBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTIBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTIBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTIBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTIBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTIBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
04-May-2018 671/1109
CA Endevor® SCM - 17.0
CLTIBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTIBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTIBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTIBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTIBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTIBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTIBL35 EXEC,RENT,REUS,ALIAS,AMODE31
CLTIBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CLTIBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTIBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTIBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTIBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTIBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTIBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTIBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTIBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTIBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTIBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTIBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTIBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTIBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTIBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTIBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLTIBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLTIBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTIBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTIBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTIBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTIBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTIBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTIBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTIBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTIBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTIBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTIBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTIBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTIBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTIBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTIBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTIBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTICL01 EXEC,RENT,REUS,ALIAS,AMODE24
CLTICL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CLTICL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTICL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTICL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTICL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTICL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTICL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTICL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTICL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTICL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTICL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTICL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTICL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTICL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTICL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTICL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLTICL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLTICL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTICL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTICL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTICL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTICL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTICL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTICL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTICL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTICL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTICL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTICL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTICL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTICL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTICL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 672/1109
CA Endevor® SCM - 17.0
CLTICL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTICL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTICL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTICL35 EXEC,RENT,REUS,ALIAS,AMODE31
CLTICL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CLTICL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTICL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTICL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTICL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTICL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTICL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTICL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTICL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTICL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTICL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTICL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTICL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTICL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTICL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTICL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLTICL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLTICL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTICL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTICL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTICL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTICL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTICL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTICL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTICL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTICL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTICL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTICL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTICL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTICL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTICL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTICL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTICL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSIBL01 EXEC,RENT,REUS,ALIAS,AMODE24
CSSIBL01 EXEC,RENT,REUS,ALIAS,AMODE24
CSSIBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CSSIBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSIBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSIBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSIBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSIBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSIBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSIBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSIBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSIBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSIBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSIBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSIBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSIBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSIBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSIBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSSIBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSSIBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSIBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSIBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSIBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSIBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSIBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSIBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSIBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSIBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSIBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSIBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSIBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSIBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSIBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSIBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSIBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
04-May-2018 673/1109
CA Endevor® SCM - 17.0
CSSIBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSIBL35 EXEC,RENT,REUS,ALIAS,AMODE31
CSSIBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CSSIBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSIBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSIBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSIBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSIBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSIBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSIBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSIBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSIBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSIBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSIBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSIBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSIBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSIBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSIBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSSIBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSSIBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSIBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSIBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSIBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSIBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSIBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSIBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSIBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSIBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSIBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSIBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSIBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSIBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSIBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSIBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSIBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSICL01 EXEC,RENT,REUS,ALIAS,AMODE24
CSSICL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CSSICL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSICL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSICL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSICL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSICL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSICL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSICL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSICL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSICL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSICL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSICL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSICL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSICL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSICL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSICL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSSICL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSSICL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSICL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSICL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSICL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSICL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSICL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSICL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSICL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSICL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSICL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSICL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSICL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSICL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSICL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSICL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSICL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSICL35 EXEC,RENT,REUS,ALIAS,AMODE31
CSSICL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CSSICL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
04-May-2018 674/1109
CA Endevor® SCM - 17.0
CSSICL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSICL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSICL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSICL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSICL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSICL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSICL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSICL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSICL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSICL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSICL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSICL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSICL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSICL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSICL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSSICL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSSICL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSICL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSICL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSICL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSICL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSICL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSICL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSICL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSICL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSICL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSICL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSICL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSICL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSICL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSICL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSICL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTIBOD7 OBJECT MODULE.
CLTIBOD8 CAOPT,OBJECT MODULE.
CLTICOD7 OBJECT MODULE.
CLTICOD8 CAOPT,OBJECT MODULE.
CSSIBOD7 OBJECT MODULE.
CSSIBOD8 CAOPT,OBJECT MODULE.
CSSICOD7 OBJECT MODULE.
CSSICOD8 CAOPT,OBJECT MODULE.
**************************************************************
**************************************************************
FORTRAN
FORIBL01 EXEC,RENT,REUS,ALIAS,AMODE24
FORIBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
FORIBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORIBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORIBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORIBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORIBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORIBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORIBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORIBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORIBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORIBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORIBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORIBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORIBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORIBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORIBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FORIBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FORIBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORIBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORIBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORIBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORIBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORIBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORIBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORIBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORIBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORIBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
04-May-2018 675/1109
CA Endevor® SCM - 17.0
FORIBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORIBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORIBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORIBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORIBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORIBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORIBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORIBL35 EXEC,RENT,REUS,ALIAS,AMODE31
FORIBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
FORIBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORIBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORIBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORIBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORIBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORIBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORIBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORIBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORIBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORIBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORIBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORIBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORIBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORIBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORIBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FORIBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FORIBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORIBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORIBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORIBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORIBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORIBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORIBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORIBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORIBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORIBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORIBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORIBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORIBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORIBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORIBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORIBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORICL01 EXEC,RENT,REUS,ALIAS,AMODE24
FORICL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
FORICL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORICL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORICL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORICL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORICL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORICL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORICL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORICL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORICL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORICL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORICL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORICL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORICL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORICL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORICL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FORICL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FORICL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORICL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORICL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORICL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORICL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORICL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORICL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORICL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORICL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORICL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORICL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORICL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORICL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 676/1109
CA Endevor® SCM - 17.0
FORICL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORICL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORICL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORICL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORICL35 EXEC,RENT,REUS,ALIAS,AMODE31
FORICL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
FORICL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORICL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORICL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORICL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORICL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORICL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORICL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORICL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORICL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORICL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORICL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORICL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORICL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORICL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORICL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FORICL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FORICL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORICL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORICL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORICL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORICL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORICL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORICL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORICL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORICL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORICL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORICL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORICL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORICL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORICL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORICL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORICL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORIBOD7 OBJECT MODULE.
FORIBOD8 CAOPT,OBJECT MODULE.
FORICOD7 OBJECT MODULE.
FORICOD8 CAOPT,OBJECT MODULE.
**************************************************************
**************************************************************
TELON
COBIBL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COBIBL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COBIBL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBIBL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBIBL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBIBL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBIBL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBIBL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBIBL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBIBL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBIBL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBIBL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBIBL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBIBL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBIBL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBIBL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBIBL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBIBL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBIBL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBIBL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBIBL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBIBL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBIBL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBIBL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBIBL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBIBL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 677/1109
CA Endevor® SCM - 17.0
COBIBL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBIBL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBIBL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBIBL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBIBL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBIBL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBIBLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBIBLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBIBLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBIBLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COBIBLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COBIBLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBIBLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBIBLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBIBLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBIBLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBIBLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBIBLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBIBLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBIBLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBIBLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBIBLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBIBLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBIBLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBIBLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBIBLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBIBLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBIBLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBIBLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBIBLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBIBLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBIBLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBIBLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBIBLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBIBLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBIBLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBIBLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBIBLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBIBLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBIBLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBIBLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBIBLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBIBLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COBICL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COBICL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBICL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBICL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBICL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBICL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBICL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBICL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBICL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBICL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBICL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBICL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBICL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBICL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBICL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBICL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBICL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBICL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBICL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBICL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBICL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBICL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBICL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBICL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBICL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBICL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBICL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBICL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
04-May-2018 678/1109
CA Endevor® SCM - 17.0
COBICL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBICL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBICL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBICLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBICLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBICLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBICLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COBICLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COBICLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBICLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBICLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBICLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBICLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBICLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBICLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBICLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBICLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBICLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBICLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBICLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBICLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBICLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBICLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBICLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBICLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBICLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBICLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBICLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBICLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBICLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBICLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBICLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBICLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBICLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1IBL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL1IBL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL1IBL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1IBL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1IBL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1IBL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1IBL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1IBL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1IBL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1IBL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1IBL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1IBL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1IBL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1IBL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1IBL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1IBL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1IBL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1IBL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1IBL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1IBL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1IBL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1IBL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1IBL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1IBL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1IBLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 679/1109
CA Endevor® SCM - 17.0
PL1IBLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1IBLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1IBLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1IBLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL1IBLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL1IBLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1IBLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1IBLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1IBLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1IBLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1IBLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1IBLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1IBLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1IBLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1IBLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1IBLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1IBLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1IBLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1IBLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1IBLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1IBLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1IBLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1IBLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1IBLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1IBLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1IBLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1IBLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1IBLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1IBLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1IBLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1IBLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1IBLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1IBLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1IBLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1IBLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1IBLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1IBLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1ICL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL1ICL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL1ICL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1ICL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1ICL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1ICL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1ICL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1ICL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1ICL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1ICL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1ICL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1ICL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1ICL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1ICL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1ICL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1ICL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1ICL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1ICL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1ICL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1ICL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1ICL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1ICL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1ICL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1ICL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1ICLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1ICLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1ICLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1ICLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
04-May-2018 680/1109
CA Endevor® SCM - 17.0
PL1ICLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL1ICLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL1ICLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1ICLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1ICLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1ICLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1ICLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1ICLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1ICLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1ICLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1ICLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1ICLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1ICLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1ICLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1ICLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1ICLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1ICLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1ICLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1ICLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1ICLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1ICLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1ICLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1ICLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1ICLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1ICLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1ICLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1ICLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1ICLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1ICLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1ICLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1ICLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1ICLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1ICLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1ICLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBIBOD9 TELON, OBJECT MODULE.
COBIBOE0 CAOPT,TELON,OBJECT MODULE.
CIIIBOD9 TELON, OBJECT MODULE.
CIIIBOE0 CAOPT,TELON,OBJECT MODULE.
PL1IBOD9 TELON, OBJECT MODULE.
PL1IBOE0 CAOPT,TELON,OBJECT MODULE.
COBICOD9 TELON, OBJECT MODULE.
COBICOE0 CAOPT,TELON,OBJECT MODULE.
CIIICOD9 TELON, OBJECT MODULE.
CIIICOE0 CAOPT,TELON,OBJECT MODULE.
PL1ICOD9 TELON, OBJECT MODULE.
PL1ICOE0 CAOPT,TELON,OBJECT MODULE.
ASFTBL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASFTBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASFTBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFTBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASFTBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASFTBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFTBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASFTBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFTBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASFTBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASFTBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFTBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASFTBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASFTBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFTBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASFTBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFTBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFTBL35 EXEC,RENT,REUS,ALIAS,AMODE31
04-May-2018 681/1109
CA Endevor® SCM - 17.0
ASFTBL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASFTBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASFTBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFTBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASFTBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASFTBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFTBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASFTBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFTBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASFTBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASFTBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFTBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASFTBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASFTBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFTBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASFTBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFTBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFTCL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASFTCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASFTCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFTCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASFTCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASFTCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFTCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASFTCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFTCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASFTCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASFTCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFTCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASFTCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASFTCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFTCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASFTCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASFTCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASFTCL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASFTCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASFTCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFTCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASFTCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASFTCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFTCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASFTCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFTCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASFTCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASFTCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFTCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASFTCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASFTCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFTCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASFTCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASFTCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHTBL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASHTBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASHTBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHTBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASHTBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASHTBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHTBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASHTBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHTBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASHTBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASHTBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHTBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASHTBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASHTBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHTBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASHTBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHTBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHTBL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASHTBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASHTBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHTBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
04-May-2018 682/1109
CA Endevor® SCM - 17.0
ASHTBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASHTBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASHTBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHTBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASHTBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHTBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASHTBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASHTBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHTBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASHTBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASHTBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHTBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASHTBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHTBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHTCL01 EXEC,RENT,REUS,ALIAS,AMODE24
ASHTCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASHTCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHTCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASHTCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASHTCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHTCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASHTCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHTCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
ASHTCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
ASHTCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHTCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
ASHTCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
ASHTCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHTCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
ASHTCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
ASHTCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
ASHTCL35 EXEC,RENT,REUS,ALIAS,AMODE31
ASHTCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASHTCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHTCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASHTCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASHTCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHTCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASHTCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHTCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
ASHTCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
ASHTCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHTCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
ASHTCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
ASHTCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASHTCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
ASHTCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
ASHTCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
ASFTBOD7 OBJECT MODULE.
ASFTBOD8 CAOPT,OBJECT MODULE.
ASFTCOD7 OBJECT MODULE.
ASFTCOD8 CAOPT,OBJECT MODULE.
ASHTBOD7 OBJECT MODULE.
ASHTBOD8 CAOPT,OBJECT MODULE.
ASHTCOD7 OBJECT MODULE.
ASHTCOD8 CAOPT,OBJECT MODULE.
**************************************************************
**************************************************************
COBOL
COBTBL01 EXEC,RENT,REUS,ALIAS,AMODE24
COBTBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
COBTBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBTBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBTBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBTBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBTBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBTBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBTBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
04-May-2018 683/1109
CA Endevor® SCM - 17.0
COBTBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBTBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBTBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBTBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBTBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBTBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBTBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBTBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBTBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBTBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBTBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBTBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBTBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTBL35 EXEC,RENT,REUS,ALIAS,AMODE31
COBTBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
COBTBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBTBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBTBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBTBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBTBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBTBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBTBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBTBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBTBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBTBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBTBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBTBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBTBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBTBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBTBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBTBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBTBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBTBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBTBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTCL01 EXEC,RENT,REUS,ALIAS,AMODE24
COBTCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
COBTCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBTCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBTCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBTCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBTCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBTCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBTCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBTCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBTCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
04-May-2018 684/1109
CA Endevor® SCM - 17.0
COBTCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBTCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBTCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBTCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBTCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBTCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBTCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBTCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBTCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBTCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBTCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTCL35 EXEC,RENT,REUS,ALIAS,AMODE31
COBTCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
COBTCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBTCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBTCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBTCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBTCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBTCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBTCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBTCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBTCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBTCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBTCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBTCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBTCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBTCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBTCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBTCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBTCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBTCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBTCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIITBL01 EXEC,RENT,REUS,ALIAS,AMODE24
CIITBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CIITBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIITBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIITBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIITBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIITBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIITBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIITBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIITBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIITBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIITBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIITBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIITBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIITBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIITBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIITBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CIITBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
04-May-2018 685/1109
CA Endevor® SCM - 17.0
CIITBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CIITBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIITBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIITBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIITBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIITBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIITBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIITBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIITBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIITBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIITBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIITBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIITBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIITBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIITBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIITBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIITBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIITBL35 EXEC,RENT,REUS,ALIAS,AMODE31
CIITBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CIITBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIITBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIITBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIITBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIITBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIITBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIITBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIITBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIITBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIITBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIITBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIITBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIITBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIITBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIITBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CIITBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CIITBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIITBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIITBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIITBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIITBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIITBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIITBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIITBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIITBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIITBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIITBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIITBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIITBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIITBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIITBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIITBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIITCL01 EXEC,RENT,REUS,ALIAS,AMODE24
CIITCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CIITCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIITCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIITCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIITCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIITCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIITCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIITCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIITCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIITCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIITCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIITCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIITCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIITCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIITCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIITCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CIITCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CIITCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIITCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CIITCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 686/1109
CA Endevor® SCM - 17.0
CIITCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIITCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIITCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIITCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CIITCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIITCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CIITCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIITCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIITCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIITCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CIITCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIITCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CIITCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIITCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CIITCL35 EXEC,RENT,REUS,ALIAS,AMODE31
CIITCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CIITCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIITCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIITCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIITCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIITCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIITCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIITCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIITCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIITCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIITCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIITCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIITCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIITCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIITCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIITCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CIITCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CIITCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIITCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CIITCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIITCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIITCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIITCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CIITCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIITCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CIITCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIITCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIITCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIITCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CIITCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIITCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CIITCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CIITCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTBOD7 OBJECT MODULE.
COBTBOD8 CAOPT,OBJECT MODULE.
CIITBOD7 OBJECT MODULE.
CIITBOD8 CAOPT,OBJECT MODULE.
COBTCOD7 OBJECT MODULE.
COBTCOD8 CAOPT,OBJECT MODULE.
CIITCOD7 OBJECT MODULE.
CIITCOD8 CAOPT,OBJECT MODULE.
**********************************************************
**********************************************************
PL1
PL1TBL01 EXEC,RENT,REUS,ALIAS,AMODE24
PL1TBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
PL1TBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1TBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1TBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1TBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1TBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
04-May-2018 687/1109
CA Endevor® SCM - 17.0
PL1TBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1TBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1TBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1TBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1TBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1TBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1TBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1TBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1TBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1TBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1TBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TBL35 EXEC,RENT,REUS,ALIAS,AMODE31
PL1TBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
PL1TBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1TBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1TBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1TBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1TBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1TBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1TBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1TBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1TBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1TBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1TBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1TBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1TBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1TBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1TBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1TBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1TBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1TBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1TBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TCL01 EXEC,RENT,REUS,ALIAS,AMODE24
PL1TCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
PL1TCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1TCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1TCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1TCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1TCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1TCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1TCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
04-May-2018 688/1109
CA Endevor® SCM - 17.0
PL1TCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1TCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1TCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1TCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1TCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1TCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1TCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1TCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1TCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TCL35 EXEC,RENT,REUS,ALIAS,AMODE31
PL1TCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
PL1TCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1TCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1TCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1TCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1TCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1TCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1TCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1TCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1TCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1TCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1TCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1TCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1TCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1TCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1TCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1TCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1TCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1TCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1TCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TBOD7 OBJECT MODULE.
PL1TBOD8 CAOPT,OBJECT MODULE.
PL1TCOD7 OBJECT MODULE.
PL1TCOD8 CAOPT,OBJECT MODULE.
******************************************************
******************************************************
C
CLTTBL01 EXEC,RENT,REUS,ALIAS,AMODE24
CLTTBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CLTTBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTTBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTTBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTTBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTTBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTTBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTTBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTTBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 689/1109
CA Endevor® SCM - 17.0
CLTTBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTTBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTTBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTTBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTTBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTTBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTTBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTTBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLTTBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLTTBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTTBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTTBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTTBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTTBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTTBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTTBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTTBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTTBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTTBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTTBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTTBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTTBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTTBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTTBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTTBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTTBL35 EXEC,RENT,REUS,ALIAS,AMODE31
CLTTBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CLTTBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTTBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTTBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTTBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTTBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTTBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTTBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTTBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTTBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTTBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTTBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTTBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTTBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTTBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTTBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLTTBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLTTBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTTBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTTBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTTBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTTBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTTBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTTBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTTBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTTBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTTBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTTBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTTBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTTBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTTBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTTBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTTBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTTCL01 EXEC,RENT,REUS,ALIAS,AMODE24
CLTTCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CLTTCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTTCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTTCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTTCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTTCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTTCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTTCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTTCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTTCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTTCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTTCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
04-May-2018 690/1109
CA Endevor® SCM - 17.0
CLTTCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTTCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTTCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTTCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTTCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLTTCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CLTTCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTTCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CLTTCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTTCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTTCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTTCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CLTTCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTTCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CLTTCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTTCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTTCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTTCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CLTTCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTTCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CLTTCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTTCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CLTTCL35 EXEC,RENT,REUS,ALIAS,AMODE31
CLTTCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CLTTCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTTCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTTCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTTCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTTCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTTCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTTCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTTCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTTCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTTCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTTCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTTCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTTCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTTCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTTCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLTTCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CLTTCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTTCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CLTTCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTTCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTTCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTTCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CLTTCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTTCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CLTTCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTTCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTTCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTTCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CLTTCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTTCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CLTTCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTTCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSTBL01 EXEC,RENT,REUS,ALIAS,AMODE24
CSSTBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CSSTBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSTBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSTBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSTBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSTBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSTBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSTBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSTBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSTBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSTBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSTBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSTBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSTBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSTBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
04-May-2018 691/1109
CA Endevor® SCM - 17.0
CSSTBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSTBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSSTBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSSTBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSTBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSTBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSTBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSTBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSTBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSTBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSTBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSTBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSTBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSTBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSTBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSTBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSTBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSTBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSTBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSTBL35 EXEC,RENT,REUS,ALIAS,AMODE31
CSSTBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CSSTBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSTBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSTBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSTBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSTBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSTBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSTBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSTBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSTBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSTBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSTBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSTBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSTBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSTBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSTBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSSTBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSSTBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSTBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSTBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSTBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSTBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSTBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSTBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSTBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSTBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSTBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSTBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSTBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSTBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSTBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSTBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSTBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSTCL01 EXEC,RENT,REUS,ALIAS,AMODE24
CSSTCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
CSSTCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSTCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSTCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSTCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSTCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSTCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSTCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSTCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSTCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSTCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSTCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSTCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSTCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSTCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSTCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSSTCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
CSSTCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
04-May-2018 692/1109
CA Endevor® SCM - 17.0
CSSTCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSTCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
CSSTCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSTCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSTCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSTCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
CSSTCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSTCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
CSSTCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSTCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSTCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSTCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
CSSTCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSTCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
CSSTCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSTCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
CSSTCL35 EXEC,RENT,REUS,ALIAS,AMODE31
CSSTCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
CSSTCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSTCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSTCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSTCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSTCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSTCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSTCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSTCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSTCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSTCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSTCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSTCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSTCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSTCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSTCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSSTCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
CSSTCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSTCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
CSSTCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSTCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSTCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSTCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
CSSTCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSTCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
CSSTCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSTCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSTCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSTCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
CSSTCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSTCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
CSSTCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CSSTCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
CLTTBOD7 OBJECT MODULE.
CLTTBOD8 CAOPT,OBJECT MODULE.
CLTTCOD7 OBJECT MODULE.
CLTTCOD8 CAOPT,OBJECT MODULE.
CSSTBOD7 OBJECT MODULE.
CSSTBOD8 CAOPT,OBJECT MODULE.
CSSTCOD7 OBJECT MODULE.
CSSTCOD8 CAOPT,OBJECT MODULE.
**************************************************************
**************************************************************
FORTRAN
FORTBL01 EXEC,RENT,REUS,ALIAS,AMODE24
FORTBL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
FORTBL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORTBL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORTBL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORTBL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORTBL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORTBL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORTBL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORTBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
04-May-2018 693/1109
CA Endevor® SCM - 17.0
FORTBL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORTBL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORTBL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORTBL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORTBL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORTBL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORTBL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORTBL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FORTBL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FORTBL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORTBL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORTBL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORTBL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORTBL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORTBL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORTBL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORTBL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORTBL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORTBL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORTBL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORTBL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORTBL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORTBL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORTBL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORTBL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORTBL35 EXEC,RENT,REUS,ALIAS,AMODE31
FORTBL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
FORTBL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORTBL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORTBL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORTBL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORTBL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORTBL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORTBL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORTBL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORTBL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORTBL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORTBL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORTBL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORTBL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORTBL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORTBL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FORTBL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FORTBL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORTBL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORTBL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORTBL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORTBL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORTBL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORTBL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORTBL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORTBL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORTBL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORTBL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORTBL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORTBL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORTBL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORTBL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORTBL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORTCL01 EXEC,RENT,REUS,ALIAS,AMODE24
FORTCL02 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE24
FORTCL03 EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORTCL04 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORTCL05 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORTCL06 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORTCL07 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORTCL08 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORTCL09 EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORTCL10 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORTCL11 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORTCL12 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORTCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
04-May-2018 694/1109
CA Endevor® SCM - 17.0
FORTCL13 EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORTCL14 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORTCL15 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORTCL16 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORTCL17 NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FORTCL18 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
FORTCL19 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORTCL20 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
FORTCL21 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORTCL22 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORTCL23 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORTCL24 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
FORTCL25 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORTCL26 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
FORTCL27 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORTCL28 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORTCL29 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORTCL30 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
FORTCL31 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORTCL32 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
FORTCL33 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORTCL34 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
FORTCL35 EXEC,RENT,REUS,ALIAS,AMODE31
FORTCL36 CAOPT,EXEC,RENT,REUS,ALIAS,AMODE31
FORTCL37 EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORTCL38 CAOPT,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORTCL39 EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORTCL40 CAOPT,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORTCL41 EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORTCL42 CAOPT,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORTCL43 EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORTCL44 CAOPT,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORTCL45 EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORTCL46 CAOPT,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORTCL47 EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORTCL48 CAOPT,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORTCL49 EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORTCL50 CAOPT,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORTCL51 NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FORTCL52 CAOPT,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
FORTCL53 NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORTCL54 CAOPT,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
FORTCL55 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORTCL56 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORTCL57 NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORTCL58 CAOPT,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
FORTCL59 NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORTCL60 CAOPT,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
FORTCL61 NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORTCL62 CAOPT,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORTCL63 NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORTCL64 CAOPT,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
FORTCL65 NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORTCL66 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
FORTCL67 NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORTCL68 CAOPT,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
FORTBOD7 OBJECT MODULE.
FORTBOD8 CAOPT,OBJECT MODULE.
FORTCOD7 OBJECT MODULE.
FORTCOD8 CAOPT,OBJECT MODULE.
**************************************************************
**************************************************************
TELON
COBTBL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COBTBL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COBTBL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBTBL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBTBL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTBL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTBL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBTBL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
04-May-2018 695/1109
CA Endevor® SCM - 17.0
COBTBL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBTBL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBTBL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBTBL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTBL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTBL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBTBL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBTBL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTBL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTBL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBTBL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBTBL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBTBL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBTBL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTBL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTBL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBTBL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBTBL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBTBL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBTBL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTBL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTBL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBTBL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBTBL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTBLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTBLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTBLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTBLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COBTBLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COBTBLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBTBLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBTBLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTBLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTBLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBTBLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBTBLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBTBLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBTBLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTBLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTBLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBTBLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBTBLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTBLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTBLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBTBLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBTBLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBTBLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBTBLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTBLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTBLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBTBLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBTBLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBTBLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBTBLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTBLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTBLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBTBLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBTBLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTBLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTBLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTBLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTCL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COBTCL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
COBTCL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBTCL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBTCL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTCL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTCL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBTCL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBTCL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBTCL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBTCL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
04-May-2018 696/1109
CA Endevor® SCM - 17.0
COBTCL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTCL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTCL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBTCL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBTCL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTCL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTCL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBTCL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
COBTCL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBTCL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
COBTCL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTCL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTCL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBTCL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
COBTCL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBTCL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
COBTCL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTCL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTCL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBTCL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
COBTCL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTCLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
COBTCLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTCLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
COBTCLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COBTCLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
COBTCLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBTCLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBTCLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTCLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTCLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBTCLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBTCLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBTCLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBTCLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTCLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTCLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBTCLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBTCLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTCLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTCLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBTCLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
COBTCLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBTCLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
COBTCLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTCLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTCLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBTCLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
COBTCLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBTCLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
COBTCLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTCLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTCLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBTCLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
COBTCLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTCLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
COBTCLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTCLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TBL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL1TBL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL1TBL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1TBL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1TBL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1TBL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1TBL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TBL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TBL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1TBL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
04-May-2018 697/1109
CA Endevor® SCM - 17.0
PL1TBL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1TBL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TBL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TBL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1TBL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1TBL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1TBL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1TBL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1TBL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1TBL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1TBL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TBL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TBL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1TBL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1TBL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TBLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TBLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TBLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TBLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL1TBLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL1TBLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1TBLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1TBLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TBLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TBLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1TBLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1TBLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1TBLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1TBLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TBLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TBLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1TBLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1TBLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TBLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TBLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1TBLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1TBLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1TBLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1TBLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TBLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TBLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1TBLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1TBLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1TBLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1TBLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TBLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TBLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1TBLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1TBLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TBLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TBLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TBLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TCL69 TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL1TCL70 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE24
PL1TCL71 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1TCL72 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1TCL73 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL74 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL75 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1TCL76 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1TCL77 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL78 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL79 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TCL80 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TCL81 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1TCL82 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1TCL83 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TCL84 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TCL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
04-May-2018 698/1109
CA Endevor® SCM - 17.0
PL1TCL85 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1TCL86 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE24
PL1TCL87 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1TCL88 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE24
PL1TCL89 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL90 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL91 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1TCL92 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE24
PL1TCL93 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL94 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE24
PL1TCL95 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TCL96 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TCL97 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1TCL98 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE24
PL1TCL99 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TCLA0 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE24
PL1TCLA1 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TCLA2 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE24
PL1TCLA3 TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL1TCLA4 CAOPT,TELON,EXEC,RENT,REUS,ALIAS,AMODE31
PL1TCLA5 TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1TCLA6 CAOPT,TELON,EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1TCLA7 TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TCLA8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TCLA9 TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1TCLB0 CAOPT,TELON,EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1TCLB1 TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1TCLB2 CAOPT,TELON,EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1TCLB3 TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TCLB4 CAOPT,TELON,EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TCLB5 TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1TCLB6 CAOPT,TELON,EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1TCLB7 TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TCLB8 CAOPT,TELON,EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TCLB9 TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1TCLC0 CAOPT,TELON,NOT-EXEC,RENT,REUS,ALIAS,AMODE31
PL1TCLC1 TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1TCLC2 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,ALIAS,AMODE31
PL1TCLC3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TCLC4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TCLC5 TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1TCLC6 CAOPT,TELON,NOT-EXEC,NOT-RENT,REUS,NOT-ALIAS,AMODE31
PL1TCLC7 TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1TCLC8 CAOPT,TELON,NOT-EXEC,RENT,NOT-REUS,ALIAS,AMODE31
PL1TCLC9 TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TCLD0 CAPEXO,TELON,NOT-EXEC,RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TCLD1 TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1TCLD2 CAOPT,TELON,NOT-EXEC,RENT,REUS,NOT-ALIAS,AMODE31
PL1TCLD3 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TCLD4 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,ALIAS,AMODE31
PL1TCLD5 TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
PL1TCLD6 CAOPT,TELON,NOT-EXEC,NOT-RENT,NOT-REUS,NOT-ALIAS,AMODE31
COBTBOD9 TELON, OBJECT MODULE.
COBTBOE0 CAOPT,TELON,OBJECT MODULE.
CIITBOD9 TELON, OBJECT MODULE.
CIITBOE0 CAOPT,TELON,OBJECT MODULE.
PL1TBOD9 TELON, OBJECT MODULE.
PL1TBOE0 CAOPT,TELON,OBJECT MODULE.
COBTCOD9 TELON, OBJECT MODULE.
COBTCOE0 CAOPT,TELON,OBJECT MODULE.
CIITCOD9 TELON, OBJECT MODULE.
CIITCOE0 CAOPT,TELON,OBJECT MODULE.
PL1TCOD9 TELON, OBJECT MODULE.
PL1TCOE0 CAOPT,TELON,OBJECT MODULE.
**********************************************************************
04-May-2018 699/1109
CA Endevor® SCM - 17.0
04-May-2018 700/1109
CA Endevor® SCM - 17.0
* IT IS ALSO POSSIBLE TO BYPASS MEMBER ANALYSIS *
* BY SETTING THE RETURN CODE APPROPRIATELY. *
* *
***********************************************************************
* *
* ABOUT THIS EXAMPLE: *
* *
* THIS EXAMPLE IS INTENDED TO DEMONSTRATE HOW *
* AN EXIT MAY SPECIFY THE OUTPUT MEMBER NAME *
* TO BE USED IN A SITUATION WHERE THE SOURCE *
* MEMBER NAME IS NOT IDENTICAL TO THE OUTPUT *
* MEMBER NAME. WE WILL ALSO DEMONSTRATE HOW *
* TO BYPASS ANALYSIS FOR CERTAIN MEMBER NAMES. *
* *
* 1) THIS EXIT WILL TAKE ANY MEMBER NAMES THAT *
* CONTAIN CHARACTERS IN POSITIONS 9 AND 10 *
* AND BUILD A MEMBER NAME USING POSITIONS *
* 1-6, AND 9-10. THIS REPRESENTS A SITUATION *
* WHERE THE INPUT FILE MIGHT BE PANVALET AND *
* THE OUTPUT FILE IS A LOAD MODULE PDS. *
* *
* 2) THIS EXIT WILL BYPASS PROCESSING ANY MEMBERS *
* WHICH CONTAIN THE STRING "ABCDE" BEGINNING *
* IN THE SECOND POSITION OF THE SOURCE MEMBER *
* NAME. *
*
***********************************************************************
* *
* REGISTERS UPON ENTRY: *
* *
* R0: IGNORE *
* R1: POINTER TO A THREE WORD PARAMETER LIST *
* WORD 1: ADDRESS OF 10 CHARACTER SOURCE *
* MEMBER NAME *
* WORD 2: ADDRESS OF 10 CHARACTER OUTPUT *
* MEMBER NAME *
* WORD 3: ADDRESS OF WORK AREA - DOUBLE WORD *
* ALIGNED. THIS WORK AREA IS 400 *
* CHARACTERS IN SIZE (100 WORDS), *
* AND MAY HOLD INFORMATION BETWEEN *
* INVOCATIONS OF THE EXIT ROUTINE. *
* R2: IGNORE *
* R3: IGNORE *
* R4: IGNORE *
* R5: IGNORE *
* R6: IGNORE *
* R7: IGNORE *
* R8: IGNORE *
* R9: IGNORE *
* R10: IGNORE *
* R11: IGNORE *
* R12: IGNORE *
* R13: CALLERS SAVE AREA *
* --PLEASE NOTE----> THE FIRST WORD OF THIS SAVE AREA *
* MUST NOT BE MODIFIED. *
* R14: RETURN ADDRESS *
* R15: ENTRY POINT ADDRESS (ADDRESS OF "ANALEXIT") *
* *
* *
* REGISTERS UPON RETURN: *
* *
* R0: IGNORE *
* R1: IGNORE *
* R2: MUST BE RESTORED *
* R3: MUST BE RESTORED *
* R4: MUST BE RESTORED *
* R5: MUST BE RESTORED *
* R6: MUST BE RESTORED *
* R7: MUST BE RESTORED *
* R8: MUST BE RESTORED *
* R9: MUST BE RESTORED *
* R10: MUST BE RESTORED *
04-May-2018 701/1109
CA Endevor® SCM - 17.0
* R10: MUST BE RESTORED *
* R11: MUST BE RESTORED *
* R12: MUST BE RESTORED *
* R13: MUST BE RESTORED *
* R14: IGNORE *
* R15: RESULT RETURN CODE *
* RC = 0, CONTINUE EXECUTION, USE THE SOURCE *
* MEMBER NAME TO LOCATE THE OUTPUT, *
* RC = 4, CONTINUE EXECUTION, AN OUTPUT MEMBER *
* NAME HAS BEEN SUPPLIED IN THE *
* SECOND FIELD IN THE PARAMETER LIST. *
* RC = 8, TERMINATE PROCESSING OF THIS MEMBER *
* *
* *
***********************************************************************
* *
* NOTE: THIS EXIT MUST BE LINKED WITH PROGRAM C1BM7500 IN ORDER *
* TO BE USED DURING PROCESSING. C1BM7500 CONTAINS A *
* WEAK-UNRESOLVED REFERENCE TO A CSECT "ANALEXIT". *
* *
* LINKAGE EDITOR INPUT: *
* *
* INCLUDE SYSLMOD(C1BM7500) *
* INCLUDE SYSLIB(C1BM7XIT) <- USE CORRECT OBJECT MEMBER NAME *
* ENTRY C1BM7500 *
* NAME C1BM7500(R) *
* *
***********************************************************************
* *
* MODIFICATION LOG: (MOST RECENT CHANGES FIRST) *
* *
* *
* MODIFICATION DATE BY DESCRIPTION *
* ------------ ---- --- -------------------------------------- *
* *
***********************************************************************
EJECT
***********************************************************************
* *
* DEFINE THE MODULE NAME (CSECT) AND ENTRY POINT FOR LINKAGE *
* EDITOR PROCESSING. *
* *
***********************************************************************
C1BM7XIT CSECT
ENTRY ANALEXIT
ANALEXIT EQU C1BM7XIT
SPACE ,
***********************************************************************
* *
* SAVE THE CALLERS REGISTER CONTENTS, TO BE RESTORED WHEN RETURNING. *
* *
***********************************************************************
SAVE (14,12),, 'ANALEXIT-&SYSDATE-&SYSTIME'
SPACE ,
***********************************************************************
* *
* THEN ESTABLISH SOME LOCAL ADDRESSABILITY *
* *
***********************************************************************
LR R12,R15 COPY ENTRY POINT ADDRESS
USING ANALEXIT,R12 INFORM THE ASSEMBLER
SPACE ,
***********************************************************************
* *
* USING THE WORK AREA PROVIDED (PARM 3), ESTABLISH OUR OWN SAVE *
* AREA AND WORK AREA. *
* *
***********************************************************************
USING PARMAREA,R1 INFORM THE ASSEMBLER ABOUT THE X
. PARMAREA
L R2,PARM3 GET THE PARM 3 ADDRESS
ST R13,4(R2) SET BACK CHAIN IN NEW SAVEAREA
04-May-2018 702/1109
CA Endevor® SCM - 17.0
ST R13,4(R2) SET BACK CHAIN IN NEW SAVEAREA
ST R2,8(R13) SET FORWARD CHAIN IN OLD SAVE
LR R13,R2 ESTABLISH THE CURRENT SAVEAREA
USING SAVEAREA,R13 INFORM THE ASSEMBLER
SPACE ,
***********************************************************************
* *
* GET THE SOURCE AND OUTPUT MEMBER NAME ADDRESS INTO WORK REGISTERS *
* SO THAT R1 MAY BE FREED FOR OTHER WORK (AS DESIRED). *
* *
***********************************************************************
L R2,PARM1 LET R1 POINT TO SOURCE MEMBER
L R3,PARM2 LET R3 POINT TO OUTPUT MEMBER
DROP R1 (PARMAREA)
USING SOURCE,R2 INFORM THE ASSEMBLER
USING TARGET,R3 INFORM THE ASSEMBLER
SPACE ,
***********************************************************************
* *
* CHECK IF THE SOURCE MEMBER NAME CONTAINS "ABCDE" BEGINNING *
* IN THE SECOND POSITION. *
* *
***********************************************************************
CLC =C'ABCDE',INMBR+1 DESIRED DATA PRESENT?
BE RETURN08 . YES, THEN SET RETURN CODE = 8
SPACE ,
***********************************************************************
* *
* CHECK IF POSITIONS 9 AND 10 CONTAINS ANY DATA. *
* *
***********************************************************************
CLI INMBR+8,C' ' ANY CHARACTER IN POSITION 9?
BNH RETURN00 . NO, THEN RETURN WITH RC = 0
MVC OUTMBR(6),INMBR COPY POSITIONS 1-6 FROM INPUT X
. TO THE OUTPUT MEMBER NAME
MVC OUTMBR+6(2),INMBR+8 COPY POSITIONS 9-10 FROM INPUT X
. TO THE OUTPUT MEMBER NAME
B RETURN04 RETURN WITH RETURN CODE = 4
DROP R2,R3 (SOURCE,TARGET)
SPACE ,
***********************************************************************
* *
* RETURN TO THE CALLER WITH THE APPROPRIATE RETURN CODE. *
* *
***********************************************************************
RETURN00 DS 0H
XR R15,R15 SET RETURN CODE = 0
B PGMEXIT
SPACE ,
RETURN04 DS 0H
LA R15,4 SET RETURN CODE = 4
B PGMEXIT
SPACE ,
RETURN08 DS 0H
LA R15,8 SET RETURN CODE = 8
B PGMEXIT
SPACE ,
DROP R13 (SAVEAREA)
SPACE ,
PGMEXIT DS 0H
L R13,4(,R13) GET CALLERS SAVE AREA ADDRESS
RETURN (14,12),,RC=(15) RETURN
EJECT
***********************************************************************
* *
* PARM AREA DEFINITION *
* *
***********************************************************************
PARMAREA DSECT
PARM1 DS A ADDRESS OF SOURCE MEMBER NAME
PARM2 DS A ADDRESS OF OUTPUT MEMBER NAME
PARM3 DS A ADDRESS OF SUPPLIED WORK AREA
04-May-2018 703/1109
CA Endevor® SCM - 17.0
PARM3 DS A ADDRESS OF SUPPLIED WORK AREA
SPACE 3
***********************************************************************
* *
* SOURCE MEMBER NAME DEFINITION *
* *
***********************************************************************
SOURCE DSECT
INMBR DS CL10 INPUT MEMBER NAME
SPACE 3
***********************************************************************
* *
* TARGET MEMBER NAME DEFINITION *
* *
***********************************************************************
TARGET DSECT
OUTMBR DS CL10 OUTPUT MEMBER NAME
SPACE 3
***********************************************************************
* *
* SAVE AREA AND WORK AREA DEFINITION *
* *
***********************************************************************
SAVEAREA DSECT
DS 18F RESERVE THE FIRST 18 WORDS AS
* THE ACTUAL SAVE AREA.
WORKAREA DS 0D THIS IS THE BEGINNING OF THE
* WORK AREA
*** A TOTAL OF 100 WORDS ARE PROVIDED IN THIS SAVEAREA/WORKAREA.
*** THE SAVE AREA ITSELF TAKES THE FIRST 18, LEAVING 82 WORDS
*** (328 BYTES) AVAILABLE AS A WORK AREA.
EJECT
***********************************************************************
* *
* REGISTER EQUATE DEFINITIONS *
* *
***********************************************************************
R0 EQU 0
R1 EQU 1
R2 EQU 2
R3 EQU 3
R4 EQU 4
R5 EQU 5
R6 EQU 6
R7 EQU 7
R8 EQU 8
R9 EQU 9
R10 EQU 10
R11 EQU 11
R12 EQU 12
R13 EQU 13
R14 EQU 14
R15 EQU 15
END
/*
//*
//STEP2 EXEC PGM=IEWL,PARM='LIST,NCAL,XREF,SIZE=(256K,64K) ',
// COND=(0,NE)
//SYSLIB DD DISP=(OLD,DELETE),DSN=&&SYSLIN.
//SYSLMOD DD DISP=SHR,DSN=uprfx.uqual.LOADLIB
//SYSUT1 DD UNIT=tdisk,SPACE=(CYL,(5,3))
//SYSPRINT DD SYSOUT=*
//SYSLIN DD *
INCLUDE SYSLMOD(C1BM7500)
INCLUDE SYSLIB
ENTRY C1BM7500
NAME C1BM7500(R)
/*
//
04-May-2018 704/1109
CA Endevor® SCM - 17.0
Case-sensitive element names for files added from USS files systems
UNIX System Services (USS) path and file information in batch add, update, and retrieve actions
USS directories as base, source output, and include libraries on type definitions
USS path and file name support for the CONWRITE and CONDELE utilities
Uppercase letters
Lowercase letters
Numbers
National characters
Slash (/)
Plus (+)
Hyphen (-)
Period (.)
04-May-2018 705/1109
CA Endevor® SCM - 17.0
USS Files
A file name can be 255 characters long. To be portable, the file name should use only the characters
in the POSIX portable file name character set, as follows:
Uppercase or lowercase A to Z
Numbers 0 to 9
Period (.)
Underscore (_)
Hyphen (-)
Shells are case-sensitive, so distinguish between upper and lower case characters. For example,
FILE1 and file1 are not the same file names.
Suffixes
An extension, consisting of a period (.) and several characters, to indicate its file type. Files
containing C code could have the extension .c, for example:
dbmod3.c
We recommend that you use suffixes and extensions to group like files together. Doing so lets
you execute a single command against multiple files.
Important! Double-byte characters in a file name can cause problems, because they are
treated as single-byte data. If one of the double-byte characters is a period (.) or / (slash),
the file system treats these as path name delimiters.
Element Names
Element names can be 255 characters long, and may contain the following characters:
Uppercase letters
Lowercase letters
Numbers
04-May-2018 706/1109
CA Endevor® SCM - 17.0
Numbers
National characters
Period(.)
Hyphen (-)
Underscore(_)
ISPF
No support for actions involving long name elements or path names.
Quick Edit
Element names greater than 10 characters are truncated in lists. The truncated format consists of:
An ellipsis (…)
Note: Element information is not available from the ISPF list; it is only accessible from CA
CMEW or the Eclipse-Based UI. If there are multiple long name elements and the first five
characters are identical, ISPF displays a single entry.
HFS path names longer than 44 characters are truncated in type definitions and on the element
master display screen. The truncated format consists of:
An ellipsis (...)
Batch (SCL), API, CA CMEW, Eclipse-Based UI, and Web Services User-Written Client Programs
04-May-2018 707/1109
CA Endevor® SCM - 17.0
Path names can be 768 characters, not including the HFS file name
HFS path and file name support is unavailable for the following functions:
DSN files-CA Endevor SCM supports base and source output libraries:
PDS, PDSE
ELIB
CA Panvalet
CA Librarian
HFS
04-May-2018 708/1109
CA Endevor® SCM - 17.0
Note: Long element names are greater than 10 and less than 256 characters. Short element
names are less than or equal to 10 characters.
Element Name Characteristics USS DSN Base USS Source DSN Source
Base Output Output
Long-alphanumeric mixed case and @, $, Yes Forward-delta Yes No
#,., - ,_ only
Short-alphanumeric mixed case and @, $, Yes Forward-delta Yes No
#,., - ,_ only
Short-alphanumeric upper case and @, $, Yes Yes Yes Yes
#,., - ,_
Note: Long element names are greater than 10 and less than 256 characters. Short element
names are less than or equal to 10 characters.
04-May-2018 709/1109
CA Endevor® SCM - 17.0
Note: Long element names are greater than 10 and less than 256 characters. Short element
names are less than or equal to 10 characters. Element information is not available from
the ISPF or Quick Edit lists. It is only available from CA CMEW or the Eclipse-Based UI. If
there are multiple long name elements and the first five characters are identical, the ISPF
list displays a single entry.
Base
Source output
Include
The following table lists the CA Endevor SCM libraries that can be located on USS file systems:
Note: Processors can write outputs to USS directories. In addition, ensure that the
maximum record size associated with the USS file can be accommodated by the delta
library specified on the type definition.
04-May-2018 710/1109
CA Endevor® SCM - 17.0
When designating USS directories as base, source output, or include libraries in type definitions, you
can use site symbolics, CA Endevor SCM symbolics, or text to construct paths. When viewing the type
definition in ISPF, symbolics are displayed for the longer paths. As with CA Endevor SCM or user
symbolics, the site symbolics are resolved at runtime.
04-May-2018 711/1109
CA Endevor® SCM - 17.0
Note: The change of a delimiter for types with existing elements may make these elements
unusable for Retrieve actions using CA Endevor SCM, CA CMEW,or the Eclipse-Based UI.
Identifies the record delimiter used in a HFS file. A record delimiter is necessary due to the nature of
HFS files. HFS files contain one large data stream. Therefore, a delimiter is used to identify individual
records within that data stream.
This is also true for elements associated with a type defined as text (Data Format=T). When the
element is transferred from CA Endevor SCM to CA CMEW or any other client application that uses
CA Endevor SCM WebServices. These programs recognize and append the delimiter for the
exchanged records. However, these delimiters are then translated from EBCDIC to the target code
page. When the element is transferred to CA Endevor SCM, all delimiters are removed before
translation. The one exception is where two delimiters appear consecutively, in which case a single
space is inserted to avoid creating zero length records.
Note: The change of a delimiter for types with existing elements may make these elements
unusable for Retrieve actions.
COMP
Variable length records compressed by CA Endevor SCM.
CR
04-May-2018 712/1109
CA Endevor® SCM - 17.0
CR
Carriage return. The hex value is x'0D' (and also x'0D' in ASCII).
CRLF
Carriage return \ line feed. The hex value is x'0D25' (or x'0D0A' in ASCII). This is the default
delimiter used on the Windows platform.
CRNL
Carriage return \ new line. The hex value is x'0D15' (or x'0D0A' in ASCII).
Note: CRNL is sometimes referred to as CRLF. However, CRNL should not be confused with
the HFS RECFM value CRLF, which is the EBCDIC version.
F
Fixed Length. When the type is specified as fixed length, CA Endevor SCM does not expect or use
any delimiters found in the file. This option should also be used for Stream data especially in
binary elements, to allow the native file system (ASCII or EBCDIC) delimiters to remain
unchanged.
LF
Line feed. The hex value is x'25' (or x'0A' in ASCII).
NL
Default. New line character. The hex value is x'15' (or x'0A' in ASCII). This is the delimiter used by
the OEDIT and OBROWSE editors. It is also the default delimiter on Unix platforms and is
supported in several Windows editor environments, making it a good choice for interoperability.
V
Variable. The first four bytes of the record contain the RDW (record descriptor word). The RDW
contains the length of the entire record, including the RDW.
CA Endevor SCM managed files (base files and source output files)
04-May-2018 713/1109
CA Endevor® SCM - 17.0
If the target file exists, its existing file permissions are kept.
If the target file does not exist, the UNIX permissions of 777 a=rwx are set.
The directory structure for the target output file must give all users execute access.
If the DD statement for the file contains file permissions ons (PATHMODE) values, those
permissions are used.
If the DD statement does not contain file permission and if the file is an existing file, the
existing permissions are kept.
If the DD statement does not contain file permission and If the file does not exist, the
UNIX permissions of 777 (a=rwx) are set.
The directory structure for the target output file must give all users execute access.
Files written by the ENUSSUTL utility, which collects package backout information for USS
processor output files.
The ENQ QNAME and RNAME follow the convention used by ISPF Edit and OEDIT as documented in
the IBM ISPF Planning and Customization manual. The QNAME is SPFEDIT. RNAME is a 12-byte value
consisting of the 4-byte Inode#, the 4-byte Device# and a 4-byte sysplex indicator. The sysplex
indicator is x'00000001' if z/OS UNIX is in a sysplex (OextSysplexActv is set ON) or x'00000000' if z/OS
UNIX is not in a sysplex (OextSysplexActv is set OFF). The ENQ scope is set to SYSTEMS if z/OS UNIX is
in a sysplex, otherwise it is set to SYSTEM.
ALTID keyword
The security context used for USS file access in processor steps is determined by the ALTID
keyword. Processors can run under either the credentials of the user, or under the Alternate ID,
so that USS outputs (created, copied, compiled, and so on) will have the Alternate ID as the
owner or group owner.
04-May-2018 714/1109
CA Endevor® SCM - 17.0
PATHOPTS=(OCREAT)
Any USS data sets created in processor steps using PATHOPTS=(OCREAT) are created using the
security context of the user ID, prior to the invocation of the processor program. When used in
the processor step, these data sets are opened using the security context of the processor step.
EXEC PGM=BPXBATCH
The security context of a processor step executing the IBM USS utility program BPXBATCH
depends on the following factors:
Whether BPXBATCH runs a shell script (PARM=’SH’) or directly executes an executable file
(PARM=’PGM’). We recommend BPXBATCH be invoked directly as processor step.
The following table shows combinations of these parameters and settings with the resulting
security context of the processor step executing BPXBATCH.
Note: We do not recommend the use of BPXBATCH in an IKJEFT01 step, because the
results can be unpredictable.
Whether BPXBATCH invoked by a CLIST or REXX in a processor step executing IKJEFT01 executes
under the context of the alternate ID depends on the following two additional factors:
Whether or not a LGNT$$$I swap was performed prior to the invocation of BPXBATCH.
Whether or not a prior USS service call was made in the job step prior to the BPXPBATCH call.
For example, the prior USS service call could occur when a USS Base or Source Output Library
was used during the CA Endevor SCM job step, or when a shell script was executed in this or
any prior CA Endevor SCM action.
The following table shows the security context results from these two additional factors when
calling BPXBATCH from a processor step that executes IKJEFT01:
LGNT$$$I swap performed Prior USS Service call made Security context
04-May-2018 715/1109
CA Endevor® SCM - 17.0
Yes No Alternate ID
Yes Yes Failure
No No User ID
No Yes User ID
04-May-2018 716/1109
CA Endevor® SCM - 17.0
The optional feature table embedded in ENCOPTNS provides a description of each option with
detailed information about parameter values and downstream effects.
The OFT source, as distributed, contains each option already coded, but inactive. To activate an entry,
remove the asterisk (*) in column 1 and verify that the second parameter, if required, contains the
appropriate value. Use sample JCL BC1JTABL to assemble and link ENCOPTBL to your iprfx.iqual.
CSIQAUTU outside of SMP/E or use an SMP/E USERMOD to accomplish this. BC1JTABL is supplied in
the installation library iprfx.iqual.CSIQJCL.
The optional feature table is provided with the CA Endevor SCM installation files as member
ENCOPTBL in the installation TABLES library (iprfx.iqual.CSIQSRC).
04-May-2018 717/1109
CA Endevor® SCM - 17.0
Package Administration
Contents
What Is a Package?
A package is a set of CA Endevor® SCM actions that might require approval before being executed. To
create a package, the user defines SCL that specifies actions to be performed against Elements. The
SCL in a package must be explicit. Wildcarding is not allowed in any SCL contained in a package. When
you create a package, you define it as a standard (default) package or as an emergency package.
Emergency packages require approval from emergency approver groups. An emergency approver
group must be given the authority to approve emergency packages. When creating a package, you
must also specify whether it is a promotion package. A promotion package can contain Move actions
only and can be easily reused. A promotion package can be either a standard or an emergency
package.
Note: For information about how to create packages and perform package actions in foreground see
Package Element Actions. For information about SCL statements for packages, see Manage Packages
in Batch (Batch Package Facility).
Package Benefits
You can use packages to do the following actions:
Lock the Elements in a package. Locking prevents modification of the Element at the source of the
package action, target of the package action, or both.
Require that a package be approved before it can be executed. Approver groups can be defined
locally or to an external security product such as CA Top Secret for z/OS, IBM RACF, or CA ACF2
for z/OS.
Inspect the Elements in a package for security, signout, synchronization conflicts, and source
changes that might affect its successful execution.
Validate package components to prevent Elements from being moved until the Elements have
been assembled, compiled, or linked with current versions of all their dependencies.
04-May-2018 718/1109
CA Endevor® SCM - 17.0
Restart a package if it fails during execution. The package is "checkpointed" and, when re-
executed, begins at the first action that failed and re-executes the failed actions.
Back out package outputs (and later back in) after a package has been executed.
Secure package actions using the External Security Interface (ESI) or using approver groups.
Customize package processing using exit points before and after each package function,
Package Lifecycle
The package lifecycle consists of five steps. A package is created, then cast and later reviewed by the
appropriate approvers. When the package is approved, it is executed and, when no further
modifications are required, the package can be committed and optionally archived and deleted.
After a package has been executed, its outputs can be backed out, backed in, or shipped to remote
locations.
CA Endevor® SCM assigns packages a status at each phase of the lifecycle and provides exit points
before and after all package functions.
The following table shows the change in package status that occurs when each package function is
performed. The table also lists the next appropriate action after the specified package action is
performed.
Unsuccessful
Review package
In-approval Approved Execute
Approved
In-approval Denied Reset and correct
Denied
Execute package
Approved In-execution None
04-May-2018 719/1109
CA Endevor® SCM - 17.0
Successful
Unsuccessful
Commit package Executed Committed Delete, Reset, Archive
Backout package Executed Executed None, Backin, Ship
Backin package Executed Executed None, Backout, Ship
Ship package Executed Executed None, Backout, Backin, Commit
Note: At any time during package processing, you can reset a package to In-edit status. You
can backout and backin a package as many times as necessary - until you commit the
package.
Reviewing Packages
A package must be reviewed if one or more approver groups are associated with the inventory areas
included in the package. Once a package is in the review phase, only designated approvers can access
the package and review its contents. If the Dynamic Approvers option is enabled in the CA Endevor®
SCM Options Table, package approvers can add more users as one-time approvers for a particular
package while it is in the in-approval state.
A local approver group is an approver group which contains approver user IDs defined to CA
Endevor® SCM. An external approver group is an approver group which has no user IDs defined in CA
Endevor® SCM. Instead, the user IDs are defined to the external security packages such as CA Top
Secret, RACF, or CA ACF2.
Note: For more information about approver groups, see Approver Groups (https://docops.ca.
com/display/CE/Using+Approver+Groups).
04-May-2018 720/1109
CA Endevor® SCM - 17.0
The approver group PKGQA consists of three approvers. The approver group was established with a
quorum size of 2, with one approver required. This means that in addition to the required approver,
one of the two remaining members of the approver group must approve the package for it to be
executed.
The following table shows the package status in relationship to the review phase:
Executing Packages
The package can be either executed online or submitted in batch. To execute the package, the user
must have the authority to execute the package and the authority to perform the actions that are
contained in the package.
The following table shows the package status in relationship to the execution phase. The outputs of
packages that have been executed can be backed out, backed in, or shipped to remote locations.
Note: CA Endevor® SCM releases Element locks during package execution. Each lock is
released after the associated action completes successfully.
Committing Packages
Package processing provides you with the ability to backout, and later backin, change packages, if
necessary. The BACKOUT/BACKIN option is available only after you have executed a package. All
package event information (user, date, and time information pertaining to each step of the package
processing procedure), and backout/backin data, is maintained with the package until you commit
the package.
Committing a package simply removes any backout/backin data while retaining package event
information. Commit a package only when you are sure that you no longer need to back it out or in.
The following table shows the package status in relationship to the commit phase:
04-May-2018 721/1109
CA Endevor® SCM - 17.0
CA Endevor® SCM Batch Package Facility lets you perform package processing in batch. This process
involves placing package action SCL in an SCL data set and specifying when to submit this SCL for
processing.
Supports all foreground package actions, except the Dynamic Approver option. For more
information, see the chapter "Processing Packages in Foreground."
SUBMIT
ARCHIVE
INSPECT
Invokes the GENPKGID exit, if installed, to generate a new package ID. For information on package
exits, see Exits Reference (https://docops.ca.com/display/CE17/Exits+Reference).
The SUBMIT action allows you to schedule package execution using the CA 7 scheduling
application. For information about implementing the CA 7 interface, see Using the CA 7 Interface
for Package Execution (see page 765).
04-May-2018 722/1109
CA Endevor® SCM - 17.0
Specify additional package action information if it is required for the action you chose to perform.
Specify when to submit the package action SCL for batch processing.
1. Access the Batch Package panel by typing 6 (Batch Packages) in the OPTION field on the
Primary Options Menu and pressing Enter.
2. Select an action by typing the number of the action you want to use in the ...SELECT AN
ACTION field. The following describes the valid actions:
1. Build SCL
Creates the SCL necessary to perform package processing in batch.
2. Edit SCL
Edits batch package SCL using the standard ISPF/PDF edit facility.
3. Browse SCL
Reviews batch package SCL using the standard ISPF/PDF browse facility.
6. Submit JCL
Submits a JCL job stream that executes one or more package in batch. Before submitting
the job, you can use action 5 to specify additional DD statements to be included with the
job.
3. Enter the name of the SCL data set that contains the package action SCL or that you want to
contain the package action SCL in the SCL DATA SET NAME fields or the SEQUENTIAL OR
PARTITIONED DATA SET field. Use standard ISPF data set specifications. You can specify a
partitioned data set or a sequential file. The record length of the data set can be fixed (exactly
80) or variable (at least 84).
a. APPEND TO EXISTING SCL--Type Y in this field if you wish to append new SCL to
existing SCL in the specified data set. Type N in this field if you want to replace the
data that currently exists in that data set.
b.
04-May-2018 723/1109
CA Endevor® SCM - 17.0
b. INCLUDE ADDITIONAL JCL--Type Y in this field if you wish to include additional JCL to
be submitted with the execution JCL. Use action 5, BUILD ADDITIONAL JCL, to specify
the additional DD statements to be included. Type N in this field if you do not want to
include additional DD statements.
5. If you are ready to submit the package action SCL for processing specify the JCL job statement
in the JCL JOB STATEMENTS field to execute the package actions, using action 6, Submit JCL.
Otherwise continue with Step 6.
6. Press Enter. The panel that appears depends upon the action you specified in Step 2 above, as
shown in the following:
1. Build SCL
The Package Specification panel appears.
2. Edit SCL
The ISPF edit panel appears displaying the data set you specified in Step 3. Use this panel
to edit batch package SCL.
3. Browse SCL
The ISPF browse panel appears displaying the data set you specified in Step 3. Use this
panel to review the batch package SCL.
6. Submit JCL
The package action SCL is submitted using the JCL job statement specified in the JCL JOB
STATEMENT field.
Build a package selection list from which you select the package actions to be performed on one
or more packages.
04-May-2018 724/1109
CA Endevor® SCM - 17.0
2.
Generate a selection list by leaving this blank or by specifying a wildcard in this field. CA
Endevor® SCM builds a list of packages that match the wildcard.
3. To limit your selection list of packages to those with a specific status, type Y in the
appropriate status field(s). If you do not wish to include packages of a specific status type in
your selection list, tab to that field(s) and type N.
4. To limit your selection list to packages that were created a specific number of days ago,
specify the number of days (up to 999) in the ADDITIONAL SELECTION CRITERIA field.
5. To limit your selection list by enterprise or promotion packages, use the following fields:
You can use the promotion package filter options to limit the selection list by promotion
flag and target location. For more information about the filters, see Promotion Package
Filter Options.
6. Press Enter, the Package Selection List appears. You can then apply actions to one or more of
the packages in this list.
You can specify one or any combination of the fields on this panel when building a package selection
list.
Note: For more information about applying actions to packages in the selection list, see
How to Specify Actions to Perform on Selected Packages (see page 726).
2. Type the fully-qualified ID of the package you wish to create or update in the PACKAGE ID
field.
04-May-2018 725/1109
CA Endevor® SCM - 17.0
Note: If you have the optional GENPKGID exit enabled at you site, you can leave this
field blank, and a new package ID is automatically generated when you press Enter.
For more information about the GENPKGID exit, see Exits Reference (https://docops.
ca.com/display/CE17/Exits+Reference).
3. Press Enter. The panel that appears next depends on whether you are creating a new package
or updating an existing one. The Create a New Package panel appears when creating a new
package. The Modify an Existing Package panel appears when updating a package.
This panel lets you apply actions to one or more of the packages in the list. Specify the actions you
wish to perform on the package by typing the two-letter action code beside the appropriate package
ID and pressing Enter. If additional information is required to process a particular action, a second
panel appears so you can enter the appropriate information for that action. The Additional
Information panels are described in the Specify Additional Package Action Information section.
Note: The Package Selection List contains all packages that meet the criteria specified on
the Package Specification Panel. You may not, however, be authorized to perform all
actions against every package in the list for the following reasons:
The package is non-shareable and you are not the owner of the package.
The package has one or more approvers associated with it of which you are not a member.
If no additional information is required for the specified action the word "written" appears next to
the package ID to indicate that the package action SCL has been written to the SCL data set. To exit
the Package Selection List, enter the END command. The Batch Package panel appears again.
Package Actions
This table lists and defines the batch package actions that you can specify, along with the required
status of the package to which that action is applied. The table also indicates the panel that appears if
additional information is required to process that action.
04-May-2018 726/1109
CA Endevor® SCM - 17.0
04-May-2018 727/1109
CA Endevor® SCM - 17.0
APPROVE
ARCHIVE
CAST
DEFINE
DENY
EXECUTE
EXPORT
SUBMIT
04-May-2018 728/1109
CA Endevor® SCM - 17.0
To approve a package
2. Press Enter.
1. Select CANCEL THE APPROVE ACTION by typing 2 in the ...SELECT AN ACTION field.
2. Press Enter.
To enter notes
You can only use an Archived package to generate package reports against the output data set. For
more information, see the chapter “Archived Package Reports” in Reports (https://docops.ca.com
/display/CE17/Reports).
The Archive Package panel appears when you specify the ARCHIVE (AR) action on the Package
Selection panel. You can use this panel to perform the following actions:
Archive a package definition to an external data set. The ARCHIVE action can, optionally, delete
the package after it is successfully written to an external data set. For promotion packages, the
current and all historical versions are archived, and the delete option deletes all versions of a
package.
To archive a package
04-May-2018 729/1109
CA Endevor® SCM - 17.0
2. Enter the name of the data set to which the package definition is to be archived in the
ARCHIVE TO DATA SET NAME fields or the OTHER PARTITIONED OR SEQUENTIAL DATA SET
field. Use standard ISPF data set specifications. The archive package file must be defined with
variable length records and have a minimum record length of 4200. The data set blocksize
must be 4 bytes greater than the record length. We recommend that you define a blocksize of
0 and let the system default to the optimum block size.
a. DELETE AFTER ARCHIVE--Type Y in this field if you wish to delete the package after the
package definition is successfully archived. If this is a promotion package, all versions
of the package are deleted. Type N in this field if you do not want to delete the
package after it is archived.
c. Press Enter.
1. Select CANCEL THE ARCHIVE ACTION by typing 2 in the ...SELECT AN ACTION field.
2. Press Enter.
To display notes
Cast a package.
To cast a package
2. Specify whether CA Endevor® SCM should validate package components when casting the
package in the VALIDATE COMPONENTS field.
04-May-2018 730/1109
2.
CA Endevor® SCM - 17.0
c. W-Validate components, but do not fail the cast if there are errors. You can only
specify this field if your site allows you to specify, through C1DEFLTS, whether
component validation is to be performed.
Note: For more information about component validation, see Component Validation
(https://docops.ca.com/display/CE17/Component+Validation).
3. Specify whether the backout/backin facility is available for this package in the ENABLE
BACKOUT field:
4. Specify the time frame within which the package can be executed, by date (in ddmmmyy
format) and time (in hh:mm format) in the EXECUTION WINDOW FROM/TO field. The initial
values are taken from the package definition.
5. Press Enter.
1. Select CANCEL THE CAST ACTION by typing 2 in the ...SELECT AN ACTION field.
2. Press Enter.
To enter notes
Important! You can define a new package using the Define Package panel by copying the
contents of an existing package or by importing the SCL from an existing data set. The
Batch Package Facility does not provide a mechanism to build the action SCL that makes up
a package. You can do this either by:
04-May-2018 731/1109
CA Endevor® SCM - 17.0
To define a package
Description
Provide a package description. You can enter up to a 50-character description. If the text
contains embedded spaces enclose it in single quotation marks.
Package Type
Specify the type of package: standard or emergency.
Promotion Package
Indicates whether this is a promotion package.
Sharable Package
Specify whether this package can be edited by more than one person when in In-edit
status.
Y-The package is shareable, and can be edited by other than the package creator.
Enable Backout
Specify whether the backout/backin facility is available for this package:
Append To Package
Specify whether you want to append imported or copied data to the contents of this
package. If you do not append the data, the contents of the package will be overwritten
with the new information. This field is valid only if the SCL IMPORT DATA SET NAME fields
or the PACKAGE TO BE COPIED field are specified.
04-May-2018 732/1109
CA Endevor® SCM - 17.0
Package To Be Copied
Enter a package ID in this field if you want the DEFINE action to copy SCL from an existing
package into the package you are creating. The package ID you specify must be a fully
qualified, existing package.
1. Select CANCEL THE DEFINE ACTION by typing 2 in the ...SELECT AN ACTION field.
2. Press Enter.
To enter notes
To deny a package
2. Press Enter.
04-May-2018 733/1109
CA Endevor® SCM - 17.0
1. Select CANCEL THE DENY ACTION by typing 2 in the ...SELECT AN ACTION field.
2. Press Enter.
To enter notes
Execute a package.
To execute a package
2. Specify the time frame within which the package can be executed, by date (in ddmmmyy
format) and time (in hh:mm format in the EXECUTION WINDOW FROM/TO field. The values in
this field are taken from the package definition and can be changed only if the existing
execution window is closed.
3. Press Enter.
1. Select CANCEL THE EXECUTE ACTION by typing 2 in the ...SELECT AN ACTION field.
2. Press Enter.
To display notes
04-May-2018 734/1109
CA Endevor® SCM - 17.0
To export a package
2. Specify the location of the external data set to which the SCL will be written in the EXPORT TO
DATA SET NAME fields. Use standard ISPF data set specifications. You can specify a partitioned
data set or a sequential file. The record length of the data set can be fixed (exactly 80) or
variable (at least 84).
3. Type Y in the EXPORT OPTIONS REPLACE MEMBER field if you want CA Endevor® SCM to
replace an existing like-named member when exporting the SCL to the external data set. You
can only replace a member if a member name is specified in the EXPORT TO DATA SET NAME
fields. Type N in this field if you do not want to replace an existing like-named member.
4. Press Enter.
1. Select CANCEL THE EXPORT ACTION by typing 2 in the ...SELECT AN ACTION field.
2. Press Enter.
To display notes
To update a package
Description
Provide a package description. The current package description of the package you are
updating appears in this field. You can enter or modify an up to 50-character description.
If the text contains embedded spaces enclose it in single quotation marks.
Package Type
04-May-2018 735/1109
CA Endevor® SCM - 17.0
Package Type
Specify the type of package: standard or emergency.
Sharable Package
Specify whether this package can be edited by more than one person when in In-edit
status.
Y -- The package is shareable, and can be edited by someone other than the package
creator
Enable Backout
Specify whether the backout/backin facility is available for this package:
Append to Package
Specify whether you want to append imported or copied data to the contents of this
package. If you do not append the data, the contents of the package will be overwritten
with the new information. This field is valid only if the SCL IMPORT DATA SET NAME fields
or the PACKAGE TO BE COPIED field are specified.
Package to Be Copied
Enter a package ID in this field if you want the DEFINE action to copy SCL from an existing
package into the package you are updating. The package ID you specify must be a fully
qualified, existing package.
1. Select CANCEL THE DEFINE ACTION by typing 2 in the ...SELECT AN ACTION field.
2. Press Enter.
04-May-2018 736/1109
CA Endevor® SCM - 17.0
To enter notes
2. Press Enter.
The Enter Package Note Text panel appears.
2. Press Enter.
1. Select DISPLAY PACKAGE NOTES by typing N in the ... SELECT AN OPTION... field.
A sample JCL job stream for submitting a package can be found in iprfx.iqual.CSIQJCL, member name
ENDEVOR. Use this as a model for your own Submit procedure.
To submit a package
2. Specify the location of the data set containing the JCL jobcard in the JOB CARD DATA SET
NAME fields or the OTHER PARTITIONED OR SEQUENTIAL JOB CARD DATA SET field. Use
standard ISPF data set specifications. You can specify a partitioned data set or a sequential
file. The record length of the data set can be fixed (exactly 80) or variable (at least 84).
3. Specify the one- to eight-character JCL procedure name to be invoked in the SUBMIT OPTIONS
JCL PROCEDURE NAME field. A sample of a procedure is in the iprfx.iqual.CSIQJCL member
ENDEVOR.
4. Press Enter.
04-May-2018 737/1109
CA Endevor® SCM - 17.0
1. Select CANCEL THE SUBMIT ACTION by typing 2 in the ...SELECT AN ACTION field.
2. Press Enter.
When you finish typing the text, press Enter then the END command to save your changes, otherwise
press the END command to cancel text updates and return to the previous panel.
2. Provide at least one JCL JOB statement in JCL JOB STATEMENT field.
3. Press Enter.
04-May-2018 738/1109
CA Endevor® SCM - 17.0
Approver Groups
Contents
Create a Relationship Between an Inventory Area and an Approver Group (see page 754)
04-May-2018 739/1109
CA Endevor® SCM - 17.0
Create a Relationship Between an Inventory Area and an Approver Group (see page 754)
Change the Approver Group for an Inventory Area (see page 754)
Approver Group Relationship List (see page 755)
Display a Relationship Between an Inventory Area and an Approver Group (see page 755)
Delete a Relationship Between an Inventory Area and an Approver Group (see page 756)
Change the Approver Group for an Inventory Area (see page 757)
Approver Group Relationship Panel (see page 757)
Delete a Relationship Between an Inventory Area and an Approver Group (see page 758)
Create a Relationship Between an Inventory Area and an Approver Group (see page 758)
Change the Approver Group for an Inventory Area (see page 759)
Locking and Approver Groups (see page 759)
Approver groups are used with package processing. A package is similar to a request data set in that it
contains one or more CA Endevor® SCM actions which are to be performed. However, a package may
require approval before it can be executed. Approval is "electronic sign-off" for the package.
Packages can be approved or denied by people who have been identified as approvers. An approver
group is simply a particular subset of those people.
Note: The C1DEFLTS parameter APRVFLG can be set to 'no' to turn off the package
processing requirement.
Approver groups can be defined externally or internally to CA Endevor® SCM. When a group is
defined internally, all approver user IDs are stored in the master control file along with the approver
group definition. When a group is defined externally, the approver group definition is stored in the
master control file and the approver user IDs are stored in the external security product in use at
your site. If you want to define a user ID as required to approve packages, you must use an internal
approver group.
When using external approver groups, the CA Endevor® SCM approver group name must be the same
name as the group defined to the external security product.
A quorum size. This is the minimum of approvers from the group who must approve a package
before it can be executed.
Required approvers. For example, if you want the project leader for a development group to
approve all changes to the software with which the group is working, you can designate the
project leader as a required approver.
Note: Since external groups don't have any approvers defined locally to CA Endevor® SCM,
required approvers are not applicable for these groups.
04-May-2018 740/1109
CA Endevor® SCM - 17.0
Any required approvers in an approver group must approve a package before it can be executed.
Even if the quorum requirements are met, if a required approver has not yet approved a package, it
cannot be executed.
Dynamic approver groups can only be assigned to approve a package while the package is in the
in-approval state.
When an approver group is related to a particular inventory area, then the group must approve
packages containing actions that affect elements in that inventory area. An inventory area consists of
a logical classification (system, subsystem, and type) within a CA Endevor® SCM location
(environment and stage).
Multiple approver groups can be associated with one inventory area. A single approver group can be
associated with many inventory areas.
Note: Once an approver group has been related to an inventory area, all processing for that
inventory area must be performed using packages. You can exempt certain actions from
this restriction by using the CA Endevor® SCM Optional Features Table.
04-May-2018 741/1109
CA Endevor® SCM - 17.0
In the following example, the IBMGROUP is 'External' and it associates the QA Profile group of users
to that IBMGROUP. ADD(dept) is the department acid you want to own the resource and PERMIT
(acid) is the user acid you want to permit it to. The PERMIT(acid) can be an attached profile or the ALL
record if all users should have access.
The following are sample ACF2 commands that will define the ENDAPR resource class to CA ACF2 for z
/OS Security. Substitute your values for lowercase items.
SET CONTROL(GSO)
INSERT CLASMAP.endapr RESOURCE(ENDAPR) RSRCTYPE(end) ENTITYLN(16)
For improved performance, it is suggested that the ENDAPR resource class be made resident by
adding it to the INFODIR record. If masked rule keys are used, this is required.
CHANGE INFODIR TYPES(R-Rend)
If the ENDAPR resource class was made resident, any modifications to the resource rules will not be
active until the following console command is issued:
F ACF2, REBUILD(end)
endgrp1
endgrp2.
In this example, user1, user2, and user3 would belong to endgrp1; all users would belong to endgrp2.
04-May-2018 742/1109
CA Endevor® SCM - 17.0
$KEY(endgrp1) TYPE(end)
UID(user1) ALLOW
UID(user2) ALLOW
UID(user3) ALLOW
$KEY(endgrp2) TYPE(end)
UID(*) ALLOW
Use the appropriate UID string for your site and the UID string in the rule can be masked. If your site
has any questions, contact your local CA ACF2 for z/OS Security Support.
Use the Approver Group Request panel to perform the following actions:
Blank
Use this field to display the current definition of a specified approver group.
#
Use this field to delete an approver group.
C
Use this field to create an approver group.
U
Use this field to update the definition of an approver group.
Environment
Name of the environment in which the approver group you want is defined. The current
environment is displayed initially. Fill in a new name and press Enter if the approver group is in a
different environment.
Approver Group
The name of the approver group you want to use. To update or delete an approver group, fill in
the full name and press enter to directly access the Approver Group Definition panel. If you leave
the approver group name blank or use a name mask, CA Endevor® SCM returns an Approver
Group Selection List showing the approver groups currently defined.
04-May-2018 743/1109
CA Endevor® SCM - 17.0
1. Enter the name of the approver group you want to display in the APPROVER GROUP field.
2. Verify that the approver group you want to display is defined to the current environment in
the ENVIRONMENT field. If the approver group you want to display is defined to a different
environment fill in the correct environment name.
3. Press Enter.
The Approver Group Definition panel displays.
4. When you have finished viewing the approver group definition, press the END key to return to
the Approver Group Request panel.
Note: To display an approver group definition from the Approver Group Selection List, type an
S to the left of the name of the approver group you want to display and press Enter. The
Approver Group Definition panel displays.
1. Enter the name of the approver group you want to delete in the APPROVER GROUP field or
leave the field blank to obtain a list of available approver groups.
The Approver Group Definition panel displays if you have specified an approver group in
the APPROVER GROUP field. If the Approver Group Definition panel displays, proceed to
Step 5.
The Approver Group Selection List panel displays if you have left the APPROVER GROUP
field blank. If the Approver Group Selection List panel displays, proceed to Step 4.
3. From the Approver Group Selection List panel type # to the left of the name of the approver
group you want to delete and press ENTER. The Approver Group Definition panel displays.
4. Review the information on the Approver Group Definition panel to verify that you want to
delete it.
04-May-2018 744/1109
CA Endevor® SCM - 17.0
1. Enter the name of the approver group you want to create in the APPROVER GROUP field. If
this is to be an external approver group, the name of the group must match an existing profile
in your security product.
Note: If you are using CA Top Secret for z/OS, the IBMGROUP resource definition
must be used.
3. Specify the appropriate approver group information on the Approver Group Definition panel
and press Enter to complete processing.
1. Enter the name of the approver group you want to update in the APPROVER GROUP field.
3. Change the appropriate approver group information on the Approver Group Definition panel
and press Enter to complete processing.
Note: If you select more than one approver group, processing occurs in the order in
which the names are listed.
The following fields appear on the Approver Group Selection List panel:
04-May-2018 745/1109
CA Endevor® SCM - 17.0
The following fields appear on the Approver Group Selection List panel:
Environment
Display-only. The name of the current environment.
Approver Group
Display-only. The names of the approver groups.
1. Enter the name of the approver group you want to display in the APPROVER GROUP field.
2. Verify that the approver group you want to display is defined to the current environment in
the ENVIRONMENT field. If the approver group you want to display is defined to a different
environment fill in the correct environment name.
Note: To display an approver group definition from the Approver Group Selection
List, type an S to the left of the name of the approver group you want to display and
press Enter. The Approver Group Definition panel displays.
4. When you have finished viewing the approver group definition, press the END key to return to
the Approver Group Request panel.
1. Enter the name of the approver group you want to delete in the APPROVER GROUP field or
leave the field blank to obtain a list of available approver groups.
3. Press Enter.
04-May-2018 746/1109
3.
The Approver Group Definition panel displays if you have specified an approver group in
the APPROVER GROUP field. If the Approver Group Definition panel displays, proceed to
Step 5.
The Approver Group Selection List panel displays if you have left the APPROVER GROUP
field blank. If the Approver Group Selection List panel displays, proceed to Step 4.
4. From the Approver Group Selection List panel type # to the left of the name of the approver
group you want to delete and press ENTER. The Approver Group Definition panel displays.
5. Review the information on the Approver Group Definition panel to verify that you want to
delete it.
1. Enter the name of the approver group you want to update in the APPROVER GROUP field.
3. Press Enter.
The Approver Group Definition panel displays.
4. Change the appropriate approver group information on the Approver Group Definition panel.
Note: If you select more than one approver group, processing occurs in the order in
which the names are listed.
04-May-2018 747/1109
CA Endevor® SCM - 17.0
Note: The current processing option displays in the upper left corner. You can cancel any
requests by pressing the End key.
Approver Group
Display-only. The name of the approver group displayed, or to be created, updated, or deleted.
Environment
Display-only. The name of the current environment.
Title
A 1- to 50-character description for the approver group.
Quorum Size
The minimum number of people in this group who must approve packages. For locally defined
groups, acceptable values are 0 - 16. For externally defined groups, acceptable values 0 - 32760.
Approver
For locally defined approver groups, the user IDs of the approvers in this group. For externally
defined approver groups, leave all of the approver fields blank. This tells CA Endevor® SCM to
look externally for the user IDs that are part of this group.
Req'd (Y/N)
Indicates whether this approver is required to approve the package: Y (yes) or N (no).
1. Enter the name of the approver group you want to delete in the APPROVER GROUP field or
leave the field blank to obtain a list of available approver groups.
3. Press Enter.
The Approver Group Definition panel displays if you have specified an approver group in
the APPROVER GROUP field. If the Approver Group Definition panel displays, proceed to
Step 5.
The Approver Group Selection List panel displays if you have left the APPROVER GROUP
field blank. If the Approver Group Selection List panel displays, proceed to Step 4.
4.
04-May-2018 748/1109
CA Endevor® SCM - 17.0
4. From the Approver Group Selection List panel type # to the left of the name of the approver
group you want to delete and press ENTER. The Approver Group Definition panel displays.
5. Review the information on the Approver Group Definition panel to verify that you want to
delete it.
1. Enter the name of the approver group you want to create in the APPROVER GROUP field. If
this is to be an external approver group, the name of the group must match an existing profile
in your security product.
Note: If you are using CA Top Secret for z/OS, the IBMGROUP resource definition
must be used.
4. Specify the appropriate approver group information on the Approver Group Definition panel.
1. Enter the name of the approver group you want to update in the APPROVER GROUP field.
3. Press Enter.
The Approver Group Definition panel displays.
4. Change the appropriate approver group information on the Approver Group Definition panel.
Note: If you select more than one approver group, processing occurs in the order in
which the names are listed.
04-May-2018 749/1109
CA Endevor® SCM - 17.0
You can use the Dynamic Approver Group Panel to create, update, or delete a dynamic approver
group. To access this panel, select DA-Dynamic Approvers on the Review Package panel.
If the dynamic approver group does not yet exist for the package, you can enter a value in the
QUORUM field and specify from 1 to 16 approver user IDs and whether or not their approval is
required.
If the dynamic approver group exists, this panel is preformatted with any existing dynamic approver
group data. If the group has approved or denied the package, all fields are nonmodifiable. Otherwise,
you can update or delete only those approver IDs that you entered, unless you are a superuser. Any
entries where the approver has approved or denied the package are protected and are not
modifiable even by a superuser. If the entry is modifiable, you can blank out the approver ID
(effectively deleting the user ID from the dynamic approver group), type a new user ID over the
existing one (effectively deleting the original user ID and replacing it with a new one), or update the
APPROVAL REQ'D value. The QUORUM value can be updated at any time.
If a dynamic approver group is attached to a package and then deleted, the status of the package will
not be updated, regardless of whether the dynamic approver group has actually approved or denied
the package. The package will need to be reapproved by any attached approver groups.
When you press Enter, the panel is updated with any changes that you made on the panel. If you
press PF3, any changes you made on the panel are ignored.
QUORUM
Similar to the QUORUM value seen on the Approver Group Definition panel, this is the quorum
size for the approver group. Valid values are 0 through 16. The quorum size cannot exceed the
number of approvers on the panel. The quorum size cannot be 0 unless one or more approvers
are required approvers. A user cannot change the quorum size in such a way that it alters the
logical approval status of the group; that is, the quorum size must always be greater than the
number of approvers who have approved the package thus far.
APPROVER
TSO user ID of a dynamic approver. The ID must pass syntax checking: it cannot contain
embedded spaces; it must consist solely of alphanumeric characters and #, @, and $; and it must
not begin with a number.
REQ
Indicates whether the approval of this approver is required. Valid values are Y, N, or blank. Blank
defaults to N.
04-May-2018 750/1109
CA Endevor® SCM - 17.0
STATUS
Indicates whether the approver has approved the package, and the time and date when the
approval was performed.
ADDED BY
Indicates the user ID that added this approver and the date and the time when the approver ID
was added.
Note: You do not have the option to provide a name or descriptive title for the dynamic
approver group. The group created on this panel is named Dynamic Approver and its title is
Dynamic Approver Group information.
Use the Approver Group Relation Request panel to perform the following actions:
Display the relationship between certain inventory areas and an approver group.
Delete a relationship between inventory areas and approver groups. When you delete a
relationship, neither the approver group nor the inventory area is deleted; only the relationship
between the two is deleted.
The following fields appear on the Approver Group Relation Request panel:
Blank
Use this field to display a list of relationships. To display all relationships, leave all fields, except
ENVIRONMENT and APPROVER TYPE, blank. To restrict the display to certain portions of the
inventory, enter additional information on the panel.
#
Specify this option to delete a relationship. When you delete a relationship, neither the approver
group nor the inventory area is deleted; only the relationship between the two is deleted.
C
Specify this option to create a relationship. When you create a relationship, the approver group
and inventory area involved must have been previously established within CA Endevor® SCM. You
are creating only the relationship.
04-May-2018 751/1109
CA Endevor® SCM - 17.0
U
Specify this option to update a relationship. This option allows you to change the approver group
for a given area of the inventory.
Environment
Displays the name of the environment that contains the inventory area and the approver group to
which the inventory area is (to be) related. If you want to change the environment, fill in the
appropriate name and press Enter.
Approver Type
Indicates the approver type for this approver group: standard or emergency. An approver group
designated as standard can be used to approve standard packages only. Similarly, an approver
group designated as emergency can be used only to approve emergency packages. You must
enter the entire word when indicating approver type; that is, you cannot abbreviate the entry.
System
Name of the system to which this approver group relationship applies.
Subsystem
Name of the subsystem to which this approver group relationship applies.
Type
The element type to which this approver group relationship applies.
Stage Number
The stage number to which this approver group relationship applies.
2. Indicate whether the approver group type is standard or emergency in the APPROVER TYPE
field. You must enter the entire word when indicating the approver type.
4. Press Enter.
The Approver Group Relationship List panel displays.
5. When you have finished viewing the list of relationships press the END key to return to the
Approver Group Relation Request panel.
2. Indicate whether the approver group type is standard or emergency in the APPROVER TYPE
field. You must enter the entire word when indicating the approver type.
3. Enter the appropriate information in the INVENTORY AREA fields. You can enter one of three
04-May-2018 752/1109
CA Endevor® SCM - 17.0
3. Enter the appropriate information in the INVENTORY AREA fields. You can enter one of three
values in these fields:
A full name. Enter a full name (number) in one or more fields, to indicate a specific
system, subsystem, type, and/or stage number.
Blanks. Leave one or more fields blank to build a list of approver group relationships for
the inventory areas matching the criteria entered.
An asterisk (*). Use an asterisk to relate an approver group to all systems, subsystems,
types or stages in an environment.
For example, if an approver group has been related to an inventory area with a system name
of ABC and a stage number of 2, and with an asterisk as the subsystem and the type, then the
approver group relationship applies to all elements in system ABC and Stage 2 -- regardless of
subsystem and type.
Note: To display a relationship from the Approver Group Relationship List panel,
type an S to the left of the inventory area and press Enter to display the Approver
Group Relationship panel.
4. Press Enter.
The Approver Group Relationship panel displays with all inventory areas matching the criteria
you indicated and the approver groups related to these areas.
5. When you have finished viewing the Approver Group Relationship panel, press the END key to
return to the Approver Group Relation Request panel.
2. Indicate whether the approver group type is standard or emergency in the APPROVER TYPE
field.
3. Specify the inventory area to which the approver group is related in the INVENTORY AREA
fields. You can obtain a list of all relationships by leaving these fields blank.
5. Press Enter.
If the Approver Group Relationship List panel displays, proceed to Step 6. If the Approver
Group Relationship panel displays, proceed to Step 7.
6. From the Approver Group Relationship List panel type a # to the left of the name of the
inventory area for which you want to delete a relationship and press Enter. The Approver
Group Relationship panel displays.
7. Review the information on the Approver Group Relationship panel to verify that you want to
04-May-2018 753/1109
CA Endevor® SCM - 17.0
7. Review the information on the Approver Group Relationship panel to verify that you want to
delete this relationship.
2. Indicate whether the approver group type is standard or emergency in the APPROVER TYPE
field. You must enter the entire word when indicating the approver type.
3. Specify the inventory area to which the approver group is related in the INVENTORY AREA
fields. You must enter either a full name or an asterisk in each of these fields.
5. Press Enter.
The Approver Group Relationship panel displays.
6. Enter the name of the approver group for which you want to build a relationship in the
APPROVER GROUP field.
2. Indicate whether the approver group type is standard or emergency in the APPROVER TYPE
field. You must enter the entire word when indicating the approver type.
3. Specify the inventory area to which the approver group is related in the INVENTORY AREA
fields. You can obtain a list of all relationships by leaving these fields blank.
5. Press Enter.
If the Approver Group Relationship List panel displays, proceed to step 6. If the Approver
Group Relationship panel displays, proceed to step 7.
6. From the Approver Group Relationship List panel, type a U to the left of the name of the
inventory area for which you want to change a relationship and press Enter.
The Approver Group Relationship panel displays.
7. On the Approver Group Relationship panel, enter the name of the approver group you want
to relate to this inventory area in the APPROVER GROUP field.
04-May-2018 754/1109
CA Endevor® SCM - 17.0
Delete a relationship between inventory areas and approver groups. When you delete a
relationship, neither the approver group nor the inventory area is deleted; only the relationship
between the two is deleted.
The following fields appear on the Approver Group Relationship List panel:
Environment
The current environment.
Approver Type
This field indicates whether this approver group type is emergency or standard.
System
The system to which the approver group is related.
Subsystem
The subsystem to which the approver group is related.
Type
The type to which the approver group is related.
Stage Number
The number of the stage to which the approver group is related.
Approver Group
The approver group related to the inventory area. Note that a given inventory area may be
related to several approver groups.
2. Indicate whether the approver group type is standard or emergency in the APPROVER TYPE
field. You must enter the entire word when indicating the approver type.
3. Enter the appropriate information in the INVENTORY AREA fields. You can enter one of three
values in these fields:
04-May-2018 755/1109
3.
A full name. Enter a full name (number) in one or more fields, to indicate a specific
system, subsystem, type, and/or stage number.
Blanks. Leave one or more fields blank to build a list of approver group relationships for
the inventory areas matching the criteria entered.
An asterisk (*). Use an asterisk to relate an approver group to all systems, subsystems,
types or stages in an environment.
For example, if an approver group has been related to an inventory area with a system name
of ABC and a stage number of 2, and with an asterisk as the subsystem and the type, then the
approver group relationship applies to all elements in system ABC and Stage 2 -- regardless of
subsystem and type.
Note: To display a relationship from the Approver Group Relationship List panel,
type an S to the left of the inventory area and press Enter to display the Approver
Group Relationship panel.
4. Press Enter.
The Approver Group Relationship panel displays with all inventory areas matching the criteria
you indicated and the approver groups related to these areas.
5. When you have finished viewing the Approver Group Relationship panel, press the END key to
return to the Approver Group Relation Request panel.
2. Indicate whether the approver group type is standard or emergency in the APPROVER TYPE
field.
3. Specify the inventory area to which the approver group is related in the INVENTORY AREA
fields. You can obtain a list of all relationships by leaving these fields blank.
5. Press Enter.
If the Approver Group Relationship List panel displays, proceed to Step 6. If the Approver
Group Relationship panel displays, proceed to Step 7.
6. From the Approver Group Relationship List panel type a # to the left of the name of the
inventory area for which you want to delete a relationship and press Enter. The Approver
Group Relationship panel displays.
7. Review the information on the Approver Group Relationship panel to verify that you want to
delete this relationship.
04-May-2018 756/1109
7. CA Endevor® SCM - 17.0
delete this relationship.
2. Indicate whether the approver group type is standard or emergency in the APPROVER TYPE
field. You must enter the entire word when indicating the approver type.
3. Specify the inventory area to which the approver group is related in the INVENTORY AREA
fields. You can obtain a list of all relationships by leaving these fields blank.
5. Press Enter.
If the Approver Group Relationship List panel displays, proceed to step 6. If the Approver
Group Relationship panel displays, proceed to step 7.
6. From the Approver Group Relationship List panel, type a U to the left of the name of the
inventory area for which you want to change a relationship and press Enter.
The Approver Group Relationship panel displays.
7. On the Approver Group Relationship panel, enter the name of the approver group you want
to relate to this inventory area in the APPROVER GROUP field.
Complete the deletion of a relationship between an inventory area and an approver group. When
you delete a relationship, neither the approver group nor the inventory area is deleted; only the
relationship between the two is deleted.
Complete the creation of a relationship between an inventory area and an approver group.
The following fields appear on the Approver Group Relationship panel. All fields are display-only,
except the APPROVER GROUP field.
04-May-2018 757/1109
CA Endevor® SCM - 17.0
Environment
This is the name of the current environment.
Approver Type
This is the type of approver group you specified: emergency or standard.
Approver Group
Name of the approver group to be related to this particular inventory area. Change the name of
the approver group accordingly.
System
This is the name of the system in the inventory area to which the approver group is related.
Subsystem
This is the name of the subsystem in the inventory area to which the approver group is related.
Type
This is the name of the element type in the inventory area to which the approver group is related.
Stage Number
This is the stage number in the inventory area to which the approver group is related.
2. Indicate whether the approver group type is standard or emergency in the APPROVER TYPE
field.
3. Specify the inventory area to which the approver group is related in the INVENTORY AREA
fields. You can obtain a list of all relationships by leaving these fields blank.
5. Press Enter.
If the Approver Group Relationship List panel displays, proceed to Step 6. If the Approver
Group Relationship panel displays, proceed to Step 7.
6. From the Approver Group Relationship List panel type a # to the left of the name of the
inventory area for which you want to delete a relationship and press Enter. The Approver
Group Relationship panel displays.
7. Review the information on the Approver Group Relationship panel to verify that you want to
delete this relationship.
04-May-2018 758/1109
CA Endevor® SCM - 17.0
2. Indicate whether the approver group type is standard or emergency in the APPROVER TYPE
field. You must enter the entire word when indicating the approver type.
3. Specify the inventory area to which the approver group is related in the INVENTORY AREA
fields. You must enter either a full name or an asterisk in each of these fields.
5. Press Enter.
The Approver Group Relationship panel displays.
6. Enter the name of the approver group for which you want to build a relationship in the
APPROVER GROUP field.
2. Indicate whether the approver group type is standard or emergency in the APPROVER TYPE
field. You must enter the entire word when indicating the approver type.
3. Specify the inventory area to which the approver group is related in the INVENTORY AREA
fields. You can obtain a list of all relationships by leaving these fields blank.
5. Press Enter.
If the Approver Group Relationship List panel displays, proceed to step 6. If the Approver
Group Relationship panel displays, proceed to step 7.
6. From the Approver Group Relationship List panel, type a U to the left of the name of the
inventory area for which you want to change a relationship and press Enter.
The Approver Group Relationship panel displays.
7. On the Approver Group Relationship panel, enter the name of the approver group you want
to relate to this inventory area in the APPROVER GROUP field.
04-May-2018 759/1109
CA Endevor® SCM - 17.0
In this example, user 1 defines package PKG1 with two Add actions. Add number 1 is to an inventory
area protected by an approver group, while Add number 2 is to an area with no associated approver
group. User 1 casts and approves PKG1.
User 2 then modifies the external files referenced in the two Add actions, and submits SCL to Add the
elements, without including the SCL in a package.
When Locking=OFF:
The first Add statement in the SCL for user 2 fails because an approver group protects the target
inventory area and the Add statement is not part of a package. The second Add statement
completes successfully because no approver group protects the target inventory area, and locking
is off.
User 1 then executes package PKG1, and both Add actions fail with PKMR515E and PKMR516E
messages informing User 1 of an integrity error because the file has been modified since he cast
package PKG1.
When Locking=(ON,Y):
Both Add statements in the SCL for user 1 fail because the element names at the target inventory
locations have been locked by the cast of package PKG1.
When User 1 then executes package PKG1, both Add actions fail with PKMR515E and PKMR516E
messages.
In this example, PKG1 fails execution whether locking is ON or OFF. Locking, however, does prevent
the changed file in Add #2 from being added to CA Endevor® SCM.
In this example, a site has a four-stage development life cycle, with a map that moves from
STG1→STG2→STG4. An approver group protects STG4. User 1 defines package PKG2 to move
element ELM1 from STG2→STG4.
After User 1 casts and approves PKG2, User 2 retrieves element ELM1, modifies it, adds it back to CA
Endevor® SCM, and tries to move it back into STG2.
With Locking=OFF:
The move back into STG2 is successful. User 2 then submits SCL to move ELM1 to STG4 but does
not include the SCL in a package. User 2's SCL fails because the STG4 inventory area is protected
by an approver group.
User 1 then executes package PKG2, and this move also fails with a PKMR512E message informing
User 1 of an element level mismatch.
With Locking=(ON,Y):
User 2's move back into STG2 fails because the element names at the source and target inventory
locations have been locked by the cast of package PKG2.
04-May-2018 760/1109
CA Endevor® SCM - 17.0
User 1 then executes package PKG2, and this move succeeds because element ELM1 at STG2 has
been protected from modification by locking.
A promotion package is a package of Move actions that can be reused to automatically promote the
package contents along the map until they reach the final location. It can consist of Move actions
only and the from environment and stage location for all Move actions must be the same. Although
you can reuse a promotion package until the contents have been promoted to the end of the map,
you still need to approve the package between executions, if approval is required, but you do not
have to reset the package, manually edit the SCL to modify the inventory source location, or re-cast
the package.
Each time a package is executed, the current copy of the package is saved and a new copy of the
package is created. Each copy is referred to as a version. There are no restrictions on the number of
promotions that can be performed against a promotion package. You can view historic versions of a
package through many of the package list functions. Even after you have executed a promotion
package, it is possible to reset the package, edit its SCL, and retain prior versions of the package.
You define a package as a promotion package when you create or modify the original package. A
promotion package can be defined as either a standard or an emergency package.
1. Create/modify package action. You define the package as a promotion package, when you
create or modify the original version.
2. Cast package action. You cast the original package. All subsequent casts of new versions occur
automatically. The following take place at cast time:
The package is checked to verify that it consists of move actions only and that all the
elements within the move actions are at the same location (environment and stage).
The target location information is stored in the package header. This identifies the target
location of the elements associated with each version of the promotion package. You can
view this information on the Display History panel and you can extract it using the API or
CSV List Package Header functions.
04-May-2018 761/1109
CA Endevor® SCM - 17.0
Note: Promotion packages are automatically recast, unless you turn off this
functionality in the Optional Features table, ENCOPTBL, using the following option:
PROM_PKG_SUPPRESS_AUTOCAST. For more information, see How to Use the
SUPPRESS_AUTOCAST Option. (see page 765)
3. Execute package action. After a version is executed, it includes the package header, approver
and approver extension records, SCL, action summary and cast report records associated with
the package at the time it was successfully executed. What happens after execution depends
on whether the package has reached the end of the map:
If execution occurred at the final location defined in the map, the package remains in
Executed status.
If the package is not at the final location in the logical map, following a successful
execution, the following promotion package logic is performed against that package.
a. The executed package is committed and a historical version of the package is saved.
b. The current version of the package is reset to remove approver, action summary, and
cast report records.
c. The SCL records associated with the current package are rebuilt to point to the next
location.
d. The STOPRC statement matches the previous SCL STOPRC statement. This also
matches the original STOPRC value specified at the time of the last create/modify,
unless you manually edited the statement in the SCL while the package was in In-Edit
status.
e. The rebuilt comment statements are enclosed in quotes, unless the comment
contains a quote. In this case, the comments are enclosed in double quotes.
f. The comment field is forty characters. On the rebuild, trailing blanks are removed.
g. All the SCL statements of the old package that start with an asterisk are copied to the
new package until the first record of the old package is found that does not start with
an asterisk. Consequently, only the comments at the beginning of the old package
are copied to the new package and all subsequent comments are dropped. The
number of comment records copied to the new package can be zero to many,
depending on the location of the first non-comment card found in the old package.
h. A cast action is performed against the rebuilt version of the package. The component
validation value found in the package header determines if the validate component
option is in effect. If the previous value was Y or W (warnings), the component
validation parameter is set to Y on the automated cast action. If the cast fails, the
new version of the package is placed into In-Edit status.
4. Commit package action. After execution, the commit action occurs automatically for
promotion packages. After the commit action, this version of the package can no longer be
used, only viewed. However, if the execution occurred at the final location defined in the
map, the package remains in Executed status and you must manually issue the commit action.
The commit action includes an option to delete all the promotion history associated with
04-May-2018 762/1109
4.
The commit action includes an option to delete all the promotion history associated with
previous versions of the package.
Back-out records are automatically deleted. The cast report records are retained for
current and historic versions.
5. Reset package action. After you execute a package, you may decide to manually edit the SCL
associated with that package before performing another promotion, for example to add
another move action. If you execute the Reset action, the package is placed in In-Edit status
and all the history associated with that promotion package is retained. Before you cast the
package, make sure that you add the appropriate SCL Move statements, because following
the successful execution of the package, a new version of the package is created and the SCL
move statements of the new version are updated to point to the next location.
Note: If the package is reset when it is at the final location in the logical map, an historic
version of the current package is created before the current version is replaced.
6. Archive package action. This action archives the current and all historical version of a package.
The option Delete After Archive deletes all versions of a package.
7. Delete package action. This action deletes not only the latest version of the package, but all
previous versions of the package.
You can override this processing, in order to ship a package before it reaches the end of the map, by
using either of the following options:
Stop-at-Stage feature -- When enabled, this features stops promotion package processing at a
specified stage so that the package stays in Executed status and can be shipped from that stage.
For more information, see the Stop-at-Stage feature. (see page 763)
SUPPRESS_AUTOCAST optional feature -- When enabled, this feature turns off automatic cast
processing. For more information, see How to Use the SUPPRESS_AUTOCAST Option. (see page
765)
Following shipment, the package can be restarted to continue the promotion process.
Stop-at-Stage Feature
The Promotion Package Stop-at-Stage feature lets administrators define inventory lifecycle stages at
which the automatic processing of promotion packages is suspended. This allows promotion
packages to be shipped from a location other than the final location defined in the map. For example,
a promotion package stopped in this manner can be shipped using the package ship facility to a test
location for validation before continuing with its promotion up the map.
04-May-2018 763/1109
CA Endevor® SCM - 17.0
During promotion package processing, at the completion of a successful execution of a package, the
promotion package logic checks the stop-at-stage parameter settings in the C1DEFLTS table, for the
target environment and stage associated with the promotion package, to see if the feature is
activated at that stage. If it is, the promotion package processing is interrupted and the package
remains in Executed status, allowing it to be shipped.
Following the shipment of the package, the promotion package can be restarted to continue the
promotion process. The user must issue the Reset action to restart the package. As part of the Reset
action, the target location information associated with each of the actions included in the package is
automatically updated to point to the next location in the logical map. Then the user must issue the
Cast, Review, and Execute actions to restart the promotion package processing that enables the
package to continue its promotion up the map.
If the administrator modifies the C1DEFLTS table and de-activates the Stop-at-Stage feature at a
location, you can still use the same technique to restart promotion packages that were previously
interrupted at that location. The only difference is that you must manually update the SCL to point to
the next logical location following the execution of the Reset action.
For more information, see How to Enable the Stop-at-Stage Feature. (see page 764)
STG1PSAS
This is a stage level parameter that, if set to Y, activates the stop-at-stage feature for promotion
packages. You can activate this feature for one or both stages within the same environment. To
activate this feature for a second stage, use STG2PSAS. You can also activate this feature in more
than one environment (for example, in both QA/1 and PRD/1).
If you do not wish to activate this feature you can code STG1PSAS=N, or STG1PSAS=, or not code
the parameter at all. The default is N.
STG2PSAS
This is a stage level parameter that, if set to Y, activates the stop-at-stage feature for promotion
packages at a second stage. You can activate this feature for one or both stages within the same
environment. To activate this feature for the first stage, use STG1PSAS. You can also activate this
feature in more than one environment (for example, in both QA/1 and PRD/1).
If you do not wish to activate this feature you can code STG2PSAS=N, or STG2PSAS=, or not code
the parameter at all. The default is N.
04-May-2018 764/1109
CA Endevor® SCM - 17.0
To ship a package mid-map, follow these steps to get your package in Executed status in the stage
you want to ship it from:
1. Cast, Review and Execute the package until the SCL target location matches the location you
wish to ship from.
3. Use the Modify package action to change the Promotion Package attribute to N.
Following the shipment of the package, the promotion package can be restarted to continue the
promotion process by following these steps:
2. Use the Modify package action to change the Promotion Package attribute back to Y.
3. Edit the target location information associated with each of the actions included in the
package to point to the next location defined in the logical map.
CA 7 is a JOB scheduling product that can add significant value to CA Endevor® SCM package
processing by controlling the initiation of package execution. CA 7 enables you to define execution
rules by class to CA 7 and schedule a package execution, dependent upon the completion of another
CA 7 based job.
04-May-2018 765/1109
CA Endevor® SCM - 17.0
When accessing a package that has associated CA 7 information, CA Endevor® SCM queries CA 7 to
determine if the information is still applicable. If the CA 7 information is no longer applicable (for
example the job has been cancelled), CA Endevor® SCM removes it.
After the execution JCL has been written to the CA 7 JCL library, CA Endevor® SCM builds the CA 7
DEMAND command and pass it to CA 7 using the CA 7 CAICCI programming interface.
Upon successful completion of the CA 7 DEMAND command, CA Endevor® SCM updates each
package that is executed by the JOB with the JOBNAME, CA 7 JOB number, in addition to the user
date and time the JOB was scheduled. If someone cancels the scheduled execution JOB using CA 7,
each package associated with that JOB must be reset and re-approved before it can be executed
outside the scope of CA 7.
BEND--CA-7ProcessingFlow--OTH
04-May-2018 766/1109
CA Endevor® SCM - 17.0
To implement the CA 7 interface, you must first define the following C1DEFLTS parameters to allow
communication between CA 7 and CA Endevor® SCM. The parameters are CA7CCINODE, CA7JCLDSN,
CA7JCLID and CA7JCLLIB. These parameters are shown next:
C1DEFLTS changes:
C1DEFLTS TYPE=MAIN, X
.
.
CA7CCINODE=, CA 7 ADDR SPACE NODE (CAICCI) X
CA7JCLDSN=, CA 7 CA7JCLID/CA7JCLLIB DSNAME X
CA7JCLID=, CA 7 JCL DATASET INDEX NUMBER X
CA7JCLLIB=, CA 7 JCL SYMBOLIC INDEX X
.
.
The CA 7 Parameters
The following describes the various C1DEFLTS parameters:
CA7CCINODE
The CA7CCINODE parameter is used to communicate with CA 7. It defines the CAICCI node name
where the CA 7 address space executes. If this parameter is not specified, local mode is assumed.
CA7JCLDSN
Defines the data set name associated with CA7JCLID or CA7JCLLIB.
The implementation of the CA 7 scheduler interface is done using the batch package SUBMIT action.
04-May-2018 767/1109
CA Endevor® SCM - 17.0
BEND--PackageSCLandCA-7--OTH
CA 7 Reports
The following reports are generated by CA 7:
04-May-2018 768/1109
CA Endevor® SCM - 17.0
This diagram illustrates this complex scenario that consists of multiple scenarios:
How to Create Backup Files for USS Supported Files (see page 814)
04-May-2018 769/1109
CA Endevor® SCM - 17.0
As a CA Endevor® SCM administrator, you can enable the package ship facility to transmit package
outputs (source, object, listing, or load modules), or package backout members from a host site to
another site. Shipping backout members enables you to undo the prior shipment of package outputs.
The utility is designed for users who develop software at a central (host) site and want to transmit
source, object, or executable code to other (remote) sites.
The following diagram shows how you enable the package ship facility.
04-May-2018 770/1109
CA Endevor® SCM - 17.0
Before shipping a package, complete the following procedures to enable package ship:
2. Configure the Package Ship Utility Program (see page 782) -- The package ship utility program
must be configured for you site.
Note: If you plan to ship USS supported files (HFS, zFS, or NFS files), you must create
backup files. For more information about this procedure, see How to Enable USS
Supported Files for Package Ship (see page 814).
04-May-2018 771/1109
CA Endevor® SCM - 17.0
5. Create Model Transmission Control Statements (see page 802) -- One of these data
transmission packages must be available, unless the Local transmission method is used:
XCOM (CA)
CONNECT:Direct
Note: Packages can also be shipped between CPUs that share DASD. This
transmission method is referred to as Local.
6. (Optional) Enable the Post-ship Script feature (see page 808) -- This feature enables the
conditional execution of custom job steps, called scripts, at a remote destination before or
after the package shipment process has completed.
7. (Optional) Enable the Ship Asis feature (see page 782) -- This feature lets you ship outputs and
backout members (and HFS files, or both) according to the backout status of the package. If
not enabled, outputs from the time the package was executed are shipped regardless of the
backout status of the package.
Review Prerequisites
Before users can ship packages, certain prerequisites are required. Complete the following
prerequisites.
Make sure that you understand how Package Ship works. Review the following topics:
How Package Ship Works for USS Files (see page 775)
The Package Ship facility requires data transmission software. Verify that one of the following
data transmission methods is available:
04-May-2018 772/1109
CA Endevor® SCM - 17.0
CA XCOM
CONNECT:Direct
Note: Packages can also be shipped between CPUs that share DASD. This transmission method is
referred to as Local.
All IDs involved need to have OMVS segments, because these enable the IDs to start a shell
environment and issue USS commands. These IDs include the IDs performing the ship (the
signed on user), the Alternate ID, and the user IDs associated with the transmission method
started task (XCOM, Connect direct, and so on.)
The transmission method started tasks must be authorized to submit jobs on behalf of the the
user doing the shipment (ACID or XAUTH authority).
The user IDs that are executing the transmission method steps, need access to the
appropriate load libraries.
The users involved must have read/write authority to the staging directory location prefix (by
default /tmp/) and the target directory to use ACLs and or insert CHOWN CHMOD commands
into the remote commands file.
If the optional feature PACKAGE_SHIP_WITH_ALTID is turned on, the following are required:
The transmission method started tasks must be authorized to submit jobs on behalf of the
Alternate ID
04-May-2018 773/1109
CA Endevor® SCM - 17.0
Note: When you use the Package Ship facility, the Ship Asis feature determines whether
the backout and backin status of a package has any effect on what gets shipped. For more
information, see the Ship Asis Feature (see page 777).
Host site processing -- When you request a package shipment, CA Endevor® SCM submits a job
stream at the host site. This job does the following:
Note: Staging data sets are dynamically created using information obtained during
the Shipment execution. The High Level Qualifier of the Staging name is obtained
from the MAPPING Destination, while the next level qualifiers are obtained from
the DATE and TIME detail from the execution parameter. The qualifiers are created
as DMMDDYY and THHMMSS. If simultaneous shipments are submitted to JES, it is
possible that these qualifiers would not be unique. This case can result in JCL errors
indicating that the shipment of duplicate data set names is being attempted. To
avoid this failure situation, a wait mechanism should be employed by the site
implementation so as to not submit shipments within the same second.
A job stream to copy package outputs from staging data sets to remote production data
sets.
A file with correspondences between production and staging data sets at the host and the
remote site
Data transmission commands to transfer all the above to the remote site. (Not applicable
for Local transmission.)
3. Transmits the host staging data sets and other files to the remote site. (Not applicable for
Local transmission.)
Remote site processing -- When the job stream built at the host site in Step 1 executes at the remote
site, it does the following:
1. Copies the package outputs from the remote staging data sets to production libraries. For
Local transmission, outputs are copied from the host staging data sets to the production
libraries.
04-May-2018 774/1109
CA Endevor® SCM - 17.0
2. Deletes, in the production libraries, all package members that were also deleted on the host.
4. (Optional) Deletes the staging data sets at the remote site. (Not applicable for Local
transmission.)
Note: Remote staging data sets are not built for Local transmission. The host staging data
sets must exist on a shared DASD, and will be copied directly into the remote production
libraries.
1. A temporary staging path structure is allocated using the host prefix specified in the
destination record.
2. The USS objects are copied into this structure, with one path for each mapped directory.
04-May-2018 775/1109
CA Endevor® SCM - 17.0
2. The USS objects are copied into this structure, with one path for each mapped directory.
Note: The package utility uses the backout records created by the ENUSSUTL utility
to correctly identify the relevant source file at the time the package was created.
3. Optionally, if complementary files have been requested, then these backout files are also
copied into their own set of paths under the staging directory.
5. The archive file is then transmitted to the remote location along with a job stream and
commands to perform the un-archive.
6. At the remote location, the archive is expanded, and the remote copy commands (contained
in the .ARUCD dataset) are executed to copy from the staging. directory into the final,
production, location.
7. If complementary files were requested, then an additional file (.CRJOB) is created at the
remote location containing the necessary commands to copy the complementary files from
the remote staging directory if required.
The Following diagram illustrates the extensions for the USS process.
04-May-2018 776/1109
CA Endevor® SCM - 17.0
Ships the package outputs of elements that have not been backed out.
Ships the pre-package outputs of elements that have been backed out.
Ships the pre-package outputs of elements that have not been backed out.
Ships the package outputs of elements that have been backed out.
If Ship Asis is not enabled, outputs from the time the package was executed are shipped regardless of
the backout status of the package. In this case, when you ship a package, the original outputs are
shipped, even if the entire package or some of the elements have been backed out. Similarly, when
you ship backouts, the original package backouts are shipped. The backout and backin status of a
package has no effect on what gets shipped.
When the Ship Asis feature is enabled, the user always must take care to synchronize shipments to
destination sites when the package is partially or fully backed out. With this feature enabled, during
the execution of a package backout and backin action (including element action backout and backin),
the user will receive messages in the package log for all destinations that this package was sent to
prior to these actions. The purpose of these messages is to alert the user that the package may need
to be reshipped, because these backout or backin actions have changed the package outputs. The
message severity level can be set to caution or warning. For example, sample caution messages are
shown next:
PKMR632C PACKAGE WAS PREVIOUSLY SHIPPED TO THE FOLLOWING DESTINATION
(S) PRIOR TO [BACK-OUT| BACK-IN]
PKMR633C JDLSHIP 19DEC12
PKMR633C JDOSHIP 19DEC12
Reason:
This package was shipped before the backout or backin function was executed. Multiple
PKMR633C messages can appear, because one message is shown for each date and time the
package was shipped to each destination.
Action:
You may need to reship the package now that the backout function has changed the packa
ge outputs.
04-May-2018 777/1109
CA Endevor® SCM - 17.0
1. The administrator creates custom script job steps by editing the shipment JCL models based
on your site's requirements. These models include additional job steps in the remote job that
can execute before or after the job copies the package outputs to their target data sets only if
a script data set in included in the shipment. To enable conditional execution, a symbol
represents each script data set. The symbol is based on the last qualifier of the host data set
name, prefixed by the characters ZZ (for example, &ZZSCRIPT for the data set BST.USER12.
SCRIPT). The value of the symbol is the remote staging data set name for the script data set.
Therefore, the script job steps can be conditionally included in the remote job steps based on
the existence of the script data set in the shipment as determined by the resolution of the
data set symbol.
2. The administrator can optionally include symbols unique by destination in the script data set
members. If the administrator chooses to use destination-specific symbols, the administrator
will have created a destination configuration member in the PARMLIB that defines a value for
the symbol that is unique to each destination. During the shipment process, symbols in the
script data set members are substituted with the values from the symbols defined in the
destination configuration member before being written to the host staging data set. The
destinations coded in the configuration member will not be validated as defined destinations.
The member will not be processed until a package shipment is executed, and only then if a
script data set is included in the shipment. Messages will be produced during package ship
indicating that a script data set has been found and whether or not a destination
configuration member is also found and the variables substituted.
3. Your site's script data sets are created by normal processor execution.
4. The script data set has to be identified as such so that the members can have their unresolved
symbols resolved before the members are written to the host staging data set. During the
package shipment process, the script data sets are identified as script data sets through
mapping rules, where the remote data set name is defined as: (SCRIPT-FILES).
Note: Script data sets are always shipped, but are not automatically copied to the remote
target data set, unless a copy step is included in the script job steps through the model control
members.
5. The host staging data set is shipped with all of the other package output data sets.
6. The remote copy job will then be executed, including the additional steps for script execution.
The symbol created to represent the script data set are used by the model control members
and will resolve to the remote staging data set for the script data set. This allows the script
data set to be used as input for the script job steps.
The following graphic shows the package ship process including post-ship script execution:
04-May-2018 778/1109
CA Endevor® SCM - 17.0
post-ship script
CA XCOM
CONNECT:Direct
A destination definition can be created or updated using the Environment Option on the CA Endevor
SCM Primary Options Panel in foreground or using the Define Ship Destination SCL in batch.
XCOM runs a batch job that copies data sets to a remote site and runs the job there. You need to
04-May-2018 779/1109
CA Endevor® SCM - 17.0
XCOM runs a batch job that copies data sets to a remote site and runs the job there. You need to
modify the sample JCL with site-specific information. In addition, the EXEC PARM may require
additional XCOM parameters.
The NDVRSHIP job step (in the Package Ship job skeleton C1BMXJOB) creates a PDS (prfx.XCOMCMD.
FILE) containing a member named CONTROL. The member contains the following commands:
A SEND TYPE=JOB command for each destination receiving a shipment to execute the remote
copy/delete job.
You can find the JCL and the control cards for the staging data set deletion in prfx.XCOMCMD.FILE as
member "destid.D". The job step that executes XCOM (in skeleton C1BMXCOM) uses the CONTROL
member as SYSIN to execute the shipment. After all transmissions are complete prfx.XCOMCMD.FILE
is deleted. The XCOM Transfer Control facility (XTC) dependently synchronizes the file transmissions
and job executions.
CA Endevor® SCM distributes model XCOM control statements in the CSIQOPTN library as members
whose names start with #PSXCOM. In general you do not need to modify these models.
Note: For more information about XCOM, see the CA-XCOM Data Transport for z/OS User
Guide. XCOM is a product of CA.
A JES route card. The route card can be a "/*ROUTE XEQ nodename" (JES2), "//*ROUTE XEQ
nodename" (JES3), or an equivalent. For more information about routing and running jobs at the
remote destination, contact your JES system programmer.
CA Endevor® SCM distributes model JCL in the CSIQOPTN library as members whose names start with
#PSBDT1. In general, you do not need to modify these models.
BDT runs a batch job that copies data sets to a remote site and runs the job there. You need to
modify the sample JCL with site-specific information about BDT.
04-May-2018 780/1109
CA Endevor® SCM - 17.0
Each data set you wish to transmit issues a NETREL for the remote copy/delete job. Each NETREL in
turn decrements a NETHOLD equal to the number of data sets you wish to transmit. When all data
sets have been transmitted, the NETHOLD is satisfied and the remote copy/delete job is released.
CA Endevor® SCM distributes model BDT control statements in the CSIQOPTN library as members
whose names start with #PSBDT2. In general you do not want to modify these models.
Note: For more information about BDT, see your IBM documentation.
Note: For more information about NetView FTP, see your IBM documentation.
The NDVRSHIP jobstep (in skeleton C1BMXJOB) creates an CONNECT:Direct Process File containing a
single process for each CONNECT:Direct destination. The member name of each process is "destid.P".
The member contains the following commands:
A RUN JOB command to delete the host staging data sets for that destination.
04-May-2018 781/1109
CA Endevor® SCM - 17.0
You can find the JCL and control cards for the staging data set deletion in the process file as member
(s) "destid.D". A single member "SUBMIT" contains a CONNECT:Direct SUBMIT command for each of
the process members. The jobstep associated with C1BMXNDM uses the "SUBMIT" member to
execute the shipment. The Process File is deleted after all processes have been submitted.
CA Endevor® SCM distributes model CONNECT:Direct control statements in the CSIQOPTN library as
members whose names start with #PSNWDM. In general you do not want to modify these models.
You can find additional information about CONNECT:Direct in the Product Overview. The Batch
Interface is documented in the CONNECT:Direct User's Guide. Syntax for CONNECT:Direct commands
can be found in the CONNECT:Direct Command Reference.
b. (Optional) Remove the asterisk in column one next to the entry and set the message
severity level to C (caution) or W (warning): ENHOPT MSGSEVERITY_PKMR632=
a. When a user executes a backout or backin action, messages are written to the package
log that indicate the destinations to which package has already been shipped. This
alerts the user to decide whether the package needs to be reshipped.
b. When the user ships a package that has been backed out, the outputs are shipped
according to the backout status of the package.
04-May-2018 782/1109
CA Endevor® SCM - 17.0
Modify the host job statement JCL skeleton (C1BMXHJC) as follows to provide job statement
information about the host site:
The &C1BJC.n statements expands into the JOB STATEMENT INFORMATION currently displayed
on the Package Shipment panel (option 6 on the Package Options Menu). You can also replace
these statements, along with their )SEL and )ENDSEL bookends with a hard-coded job statement.
Substitute a site-specific JES Node Name value for HOSTNAME on the ROUTE statement. This
causes jobs you submit at either site to be routed to the host for execution. This modification
enables you to submit this job statement on both the host and the remote systems.
Enable the JCL to pass security checks by including the USERID and PASSWORD keywords on the
job statement, if your site requires it. You can do this by including these keywords in one of the
&C1BJC.n statements. For example:
&C1BJC2.,USERID=userid,PASSWORD=password
Remove the transmission package DD statements that do not apply (for example, if BDT is not
used, remove C1BMXBDC, C1BMXBDR, and C1BMXBDM).
Modify the remaining model control card data sets using site-specific prefixes and names. The
prefix/qualifier of the CA Endevor® SCM libraries is iprfx.iqual.
Note: The C1BMXJOB job parm contains a reference to system variable of &ZPREFIX, which
04-May-2018 783/1109
CA Endevor® SCM - 17.0
Note: The C1BMXJOB job parm contains a reference to system variable of &ZPREFIX, which
corresponds to a user's TSO Profile Prefix. If users at your site typically set their profile to
NOPREFIX, for example, "TSO PROFILE NOPrefix", you should change this parameter to
&ZUSER or other high-level qualifier. Some of the ship JCL models use this parameter as
the first node of a certain data set allocated during the ship process.
This skeleton imbeds SCMM@LIB for the STEPLIB and CONLIB definitions to run the package
shipment jobs at the host site.
C1BMXRCN-Confirm remote IEBCOPY of remote staging data sets to remote production data sets.
To modify this skeleton, modify the STEPLIB and CONLIB DD statements using a site-specific prefix,
qualifier, and name. The prefix/qualifier of CA Endevor® SCM libraries is iprfx.iqual. If your AUTLIBS or
CONLIBS are in the linklist these two DD statements can be commented out.
The C1BMXRCN Skeleton
Use this skeleton to confirm the copying of the staging data sets to production data sets at the
remote site. It is included in the C1BMXJOB skeleton.
The shipment staging utility reads this skeleton and uses it to build the part of the remote job that
copies staging data sets into their respective production data sets. There are two IEBGENER steps
which write JCL to the internal reader. Only one of these steps executes, based on condition codes.
The job stream that is entered into the internal reader executes at the host and updates the
shipment record.
No modification is necessary for this skeleton. However, you can modify it to give more specific
information about the results of the copy process.
This C1BMXCOM skeleton contains four steps. The &&XXCC data set built by the package shipment
utility contains IEBUPDTE SYSIN used in the two IEBUPDTE steps to populate the prfx.XCOMCMD.FILE
as described in Transmission Method Considerations. XCOM is executed in the third step. The fourth
step deletes the member "CONTROL" from the prfx.XCOMCMD.FILE data set.
04-May-2018 784/1109
CA Endevor® SCM - 17.0
1. Modify the STEPLIB and XCOMCNTL dsnames using a site-specific prefix, qualifier, and name.
The prefix/qualifier of the XCOM libraries is iprfx.XCOM. Contact your in-house XCOM
administrator to find out this information.
Because the JCL generated for BDT through NJE/NJI varies depending upon the number of data sets
you are transmitting, the actual job stream is built by the package shipment utility and written to an
internal reader in this job step.
Note: For more information about the modification of this job stream (C1BMXBD1), see
Creating Model Transmission Control Statements (see page 802).
Use the C1BMXBDT skeleton to transmit staging data sets and run jobs using Bulk Data Transfer,
Version 2. No modification is necessary for this skeleton.
C1BMXNDM JCL for CONNECT Direct
The C1BMXNDM skeleton contains four steps. The &&XNWC data set built by the package shipment
utility contains IEBUPDTE SYSIN used in the two IEBUPDTE steps to populate the prefix.CONNCMD.
FILE. CONNECT:Direct is executed in the third step. The fourth step deletes the member "SUBMIT"
from the prefix.CONNCMD.FILE data set.
1. Modify LINKLIB, NETMAP, and MSG dsnames with site-specific names. The prefix/qualifier of
the CONNECT:Direct libraries is iprfx.ndm.
2. If you need a SIGNON statement, modify the SIGNON statement in the &VNBXSTP job step
using site-specific signon data. You may add additional keywords and CONNECT:Direct control
statements other than signon. For more information, see CONNECT: Direct Control Statements
(see page 806).
3. If you do not need a SIGNON statement, delete the SIGNON and //SYSIN DD * statements in
the &VNBXSTP job stepand code //SYSIN on the CONNCMD.FILE DD statement.
04-May-2018 785/1109
CA Endevor® SCM - 17.0
Note: If most of your users' profiles are set to NOPREFIX, the C1BMXJOB job parm
contains a reference to system variable of &VNBSHHLI, which corresponds to a
user's TSO Profile Prefix. If users at your site typically set their profile to NOPREFIX,
for example, "TSO PROFILE NOPrefix", you should change this parameter to &ZUSER
or other high-level qualifier. Some of the ship JCL models use this parameter as the
first node of a certain data sets allocated during the ship CONNCMD.
Use the C1BMXLOC skeleton to transfer host staging data sets that exist on shared DASD to
production data sets which may or may not exist on shared DASD. The job executes a submit
command for the remote copy/delete job using batch TSO.
Because the Netview FTP JCL varies depending upon the number of data sets you are transmitting,
the actual job stream is built by the package shipment utility and written to an internal reader in this
job step. The tailoring of the C1BMXFTP job stream is discussed in Creating Model Transmission
Control Statements (see page 802).
There is no third job step for BDT via NJE/NJI and Netview FTP. However, this skeleton is read by the
first job step (DD name C1BMXHCN) and becomes part of the JCL stream which is written to the
internal reader in the second job step.
To modify the C1BMXHCN skeleton, insure that the condition code on the CONFEXEC step matches
the condition code in the preceding file transmission step. This skeleton can be modified to give more
specific information about the results of the file transmission step.
04-May-2018 786/1109
CA Endevor® SCM - 17.0
These skeletons are members in the CSIQSENU library and the model members are found in the
CSIQOPTN library.
RJCLROOT
Specifies the member root for the package ship remote JCL model. Controls the choice of remote
JCL generation. There are three choices:
Note: The option to tailor the remote command stream, or execute Post-Ship Script
processing is ONLY enabled using either RJCLROOT=ICPY or RJCLROOT=FCPY. If RJCLROOT
is not specified (or omitted) these options are not available. See How to Tailor the
Command Stream and Enable Post-Ship Script Execution later, for details
If RJCLROOT is not specified, the three-step job stream is programmatically generated using IEBCOPY
and IDCAMS and the #PSxxxx model control members, where xxxx is specific to the transmission
method.
This JCL copies staging data sets to their production counterparts. This job step member is read
/written at the host site by the shipment staging utility and is executed at the remote site. The
member is C1BMXCOP and is distributed in the CSIQSENU library.
Note: This is not an ISPF skeleton. All skeleton control statements (close parenthesis in column 1) are
ignored.
The utility-generated copy control cards are in IEBCOPY format. COPY and COPYMOD commands
are used. No SELECT MEMBER statements are generated.
This JCL deletes production members and remote staging data sets at the remote site. This member is
read/written at the host site by the shipment staging utility and is executed at the remote site. The
member is C1BMXDEL and is distributed in the CSIQSENU library.
04-May-2018 787/1109
CA Endevor® SCM - 17.0
Note: This is not an ISPF skeleton. All skeleton control statements (close parenthesis in column 1) are
ignored.
Remote confirmation steps are discussed in Host Job Step 1: Shipment Staging (C1BMXJOB), in the
C1BMXRCN subsection.
Remote Job RJCLROOT=FCPY
If RJCLROOT is equal (=) to FCPY, the job stream is generated through the set of model members
beginning with the character string #RJFCPY. The distribution version consists of the following three
steps:
For more information about the remote confirmation steps, see Host Job Step 1: Shipment Staging
(C1BMXJOB).
Remote Job RJCLROOT=ICPY
If RJCLROOT is equal (=) to ICPY, the job stream is generated through the set of model members in
the CSIQOPTN library beginning with the character string #RJICPY. The distributed version generates
the same job stream that is generated when RJCLROOT is omitted. The job stream consists of three
steps:
Remote Job Step 1: Execute IEBCOPY to copy members to remote data sets
Remote Job Step 2: Execute IDCAMS to delete members and staging data sets
For more information about the remote confirmation steps, see Host Job Step 1: Shipment Staging
(C1BMXJOB).
BPXBATCH Remote Job Step for USS Objects
If a package shipment contains any USS objects, then an extra step (BPX) is inserted into the remote
copy jobs to perform the required un-archive and copy commands. As delivered, the remote
commands perform the following:
04-May-2018 788/1109
CA Endevor® SCM - 17.0
Note: If an error is encountered, a return code 256 is set and this can be tested in the
confirmation steps. For more information, see How to Build, Track and Confirm
Shipments.
set -x
Enables echoing of the commands, prefixed with a plus ('+') to the STDERR output DD which
makes it easier to diagnose any problems.
mkdir -p '<remoteStaginPath>'
Creates a target staging directory if it doesn't already exist.
rm -fv '<targetFile>'
Builds a corresponding delete request, for each copy, before the copy is performed. This
command ensures that time stamp information is preserved in the following copy command.
Note: The remote copy and delete command pairs will repeat for as many USS objects as
need to be managed.
You can tailor the command stream to your site standards, by inserting a step to tailor the file at the
remote location. For example, you can insert mkdir, chown, or chgroup commands or modify the
delivered un-pax command switches.
1. Select a model for the remote JCL. The RJCLROOT parameter in the Defaults table (C1DEFLTS)
determines which custom set of models is in use at your site.
If your value is FCPY, or ICPY, note the value and continue to the next step.
If RJCLROOT is omitted or blank, then edit the C1DEFLTS to specify RJCLROOT=ICPY and
reassemble the table.
04-May-2018 789/1109
CA Endevor® SCM - 17.0
For more information about RJCLROOT, see Specifying Remote Job Stream in
C1DEFLTS (see page 787). For more information about the Defaults table, see
Defaults Table (https://docops.ca.com/display/CE17/Defaults+Table).
If your Defaults table specifies RJCLROOT=FCPY, use this model member: #RJFCPY1
If your Defaults table specifies RJCLROOT=ICPY use this model member: #RJICPY1
b. Locate the BPXBATCH step in your model member. This step executes the command
stream. A sample BPXBATCH step for #RJICPY1 is shown next:
//*
//BPXBAT EXEC PGM=BPXBATCH ICPY
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//STDPARM DD DISP=SHR,
// DSN=&RUCD
DSN=&RUCD
Resolves the name of the remote command file.
c. Insert steps before the BPXBATCH step to invoke your modification code according to
your needs.
Suppose that you want to have a REXX program read in the current command stream from SYSUT1
and then write the customized stream to SYSUT2. To accomplish this result, you would insert the
following code before the BPXBATCH step in your model member:
//***********************************************************
//* SAMPLE TAILOR UCD COMMAND STREAM
//***********************************************************
//UCDEDIT EXEC PGM=IRXJCL,PARM='UCDEDIT'
//SYSEXEC DD DISP=SHR,DSN=BST.SUPPNDVR.ISRCLIB
//SYSUT1 DD DISP=SHR,DSN=&RUCD
//SYSUT2 DD DISP=SHR,DSN=&RUCD
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//***********************************************************
The following sample REXX exit (UCDEDIT) illustrates the key requirements of your command stream
tailoring. The program must read in the existing command stream and write out the tailored stream.
The program reads the input from SUSYT1 and writes the tailored output to SYSUT2. This exit
performs a simple string search and replace to amend (insert) an extra switch in the pax command.
/* Rexx to read from Sysut1 and write to Sysut2 (like IEBGENER)
However, this version is a bit special in that it also performs
some string substitutions. It's intended to allow a customer
to edit their USS Ship command stream at the remote location
changing the pax command parms or saving some commands to be
executed later. */
04-May-2018 790/1109
CA Endevor® SCM - 17.0
frmstr = 'pax -rvzk' /* This is what we're looking for */
tgtstr = 'pax -rvzk -p op' /* and we'll replace it with this */
/* Read input file (BPXBATCH commands) */
"EXECIO * DISKR SYSUT1(STEM DATA. FINIS"
IF RC ¬= 0 THEN SIGNAL IOERROR
/* Main loop to search/replace the string */
do i = 1 to DATA.0
start = 1
do while start < length(DATA.i)
found = pos(frmstr,DATA.i,start)
if found = 0 then leave
endstr = found + length(frmstr)
newstr = Left(DATA.i,(found - 1)) || tgtstr
DATA.i = newstr || substr(DATA.i,endstr)
start = found + length(tgtstr)
end
end
/* Write the substituted file out */
"EXECIO * DISKW SYSUT2(STEM DATA. FINIS"
IF RC ¬= 0 THEN SIGNAL IOERROR
/* That's it all done */
Exit 0
IOERROR:
SAY 'PROBLEM DURING I/O, Return code:' || RC
EXIT RC
Create a Destination
You must define at least one destination for each remote site to which you plan to ship package
outputs. CA Endevor® SCM stores destination information in the package data set. Destinations can
be defined for data sets or the USS supported file types HFS, zFS, or NFS.
2. Select option D- Destination on the Environment Options Menu. Then press Enter.
The Destination Options Menu opens.
3. Select 2-Build. Type a fully qualified destination name in the Destination field. Press Enter.
A Create/Modify Destination panel opens.
4. Complete the information on the panel. Then press Enter. This panel includes the following
fields:
DESTINATION
Specifies a data set name or a USS supported path and file name.
For a data set name, the value can be a maximum of seven characters. The first
character must be alphabetic. Remaining characters can be alphabetic or national.
For a USS system file, the value can be up to a 732-byte path name.
04-May-2018 791/1109
CA Endevor® SCM - 17.0
DESCRIPTION
Specifies a maximum 30-character description for the destination, which is treated as a
comment.
TRANSMISSION METHOD
Specifies the transmission utility for this destination. Acceptable values are as follows:
L -- Local
NWD -- CONNECT:Direct
REMOTE NODENAME
Specifies a 1-to 16-character nodename to which package outputs are to be shipped. The
name must be valid for, and defined, to the chosen data transmission program.
Nodename has no meaning for BDT via NJE/NJI and for local transmissions.
REMOTE IPNAME/IPPORT
Specifies the XCOM SERVPORT specification of the target server to which package outputs
are to be shipped. IPname can be 1 to 63 characters. IPPORT can be 1 to 5 characters and
range from 1 to 65535. The IPNAME and IPPORT specification is only valid for the XCOM
transmission method.
Note: For XCOM, you must specify either the IPNAME/IPPORT or the NODENAME,
but not both.
04-May-2018 792/1109
CA Endevor® SCM - 17.0
Disposition
Delete or keep. When DISPOSITION=DELETE, CA Endevor® SCM includes a step in the
host and/or remote JCL streams to delete the staging data sets after they have been
processed. Acceptable values are:
D -- Default. Delete staging data sets
K -- Keep staging data sets
All staging data sets are initially cataloged. Keep/Delete refers to the final disposition
of:
- Host staging data sets after they have been transmitted.
- Remote staging data sets once they have been copied to their production
counterparts.
Unit
Specifies the unit designation to be used when allocating staging data sets. Default is
SYSDA.
Modify a Destination
You can modify a destination that has already been created.
1. Select option D (DESTINATIONS) on the Environment Options Menu. Then press Enter.
04-May-2018 793/1109
CA Endevor® SCM - 17.0
1. Select option D (DESTINATIONS) on the Environment Options Menu. Then press Enter.
The Destination Options Menu opens.
2. Select 2-Build. Type a fully qualified destination name in the Destination field. Press Enter.
A Create/Modify Destination panel opens. The CREATED and UPDATED fields show the date
and time when the destination was created and last updated, and the user ID associated with
each activity.
Note: If you left the destination name blank or use name masking, a selection list opens. Then
you can select a destination to modify from the list.
Display a Destination
You can display information for a destination that has already been defined.
1. Select option D (DESTINATIONS) on the Environment Options Menu. Then press Enter.
The Destination Options Menu opens.
2. Select 1-Display. Type a fully qualified destination name in the Destination field. Press Enter.
Note: If you leave the Destination field blank or use a name mask, a selection list
opens. Then you must select a destination from the selection list. The Display
Destination panel opens for the destination you specified.
Delete a Destination
You can delete a destination and any associated mapping rules that have already been created.
1. Select option D (DESTINATIONS) on the Environment Options Menu. Then press Enter.
The Destination Options Menu opens.
2. Select 3-Delete on the Destination Options panel. Type a fully qualified destination name in
the Destination field. Press Enter.
Note: If you leave the Destination field blank or use a name mask, a selection list
opens. Then you must select a destination from the selection list.
The Delete Destination panel opens for the destination you specified.
04-May-2018 794/1109
CA Endevor® SCM - 17.0
Note: To delete multiple destinations, select the destinations you want to delete on a
Destination Selection List. When you press enter, a Delete Destination panel appears for
the first selected destination. After you delete that destination, press END key. The Delete
Destination panel remains displayed, with the name of the second selected destination in
the DESTINATION ID field. Repeat the delete procedure for this and subsequent selected
destinations.
Mapping Rules
When you create each destination, you define the staging data sets or USS directories that are built
for each ship request to that destination. You must also create one or more mapping rules for each
destination. A mapping rule maps production data sets or USS directories at the host to
corresponding production data sets or USS directories at the remote site as follows:
A data set mapping rule is a relationship between a host data set name or mask and a remote
data set name or mask. Both the host and remote data set name or mask can be 1 - 44 characters
in length.
A USS mapping rule is a relationship between a host path name or mask and a remote path name
or mask. Both the host and remote path name or mask can be up to 768 characters in length.
In order to match a mapping rule, CA Endevor® SCM first checks that the number of qualifiers or
sub-directories match. This means that the host data set name in the mapping rule must have the
same number of qualifiers (separated by '.') as the input production names. For USS path names,
the host path name must have the same number of sub-directories (separated by '/')as the input
production path name.
We recommend that the host names and their corresponding remote names in the mapping rule
have the same number of qualifiers. This format makes the rules easier to understand and
administer.
Note: Matching begins with the highest to the lowest level qualifier. Therefore, a data set
named testap.program.loadlib.clone would map to testap.program.*.* if the mapping rule
options were as follows:
testap.program.*.*
Testap.*.loadlib.clone
For example, the following host data set names should be mapped to the following remote
data set names:
Host data set name mask Remote data set name mask
04-May-2018 795/1109
CA Endevor® SCM - 17.0
HOST.*.LOADLIB REMOTE.*.LOADLIB
HOST.*.*.* REMOTE.*.*.*
For example, the following host path name masks should be mapped to the following remote names:
The remote data set name fields in the mapping rules can have any number of qualifiers. If the
number of qualifiers is not the same, then generally both data set names align to the right before
building a new data set name.
For example, assume this mapping rule where the remote data set has more qualifiers than
the host:
Host data set name mask Remote data set name mask
TESTAP.*.* PROD.AP.*.*
This mapping rule would result in the following remote data set being built for the following host:
For example, assume this mapping rule, where the host data set has more qualifiers than the remote:
Host data set name mask Remote data set name mask
TESTAP.*.* PROD.*
This mapping rule would result in the following remote data set being built for the following host:
If the target has more nodes than the host, and the host and target start with the same explicitly
defined node, but do not end with the same explicitly defined node, then the data set names
align to the left.
For example, assume this mapping rule, where the remote data set has more qualifiers than
the host:
Host data set name mask Remote data set name mask
PRODAP.*.* PRODAP.*.*.REMOTE1
This mapping rule would result in the following remote data set being built for the following host:
04-May-2018 796/1109
CA Endevor® SCM - 17.0
For example, assume this mapping rule, where the remote USS path has more qualifiers than the
host:
This mapping rule would result in the following remote data set being built for the following host:
An exception to the alignment rules occurs when both the host mask and the remote mask
contain no wildcards. In this case, the remote mask becomes the remote data set name or path.
When executing a shipment request, each input data set is compared to its list of data set
mapping rules until the most specific match is found. For example, the input data set TESTAP.
PROGRAM.LOADLIB matches the following three host masks. The first mask, TESTAP.*.LOADLIB, is
the most specific and is the one that would be used.
If the remote mask is null, data sets matching the host mask are excluded from the package
shipment. This behavior is useful, for example, when only load modules are shipped. This
behavior enables you to set up rules to prevent the shipment of source, listings, object modules,
and so on.
If no matching rule exists, then the remote data set defaults to the same name as the input data
set when executing a shipment request. If your site does not require any name changes, then all
you need is a single dummy mapping rule, which causes every data set to map to itself. A dummy
mapping rule is a mapping rule that does not include a definition for the remote data set.
Important: If you are using a dummy mapping rule with the local shipment method, the target
and source file would be the same physical data set or path. This default behavior can cause
results that had not been considered during the initial planning. For example, if a new file with a
USS path name has one extra node than the input masks, the data set would map to itself.
Note: The Shipment Activity Report created at run time lists the remote data set name for
each host data set, with the mapping rule that was used to generate it. A DSN cross
reference data set is also shipped to the remote site.
04-May-2018 797/1109
CA Endevor® SCM - 17.0
2. Select option D (DESTINATIONS) on the Environment Options Menu. Then press Enter.
The Destination Options Menu opens.
3. Select 2 on the Destination Options panel. Type a fully qualified destination name in the
Destination field. Press Enter.
A Create/Modify Destination panel opens.
C
Create a DSN mapping rule.
CU
Create a USS mapping rule.
A Create DSN Mapping Rule panel or a Create USS Mapping Rule panel opens, depending on
the option you selected.
Remote data set name or mask for this mapping rule. To exclude data sets from being
transmitted, leave this field blank.
For script data sets, which are used for the Post-ship Script feature, specify the keyword
exactly as shown next: (SCRIPT-FILES). The parentheses, which must be included and the dash
are not valid characters for a data set name, so this value cannot be mistaken for one.
04-May-2018 798/1109
CA Endevor® SCM - 17.0
This field contains an approximation of the number of members that one cylinder might
contain for data sets that map to this rule. The default is 16.
When packages are staged for shipment, CA Endevor® SCM divides this value into the actual
number of members that are being staged. Then CA Endevor® SCM allocates the result +1
cylinder of primary and secondary space for the staging data sets.
Fields on the Create USS Mapping Rule panel:
Specifies a 1- to 768- character name or mask for a path at a remote site. All path names will
be prefixed and appended with a forward slash (/). If you do not want USS package outputs in
a host path to be transmitted, leave the remote path name blank. Remote path names can
have up to 128 directories. To make the rules easier to understand and administer, we
recommend that the host names and their corresponding remote names have the same
number of qualifiers.Make sure to test your mapping rules using the Test Mapping Rules
utility. For more information about testing mapping rules, see Test a Mapping Rule (see page
801).
Note: For more information about mapping host and remote locations, see
Mapping Rules (see page 795).
1. Select option D (DESTINATIONS) on the Environment Options Menu. Then press Enter.
The Destination Options Menu opens.
2. Select 1 on the Destination Options panel. Type a fully qualified destination name in the
Destination field. Press Enter.
Note: If you leave the Destination field blank or use a name mask, a selection list
04-May-2018 799/1109
2.
Note: If you leave the Destination field blank or use a name mask, a selection list
opens. Then you must select a destination from the selection list. The Display
Destination panel opens for the destination you specified.
Note: To return to the Delete Destination panel, press End twice.
3. Select one of the following display options in the Option field on the Display Destination
panel. The option you select depends on the file type that ships to the destination shown on
this panel.
D
Displays the DSN mapping rules for the destination.
DU
Displays the USS mapping rules for the destination.
The DSN Mapping Selection List panel or the USS Mapping Selection List panel opens,
depending on which option you specified. The panel lists the mapping rules for the
destination you specified.
4. Select the mapping rule you want to display from the selection list.
The Display DSN Mapping Rule panel or the Display USS Mapping Rule panel opens displaying
information about the mapping rule you selected from the selection list.
The Display DSN Mapping Rule panel displays the Host Dataset Name and the Remote
Dataset Name to which it maps.
The Display USS Mapping Rule panel displays the Host Path Name and the Remote Path
Name to which it maps.
1. Select option D (DESTINATIONS) on the Environment Options Menu. Then press Enter.
The Destination Options Menu opens.
2. Select 2 on the Destination Options panel. Type a fully qualified destination name in the
Destination field. Press Enter.
A Create/Modify Destination panel opens.
D
Display a DSN mapping rule for update.
DU
Display a USS mapping rule for update.
The DSN Mapping Selection List panel or the USS Mapping Selection List panel opens,
04-May-2018 800/1109
CA Endevor® SCM - 17.0
The DSN Mapping Selection List panel or the USS Mapping Selection List panel opens,
depending on which option you specified. The panel lists the mapping rules for the
destination you specified.
4. Select the mapping rule you want to modify from the selection list.
The Display DSN Mapping Rule panel or the Display USS Mapping Rule panel opens displaying
information about the mapping rule you selected from the selection list.
The Display DSN Mapping Rule panel displays the Host Dataset Name and the Remote
Dataset Name to which it maps.
The Display USS Mapping Rule panel displays the Host Path Name and the Remote Path
Name to which it maps.
Note: Press the End key until you reach the panel you need to perform your next
action.
Note: The DSN Mapping Selection List and the USS Mapping Selection List are ordered from
the most specific to the least specific rule. If you change the host mask when modifying a rule,
the rule is marked *RE-KEYED. This may mean that the rule has changed its relative position in
the list. Redisplay the list to find the new position of the rule.
1. Select option D (DESTINATIONS) on the Environment Options Menu. Then press Enter.
The Destination Options Menu opens.
2. Select 2 on the Destination Options panel. Type a fully qualified destination name in the
Destination field. Press Enter.
A Create/Modify Destination panel opens.
T
Test a DSN mapping rule.
TU
Test a USS mapping rule.
04-May-2018 801/1109
CA Endevor® SCM - 17.0
A Test DSN Mapping Rule panel or a Test USS Mapping Rule panel for the destination opens,
depending on the option you selected.
The mapping rules for this destination are searched and the remote name that
corresponds to the specified host is generated and displayed on this panel. The
mapping rule used to match the host to the remote location is also displayed.
When a remote site needs a different set of commands, make a copy of the #PSXCOMx member,
naming it "destid.x" and make the changes. Only the members suffixed by an alpha character can be
prefixed with user members, not members suffixed by a numeric character. The search order for
members is "destid.x", #PSXCOMx, #PSNDVRx.
Note: For information about XCOM commands, see the XCOM User's Manual.
The XCOM control statement models in the CSIQOPTN library are described next. Modify these
models as appropriate for your site.
#PSXCOME
Contains the XCOM commands to execute the remote copy/delete job and delete the host
staging data sets. To prevent automatic execution at all remote sites, place an @EOF as the first
statement of this member. To prevent this from happening at a particular site, create a member
"destid.E" with an @EOF as the first statement.
#PSXCOMP
Contains the XCOM commands to transmit a Partitioned Data Set
#PSXCOMS
Contains the XCOM commands to transmit a Sequential Data Set
#PSXCOMT
04-May-2018 802/1109
CA Endevor® SCM - 17.0
#PSXCOMT
Contains cleanup steps to delete prfx.XCOMCMD.FILE when all destinations have been processed.
This member becomes the last two job steps in prfx.XCOMCMD.FILE(destid.D).
1. Unloads the partitioned staging data sets to temporary sequential data sets.
3. Optionally deletes host staging data sets via the JCL DISP parameter.
3. Submits the job to copy members into the production data sets.
Those #PSBDT1 members ending in a letter contain JCL segments which may have to be modified
with site-specific data. BDT via NJE/NJI also uses a set of members whose names begin with
#PSNDVR. In cases where the needs of a remote site differ, make a copy of the #PSBDT1x or
#PSNDVRx member, name it "destid.x" and make the changes. Only the members suffixed by an
alpha character can be prefixed with user members, not members suffixed by a numeric character.
The search order for members is "destid.x," #PSBDT1x, #PSNDVRx.
The BDT control statement models in the CSIQOPTN library are described next. Modify these models
as appropriate for your site.
#PSBDT1E
This job step is transmitted to the remote site and is executed there after the data sets are
received (as sequential files) and restaged into partitioned data sets. To prevent automatic
execution at all remote sites, place an @EOF as the first statement of this member. To prevent
this from happening at a particular site, create a member "destid.E" with an @EOF as the first
statement.
#PSBDT1J
This job step is executed at the host site after the partitioned staging data sets have been
unloaded into sequential data sets.
#PSBDT1W
This job step is executed at the remote site.
#PSNDVRH
This job step is executed at the host site and unloads the partitioned staging data sets into
temporary sequential data sets prior to transmission.
04-May-2018 803/1109
CA Endevor® SCM - 17.0
#PSNDVRR
This job step is executed at the remote site and restages the received sequential data sets into
temporary partitioned data sets. This control statement is set up to use the same JCL as that
executed on the host. If different JCL is required, replace the @INCLUDE=H statement with the
appropriate JCL.
When a remote site needs a different set of commands, make a copy of the #PSBDT2x member,
naming it "destid.x" and make the changes. Only the members suffixed by an alpha character can be
prefixed with user members, not members suffixed by a numeric character. The search order for
members is "destid.x", #PSBDT2x, #PSNDVRx.
Note: For more information about BDT commands, see the BDT Version 2 File-to-File
Transaction Guide.
The BDT Version 2 control statement model in the CSIQOPTN library is described next. Modify this
model as appropriate for your site.
#PSBDT2E
This member contains the BDT Version 2 command to execute the remote copy/delete job. To
prevent automatic execution at all remote sites, place an @EOF as the first statement of this
member. To prevent this from happening at a particular site, create a member "destid.E" with an
@EOF as the first statement.
CA Endevor® SCM distributes Local control statements in the CSIQOPTN library as a set of members
whose names begin with "#PSLOCL." In cases where the needs of a remote site differ, make a copy of
the #PSLOCLx member, naming it "destid.x" and make the changes. Only the members suffixed by an
alpha character can be prefixed with user members, not members suffixed by a numeric character.
The search order for members is "destid.x," #PSLOCLx, #PSNDVRx.
The Local control statement model in the CSIQOPTN library is described next. Modify this model as
appropriate for your site.
#PSLOCLE
This job step submits the copy/delete job for execution via TSO. To prevent automatic
submission, place an @EOF as the first statement of this member. To prevent this from
happening for a particular site, create a member "destid.E" with an @EOF as the first statement.
04-May-2018 804/1109
CA Endevor® SCM - 17.0
1. Executes FTP to transmit a data set to the remote site (multiple job steps).
2. Submits the job to copy members into the production data sets.
3. Deletes the host staging data sets (optional, based on the Destination Definition).
#PSNFTP members ending in a letter contain the FTP JCL and command models and may have to be
modified with site-specific data or features desired by the user. NetView FTP also uses a set of
members whose names begin with #PSNDVR. In cases where the needs of a remote site differ, make
a copy of the #PSNFTPx member, name it "destid.x" and make the changes. Only the members
suffixed by an alpha character can be prefixed with user members, not members suffixed by a
numeric character. The search order for members is "destid.x," #PSNFTPx, #PSNDVRx.
In the job stream described previously, the SUBMIT step cannot execute before the actual
transmission of the data sets. This can be accomplished in one of two ways. The transmit commands
can specify WAIT=YES, or the SUBMIT command of the second step can specify HOLD and be
manually released.
Note: For information about FTP commands, see the appropriate NetView FTP Manual.
The NETVIEW FTP control statement models in the CSIQOPTN library are described next.
Modify these models as appropriate for your site.
#PSNFTPE
This job step submits the copy/delete job for execution via TSO. To prevent automatic
submission, place an @EOF as the first statement of this member. To prevent this from
happening for a particular site, create a member "destid.E" with an @EOF as the first statement.
#PSNFTPJ
This job step is executed at the host site to transmit a data set.
#PSNFTPP
This member contains the FTP command which transmits a partitioned data set to the remote
site. The WAIT=YES is necessary to prevent the premature execution of the "SUBMIT COPY
/DELETE" step generated by #PSNFTPE.
#PSNFTPS
This member contains the FTP command which will transmit a sequential data set to the remote
site. The data set name to be transmitted is located in member #PSNFTP6. The WAIT=YES is
necessary to prevent the premature execution of the "submit copy/delete" step generated by
#PSNFTPE.
04-May-2018 805/1109
CA Endevor® SCM - 17.0
#PSNDVRD
This job step deletes the host staging data sets if "DELETE" was specified as the Host Staging Data
set Disposition.
Note: For more information about establishing destinations, see How to Establish
Destinations.
When a remote site needs a different set of commands, make a copy of the #PSNWDMx member,
name it "destid.x" and make the changes. Only the members suffixed by an alpha character can be
prefixed with user members, not members suffixed by a numeric character. The search order for
members is "destid.x", #PSNWDMx, #PSNDVRx.
The CONNECT:Direct control statement models in the CSIQOPTN library are described next.
Modify these models as appropriate for your site.
#PSNWDMB
Contains the CONNECT:Direct Submit Statement.
#PSNWDMC
Contains the Process Statement.
#PSNWDME
Contains the CONNECT:Direct command to execute the remote copy/delete job. To prevent
automatic execution at all remote sites, place an @EOF as the first statement of this member. To
prevent this from happening at a particular site, create a member "destid.E" with an @EOF as the
first statement.
#PSNWDMP
Contains the statements to transmit a Partitioned Data Set.
#PSNWDMS
Contains the statements to transmit Sequential Data Sets.
04-May-2018 806/1109
CA Endevor® SCM - 17.0
#PSNWDMT
Contains cleanup steps to delete prfx.CONNCMD.FILE when all destinations have been processed.
It becomes the last two job steps in prfx.CONNCMD.FILE(destid.D).
2. On the Package Shipment panel, code TYPRUN=COPY in the HOST JOB STATEMENT
INFORMATION field. Insure that the MSGCLASS points to a HELD queue.
3. Submit the shipment queue by typing 3 in the OPTION field on the Package Shipment panel.
TSO displays a IKJ56250I message. Copy the jobname and job number the message displays. If
no message displays, use SDSF to obtain the job name and job number.
4. Return to the Package Shipment panel and remove the TYPRUN=COPY from the HOST JOB
STATEMENT INFORMATION field and restore the MSGCLASS to its original state.
The Package Shipment JCL Stream, including all in-stream data, now resides on the JES queue.
1. Move the JES Queue to a sequential data set or to a member of a PDS. If the data set that is to
contain the JCL stream does not exist, allocate it with a RECFM of "F" or "FB" and an LRECL of
80.
2. Issue the following command from the TSO READY prompt or the ISPF TSO Command Panel
using the jobname and number from Step 1.
OUTPUT jobname (jobnumber) PRINT ('data set')
TSO displays "OUTPUT" to indicate that the JCL stream now resides in the specified data set.
Press End.
04-May-2018 807/1109
CA Endevor® SCM - 17.0
d. Ensure that the first statement in the file is the JOB statement and the last is the
expansion of the ISPSLIB(C1BMXEOJ) skeleton.
e. Modify the date and time components in all parameter cards to match the intended
execution date and time, if necessary. These data and time fields are used to generate
unique data set names and to ensure that confirmation messages are sent back for the
appropriate shipment. They do not imply any scheduling restrictions. For example, in
the following code, YYYYMMDD is a valid date in year, month, and date format.
HHMMSSTT is a valid time (including hundredths of seconds):
PARM='C1BMX000,YYYYMMDD,HHMMSSTT,….
f. Tailor all the temporary data set names (in the format <prefix>.D<yymmdd>.
T<hhmmss>.*) to match the date and time used in the parameter cards in the prior
step. Due to limitations of the node length, a shorter version of the date and time is
used. The century is omitted from the date and the hundredths of seconds from the
time.
Note: For more information about package shipment SCL, see Using Package Shipment SCL.
Leaving it as an in-stream data set and modifying the SCL that follows it prior to each run.
Changing the C1BMXIN DD statement from an in-stream data set to a sequential data set or PDS
member (RECFM=F or FB,LRECL=80) into which you can store the SCL until each run.
Using SCL generators to precede the NDVRSHIP step and populate a temporary data set with SCL
that will be passed through C1BMXIN.
04-May-2018 808/1109
CA Endevor® SCM - 17.0
As a CA Endevor® SCM administrator, you can enable the Post-Ship Script feature to facilitate the
conditional execution of custom job steps, called scripts, at a remote destination before or after the
package shipment process has completed.
The following graphic shows how you enable the Post-Ship Script feature:
1. Configure your C1DEFLTS table (see page 810). This involves reviewing your C1DEFLTS table
and updating the table if necessary.
2. Update your Generate or Move Processors (see page 810) to add steps that build scripts.
3. Define mapping rules for the data sets that contain your script files (see page 811). For script
data sets, you define the mapping rule's remote destination as: (SCRIPT-FILE).
4.
04-May-2018 809/1109
CA Endevor® SCM - 17.0
1. Review your C1DEFLTS table to confirm that your RJCLROOT parameter is set to either ICPY or
FCPY. If this option was omitted, insert it with a value of RJCLROOT=ICPY. For more
information on the RJCLROOT parameter, see Remote Job Stream (C1DEFLTS).
2. (Optional) Update your C1DEFLTS table as follows, if you plan to use destination script
symbols:
a. Define the name of your Destination Configuration member to C1DEFLTS, using the
DESTCFGMBR= parameter. If no value is specified, the value defaults to null.
b. Review your C1DEFLTS table to confirm that you have a valid PARMLIB dataset.
1. Update your generate or move processors to insert any additional steps needed to build the
required remote script syntax based on your site's requirements.
2. Verify that MONITOR and BACKOUT keywords are specified on the script data set so that
package processing can create backout records to track your script files.
Name your script data set so that it is easy to determine its content. The final qualifier of the script
data set will be used when building model control statements. So consider choosing an appropriate
name so the different types of script processing can be determined. For example, an appropriate
name might be CICSNEWC for CICS Phasin requests or DB2BIND for DB2 bind requests. Any
destination specific symbols that you want to be substituted at shipment must be present in the
script file created by the processor.
Example: Create CICS New Copy Script for Post-Ship Script Execution
The following code sample will create CICS phase-in requests when the processor is executed in a
package. The &CICSREGN symbol in this example will be substituted at ship time.
//***************************************************************
04-May-2018 810/1109
CA Endevor® SCM - 17.0
//***************************************************************
//* CREATE CICS NEW COPY SCRIPT
//***************************************************************
//PKGCHK IF &C1PKGID NE "" THEN * ONLY IF PACKAGE EXEC
//SCRIPCP EXEC PGM=IEBGENER,MAXRC=0
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT2 DD DISP=SHR,MONITOR=&MONITOR,FOOTPRNT=CREATE,
// DSN=&DSPREFIX.CICSNEWC
(&C1ELEMENT)
//SYSUT1 DD DATA,DLM=##
/*VS,'F &CICSREGN,CEMT SET PRO(&C1ELEMENT),PHASEIN'
##
//PKGCHKX ENDIF
1. Specify the Host Dataset Name field masks to match the script data set name.
2. Specify the Remote Dataset Name field value using the keyword exactly as shown next:
(SCRIPT-FILES)
The parentheses, which must be included and the dash are not valid characters for a data set
name, so this value cannot be mistaken for one.
Note: For more information about defining mapping rules, see Create a Mapping Rule (see
page 798).
To create a mapping rule for a script data set with a final qualifier of CICSNEWC, define the Host
Dataset Name and the Remote Dataset Name as shown next.
HOST DATASET NAME ===> *.*.*.CICSNEWC
maps to
REMOTE DATASET NAME ===> (SCRIPT-FILE)
Note: This example creates a mapping rule for the CICS new copy script created in the example
shown in Update Processors for Post-Ship Script (see page 810).
Note: On the DSN Mapping Selection List, SCRIPT appears in the Status column when a
script file is identified by a mapping rule.
04-May-2018 811/1109
CA Endevor® SCM - 17.0
execution time to create symbols unique to a destination that can be used in script data set members
to resolve symbols for the target destination. These symbols must have been created in the script
dataset members by your processors in order for the substitution to take place correctly.
1. Create a Destination Configuration file to define symbol names and values unique to each
package ship destination.
Use the following syntax to define the symbol names and values for each destination:
>>-- DESTination 'destid' --------------------------->
+<----<----<----<----<----<----<----<----<----<---+
--+--> SYMbol 'symbol-name' VALue 'symbol-value' -- - ->
---> . ---------------------------------------------><
This statement can be repeated for each destination and the SYMBOL and VALUE combination
can be defined as many times as necessary within each statement. If SYMBOL is coded (there
must be at least one) then VALUE must also be coded. To code a null value for a symbol, use
two consecutive single quotes after the VALUE keyword.
3. Include the symbols in your script data set members as appropriate to represent information
that will vary by destination.
Important: Symbol substitution can cause syntax errors by causing line overflows.
Consider the maximum length of your symbols, use symbol substringing to generate
appropriate syntax, or both. For more information on Symbol substring syntax, see the
Extended Processors Guide. Alternatively, if for example you need to substitute long symbols
such as path or file names, consider using a variable blocked (RECFM=VB) script file.
Note: The content of the Destination Configuration member can be viewed from the Display Options
menu and any syntax errors can be reviewed there. The name of the Destination Configuration
member is displayed in the Parameter Library Information section of the Site Information from
C1DEFLTS panel. On the DSN Mapping Selection List, SCRIPT appears in the Status column when a
script file is identified by a mapping rule. Script Execution status can be returned and displayed in the
'Shipment Status' view by scrolling right.
This example of a Destination Configuration file defines different values for the symbol CICSREGN
depending on the target destination.
DESTINATION CA31XCM
SYMBOL 'CICSREGN' VALUE 'CICS31DN'
SYMBOL 'DB2SYS' VALUE 'DBS31DN' .
DESTINATION CA11LOC
SYMBOL 'CICSREGN' VALUE 'CICS11PR'
SYMBOL 'DB2SYS' VALUE 'DB2S11DN' .
Note: This example creates a CICSREGN symbol for the CICS new copy script created in the example
04-May-2018 812/1109
CA Endevor® SCM - 17.0
Note: This example creates a CICSREGN symbol for the CICS new copy script created in the example
shown in Update Processors for Post-Ship Script (see page 810).
To enable conditional execution, a symbol represents each script data set. The symbol is based on the
last qualifier of the host data set name, prefixed by the characters ZZ (for example, &ZZCICSNEWC for
the data set BST.USER12.CICSNEWC. The value of the symbol will be the remote staging data set
name for the script data set.
The symbols can be checked in the package ship model control members through @IF and @IFNOT
statements. Therefore, the script job steps can be conditionally generated in the remote job steps
based on the existence of the script data set in the shipment as determined by the resolution of the
data set symbol.
This model code is delivered as #RJNDVRA in the CSIQOPTN library. This code sample executes a CICS
New Copy after the data set is copied to the remote target. Script files will be transmitted as PDS
/Library members, one for each member that created a script, and potentially many Script files.
@REM ************************************************************
@REM * THESE STEPS WILL EXECUTE AFTER THE COPY TO THE REMOTE TGT
@REM ************************************************************
//* START #RJNDVRA
@IF &ZZCICSNEWC
//* START SCRIPT CICS NEW COPY
//ASCRIPT1 EXEC PGM=<YourNewCopyUtil>
//SCRIPTIN DD DISP=SHR,
// DSN=&ZZCICSNEWC
...
<insert your site specific JCL here...>
...
//* END SCRIPT 1
@ENDIF
Example: Model Post-Ship Script Steps to Flatten a PDS into a Sequential File
This model is delivered as #RJNDVRB in the CSIQOPTN library. This code sample flattens a PDS into a
sequential file. (This example includes a modified separator line.) If your processing requires a
sequential input you may need to flatten the library structure using your own utility or standard IBM
utilities as shown in the this sample.
@REM ************************************************************
@REM * THESE STEPS provide a sample FLATTEN process
@REM ************************************************************
@IF &ZZSCRIPTFB
//***************************************************************
//* THIS SCRIPT WILL TAKE A PDS & CREATE A FLAT (SEQUENTIAL) FILE
//* FROM ITS MEMBERS USING STANDARD IBM UTILITIES.
//*
//***************************************************************
//*
//SCR010 EXEC PGM=IDCAMS * FIRST CLEAN UP TEMP MEMBERS
04-May-2018 813/1109
CA Endevor® SCM - 17.0
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEL &ZZSCRIPTFB.P
DEL &ZZSCRIPTFB.S
SET MAXCC = 0
//*
//SCR020 EXEC PGM=IEBPTPCH * THEN PUNCH OUT ALL MEMBERS
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DISP=SHR,
// DSN=&ZZSCRIPTFB
//SYSUT2 DD DISP=(,CATLG),
// DSN=&ZZSCRIPTFB.P,
// SPACE=(CYL,(1,1),RLSE),
// UNIT=SYSDA,
// DCB=(RECFM=FBA,LRECL=81)
//SYSIN DD *
PUNCH TYPORG=PO
//*
//SCR030 EXEC PGM=SORT * USE SORT TO STRIP OFF LEADING
//SYSOUT DD SYSOUT=* * PUNCH CONTROL CHARACTERS
//SYSPRINT DD SYSOUT=* * AND REPLACE MEMBER CARDS
//SYSUDUMP DD SYSOUT=*
//REPORT1 DD SYSOUT=*
//SORTIN DD DISP=SHR,
// DSN=&ZZSCRIPTFB.P
//SORTOUT DD DSN=&ZZSCRIPTFB.S,
// DISP=(,CATLG),
// UNIT=SYSDA,
// SPACE=(CYL,(1,1)),
// DCB=(RECFM=FB,LRECL=80)
//SORTWK01 DD UNIT=DISK,SPACE=(CYL,(5,5))
//SORTWK02 DD UNIT=DISK,SPACE=(CYL,(5,5))
//SORTWK03 DD UNIT=DISK,SPACE=(CYL,(5,5))
//SYSIN DD *
SORT FIELDS=COPY
INREC IFTHEN=(WHEN=(2,13,CH,EQ,C'MEMBER NAME '),
BUILD=(C'./ ADD NAME=',15,8)),
IFTHEN=(WHEN=NONE,BUILD=(1:2,80))
//*
//* END SCRIPT 1
@ENDIF
@IFNOT &ZZSCRIPTFB
//* START SCRIPT - THIS STEP WILL RUN IF THERE IS NO SCRIPT FILE
//BSCRIPT1 EXEC PGM=IEFBR14,COND=((0,LE),ONLY) NO SCRIPT STEP
//* END SCRIPT 1
@ENDIF
Enable USS Supported Files for Package Ship (see page 815)
How to Enable Backout of USS Source Output Files (see page 818)
ENUSSUTL Utility (see page 819)
As a change manager (CA Endevor® SCM administrator), you can enable USS-supported files (USS,
zOS, or NFS files) for the Package Ship facility. Before USS supported files can be shipped, backout
files and records must exist for these files. To create backout files and records, add the ENUSSUTL
utility to the processor associated to the element Type definition.
04-May-2018 814/1109
CA Endevor® SCM - 17.0
The following diagram shows how you enable USS files for Package Ship and, optionally, how you
enable USS source outputs for package ship.
Complete the following procedures to enable USS files for Package Ship:
2. (Optional) How to Enable USS Source Output Files for Package Ship (see page 818) -- This
process is required only If you have USS source output files that you intend to back out or
ship.
1. Add the ENUSSUTL utility to the processor with the appropriate Copy and Select or Delete and
Select statements. The ENUSSUTL syntax depends on whether it is used in a Move, Generate,
or Delete processor. Move and Generate processors use Copy statements. Delete processors
use Delete statements.
Move and Generate processors
COPY syntax: Copy, Select group statements are used in Generate and Move processors. In a
generate processor, copy the USS file from the CA Endevor® SCM path location to a temporary
path. Then use this file as input into the ENUSSUTL utility.
Copy Indd dd-name Outdd dd-name .
Select File file-name [Newfile file-name].
Copy Indd dd-name Outdd dd-name: Identifies the dd-name copy source and target path
locations.
Indd dd-name: Specifies the dd-name source location. CA Endevor® SCM and user symbolics
can be used on the JCL path name specification.
Outdd dd-name: Specifies the dd-name target location. CA Endevor® SCM and user symbolics
can be used on the JCL path name specification.
Select FIle file-name: Specifies the name of the file at the source location for the associated
Copy statement. If the Newfile clause is not used, this file specification will be used at the
target location. A file name can be up to 255 characters. See SCL Reference (https://docops.ca.
com/display/CE18/SCL+Reference) for information on how to specify a value that spans multiple
80 character lines. Multiple select statements can follow the copy statement. Copy and Select
group statements are supported. Select statements are paired with the copy statement that
precedes it. CA Endevor® SCM and user symbolics can be used on the file name specification.
04-May-2018 815/1109
CA Endevor® SCM - 17.0
Newfile file-name: (Optional) Specifies the copy file name to be used for the file at the target
location. If this clause is not used, the file specification name is used. The name can be up to
255 characters. See SCL Reference (https://docops.ca.com/display/CE18/SCL+Reference) for
information on how to specify a value that spans multiple 80 character lines. CA Endevor®
SCM and user symbolics can be used on the file name specification.
Multiple COPY SELECT groups can be specified. Select statements are associated with the
preceding Copy statement.
COPY INDD 'INPT1' OUTDD 'OUTP1' .
SELECT FILE 'fileone.ext' .
SELECT FILE 'filetwo.ext' .
COPY INDD 'INP2' OUTDD 'OUTP2' .
SELECT FILE 'filethree.ext' .
The JCL PATHOPTS parameter is ignored if used on the Copy DD JCL statements.
The PATHMODE parameter should be used on the OUTDD DD statement. If unspecified, the
default filemode is set to '000'.
Concatenation of paths are not allowed on the INDD DD statement. The utility will check for
this and if found will fail during syntax validation.
You cannot copy to the same path and file name.
By default, ENUSSUTL copies the USS file using the credentials of the Alternate ID, so the
owner and group of the file after the copy is the Alternate ID. If you want to use the user's
credentials instead code, ALTID=N on the processor step.
Delete processors
DELETE Syntax: Use the utility's Delete and Select group statements in a delete processor.
04-May-2018 816/1109
CA Endevor® SCM - 17.0
DELETE Syntax: Use the utility's Delete and Select group statements in a delete processor.
Delete FRomDD dd-name .
Select File file-name .
FRomdd dd-name: Specifies the FROM dd-name. CA Endevor® SCM and user symbolics can be
used on the JCL path name specification.
Select FIle file-name: Specifies the name of the file to be deleted that is associated with the
Delete statement. A file name can be up to 255 characters. See SCL Reference (https://docops.
ca.com/display/CE18/SCL+Reference) for information on how to specify a value that spans
multiple 80 character lines. Multiple select statements can follow the delete statement.
Delete and Select group statements are supported. Select statements are paired with the
delete statement that precedes it. CA Endevor® SCM and user symbolics can be used on the
file name specification.
Multiple DELETE SELECT groups can be specified. Select statements are associated with the
preceding Delete statement.
DELETE FROMDD 'FROM1' .
SELECT FILE 'fileone.ext' .
SELECT FILE 'filetwo.ext' .
DELETE FROMDD 'FROM2' .
SELECT FILE 'filethree.ext' .
The JCL PATHOPTS parameter is ignored if used on the Delete DD JCL statements.
Concatenation of paths are not allowed on the FROMDD DD statement. The utility checks for
this and if found will fail during syntax validation.
By default, ENUSSUTL deletes the USS file using the credentials of the Alternate ID, so the
Alternate ID must have appropriate access to the from path. If you want to use the user's
credentials instead code, ALTID=N on the processor step.
2. (Optional) Include the NOECHO parameter on the EXEC statement, if you want to suppress the
echo of ENUSSUTL commands produced by the parser from appearing in the C1MSGS1
output.
NOECHO: Suppresses the SCL statements from appearing in the C1MSGS1 output. For
example, the following EXEC statement includes the NOECHO parameter and will prevent the
ENUSSUTL commands from appearing in the C1MSGS1 output:
04-May-2018 817/1109
CA Endevor® SCM - 17.0
1. Add the CONWRITE utility to the processor to extract the element to a temporary file. For
more information about CONWRITE, see the Extended Processors Guide.
2. Add the ENUSSUTL utility to the processor after the CONWRITE utility. Use the Copy and
Select statements to specify that the ENUSSUTL utility copy the temporary file to the targeted
USS file. The targeted USS file is the source output library defined on the Type definition.
By using the ENUSSUTL utility, a backout record and a backout file is created when an action is
executed under package processing control against this element. For more information about
using the ENUSSUTL utility, see Enable Supported Files for Package Ship.
3. Change the Type definition to remove the SOURCE OUTPUT USS library definition.
Note: If you do not intend to back out or ship your source output USS file, you do not need
to change your processor or type definition.
Example: CONWRITE and ENUSSUTL in Processor for USS Source Output Files
This example shows how a processor can use the CONWRITE and ENUSSUTL utilities to create back
out files and information for USS source output files. Thus enabling the USS files to be shipped. This
partial processor uses the CONWRITE utility to create USS output from a CA Endevor® SCM element
and copy it to a temporary USS file. The ENUSSUTL utility copies the USS file to its real name and
location. The BPXBATCH utility deletes the temporary USS file.
//GUSS PROC USSDIR='/u/users/endeavor/&C1EN(1,1)&C1S#/'
•
•
•
//***********************************************************
//* Create USS output from endevor element to a temporary USS
//* file and then use ENUSSUTL t0 copy it to its real name
//* and location.
//* Delete the temporary USS file
//* - CONWRITE element.tmp
//* - ENUSSUTL copy element.tmp to element
//* - BPXBATCH delete element.tmp
//***********************************************************
//CONW1 EXEC PGM=CONWRITE,MAXRC=0
//ELMOUT1 DD PATH='&USSDIR',
// PATHOPTS=(OWRONLY,OCREAT),
// PATHMODE=(SIRWXU,SIRWXG,SIRWXO)
//CONWIN DD *
WRITE ELEMENT &C1ELMNT255
FROM ENV &C1EN SYSTEM &C1SY SUBSYSTEM &C1SU
TYPE &C1TY STAGE &C1SI
TO DDN ELMOUT1
USSFILE &C1ELMNT255..TMP
.
04-May-2018 818/1109
CA Endevor® SCM - 17.0
.
//***********************************************************
//ENUSS1 EXEC PGM=ENUSSUTL,MAXRC=4
//INPUT DD PATH='&USSDIR'
//OUTPUT DD PATH='&USSDIR',
// PATHMODE=(SIRWXU,SIRWXG,SIRWXO)
//ENUSSIN DD *
COPY INDD 'INPUT' OUTDD 'OUTPUT' .
S FILE '&C1ELMNT255..tmp
NEWF '&C1ELMNT255'
.
//***********************************************************
//BPXB1 EXEC PGM=BPXBATCH,MAXRC=0,COND=(4,LT)
//STDPARM DD *
SH rm - r '&USSDIR.&C1ELMNT255..tmp' ;
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//*
ENUSSUTL Utility
The ENUSSUTL processor utility collects package backout information for USS processor output files.
This backout information consists of backout records and backout files.
Package outputs for USS files can be transmitted to other sites using the Package Ship utility.
However, the output cannot be shipped unless package backout information for USS files is available.
To collect this information, the processor that is associated to the element type must include the
ENUSSUTL utility to collect and associate the backout files to an element. When this utility is
executed under Package processing, the utility enables these files for Package Backout and Package
Ship.
Backout records are stored in the CA Endevor® SCM Package data set.
Delete processors
The execution of the ENUSSUTL utility in a Delete processor deletes user-selected USS files from a
user-specified USS directory. Backout files and backout records are created for these USS files, if
executed under a package.
Backout records are stored in the CA Endevor® SCM Package data set.
1. If the select source file exists at the target location, an eight-character backout file name is
generated and used as the backout saved file name. The selected file is renamed at the target
location to the backout saved file name.
2. The selected Indd path and file is copied to the Outdd path and file.
04-May-2018 819/1109
CA Endevor® SCM - 17.0
2. The selected Indd path and file is copied to the Outdd path and file.
If the select source file does not exist at the target location, no backout or rename processing is
done.
If the select source file exists at the target location, an eight-character backout file name is
generated and used as the backout saved file name. The existing file is renamed to the backout
saved file name in the same location.
As a CA Endevor® SCM administrator, you can enable the shipment of Natural objects to a remote
site and the backout of those objects from the remote site. This functionality is enabled by the Post-
Ship Script feature, which lets you ship job steps (scripts) to the remote destination for conditional
execution. In this case, the scripts are needed to write the Natural objects to the remote Natural
library after shipment.
This graphic shows how to enable backout and shipment for Natural objects:
04-May-2018 820/1109
CA Endevor® SCM - 17.0
Complete the following procedures to enable backout and shipment of Natural Objects:
1. Review the considerations for the backout and shipment of Natural objects (see page 822).
2. Configure your C1DEFLTS table (see page 822) to enable the Post-Ship Script feature. This
involves reviewing your C1DEFLTS table and updating the table if the feature is not enabled.
3. Update your Move processors (see page 823) to add steps that will build your script output
data sets for shipment and create backout records to enable backout of these data sets. The
model processor steps enable package processing for shipment and backout, store unloaded
Natural objects into PDS format, and put remote Natload JCL into the NATCMD library.
4. Define mapping rules for the data sets that contain your script files (see page 825). For these
script data sets, you always define the mapping rule remote destination as: (SCRIPT-FILE).
5. (Optionally) Create a Destination Configuration member (see page 820) to define unique
symbol values for each package ship destination. This member is only required if you want the
symbols in your script data sets to resolve to values that are based on the destination.
04-May-2018 821/1109
CA Endevor® SCM - 17.0
6. Create script steps (see page 827) that can be conditionally executed at the remote
destination, based on the existence of a script data set in the shipment. The model script
creates a sequential file from the NATCMD file PDS members being shipped and then loads
the shipped Natural objects to their Natural libraries.
For Natural objects, backout and shipment has the following limitations:
The Natural objects that you plan to ship must have valid PDS names. The Move processor for
Natural requires steps that write members to two PDSs, using the CA Endevor® SCM element
name as the member name. Therefore, all objects being shipped must have names that are valid
as member names of a PDS.
Each package that you plan to ship can contain a maximum of about 250 elements. This limitation
is due to a Natural utility requirement that sequential files be used. At the remote site, the script
file is submitted to the internal reader as a single job that consists of sequential job steps created
from the PDS members. This job uses the same job card as all other jobs executed at the remote
location. Thus, the number of job steps limits the shipments to approximately 250 elements per
package.
To avoid the 250 element per package limitation, you can make each member its own job, by
including the job card in the JCL written to the script file member.
Delete of Natural objects is not supported. The backout of shipped objects is possible by shipping
complementary files (a destination option):
Submission of the CRJOB file at the remote location (CHJOB for LOCAL shipments) restores
pre-existing Natural objects to their state before shipment.
Deletes of new objects at remote locations as part of backout processing is not handled by
this process.
1. Review your C1DEFLTS table to confirm that your RJCLROOT parameter is set to ICPY or FCPY.
If this option was omitted, insert it with a value of RJCLROOT=ICPY. For more information on
the RJCLROOT parameter, see Remote Job Stream (C1DEFLTS).
2. (Optional) Update your C1DEFLTS table as follows, if you plan to use destination script
symbols:
a.
04-May-2018 822/1109
2.
a. Define the name of your Destination Configuration member to C1DEFLTS, using the
DESTCFGMBR= parameter. If no value is specified, the value defaults to null.
b. Review your C1DEFLTS table to confirm that you have a valid PARMLIB dataset.
1. Update your Move processor to insert any additional steps needed to build the required
remote script Natural LOAD JCL syntax based on your site's requirements. For Natural objects,
the additional steps for the Move processor must meet the following requirements:
Write members to two PDSs, using the CA Endevor® SCM element name as the member
name. This requires that all objects being shipped have names that are valid as member
names of a PDS.
The first PDS members contain the individual unload of the Natural objects. This is not
a script file.
The second PDS members contain a complete job step to write the Natural object to
the remote Natural library after shipment. This data set must be identified as a
(SCRIPT-FILE) during shipment. This is done through the mapping rules based on the
shipment destination. For more information about the SCRIPT-FILE, see Define
Mapping Rules for Post-Ship Script Data Sets (see page 825).
Because each Natural object is individually unloaded, each must also be individually
loaded back to Natural.
Because the script file members contain a complete job step, symbols can be used that
will be substituted at shipment time based on the destination, through the destination
configuration member of the CA Endevor® SCM PARMLIB.
You must be careful not to use existing processor symbols; &C1 symbol names are not
allowed in the destination configuration member.
Symbols, to be resolved at shipment time, can be used for the values: Natural nucleus
name, parameters to the nucleus, and the remote target Natural library name.
2. Update the CA Endevor® SCM PARMLIB destination configuration member, if symbols are
used in the script file members.
Each destination that will receive the shipment must be updated to include the symbols
used in the script file members.
Each destination can have its own value for the symbols.
04-May-2018 823/1109
CA Endevor® SCM - 17.0
3. Verify that MONITOR and BACKOUT keywords are specified on the script data set so that
package processing can create backout records to track your script files.
4. Name your script data set so that it is easy to determine its content. The final qualifier of the
script data set will be used when building model control statements. So consider choosing an
appropriate name so the different types of script processing can be determined. For example,
an appropriate name might be NATCMD for the script file containing the Natural LOAD JCL
steps.
Example: Model Code to Create Post-Ship Script Output Data Sets for Natural Objects
The following code sample added to the PNATMOV Move processor for Natural objects will enable
package processing for shipment and backout, store unloaded Natural objects into PDS format, and
put remote Natload JCL into the NATCMD library. This sample uses symbols that will be resolved at
shipment time based upon shipment destination. These symbols all begin with &RMT.
// OBJMT='&C1ELMNT255',
// OBJMD='&C1ELMNT255',
// OBJMS='NAT&C1ELMNT255(1,4)',
// OBJWN='WITH,NEWLIBRARY,&RMTLNAME,%',
// OBJLT='LOAD &C1ELMNT255,LIB,*,OBJTYPE,N,&OBJWN',
// OBJLD='LOAD &C1ELMNT255,LIB,*,OBJTYPE,D,%',
// OBJLS='LOAD &C1ELMNT255,LIB,*,OBJTYPE,E,&OBJWN',
// OBJMEM=&OBJM&C1TY(3,1)
//*
//*******************************************************************
//* PACKAGE PROCESSING FOR SHIPMENT AND BACKOUT (NO DDMS)
//*******************************************************************
//IF1 IF (&C1PKGID NE ' ') THEN
//IF2 IF (&C1TY NE 'NTDDM') THEN
//*
//*********************************************************************
//* STORE UNLOADED NATURAL OBJECT INTO PDS
//*********************************************************************
//GENER1 EXEC PGM=IEBGENER,MAXRC=0
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD DSN=&&ELMMOVE,DISP=OLD
//SYSUT2 DD DISP=SHR,
// DSN=BST.MOTM.ESCM715.NATOBJ(&OBJMEM),
// MONITOR=COMPONENTS
//*
//*********************************************************************
//* PUT REMOTE NATLOAD JCL INTO NATCMD LIBRARY
//*********************************************************************
//GENER2 EXEC PGM=IEBGENER,MAXRC=0
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD DATA,DLM='$$'
//*
//NATLOAD EXEC PGM=&RMTNATNUC
//STEPLIB DD DSN=&RMTNATLIB,DISP=SHR
// DD DSN=&RMTADALIB,DISP=SHR
//CMPRMIN DD *
&RMTPRM1
&RMTPRM3
&RMTPRM4
&RMTPRM5
//DDCARD DD *
&RMTDDCARD
//CMWKF01 DD DISP=SHR,
// DSN=PUBLIC.MORMI08.NATOBJ(&OBJMEM)
//CMPRINT DD SYSOUT=*
//DDPRINT DD SYSOUT=*
//DDDRUCK DD DUMMY
//MPMDUMP DD DUMMY
//DDKARTE DD DUMMY
04-May-2018 824/1109
CA Endevor® SCM - 17.0
//DDKARTE DD DUMMY
//CMSYNIN DD *
SYSPROF
SYSOBJH
&OBJL&C1TY(3,1)
WHERE,REPLACE,ALL,REPORT
.
FIN
$$
//SYSUT2 DD DISP=SHR,
// DSN=BST.MOTM.ESCM715.NATCMD(&OBJMEM),
// MONITOR=COMPONENTS
//*
//IF2 ENDIF
//IF1 ENDIF
Define Mapping Rules for Post-Ship Script Data Sets for Natural Objects
Define data set mapping rules for your processor output files that contain your scripts.
1. Specify the Host Dataset Name field masks to match the script data set name.
2. Specify the Remote Dataset Name field value using the keyword exactly as shown next:
(SCRIPT-FILE)
The parentheses, which must be included and the dash are not valid characters for a data set
name, so this value cannot be mistaken for one.
Note: For more information about defining mapping rules, see Create a Mapping Rule (see
page 820).
To create a mapping rule for a script data set with a final qualifier of NATCMD , define the Host
Dataset Name and the Remote Dataset Name as shown next.
HOST DATASET NAME ===> *.*.*.NATCMD
maps to
REMOTE DATASET NAME ===> (SCRIPT-FILE)
Note: This example creates a mapping rule for the Natural LOAD JCL created in the example shown in
Update Processors for Post-Ship Script (see page 820) Processing of Natural Objects
Note: On the DSN Mapping Selection List, SCRIPT appears in the Status column when a
script file is identified by a mapping rule.
04-May-2018 825/1109
CA Endevor® SCM - 17.0
1. Create a Destination Configuration file to define symbol names and values unique to each
package ship destination.
Use the following syntax to define the symbol names and values for each destination:
>>-- DESTination 'destid' --------------------------->
+<----<----<----<----<----<----<----<----<----<---+
--+--> SYMbol 'symbol-name' VALue 'symbol-value' -- - ->
---> . ---------------------------------------------><
This statement can be repeated for each destination and the SYMBOL and VALUE combination
can be defined as many times as necessary within each statement. If SYMBOL is coded (there
must be at least one) then VALUE must also be coded. To code a null value for a symbol, use
two consecutive single quotes after the VALUE keyword.
3. Include the symbols in your script data set members as appropriate to represent information
that will vary by destination.
Important: Symbol substitution can cause syntax errors by causing line overflows.
Consider the maximum length of your symbols, use symbol substringing to generate
appropriate syntax, or both. For more information on Symbol substring syntax, see the
Extended Processors Guide. Alternatively, if for example you need to substitute long symbols
such as path or file names, consider using a variable blocked (RECFM=VB) script file.
Note: The content of the Destination Configuration member can be viewed from the Display Options
menu and any syntax errors can be reviewed there. The name of the Destination Configuration
member is displayed in the Parameter Library Information section of the Site Information from
C1DEFLTS panel. On the DSN Mapping Selection List, SCRIPT appears in the Status column when a
script file is identified by a mapping rule. Script Execution status can be returned and displayed in the
'Shipment Status' view by scrolling right.
This example of a Destination Configuration file defines different values for the symbol RMTNATNUC
and RMTNATLIB, depending on the target destination.
DESTINATION CA31XCM
SYMBOL 'RMTNATNUC' VALUE 'N41DB99B'
04-May-2018 826/1109
CA Endevor® SCM - 17.0
SYMBOL 'RMTNATNUC' VALUE 'N41DB99B'
SYMBOL 'RMTNATLIB' VALUE 'BST.NAT414.LOAD' .
DESTINATION CA11LOC
SYMBOL 'RMTNATNUC' VALUE 'N42DB99B'
SYMBOL 'RMTNATLIB' VALUE 'BST.NAT427.LOAD' .
Note: This example creates &RMTNATNUC and &RMTNATLIB symbols for the Natural LOAD
JCL script created in the example shown in Update Processors for Post-Ship Script
Processing of Natural Objects (see page 823).
To enable conditional execution, a symbol represents each script data set. The symbol is based on the
last qualifier of the host data set name, prefixed by the characters ZZ (for example, &ZZNATCMD for
the data set BST.USER12.NATCMD. The value of the symbol will be the remote staging data set name
for the script data set.
The symbols can be checked in the package ship model control members through @IF and @IFNOT
statements. Therefore, the script job steps can be conditionally generated in the remote job steps
based on the existence of the script data set in the shipment as determined by the resolution of the
data set symbol.
The following script is provided in the model control member #RJNDVRA. This script will create a
sequential file from the NATCMD file PDS members being shipped and then loads the shipped Natural
objects to their Natural libraries.
The model member #RJNDVRA includes the following steps for processing the script file:
Using standard IBM utilities (IEBPTPCH, SORT) to sequentialize all shipped members in the script
file
Submitting the sequentialized job steps created from the members to the internal reader as a
single job
This job uses the same job card as all other jobs executed at the remote location.
This will limit shipments to approximately 250 elements per package (number of job steps
limitation).
It is also possible to include the job card in the JCL written to the script file member, removing
the 250 element per package limitation by making each member its own job.
To use the model #RJNDVRA script, you do not need to make any edits to the #RJNDVRB model.
04-May-2018 827/1109
CA Endevor® SCM - 17.0
@IF &ZZNATCMD
//********************************************************************
//*
//*
//* THESE STEPS CREATE A SEQUENTIAL FILE FROM THE NATCMD FILE PDS
//* MEMBERS BEING SHIPPED AND THEN
//* LOADS THE SHIPPED NATURAL OBJECTS TO THEIR
//* NATURAL LIBRARIES.
//*
//********************************************************************
//* DELETE WORK FILES
//********************************************************************
//SCR010 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEL PUBLIC.MORMI08.NATCMDT
DEL PUBLIC.MORMI08.NATCMDS
SET MAXCC = 0
//*
//********************************************************************
//* CREATE SEQUENTIAL FILE FROM PDS MEMBERS
//********************************************************************
//SCR020 EXEC PGM=IEBPTPCH
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DISP=SHR, REMOTE STAGING DATA SET FOR SCRIPT
// DSN=&ZZNATCMD
//SYSUT2 DD DSN=PUBLIC.MORMI08.NATCMDT,
// DISP=(,CATLG),
// SPACE=(CYL,(1,1),RLSE),
// UNIT=SYSDA,
// DCB=(RECFM=FBA,LRECL=81)
//SYSIN DD *
PUNCH TYPORG=PO
//*
//********************************************************************
//* REMOVE LEADING CONTROL CHARACTER AND SEPARATOR LINES
//********************************************************************
//SCR030 EXEC PGM=SORT
//SYSOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//REPORT1 DD SYSOUT=*
//SORTIN DD DISP=SHR,DSN=PUBLIC.MORMI08.NATCMDT
//SORTOUT DD DSN=PUBLIC.MORMI08.NATCMDS,
// DISP=(,CATLG),
// UNIT=SYSDA,
// SPACE=(CYL,(1,1)),
// DCB=(RECFM=FB,LRECL=80)
//SORTWK01 DD UNIT=DISK,SPACE=(CYL,(5,5))
//SORTWK02 DD UNIT=DISK,SPACE=(CYL,(5,5))
//SORTWK03 DD UNIT=DISK,SPACE=(CYL,(5,5))
//SYSIN DD *
OMIT COND=((2,13,CH,EQ,C'MEMBER NAME '))
SORT FIELDS=COPY
INREC FIELDS=(1:2,80)
//*
//GENER1 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD DATA,DLM='$$'
&RJOBCARDS
$$
// DD DISP=SHR,DSN=PUBLIC.MORMI08.NATCMDS
//SYSUT2 DD SYSOUT=(A,INTRDR)
@ENDIF
04-May-2018 828/1109
CA Endevor® SCM - 17.0
When you submit the shipment queue, CA Endevor® SCM builds and submits a JCL stream to ship the
packages. The remainder of this section describes the steps in this shipment JCL.
BEND--Step1BuildandStagetheShipment--OTH
When it executes this step, the ship utility builds a shipment consisting of the following:
A staging data set for each library involved in the package execution.
JCL for execution at the remote site, consisting of an IEBCOPY step, an IDCAMS (delete) step, and
confirmation steps.
Data transmission utility commands and/or JCL to transmit the data sets and execute the remote
copy/delete job. (Not applicable for local transmissions.)
A file of correspondences between host and remote production and staging data sets.
04-May-2018 829/1109
CA Endevor® SCM - 17.0
The ship utility then populates the staging data sets, records the shipment, and passes the entire
shipment to Step 2.
prefix
The user-defined prefix for the host or remote site on the Create/Modify Definition panel, or the
default value TSOuserid.NDVR.
Dyymmdd
The date the shipment queue was submitted.
Thhmmss
The time the shipment queue was submitted.
destination
The destination name.
suffix
The kind of shipment member. Possible suffixes:
CxJOB -- Identifies a host (CHJOB) or remote (CRJOB) copy/delete/confirm job stream for
complementary data sets
.AxREF -- Identifies a host (AHREF) or remote (ARREF) data set name and or USS path cross-
reference file.
AxPAX -- Identifies the a host (AHPAX) or remote (ARPAX) Archive files that are used to
contain USS files and their complementaries, if any, in the shipment. This file is optional and is
only present if the shipment request includes USS objects.
AxUCD -- Identifies the host (AHUCD) or remote (ARUCD) commands stream that perform the
un-pax, and copy commands to move shipped USS objects to the final location. This file is
optional and is only present if the shipment request includes USS objects.
.AHnnn -- Identifies a host shipment data set, where nnn is a sequential number starting at
001.
.CHnnn -- Identifies a host complementary data set, where nnn is a sequential number
starting at 001.
.ARnnn -- Identifies a remote shipment data set, where nnn is a sequential number and
corresponds to its host counterpart AHnnn.
04-May-2018 830/1109
CA Endevor® SCM - 17.0
.CRnnn -- Identifies a remote complementary data set, where nnn is a sequential number and
corresponds to its host counterpart CHnnn.
.SHnnn -- Identifies a host shipment script data set, where nnn is a sequential number starting
at 001.
.THnnn -- Identifies a host complementary script data set, where nnn is a sequential number
starting at 001.
.SRnnn -- Identifies a remote shipment script data set, where nnn is a sequential number and
corresponds to its host counterpart SHnnn.
.TRnnn -- Identifies a remote complementary script data set, where nnn is a sequential
number and corresponds to its host counterpart THnnn.
userid.NDVR.D071130.T142532.BOSTON.AH0000034
userid.NDVR.D071130.T143515.CHICAGO.CRJOB
userid.NDVR.D071130.T145216.BOSTON.ARREF
1. Copying package outputs from remote staging data sets to production data sets, using
IEBCOPY.
2. Deleting members from the production data sets that were also deleted on the host.
Note: For more information, see Creating Model Transmission Control Statements (see
page 802).
04-May-2018 831/1109
CA Endevor® SCM - 17.0
Example
SHIPMENT DATASETS
HOST LIBRARY: BST.XDVRC1S1.LISTINGS
HOST STAGING: DA1ME10.D10322.T164235.BOSTON1.AH003
REMOTE STAGING: DA1ME10.D10322.T164235.BOSTON1.AR003
REMOTE LIBRARY: BST.XDVRC1S1.LISTINGS
*
SHIPMENT DATASETS
HOST LIBRARY: BST.XDVRC1S1.LKEDLIB
HOST STAGING: DA1ME10.D10322.T164235.BOSTON1.AH004
REMOTE STAGING: DA1ME10.D10322.T164235.BOSTON1.AR004
REMOTE LIBRARY: BST.XDVRC1S1.LKEDLIB
*
SHIPMENT DATASETS
HOST LIBRARY: BST.XDVRC1S1.LKEDLIST
HOST STAGING: DA1ME10.D10322.T164235.BOSTON1.AH006
REMOTE STAGING: DA1ME10.D10322.T164235.BOSTON1.AR006
REMOTE LIBRARY: BST.XDVRC1S1.LKEDLIST
*
SHIPMENT DATASETS
HOST LIBRARY: BST.XDVRC1S1.LOADLIB
HOST STAGING: DA1ME10.D10322.T164235.BOSTON1.AH005
REMOTE STAGING: DA1ME10.D10322.T164235.BOSTON1.AR005
REMOTE LIBRARY: BST.XDVRC1S1.LOADLIB
*
SHIPMENT DATASETS
HOST LIBRARY: BST.XDVRC1S1.OBJLIB
HOST STAGING: DA1ME10.D10322.T164235.BOSTON1.AH002
REMOTE STAGING: DA1ME10.D10322.T164235.BOSTON1.AR002
REMOTE LIBRARY: BST.XDVRC1S1.OBJLIB
Shipments Contents
By the end of Step 1, the ship utility has built a shipment consisting of the following items:
If the shipment contained script files, Script files (.SHnnn) are also included.
If complementary data sets have been requested, the shipment also contains the remote JCL for the
complementary files (.CHJOB) and if appropriate, the complementary script files).
04-May-2018 832/1109
CA Endevor® SCM - 17.0
BEND--Step2TransmittingtheShipment--OTH
XCOM (C1BMXCOM), BDT Version 2 (C1BMXBDT), and CONNECT:Direct (C1BMXNDM) execute in this
step. The transmission program performs the following steps:
2. If there are any script files, they are staged and any "Destination Symbols" are resolved.
3. Transmits the host staging data sets to the remote sites where it builds remote staging data
sets.
4. Executes the remote copy/delete JCL (.AxJOB) if the skeletal JCL (BDT and CONNECT:Direct) or
model transmission control member (XCOM) are set up for automatic execution.
BDT using NJE/NJI (C1BMXBD1) and NetView FTP (C1BMXFTP) are executed in a secondary job
stream built in Step 1. This step consists of writing that job stream to an internal reader. The first step
of the secondary job stream performs the same functions as listed previously.
Local transfers (C1BMXLOC) do not execute a physical transmission. The copy/delete JCL is submitted
for execution if the model transmission control member is set up for automatic execution.
04-May-2018 833/1109
CA Endevor® SCM - 17.0
BEND--Step3ConfirmingtheTransmission--OTH
During this step, the ship utility records confirmation of the transmission to the remote site.
Note: An after-confirm exit can be used, with the notification utility, to notify users of the
completion of the shipment.
04-May-2018 834/1109
CA Endevor® SCM - 17.0
BEND--Step4DeletetheStagingDataSets--OTH
If the DISPOSITION field for the host staging data set names has the value DELETE, the ship utility
deletes the host staging data sets.
1. Execution of the "Before" ship script file steps from #RJNDVRB (if any).
2. Copying package outputs from staging data sets to production data sets, using IEBCOPY.
BEND--RemoteCopyDeleteJobSteps1of4--OTH
3. If the package contained any USS objects, then an additional step (BPXBATCH) invokes the
command stream (ARUCD) to unarchive the USS objects to the staging directories, and copies
each file to the final location.
Note: The actual syntax built performs a delete (rm) for each output before
04-May-2018 835/1109
3.
Note: The actual syntax built performs a delete (rm) for each output before
performing a copy (cp) for each file. This ensures that date and timestamps on the
remote files match the corresponding generate (move) times on the host system.
4. Deleting members from the production data sets or paths that were also deleted on the host
during package execution or backout.
BEND--RemoteCopyDeleteJobSteps2of4--OTH
5. Execution of the "After" ship script file steps from #RJNDVRA (if any).
BEND--RemoteCopyDeleteJobSteps3of4--OTH
7. (Optional) Deleting the staging and cross reference data sets. This step is included only if the
disposition of the staging data sets on the destination record used for the shipment is delete.
04-May-2018 836/1109
CA Endevor® SCM - 17.0
BEND--RemoteCopyDeleteJobSteps4of4--OTH
//IAR001 DD DISP=SHR,DSN=TSOUSER.NDVR.D11119.T123747.DESTNDM.AR001
//OAR001 DD DISP=OLD,DSN=TEST.IMRENV1.SRCOUT1
//IAR002 DD DISP=SHR,DSN=TSOUSER.NDVR.D11119.T123747.DESTNDM.AR002
//OAR002 DD DISP=OLD,DSN=TEST.IMRENV1.OBJLIB1
//IAR003 DD DISP=SHR,DSN=TSOUSER.NDVR.D11119.T123747.DESTNDM.AR003
//OAR003 DD DISP=OLD,DSN=TEST.UTILS1.LISTINGS
//SYSIN DD *
COPY OUTDD=OAR002,INDD=((IAR002,R))
COPY OUTDD=OAR001,INDD=((IAR001,R))
COPY OUTDD=OAR003,INDD=((IAR003,R))
//* *------------------------* ISPSLIB(C1BMXDEL)
//* * REMOTE SITE JOBSTEP TO DELETE MEMBERS WHICH
//* * WERE DELETED BY THE EXECUTION OF THE PACKAGE
//* *---------------------------------*
//DELETE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE 'TSOUSER.NDVR.D11119.T123747.DESTNDM.AR002' NONVSAM
DELETE 'TSOUSER.NDVR.D11119.T123747.DESTNDM.AR001' NONVSAM
DELETE 'TSOUSER.NDVR.D11119.T123747.DESTNDM.AR003' NONVSAM
DELETE 'TSOUSER.NDVR.D11119.T123747.DESTNDM.ARJOB' NONVSAM
DELETE 'TSOUSER.NDVR.D11119.T123747.DESTNDM.ARREF' NONVSAM
//CONFCOPY EXEC PGM=IEBGENER EXECUTED AT THE REMOTE SITE
//SYSUT1 DD DATA,DLM=$$ JOB SHIPPED BACK TO HOST
//TSOUSERP JOB (1111),'WESTBORO',CLASS=A,
// MSGCLASS=X,NOTIFY=TSOUSER
/*ROUTE PRINT U101
/*ROUTE XEQ HOSTNODE
//CONFCOPY EXEC PGM=NDVRC1,
// PARM='C1BMX000,19911119,12374712,CONF,RCPY,EX,****,DESTNDM '
//*
//* *----------------------* ISPSLIB(C1BMXLIB) *
//*
//* *================================================================*
//* * STEPLIB, CONLIB, MESSAGE LOG AND ABEND
DATASETS
//* *================================================================*
//*
//STEPLIB DD DISP=SHR,DSN=iprfx.iqual.CSIQAUTH
04-May-2018 837/1109
CA Endevor® SCM - 17.0
//STEPLIB DD DISP=SHR,DSN=iprfx.iqual.CSIQAUTH
//CONLIB DD DSN=TEST.NDVR36B.ZAPLOAD,DISP=SHR
// DD DSN=TEST.C19109.CONLIB,DISP=SHR
//*
//SYSABEND DD SYSOUT=*
//C1BMXLOG DD SYSOUT=* *** MESSAGES, ERRORS, RETURN CODES ********
//* *----------------------* C1BMXRCN (CONT.) *
$$
//SYSUT2 DD SYSOUT=(A,INTRDR)
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//*
//CONFABND EXEC PGM=IEBGENER,COND=ONLY EXECUTED AT THE REMOTE SITE
//SYSUT1 DD DATA,DLM=$$ JOB SHIPPED BACK TO HOST
//TSOUSERP JOB (1111),'WESTBORO',CLASS=A,
// MSGCLASS=X,NOTIFY=TSOUSER
/*ROUTE PRINT U101
/*ROUTE XEQ HOSTNODE
//CONFCOPY EXEC PGM=NDVRC1,
// PARM='C1BMX000,19911119,12374712,CONF,RCPY,AB,****,DESTNDM '
//*
//* *----------------------* ISPSLIB(C1BMXLIB) *
//*
//* *================================================================*
//* * STEPLIB, CONLIB, MESSAGE LOG AND ABEND DATASETS
//* *================================================================*
//*
//STEPLIB DD DISP=SHR,DSN=iprfx.iqual.CSIQAUTH
//CONLIB DD DSN=TEST.NDVR36B.ZAPLOAD,DISP=SHR
// DD DSN=TEST.C19109.CONLIB,DISP=SHR
//*
//SYSABEND DD SYSOUT=*
//C1BMXLOG DD SYSOUT=* *** MESSAGES, ERRORS, RETURN CODES ********
//* *----------------------* C1BMXRCN (CONT.) *
$$
//SYSUT2 DD SYSOUT=(A,INTRDR)
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//* **** END OF JCL STREAM ****
Note: You can change the allocation disposition of the package ship destination data sets
defined in the IEBCOPY jobs from DISP=OLD to DISP=SHR. See the Optional Features table,
ENCOPTBLE, for the parameter ENHOPT SHP_DISP_SHR=ON.
04-May-2018 838/1109
CA Endevor® SCM - 17.0
Administering Package Ship involves building, tracking, and confirming shipments. The first step in
shipping a package is to build a shipment request. You can build ship requests in foreground or in
batch. This section describes how to build shipments in foreground.
When you press ENTER after building a shipment, CA Endevor® SCM places that shipment in a
request queue. You can do the following:
Display the queue, reset it (deleting all shipment requests), or submit it.
You build ship requests in foreground from the Package Shipment panel. To access the Package
Shipment panel, type 6 (SHIP) in the OPTION field on the Package Options Menu; press ENTER. CA
Endevor® SCM displays the Package Shipment panel. On the Package Shipment panel, enter the
appropriate information and type 1 (BUILD SHIPMENT REQUEST); press ENTER. CA Endevor® SCM
displays a Package Selection List and/or a Destination Selection List, then a Confirm Shipment panel.
You place a shipment in the shipment queue from the Confirm Shipment panel.
The procedures that follow explain how to build requests to ship the following:
1. Type 1 in the OPTION field on the Package Shipment panel, along with all required and any
optional information you desire. Press ENTER.
2. If the Confirm Shipment panel displays, proceed to Step 3. Otherwise select the package and
/or destination from the selection lists that appear.
When you press ENTER on the last selection list, the Confirm Shipment panel displays.
Type SH and press ENTER to place the ship request in the request queue.
Note: For more information, see Confirm a Package for Shipment (see page 843).
04-May-2018 839/1109
CA Endevor® SCM - 17.0
4. Press END key until you return to the panel you need to perform your next action.
1. Type 1 in the OPTION field on the Package Shipment panel, as well as all required and any
optional information you want and press ENTER.
2. If the Confirm Shipment panel displays, proceed to Step 3. Otherwise select the package and
/or destinations from the selection lists that appear. When you press ENTER on the last
selection list, the Confirm Shipment panel displays.
3. Review the information on the Confirm Shipment panel, then type SH and press ENTER to
place the ship request in the request queue. When you press ENTER, the DESTINATION field
changes to display the next destination you have selected.
Note: For more information, see Confirm a Package for Shipment (see page 843).
4. Repeat Step 3 until the Destination Selection List appears when you press ENTER. This
indicates that you have placed shipments for all selected destinations in the shipment queue.
Select another destination, then press ENTER to display the Confirm Shipment panel.
Proceed from Step 3.
Press END key until you return to the panel you need to perform your next action.
1. Type 1 in the OPTION field on the Package Shipment panel, as well as all required and any
optional information you desire and press ENTER.
2. If the Confirm Shipment panel displays, proceed to Step 3. Otherwise select the packages and
/or destination from the selection lists that appear.
When you press ENTER on the last selection list, the Confirm Shipment panel displays.
3. Review the information on the Confirm Shipment panel, then type SH and press ENTER to
place the ship request in the request queue and return to the Destination Selection List. The
name of the first selected package displays in the WHICH field on this panel.
Note: For more information, see Confirm a Package for Shipment (see page 843).
04-May-2018 840/1109
CA Endevor® SCM - 17.0
4. Press END key on the Destination Selection List to display the second selected package. Then
select a destination for this package and press ENTER to display the Confirm Shipment panel.
Repeat Step 3.
5. Repeat Steps 3 and 4 until the Package Selection List or Package Shipment panel appears
when you press END key. This indicates that you have placed shipments for all selected
packages in the shipment queue.
Press END key until you return to the panel you need to perform your next action.
Package ID
Required. The 1- to 16-character ID of the package you want to ship.
Destination
Required. The 1- to 7-character name of the destination which is to receive the package (or
backouts).
Pkg/Backout
Default is P, package. Indicates whether you want to ship package outputs or backout members.
Acceptable values are:
Package
04-May-2018 841/1109
CA Endevor® SCM - 17.0
Package
The up to 16 character package ID
Status
The status of the package. The status must be executed to ship the package.
Description
The up to 40 character package description.
DEST-ID
Identifies the destination name.
MESSAGE
Identifies a literal or message ID indicating an action was performed against this destination (for
example, *MODIFIED, *DELETED, and so on).
TRAN-METHOD
Identifies the data transmission utility used for this destination.
RMT-NODENAME
Identifies the data transmission utility nodename of the destination.
DESCRIPTION
Describes the destination.
REMOTE-IPNAME
Identifies the site to which package outputs are to be shipped.
IPPORT
Identifies the XCOM SERVPORT specification of the target server.
Note: If a remote IPNAME is specified for a destination, you can scroll to the right to view
the REMOTE IPNAME and IPPORT. ESORT is supported for all column headings.
Press END key from this panel to perform the following actions:
Display the next selected package in the S - SELECT DESTINATION TO RECEIVE: field, if multiple
packages were selected and not all have been placed in the shipment queue.
Return to the Package Selection List or Package Shipment panel if there are no more selected
packages.
04-May-2018 842/1109
CA Endevor® SCM - 17.0
1. Review the shipment information on the Confirm Shipment panel and change the values in
the following fields, if necessary.
Note: If you do not want to place the package in the shipment queue at this time,
press the End key to return to the immediately prior panel.
The next selected destination appears in the DESTINATION field, if you selected multiple
destinations for this package and not all package and destination pairs have been placed
in the shipment queue.
The Destination Selection panel appears, if you selected multiple packages and not all
packages have been placed in the shipment queue.
Two other points in the process of shipping are tracked: the execution of the data transmission utility
and the execution of the remote COPY/DELETE/CONFIRM job. These points are tracked by executing
the shipment confirmation utility as a conditional job step after the execution of the data
transmission utility (at the host site) and after the execution of the IEBCOPY/IDCAMS job (at the
remote site).
Confirmation Steps
Two ISPF Skeletal JCL members deal with shipment confirmation for ISPF initiated shipments.
C1BMXHCN handles confirmation of the data transmission job step which executes at the host site.
C1BMXRCN handles confirmation of the IEBCOPY/IDCAMS job which executes at the remote site.
There is also a corresponding pair of JCL/PROCLIB members which are called to perform
confirmations for API shipments (SHIPHCN and SHIPRCN). Left unmodified, these steps would leave a
04-May-2018 843/1109
CA Endevor® SCM - 17.0
confirmations for API shipments (SHIPHCN and SHIPRCN). Left unmodified, these steps would leave a
generic record of the data transmission or COPY/DELETE. The record of shipment would be marked
EXEC'D or ABEND under the "HOST TRANS" or "REMOTE MOVE" columns of the Package Shipment
Status panel.
If a more precise record of these events is required, the number of conditional confirmation steps can
be increased, status of script file exececution steps can be returned, and the shipment confirmation
utility parameter can be changed to report different things.
The confirmation parameter is made up of a symbolic prefix (resolved by ISPF facilities), a root, and a
symbolic suffix (resolved by the shipment staging utility)
//STEPNAME EXEC PGM=NDVRC1,PARM='&VNBCPARM.,CONF,pppp,op,code,********',
// COND=(see_example)
Pppp-Is the point of confirmation. This is a four-character string which can have the following
values
Op-Is the algebraic operator associated with the return code of the step being confirmed. The
valid operators are:
EQ-Equal.
GT-Greater than.
LT-Less than.
Code-Is the code to be reported. Usually this would be a four-digit number which bears a
relationship to the step being confirmed.
This sample shows how C1BMXHCN could be modified to report the following return codes: RC=00,
RC=04, RC=08, RC>=12, ABEND.
//CONFGE12 EXEC PGM=NDVRC1,REGION=4096K,COND=(12,GT,&VNBXSTP),
// PARM='&VNBCPARM,CONF,HXMT,GE,0012,********'
//C1BMXDTM DD DSN=&&&&XDTM,DISP=(MOD,PASS),SPACE=(TRK,(1,0)),
// DCB=(RECFM=F,LRECL=80,BLKSIZE=3120,DSORG=PS),
// UNIT=tdisk
//*
04-May-2018 844/1109
CA Endevor® SCM - 17.0
//*
)IM C1BMXLIB OPT
//*
//*
//CONFEQ08 EXEC PGM=NDVRC1,REGION=4096K,COND=(08,NE,&VNBXSTP),
// PARM='&VNBCPARM,CONF,HXMT,EQ,0008,********'
//C1BMXDTM DD DSN=&&&&XDTM,DISP=(MOD,PASS),SPACE=(TRK,(1,0)),
// DCB=(RECFM=F,LRECL=80,BLKSIZE=3120,DSORG=PS),
// UNIT=tdisk
//*
)IM C1BMXLIB OPT
//*
//*
//CONFEQ04 EXEC PGM=NDVRC1,REGION=4096K,COND=(04,NE,&VNBXSTP),
// PARM='&VNBCPARM,CONF,HXMT,EQ,0004,********'
//C1BMXDTM DD DSN=&&&&XDTM,DISP=(MOD,PASS),SPACE=(TRK,(1,0)),
// DCB=(RECFM=F,LRECL=80,BLKSIZE=3120,DSORG=PS),
// UNIT=tdisk
//*
)IM C1BMXLIB OPT
//*
//*
//CONFEQ00 EXEC PGM=NDVRC1,REGION=4096K,COND=(00,NE,&VNBXSTP),
// PARM='&VNBCPARM,CONF,HXMT,EQ,0000,********'
//C1BMXDTM DD DSN=&&&&XDTM,DISP=(MOD,PASS),SPACE=(TRK,(1,0)),
// DCB=(RECFM=F,LRECL=80,BLKSIZE=3120,DSORG=PS),
// UNIT=tdisk
//*
)IM C1BMXLIB OPT
//*
//*
//CONFABND EXEC PGM=NDVRC1,REGION=4096K,COND=ONLY,
// PARM='&VNBCPARM,CONF,HXMT,AB,****,********'
//C1BMXDTM DD DSN=&&&&XDTM,DISP=(MOD,PASS),SPACE=(TRK,(1,0)),
// DCB=(RECFM=F,LRECL=80,BLKSIZE=3120,DSORG=PS),
// UNIT=tdisk
//*
)IM C1BMXLIB OPT
//*
This sample shows how C1BMXRCN could be modified to report the following return codes: RC=00,
RC=04, RC=08, RC>=12, ABEND. The COND= parameter is on the IEBGENER execute card, not on the
NDVRC1 execute card. $DEST_ID is resolved by the shipment staging utility.
//CONFGT12 EXEC PGM=IEBGENER,COND=(12,GT)
//SYSUT1 DD DATA,DLM=$$ JOB SHIPPED BACK TO HOST
)IM C1BMXHJC
//CONFCOPY EXEC PGM=NDVRC1,
// PARM='&VNBCPARM,CONF,RCPY,GE,0012,$DEST_ID'
)IM C1BMXLIB
$$
//SYSUT2 DD SYSOUT=(INTRDR,A)
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//*
//* *--------------------------------*
//*
//CONFEQ08 EXEC PGM=IEBGENER,COND=(08,NE)
//SYSUT1 DD DATA,DLM=$$ JOB SHIPPED BACK TO HOST
)IM C1BMXHJC
//CONFCOPY EXEC PGM=NDVRC1,
// PARM='&VNBCPARM,CONF,RCPY,EQ,0008,$DEST_ID'
)IM C1BMXLIB
$$
//SYSUT2 DD SYSOUT=(INTRDR,A)
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//*
//* *--------------------------------*
04-May-2018 845/1109
CA Endevor® SCM - 17.0
//* *--------------------------------*
//*
//CONFEQ04 EXEC PGM=IEBGENER,COND=(04,NE)
//SYSUT1 DD DATA,DLM=$$ JOB SHIPPED BACK TO HOST
)IM C1BMXHJC
//CONFCOPY EXEC PGM=NDVRC1,
// PARM='&VNBCPARM,CONF,RCPY,EQ,0004,$DEST_ID'
)IM C1BMXLIB
$$
//SYSUT2 DD SYSOUT=(INTRDR,A)
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//*
//* *--------------------------------*
//*
//CONFEQ00 EXEC PGM=IEBGENER,COND=(00,NE)
//SYSUT1 DD DATA,DLM=$$ JOB SHIPPED BACK TO HOST
)IM C1BMXHJC
//CONFCOPY EXEC PGM=NDVRC1,
// PARM='&VNBCPARM,CONF,RCPY,EQ,0000,$DEST_ID'
)IM C1BMXLIB
$$
//SYSUT2 DD SYSOUT=(INTRDR,A)
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//*
//* *--------------------------------*
//*
//CONFABND EXEC PGM=IEBGENER,COND=ONLY EXECUTED AT THE REMOTE SITE
//SYSUT1 DD DATA,DLM=$$ JOB SHIPPED BACK TO HOST
)IM C1BMXHJC
//CONFCOPY EXEC PGM=NDVRC1,
// PARM='&VNBCPARM,CONF,RCPY,AB,****,$DEST_ID'
)IM C1BMXLIB
$$
//SYSUT2 DD SYSOUT=(INTRDR,A)
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
Note: If you perform shipments using the ISPF interface and the API interface, apply your
customizations to both models in the CSIQOPTN library and the JCL/PROCLIB supplied in
the CSIQJCL library.
Request Queue
CA Endevor® SCM stores ship requests in a queue until they are executed. The queue is active only
for the current CA Endevor® SCM session.
Display the Queued Shipment List by typing 2 in the OPTION field on the Package Shipment panel
and pressing ENTER.
Reset the Queued Shipment List by typing 4 in the OPTION field on the Package Shipment panel
and pressing ENTER. This deletes all shipments from the queue.
04-May-2018 846/1109
CA Endevor® SCM - 17.0
Submit the request queue by typing 3 in the OPTION field on the Package Shipment panel and
pressing ENTER. When you submit a shipment request, CA Endevor® SCM automatically resets the
queue.
Use the scroll left/right (PF10/PF11) to alternate between the available views; showing the local
(host) shipment status or the remote copy, and script execution status.
Note: The shipment records displayed are filtered according to the Package and
Destination values supplied on the Shipment panel. To change the filter, hit PF3 to back out
a level and enter a value or mask, or leave these fields blank to display all shipment
records.
TO DESTINATION destination-name
Indicates the one- to eight-character name of the remote site to which you want to ship the
specified Package. The destination name can be alphanumeric, but must begin with an alphabetic
character.
This information is required. If you do not enter a destination here, a SET DESTINATION statement
with the appropriate information must have been previously coded.
OPTION OUTPUT/BACKOUT
Indicates whether you want to ship output members or backout members to the remote site. If
you do not indicate an option here, the System looks for a SET OPTION statement. If no SET
OPTION clause is found, the System defaults to Option Output, and automatically ships output
members to the remote site.
OUTPUT
04-May-2018 847/1109
CA Endevor® SCM - 17.0
OUTPUT
Indicates that you want to ship the members created by the execution of the Package.
BACKOUT
Indicates that you want to ship the members needed to backout a Package.
PREfix prefix
Indicates the one- to eight-character data set name prefix to be used in the XCOM or CONNECT:
DIRECT transmission methods. If the transmission method selected is not XCOM or CONNECT:
DIRECT, this option is ignored. More than one node can be specified for the Package Ship output
prefix, as long as the nodes, with separating periods, fit within the eight-character space.
You can specify different options for different package/destination combinations, however. The next
request is valid:
On occasion, a module can be affected by the execution of two different packages. If you try to ship
output members from one package and backout members from the other package to the same
destination, you receive an error message. For example, assume a module has been affected by the
execution of PKG01 and PKG02. A request similar to that shown next is invalid:
You can ship the two packages to the same destination if you use the same option, however.
Therefore, either of the next requests would be acceptable:
or
Note: The sequence of the Package Shipment Utility requests is unimportant. The utility looks at
the package execution dates.
04-May-2018 848/1109
CA Endevor® SCM - 17.0
You can use two SET statements with the Package Shipment Utility:
Because the SHIP statement does not require an option, however, you need not code this statement
at all. In this situation, the default option output is applied.
CLEAR statements apply only to SET statements; similar information entered in a SHIP statement is
not affected by the CLEAR statement.
Two CLEAR statements can be used with the Package Shipment Utility:
CLEAR DESTINATION
The CLEAR DESTINATION statement clears the destination specified in a previous SET statement.
CLEAR OPTIONS
The CLEAR OPTIONS statement clears the option specified in a previous SET statement.
04-May-2018 849/1109
CA Endevor® SCM - 17.0
The CA Endevor® SCM administrator can use the following tools to monitor and review the shipment
of packages:
Display Shipment Status -- The Display shipment status option, accessible from the Package Ship
Destination panel, lets you view a scrollable list showing shipment status, including staging,
remote copy, and script execution status. For more information, see Display Shipment Status (see
page 847).
SHIPMENT OF MODULES or COMPLEMENTARY FILE; the former is the requested shipment and
the latter is a backout of the shipment.
The destination.
04-May-2018 850/1109
CA Endevor® SCM - 17.0
Detail lines follow the header. There is one detail line for each member in each package being
shipped from the host data set to the destination mentioned in the header. If a member is in more
than one package, it is listed multiple times. Each detail line contains the following information:
Action
Indicates how the shipment utility handles the member. Possible values are COPY, DELETE, and
BYPASS.
COPY
Indicates that the member was copied to the host staging data set and will be shipped.
DELETE
Indicates that an IDCAMS DELETE command will be shipped to the remote site.
BYPASS
Indicates that the member is in multiple packages and this occurrence of the member is not
being shipped.
Mbr-Name
The name of the HOST data set member.
Option
Indicates the shipment option. Possible values are OUTPUT and BACKOUT.
OUTPUT
Indicates that the member being shipped is part of the package output.
BACKOUT
Indicates that the member being shipped is the backout of the package member.
Package Name
The name of the package in which this member is a participant.
04-May-2018 851/1109
CA Endevor® SCM - 17.0
Following all the detail lines for a given data set are eight trailer lines, which contain the following
information:
The first two show how many members were copied and how many will be deleted.
The next four show the correspondence between output data set names and staging data set
names at the host and remote site. If a DSNAME Mapping Rule was set up to exclude transmission
of this data set, the "HOST LIBRARY DSN:" line is marked "* DATASET EXCLUDED FROM
TRANSMISSION *."
The final two lines show the DSNAME Mapping Rule which was used to generate the "REMOTE
LIBRARY DSN." If blank, the host data set name is used as the remote data set name.
Note: Shipment reports and Footprint reports are mutually exclusive. If you need both
report types, submit two separate jobs or two separate jobsteps within the same job.
04-May-2018 852/1109
CA Endevor® SCM - 17.0
The Shipment Confirmation Email Notification feature is in effect for any shipment request, whether
initiated from CA CM Enterprise Workbench, an API program, or a CA Endevor® SCM online Ship
action.
This feature is implemented using the existing Email Notification Facility. The Email Notification
Facility's Notification Facility table, ESMTPTBL, is shared with other features, such as override signout
notification and package approval notification. However, you can disable the shipment confirmation
feature by enabling the SUPPRESS_SHIPCONF_EMAIL option in the Optional Features Table,
ENCOPTBL.
Note: For more information about the Email Notification facility, see Notification (see page
263).
04-May-2018 853/1109
CA Endevor® SCM - 17.0
Why Do a Backout?
If you discover a problem after executing a Package, or if the execution failed, you can undo the
effects of the execution using Package backout (backout processing). For example, assume that your
Package executed successfully, but you know or suspect that the execution caused problems
elsewhere in the system. You can undo the execution and return the outputs of the Package to the
state they were in before being executed. After you use backout processing to back out the outputs,
if you decide that you want to return the outputs to the executed state, you can use Package backin
(backin processing) to undo the backout processing.
Package backout returns Package outputs to their prior state. Package backin reinstates the outputs.
Backout and backin processing can be used to back out and back in the following outputs:
An Entire Package— All output members and USS files (produced through the ENUSSUTL
processor) of a specific Package, that is the entire Package.
An Element action— All the output members and files of a single action within a specific Package,
without backing out the entire Package. However, if there are multiple actions within the Package
that produce the same output member and file, the Package is not eligible for Element Action
Backout. This option is particularly helpful if your site uses large Packages to move many
elements through the lifecycle.
By flagging the element in the MCF, CA Endevor SCM knows that the executables were backed out
even if the source was not backed out. CA Endevor SCM warns users who later attempt to retrieve
the backed out element that they are working with a backed out copy.
If you want to restore the prior level of source, you can do this by selecting the S option (Summary of
Levels) from the Retrieve Elements panel. The prior level of source, after retrieval, can then be added
back into CA Endevor SCM, creating a new change level and preserving the audit trail of the bad
change.
04-May-2018 854/1109
CA Endevor® SCM - 17.0
Restrictions
Backout processing affects CA Endevor SCM output libraries, not base and delta libraries. If reverse
delta format is being used, the base library member is not backed out. Also any outputs that are
written to CA Endevor SCM libraries, such as listings, are not backed out.
Dependencies between Packages affect backout of Packages and Element actions. Before you back
out a Package or Element action, you must be aware of any dependencies between Packages.
Consider the following situations and how they can affect backout.
Note: If Package backout, backin is not possible in any of the following cases, then Element Action
backout, backin is also not possible.
More than one Package moves the same element to the same location:
For example, assume you execute Package, PKG1, which moves elements COPYA, COPYB, COPYC,
and COPYF to the next location. Then you execute Package, PKG2, which also moves element
COPYF, as well as elements COPYD, and COPYE to the same location. Next, you decide that you
need to back out PKG1. Because PKG2's execution has affected element COPYF, which is common
to both Packages, you must back out PKG2 first, or the element will not be returned to its
appropriate pre-execution state.
A later Package moves an element from the target location of an earlier Package:
If the action is executed in a Package with backout in effect, the Package dependencies remain
valid as long as the elements remain at the target stage, or at the source stage for Delete, Archive
and Generate actions. For example, if Package PKG1 moves an element to one stage and Package
PKG2 moves this element to the next stage, then you will not be able to back out PKG1 after the
execution of PKG2. The reason for this is that the move action manages backout information only
for its target location, not its source location.
An element's outputs are executed outside of a Package or in a Package with backout disabled:
Actions affecting an element's outputs executed outside of a Package (or in a Package with
backout disabled) will invalidate the backout information for the last Package and all previous
Packages depending on that Package.
Prerequisites
You can only back out Packages that are defined with the option Enable Backout. The Enable Backout
option creates backout members for the element outputs that are created or modified by the
execution of the CA Endevor SCM actions, that is the processors associated with those actions. This
creation of backout members and USS backout files lets you back out a Package, restoring all output
members (load modules, listings, and objects), and USS files of the Package to their state before the
execution of the Package.
When you execute a backout, make sure that the processors do not use the IEBCOPY utility.
Processors whose output you want to back out can use the BSTCOPY utility. For more information
about BSTCOPY, see Processor Utilities.
04-May-2018 855/1109
CA Endevor® SCM - 17.0
Note: Before you back out a Package, you must consider dependencies between Packages as
described in the Restrictions section of this article.
1. Type 7 in the Option field on the Package Options Menu. Type a Package name in the Package
ID field. Press Enter.
Note: If you leave the Package ID field blank or type a name mask and then press Enter, a
Package Selection List will open. The Package Selection List shows only those Packages
available for your user ID, with a status of Executed, In-execution, or Exec-failed, that meet
the Package ID field criteria. If a Package Selection List displays, select the Package you want,
and then press Enter to display the Backout Package panel.
If the backout is successful, the Package Options Menu or the Package Selection List is
returned immediately.
If the backout is not successful, the Package Backout Report appears, indicating why the
backout failed.
1. Type 7 in the Option field on the Package Options Menu. Type a Package name in the Package
ID field. Press Enter.
Note: If you leave the Package ID field blank or type a name mask and then press Enter, a
Package Selection List will open. The Package Selection List shows only those Packages
available for your user ID, with a status of Executed, In-execution, or Exec-failed, that meet
the Package ID field criteria. If a Package Selection List displays, select the Package you want,
and then press Enter to display the Backout Package panel.
04-May-2018 856/1109
CA Endevor® SCM - 17.0
2.
If the backin is successful, the Package Options Menu or the Package Selection List returns
immediately.
Note: The next time the Backout Package panel is accessed, the BACKED IN field contains
user ID, date, and time information.
If the backin is not successful the Package Backin Report is returned, indicating why the
backin failed.
You cannot use this feature for Packages that have multiple actions that produce the same output
member.
Note: If a Package is partially backed out using the EO Element Backout option on the Element Action
Backout panel, you can back in the entire Package using the BI Backin Package option or back out the
entire Package using the BP Backout Package option on the Backout Package panel.
Note: Before backing out an element action, you must consider dependencies between Packages as
described in the Restrictions section of this article.
1. Type 7 in the Option field on the Package Options Menu. Type a Package name in the Package
ID field. Press Enter.
Note: If you leave the Package ID field blank or type a name mask and then press Enter, a
Package Selection List will open. The Package Selection List shows only those Packages
available for your user ID, with a status of Executed, In-execution, or Exec-failed, that meet
the Package ID field criteria. If a Package Selection List displays, select the Package you want,
and then press Enter to display the Backout Package panel.
Note: You can scroll to the right on the Element Action Backout panel to view information
about each action.
Note: The EB option may be highlighted on the Backout Package panel for a Package that
does not qualify for this option. If you select the EB option for a Package that does not qualify
for element action backout, the EB option grays out. This product behavior avoids the
overhead of examining all of the backout records in a Package before the EB option has been
selected.
3. Type EO in the selection column to the left of the SCL Stmt column for each element action
04-May-2018 857/1109
CA Endevor® SCM - 17.0
3. Type EO in the selection column to the left of the SCL Stmt column for each element action
you want to back out. Press Enter.
The output members for the element actions you selected are backed out.
Package A was created and executed. When executed, it moved element X and element Y to
Stage 2.
Then Package B was created and executed. When executed, it moved element Y to the next
environment.
If you attempt to perform an element backout on element X from Package A, the backout fails with
the following message:
The backout fails, because a Package element backout request is checked at the Package level, before
it is checked at the element level. In this case, because Package B acted on an element in Package A,
no elements in Package A can be backed out.
Note: If a Package is partially backed out using the EO Element Backout option on the Element Action
Backout panel, you can back in the entire Package using the BI Backin Package option or back out the
entire Package using the BP Backout Package option on the Backout Package panel.
1. Type 7 in the Option field on the Package Options Menu. Type a Package name in the Package
ID field. Press Enter.
Note: If you leave the Package ID field blank or type a name mask and then press Enter, a
Package Selection List will open. The Package Selection List shows only those Packages
available for your user ID, with a status of Executed, In-execution, or Exec-failed, that meet
the Package ID field criteria. If a Package Selection List displays, select the Package you want,
and then press Enter to display the Backout Package panel.
04-May-2018 858/1109
2.
Note: You can scroll to the right the Element Action Backout panel to view information about
each action.
3. Type EI in the selection column to the left of the SCL Stmt column for each element action you
want to back in. Press Enter.
The output members for the element actions you selected are backed in.
1. Type 7 in the Option field on the Package Options Menu. Type a Package name in the Package
ID field. Press Enter.
Note: If you leave the Package ID field blank or type a name mask and then press Enter, a
Package Selection List will open. The Package Selection List shows only those Packages
available for your user ID, with a status of Executed, In-execution, or Exec-failed, that meet
the Package ID field criteria. If a Package Selection List displays, select the Package you want,
and then press Enter to display the Backout Package panel.
2. Type one of the following options in the Option field and press Enter.
B - Display backout Information for data sets. This option opens the Dataset Backout
Information panel. That panel shows the member name, backout status, and data set
name.
BU - Display USS backout information. This option shows the file name, path name, and
backout status
BU - Display backout information for USS supported files. This option opens the USS
Backout Information panel. That panel shows the file name, backout status, and path
name.
CI - Display correlation information. This option is only visible if correlation records exist
for this Package. Correlation records could exist if they were created for enterprise
Packages created in CA CMEW. Correlation records could also have been created if your
site is using the CA Endevor SCM Interface to InfoMan.
A panel opens that corresponds to the option you selected for the specified Package.
04-May-2018 859/1109
CA Endevor® SCM - 17.0
The validation section of this report tells you which outputs will be backed out, and their status after
backout is complete. Output can be as follows:
Recovered as of Package (N/A) The outputs were not associated with any Package before the backed
out Package was executed. Recovered as of Package Package ID The outputs were associated with
the named Package before the backed out Package was executed. Deleted The outputs did not exist
before the backed out Package was executed.
The backout section of the report tells you which outputs were backed out and their status when the
backout was completed.
LLACOPY
The use of LLACOPY by CA Endevor SCM prevents incorrect directory entries from being created in
the processes of creating and using backout entries and in writing footprints.
LLACOPY is a macro that is provided with the operating system to enable a program to cause the LLA
directory to be refreshed with current information from the directory of a given library. CA Endevor
SCM issues the LLACOPY macro when it detects a STOW operation to force the refresh.
The LLACOPY macro is issued within CA Endevor SCM to make sure that, when CA Endevor SCM
performs more than one update of a PDS or PDSE directory entry in succession, the second of the
updates will have access to the changes that resulted from the first update. This is of particular
importance in the writing of CA Endevor SCM footprints, and in the writing and using of Package
Backout entries in libraries of load modules or program objects.
Whenever CA Endevor SCM activity has identified that the STOW SVC has been issued to update a
library directory entry, the LLACOPY macro is issued. However, CA Endevor SCM does not determine
whether a given library is LLA managed before issuing the LLACOPY call as that determination is made
by the operating system modules that receive control when the LLACOPY macro is invoked.
If Package execution is occurring and the Package Backout option in effect, and, if an existing
member is being replaced in a library, then CA Endevor SCM performs additional activities related to
performing the LLACOPY. CA Endevor SCM first issues an LLACOPY to ensure that it has current
directory information for the library member and to verify that the member exists in the library. CA
Endevor SCM then issues a STOW to create a directory entry for a Backout copy of the member. This
STOW is followed by an LLACOPY to update the LLA directory.
In all cases, an LLACOPY will be performed after the STOW of the new copy of the member has been
completed. There are instances where CA Endevor SCM does not perform LLACOPY calls, such as
when PMO and PDSMAN are handling the updating of directory entries.
04-May-2018 860/1109
CA Endevor® SCM - 17.0
After a STOW has been done within CA Endevor SCM, the given directory entry will be immediately
reflected in the LLA directory.
04-May-2018 861/1109
CA Endevor® SCM - 17.0
As a change manager ( CA Endevor® SCM administrator), you can use the BPI to set up a complete
implementation of CA Endevor® SCM that incorporates best practices. This method lets you easily
and quickly allocate and populate the libraries that support the software development lifecycle. The
BPI is delivered as a set of input tables and jobs that you configure and run.
04-May-2018 862/1109
CA Endevor® SCM - 17.0
3. Run BPISTART. (see page 875) This job allocates the BPI libraries.
5. Edit #JOBCARD to prepare the BPI job card. (see page 885)
6. Edit #OPTION. (see page 886) This member defines symbol values that are used to resolve
variables defined in the BPI models and REXX members.
7. Submit the BPI jobs. (see page 886) We recommend that you execute the BPI process in
iterations implementing one System or application at a time.
8. Verify the implementation. Access your implementation and make sure it was created and
setup successfully.
9. Load your software inventory. We recommend that you complete setting up the BPI, before
you load any inventory.
We recommend that you execute the BPI process in iterations. For the first iteration, you might
implement one System (or application). This lets you become familiar with how to edit the input
tables and how the jobs work. After the first iteration, you could execute the BPI to implement an
entire application. (An application can consist of multiple Systems and Subsystems.) Then you could
do additional iterations, one for each additional application. For the first iteration, you perform all
the steps. For subsequent iterations, you re-edit the BPI input tables and then rerun the jobs
beginning with job #5ALLOC. For more information about performing the steps in iterations, see The
Iterative BPI Process (see page ).
Review Prerequisites
Before attempting this implementation, verify that the following prerequisites are complete.
Verify that CA Endevor® SCM is properly installed at your site. For more information about the
installation steps, see Installation Tasks for the Systems Programmer (https://docops.ca.com/display
/CE17/Installation+Tasks+for+the+Systems+Programmer). Proper installation has the following
requirements:
The CA Common Services components CA LMP and CAIRIM for product licensing and
authorization must be installed and customized.
Note: The components CAIENF and CAICCI are not required for the BPI. However,
these components are required if you want to use CA Endevor® SCM with the
Concurrent Action Processing feature, the Web Services component, or the companion
product CA CMEW. CAIENF and CAICCI can be configured after you complete the BPI.
04-May-2018 863/1109
CA Endevor® SCM - 17.0
If your site has multiple CPUs sharing DASD, you must define queue names. If you are using
Unicenter CA-MIM Resource Sharing or IBM Global Resource Serialization (GRS), include the
queue names in the appropriate Global Resource Queue Name Table.
If CA ACF2 is the security software used at your site, modify the TSO Command Limiting
Facility to allow ISPTLIB commands (ACMQ, BC1PACMI, ESORT, EONLY, EM, QM, and so on).
The following BPI installation considerations apply depending on how CA Endevor® SCM is
configured at your site:
The BPI assumes your site is licensed for the following product options:
If you use LINKLIST or LPA libraries for the CSIQAUTH/CSIQAUTU data sets, tailor the jobs
created by the BPI process prior to submission. Remove, or comment out, the STEPLIB DD
statements from the job members created in the BPILIB library before submitting the job.
If you use LINKLIST or LPA libraries for the CSIQLOAD data set, tailor the jobs created by the
BPI process prior to submission. Remove, or comment out, the STEPLIB and CONLIB DD
statements from the job members created in the BPILIB library before submitting the job.
The person performing the BPI needs the following general knowledge of the mainframe
04-May-2018 864/1109
CA Endevor® SCM - 17.0
The person performing the BPI needs the following general knowledge of the mainframe
environment and a basic understanding of the CA Endevor® SCM.
You need a working knowledge of the mainframe environment, the z/OS mainframe operating
system, the Time Sharing Option facility (TSO), and the Interactive System Productivity Facility
(ISPF).
Become familiar with the basic CA Endevor® SCM concepts. For more information, see
Installing (https://docops.ca.com/display/CE17/Installing)and Administrating (see page 36).
Become familiar with the Best Practice Implementation concepts. For more information about
the BPI concepts, see the BPI Software Inventory Lifecycle (see page 865).
The lifecycle defines the movement of your software inventory through a set of data set libraries.
These lifecycles are defined in the Defaults table (C1DEFLTS). A data set naming convention supports
the lifecycle structure. The Best Practice Implementation sets up the following lifecycles or maps:
Standard Map
For regular development activities. The Standard Map is where most activity occurs. The Standard
Map starts with the DEV environment, at entry stage, stage 1. From DEV Stage 1, source is
promoted to DEV Stage 2, then to QAS stage 2, and finally PRD stage 2. Stage one for the Quality
Assurance and Production environments are skipped. DEV stage 2 maps to QAS stage 2, and QAS
stage 2 maps to PRD stage 2.
Emergency Map
For emergency fixes. The Emergency environment maps also to PRD stage 2.
Unclaimed Map
For unclaimed or unclassified elements. The Unclaimed environment has an entry stage of 2. This
environment does not map to any other environment.
Archive Map
For archived elements. The Archive environment has an entry stage of 2. This environment does
not map to any other environment.
Administrator Map
04-May-2018 865/1109
CA Endevor® SCM - 17.0
Administrator Map
For the CA Endevor® SCM Administrator activities. The Administrator environment has an entry
stage of 1. This environment does not map to any other environment.
BPI lifecycle
04-May-2018 866/1109
CA Endevor® SCM - 17.0
04-May-2018 867/1109
CA Endevor® SCM - 17.0
Previously if you were not using the BPI method, CA Endevor® SCM used two sets of high and second
level qualifiers for data set naming (iprfx.iqual and uprfx.uqual). The first set was reserved for the CA
Endevor® SCM installation runtime data sets. These data sets were prompted for during the
installation process (job BC1JJB03). The second set was used as the prefix for all the CA Endevor®
SCM data sets that were created (element catalog, MCFs, package file, base and delta files, processor
output libraries, and so on).
When you configure CA Endevor® SCM using the BPI, you must specify four high level qualifiers for
the CA Endevor® SCM data sets. The installation runtime qualifier (iprfx.iqual) remains the same. The
remaining three high level qualifiers are specified in the BPI Option member. Having these multiple
high level qualifiers makes it easier for administrators to establish and maintain security rules, as well
as provide a visual distinction between the data sets. The three prefixes are as follows:
SiteHighLevelQual for all CA Endevor® SCM site-wide data sets. This includes element catalog and
index, ACM root and cross reference files, package file and Master Control files.
AdminHighLevelQual for all CA Endevor® SCM ADMIN environment data sets. This includes all
allocations for the ADMIN environment.
ApplHighLevelQual for all CA Endevor® SCM application data sets. This includes the base and
delta files for each of the standard application system, subsystem, and type combinations.
The maximum size for a data set name cannot exceed 44 characters, thus the maximum sizes allowed
for the three high-level qualifiers will depend on the system and subsystem names. You can use
multiple nodes within each high-level qualifier. The number of nodes is not important. However, the
CA Endevor® SCM data set names use a standard format consisting of the following, where the
maximum number of characters allowed are shown in parenthesis: system (8), subsystem (8), subset
of the environment name (3), stage number (1) and type (8). Using this standard, if you use the
04-May-2018 868/1109
CA Endevor® SCM - 17.0
of the environment name (3), stage number (1) and type (8). Using this standard, if you use the
maximum amount of characters for system, subsystem, and so on, then only 12 characters are left for
the high-level qualifier nodes. We recommend that the prefix nodes be 12 characters or fewer, if
possible. This is to avoid data set length problems in the future if additional systems, subsystems, and
types are created.
Type name is the last node of the data set name and reflects the language.
Provide High-Level Qualifier only, the BPI provides an ending qualifier. Processors also use this
naming convention.
Reverse delta format is used for most types. Some types are better suited for full image or log
delta format.
Centralized Processors
The Best Practice Implementation establishes a single repository location for processors instead of
having unique or custom processors that are defined and stored for each system. It is simpler to
maintain one set of processors and ensures consistency across systems.
The BPI process stores all processors in the administrator (ADMIN) environment.
Inventory Structure
The CA Endevor® SCM inventory structure allows you to do the following:
Work with program modules without having to know where they are physically located, or how
they are compiled.
List all the program components that make up an application, regardless of type.
Determine the locations of an element simply by entering the element name on a display screen.
Act on a cross section of your program inventory. For example, CA Endevor® SCM allows you to
list all COBOL code in your shop, or promote an entire new release of the payroll application with
a single command.
04-May-2018 869/1109
CA Endevor® SCM - 17.0
With the BPI, a predefined inventory structure is included. The structure (environments, systems,
subsystems, types, and so on) is outlined in rows within table file members.
The BPI provides the following default definitions for the inventory structure components.
Environments
The default environment names are delivered in the BPI input table, T#ENVMTS. Each data row
consists of the environment name and stage information.
Note: BPI REXX member, O#ENVMTS located in BPILIB must remain in sync with
T#ENVMTS.
The rows in these tables are used to build the software change lifecycle (established within the
C1DEFLTS table), the CA Endevor® SCM configuration tables, and to build SCL members. You specify
what environments you want to create, the environment stage names, and the entry stage for that
environment. Also, you specify how these are mapped -- the next environment to map to and the
next stage of that environment to map to.
Systems
The default system names are delivered in members T#ADMSYS and T#SYSTMS. Each data row
consists of a system name and a description. T#ADMSYS is used solely for the ADMIN environment.
The ADMIN environment, as delivered, contains one system and subsystem. It is required that you
keep the administrative environment. The BPI defaults to creating the first ADMIN system specified in
T#ADMSUB as the main repository of all the CA Endevor® SCM processors and configuration tables
that the remaining application systems use. The system name for the Processor Output Libraries
defaults to the first system specified in T#ADMSYS. You can add additional systems to the ADMIN
environment, by adding additional rows to the T#ADMSYS table.
T#SYSTMS table is used by all the environments defined in the T#ENVMTS table except for
Administrator and Unclaimed environments. That includes the Development, Quality Assurance,
Production, Emergency, and Archive environments in the delivered table.
This T#SYSTMS table is related to the T#SUBSYS table. If you add or remove a system row from the
T#SYSTMS table, add or remove the associated rows in the T#SUBSYS table.
The system definition defaults delivered with the BPI are as follows:
Comments Required
CCID Required
04-May-2018 870/1109
CA Endevor® SCM - 17.0
Signout is Active
Subsystems
The default subsystem names are delivered in members T#ADMSUB and T#SUBSYS. Each row consists
of a system name, subsystem name and a description. Any system specified in T#SUBSYS must match
a system specified in T#SYSTMS. Any system specified in T#ADMSUB must match a system specified
in T#ADMSYS
The delivered subsystem definition specifies that the Next Subsystem defaults to the current
subsystem.
Types
The default type names are delivered in members T#ADMTYP and T#TYPES. The T#ADMTYP member
is used to define types for the Administrator environment and the T#TYPES member is used to define
types for the Development, Quality Assurance, Production, Emergency, Unclaimed, and Archive
environments. The length of the data in each row of these members is 200 characters. Each row
consists of a type name, processor group name, generate, move and delete processor names,
foreground allowed flag, language, Panvalet and Librarian source languages, compare from and
compare to columns, element delta format, and type and processor group descriptions. When a type
is defined during the BPI process, the first processor group listed for each type is the default
processor group.
Note: If the BPI process is executed and your site did not purchase the Extended Processor
option, the implementation fails at the point when the DEFINE TYPE PROCESS action is
executed. The execution of this action results in a return code of 12 when CA Endevor®
SCM performs a check against the PROC parameter value in the C1DEFLTS configuration
table and determines this option is not activated.
Regression Threshold is 80
04-May-2018 871/1109
CA Endevor® SCM - 17.0
HFS Recfm NL
Note: The Regression Percentage Threshold is automatically set to 80, except for LOG or
IMAGE delta formats, where it is set to 0.
Processor Groups
The processor group and processor names are included in members T#ADMTYP and T#TYPES with the
type attributes.
One exception to the naming standard is for the special Endevor processor group used by the type
PROCESS. The name of this processor group is PROCESS.
The processor group definition defaults delivered with the BPI are listed below:
If the entry stage of the environment is stage 1, it uses the Generate processor. The
production environment always uses the Move processor
The Allow or Do Not Allow is specified in the T#ADMTYP and T#TYPES table. The Unclaimed
and Archive environments uses Allow for all types
Generate/Move/Delete Processors
The processor names are be taken from the T#TYPES table, except for type PROCESS, which
always uses the Endevor processor names. The Unclaimed and Archive environments set all
processor values to *NOPROC* for all types
04-May-2018 872/1109
CA Endevor® SCM - 17.0
Processor Symbols
Processor group symbol overrides are created in #3ADMIN and #9DEFGRP, to coincide with the
delivered BPI processors in CSIQSAMP. There are two tables within the #3ADMIN JCL that define
what symbols need to be created for the administrator environment. The standard environments use
the T#SYMBLS table. Processor symbols can be a length of eight characters and the override values
can be up to 65 characters. As delivered, processor symbol overrides are required, because a single
processor is shared across multiple processor groups. You have the flexibility to change or add to the
delivered processor symbol definitions by editing #3ADMIN or T#SYMBLS.
The processor symbols definition defaults delivered with the BPI are listed below:
04-May-2018 873/1109
CA Endevor® SCM - 17.0
Configuration Tables
CA Endevor® SCM configuration table source is delivered in the iprfx.iqual.CSIQSRC deployment
library. New C1DEFLTS and ESYMBOLS configuration table source is built by the BPI process, based on
information specified in the table input members located in the BPIDATA data set and information
specified in the #OPTION member located in the BPILIB data set. None of the other configuration
table source is altered by the BPI process.
BPI job #1TABLES builds the two new tables and creates load modules for the C1DEFLTS,
ENCOPTBL, ENDICNFG and ESYMBOLS tables.
BPI job #3ADMIN builds an inventory location for the tables (ADMIN/ADMIN/ENDEVOR/TABLE/2)
and adds and promotes all the configuration tables to that location.
You can modify the source as required after the implementation is complete.
Note: When performing the Best Practice Implementation, we recommend that you set the WARN
parameter to YES in the CA Endevor® SCM configuration table, BC1TNEQU. When WARN=YES, the ESI
warning mode is in effect. Warning mode allows access to resources even if your site security
package (RACF, CA ACF2, or CA Top Secret) indicates that access should be denied. You should use ESI
Warning Mode when running the Best Practice Implementation. System Management Facility (SMF)
messages will indicate any authorization issues with data sets, but will not halt the BPI
implementation process. After running the implementation process, you can adjust your security
rules and change the WARN parameter to NO, if you prefer not to run CA Endevor® SCM in warning
mode. For more information about the WARN parameter, see The ESI Warning Mode in Securing (
https://docops.ca.com/display/CE17/Securing).
Concurrent Action Processing (CAP)— When CAP is specified for a batch job or packages
submitted for processing, certain element action requests are executed concurrently. CAP uses
Global Type Sequencing to determine which actions can be processed at the same time.
04-May-2018 874/1109
CA Endevor® SCM - 17.0
Autogen option for Add, Update, and Generate actions— When Autogen is specified for an
element, elements that use this component element are automatically generated. Autogen
requires Global Type Sequencing so that the elements that use a component are generated after
all of the components have been processed (for example, macros before source, source before
load modules).
To enable Global Type Sequencing during the BPI process, you define the type sequence order in the
table T#GLBSEQ. Types and System names need to match those you specify in the T#TYPES and
T#SYSTMS tables.
iprfx.iqual.CSIQSAMP
Skeleton, model, and BPI processor members
iprfx.iqual.CSIQCLS0
REXX procedures and REXX options statement members
iprfx.iqual.CSIQJCL
Job control statement members
iprfx.iqual.CSIQDATA
BPI input table members
The iprfx.iqual set of libraries is referred to as the deployment or runtime libraries. These are the
libraries that contain the product software that is executed. These members are edited by the
BC1JJB03 installation job as part of the installation process.
Run BPISTART
To start the BPI, you edit and submit the job, BPISTART.
1. Set the WARN parameter to YES in the CA Endevor® SCM configuration table, BC1TNEQU.
Note: When performing the Best Practice Implementation, we recommend that you
set the WARN parameter to YES in the CA Endevor® SCM configuration table,
BC1TNEQU. When WARN=YES, the ESI warning mode is in effect. Warning mode
allows access to resources even if your site security package (RACF, CA ACF2, or CA
Top Secret) indicates that access should be denied. You should use ESI Warning
Mode when running the Best Practice Implementation. System Management
Facility (SMF) messages will indicate any authorization issues with data sets, but will
not halt the BPI implementation process. After running the implementation
04-May-2018 875/1109
CA Endevor® SCM - 17.0
not halt the BPI implementation process. After running the implementation
process, you can adjust your security rules and change the WARN parameter to NO,
if you prefer not to run CA Endevor® SCM in warning mode. For more information
about the WARN parameter, see The ESI Warning Mode in Securing (https://docops.
ca.com/display/CE17/Securing) .
3. (Optional) Edit the SET LBPRFX=uprfx.uqual statement in BPISTART to override the uprfx and
uqual values specified in the BC1JJB03 installation job.
4. Add a valid job card statement and submit the BPISTART job for execution.
This job does the following:
Note: These libraries are modified during the BPI process. The delivered libraries is
not be modified and thus is available for backup if the BPI process needs to be
restarted for any reason.
Copies delivered and tailored members into the BPIDATA, BPILIB and BPIPRCR libraries.
The following libraries are created with the uprfx.uqual values specified in the BPISTART job:
uprfx.uqual.BPIDATA
Contains all the default input table members. This is a copy of the iprfx.iqual.CSIQDATA
library. These tables are used to define the inventory structure (environments, systems,
subsystems, types, processor groups, and so on.) to the BPI process jobs.
uprfx.uqual.BPILIB
Contains several members copied from other installation libraries, JCL members built by
the BPI process such as job #1TABLES - #9DEFTYP and several other files that are built by
the BPI process, including the C1DEFLTS and ESYMBOLS configuration table source. This is
the library the user works from to execute the BPI process jobs.
uprfx.uqual.BPIPRCR
Contains the source for the delivered BPI CA Endevor® SCM processors. They are added
into the Administrator environment by the #3ADMIN BPI job.
uprfx.uqual.BPIWRK
Contains temporary and intermediate members built by one of the BPI jobs or steps and
passed to another job or step later in the process. Examples include the SCL built by the
process to DEFINE SYSTEMs and SUBSYSTEMs. Other members are placed into this library
for support purposes in case any issues arise.
04-May-2018 876/1109
CA Endevor® SCM - 17.0
Edit each member in the BPIDATA library depending on how you decide to configure your
implementation. You can use conversion utilities, the ISPF Editor, upload from a word document, or
other methods may be used to modify or create these required tables.
Important: When editing tables, make sure that all changes conform to the table format
rules.
Important: How you customize the input tables depends on how many times you plan to
execute the BPI process. For more information about planning your implementation, see
The Iterative BPI Process (see page ).
Heading row
One heading row (single asterisk in column 1) must exist in each table.
The format of the delivered heading rows must not be changed in any way.
Data rows
All values in the data rows must be entered in upper case mode unless otherwise stated.
The data in the data rows must be placed in the same columns as the field literal in the
heading row.
Comment rows
Comment rows can be added anywhere within the table source by placing asterisks in
columns 1-2 of a row. When detected the row is ignored.
04-May-2018 877/1109
CA Endevor® SCM - 17.0
One DELTA, LISTLIB, LLISTLIB, LOADLIB, and OBJLIB library for each element type for the ADMIN
environment.
One base library for each element type for each system, subsystem, environment, stage. Each
base library has the following name format:
adminprfx. .&C1SY..&C1SU..&C1EN(1,3)&C1S#.typename
typename
Specifies a language version.
1. Add or remove element type rows to include the language types that are used at your site.
The type names appear in the table Node column.
2. Do not change the type names for PROCESS, TABLE, DELTA, LISTLIB, LLISTLIB, LOADLIB or
OBJLIB, because these have a specific meaning to CA Endevor SCM and must not be altered.
For these types, unless you are changing the format of the DELTA, LISTLIB, or LLISTLIB
libraries, limit your changes to the Sizeunit, Primary, Secondary, and Directory.
3. (Optional.) To define ELIB BDAM data sets for DELTA, LISTING, and LLISTING data sets, specify
the following values:
Note: The #OPTION member DELTA and LISTLIB data set format must be the same
as the format specified in the T#ADMALL member. By default, the DELTA, LISTLIB
and LLISTLIB are created as ELIB BDAM. You can leave them as is, or can change
them to PDS or PDSE by editing the table. For more information about ELIB BDAM
data sets, see Administrating (see page 36).
PrimPages -- Specifies the number of primary pages for the ELIB initialization
program to allocate. The value of this parameter is placed into the ALLOCATE PAGES
parameter;
SecdryPages -- Specifies the number of secondary pages for the ELIB initialization
program to allocate. The value of this parameter is placed into the ALLOCATE PAGES
parameter;
ResrvePages -- Specifies the number of pages for the ELIB initialization program to
reserve. The value of this parameter is placed into the RESERVE PAGES parameter;
04-May-2018 878/1109
CA Endevor® SCM - 17.0
DirPages -- Specifies the number of directory pages for the ELIB initialization
program to allocate. The value of this parameter is placed into the DIRECTORY
PAGES parameter;
Important: The same types must be listed in the T#ADMALL andT#ADMTYP tables.
If you add or remove type rows from any of these tables, you must make a
corresponding change to the other tables.
System: ADMIN.
Subsystem: ENDEVOR.
Important: The system names must be the same in each of these tables: T#ADMSYS and
T#ADMSUB. If you add or remove a system row from the T#ADMSYS table, you must add or
remove the associated rows in the T#ADMSUB table.
System: ADMIN.
The system name is used to build the following processor output libraries.
Important: The first system that is referenced in the table is used to build the processor
04-May-2018 879/1109
CA Endevor® SCM - 17.0
Important: The first system that is referenced in the table is used to build the processor
output library names.
system_name
Specifies the name of the system in the ADMIN environment.
Important: The system names must be the same in these tables: T#ADMSYS and
T#ADMSUB. If you add or remove a system row from the T#ADMSYS table, add or remove
the associated rows in the T#ADMSUB table.
1. Add or remove element type rows to include the language types that are used at your site.
2. Do not change the type names for PROCESS or TABLE, because CA Endevor SCM uses these to
hold the CA Endevor SCM processors and configuration tables and these must be set to the
values provided.
Important: The first processor group listed for each type is used as the default processor
group for that type.
Important: The same types must be listed in the T#ADMALL andT#ADMTYP tables. If you add or
remove type rows from any of these tables, you must make a corresponding change to the other
tables.
04-May-2018 880/1109
CA Endevor® SCM - 17.0
This table enables the creation of the following data sets for each element type that is defined in the
T#TYPES table.
One DELTA, LISTLIB, LLISTLIB, LOADLIB, and OBJLIB library for each element type for the
application or standard environment.
One base library for each element type for each system, subsystem, environment, stage. Each
base library has the following name format:
aprfx. .&C1SY..&C1SU..&C1EN(1,3)&C1S#.typename
typename
Specifies a language version.
1. Add or remove element type rows to include the language types used at your site. The type
names appear in the table Node column.
2. Do not change the type names for PROCESS, TABLE, DELTA, LISTLIB, LLISTLIB, LOADLIB or
OBJLIB, because these have a specific meaning to CA Endevor SCM and must not be altered.
For these types, unless you are changing the format of the DELTA, LISTLIB, or LLISTLIB
libraries, limit your changes to the Sizeunit, Primary, Secondary and Directory.
3. (Optional.) Specify the following values to define ELIB BDAM data sets for DELTA, LISTING, and
LLISTING data sets: (ELIB BDAM is the default.)
PrimPages
Specifies the number of primary pages for the ELIB initialization program to allocate. The
value of this parameter is placed into the ALLOCATE PAGES parameter;
ALLOCATE PAGES = (&PrimPages,&SecdryPages)
SecdryPages
Specifies the number of secondary pages for the ELIB initialization program to allocate.
The value of this parameter is placed into the ALLOCATE PAGES parameter;
ALLOCATE PAGES = (&PrimPages,&SecdryPages)
ResrvePages
Specifies the number of pages for the ELIB initialization program to reserve. The value of
this parameter is placed into the RESERVE PAGES parameter;
RESERVE PAGES = &ResrvePages
DirPages
Specifies the number of directory pages for the ELIB initialization program to allocate.. The
value of this parameter is placed into the DIRECTORY PAGES parameter;
DIRECTORY PAGES = &DirPages
The #OPTION member affects the UNCLMED environment and the PRD environments as follows:
04-May-2018 881/1109
CA Endevor® SCM - 17.0
library and the ProductionSizeFactor value is 3, the data set is allocated with 150 primary
cylinders. This factor is also applied to the Secondary and Directory columns when processing the
production environment. The ProductionSizeFactor is skipped when allocating ELIB DELTAs or
LISTINGs.
1. Add or remove environment rows to include the environments used at your site. All values in
the data rows must be entered in upper case character mode. The first three characters of the
environment name are used to build data set names. Therefore, the first three characters of
the names must be unique across environments. If the environment names do not contain
three characters, a pad character ($) is added to the environment name when allocating the
data sets for that environment.
2. Do not change the environments names for ADMIN, PRD, UNCLMED, or ARCHIVE, unless you
have business reason to do so. If you change these, you must also change the name in the
O#ENVMTS REXX member, located in the uprfx.uqual.BPILIB data set. The purpose of this
member is to identify which of the environments is the administrator, production, unclaimed
element and archive element environments.
3. If you decide you do not need the UNCLMED environment, comment out the UNCLMED row
in this table prior to executing the #1TABLES job. Job #1TABLES builds the C1DEFLTS table.
04-May-2018 882/1109
3.
Only types that must be executed in a specific sequence should be included in this table. Do not
include types such as JCL and PROCS in this table. Following this rule results in more efficient
throughput from the current action processing feature.
ACMROOT
ACM root and data sets.
ACMXREF
Cross-reference data sets.
ELMCATL
Element catalog data sets.
ELMCATL.EINDEX
Element catalog index data sets.
PACKAGE
Package file.
PARMLIB
Parameter library.
MCF
Master Control File for each environment-stage combination.
Do not add or remove any rows from this table, however, you should review the type of data set
specified in the MODEL column and the data set size attributes.
It is highly recommended that you do not change the Node, MODEL or TBLOUT values in this table.
DO NOT change the MCF name. If you have a business reason to change one of the other node
names, you must also change the name in the O#LIBRYS REXX model, located in the iprfx.iqual.
CSIQCLS0 data set.
04-May-2018 883/1109
CA Endevor® SCM - 17.0
1. Change the default to the Systems and Subsystems appropriate for your business model.
2. Add or remove corresponding rows in the T#SYSTMS table, if you changed the T#SUBSYS table
in step 1.
This table contains the symbol overrides to be defined for the standard environments. You must
specify the type, processor group, environment, stage, processor type, symbol, and override value for
each row in the table. You can wildcard the processor group, environment, and Stg# columns.
However, no partial wildcarding is supported for the environment or stage column.
The stage column if wildcarded, creates symbol definitions for stage 1 and stage 2.
The environment column if wildcarded, creates symbol definitions for all environments (DEV, QAS,
PRD, EMER) except for ADMIN, UNCLMED, and ARCHIVE. They are excluded because the
Administrator environment has symbol creation steps in #3ADMIN, and the Unclaimed and Archive
environments set processors to *NOPROC*. However, you may define symbols for any of the
environments by creating a unique row for that location in the table, placing the environment name
directly in the Envname column. In other words, although the wildcarding feature excludes the
Administrator environment, you can still create symbols for that environment using this table, by
placing ADMIN in the Envname column.
All symbol definitions with wild carded environments is created first, followed by specific symbol
definitions, allowing for additional flexibility when establishing the symbol rows. There are many
processor symbolic overrides being created, as delivered. You can delete or add additional rows to
the symbol table as needed.
04-May-2018 884/1109
CA Endevor® SCM - 17.0
This table is related to the T#SUBSYS table. If you add or remove a system row from the T#SYSTMS
table, you must add or remove the associated rows in the T#SUBSYS table.
Do not alter the values in the PROCESS rows. This type is used to hold the CA Endevor SCM
processors and must be set to the values provided.
If type definition rows are added or removed from the T#TYPES table, the corresponding row must be
added or removed from the T#ALLOC table. The T#GLBSEQ table should also be reviewed to
determine if rows must be added or removed from that table.
//BPI@ENDV JOB (#########),'BPI &TBLOUT ',
// CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1),
// NOTIFY=&SYSUID
Note: When the #0SETUP job is executed, this job card is automatically placed at the
beginning of each of the other BPI jobs.
Note: After the BPISTART job is executed, the remaining BPI process is executed from the
BPILIB library.
04-May-2018 885/1109
CA Endevor® SCM - 17.0
Edit the uprfx.uqual.BPILIB(#OPTION) member and answer all the questions. The questions are in the
format of REXX comments and the answers are in the format of REXX statements. These statements
are used as symbol values during the implementation process. For example, many of the C1DEFLTS
table site parameter values are derived from the information specified in this member. The literals on
the left side of the equal symbols are REXX variables and must remain in mixed character mode. The
values you enter on the right side of the equal symbols are data values and must be entered in upper
case character mode, unless otherwise stated; for example, comments, descriptions and notes can be
entered in mixed character mode.
5.
04-May-2018 886/1109
CA Endevor® SCM - 17.0
11. Manually delete the uprfx.uqual.BPIWRK library after every iteration of the BPI process. The
BPIWRK data set provides no value once the implementation is complete.
1. Submit BPISTART.
5. Execute the BPI jobs #0SETUP through #9DEFGRP, and submit the additional jobs that get
created.
04-May-2018 887/1109
CA Endevor® SCM - 17.0
For the second and subsequent iterations, do the following:
2. Execute BPI jobs #5ALLOC through #9DEFGRP, and submit the additional jobs that get created.
3. Repeat these steps as many times as needed to add all the Systems you want to put under the
control of CA Endevor® SCM at this time.
04-May-2018 888/1109
CA Endevor® SCM - 17.0
Business Value:
Full volume backups run more quickly than CA Endevor® SCM full unloads. For disaster recovery, you
could restore from the full volume backup, and then add data from the incremental unload.
Additional Considerations:
The Unload/Reload utility (program C1BM5000) is a backup, recovery, and file validation mechanism
for CA Endevor® SCM VSAM control files (Master Control File, package data sets) and their related
base and delta libraries. It allows users to backup (unload), restore (reload), and/or validate the
integrity of one or more CA Endevor® SCM environments in the event of a physical device failure or
site disaster.
The Unload/Reload utility creates a file from which individual elements can be retrieved should one
be accidentally deleted. It also ensures that there is no loss of synchronization among the CA
Endevor® SCM files, which can occur during the full volume backups.
Business Value:
With CA Endevor® SCM making extensive use of VSAM to maintain the control information, it can, in
larger installations, incur some performance bottlenecks mainly caused by VSAM open and close
processing. Using VSAM RLS can help improve overall performance.
04-May-2018 889/1109
CA Endevor® SCM - 17.0
With the grouping capability, the application continues to dispatch element actions from the
sequenced type chain as long as the group category value matches the previous request. Available
STCs will only have to wait if sequenced type requests from one group category value are still
processing and there are no non-type sequenced requests to process.
Business Value:
If you have bulk moves of large numbers of elements in a package or batch job, it can take a long
time to complete the moves. Concurrent Action Processing speeds processing of batch jobs and
packages, greatly reducing processing time. This feature enables CA Endevor® SCM to exploit
additional capacity on z/OS platforms to simultaneously execute certain element action requests,
which reduces the elapsed time it takes to process multiple actions. An increase in throughput is
immediate after Concurrent Action Processing has been activated.
Additional Considerations:
04-May-2018 890/1109
CA Endevor® SCM - 17.0
Forward and reverse deltas let you manage the changes made to an element, and they have the
same performance characteristics in terms of storage. The difference is in what CA Endevor SCM
considers to be the base level.
For forward deltas, the base element is the original code, and the delta levels correspond to the
changes made to that code. When you want a copy of the latest version of an element, CA
Endevor SCM has to merge the base and delta levels using the CONWRITE utility.
Forward deltas are useful when elements are relatively stable, because when the element is
saved, CA Endevor SCM only writes the changes to a file and does not rewrite the full source text.
For reverse deltas, the base element is the current copy of the code, and the delta levels contain
the information needed to return the element to its original form. When you want a copy of the
latest version of an element, CA Endevor SCM (or any other program) can ignore the delta levels
and simply read the base element. This behavior also improves processor performance, because
CA Endevor SCM does not need to invoke the CONWRITE utility to rebuild the element.
Reverse deltas are useful when you are compiling an element frequently, because CA Endevor
SCM does not have to merge in the delta files. However, when an element is saved, CA Endevor
SCM has to replace the entire base level in addition to saving the changes in the delta library.
Note: Backout processing requires a source output library that cannot be the same data set
as the reverse delta base library.
04-May-2018 891/1109
CA Endevor® SCM - 17.0
The following table summarizes the forward and reverse delta formats.
Are in production.
Reverse 1 2 Normally needed a source output library but do not need to be
backed out. These files need to be kept in a standard format (such
as a PDS) for utilities such as Advantage CA File Master.
Note: For more information about the conversion process, see Converting Delta Formats
(see page 258).
04-May-2018 892/1109
CA Endevor® SCM - 17.0
For each Type to be activated, navigate to the Type Definition panel in foreground and set AUTO
CONSOL to N and LVLS TO CONSOL to 0. If you were not previously using Auto Consolidation, and had
not changed these fields, these values are already set.
Alternatively, run the Batch Admin DEFINE TYPE action to set these field values for each Type to be
activated. With Auto Consolidation turned off, you may eventually run out of levels or accumulate
more levels than you really need.
Note: For the most efficient level consolidation across environments, set this parameter to
the maximum value of 96.
Merges levels 01 through 25 together to create a single delta level (level 01)
When working in the lower stages where the level number is not equal to the physical number of
levels, Auto Level Versioning is used to increase or “roll over” the vvll value until the number of
physical levels specified on CONSOL AT LVL is reached.
Using the same consolidation values as in the prior example, suppose an element at vvll 0194 is
04-May-2018 893/1109
CA Endevor® SCM - 17.0
Using the same consolidation values as in the prior example, suppose an element at vvll 0194 is
retrieved from the production stage for modification. When it is added back into CA Endevor SCM
at a lower stage, level 0194 is fetched back for compare and level 0195 is created. The level
number is 95, but the number of physical levels is two-- 0194 and 0195. For auto consolidation to
be triggered in this lower stage, 94 more changes would have to be made to get up to 96 physical
levels. Auto versioning comes into play when vvll 0199 is reached, the next change would roll over
to 0200, then 0201 and so on until 0290 is reached (0194+96=0290), should one more change be
attempted auto consolidation would be triggered causing the lower 25 levels, 0195 through 0220,
to become a new 0195, and levels 0221 through 0290 to be renumbered accordingly.
Determine the maximum and minimum number of levels you want to store on the system. Using
these values, you can calculate the number of levels to consolidate (LVLS TO CONSOL). The
maximum value is specified in the consolidate level (CONSOL AT LVL) field. The minimum value is
only used for calculation purposes. The difference between the maximum value and the minimum
value is the number of levels to consolidate (LVLS TO CONSOL).
Maximum level (CONSOL AT LVL)
-- Minimum level
Levels to consolidate (LVLS TO CONSOL)
The larger the number of levels you retain, the longer it takes CA Endevor SCM to rebuild,
because each delta level requires additional I/O operations.
Note: Verify the parameter values match for the same element type across different CA
Endevor SCM locations.
Note: For more information about the type definition fields LVLS TO CONSOL and CONSOL
AT LEVEL, see Defining Inventory Structures (https://docops.ca.com/display/CE17
/Defining+Inventory+Structures).
When auto age level retention is set, change levels for all types in the system expire after the number
of months that are specified on the system definition. The base element or component is rebuilt to
reflect the changes from the deleted levels, with the base delta version and level numbers set to the
last discarded version and level. The delta format you are using, reverse, forward, or full image,
determines how the consolidated level is built. For reverse and full image deltas, change levels that
expire are dropped. For forward deltas, change levels that expire are incorporated into the base.
04-May-2018 894/1109
CA Endevor® SCM - 17.0
Setting the age retention limits in the system definitions, to indicate how long delta levels are kept,
turns on the Age Level Retention feature. You can examine what effect this will have on elements and
components by using the Age-Managed Delta utility, in examine mode, to see which delta levels have
expired.
Note: Delta removal occurs at the first modification of the elements or components after
turning on the Age Level Retention feature.
In this example, the delta levels are set to expire after five months, and the element is changed and
moved through the lifecycle as follows:
The element that is named ELEMENT1 is added to stage 1 of the Test environment from stage 2 of
the Production environment. The highest level of the element in stage 2 of the Production
environment, which is 0103, is fetched to stage 1 of the Test environment.
The element is updated in stage 1, Test, four times over a ten-month period. Each time the
element is saved, a new level is created with the level number incremented by 01. So that after
the element is saved four times, the new levels are 0104, 0105, 0106, and 0107.
The element is moved with history to stage 2, Test. All the levels in stage 1, Test (0103, 0104,
0105, 0106, and 0107) are included in the move.
The element is moved with history to stage 2 of the Production environment. Auto-age level
retention is triggered because the element has reached the end of the map and some of the
element levels are older than the five-month retention period. The result of the move with
history to stage 2, Production, depends on the delta format as described next:
If reverse delta (the base is a full copy of the current code):
Levels 1 thru 4 are removed, because they are older than 5 months.
A new base delta record is created reflecting level 4 with the following modifications:
Base is re-built to contain change levels 1 through 4, because they are older than 5 months.
A new base delta record is created. The base level 0 record reflects level 4 with the following
modifications:
04-May-2018 895/1109
CA Endevor® SCM - 17.0
Levels 1 through 4 are removed, because they are older than 5 months. The full image deltas
for level 0 through level 3 are deleted.
A new base level record is created. The base level 0 record reflects level 4.
Note: Regardless of the delta level format, the delta main control record (the first record in
the file) is updated to reflect the new base level. In this example, level 4 is made into the
new base level 0. The base record count, date, and time fields reflect level 4.The last level
value and record count reflect level 4. The last level date and time fields are set to blanks.
The following chart illustrates this example and shows how delta levels are incremented and
consolidated using the auto age delta retention feature.
04-May-2018 896/1109
CA Endevor® SCM - 17.0
(0104)
(0105)
(0106)
(0107)
Results of Move with history: Delta management
is triggered, because levels 1 thru 4 are older than
the 5 month retention limit.
ELEMENT1 (0100)
(0101)
(0102)
(0103)*
*In this example, at the end of the map, if the level format is:
reverse delta, then levels 1 thru 4 are removed. Level 4 becomes the new base level 00.
forward delta, then the base is re-built to contain change levels 1 thru 4. Level 4 becomes the
new base level 00.
Note: By default, the age delta level retention options on all the system definitions are
turned off for both elements and components. The default settings are ELEMENT=N and
COMPONENT=N and the only allowable value for their corresponding RETAIN LVLS FOR
fields is 0.
3.
04-May-2018 897/1109
CA Endevor® SCM - 17.0
3. To specify how many months the element delta levels are retained, type the number of
months in the RETAIN LVLS FOR field that appears next to the ELEMENT option. Allowable
values are 1 to 999. The default is 999.
Element delta levels are retained for the number of months specified, provided the ELEMENT
option is set to Y.
5. To specify how many months the element delta levels are retained, type the number of
months in the RETAIN LVLS FOR field that appears next to the COMPONENT option. Allowable
values are 1 to 999. The default is 999.
Component delta levels are retained for the number of months specified, provided the
COMPONENT option is set to Y.
Note: After you set retention limits in the system definitions, you can examine what effect
this will have on elements and components by using the Age-Managed Delta utility, in
examine mode, to see which delta levels have expired.
For example, the following diagram shows two environments (QA and PROD) with links between the
first and second stage in each environment and another link between stages HOLD and PROD.
04-May-2018 898/1109
CA Endevor® SCM - 17.0
This figure illustrates two environments with links between the first and second stage in each environment
This model cannot be implemented using the basic CA Endevor SCM pathways, because you can only
enter an environment through a single entry stage. If developers want to move an element from
Stage HOLD to Stage PROD, they must use the TRANSFER action instead of the familiar MOVE action.
To solve this problem, create Stage 2 to Stage 2 links by mapping the environments in the Defaults
Table. Mapping lets you do the following:
Provide developers with the ability to MOVE, ADD, and RETRIEVE elements between the linked
stages.
Create multiple entry points into a software lifecycle or join multiple lifecycles.
04-May-2018 899/1109
CA Endevor® SCM - 17.0
PDS
Benefits:
No installation issues.
Drawbacks:
Directory overhead becomes inefficient if there are more than 3-4K+ members.
PDS/E
Benefits:
Low maintenance.
Current technology.
Drawbacks:
ELIB
Benefits:
Low maintenance.
BDAM is more efficient for medium-sized directories, and VSAM is more efficient for large
directories, than either PDS or PDS/E.
Directory overhead routines are designed for many members, thereby increasing efficiency.
You can allocate a VSAM ELIB across multiple volumes. If you initially allocate an ELIB data set
across two volumes, CA Endevor SCM honors that allocation when ELIB expansion occurs. The
expansion can be automatic when the page reserve limit is reached or explicitly performed by
using BC1PNLIB. This is only for VSAM ELIB; BDAM ELIB must be allocated on a single volume.
Drawbacks:
04-May-2018 900/1109
CA Endevor® SCM - 17.0
Source output file can be read directly by CA Panvalet and CA Librarian utilities.
Drawbacks:
With CA Panvalet, conflicts arise with CA Endevor SCM footprint and comment information.
When a PDS load module is copied to a PDSE, CA Endevor SCM load module footprint information is
retained only if the CA Endevor SCM processor utility BSTCOPY is used. Other utilities, such as
IEBCOPY, cannot copy the *LOADMOD footprint. For more information, see TEC316937, How to
Convert AllFusion Endevor Change Manager Load Libraries between PDS and PDSe Formats, on ca.
com/support (http://ca.com/support).
CA L-Serv is a master started task that controls CA Endevor SCM VSAM files for Master Control Files
(MCFs), packages, and ELIB (if you are using VSAM processing instead of BDAM processing). This task
provides the following benefits:
Reduces the number of file I/O operations such as opens, closes, verifies, enqueues, and
dequeues.
Cross-system communications.
04-May-2018 901/1109
CA Endevor® SCM - 17.0
Only MCFs and package data sets, set RECBUFFSIZE to 1 K (the size of the largest VSAM record in
these files).
ELIB VSAM files (with or without MCFs or packages), set RECBUFFSIZE to the block size of the
largest library file being managed (typically 4 K).
Note: If you are using Point in Time Recovery, set RECBUFFSIZE to 12 K.Internally, CA
Endevor SCM blocks all non-VSAM Base/Delta records before writing to the journal files in
12 K increments.
Any significant additional CA Endevor SCM load is added (for example, environments and
elements).
Any significant CA Endevor SCM data set reconfiguration takes place (for example, splitting of Base
/Delta's or changing from PDS to VSAM E-Lib).
Any system hardware or software changes are made (for example, VTAM, CPU, or the operating
system).
04-May-2018 902/1109
CA Endevor® SCM - 17.0
As a new data access mode, VSAM RLS allows multisystem access to a VSAM data set while ensuring
cross-system locking and buffer invalidation. VSAM RLS uses z/OS coupling facility (CF) services to
perform data set level locking, record locking, and data caching. VSAM RLS maintains data coherency
at the control interval level. It uses CF caches as store-through caches; when a control interval of data
is written, it is written to both the CF cache and to DASD. This ensures that a failure in the CF cache
does not result in the loss of VSAM data.
The SMSVSAM server is a new system address space that is used for VSAM RLS. The data space that is
associated with the server contains most of the VSAM control blocks and the system-wide buffer pool
that is used for data sets opened for record-level sharing. SMSVSAM assumes responsibility for
synchronizing this control block structure across the parallel Sysplex.
With VSAM RLS, multiple CA Endevor SCM systems can directly access a shared VSAM data set,
eliminating the need for Reserve/Release and Enqueues between CA Endevor SCM Users or Batch
Jobs to maintain the integrity of the CA Endevor SCM VSAM data sets. VSAM RLS provides for
serialization and synchronization of data sets and cross-system caching. With VSAM RLS, multiple CA
Endevor SCM Users or Batch Jobs can have concurrent read/write access to CA Endevor SCM VSAM
data sets.
A new attribute, LOG, defines a data set as recoverable or non-recoverable. Because CA Endevor SCM
does not use CICS compatible Recovery, Logging or Journaling, the LOG attribute must be set to LOG
(NONE).
At OPEN time, CA Endevor SCM determines if the file is defined with VSAM RLS support, and, if so, CA
Endevor SCM opens the file with RLS.
System administration determines when RLS is used. Typically, this determination is made when the
cluster is defined with the IDCAMS utility program.
Sample JCL to enable RLS support may be found in iprfx.iqual.CSIQJCL, member BC1JDRLS.
The VSAM buffers for ALL jobs and/or TSO users are consolidated into the SMSVSAM address
space, increasing the chance of a record being in memory
04-May-2018 903/1109
CA Endevor® SCM - 17.0
The SYSPLEX Lock Manager provides record level, CI level and CA level locking between SYSPLEX
systems
Due to the first two enhancements, CA Endevor SCM is able to bypass its own native Reserve
/Release logic
The I/O performance of the SMSVSAM address space and the SYSPLEX cache allows a significant
reduction in the elapsed time required to do update I/Os.
Implementing RLS
CA Endevor SCM provides RLS support for Master Control Files (MCFs), the Element catalog and
Element catalog index (EINDEX), and the package data set.
To use CA Endevor SCM with RLS-managed data sets, certain data set attributes must be used when
allocating the VSAM cluster. As previously mentioned, LOG (NONE) must be part of the definition.
Also, a share attribute of (1,3) must be part of the cluster definition.
Ensure that record formats (RECFMs), block sizes (BLKSIZEs), and logical record lengths (LRECLs)
are specified correctly for the program being executed.
Note: The operating system provides the "System Determined BLKSIZE" facility, which
selects the best block size for a data set (based on its RECFM, LRECL, and the track size
DASD device) if it is allocated with BLKSIZE=0. You can use this facility with any CA Endevor
SCM data sets except for linkage-editor data sets.
Avoid recursive executions of CA Endevor SCM by using the CONWRITE utility to output other
elements. For example, if your jobcards are stored in one file and need to be merged into every
executable file, CONWRITE can perform this merge without re-invoking CA Endevor SCM.
Streamline processors by taking advantage of instream data (for example, DD *) and symbolics
(for example, &C1SYSTEM). This step eliminates extra steps that may have been required in the
past.
04-May-2018 904/1109
CA Endevor® SCM - 17.0
Allocate all temporary sequential data sets with BC1PDSIN to ensure that they are available for
other programs such as CONLIST. Allocate other data sets using traditional JCL statements for
each step.
Ensure that your JCL dispositions are properly coded to release data sets when appropriate (for
example, use FREE=CLOSE).
Ensure that VSAM and all output libraries are properly located, maintained, and sized. Poorly
tuned VSAM files can seriously degrade performance, so:
For highly accessed VSAM files, move the index to a cache device (remember to de-imbed the
index first).
Do not alter the attributes of the VSAM Master Control File (MCF) unless you are using CA L-
Serv.
Highly volatile files, such as those in development locations, perform better near the
beginning of the string, while more stable files, such as those in production locations, can be
located near the end of the string.
Analyze how many files reside on a single pack, and how large they are. Split CA Endevor SCM
files across multiple packs, and ensure that no other large files (such as the system catalog)
share the pack.
Ensure that your file allocations are the most efficient ones for your system.
Consider deleting and reallocating processor outputs for major system regenerations.
Process concurrently whenever possible. For example, if you want to recompile the entire system,
specifying GEN ELEM A* K* and GEN ELEM L* Z* instead of GEN ELEM * lets the system process
both halves simultaneously.
Consider using other products to help improve library performance. For example, CA developers
had an unload that required 90 minutes with CA Endevor SCM. When they combined CA Endevor
SCM with two other CA products, Unicenter CA PMO and Unicenter CA QuickFetch, the unload
took only 12 minutes. Unicenter CA PMO eliminates more than 90 percent of the directory search
I/Os for libraries and PDSs, while Unicenter CA QuickFetch eliminates more than 90 percent of the
fetch I/O for load modules in any managed program library.
04-May-2018 905/1109
CA Endevor® SCM - 17.0
Set the block size (BLKSIZE) for variable block files to 27998, which is half a 3390 DASD track.
This setting size allows rapid I/O time and efficient space usage. The reason for this is that
MVS puts as many records as possible in the buffer defined by the BLKSIZEs and only writes
the block if the remaining space cannot hold the next record. If a BLKSIZE of 2550 is chosen, it
holds a maximum of 2546 bytes; however, small BLKSIZEs are inefficient for disk use and also
inefficient in I/O time.
The logical record lengths (LRECLs) for variable block files should be at least 4 less than 27998
(that is, 27994). MVS uses what it needs and as long as the buffer allocation (LRECL'value) is
large enough, it fits without problems or wasting space. There is no reason to reduce the
LRECL to 255, for example. For variable or variable block files, the actual LRECL is unimportant.
The LRECL does not define the length of the records. The actual size is defined in the records.
The LRECL defines the maximum length of any one record. Consequently, setting a larger
LRECL and BLKSIZE for variable block files is not a problem. As long as the LRECL is larger than
the actual record, the record fits.
For types that contain binary data, we recommend a VB LRECL of 2048 or less. This practice
make source comparison perform more efficiently. The maximum LRECL is 13 K. This setting
allows for a compression result twice as large as the input.
The elimination of the requirement to fetch back unchanged source code dramatically improves
concurrent development productivity by reducing the possibility of out-of-sync changes being made
to different copies of the same source code. For example, with this option, source code can be
fetched back to a sandbox work area only when source changes are required. Another benefit is
improved performance resulting from the elimination of the movement (fetch and promotion) of
unchanged source code. In addition, virtual inventory configuration is used by the new Autogen
action option to facilitate processing of Generate actions.
When NoSource is used, the target location coded in a Generate action contains the outputs created
by the Generate processor. In addition, a sourceless element is created at the target. Because the
element source is not fetched back to the target location, the MCF record for the element generated
at the target identifies it as a sourceless element. The MCF element contains the last level timestamp
04-May-2018 906/1109
CA Endevor® SCM - 17.0
at the target identifies it as a sourceless element. The MCF element contains the last level timestamp
of the upstream element. Base and deltas do not exist for sourceless elements, so these fields are
blank in the MCF. When actions are performed against sourceless elements, the source from the next
sourced element upstream from it will be used providing that the last level timestamps are equal.
Assuming that the element source is not at the target location and the element source is located up
the map from the target, the effect of the Generate NoSource action is as follows:
1. The element source is not fetched back to the target location from up the map.
2. The first occurrence of the element up the map from the target location is used as input to
the generate processor. This element source is used as follows:
a. All target inventory C1 symbols are set with the element source inventory fields before
doing the C1BASELIB substitution.
b. The C1BASELIB symbol is set with the library base data set defined at the source
location (up the map).
c. After the C1BASELIB symbol is resolved, the target inventory C1 symbol is reset to the
action's target inventory.
3. After the Generate action completes, the targeted location coded in a Generate action
contains the outputs created by the generate processor. The MCF element created at the
target location contains data similar to a fetched back element except that the element base
and delta name fields are blank and the record is marked as a sourceless element.
Note: Elements with forward deltas must use the CONWRITE utility in their processors to
rebuild the element source. This utility supports sourceless elements by using the actual
source location from up the map to rebuild the element. Conwrite also supports forward
and reverse deltas.
04-May-2018 907/1109
CA Endevor® SCM - 17.0
PITR lets you recover changes made since the last backup to Element Catalog (ECF), Element Catalog
Index (EIX), CA Endevor® SCM Package Control File (PCF), Master Control File (MCF), and base and
delta libraries.
Note: PITR does not include a mechanism to back up and recover source output libraries or
processor outputs (for example object modules, load modules, listings). Source output
libraries and processor outputs may be backed up during normal processor execution and
recovered through manual procedures, or regenerated after the PITR process has been
completed.
PITR builds GENERATE SCL for elements that have been affected by the recovery process.
PITR is based on change journaling. This fact means that each change created by a CA Endevor® SCM
request is logged to a journal data set before the change is actually executed by CA Endevor® SCM.
Once the change has been made, a confirmation record is written to the journal, indicating whether
the change was successful or unsuccessful.
04-May-2018 908/1109
CA Endevor® SCM - 17.0
04-May-2018 909/1109
CA Endevor® SCM - 17.0
CA L-Serv must be enabled to use the PITR feature. We recommend that when implementing the PITR
feature you have available someone who is familiar with how CA L-Serv is set up at your site. You
should have access to the following CA Common Services content (http://wiki-dev.ca.com/wiki.ca.com
/CCSZOS).
Switch to other files in the group when one file becomes full.
Submit a batch job automatically to offload the information from files that are full.
Note: For more information about file groups, see the CA Common Services for z/OS
04-May-2018 910/1109
CA Endevor® SCM - 17.0
Note: For more information about file groups, see the CA Common Services for z/OS
Administration Guide.
Site level changes (the Package Control File element catalog and element catalog index) by
specifying a CA L-Serv Group ID in the JRNLGRP parameter in the TYPE=MAIN section of the
C1DEFLTS table.
Element and environment definition changes (Master Control File, base and delta libraries) by
specifying a CA L-Serv Group ID in the JRNLGRP parameter in the appropriate
TYPE=ENVIRONMENT section of the C1DEFLTS table.
Note: For more information about how to specify group IDs in the C1DEFLTS table, see
How to Modify the C1DEFLTS Table (see page 918).
Journaling
Journaling applies to any CA Endevor® SCM processing that changes the information in the data sets
(ECF, EIX, PCF, MCF, base, and delta libraries) that are under the protection of journaling.
1. Before executing a request that will change information, CA Endevor® SCM records the
change in the current journal data set.
3. Upon completion of the update, CA Endevor® SCM writes a confirmation record to the journal
data set indicating whether the update was successful or failed.
If any of these three steps is not completed, the requested action fails.
Important! If CA L-Serv is not available, or none of the specified journal data sets are
available, or all journal data sets are full, the requested action fails.
04-May-2018 911/1109
CA Endevor® SCM - 17.0
Assume that element PROGX, version 1.0, is located at Stage 2 in the development environment, and
that a modified version of PROGX is being added to Stage 1. The journaling activity that takes place at
each step of the ADD action is described in the following items:
2. The MCF record, element base and element delta for PROGX (1.0) are written to the journal.
3. PROGX (1.0) compared with modified version being added, and a delta is created.
The MCF record, element base and element delta for PROGX (1.1) are written to the journal.
In general, all components associated with a change to an element are written to the journal data
set. This point means that, for example, if a source change is made, the MCF record, element base
and element delta are written to the journal. If an element component list is modified, the MCF
record, component base and component delta are written to the journal.
Note: For more information about how to set up CA L-Serv to submit this job automatically,
see How to Define Journaling Components to CA L-Serv (see page 916).
Setting up the archive files as generation data groups (GDGs) assures that each offloaded journal is
fully accessible.
Note: When CA L-Serv starts up, if it detects either a full or partially full journal data set it
invokes the archive JCL for that data set.
04-May-2018 912/1109
CA Endevor® SCM - 17.0
Note: The Recovery utility uses the recovery utility control statements to determine which
transactions to recover. For more information, see Recovery Utility Syntax (see page 925).
The offloaded journal data sets can be concatenated in any order since all journal log entries are
sorted prior to processing.
The recovery utility processes the journal information in the following order:
2. It discards records that meet the selection criteria but do not meet the from/to date and time
criteria.
5. It compares the journal file footprint dates and times with the footprint dates and times in the
current MCF, PCF, and ELIB VSAM base and delta libraries, replacing files as necessary from
the journal in the backup files.
7. It deletes the scheduled SCL command whenever the element master record is deleted by a
subsequent journal file transaction
8. After all the journal transactions have been processed the utility writes all remaining
scheduled SCL statements to the C1SCL1 data set.
04-May-2018 913/1109
CA Endevor® SCM - 17.0
Consider including the group ID in the names of both the journal and the archive files. For example,
four journal files in a group named GRP1 might be named as follows:
NDVR.GRP1.JOURNAL1
NDVR.GRP1.JOURNAL2
NDVR.GRP1.JOURNAL3
NDVR.GRP1.JOURNAL4
CA L-Serv accesses the journal data sets using a journal group ID. Each journal group ID can reference
one or more journal data sets. The data sets associated with a particular group ID can be the journal
data sets for a Package Control File, the data sets for a particular environment, or a combination.
Group names can be up to four characters in length.
The PITR process can be streamlined somewhat by using a single group ID for all the journal data sets
at a site.
Note: For suggestions on setting up groups for journal data sets, see Implementation
Scenarios (see page 919).
When a data set becomes full, CA L-Serv automatically selects the next available journal data set for
recording subsequent change activity. Optionally, you can instruct CA L-Serv to submit automatically
a batch job to offload the journal information to a sequential file (for example, to a tape), switch to
the next available journal data set, and reinitialize the journal data set that has just been offloaded.
04-May-2018 914/1109
CA Endevor® SCM - 17.0
The automatic offloading of journal data set information is implemented using the ARCHIVE
command of the CA L-Serv LDMAMS utility.
The JCL for archiving full journal data sets is in member BC1JJARC in iprfx.iqual.CSIQJCL. To use this
JCL, modify it as necessary and include it in the data set referenced in the JCLLIB DD statement of the
CA L-Serv start-up member in your site PROCLIB.
Journal files should be allocated with a maximum record size of 32,760. Journal archive files should
have an LRECL of 32,756, and a maximum length of 32,760.
The files to be used to archive full journal data sets are best set up as generation data groups (GDG).
Note: Separate journal data sets and journal archive GDGs should be defined for each CA
Endevor® SCM journal group ID.
Sizing Considerations
The size of the journal data sets depends on the amount of CA Endevor® SCM activity at your site and
the size of your elements. Here are some general guidelines to follow:
Environment and package records take up a relatively small percentage of the total space.
When a journal data set is full, it is archived. The next journal data set must be at least large
enough to accept the journal records created during the time while the preceding data set is
being archived.
We recommend using three or four journal data sets. Remember that smaller journal data sets
require less time to archive, making them available again for journaling more promptly.
For example, consider a site with an average element size of 1,000 lines, with 500 updates per day to
these elements. Since most actions involve one write of an element base, element delta, component
list base, and component list delta, and two writes of the MCF, a size calculation would appear as
follows:
Component list base and delta, 100 lines @ 100 characters 10,000
04-May-2018 915/1109
CA Endevor® SCM - 17.0
Assuming 45,000 bytes per track, this means that an average CA Endevor® SCM action requires 2.5
tracks of journal data set space.
Assuming 500 transactions per day, there needs to be 1,250 tracks of journal data set space to handle
one day's activity.
Allocating this space amongst three journal data sets means that each journal data set would be
approximately 420 tracks. In this scenario, you might consider allocating a fourth journal data set to
handle the package and environment definition updates.
The JCL for defining a generation data group and journal data sets is in member BC1JJDEF in the iprfx.
iqual.CSIQJCL data set. Before submitting this job, perform the following actions:
Specify the name for the GDG. Consider including the group ID of the related journal group in the
GDG name.
Change as necessary the maximum number of data sets to be retained in the GDG. The default in
this example is 100.
Change the names of the journal data sets in the job according to your naming standards.
Note: Do not specify a secondary extent for the cylinder allocation. Doing so prevents the
journal files from filling up, defeating the purpose of journaling.
LDMPARM
NDVRPARM
Note: For examples of how to set up journaling, see Implementation Scenarios (see page
919).
04-May-2018 916/1109
CA Endevor® SCM - 17.0
CA L-Serv PROC
If you are using an existing CA L-Serv, modify the PROC for that CA L-Serv. If you are creating an L-
Serv, write a PROC for that CA L-Serv. This start-up procedure must include an //LDMCMND DD
statement, which points to the CA L-Serv parameter data set.
LDMPARM
LDMPARM is the default name of a member in the CA L-Serv parameter data set that contains the
parameters for the CA L-Serv to which you want to identify the PITR components. If you are using an
existing CA L-Serv, modify the existing LDMPARM member for the CA L-Serv you want to use to
include an ATTACH statement specifying the CA L-Serv type (local, remote, or host) and an INCLUDE
statement referencing the member NDVRPARM. If you are using a new CA L-Serv, create this
member.
An example of the syntax for the statements to be included in the LDMPARM member is shown next:
ATTACH
FILESERVER,SERVERTYPE=HOST,COMMSERVER(operands)
INCLUDE NDVRPARM
When included in a new or existing LDMPARM member, this syntax specifies a Host CA L-Serv, with L-
Serv's communication server enabled, and specifies NDVRPARM as the member identifying the data
sets to be managed by this CA L-Serv.
NDVRPARM
NDVRPARM is the suggested name for a member in the CA L-Serv parameter data set that contains
an ADDFILE command for each CA Endevor® SCM library or PITR journal data set managed by L-SERV.
A sample NDVRPARM member in an instance where CA L-Serv is being used to manage journal data
sets is shown next:
*************************************************************
*** JOURNAL FILES
*************************************************************
ADDPOOL 13 (32768,100)
ADDFILE JRNL1 uprfx.uqual.ugrpid.JOURNAL1 GROUP=ugrpid,
OPTION=(SUBMIT) POOL=13,
JCLMEMBER=BC1JJARC
ADDFILE JRNL2 uprfx.uqual.ugrpid.JOURNAL2 GROUP=ugrpid,
OPTION=(SUBMIT) POOL=13,
JCLMEMBER=BC1JJARC
ADDFILE JRNL3 uprfx.uqual.ugrpid.JOURNAL3 GROUP=ugrpid,
OPTION=(SUBMIT) POOL=13,
JCLMEMBER=BC1JJARC
ADDFILE JRNL4 uprfx.uqual.ugrpid.JOURNAL4 GROUP=ugrpid,
OPTION=(SUBMIT) POOL=13,
JCLMEMBER=BC1JJARC
The ADDFILE and GROUP= clauses are required for journal files. The OPTION=(SUBMIT) and
JCLMEMBER= clauses are required for automatic archiving. The ADDPOOL and POOL= clauses are
optional but recommended.
Note: Do not use the APPEND parameter of the ADDFILE statement when identifying
journal files or CA Endevor® SCM files to CA L-Serv.
04-May-2018 917/1109
CA Endevor® SCM - 17.0
The syntax for including this information in the C1DEFLTS table is shown:
JRNLGRP=(group id,nnnn)
group id
The journal group ID associated with the journal files.
nnnn
The subsystem name for CA L-Serv being used to implement journaling. The default CA L-Serv
subsystem ID is LSRV.
1. The TYPE=MAIN section of the C1DEFLTS table to enable journaling in the Package Control
File.
2. Each TYPE=ENVIRONMENT section of the MCF base and delta libraries (VSAM and non-VSAM)
for which you want to enable journaling.
Note: If you want to use the same journal group ID for more than one environment,
include the journal group ID in each environment section of the C1DEFLTS table. We
recommend that PITR be specified for all environments defined in the C1DEFLTS.
04-May-2018 918/1109
CA Endevor® SCM - 17.0
Implementation Scenarios
The number of CA L-Servs required to implement PITR depends on the site configuration. This section
presents common single and multiple CPU implementation scenarios, and provides guidelines for
each.
04-May-2018 919/1109
CA Endevor® SCM - 17.0
Note: For more information about modifying the C1DEFLTS table, see How to
Modify the C1DEFLTS Table (see page 918).
04-May-2018 920/1109
CA Endevor® SCM - 17.0
Creating or modifying member LDMPARM, and the CA L-Serv PROC, as described earlier in
this section. As a remote CA L-Serv, it does not manage any files and therefore does not
need an NDVRPARM member.
3. Set up communication between CA L-Serv Host and CA L-Serv Remote, referring to the CA
Common Services for z/OS Getting Started Guide as necessary.
04-May-2018 921/1109
CA Endevor® SCM - 17.0
Note: For more information about modifying the C1DEFLTS table, see How to
Modify the C1DEFLTS Table (see page 918).
There is a trade-off to this scenario, namely that handling journaling remotely is somewhat slower
than local journaling.
04-May-2018 922/1109
CA Endevor® SCM - 17.0
Defining both as Local, using the same subsystem name for each.
2. Modify the C1DEFLTS Table to include entries for CA L-Serv 1 and CA L-Serv 2.
Note: For more information about modifying the C1DEFLTS table, see How to
Modify the C1DEFLTS Table (see page 918).
1. Clean out journal data sets that may contain information, by executing the JCL found in
member BC1JJARG in the data set iprfx.iqual.CSIQJCL.
2. Disable journaling by either issuing the CA L-SERV REMOVEFILE command or stop CA L-Serv
using one of the following console commands:
/F task,SHUTDOWN
/P task
These commands deactivate all functions running in the CA L-Serv address space. For
information about CA L-Serv system commands refer to the CA Common Services for z/OS
Getting Started Guide.
3. After you have successfully removed the files from the control of CA L-SERV, change the SHR(1
3) to SHR(3 3). To do this, run job BC1JLSRV supplied in your iprfx.iqual.CSIQJCL library. This
job is intended to ALTER the SHR attributes of the Master Control File (MCF), Package and ELib
data sets from SHR (1 3) to SHR (3 3).
4. Backup CA Endevor® SCM, using either the Unload Utility or your regular backup utility.
04-May-2018 923/1109
CA Endevor® SCM - 17.0
4. Backup CA Endevor® SCM, using either the Unload Utility or your regular backup utility.
6. Restart CA L-Serv by either using the following following START command, or by using the CA
L-SERV ADDFILE command to issue journaling again.
/S task parms
1. Execute the CA L-Serv LDMAMS utility to offload all used journal data sets.
2. Disable PITR journaling to keep any new journaling from being issued.
3. Restore all CA Endevor® SCM data sets to be recovered from the most current back-up (either
CA Endevor® SCM UNLOAD or similar back-ups).
Replace UGRPID with the CA L-Serv group ID for the journal data sets.
Replace uprfx.uqual.ugrpid.JRNLDATA with the GDG name used at your site for the archive data
sets.
If the CA L-Serv load library has not been included in LINKLST, specify the load library data set
name in the STEPLIB DD statement. Otherwise remove the STEPLIB DD statement.
Specify the unit, volser, and space parameters for the journal archive data set.
The ARCHIVE statement in this sample differs from the statement used to archive data sets that are
full. The difference is the SWITCH parameter. When a data set in a CA L-Serv group is not full, this
parameter tells CA L-Serv to switch to the next data set in the group after archiving whatever data is
in the data set.
04-May-2018 924/1109
CA Endevor® SCM - 17.0
Note: These commands deactivate all functions running in the CA L-Serv address space. For
more information about CA L-Serv system commands, see the CA Common Services for z
/OS Getting Started Guide.
The utility uses the restored data sets as a baseline, recovering any transactions that have taken
place since the most recent backup. Do this using the recovery procedure at your site.
RECOVER /LIST
(Required) The RECOVER or LIST keyword must be the first word in the syntax. Use LIST if you
want to list the contents of a journal file before recovering it.
04-May-2018 925/1109
CA Endevor® SCM - 17.0
PKGDS
(Optional) Indicates that you want to recover the package data set for the site.
ENVIRONMENT
(Optional) Indicates that you want to recover the named environment.
SYSTEM
(Optional) Indicates that you want to recover the named system.
ALL
(Default) Indicates that you want to recover the element catalog, element catalog index, package
data set, MCF, base, and delta library information.
TO DATE, TIME
(Optional) Allows you to specify a date and time through which you want to recover information.
Recover Examples
To recover the package data set for a site, submit the following syntax:
RECOVER PKGDS.
To recover MCF, base and delta information for environment PROD, submit the following syntax:
RECOVER ENV PROD.
To recover MCF, base and delta information for environment PROD, system Finance, submit the
following syntax:
RECOVER ENV PROD SYS FINANCE.
If, for some reason, the PROD environment should be restored as it was on July 19th (as opposed to
all logged changes) the following clause would be specified:
RECOVER ENV PROD
TO DATE 19JUL92 TO TIME 08:00.
The following statement would recover all logged changes (contained in the input sequential journal
files) for the Package Control File and for all environments:
RECOVER ALL.
You can find the JCL to run the recovery utility in member BC1JJRCV in iprfx.iqual.CSIQJCL.
C1MSGS1
The C1MSGS1 DD statement specifies the destination for the Journal Recovery Execution Report.
C1SUMMRY
The C1SUMMRY DD statement specifies the destination for the Journal Recovery Execution
Summary Report.
04-May-2018 926/1109
CA Endevor® SCM - 17.0
JOURNAL
The JOURNAL DD statement identifies the data set containing the journal data to be recovered.
C1SCL1
The C1SCL1 DD statement identifies the data set containing the SCL statements written by the
Recovery utility.
BSTIPT01
The BSTIPT01 DD statement contains syntax for this run of the Recovery utility.
Transaction detail
Transaction summary
JRCV032I
The transaction number, the journal date and timestamps, and the number of records in the
transaction.
JRCV015I
The kind of action.
JRCV016I
The CA Endevor® SCM location associated with the member in the previous message.
JRCV031I
The date and time of the most recent update to the CA Endevor® SCM entity described in this
entry. If no information is available, a NOT FOUND message is returned.
JRCV023I
Indicates that generate SCL has been built for the entity.
04-May-2018 927/1109
CA Endevor® SCM - 17.0
JRCV025I
Indicates that the recover utility has issued a generate processor request for the element.
JRCV026I
The CA Endevor® SCM location associated with the element to be generated.
JRCV020I
Indicates that the journal entry has been recovered, and provides the return code for the
recovery process.
PCF
Package Control File.
MCF
Master Control File.
EBASE
Element base.
EDELTA
Element delta.
CBASE
Component list base.
CDELTA
Component list delta.
JRCV100I
The data set usage by CA Endevor® SCM. Usage may be any of the following:
ECF
Element Catalog
EIX
Element Catalog Index
CBASE
Component list base
04-May-2018 928/1109
CA Endevor® SCM - 17.0
CDELTA
Component list delta
EBASE
Element base
EDELTA
Element delta
MCF
Master Control File
PCF
Package Control File
JRCV113I
The CA Endevor® SCM location associated with the file. For example, a file used to store element
base records might be used for base records associated with a particular environment, stage,
system, and type. A Master Control file on the other hand is associated with only an environment
and stage.
JRCV101I
Indicates the number of members created in this data set for the period covered by the journal
file.
JRCV102I
Indicates the number of members updated in this data set for the period covered by the journal
file.
JRCV103I
Indicates the number of members deleted in this data set for the period covered by the journal
file.
04-May-2018 929/1109
CA Endevor® SCM - 17.0
You can run the utility in validate mode to check that the SCL statements generated for your search
request are valid. Whether the utility is run in replace or validate mode, you can generate a report of
the search targets found. Additionally, other options can be specified.
The Search and Replace utility is controlled by the SEARCH ELEMENT request (available in batch only).
You specify the inventory location to be searched as well as any additional selection criteria, such as
CCID or processor group. You also provide the character string for which you are looking and,
optionally, a character string with which you want to replace the original string.
If you include a replacement string in your request, the utility replaces the original character string
with the second string. The utility then adds the element back into the entry stage at the
environment specified on the request. If you do not specify a replacement string, the element is not
updated.
The premise of the Search and Replace Utility is that one or more text strings can be found and,
04-May-2018 930/1109
CA Endevor® SCM - 17.0
The premise of the Search and Replace Utility is that one or more text strings can be found and,
optionally, replaced by one or more different text strings. Information is compared on a line-by-line
basis, within specific columns. Information is replaced within specific columns of specific lines.
The following concepts are also important to your understanding of the search and replace process.
IN-COLUMNS and BOUNDS ARE parameters are used in conjunction with each other to set the
limits for the search and replace operations.
Note: For a discussion of compare column ranges, IN COLUMNS rules, and BOUNDS ARE
rules, see Text Replacement (see page 947).
Data is manipulated only within the modifiable range. Data in columns outside this range is
neither modified nor affected by data shifting.
Note: For a discussion and examples regarding replacement string length, see Shorter
Replacement String (see page 948).
You can override the type compare columns by assigning IN-COLUMNS and BOUNDS ARE values
in the SEARCH ELEMENT statement. You cannot assign a value that exceeds the type definition
compare column value. For example, you are using element type COBOL, whose compare
columns are 7-72. If you assign a right boundary of 80, you will receive an error message. The
right boundary can be any value up to and including 72. Similarly, assigning a left boundary of 6
results in an error. The left boundary value cannot be less than 7.
Note: For a discussion of the SEARCH ELEMENT SCL, see Search Element SCL (see page 940)
. For a discussion about IN COLUMNS and BOUNDS ARE rules, see Text Replacement (see
page 947).
The search is always done against the current level of the element, and always begins at the entry
stage of the indicated environment. You cannot specify a beginning stage location in your SEARCH
ELEMENT request.
04-May-2018 931/1109
CA Endevor® SCM - 17.0
By default, the Search and Replace utility looks for the character string in the column range
associated with the element type entered in the request. You can override the type values by coding
an explicit search column range.
Validate
Executed when you code VALIDATE in the PARM= field in the execution JCL. The utility parses and
verifies the SCL statements in the SEARCH ELEMENT request.
Note: For more information about validate mode, see Validate Mode (see page 935).
Search-Only
Executed by default, the utility searches for the search string specified and produces a report
indicating the element in which the string is found. Optionally (depending on what is coded in the
execution JCL), the utility generates SCL for each element that contains the search string.
Note: For more information about search-only mode, see Search-Only Mode (see page 936
).
Replacement
Executed when a replacement text string is included in the request and the OPTIONS UPDATE
ELEMENT clause is coded. Both conditions must exist in order for the utility to replace one string
with another. The utility replaces the original string with the replacement string, and adds the
element back into the entry stage of the environment specified on the SEARCH ELEMENT request.
Note: For more information about replacement mode, see Replacement Mode (see page
937).
04-May-2018 932/1109
CA Endevor® SCM - 17.0
Modifiable range
The union of the BOUNDS ARE parameters and IN COLUMNS parameters.
The left or first position of the modifiable range is the IN COLUMNS from-column.
The right or end position of the modifiable range is BOUNDS ARE right-column, with one
exception:
If the IN COLUMNS to-column is greater than the BOUNDS ARE right-column, the IN
COLUMNS to-column value is used as the end of the modifiable range.
The default modifiable range is the compare column range of the element type.
All updates to elements are performed at the entry stage in the environment specified in the
SEARCH ELEMENT request.
Variable length records are never shortened. A record's length may increase, but it will not
04-May-2018 933/1109
CA Endevor® SCM - 17.0
Variable length records are never shortened. A record's length may increase, but it will not
decrease.
In replacement mode, the Search and Replace utility does not search elements that are signed
out to users other than the current user, unless the OVERRIDE SIGNOUT option is specified in the
SEARCH ELEMENT request. Nor does the utility search elements in an in-between stage (that is, a
stage not on the map but between two stages that are on the map).
The Search and Replace utility uses the CA Endevor® SCM security system to verify that a user is
authorized to perform the requested actions against the element. The following security checks are
performed:
Does the user have RETRIEVE authority for the element at the inventory location at which it is
found?
Does the user have OVERRIDE SIGNOUT authority at the inventory location at which the element
is found?
This check is performed when the OVERRIDE SIGNOUT clause is specified and the element
is not signed out to the current user. (Applies to replacement mode only.)
Does the user have ADD or UPDATE authority for the element at the entry stage of the specified
environment?
This check occurs when the updated element is added back into CA Endevor® SCM. If the
element exists at the entry stage, the user must have UPDATE authority for the element at
that stage. If the element does not exist at the entry stage, the user must have ADD
authority for the element at that stage.
04-May-2018 934/1109
CA Endevor® SCM - 17.0
Exit 1--Security
Exit 1
Invoked for the following actions:
Retrieve
Add, Update
When invoked:
Before ADD or UPDATE processing, only if it has been determined that the element will need
to be added back into CA Endevor® SCM.
Exit 2
Invoked for the following actions: Add or Update
When invoked: Before action processing begins.
Exit 3
Invoked for the following actions: Add or Update, based on exit 2
When invoked: After a corresponding (and successful) invocation of exit 2.
If exit 2 is invoked and allows an action, exit 3 is invoked after the action has been performed.
If exit 2 is invoked but does not allow an action, exit 3 is not invoked.
If exit 2 is not invoked for an action or element, exit 3 is not invoked for that action or
element.
Validate Mode
The Search and Replace utility operates in validate mode when you code VALIDATE as part of the
PARM= parameter in the execution JCL. In this mode, the utility parses and verifies the generated SCL
statements for proper syntax. If no errors are found, the SCL statements are formatted.
Processing stops after validation. The actions implied by the SCL statements are not performed.
Errors other than syntax errors are not noted at this time.
To invoke validate mode, you need to code the following in the execution JCL:
PARM='ENBS1000VALIDATE'
You can abbreviate the word validate, using any of the following entries:
V, VA, VAL, VALI, VALID, VALIDA, or VALIDAT
04-May-2018 935/1109
CA Endevor® SCM - 17.0
V, VA, VAL, VALI, VALID, VALIDA, or VALIDAT
Search-Only Mode
The Search and Replace utility executes in search-only mode by default. In this mode, the utility
searches for a particular search string in the elements specified in your SEARCH ELEMENT request. At
a minimum, the utility generates a list of the elements that contain the search string. Depending on
what you code in the request or in the execution JCL, the utility performs the following actions:
A replacement string in the request and allocate the ENSSCLOT file in the JCL
Generates SCL for all the elements that would be affected by replacement of the search string.
SCL statements are generated only when a replacement string is specified in the original search
request.
Note that in search-only mode, the OPTIONS UPDATE clause is not specified.
The Search and Replace utility verifies RETRIEVE authority before processing the element.
The Search and Replace utility does not do the following when in search-only mode:
The utility does not check whether an element is at an in-between stage (a stage not on the map,
but between two stages that are on the map).
Important! The search string is case-sensitive. If the search string contains only uppercase
characters, the utility looks only for text in uppercase characters. If a line in an element
matches the text of the search string but is in lowercase or a combination of lowercase and
uppercase characters, the utility does not record a match.
04-May-2018 936/1109
CA Endevor® SCM - 17.0
This capability is useful when a large number of elements are searched before search strings are
replaced. You can review the output to see how elements will be affected by the text replacement. If
the output is acceptable, execute the Search and Replace utility again, using the generated SCL as the
input file. Because the SCL statements have been created, the utility only needs to execute them; a
second search of the entire inventory is not necessary. Using this option not only allows you to
review the results of replacing text before you actually do so--it also saves you time.
The Search and Replace utility generates SCL statements if you enter a replacement string in the
SEARCH ELEMENT request and you allocate the ENSSCLOT DD statement in the execution JCL. The SCL
statements written to the ENSSCLOT file contain all the information entered in the original SEARCH
ELEMENT request as well as an OPTIONS UPDATE ELEMENT clause. When you invoke the utility a
second time, using the generated SCL as the input file, only the specified elements are searched and
updated.
If the source SCL contains multiple SEARCH ELEMENT requests, the output data set may contain
multiple SCL statements for the same element.
Note: Each FROM statement in the generated SCL will contain explicit system, subsystem,
and type values, even if you used a wildcard for that value in the original SEARCH ELEMENT
request. These values represent the location where the updates will be applied.
ENSSCLOT File
The ENSSCLOT DD statement should refer to a sequential data set or a partitioned data set with an
explicit member. Allocate the data set with the following attributes:
RECFM=F or FB
LRECL=80
Replacement Mode
The Search and Replace utility operates in replacement mode when you include both the REPLACE
WITH clause and the OPTIONS UPDATE ELEMENT clause in your SEARCH ELEMENT request. In this
mode, the utility searches the element for the search string, replaces each occurrence of the string
with the replacement string, and adds the element back into CA Endevor® SCM at the entry stage of
the specified environment.
04-May-2018 937/1109
CA Endevor® SCM - 17.0
In this mode, the utility verifies RETRIEVE, SIGNOUT, and ADD/UPDATE authorization. In addition, the
utility checks whether any of the elements specified exist at an in-between stage (stage not on the
map but between two stages that are on the map).
Note: For more information about these authorizations and conditions, see Processing
Checkpoints (see page 938).
SIGNOUT authorization and in-between stage checking are not performed in search-only mode.
Consequently, elements that are signed out to another user or exist at an in-between stage may
be searched, and may have SCL statements written to the ENSSCLOT file. Because the utility does
perform these two checks in replacement mode, some of the SCL statements may terminate with
an error if you use this ENSSCLOT file as input to a subsequent Search and Replace job.
The search string and the replacement string are case-sensitive. If the search string contains only
uppercase characters, the utility looks only for text in uppercase characters. If a line in an element
matches the text of the search string but is in lowercase or a combination of lowercase and
uppercase characters, the utility does not record a match.
Similarly, the utility places the replacement string in the element exactly as it has been coded in
the SEARCH ELEMENT request. The utility does not convert lowercase characters to uppercase
characters (or vice versa).
When fetch processing occurs, if the value of Signout Fetch (SOFETCH), a CA Endevor® SCM
Defaults Table parameter, is Y, the element that is fetched will be signed out to you at the
location from which it was fetched, unless it is already signed out to someone else. If the value of
SOFETCH is N, the element that is fetched will not be signed out.
The element that is put in the entry stage will be signed out to you.
Processing Checkpoints
Before and during processing, the utility checks for the following authorizations and conditions:
RETRIEVE authority
Before processing an element, if the user does not have RETRIEVE authority, then processing
stops for that element and begins for the next element.
04-May-2018 938/1109
CA Endevor® SCM - 17.0
RETRIEVE authority
Before processing an element, if the user has RETRIEVE authority, then processing for the
element continues.
SIGNOUT authority
After RETRIEVE authority is determined but before processing for the element, if the user does
not have SIGNOUT authority, then processing stops for that element and begins for the next
element.
SIGNOUT authority
After RETRIEVE authority is determined but before processing for the element, if the user does
have SIGNOUT authority, then processing for the element continues.
ADD/UPDATE authority
After the element is searched and the search string is replaced, but before the element is added
or updated into CA Endevor® SCM, if the user does not have ADD/UPDATE authority, then
processing stops for that element and begins for the next element.
ADD/UPDATE authority
After the element is searched and the search string is replaced, but before the element is added
or updated into CA Endevor® SCM, if the user does have ADD/UPDATE authority, then the utility
performs the appropriate action at the entry stage of the specified environment:
ENSSCLIN DD Statement
The user control statements specified in the ENSSCLIN DD statement are SEARCH ELEMENT requests,
which specify element search criteria, the search string, and, optionally, a replacement text string.
You can code as many SEARCH ELEMENT requests as you need; there is no defined limit on the
number of statements allowed.
04-May-2018 939/1109
CA Endevor® SCM - 17.0
Note: For more information about the SEARCH ELEMENT SCL, see Search Elements SCL (see
page 940).
PARM= Statement
You must specify the ENBS1000 parameter to invoke the Search and Replace utility. You can
optionally code the VALIDATE parameter (immediately after ENBS1000) to request validate mode
processing.
The utility performs the following actions depending on the value that you specify in the PARM=
statement:
PARM=ENBS1000
Parses and validates all the requests before processing them.
If the parser or validation routine detects an error, the utility will not execute any of the
statements. The parsing routine attempts to parse all of the control statements before
terminating.
PARM=ENBS1000VALIDATE
Parses and validates all the requests, but does not execute the requests even if no syntax or
validation errors are found.This parameter must follow the ENBS1000 parameter, as shown here:
PARM=ENBS1000VALIDATE
The utility parses and validates all requests before it begins executing them. If there is a syntax error
in any request or an error is found validating a request, none of the statements are executed. The
utility tries to parse all statements before terminating.
When the requests have been successfully parsed, the utility executes them. Requests are executed
as long as the highest return code is less than or equal to 12.
Note: If you code PARM=VALIDATE, the utility will not execute the requests when parsing is
complete.
The SEARCH ELEMENT syntax is shown in the next section, followed by a description of each clause in
the syntax.
04-May-2018 940/1109
CA Endevor® SCM - 17.0
►─ FROm ─ ENVironment ─ env-name ─ SYStem ─ sys-name ────────────────────────►
►─ SUBsystem ─ subsys-name ─ TYPe ─ type-name ───────────────────────────────►
┌───────────────────────────────────┐
►── ▼ ─ FOR ─┬────────┬─ search-string ─┴────────────────────────────────────►
└─ TEXt ─┘
►─ ¤ ┬──────────────────────────────────────────────────────────────────┬─ ¤ ─►
├─┬──────┬ ─ COLumns ─┬─ from-column ─┬─┬─────────────────────────┬┤
│ └─ IN ─┘ └─ FIRst ───────┘ └─ TO ─┬─ to-column ─┬────┘│
│ └─ LASt ──────┘ │
├─ REPlace WITh ─┬────────┬─ repl-string ──────────────────────────┤
│ └─ TEXt ─┘ │
└─ BOUnds ┬───────┬─┬──────────┬─┬─ left-col ┬─┬──────────────────┬┘
└─ ARE ─┘ └─ COLumn ─┘ └─ FIRst ◄ ─┘ └─ TO ┬─ right-col┬┘
└─ LASt ◄ ──┘
►─┬──────────────────────────────┬──────────────────────────────────────────────►
└─ WHEre ─ ¤ ─┬──────────┬─ ¤ ─┘
├─┤ CCID ├─┤
└─┤ PRO ├──┘
►─┬───────────────────────────────────────────────────────────────────────────┬─►
└─ OPTion ─ ¤ ─┬──────────────────────────────────────────────────────┬─ ¤ ─┘
├─ CCId ─┬──────┬─ ccid ───────────────────────────────┤
│ ├─ EQ ─┤ │
│ └─ = ──┘ │
├─ COMment ─┬──────┬─ comment ─────────────────────────┤
│ ├─ EQ ─┤ │
│ └─ = ──┘ │
├─ BYPass GENerate PROCessor ──────────────────────────┤
├─ PROCessor GROup ─┬─ EQ ─┬─ group-name ──────────────┤
│ └─ = ──┘ │
├─ OVErride SIGNOut ───────────────────────────────────┤
├─ SEArch ENVironment ─┬─ MAP ──┬──────────────────────┤
│ └─ ONLy ─┘ │
├─┬────────┬ ─ TRUncation ─┬──────┬─┬─ PROHibited ◄ ─┬─┤
│ └─ DATa ─┘ └─ IS ─┘ └─ PERmitted ────┘ │
├─ LISt DETails ───────────────────────────────────────┤
└─ UPDate ─┬───────────┬───────────────────────────────┘
└─ ELEment ─┘
Expansion of CCID
┌─── , ───┐
├── CCId ─┬────────────────────────┬─┬─ EQ ─┬─ (─ ▼ ─ ccid ─┴─ ) ─────────────────┤
└─ OF ─┬─ ANY ◄ ───────┬─┘ └─ = ──┘
├─ BASe ────────┤
├─ GENerate ────┤
├─ LASt ACTion ─┤
└─ RETrieve ────┘
Expansion of PRO
┌─── , ─────────┐
├── PROCessor GROup ─┬─ EQ ─┬─ (─ ▼ ─ group name ─┴─ ) ──────────────────────────┤
└─ = ──┘
04-May-2018 941/1109
CA Endevor® SCM - 17.0
From Clause
The FROM clause identifies the CA Endevor® SCM inventory location at which the element search
begins. You must enter all FROM information. You need to code the word FROM only once. The
FROM clause is described next:
Note that you cannot indicate a stage. The search always begins at the entry stage of the
environment you specify.
If you specify OPTIONS SEARCH ENVIRONMENT MAP, the utility searches this inventory location first,
and then continues the search for the element up the map. If you specify OPTIONS SEARCH
ENVIRONMENT ONLY, the utility searches only the environment defined in this clause.
If an element changes as a result of the search, the utility either adds it or updates it at the entry
stage of the environment specified in this FROM clause. The element is always added (or updated) at
the entry stage of this environment, no matter where the element was retrieved.
04-May-2018 942/1109
CA Endevor® SCM - 17.0
For Clause
The FOR [TEXT] clause identifies the text strings the utility searches for and, optionally, provide the
compare ranges to be searched and replacement text for the search strings. If you do not enter
column compare range values, the utility uses the COMPARE FROM and COMPARE TO columns
associated with the element type.
The IN COLUMNS, BOUNDS ARE, and REPLACE WITH clauses can be entered in any order, as long as
they all follow the FOR [TEXT]. These clauses are described in the following: search-string clause.
The maximum length of the string is 72 characters. The length of the string must be less than
or equal to the number of columns searched (see the description of IN COLUMNS that
follows).
You can specify multiple search strings by repeating the FOR TEXT search-string clause. For
example:
FOR TEXT ABCDE
FOR TEXT BCXYZ
If the string contains imbedded spaces or any other parser delimiter, it must be enclosed by
either apostrophes or quotation marks.
The string itself cannot contain both apostrophes and quotation marks.
Trailing blanks are significant during the search operation if the search-string is quoted.
The comparison of text strings is case-sensitive; that is, lowercase characters remain
lowercase.
from-column or FIRST, to indicate the first column (inclusive) of the compare range. You can
enter any value as the from-column value as long as that value is less than or equal to the to-
column value (see next). If you do not enter a from-column but you do enter a to-column, the
utility uses the left-column value of the BOUNDS clause as the first column. FIRST reflects the
COMPARE FROM value of the type associated with the element.
to-column or LAST, to indicate the ending column (inclusive) of the compare range. The to-
04-May-2018 943/1109
CA Endevor® SCM - 17.0
to-column or LAST, to indicate the ending column (inclusive) of the compare range. The to-
column value must be greater than the from-column value, and cannot exceed 32,000. LAST
reflects the COMPARE TO value of the type associated with the element.
left-column or FIRST, to indicate the first column (inclusive) of the compare range. The utility
uses this value if you do not specify an explicit IN COLUMNS from-column value. If you do not
enter a left-column value, the utility defaults to FIRST.
right-column or LAST, to indicate the last column that can be modified in the range. If you do
not enter a right-column value, the utility defaults to LAST.
Where Clauses
WHERE clauses provide additional element selection criteria. The search is limited to only those
elements whose CCID or processor group match the entry in the SEARCH ELEMENT request. WHERE
clauses are optional and are described as follows:
WHERE CCID OF . . . EQ . . .
Specifies the CCID that must be associated with the element in order for the utility to search the
element. The CCID can be from 1-12 characters in length, and can be explicit, partially wildcarded,
or fully wildcarded. Note that coding a fully wildcarded CCID produces the same result as not
coding this clause or coding WHERE CCID OF ANY--all elements are selected no matter what the
CCID is.
You can provide a list of CCIDs; enclose the list in parentheses. The CCID associated with the
element must match at least one CCID in the list to be selected for processing. The utility checks
only the current MCF for the CCID.
You can limit the search to only those elements whose base, generate, last action, or retrieve
CCID match the CCID specified in the request. Again, the utility checks only the current MCF
04-May-2018 944/1109
CA Endevor® SCM - 17.0
CCID match the CCID specified in the request. Again, the utility checks only the current MCF
record.
If you use WHERE CCID OF ANY, all of the above CCID fields in the current MCF record are
examined.
Option Clauses
OPTION clauses allow you to further qualify your request. You can specify none, one, or more than
one option. You need to code the word OPTION only once. Option clauses are described next:
04-May-2018 945/1109
CA Endevor® SCM - 17.0
OVERRIDE SIGNOUT
If the element is signed out to someone else, override signout must be used and the
corresponding authority granted.
You will not get the signout of the element that is fetched. However, the element that is put in
the entry stage will be signed out to you.
This clause applies only if you code the REPLACE WITH clause.
SEARCH ENVIRONMENT MAP indicates that the utility is to search the environment map for
the element if the element is not found at the entry stage of the specified environment.
SEARCH ENVIRONMENT ONLY indicates that the utility is to search only the environment
specified in the SEARCH ELEMENT request. The utility can search both stages of the
environment, but not the other environments in the map.
If this clause is not coded, the utility searches only the entry stage of the specified environment.
This is the default.
Code DATA TRUNCATION IS PROHIBITED to prevent data in an element record from being
truncated. This is the default. An error message is returned if text replacement would have
resulted in data truncation.
LIST DETAILS
Indicates that you want to list, on the Search and Replace Utility Execution Report, each line (or a
portion of the line, up to 90 bytes of data) of text containing the search string. The lines are
printed as they are encountered during execution of the request. If the request contains a
replacement string, the updated line is also printed.
If this clause is not coded, the text of each line containing the text string is not printed in the
execution report. Each element searched, along with the number of matches found in that
element (0 to 99999), is printed to the execution and summary report, regardless of the LIST
DETAILS option setting.
UPDATE [ELEMENTS]
Indicates that the utility is operating in replacement mode. That is, as appropriate, the utility
replaces the search string with the replacement string and updates the element. (For more
information, see Replacement Mode in this chapter.)
If this clause is coded, you need to code the REPLACE WITH clause if you want to replace the
search string and update the element(s). Otherwise, the utility runs in search-only mode.
If this clause is not coded, the utility operates in search-only mode.
04-May-2018 946/1109
CA Endevor® SCM - 17.0
Text Replacement
The replacement text string may be equal to, longer, or shorter than the search string. A longer or
shorter search string causes data to be shifted to the right or left and blank spaces to be consumed or
inserted. The size of the replacement string does not affect the record length, however, except under
the following conditions:
The extended length will not exceed the maximum length permitted for the element.
Note: The search string and the replacement string are case-sensitive.
The BOUNDS ARE clause, used in conjunction with the IN COLUMNS clause, restricts the range of data
that is searched and the range of data that may be affected by a change.
When both the IN COLUMNS and BOUNDS ARE clauses are specified, the utility uses the higher of
the IN COLUMNS to-column and the BOUNDS ARE right-column to set the rightmost column that
may be affected by data shifting.
When the IN COLUMNS clause is specified, the search for the search string is limited to the
columns indicated.
When the IN COLUMNS clause is not specified, the utility uses the values specified or implied by
the BOUNDS ARE values.
When the BOUNDS ARE right-column is greater than the IN COLUMNS to-column, data between
the to-column and the right-column is usually not changed. The data may be shifted either left or
right, depending upon the length of the replacement string. If shifted to the left, the data might
be moved into the compare column range. The data then becomes subject to change, as all or
part of it could be searched and, possibly, replaced.
If the replacement string is larger than the search string and data truncation is allowed, some of
the “in-between” data may be truncated.
04-May-2018 947/1109
CA Endevor® SCM - 17.0
IN COLUMNS Rules
If you use the IN COLUMNS clause, you must follow the rules listed as follows:
The IN COLUMNS from-column value must be less than or equal to the to-column value.
The IN COLUMNS to-column value must be less than or equal to the source element length
associated with the element type record.
The IN COLUMNS from-column and to-column values must be included in the range of FIRST to
LAST, respectively. That is, the values must be within the element type COMPARE FROM and
COMPARE TO values, inclusively.
If only a single column number is specified, the utility assumes it represents the from-column
value. The to-column is calculated as the from-column plus the size of the search string less 1.
If only the to-column is specified, the from-column value is assumed to be the left-column value
specified or implied in the BOUNDS ARE clause.If both from-column and to-column are omitted,
they adopt the values specified or implied by the BOUNDS ARE clause.
If only a single column number is specified in the BOUNDS ARE clause, the utility assumes it
represents the left-column of the range.
If the left-column value is omitted from the BOUNDS ARE clause, the utility defaults to FIRST.
FIRST reflects the COMPARE FROM value of the element type.
If the right-column value is omitted from the BOUNDS ARE clause, the utility defaults to LAST.
LAST reflects the COMPARE TO value of the element type.
If the BOUNDS ARE left-column does not fall within the IN COLUMNS from-column--to-column
range, the IN COLUMNS from-column (or the first column of the element type's compare column
range) is used as the beginning column for the search and replace operation.
If no blanks appear between the search string and the rightmost column of the modifiable range,
data up to and including that rightmost column is shifted left. Blanks are inserted at the rightmost
column of the modifiable range.
04-May-2018 948/1109
CA Endevor® SCM - 17.0
If at least one blank occurs between the text and the rightmost column of the modifiable range
but there are no repeating blanks within this range of data, blanks are inserted at the last blank
within the range. The data preceding that blank is shifted to the left.
If the data between the search string and the rightmost column of the modifiable range contains
at least two consecutive blanks, additional blanks are inserted at the first occurrence of the
repeating blank characters.
The modifiable range in this example is 3 through 12. A blank is inserted at column 12 to
accommodate for the shorter replacement string. The remaining portion of the original text is not
modified at all, as it is outside the range defined.
Data from the original string to the rightmost column of the modifiable range is searched from
left to right. All repeating blank characters are consumed as required to perform the substitution.
When the appropriate number of blanks have been consumed, the data between the end of the
text string and the rightmost column of the modifiable range is shifted to the right and the
replacement string is inserted into the record.
If there are not enough extra blank characters and data truncation is permitted (specified in the
request), the utility performs data truncation. The data at the rightmost column of the modifiable
range is deleted, as necessary, to provide space for the replacement string. The utility issues a
cautionary message and continues processing the element.
If there are not enough blank spaces for the replacement string and data truncation is prohibited,
the utility does the following:
Generates an error message.
Displays the data for the element on the Search and Replace Utility Execution Report.
Continues to search the element for other search and replace operations.
04-May-2018 949/1109
CA Endevor® SCM - 17.0
Example 1
BOUNDS ARE: 1 and 26
IN COLUMNS: 3 and 10
+----1----+----2...
Original text: AABBBCCCCDDDDDxxx
Search string: BBB
Compare range: 3-10
Replacement string: EEEEEE
Updated text: AAEEEEEECCCCDDDDD
The modifiable range in this example is 3 through 26. The replacement string fits within the compare
columns and is only three characters longer than the search text. Consequently, the three blanks at
the end of the original text are consumed by the replacement string as the data shifts to the right.
Example 2
BOUNDS ARE: 1 and 10
IN COLUMNS: 3 and 10
+----1----+----2...
Original text: AABBBCCCCDDDDDxxx
Search string: BBB
Compare range: 3-10
Replacement string: EEEEEE
Truncation permitted: AAEEEEEECDDDDDxxx
Truncation prohibited: Error
The modifiable range in this example is 3 through 10. The replacement string is too long to replace
only the search string within the modifiable range. If truncation is permitted, the utility replaces the
search string, and the characters following the search string up through column 10, with the
replacement string. The remainder of the original text, starting in column 11, is not modified.
If truncation is not permitted, you receive an error message and processing stops for this element.
Example 3
BOUNDS ARE: 1 and 23
IN COLUMNS: 3 and 10
+----1----+----2...
Original text: AABBBxxCCxxDDDDxxxGGG
Search string: BBB
Compare range: 3-10
Replacement string: EEEEEEE
Updated text: AAEEEEEEExCCxDDDDxGGG
The modifiable range in this example is 3 through 23. The replacement string can replace the search
string and shift data to the right, within the modifiable range. Repeating blanks are consumed in such
a way as to shift the remainder of the original string to the right--the replacement string is four
characters longer than the search string so four blanks were consumed.
04-May-2018 950/1109
CA Endevor® SCM - 17.0
The first occurrence of B is replaced by QQ. The utility begins its search for the next appearance of B
after the second Q in the text string.
Note: The results of search and replace with multiple occurrences of the search string may
not be what you expect, due to data being shifted into and out of the compare column
range by replacement strings.
If you had a compare column range of 1-4 in the previous example, the utility would not replace the
second occurrence of B, because the search string is now outside the specified column range.
Similarly, if a replacement string is shorter than the search string, data may move into the compare
column range that would not otherwise be included in the search.
Execution Report
Contains information about the execution of each request.
Summary Report
Summarizes each request processed. The summary indicates the element name, the return code,
the number of matches found, the location where the match was found, and the location where
the element was added (updated) back into CA Endevor® SCM.
04-May-2018 951/1109
CA Endevor® SCM - 17.0
Statement Number
The statement number associated with a SEARCH ELEMENT request.
If the SEARCH ELEMENT request contains multiple FOR TEXT clauses and at least one search string
was found in the element, multiple report lines are generated for the element. The first line
provides the element information, and lists the total number of matches found. Each additional
line for the element (numbered nn.1, nn.2...nn.x, for x number of FOR TEXT clauses) lists the
number of matches found for a specific FOR TEXT clause.
Page Number
The page number on the Search and Replace Utility Execution Report at which processing for the
element began.
Element
The name of the CA Endevor® SCM element that was processed.
Return Code
The return code associated with the element's SEARCH ELEMENT request.
Lines Searched
The number of times the FOR TEXT clauses are searched for the FOR TEXT string.
Matches Found
The number of times the FOR TEXT strings were found. This value represents the actual number
of occurrences, not the number of lines that contain the search string.
04-May-2018 952/1109
CA Endevor® SCM - 17.0
Scenario 3--A search in replacement mode, using the SEARCH ENVIRONMENT MAP feature,
multiple FOR TEXT clauses, and the BOUNDS ARE parameter.
Three elements constitute the sample elements for demonstrating the effects of the SEARCH
ELEMENT SCL statement and its optional parameters. The sample elements each represent a
different type: C source code (type C), COBOL source code (type COB), and text (type TXT). To
highlight the SEARCH ENVIRONMENT option, the type C and type COBOL elements are stored in
Stages A and B, respectively, in the first environment. The type TXT element is stored at Stage D of
the second environment. Stage A in this example is the entry stage for the first environment. Entry
stages are defined through the C1DEFLTS environment table.
When the OPTIONS SEARCH ENVIRONMENT clause is not coded, the utility searches only Stage A
of the first environment. This happens in Scenario 1.
When the OPTIONS SEARCH ENVIRONMENT ONLY clause is specified, the utility searches both
Stages A and B of the first environment. This happens in Scenario 2.
When the OPTIONS SEARCH ENVIRONMENT MAP clause is specified, the entire map is searched.
This happens in Scenario 3.
Test Elements
The utility is executed against three elements:
HELLO.TXT, which is a text file that further explains (sets) the scene
The results of the search depend upon the attributes of each element as well as the information
provided in the SEARCH ELEMENT request.
04-May-2018 953/1109
CA Endevor® SCM - 17.0
HELLO.C Element
Element HELLO.C
#include <stdio.h>
void main()
{
printf("Hello, world!\n"); /* print 'Hello' message */
}
HELLO.COB Element
Element HELLO.COB
000100 ID DIVISION.
000200 PROGRAM-ID. HELLO.
000300 AUTHOR. DEVELOPMENT.
000400 INSTALLATION. CA.
000500 DATE-WRITTEN. FEBRUARY 14, 1994.
000600 DATE-COMPILED.
000700*************************************************************
000800* TRIVIAL PROGRAM TO DISPLAY 'HELLO' MESSAGE *
000900*************************************************************
001000 SKIP3
001100 ENVIRONMENT DIVISION.
001200 CONFIGURATION SECTION.
001300 SOURCE-COMPUTER. IBM.
001400 OBJECT-COMPUTER. IBM.
001500 INPUT-OUTPUT SECTION.
001600 FILE-CONTROL.
001700**************
001800 DATA DIVISION.
001900**************
002000************************************************
002100 FILE SECTION.
002200************************************************
002300************************************************
002400 WORKING-STORAGE SECTION.
002500************************
003000**************************************************************
003100**************************************************************
003200*******************
003300 PROCEDURE DIVISION.
003400*******************
003500 SKIP1
003900 DISPLAY 'HELLO, WORLD!'
004500 GOBACK.
HELLO.TXT Element
Element HELLO.TXT
Three elements, all named HELLO, comprise the sample elements for
demonstrating the effects of the SEARCH ELEMENT SCL statement and
its optional parameters. The sample elements are of type C, COB and
TXT representing C source code, COBOL source code and this text
document. To further highlight the SEARCH ENVIRONMENT option, the
type C and COBOL elements will be stored in stages A and B,
respectively, in the first environment and the type TXT element
will be stored at stage D of the second environment; the environment
mapping and the element location established for the sample reports
is as follows:
04-May-2018 954/1109
CA Endevor® SCM - 17.0
+--------+ +-----------------------------+
| | | |
| V | V
+------------+------------+ +-------------------------+
| STAGE A | STAGE B | | STAGE C | STAGE D |
+------------+------------+ +------------+------------+
| SYS: SYS2 | | | | |
| SBS: BASE | | | | |
| TYP: C | | | | |
| ELM: HELLO | | | | |
| | SYS: SYS2 | | | |
| | SBS: BASE | | | |
| | TYP: COB | | | |
| | ELM: HELLO| | | |
| | | | | SYS:SYS2 |
| | | | | SBS:BASE |
| | | | | TYP:TXT |
| | | | | ELM:HELLO |
+------------+------------+ +------------+------------+
Environment: BATCHEN2 Environment: BATCHEN3
When OPTIONS SEARCH ENVIRONMENT is omitted, only stage A, the entry
stage of the environment, is searched. When OPTIONS SEARCH ENVIRONMENT
ONLY is specified, both stages A and B are searched, because A is the
entry stage.
(Note: If B is the entry stage, only B is searched.)
Finally, when OPTIONS SEARCH ENVIRONMENT MAP is specified, the entire
map is searched. In all cases, the first occurrence of an element is
processed.
04-May-2018 955/1109
CA Endevor® SCM - 17.0
As mentioned above, the Search and Replace utility found 6 matches of the FOR TEXT string. The
location in which the matches were found is listed.
Note that there is no entry in the LOCATION OF ADD/UPDATE OPERATION field. This is because the
utility is operating in search-only mode. The element is not changed and not updated.
You do not code the OPTIONS UPDATE ELEMENTS clause, but you do include a replacement string
in the SCL.
In this scenario, assume the ENSSCLOT DD statement has been allocated in the execution JCL.
SEARCH ELEMENT SCL is generated for the element containing the search string.
The utility searched two elements, HELLO.C and HELLO.COB, but only element HELLO.C contains a
match for the search string. Element HELLO.COB does contain the letter I, but not in lowercase
format. Because the search string is case-sensitive, the utility does not consider the text a match.
The Search and Replace utility found three matches in element HELLO.C and no matches in HELLO.
04-May-2018 956/1109
CA Endevor® SCM - 17.0
The Search and Replace utility found three matches in element HELLO.C and no matches in HELLO.
COB. The report lists the location where both elements were found. Note that the utility searched
both Stage A and Stage B of environment BATCHEN2.
There is an entry in the LOCATION OF ADD/UPDATE OPERATION field, for element HELLO.C. This
entry is for reference purposes only. The element is not modified and added or updated back into CA
Endevor® SCM because the OPTIONS UPDATE ELEMENTS clause was not coded in the SEARCH
ELEMENT request. The entry is provided to let you know what location will be affected should you
decide to update the element with the replacement string.
04-May-2018 957/1109
CA Endevor® SCM - 17.0
BOUNDS ARE is set to BOUNDS ARE 1 TO LAST to demonstrate type compare column checking in
relation to the SCL statements.
WHERE CCID limits the search to those elements whose CCID is CCID-02.
The CCID and comment provided in the OPTIONS clause are assigned to the element when it is added
(updated) back into CA Endevor® SCM.
LIST DETAILS tells the utility to print the original line of text where the search string is found and the
line of text after the string is replaced.
UPDATE ELEMENTS indicates that the element is to be added or updated into CA Endevor® SCM after
the text string is replaced.
The utility searched only one element--HELLO.TXT. The element was found up the map, in Stage D of
BATCHEN3. Substitution was performed, as appropriate, for each FOR TEXT clause.
Note message ENBS048E (immediately after the SCL request). A matching element was found in
Stage A of environment BATCHEN2, but the column values specified in the SEARCH ELEMENT request
are outside the compare column values for the element. This is why only one element was searched.
Note the information message lines ENBS016I and ENBS017I. ENBS016I lines present the original line
of text containing the search string. ENBS017I lines show the line of text after the search string has
been replaced.
A processing code of 12 was returned for the request. The utility processes a request as long as the
return code does not exceed 12.
The Search and Replace utility found a total of 66 matches for the search strings in the SEARCH
ELEMENT request. All information for the element is presented on the first line for Statement 1.
Statement line 1.1 indicates the number of matches found for the first FOR TEXT clause. Statement
line 1.2 indicates the number of matches found for the second FOR TEXT clause.
Although the element was found in Stage D of environment BATCHEN3, it is added into CA Endevor®
SCM at the entry stage (Stage A) of the base environment (BATCHEN2).
+--------+ +---------------------------------+
04-May-2018 958/1109
CA Endevor® SCM - 17.0
+--------+ +---------------------------------+
| | | |
| V | V
+------------+------------+ +-----------------------+
| S$AGE A | S$AGE B | | S$AGE C | S$AGE D |
+------------+------------+ +------------+----------+
| SYS: SYS2 | | | | |
| SBS: BASE | | | | |
| $YP: C | | | | |
| ELM: HELLO | | | | |
| | SYS: SYS2 | | | |
| | SBS: BASE | | | |
| | $YP: COB | | | |
| | ELM: HELLO | | | |
| | | | |SYS: SYS2 |
| | | | |SBS: BASE |
| | | | |$YP: $X$ |
| | | | |ELM: HELLO|
+------------+------------+ +------------+----------+
Env*ronment: BA$CHEN2 Env*ronment: BA$CHEN3
When OP$IONS SEARCH ENVIRONMEN$ *s om*tted, only the entry stage of
the env*ronment, *s searched. When OP$IONS SEARCH ENVIRONMEN$ ONLY *s
spec*f*ed, both stages A and B of the entry env*ronment are searched.
F*nally, when OP$IONS SEARCH ENVIRONMEN$ MAP *s spec*f*ed, the ent*re
map *s searched. In all cases, the f*rst occurrence of an element
*s processed.
You might want to use this option to address problems that can occur when the component data
contains out of date information. For example, an error occurs when using LL (List Listing) from the
Quick Edit or List Element panels for an element that was moved but not regenerated. In that case,
the component data points to the list lib used when the element was last generated, not to the
current list lib in which the listing resides. This causes the LL to fail because the member is no longer
present in that library. The same problem can exist for other output libraries (such as LOADLIBs) and
automated CONDELE with 'PARM=*COMPONENTS'.
Any user with ESI security move authority for the element is authorized to update the component
data at stage 2, if it is a non-entry stage. Any user with ESI security update authority for the element
is authorized to update the component data at stage 1, even if stage 1 is a non-entry stage. As with
element source changes, a history of component data changes is maintained. Therefore, a user can
see who changed output component data and when the change was made.
The JCL used to execute this utility can be found in member ENBSRPL1, in the JCL library iprfx.iqual.
CSIQJCL. To specify the changes you want, you need to code an SCL statement in the JCL. The SCL
specifies what component lists will be searched, what data set names will be searched for, and what
data set names they will be replaced with.
In addition to replacement mode, you have the option to run the utility in validate mode to ensure
the SCL is properly coded, or in search-only mode, which produces a report showing the component
lists that include the data set names that are the object of your search.
04-May-2018 959/1109
CA Endevor® SCM - 17.0
1. Add a valid job card at the front of the ENBSRPL1 job stream.
2. Change the data set names and other variables in the JCL to the appropriate values for your
installation.
3. Code a Search Element Component List statement in the JCL's ENSSCLIN DD statement, as
appropriate for the action you want to perform.
To search for and replace a data set name, code the For clause and the Replace With clause
and run the utility in the replacement mode by including the Options clause with the Update
option. To search for and replace more than one data set name, you can include multiple
combinations of the For clause and Replace With clause in one Search Element Component
List statement.
Note: Before you update the component list, you may want to produce a report
that lists the data sets found by the search. To produce a report instead of updating
the component list, make sure that your SCL does not include the Update option on
the Options clause. To produce a report, code at least the required keywords and
variables of the Search Element Component List statement, which includes
specifying the complete location of the element and the FOR clause to specify the
data set you are searching for. However, do not include the Options clause Update
option. To search for more than one data set name, you can include more than one
For clause in one Search Element Component List statement.
The SCL statement you code is used to specify what action the utility performs.
4. (Optional) Add the validate parameter in the execution JCL after the PARM=ENBS1000
statement:
PARM='ENBS1000VALIDATE'
You can abbreviate VALIDATE in the parameter, using any of the following entries: V, VA, VAL,
VALID, VALIDA, or VALIDAT
The utility will operate in validate mode.
If you specified the validate parameter, then the utility parses and verifies all the requests
in the generated SCL statements for proper syntax, but does not execute the requests
even if no syntax or validation errors are found. If no errors are found, the SCL statements
are formatted, but processing stops after validation. The SCL actions are not performed.
Errors other than syntax errors are not noted at this time.
If you did not specify the validate parameter, then the utility parses and validates all the
requests before processing them. If the parser or validation routine detects an error, the
utility will not execute any of the statements. The parsing routine attempts to parse all of
the control statements before terminating. If no errors are found, then the SCL action is
performed.
04-May-2018 960/1109
CA Endevor® SCM - 17.0
If the SCL does not include the Update option, then a report is produced.
If the SCL does include the Update option, then the component list's output data set
name that is the object of the search (as specified in the FOR clause) is replaced with
the data set name (specified in the Replace clause).
►─ ──┬──────────────────────────────┬─────────────────────────────────────────►
└─┬─ THRough ─┬─ element-name ─┘
└─ THRu ────┘
►─ FROm ─ ENVironment ─ env-name ─ SYStem ─ sys-name ─────────────────────────►
►─ SUBsystem ─ subsys-name ─ TYPe ─ type-name ────────────────────────────────►
►─┬─ STAge ─ stage-id ────────────┬─ FOR ─┬─────────────────┬─ 'dsname' ──────►
└─ STAge NUMber ─ stage-number ─┘ └─ OUTput DSName ─┘
►─┬──────────────────────────────────────────────────┬────────────────────────►
└─ REPlace WITh ─┬────────────────────┬─ 'dsname' ─┘
└─ OUTput DSName ────┘
►─┬──────────────────────────────┬────────────────────────────────────────────►
└─ WHEre ─ ¤ ─┬──────────┬─ ¤ ─┘
├─┤ CCID ├─┤
└─┤ PRO ├──┘
►─┬───────────────────────────────────────────────────┬─ . ───────────────────┤
└─ OPTion ─ ¤ ─┬──────────────────────────────┬─ ¤ ─┘
├─ CCId ─┬──────┬─ ccid ───────┤
│ ├─ EQ ─┤ │
│ └─ = ──┘ │
├─ COMment ─┬──────┬─ comment ─┤
│ ├─ EQ ─┤ │
│ └─ = ──┘ │
├─ LISt DETails ───────────────┤
└─ UPDate ─┬───────────┬───────┘
└─ ELEment ─┘
Expansion of CCID
┌─ , ────┐
├── CCId ─┬──────────────────────┬──┬─ EQ ─┬── ( ─▼─ ccid ─┴─ ) ──────────────┤
└─ OF ─┬─ ANY ◄ ───────┤ └─ = ──┘
├─ BASe ────────┤
├─ GENerate ────┤
├─ LASt ACTion ─┤
└─ RETrieve ────┘
Expansion of PRO
┌─── , ────────┐
├── PROCessor GROup ─┬─ EQ ─┬─ (─ ▼─ group name ─┴─ ) ─────────────────────────┤
└─ = ──┘
Parameters
THRough element
04-May-2018 961/1109
CA Endevor® SCM - 17.0
THRu element
(Optional) Indicates that a range of elements are to be searched, up to and including the
element named in this clause. The element in the Search Element Component List clause
specifies the first element in the range.
FROM
Identifies the inventory location from which the search begins. You must use the keywords
environment, system, subsystem, type, and either the stage or the stage number.
ENVironment env-name
Identifies the environment. The environment must be fully specified, you cannot use a name
mask.
SYStem sys-name
Identifies the system. You can fully specify the name or use name mask.
SUBsystem subsys-name
Identifies the subsytem. You can fully specify the name or use name mask.
TYPe type-name
Identifies the type. You can fully specify the name or use name mask.
STAge stage-id
FOR dsname
04-May-2018 962/1109
CA Endevor® SCM - 17.0
WHEre
(Optional) Specifies additional element selection criteria. Limits the search to only those elements
whose CCID or processors group match the specified value.
OF ANY|BASe|GENerate|LASt ACTion|RETrieve
(Optional) Specifies where the matching CCID can be located to limit the search to only those
elements whose base, generate, last action, or retrieve CCID match the CCID specified in the
request.
ANY
(Optional) All CCIDs in the current MCF are searched. The default.
BASe
(Optional) All CCIDs in the current MCF associated with a base level element are searched.
GENerate
(Optional) All CCIDs in the current MCF associated with a generate action on an element are
searched.
LASt ACTion
(Optional) All CCIDs in the current MCF associated with the last action on an element are
searched.
RETrieve
(Optional) All CCIDs in the current MCF associated with a retrieve action on an element are
searched.
OPTions
(Optional) The options clause allows you to further qualify your request. You can specify none,
one, or more than one option. The CCID and COMMENT options maybe required depending on
your element system record requirements. The Update Element option is required to run the
utility in replacement mode.
04-May-2018 963/1109
CA Endevor® SCM - 17.0
LISt DETails
(Optional) Indicates that you want to list, on the Search and Replace Utility Execution Report,
each output data set name component found and, if run in replace mode, each new output
data set name. Each element searched, along with the number of matches found in that
element (0 to 99999), is printed to the execution and summary report, regardless of the LIST
DETAILS option setting.
UPDate ELEment
(Optional) Indicates that the utility is operating in replacement mode. The utility replaces the
data set name specified in the For clause with the data set name specified in the Replace
clause. The utility operates in search-only mode, if either the Replace With clause or the
Update Element clause is not coded.
04-May-2018 964/1109
CA Endevor® SCM - 17.0
Data Sets
An Endevor LIB (ELIB) is a high-performance alternative to OS partitioned data sets under CA
Endevor® SCM. You can organize CA Endevor® SCM base, delta, and listing libraries as ELIB data sets.
Three concepts are important when working with ELIBs. These concepts are page size, record format,
and target directory page.
Page size:
Specifies the size of the control interval used by ELIB for storage. All blocking is internal to ELIB
and not available to operating system utilities. You cannot reblock an ELIB data set. If reblocking is
necessary, reallocate the data set and copy members into it.
Record format:
ELIB data sets store members in compressed format with the record length stored at the front of
each record. This format allows members of different record lengths to be stored in one ELIB data
set.
CA Endevor® SCM provides three utilities for use when setting up and maintaining ELIB data sets. The
following lists these utilities and the purpose of each:
BC1PNLIB
Set up, maintain, and print information about ELIB data sets.
04-May-2018 965/1109
CA Endevor® SCM - 17.0
BC1PNLST
Print information about ELIB data sets.
BC1PNCPY
Copy library members from and to ELIB data sets, and to copy members from and to any CA
Endevor® SCM library format.
Note: The ELIB utilities BC1PNLIB, BC1PNCPY, and BC1PNLST cannot be executed within a
CA Endevor® SCM processor.
BC1PNLIB Utility
This utility lets you set up and maintain the ELIB data sets. It also lets you perform five actions against
ELIB data sets:
A Sample JCL to execute the BC1PNLIB ELIB utility is provided with the CA Endevor® SCM installation
files as member BC1JNLIB in the installation JCL library.
Initialize Function
This function of the BC1PNLIB utility initializes an ELIB data set. Space must have been allocated for
the library. The syntax for the INITIALIZE function of the BC1PNLIB utility is shown next:
04-May-2018 966/1109
CA Endevor® SCM - 17.0
INITIALIZE
Indicates that you want the BC1PNLIB utility to initialize an ELIB data set. You must have allocated
space for this data set.
DDNAME
The DDname of the data set you want to initialize.
DSNAME
(Optional) Data set name for this ELIB data set. If you code the DSNAME statement, the system
validates the DSname in this statement against the DSname in the JCL.
TYPE
(Optional) Indicates whether this ELIB is a VSAM cluster or a BDAM data set. If you do not code a
TYPE statement, the BC1PNLIB utility reads this information from the JCL.
PAGE SIZE
(Optional) If you are using VSAM clusters, page size is system-defined by the IDCAMS utility as
eight bytes less than the control interval size.
If you are using BDAM data sets, page size equals block size. Block size is specified in the JCL. If
you also code a PAGE SIZE statement, the system validates it against the block size you have
specified in the JCL.
If you code a PAGE SIZE statement, the entry can have up to six numeric characters.
ALLOCATE PAGES
Determines number of pages in this ELIB data set. You can specify two numbers:
#-primary-pages
Indicates the number of pages initialized as primary storage for this ELIB data set.
04-May-2018 967/1109
CA Endevor® SCM - 17.0
#-secondary-pages
Indicates number of pages initialized as secondary storage during each automatic expansion
of the ELIB data set.
If you do not want to assign a secondary allocation quantity, do not specify secondary pages.
The primary and the secondary entries can be up to six numeric characters.
RESERVE PAGES
(Optional) Determines when the system allocates a secondary storage block to this ELIB data set.
Expressed as a number of pages (up to six numeric characters). When this number of pages
remain unused within the current storage allocation, CA Endevor® SCM automatically attempts to
allocate a secondary storage block.
If you assign a RESERVE PAGES value, assign a value that is greater than the number of pages
you expect the largest data set member to take up. Very often, assigning a value equal to one
cylinder of storage is adequate.
If you omit this clause, the reserve threshold defaults to 1/16 of the number of pages
allocated to primary storage. For example, if the primary allocation is 400, the reserve
threshold defaults to 25 (400/16).
If you assign a value of 0, ELIB will not automatically expand. In this situation, once the
primary allocation is filled any attempts to store a new member fails until you manually
expand the library.
Note: If ELIB tries to expand the library and runs out of space, it automatically sets the
reserve threshold value to zero. For more information about resolving this problem, see
Expand or Compress ELIB Data Sets (see page 434).
DIRECTORY PAGES
(Optional) Number of target directory pages. The default allocation is 7 pages.
If you want to allocate a different number of target directory pages, enter that number (must be
greater than 7) in this statement. Can be up to six numeric characters.
When estimating the number of target directory pages bear in mind that:
This means that if your page size is 4096 bytes, a target directory page could hold [(4096-32)/84]
= 48 members.
Note: If a member is added and the directory page is full, the page overflows, eventually
degrading performance. To avoid overflow, allocate target directory pages so that
member directory information fills less than 50 percent of the available target directory
page space.
Example: Your target directory page size is 4096 bytes, and you want to store directory
04-May-2018 968/1109
CA Endevor® SCM - 17.0
Example: Your target directory page size is 4096 bytes, and you want to store directory
information for approximately 24 members per page (half of the maximum of 48 members). If
you estimate that 1,000 members will reside in the data set, allocate the data set with 1,000/24 =
42 target directory pages.
If you omit this clause, the BC1PNLIB utility automatically calculates the number of pages within
the ELIB data set needed for its directory. It does this step by allocating enough target directory
pages to support one member per each four pages of the primary allocation.
DESTROY TO REUSE
(Optional) Code this statement only if you are re-initializing an ELIB data set.
Note: If you code this statement, all data in the existing data set are lost.
Expand Function
Normally, ELIB expands automatically according to your secondary allocation value. The EXPAND
function of the BC1PNLIB utility allows you to expand ELIB data sets manually. The syntax for the
EXPAND function of the BC1PNLIB utility is shown next:
The following describes the keywords used in the syntax for the EXPAND function:
EXPAND
Indicates that you want the BC1PNLIB utility to acquire secondary storage for an ELIB data set.
DDNAME
The DDname of the data set you want to expand.
DSNAME
(Optional) Data set name for this ELIB data set. If you code the DSname statement, the system
validates the DSname in this statement against the DSname in the JCL.
ALLOCATE PAGES
(Optional) Determines number of additional pages in the expanded ELIB data set. If you do not
code this statement the secondary allocation originally specified during the INITIALIZE function is
used.
04-May-2018 969/1109
CA Endevor® SCM - 17.0
RESERVE PAGES
(Optional) Lets you respecify the RESERVE threshold established in the INITIALIZE function for this
library. If you want to keep the existing RESERVE threshold, do not code this statement.
Adjust Function
The ADJUST function allows you to modify the specifications for secondary storage and the reserve
threshold for an ELIB data set. The syntax for the ADJUST function is shown next:
The following describes the keywords used in the syntax for the ADJUST function:
ADJUST
Indicates that you want the ADJUST function of the BC1PNLIB utility to adjust the reserve
threshold and/or the secondary storage allocation.
DDNAME
The DDname of the data set you want to adjust.
DSNAME
(Optional) Data set name for this ELIB data set. If you code the DSname statement, the system
validates the DSname in this statement against the DSname in the JCL.
ALLOCATE PAGES
(Optional) Determines number of pages to be allocated in subsequent secondary allocations.
RESERVE PAGES
(Optional) Allows you to respecify the RESERVE threshold established in the INITIALIZE function
for this library. If you want to keep the existing RESERVE threshold, do not code this statement.
Note: When using the ADJUST function, you may code the ALLOCATE PAGES statement or
the RESERVE PAGES statement, or both statements.
04-May-2018 970/1109
CA Endevor® SCM - 17.0
Reorganize Function
The reorganize (REORG) function of the BC1PNLIB utility allows you to reorganize ELIB data sets.
During this process, you can respecify the number of pages allocated to the data set directory. The
system re-allocates storage for the directory according to this specification, and rewrites the
directory entries. The syntax for the REORG function of the BC1PNLIB utility is shown next:
The following describes the keywords used in the syntax for the REORG function:
REORG
Indicates that you want the REORG function of the BC1PNLIB utility to respecify the number of
pages allocated to the directory of an ELIB data set.
DDNAME
The DDname of the data set you want to reorganize.
DSNAME
(Optional) Data set name for this ELIB data set. If you code the DSname statement, the system
validates the DSname in this statement against the DSname in the JCL.
DIRECTORY PAGES
Indicates the number of pages you want to allocate for the directory of the ELIB data set specified
by the DDname.
Inquire Function
The INQUIRE function of the BC1PNLIB utility allows you to print summary statistics about the library
directory and/or individual members, and also allows you to check the integrity of the library. The
following syntax is for the INQUIRE function of the BC1PNLIB utility:
The following describes the keywords used in the syntax for the INQUIRE function:
INQUIRE
04-May-2018 971/1109
CA Endevor® SCM - 17.0
INQUIRE
Indicates that you want to use the INQUIRE function of the BC1PNLIB utility.
DDNAME
(Required) The DDname of the data sets for which you want to print information.
OPTION
(Optional) Allows you to specify more reporting options. You can use any or all options whenever
you run the INQUIRE function of the BC1PNLIB utility. If you omit this clause, CA Endevor® SCM
prints only data set header information.
MEMBERS--Tells CA Endevor® SCM to print footprint information plus member size in pages,
records, and bytes.
BC1PNLST Utility
This utility lets you inquire against directories and/or members of an ELIB data set. This utility
provides read-only access to ELIB data sets.
A Sample JCL to execute the BC1PNLST ELIB utility is provided with the CA Endevor® SCM installation
files as member BC1JNLST in the installation JCL library.
BEND--BC1PNLST Syntax--OTH
The following keywords in the INQUIRE request allow you to specify options that provide more
detailed output. Code any or all of the options that you want to use.
INQUIRE
Indicates that you want to use the INQUIRE function of the BC1PNLST utility to retrieve
information about an ELIB data set.
DDNAME
The DDname of the data sets you want to inquire against.
OPTION
(Optional) Lets you specify more reporting options. You can use any or all of these options
whenever you run the INQUIRE function of the BC1PNLST utility. If you do not want more detail,
you can omit this clause entirely; only summary library information is printed.
04-May-2018 972/1109
CA Endevor® SCM - 17.0
DIRECTORY
The DIRECTORY option displays the number of members for each directory page, and
summary directory usage statistics.
MEMBERS
The MEMBERS option lists each member of the library, with full CA Endevor® SCM footprint
information plus member size in pages, records, and bytes.
BC1PNCPY Utility
This utility lets you copy between any CA Endevor® SCM supported library types, while preserving the
original CA Endevor® SCM footprint of copied members. You can use this utility to copy all or selected
members of an existing base, delta, or listing library from a PDS or PDS/E to an ELIB or the reverse. A
Sample JCL to execute the BC1PNCPY ELIB utility is provided with the CA Endevor® SCM installation
files as member BC1JNCPY in the installation JCL library.
For large libraries, BC1PNCPY takes a great deal of time to run. It requires exclusive control
of the input and output libraries, for integrity.
Note: When an element name is longer than eight characters and you copy to a PDS or PDS
/E, the element name is truncated at eight characters. When truncation occurs, different
input members can truncate to the same input name.
If the UPDATE IF PRESENT option is specified, the last duplicate member overwrites all
prior duplicates. If the UPDATE IF PRESENT option is not specified, only the first
encountered duplicate member is overwritten. Any subsequent duplicate member names
does not overwrite the first duplicate member.
04-May-2018 973/1109
CA Endevor® SCM - 17.0
BEND--BC1PNCPY Syntax--OTH
The following keywords in the COPY request let you specify options that provide more detailed
output. Code any or all options that you want to use.
COPY
Indicates that you want to use the BC1PNCPY utility.
UNPACKED
(Optional) The UNPACKED option is used with PDS or PDS/Es only, and only if a PDS or PDS/E is
not a CA Endevor® SCM compressed library. When you use this option with the INPUT statement
BC1PNCPY does not attempt to decompress the members being read from the input data set.
DSNAME
(Optional) If you use the DSNAME option, the data set name of the input library is validated
against the DDNAME in the JCL. If the DSN contains periods, it must be enclosed in single quotes.
UNPACKED
(Optional) The UNPACKED option is used with PDS or PDS/Es only, and only if a PDS or PDS/E is
not a CA Endevor® SCM compressed library. When you use this option with the OUTPUT
statement, BC1PNCPY does not attempt to compress the members being written to the output
data set.
04-May-2018 974/1109
CA Endevor® SCM - 17.0
DSNAME
(Optional) If you use the DSNAME option, the data set name of the target library is validated
against the DDNAME in the JCL. If the DSN contains periods, it must be enclosed in single quotes.
UPDATE IF PRESENT
(Optional) Use this option to update (replace) members with the same name within the target
library. If you do not use this option, the utility does not replace members of the same name.
Note: A period must be coded at the end of each complete statement. If you specify any
MEMBER [THRU] clauses, enter the period after the last of those clauses. If you specify
more than one MEMBER [THRU] clause, do not code a comma between the clauses.
By default BC1PNCPY's parser stack supports 1000 MEMBER= statements. If more than 1000
statements are needed, the parameter MEMBERS can be passed to the utility using the PARM=
field on the EXEC statement:
//JS10 EXEC PGM=NDVRC1,PARM='BC1PNCPYMEMBERS=nnnnnn'
Note: Specifying this parameter may increase the storage requirements for the step.
Approximately 40 bytes per member is needed. Specify an appropriate REGION size to
accommodate the requests.
3. Allocate the appropriate data set (BDAM data set or VSAM cluster), then initialize the data set
with the ELIB utility program BC1PNLIB.
04-May-2018 975/1109
CA Endevor® SCM - 17.0
VSAM provides better performance by exploiting 31-bit storage and better data set protection
mechanisms. VSAM also supports spanned volumes
BDAM provides slightly better performance and simpler installation and de-installation, but
spanned volumes are not supported.
For an ELIB base library, figure out how many members are in the library, and how much space
they take up in the data set after the data set has been compressed. Then add 20 percent to this
figure, for expansion.
For an ELIB delta library, estimate approximately half the size of the corresponding base library. If
you are an existing CA Endevor® SCM user, you may want to use a larger percentage, to
accommodate for the growth of your delta libraries over time.
For an ELIB listing library, estimate 80% of the space required for the corresponding members in a
PDS or PDS/E (measured after the PDS has been compressed).
You can use the ISPF "3.2" utility to examine space used by a PDS or PDS/E.
Note: If you estimate space requirements that are too low, ELIB lets you increase the
library size without reorganizing.
//ALLOCBDAM EXEC PGM=IEFBR14
04-May-2018 976/1109
CA Endevor® SCM - 17.0
//ALLOCBDAM EXEC PGM=IEFBR14
//LIBRARY DD DSN=ELIB.DATASET,DISP=(NEW,CATLG),
// UNIT=PDASD,SPACE=(CYL,(5,2)),
// DCB=(DSORG=DA,BLKSIZE=4096,LRECL=4096,RECFM=FBS)
In this example, the IEFBR14 utility allocates five cylinders to primary storage and 2 cylinders to
secondary storage. The LRECL and BLKSIZE for this BDAM ELIB data set are 4096 bytes.
To initialize this data set as an ELIB data set, convert your estimated space requirements to their page
equivalents. This step is necessary because the BC1PNLIB utility needs all its specifications in pages.
In BDAM data sets, the BLKSIZE is the same as the page size. The number of 4096-byte pages per
track and per cylinder varies by DASD device, as shown in the following table:
The BDAM data set in this example would therefore have a capacity of 750 pages in primary storage
and 300 pages in secondary storage when using a 3380 device, and 900 pages in primary storage and
360 pages in secondary storage when using a 3390 device.
Use the BC1PNLIB utility to initialize the data set. The following JCL assumes that you are using a 3380
device.
//ELIBINIT EXEC PGM=BC1PNLIB
//STEPLIB DD DISP=SHR,DSN=iprfx.iqual.CSIQAUTU
// DD DISP=SHR,DSN=iprfx.iqual.CSIQLOAD
//*
//* OMIT THE FOLLOWING DCB INFORMATION IF VSAM
//*
//BDAMINIT DD DSN=BDAM.DATASET,
// DCB=(DSORG=DA,BLKSIZE=4096,LRECL=4096,RECFM=FBS),
// DISP=(OLD,KEEP)
//SYSPRINT DD SYSOUT=*
//BSTERR DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
INIT DDNAME = BDAMINIT
PAGE SIZE = 4096
ALLOCATE = (750,300)
RESERVE PAGES = 150
DIRECTORY PAGES = 14
.
INQUIRE DDNAME = BDAMINIT
.
/*
In the previous example, you have allocated and initialized a BDAM data set as an ELIB data set with
750 pages initialized as primary storage. When 150 pages remain in this primary storage area, CA
Endevor® SCM automatically attempts to allocate and initialize secondary storage with a capacity of
300 pages. In addition, you have requested the BC1PNLIB utility to list statistical information about
this data set after initialization.
04-May-2018 977/1109
CA Endevor® SCM - 17.0
Note: The ELIB data set format supports z/OS VSAM extended addressability for VSAM data
sets. The extended addressability feature lets you allocate VSAM data sets that are larger
than 4 GB. If extended addressability is enabled in z/OS for any of your VSAM ELIB data
sets, CA Endevor® SCM recognizes that this option is enabled and handles ELIB access
appropriately. You do not need any changes in CA Endevor® SCM to enable support for
extended addressability. Ask your Storage Administrator to determine whether z/OS VSAM
extended addressability is available for your site and how you can implement it.
To allocate a VSAM cluster, use the IBM IDCAMS utility in a JCL stream similar to the following
sample:
//ALOCVSAM EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE CLUSTER -
(NAME(VSAM.DATASET) -
MASTERPW(plant) -
CONTROLPW(ENDEVOR) -
UPDATEPW(ENDEVOR) -
RECORDSIZE(4088 4088) -
CONTROLINTERVALSIZE(4096) -
SHAREOPTIONS(3,3) -
VOLUMES(BST001) -
CYLINDERS(5,2) -
NONINDEXED -
) -
DATA (NAME(VSAM.DATASET.DATA) -
MASTERPW(plant) -
CONTROLPW(ENDEVOR) -
UPDATEPW(ENDEVOR) -
)
In this example, the IDCAMS utility defines a VSAM cluster named VSAM.DATASET. The control
interval for this data set is 4096 bytes, and the record size is 4088 bytes. In VSAM data sets the record
size is the same as the page size. IDCAMS allocates 5 cylinders of primary storage, and 2 cylinders to
secondary storage for the data set. The data set resides in a DASD volume with a serial number of
BST001. The master password to the data set is plant.
Note: Choose a master password to protect your data. This password is required whenever
you want to delete or rename the cluster. CA Endevor® SCM processing uses the built-in
password ENDEVOR for all update processing. If you omit the master password, this library
is unprotected.
Before initializing this data set as an ELIB data set, convert your estimated space requirements to
their page equivalents. This step is necessary because the BC1PNLIB utility needs all its specifications
in pages.
04-May-2018 978/1109
CA Endevor® SCM - 17.0
In VSAM data sets, the page size is eight bytes smaller than the control interval size, in this case 4088
bytes. The number of 4088 byte pages per track and per cylinder varies by DASD device, as shown in
the following table:
The VSAM data set in this example would therefore have a capacity of 750 pages in primary storage
and 300 pages in secondary storage when using a 3380 device, and 900 pages in primary storage and
360 pages in secondary storage when using a 3390 device.
Note: If you are using VSAM, specify one less page than fits in the primary space allocation.
VSAM uses one control interval for an end-of-file mark. For example, on a 3380 device with
one cylinder of primary space allocation, specify 149 pages per cylinder.
Use the BC1PNLIB utility to initialize the data set. The following JCL assumes that you are using a 3380
device.
//ELIBINIT EXEC PGM=BC1PNLIB
//STEPLIB DD DISP=SHR,DSN=iprfx.iqual.CSIQAUTU
// DD DISP=SHR,DSN=iprfx.iqual.CSIQLOAD
//*
//*
//*
//INITVSAM DD
// DSN=VSAM.DATASET,DISP=(OLD,KEEP)
//SYSPRINT DD SYSOUT=*
//BSTERR DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
INIT DDNAME = INITVSAM
PAGE SIZE = 4088
ALLOCATE = (749,300)
RESERVE PAGES = 150
DIRECTORY PAGES = 14
.
INQUIRE DDNAME = INITVSAM
.
/*
In this example, you have allocated and initialized a VSAM data set as an ELIB data set with 749 pages
initialized as primary storage. When 150 pages remain in this primary storage area, CA Endevor® SCM
automatically attempts to allocate and initialize secondary storage with a capacity of 300 pages. In
addition you have requested the BC1PNLIB utility to list statistical information about this data set
after it has been initialized.
2. Rerun the initialization procedure, with the following more clause: DESTROY TO REUSE.
04-May-2018 979/1109
CA Endevor® SCM - 17.0
2.
Note: If you use this clause, any data currently in the library is destroyed. Use this
option with caution.
The following example shows a sample JCL and the control statements that you can use to
accomplish this task:
//EXPAND EXEC PGM=BC1PNLIB
//STEPLIB DD DISP=SHR,DSN=iprfx.iqual.CSIQAUTU
// DD DISP=SHR,DSN=iprfx.iqual.CSIQLOAD
//INITVSAM DD DSN=VSAM.DATASET,
// DISP=(SHR,KEEP)
//SYSPRINT DD SYSOUT=*
//BSTERR DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
EXPAND DDNAME = INITVSAM
ALLOCATE PAGES = 300
.
INQUIRE DDNAME = INITVSAM
.
/*
In this example, you have specified a secondary storage allocation of 300 pages. This causes two
cylinders of secondary storage to be allocated and initialized for this data set. You have also
requested a listing of statistical information about this expanded data set, using the INQUIRE facility.
Adjust the secondary storage allocation after expanding an ELIB data set, so that subsequent
expansions allocate a different amount of space.
Adjust the reserve threshold so that additional space is allocated based on a different threshold
of unused space.
Reset the reserve threshold after CA Endevor® SCM resets the reserve threshold value to zero. It
does this after attempting to expand a data set and, failing to do so, to prevent repeated failures.
If this situation occurs, follow these procedures:
04-May-2018 980/1109
CA Endevor® SCM - 17.0
Adjust the reserve threshold value (that is, the threshold at which ELIB expands to a new
extent) for future expansions.
You might also want to adjust the secondary allocation quantity assigned during initialization.
The following example shows a sample JCL and the control statements that you can use to adjust an
ELIB data set:
//ADJUST EXEC PGM=BC1PNLIB
//STEPLIB DD DISP=SHR,DSN=iprfx.iqual.CSIQAUTU
// DD DISP=SHR,DSN=iprfx.iqual.CSIQLOAD
//INITVSAM DD DSN=VSAM.DATASET,
// DISP=(SHR,KEEP)
//SYSPRINT DD SYSOUT=*
//BSTERR DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
ADJUST DDNAME=INITVSAM
ALLOCATE PAGES = 600
RESERVE PAGES = 300
.
INQUIRE DDNAME=INITVSAM
.
/*
In this example, a secondary storage allocation of 600 pages was specified, and a reserve threshold of
300 pages. This allocation changes the original specifications for the ELIB data set INITVSAM. After
this code is run, subsequent secondary allocations are 600 pages rather than 300 pages, and the
threshold of unused space that triggers automatic expansion is 300 pages rather than 150.
You have also requested a listing of statistical information about this expanded data set, using the
INQUIRE facility.
Note: ELIB locks the library during the reorganization procedure, but this process is usually
brief.
Note: The reorganization process is memory-intensive. Therefore, give the utility a region
large enough to avoid multiple passes against the directory.
04-May-2018 981/1109
CA Endevor® SCM - 17.0
To reorganize a directory, use JCL and control statements similar to the following sample:
//REORG EXEC PGM=BC1PNLIB
//STEPLIB DD DISP=SHR,DSN=iprfx.iqual.CSIQAUTU
// DD DISP=SHR,DSN=iprfx.iqual.CSIQLOAD
//INITVSAM DD DSN=VSAM.DATASET,
// DISP=(SHR,KEEP)
//SYSPRINT DD SYSOUT=*
//BSTERR DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
REORG DDNAME=INITVSAM
DIRECTORY PAGES = 20
.
INQUIRE DDNAME=INITVSAM
.
/*
In this example, the number of target directory pages allocated to the ELIB data set was reset to 20.
The BC1PNLIB utility allows you to print header information for ELIB data sets, information about
members and/or target directory pages, and to analyze the integrity of the data set.
The BC1PNLST utility allows you to perform all functions except for data set integrity analysis.
To use the INQUIRY function to print header information, use JCL similar to the following sample:
//INQUIRE EXEC PGM=BC1PNLST
//STEPLIB DD DISP=SHR,DSN=iprfx.iqual.CSIQAUTU
DD DISP=SHR,DSN=iprfx.iqual.CSIQLOAD
//ELIB DD DSN=ELIB.DATASET,
// DISP=(SHR,KEEP)
//SYSPRINT DD SYSOUT=*
//BSTERR DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
INQUIRE DDNAME=ELIB
.
/*
04-May-2018 982/1109
CA Endevor® SCM - 17.0
//ELIB DD DSN=ELIB.DATASET,
// DISP=(SHR,KEEP)
//SYSPRINT DD SYSOUT=*
//BSTERR DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
INQUIRE DDNAME=ELIB
OPTION
MEMBERS
.
/*
To use the INQUIRY function to retrieve directory information, use JCL and control statements similar
to the following sample:
//INQUIRE EXEC PGM=BC1PNLST
//STEPLIB DD DISP=SHR,DSN=iprfx.iqual.CSIQAUTU
DD DISP=SHR,DSN=iprfx.iqual.CSIQLOAD
//ELIB DD DSN=ELIB.DATASET,
// DISP=(SHR,KEEP)
//SYSPRINT DD SYSOUT=*
//BSTERR DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
INQUIRE DDNAME=ELIB
OPTION
DIRECTORY
.
/*
04-May-2018 983/1109
CA Endevor® SCM - 17.0
To verify the integrity of an ELIB library, use JCL and control statements similar to the following
sample
//ANALYZE EXEC PGM=BC1PNLIB
//STEPLIB DD DISP=SHR,DSN=iprfx.iqual.CSIQAUTU
// DD DISP=SHR,DSN=iprfx.iqual.CSIQLOAD
//ELIB DD DSN=ELIB.DATASET,
// DISP=(SHR,KEEP)
//SYSPRINT DD SYSOUT=*
//BSTERR DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
INQUIRE DDNAME=ELIB
OPTION
ANALYZE
.
/*
The report produced by the analyze function can contain the following messages:
04-May-2018 984/1109
CA Endevor® SCM - 17.0
Note: For large libraries, BC1PNCPY takes a great deal of time to run. In addition, it requires
exclusive control of the input and output libraries, for integrity.
To copy between CA Endevor® SCM libraries or from/to an external library, use JCL and control
statements similar to the following sample:
//CONVERT EXEC PGM=NDVRC1,PARM='BC1PNCPY'
//STEPLIB DD DISP=SHR,DSN=iprfx.iqual.CSIQAUTU
// DD DISP=SHR,DSN=iprfx.iqual.CSIQAUTH
//CONLIB DD DISP=SHR,DSN=iprfx.iqual.CSIQLOAD
//OLDBASE DD DSN=BST.OLD.BASE,
// DISP=(OLD,KEEP)
//NEWELIB DD DSN=BST.NEW.BASE,
// DISP=(OLD,KEEP)
//SYSPRINT DD SYSOUT=*
//BSTERR DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
COPY INPUT DDNAME = OLDBASE
OUTPUT DDNAME = NEWELIB
.
/*
In this example, the system copies all members from the OLDBASE data set to the NEWELIB data set.
04-May-2018 985/1109
CA Endevor® SCM - 17.0
The Unload, Reload, and Validate utility provides a point-in-time physical recovery mechanism. The
utility can be used to perform the following actions:
Unload all or specific environments and/or systems and their related elements/components.
Reload all or specific environments and/or systems and their related elements/components.
Validate the integrity of all or specific environments and/or systems and their related elements
/components.
The Unload, Reload, and Validate utility provides a point-in-time physical recovery mechanism. It
allows you to backup (unload), restore (reload), and validate the integrity of one or more CA
Endevor® SCM environments in the event of a physical device failure or site disaster.
The Unload function copies all Master Control File environment information (system, subsystem,
type, type sequence, data set, and element master record) to the data set you specify. Then it copies
all the elements in full or incremental mode. If an incremental unload is specified on the Unload
request, then base and delta information is only copied for elements that have changed since the last
unload. During the unload process, validation always occurs to ensure that the elements to be
unloaded meet certain integrity criteria. Any corrupt elements are not unloaded. You can run the
Validate function independent of the Unload function.
The Reload function restores data from the data sets created by the unload process. You can use the
Reload function to recover from hardware failure.
This article discusses the Unload, Reload, and Validate functions performed by program C1BM5000.
For each, there is a brief description of the function, a syntax diagram, and a discussion of the rules
that each follows.
04-May-2018 986/1109
CA Endevor® SCM - 17.0
Note: For the element catalog, the Reload utility uses normal CA Endevor® SCM inventory
management functions which will update the MCF, BASE/DELTA and element catalog and
EINDEX where necessary.
How the Reload utility affects the validity of the ACMQ files in various situations is described next:
Suppose you lose a delta and decide to reload the missing pieces.
In this case the ROOT and XREF files before the reload will contain correct data and thus the
reload will not impact the quality of the content.
Suppose you want to recover some elements that have been deleted from a full or incremental
unload.
In this case, we recommend using Transfer from unload and regenerate the elements. The
Transfer action will rebuild the outputs and the ACMQ data. If you want to use Reload, because
you do not want to rebuild the outputs, ACMQ will be out of sync and you must run a partial
rebuild of the ACMQ data for these reloaded elements.
Unload Function
This function unloads and validates the contents of the VSAM Master Control Files (MCFs), base and
delta files associated with the environments and systems specified on the job request. The file
created by the Unload function contains a backup of all internal MCF definitions (system, subsystem,
type, type sequence, data set, element master record) and base/delta data (element base, element
delta, component base, component delta). Packages contained within a package data set can also be
unloaded.
Unload may be run for an entire environment, or for selected systems within an environment. Unload
may also be directed to backup an entire package data set or individual packages.
Note: The LRECL of the unload data set must be at least 84 bytes larger than the largest
type record length in the unloaded environment or system.
04-May-2018 987/1109
CA Endevor® SCM - 17.0
Regardless of whether you specify a full or incremental unload, all Master Control File environment
information (system, subsystem, type, type sequence, data set, and element master record) is
unloaded to the data set you specify. This step is done so that the environment definitions can be
restored from any unload point.
After unloading the environment information, the function unloads elements in a full or incremental
mode.
This unloading of environment information and elements occurs in the following order:
3. Stage 1 elements.
4. Stage 2 elements.
►─ ─┬──────────────────────────────────────────────┬───────────────────────────►
└─ ENVironment ─ env-name ─ SYStem ─ sys-name ─┘
►─ TO ─ DDName ─ ddname ─ FROm ─ ENVironment ─ env-name ─ SYStem ─ sys-name ───►
►────┬───────────────────┬─────────────────────────────────────────────────────►
└─ CHEckpoint ONLY ─┘
►─ ─┬────────────────────────────────────────────────────────────┬─ . ─────────►◄
│ ┌──────────────────────────────────────────────────────┐ │
└──▼─ EXCLUDE ENVironment ─ env-name ─ SYStem ─ sys-name ─┴──┘
The following syntax provides the parameters for using Unload against one or more package data
sets:
►►─ UNLoad PACkage ─┬─────────────────────────┬─ TO ─ DDName ─ ddname ─ . ────►◄
└─ ID ─ = ─ package-name ─┘
UNLOAD
Specifies the UNLOAD function. You must further qualify the UNLOAD request with one of the
following:
FULL-Unloads Master Control File environment and related base/delta information for all
elements in the environments and systems specified in the FROM statement.
INCREMENTAL-Unloads Master Control File information for all elements in the environments
and systems specified in the FROM statement. Base and delta information are unloaded only
for elements that have changed since the last unload, based on the date/time stamp for each
system. Any number of UNLOAD statements may be coded for a single run.
04-May-2018 988/1109
CA Endevor® SCM - 17.0
Note: Any change to an element (SOURCE, MCF fields or STATUS (that is, SIGNED IN)) is
considered and the unload incremental occurs for these changes.
TO DDNAME
Identifies the DDname to which the unload data set is assigned for environment and package
processing.
Note: If you specify a DDname, you cannot use the CHECKPOINT ONLY clause.
FROM
Allows you to specify the FROM location for a combination of environments and systems to be
unloaded. The qualifying statements are:
SYSTEM-Identifies the system from which information is to be unloaded. A name mask may be
used.
CHECKPOINT ONLY
Causes a FULL UNLOAD request to simply update the system backup timestamp so you can use
something other than the Unload utility to do the full backup and use the Unload utility for
incremental backups. Specify the FULL and the FROM clauses when using this option.
EXCLUDE
Bypasses unload processing for the specified environments and systems that are a subset of the
environments and systems to be unloaded. CA Endevor SCM does issue an Enqueue for the
environment and system combinations specified on the Exclude clause. You can specify multiple
Exclude clauses. Wildcards and placeholders are allowed. For example:
If you specify UNLOAD FULL ENV '*' SYS '*' but do not want to process environment ENVTEST
system SYSTEST, you would specify:
UNLOAD FULL FROM ENV '* '
SYS '*' TO DDNAME UNLODNN EXCLUDE ENV 'ENVTEST' SYS 'SYSTEST'
If you specify more than one Unload SCL statement and they are identical with the exception
of the Exclude clause, then the Exclude clause from the last SCL is the one used.
If you specify more than one Unload SCL statement and they are identical except that the
Exclude clauses are different and the environment and system combinations to be unloaded
overlap, then the most recent Exclude statements apply to the specified environment and
systems to be unloaded. For example:
UNLOAD FULL FROM ENV '*' SYS '*' EXCLUDE ENV 'ENVT*' SYS 'SYST*' TO UNLOAD UNLO
DNN.
In this case, when any environment whose name begins with P is about to be unloaded, then
04-May-2018 989/1109
CA Endevor® SCM - 17.0
In this case, when any environment whose name begins with P is about to be unloaded, then
any environment with the name PROD and the system name SYSX is excluded. In all other
cases, the prior Exclude clause takes effect.
PACKAGE
Required when unloading one or more packages. You may also select a package identifier (ID) to
identify the name of a specific package to be unloaded. You can use a name mask. If you do not
specify a package ID, all packages in the package data is unloaded.
For promotion packages, you cannot specify the package ID of individual historic versions. You
can specify the fully qualified name or mask package ID of the current version. This unloads the
records for all versions of a promotion package.
Full Unloads
All base and delta members and related component list base and delta members are unloaded for
each element associated with the environments and systems specified in the UNLOAD request.
Incremental Unloads
Only elements associated with the environments and systems specified in the Unload request that
have changed since the last unload is unloaded.
When Unload is successfully run against a system, the Master Control Record for that system is
updated with the date/time of the unload. During an incremental unload, the date/time stamp on
each element is compared with the date/time stamp on the Master Control Record for the system to
which the element belongs. Only those elements with a date/time stamp that is more recent than the
date/time stamp in the Master Control File system record is selected during incremental unload
processing.
Package Unloads
All packages contained in the package data set defined in the C1DEFLTS table will be unloaded.
Optionally, individual packages may be selected for unloading using the ID parameter.
Historic versions of promotion packages are unloaded with the current version. In the unload SCL,
you cannot specify the package ID of individual historic versions of a promotion package. This ensures
the integrity of the entire package. Always specify the fully qualified or mask package ID of the
current version you want to unload. The unload utility unloads the records for all versions of that
promotion package.
04-May-2018 990/1109
CA Endevor® SCM - 17.0
If an error is detected during Unload processing, it is important to determine the cause of the error
and to correct the problem. In most cases (a physical problem) the Reload facility should allow you to
accomplish this task by going back to the last good unload point.
For all corrective action, see the message description. For certain logical problems it may be
necessary to contact CA Endevor® SCM Customer Support.
Write an SCL DELETE statement to the C1SCL1 data set. The SCL contained in the C1SCL1 data
set can then be used in a subsequent recovery operation to delete the element before
performing Reload processing.
If the element itself is intact, but there is a problem in the associated ACM component list,
Unload will:
Write an SCL DELETE statement with the ONLY COMPONENT clause to the C1SCL1 data set.
The SCL contained in the C1SCL1 data set can then be used in a subsequent recovery
operation to delete only the element component list before a GENERATE action or Reload
processing.
Packages
No validation takes place during a package unload. The package data set is considered to be intact if
each package ID can be read successfully.
Unload Recommendations
Unload is designed to easily capture all related parts of the CA Endevor® SCM structure in a unified
manner. This allows for timely physical recovery in the event of a device failure or site disaster.
Performing a needs analysis for your site is the first step in making optimal use of this utility. The
criteria that you should consider include the following:
Number of environments/systems and related base and delta libraries at your site.
04-May-2018 991/1109
CA Endevor® SCM - 17.0
Use this information to determine how best to use and/or schedule Unload processing.
Unload processing does not begin until the lock can be set (after all activity against the system has
ceased). No CA Endevor® SCM activity can resume until the unload for that system has been
completed. The reload function still sets an enqueue exclusive at the environment level, thus it
cannot be run while an unload is being performed.
Locking Example 1
A site has only one environment, with all systems pointing to one set of base and delta libraries. A
low number of changes are made and there is little concern if a physical problem causes an outage
during recovery.
In this situation it may be simpler to back-up all files on a daily basis using the appropriate in-house
methods. In the event of a physical problem, CA Endevor® SCM can be completely restored using the
previous evening's backup files.
Locking Example 2
A site has many environments/systems, each with their own base/delta libraries. Any outage affects
many people in many areas of the company.
In this situation, full (FULL) and incremental (INC) unloads should be run. In most cases, a full unload
job should be scheduled on a weekly basis, and an incremental unload run each night. During a
physical failure, you must be able to recognize which unload files pertain to each system. Therefore
appropriate naming conventions for the unload files should be adopted.
Note: Align scheduling of Unload processing with in-house backup utilities to determine
what unload files need to be applied when a DASD volume is restored. In general, run
Unload processing immediately following each backup utility run. This action minimizes the
number of “orphan” members that occur during a reload.
In this example, CA Endevor® SCM unloads all systems within this environment to an output data set
with DDname UNLOD01. This data set must be coded in the Unload JCL.
04-May-2018 992/1109
CA Endevor® SCM - 17.0
CA Endevor® SCM unloads the entire package data set for this site to an output data set with ddname
UNLODPKG. This data set must be coded in the Unload JCL. The JCL which unloads the package can be
found in member BC1JUNLD, in the JCL library iprfx.iqual.CSIQJCL.
C1BM5000
The Unload/Reload/Validate Utility program.
CONLIB
Data set name of the installation CA Endevor® SCM CONLIB load library.
BSTIPT01
Required DDname for Unload/Reload/Validate statements.
UNLODNN
This is the DDname for the data set to which the Unload information is written. This parameter
must be allocated with a minimum LRECL=4200, a block size 4 bytes greater than 4200, and a
RECFM=VB.
Note: The LRECL should be at least 84 bytes larger than the largest LREC you are
unloading.
This data set should be set up as a Generation Data Group (GDG) with the proper number of
levels based on unload frequency.
Note: We recommend that you adopt a naming convention based on the type of Unload
being performed (FULL or INC) and the environment system to which it applies. For
example:
SPACE=(TRK, (NN,NN))
Required disk space for the unload data set (omit if tape). To estimate an approximate space
allocation for this data set, add the following items:
1105 bytes for each environment definition record on the Master File (1021-byte record
length plus 84-byte prefix; the system unloads one environment record for each system,
subsystem, type, type sequence, data set, and element master record).
The current space taken up by your base and delta libraries (these libraries continue to be
written in compressed format).
C1SCL1
Required DDname for the data set to which SCL DELETE statements are written.
04-May-2018 993/1109
CA Endevor® SCM - 17.0
Reload Function
This function lets you recover a CA Endevor® SCM VSAM control file (Master Control File or package
data set) or a base/delta data set that was lost as the result of a physical device failure or site
disaster. Reload restores data from data sets created by the Unload process. The TRANSFER action
may be used to transfer elements from an Unload file.
Note: For more information about the TRANSFER action, see SCL Reference (https://docops.
ca.com/display/CE17/SCL+Reference).
Reload processing occurs in two phases. Phase one reloads Master Control File environmental
definitions (system, subsystem, type, type sequence, data set, and so on) re-establish this
information. Phase two reloads elements (element master record, base/delta/component list).
The Reload function, when used in combination with the batch Restore (SCL) action it can also be a
powerful tool for recovering most logical and physical problems.
To make the best use of the Reload function, keep in mind the following:
Because no active journaling takes place, Reload processing cannot perform “point-of-failure”
recoveries. It is intended to be used with proper file/DASD layouts to reduce the impact, across all
systems, of a base/delta failure, and to ensure proper inventory synchronization if other outages
occur.
Reload processing replaces CA Endevor® SCM data set or library contents with unload file
contents when:
The date/time stamp of a record on the unload file is more recent than the one currently in
CA Endevor® SCM.
An element currently in CA Endevor® SCM does not meet the Validation criteria (the record in
CA Endevor® SCM has a more recent date/time stamp but the Validation process finds a
missing base member).
This utility is not designed to be used to simply back off or back out a member in a data set.
Reload can accept a concatenated input stream of unload files. Because of the date/time
checking that occurs, only the latest data is reloaded. However, it is highly recommended that
files be ordered from the oldest to the newest. This ensures that the logical cleanup of elements
occurs. Failure to do this may result in elements ending up at both stages, out of logical order.
The CA Endevor® SCM RESTORE action can use an unload file as input. This action can be used to
perform logical recovery by first deleting the element, then restoring from the unload file.
The Unload/Reload reports (CONRPT50-55) should be used to determine the status of an unload
file. Use the reporting facility whenever you need to itemize the activity contained on one of
these files.
04-May-2018 994/1109
CA Endevor® SCM - 17.0
The parameters for using Reload for a package data set or one or more specific IDs are as follows:
►►── RELoad ─ PACkage ─┬─────────────────────┬─ FROm ─ DDName ddname ──. ──────►◄
└─ ID ─ package-name ─┘
The parameters for the Reload control card are described next:
RELOAD
Specifies the Reload function of program C1BM5000.
FROM DDNAME
Identifies the DDname to which the input Reload data set name is assigned. Environment and
package processing require a DDname.
TO
Allows you to specify the to location for a combination of environments and systems to be
reloaded. The qualifying statements are:
SYSTEM-Identifies the systems into which information is to be reloaded. A name mask may be
used.
PACKAGE
Required when reloading a package data set or one or more packages. You may also select a
package ID to identify the name of a specific package to be reloaded. You can use a name mask. If
you do not specify a package ID, all packages found in the unload data set is reloaded to the
package data set defined in the C1DEFLTS table.
For promotion packages, you cannot specify the package ID of individual historic versions. You
can specify the fully qualified name or mask package ID of the current version. This reloads each
promotion package version that is missing or that needs to be reloaded due to date validation
inconsistencies.
04-May-2018 995/1109
CA Endevor® SCM - 17.0
If the VSAM Master Control File for the environment being reloaded is empty (new file allocated),
Reload processing rebuilds the file using the contents of the unload data set(s).
If the Master Control File contains the environmental record, Reload processing does the following:
If the system information about the unload file is more recent than the existing system
information, the existing information is replaced.
If the subsystem information about the unload file is more recent than the existing subsystem
information, the existing information is replaced.
If the type information about the unload file is more recent than the existing type information,
the existing information is replaced. This is done as follows:
Type sequence types added from the unload file are sequenced after the existing
If the approver group/relation information about the unload file is more recent than the existing
approver group/relation information, the existing information is replaced.
No existing data set information is replaced. Rather, Reload adds any data set information that is
not found in the current Master Control File.
If the element or component list in the unload file is more recent than the existing MCF element
or component list, Reload processing will:
Replace the existing element master record with the contents of the unload file.
Replace the existing base and delta members for the element and/or component list with the
contents of the unload file.
Write an SCL GENERATE action request for that element to the C1SCL1 data set.
If the element or component list in the unload file is not more recent than the existing MCF
element or component list, Reload performs validation processing on the element/component
list. .
Replace the existing element master record with the contents of the unload file.
Replace the existing base and delta members for the element and/or component list with the
contents of the unload file.
Write an SCL GENERATE action request for that element to the C1SCL1 data set.
04-May-2018 996/1109
CA Endevor® SCM - 17.0
If a Stage 2 element is reloaded and the element exists at Stage 1, reload processing will delete
the Stage 1 element if the last action date for the Stage 2 element is more recent than the last
action date for the Stage 1 element.
If the date/time stamp of the package from the unload file is the more recent than the one
contained in the package data set, Reload replaces the existing package.
If the date/time stamp of the existing package is more recent than the one contained in the
unload file, Reload will not replace the package.
For promotion packages, the reload utility loads each of the versions that are missing or that need to
be reloaded due to date validation inconsistencies.
For example, assume the unload utility was executed against the package file and the package ID of
the current version is PKG1 and there are two historic versions: EXAOBHX1 and EXAJHBX2. Assume
that the package records for EXAOBHX1 were deleted and the PKG1 and EXAJHBX2 package records
remain intact. When you issue the reload for PKG1, the reload utility determines that only package
EXAOBHX1 must be reloaded and reloads it.
Solution: Restore the DASD volume from the latest in-house backup file. After this step has been
done, determine to what point the volume was restored (date/time) in relation to the unload files
that you have available.
If no changes have been made to CA Endevor® SCM data since the last backup, the files should be
considered recovered (in sync), and CA Endevor® SCM processing may be continued.
04-May-2018 997/1109
CA Endevor® SCM - 17.0
If only environmental changes have been made to CA Endevor® SCM since the last backup (no
element updates were made), the files should be considered recovered (in sync), and CA
Endevor® SCM processing may be continued.
If element modifications have been made since the last backup, an out-of-sync condition exists
between the base and/or delta libraries and the Master Control File (MCF), requiring the systems
to be reloaded. To do so:
Set up a Reload job using as input the last full unload file, and all incremental files that are
available up to the point of the failure.
Run Reload processing for all the affected systems using the concatenated input of unload
files.
Use the SCL file (C1SCL1) produced during Reload to run the GENERATE action against the
reloaded elements. This will synchronize the outputs.
Once the reload has been completed, Validate processing must be run for each system that was
reloaded. This is necessary to identify “orphan” members (members that had been added since the
recovery point). To do this:
Use the SCL file (C1SCL1) produced by the Validate process to delete each element that failed
validation and complete the synchronization process.
Note: The deleted elements can be manually recovered from a source output library member or
an external copy of the source. If a source output library exists, ensure that the members to be
recovered are first saved from this library before delete processing is performed. All other
changes that have been made since that time has been effectively “rolled back.”
Solution: Restore the DASD volume from the latest in-house backup file. After this step has been
done, determine to what point the volume was restored (date/time) in relation to the unload files
that you have available.
If no changes have been made to CA Endevor® SCM since the last backup, the files should be
considered recovered (in sync), and CA Endevor® SCM processing may be continued.
If only environmental changes have been made to CA Endevor® SCM since this last backup (no
element updates were made) the files should be considered recovered (in sync). Any
environmental changes made since the recovery point has been lost and must be manually
recovered. Once this has been done CA Endevor® SCM processing may be continued.
04-May-2018 998/1109
CA Endevor® SCM - 17.0
If element modifications have been made since the last backup, an out-of-sync condition exists
between the Master Control File (MCF) and the base and/or delta library, requiring the systems to
be reloaded. To do this:
Set up a Reload job using as input the last full unload file, and all incremental files that are
available up to the point of the failure.
Run Reload processing for all the affected system(s) using the concatenated input of unload
files.
Use the SCL file (C1SCL1) produced during Reload to run the Generate action against the
reloaded elements. This will synchronize the associated outputs.
Note: Elements added since the recovery point can be manually recovered from the
contents of a source output library member or an external copy of the source. All other
changes that have been made since that time will have been effectively “rolled back.”
Note: If the reloaded SYSTEM requires CCID and/or COMMENT to be specified for actions
against its elements, you must insert a SET OPTIONS statement in the generated SCL file
(C1SCL1).
Solution: Restore the DASD volume from the latest in-house backup files. After this step has been
done, determine to what point the volume was restored (date and time) in relation to any package
unload files you may have available.
If no changes have been made to the package data set since the last backup, the data set should
be considered recovered (in sync), and CA Endevor® SCM processing may be continued.
If any package modifications have been made since the last backup, they are lost. If there is an
unload file available that is more recent than the backup from which the data set was restored
you can reload the package data set. To do so:
Set up a Reload job, using as input any unload file that is more recent than the backup file
used to restore the data set.
Run Reload processing for all the affected packages or selected package IDs.
04-May-2018 999/1109
CA Endevor® SCM - 17.0
UNLODPKG is the DDname assigned to the input data set that contains the data to be reloaded. This
data set must be coded in the Reload JCL. The JCL which unloads the package can be found in
member BC1JRELD, supplied in your iprfx.iqual.CSIQJCL library.
C1BM5000
The Unload/Reload/Validate Utility program.
CONLIB
Data set name of the installation CA Endevor® SCM CONLIB load library.
BSTIPT01
Required DDname for Unload/Reload/Validate statements.
UNLODNN
The target DDname of the unload data set name specified for this Reload operation.
C1SCL1
Required DDname for the data set to which the SCL GENERATE statements produced by the
Reload operation will be written.
C1RLDWK*
Pre-allocates work files so that site does not have to rely on CA Endevor® SCM for temporary
allocation.
Validate Function
This function lets you ensure the integrity of one or more existing CA Endevor® SCM environments
and/or systems and their related elements and components.
The Validate function performs a series of checks against the contents of the VSAM Master Control
File(s), and the related base and delta libraries associated with the environments and systems
specified on the job request. These are the same checks performed as part of Unload processing,
allowing this function to operate in a standalone mode.
Validate may be run for an entire environment, or for selected systems within an environment. There
is no validation processing currently available for the package data set.
The Validate function should be run any time there is a question about the integrity of an
environment/system, and with a reload operation. An unload does not do the same checking against
the files as a validate.
04-May-2018 1000/1109
CA Endevor® SCM - 17.0
The parameters for the Validate control card are described next:
VALIDATE
Specifies the Validate function of program C1BM5000. You must further qualify the Validate
request with one of the following:
SYSTEM-Identifies the systems from which information is to be validated. A name mask may
be used.
Validate Processing
Validate processing performs a series of checks against the contents of the VSAM Master Control
Files, and the related base and delta libraries. These checks include:
Footprint correlation.
Insert/delete counts.
If an error is detected it is important to determine the cause and to correct the problem. In most
cases (a physical problem) the Reload facility should allow you to accomplish this task by going back
to the last good unload point.
Validate checks Master Control File and element information in the following order:
3. Stage 1 elements.
4. Stage 2 elements.
04-May-2018 1001/1109
CA Endevor® SCM - 17.0
If the validation problem affects the element itself, Validate will write:
An SCL DELETE statement to the C1SCL1 data set. The SCL contained in the C1SCL1 data set
can then be used in a subsequent recovery operation to delete the element prior to
performing Reload processing.
If the element itself is intact, but there is a problem in the associated ACM component list,
Validate will write:
An SCL DELETE statement with the ONLY COMPONENT clause to the C1SCL1 data set.
The SCL contained in the C1SCL1 data set can then be used in a subsequent recovery operation to
delete only the element's component list prior to a GENERATE action or Reload processing.
The JCL which validates the package can be found in member BC1JVALD, supplied in your iprfx.iqual.
CSIQJCL library.
C1BM5000
The Unload/Reload/Validate Utility program.
CONLIB
Data set name of the installation CA Endevor® SCM CONLIB load library.
BSTIPT01
Required DDname for Unload/Reload/Validate statements.
C1SCL1
Required DDname for the data set to which the SCL DELETE statements produced during Validate
processing is written.
04-May-2018 1002/1109
CA Endevor® SCM - 17.0
If you updated a processor and removed some symbolics from its PROC statement, the corresponding
symbolic overrides that are defined for that processor would remain in the Master Control File. These
are considered to be unused symbolic overrides, because the corresponding symbolic is removed
from the processor for which the override existed.
If you later modify the processor to include the same symbolic, then the override becomes active
again without the user awareness. This can cause unexpected behavior of the changed processor.
Also, the API and the CSV utility report unused symbolic overrides, without identifying them as
unused. To avoid these situations, use the BC1PSDEL utility to identify and remove any unused
symbolic overrides. The utility cannot prevent symbolics from becoming unused; it can identify and
remove them for you.
The BC1PSDEL utility scans all Master Control Files searching for unused symbolic overrides. It does
not directly remove them, but does produce output with "DELETE PROCESSOR SYMBOL" SCL
statements, which can be reviewed and passed to the Batch Environment Administration facility
(ENBE1000) to be processed.
The utility identifies and classifies unused processor symbolic overrides as follows:
Regular unused symbolic overrides, which originate from a source change of the corresponding
processor.
Irregular unused symbolic overrides, which are identified if the corresponding processor load
module or load library does not exist or cannot be accessed. In this case, the utility treats all
respective symbolic overrides as unused, because it cannot be determined if the corresponding
symbolics exist in the processor load module.
04-May-2018 1003/1109
1.
c. MODE =1
If the utility has been run before, this mode deletes previously created SCL data
sets, before building new SCL data sets.
Executes the BC1PSDEL utility to build SCL data sets, but does not process them.
d. MODE=2
If the utility has been run before, this mode deletes previously created SCL data
sets, before building new SCL data sets.
e. MODE=3
f. Make sure that the DD statements refer to the correct SCL1 and SCL2 data sets.
MODE 1 or MODE 2
If the job runs in MODE 1 or 2, the BC1PSDEL utility scans all Master Control Files for unused
processor symbolic overrides and generates the following output.
Note: MODE 2 also executes the SCL statements, for details see section "MODE 2 or
MODE 3".
If the job runs in MODE 2 or 3, the Batch Environment Administration facility (ENBE1000)
processes the "DELETE PROCESSOR SYMBOL" SCL statements generated by the BC1PSDEL
utility and deletes the unused processor symbolic overrides from Master Control Files. By
default, only SCL1 statements are executed. However, if you uncommented the SCL2 data set
in the ENESCLIN DD statement, the SCL2 statements are executed also.
If any regular unused symbolic overrides are deleted, the Batch Environment Administration
facility (ENBE1000) finishes with RC=4 and the action log contains ENBE144W messages
(ENBE144W Processor Symbol X has not been overridden or is not defined for Generate
04-May-2018 1004/1109
CA Endevor® SCM - 17.0
(ENBE144W Processor Symbol X has not been overridden or is not defined for Generate
/Delete/Move processor ). This outcome is correct because the Batch Environment
Administration facility cannot see regular unused symbolic overrides; however, it does
remove them.
04-May-2018 1005/1109
CA Endevor® SCM - 17.0
Catalog Utilities
Contents
CA Endevor SCM uses an Element Catalog file to support long element names and to boost
performance by reducing the volume of I/O operations.
With the implementation of the Element Catalog, all MCF's have the catalog name recorded in its
stage record. The first time CA Endevor SCM is invoked after migration from a prior release, the
MCF's, at open time, are updated with the Element Catalog name. From that point on, (at open time)
CA Endevor SCM checks the stage record's catalog name against the name specified in the C1DEFLTS
table. If the names are not equal, the MCF open fails. This check prevents MCF's from belonging to
more than one catalog.
The CA Endevor SCM MCF Catalog Rename Utility allows you to change the catalog name in the
MCF's stage record. This utility should be run after you have created a new Catalog and have defined
it to the C1DEFLTS table.
Validate Mode-All environments defined in the C1DEFLTS table are examined. A report is
produced showing the current MCF catalog name and a statement as to whether or not the name
agrees or disagrees with the C1DEFLTS table. A return code of 0 indicates all environments match
the table's definition. A return code of 4 indicates that some or all environments are not current
with the table's definition.
Update Mode-All environments defined in the C1DEFLTS table are examined, but instead of just
reporting the mismatches, the utility rewrites the stage records with the name defined from the
C1DEFLTS table. A return code of 0, under Update mode, indicates that all environments match
the table's definition. A return code of 4 indicates that some or all of the stages were updated
with the table's name.
To execute the rename utility, use member BC1JXCNM from your JCL library. To invoke validate or
update mode, change the PARM= parameter on the execute statement.
04-May-2018 1006/1109
CA Endevor® SCM - 17.0
This utility has two modes, a validate mode and an update mode. The validate mode simply reports
on the differences between the catalog and MCF files. The update mode actually recovers the
differences between the element catalog and its related MCFs by updating the element catalog file.
Under the update mode, the utility synchronizes the element catalog and the MCF element records in
two phases.
The first phase validates MCF records against the catalog. A catalog segment is created for any MCF
record found missing from the catalog. A catalog segment is updated with MCF element data when
the associated catalog data is found to be different.
The second phase validates the catalog to MCF to remove dead segments from the catalog. All
segments which do not have a MCF element record are removed from the catalog.
Under validate mode, the utility performs the same two-phase check but does not modify the
catalog. Any differences are simply reported in the execution log.
To select the mode, use the PARM= parameter on the JCL execution statement. 4.
In both phases, processing is done by environment. You can specify which environments the utility
will process, or allow the environment selection to default to all environments defined in the
C1DEFLTS table.
Important! Do not use this utility to initially load the catalog file. Use job BC1JXCNV to load
the catalog file. For more information, see Run the Catalog Build Utility (see page ).
04-May-2018 1007/1109
CA Endevor® SCM - 17.0
1 (C) 2005 Computer Associates International, Inc. 10NOV04 14:33:53 PAGE 1
Endevor MCF Catalog Synchronization UTILITY LOG RELEASE 7.0 SERIAL B7000C
SYN0000I BEGINNING PHASE 1
SYN0002I ENVIRONMENT ENV1 MCF ELEMENT TO CATALOG SYNCRONIZATION STARTING
*MISSING* CTLG SGMT: ELEMENT EJZZBLONGNAME02
TYPE JDOHFS AT ENV ENV1 SID 1 SYS SYST100 SBS SBS100
*MISSING* CTLG SGMT: ELEMENT JBEANlongld5VERYLONGNAMEverylongnameVERYLONGNAMEverylongnameLAROSE
TYPE JDOHFS AT ENV ENV1 SID 1 SYS SYST100 SBS SBS100
*MISSING* CTLG SGMT: ELEMENT EJudylarose01
TYPE JDOHFS AT ENV ENV1 SID 1 SYS SYST100 SBS SBS100
*OLD * CTLG SGMT: ELEMENT EJudylarose02
TYPE JDOHFS AT ENV ENV1 SID 1 SYS SYST100 SBS SBS100
*OLD * CTLG SGMT: ELEMENT IA6PGM
TYPE ASMPGM AT ENV ENV1 SID 1 SYS SYST100 SBS SBS100
*OLD * CTLG SGMT: ELEMENT OLENIC01
TYPE JDOHFS AT ENV ENV1 SID 2 SYS SYST100 SBS SBS100
SYN0003I TOTAL # OF MISSING CTLG SGMTS FROM ENVIRON ENV1 : 3
SYN0004I TOTAL # OF OLD CTLG SGMTS FOUND IN ENVIRON ENV1 : 3
SYN0005I TOTAL # OF ELEMENTS PROCESSED FROM ENVIRON ENV1 : 102
SYN0002I ENVIRONMENT ENVA MCF ELEMENT TO CATALOG SYNCRONIZATION STARTING
*MISSING* CTLG SGMT: ELEMENT TESTJO1
TYPE JCLI AT ENV ENVA SID 2 SYS SYSTA00 SBS SBSA00
*MISSING* CTLG SGMT: ELEMENT SANELM1
TYPE JCLI AT ENV ENVA SID 2 SYS SYSTC00 SBS SBSC00
SYN0003I TOTAL # OF MISSING CTLG SGMTS FROM ENVIRON ENVA : 2
SYN0004I TOTAL # OF OLD CTLG SGMTS FOUND IN ENVIRON ENVA : 0
SYN0005I TOTAL # OF ELEMENTS PROCESSED FROM ENVIRON ENVA : 5
SYN0002I ENVIRONMENT ENVZ MCF ELEMENT TO CATALOG SYNCRONIZATION STARTING
SYN0003I TOTAL # OF MISSING CTLG SGMTS FROM ENVIRON ENVZ : 0
SYN0004I TOTAL # OF OLD CTLG SGMTS FOUND IN ENVIRON ENVZ : 0
SYN0005I TOTAL # OF ELEMENTS PROCESSED FROM ENVIRON ENVZ : 1
SYN0011I TOTAL # OF ELEMENTS PROCESSED, ALL ENVIRONMENTS: 108
SYN0000I BEGINNING PHASE 2
SYN0031I ENVIRONMENT ENV1 CATALOG TO MCF ELEMENT SYNCRONIZATION STARTING.
04-May-2018 1008/1109
CA Endevor® SCM - 17.0
*ORPHAN * CTLG SGMT: ELEMENT EJudylarose01
TYPE JDOHFS AT ENV ENV1 SID 2 SYS SYST100 SBS SBS100
*ORPHAN* CTLG SGMT: ELEMENT EJZZBLONGNAME02
1 (C) 2005 Computer Associates International, Inc. 10NOV04 14:34:03 PAGE 2
Endevor MCF Catalog Synchronization UTILITY LOG RELEASE 7.0 SERIAL B7000C
TYPE JDOHFS AT ENV ENV1 SID 2 SYS SYST100 SBS SBS100
*ORPHAN * CTLG SGMT: ELEMENT JBEANlongld5VERYLONGNAMEverylongnameVERYLONGNAMEverylongnameLAROSE
TYPE JDOHFS AT ENV ENV1 SID 2 SYS SYST100 SBS SBS100
SYN0032I TOTAL # OF ORPHAN CTLG SGMTS IN ENVIRON ENV1 : 3
SYN0033I TOTAL CATALOG SEGMENTS PROCESSED FOR ENVIRON ENV1 : 105
SYN0031I ENVIRONMENT ENVA CATALOG TO MCF ELEMENT SYNCRONIZATION STARTING.
*ORPHAN * CTLG SGMT: ELEMENT SANELM1
TYPE JCLI AT ENV ENVA SID 1 SYS SYSTC00 SBS SBSC00
*ORPHAN * CTLG SGMT: ELEMENT TESTJO1
TYPE JCLI AT ENV ENVA SID 1 SYS SYSTA00 SBS SBSA00
SYN0032I TOTAL # OF ORPHAN CTLG SGMTS IN ENVIRON ENVA : 2
SYN0033I TOTAL CATALOG SEGMENTS PROCESSED FOR ENVIRON ENVA : 7
SYN0031I ENVIRONMENT ENVZ CATALOG TO MCF ELEMENT SYNCRONIZATION STARTING.
SYN0032I TOTAL # OF ORPHAN CTLG SGMTS IN ENVIRON ENVZ : 0
SYN0033I TOTAL CATALOG SEGMENTS PROCESSED FOR ENVIRON ENVZ : 1
SYN0034I TOTAL CATALOG SEGMENTS PROCESSED, ALL ENVIRONMENTS: 113
If the utility is executed again, but this time in update mode, the catalog is repaired and the following
log report is produced.
1 (C) 2005 Computer Associates International, Inc. 10NOV04 14:33:53 PAGE 1
Endevor MCF Catalog Synchronization UTILITY LOG RELEASE 7.0 SERIAL B7000C
SYN0000I BEGINNING PHASE 1
SYN0002I ENVIRONMENT ENV1 MCF ELEMENT TO CATALOG SYNCRONIZATION STARTING
*CREATED* CTLG SGMT: ELEMENT EJZZBLONGNAME02
TYPE JDOHFS AT ENV ENV1 SID 1 SYS SYST100 SBS SBS100
*CREATED* CTLG SGMT: ELEMENT JBEANlongld5VERYLONGNAMEverylongnameVERYLONGNAMEverylongnameLAROSE
TYPE JDOHFS AT ENV ENV1 SID 1 SYS SYST100 SBS SBS100
*CREATED* CTLG SGMT: ELEMENT EJudylarose01
TYPE JDOHFS AT ENV ENV1 SID 1 SYS SYST100 SBS SBS100
*UPDATED* CTLG SGMT: ELEMENT EJudylarose02
TYPE JDOHFS AT ENV ENV1 SID 1 SYS SYST100 SBS SBS100
*UPDATED* CTLG SGMT: ELEMENT IA6PGM
TYPE ASMPGM AT ENV ENV1 SID 1 SYS SYST100 SBS SBS100
*UPDATED* CTLG SGMT: ELEMENT OLENIC01
TYPE JDOHFS AT ENV ENV1 SID 2 SYS SYST100 SBS SBS100
SYN0003I TOTAL CATALOG SEGMENTS CREATED FOR ENVIRON ENV1 : 3
SYN0004I TOTAL CATALOG SEGMENTS UPDATED FOR ENVIRON ENV1 : 3
SYN0005I TOTAL # OF ELEMENTS PROCESSED FOR ENVIRON ENV1 : 102
SYN0002I ENVIRONMENT ENVA MCF ELEMENT TO CATALOG SYNCRONIZATION STARTING
*CREATED* CTLG SGMT: ELEMENT TESTJO1
TYPE JCLI AT ENV ENVA SID 2 SYS SYSTA00 SBS SBSA00
*CREATED* CTLG SGMT: ELEMENT SANELM1
TYPE JCLI AT ENV ENVA SID 2 SYS SYSTC00 SBS SBSC00
SYN0003I TOTAL CATALOG SEGMENTS CREATED FOR ENVIRON ENVA : 2
SYN0004I TOTAL CATALOG SEGMENTS UPDATED FOR ENVIRON ENVA : 0
SYN0005I TOTAL # OF ELEMENTS PROCESSED FOR ENVIRON ENVA : 5
SYN0002I ENVIRONMENT ENVZ MCF ELEMENT TO CATALOG SYNCRONIZATION STARTING
04-May-2018 1009/1109
CA Endevor® SCM - 17.0
SYN0003I TOTAL CATALOG SEGMENTS CREATED FOR ENVIRON ENVZ : 0
SYN0004I TOTAL CATALOG SEGMENTS UPDATED FOR ENVIRON ENVZ : 0
SYN0005I TOTAL # OF ELEMENTS PROCESSED FOR ENVIRON ENVZ : 1
SYN0011I TOTAL # OF ELEMENTS PROCESSED, ALL ENVIRONMENTS: 108
SYN0000I BEGINNING PHASE 2
SYN0031I ENVIRONMENT ENV1 CATALOG TO MCF ELEMENT SYNCRONIZATION STARTING.
*DELETED* CTLG SGMT: ELEMENT EJudylarose01
TYPE JDOHFS AT ENV ENV1 SID 2 SYS SYST100 SBS SBS100
*DELETED* CTLG SGMT: ELEMENT EJZZBLONGNAME02
1 (C) 2005 Computer Associates International, Inc. 10NOV04 14:34:03 PAGE 2
Endevor MCF Catalog Synchronization UTILITY LOG RELEASE 7.0 SERIAL B7000C
TYPE JDOHFS AT ENV ENV1 SID 2 SYS SYST100 SBS SBS100
*DELETED* CTLG SGMT: ELEMENT JBEANlongld5VERYLONGNAMEverylongnameVERYLONGNAMEverylongnameLAROSE
TYPE JDOHFS AT ENV ENV1 SID 2 SYS SYST100 SBS SBS100
SYN0032I TOTAL CATALOG SEGMENTS DELETED FOR ENVIRON ENV1 : 3
SYN0033I TOTAL CATALOG SEGMENTS PROCESSED FOR ENVIRON ENV1 : 105
SYN0031I ENVIRONMENT ENVA CATALOG TO MCF ELEMENT SYNCRONIZATION STARTING.
*DELETED* CTLG SGMT: ELEMENT SANELM1
TYPE JCLI AT ENV ENVA SID 1 SYS SYSTC00 SBS SBSC00
*DELETED* CTLG SGMT: ELEMENT TESTJO1
TYPE JCLI AT ENV ENVA SID 1 SYS SYSTA00 SBS SBSA00
SYN0032I TOTAL CATALOG SEGMENTS DELETED FOR ENVIRON ENVA : 2
SYN0033I TOTAL CATALOG SEGMENTS PROCESSED FOR ENVIRON ENVA : 7
SYN0031I ENVIRONMENT ENVZ CATALOG TO MCF ELEMENT SYNCRONIZATION STARTING.
SYN0032I TOTAL CATALOG SEGMENTS DELETED FOR ENVIRON ENVZ : 0
SYN0033I TOTAL CATALOG SEGMENTS PROCESSED FOR ENVIRON ENVZ : 1
SYN0034I TOTAL CATALOG SEGMENTS PROCESSED, ALL ENVIRONMENTS: 113
If the utility is executed again in update mode, no discrepancies should be found, as indicated in the
following sample report.
1 (C) 2005 Computer Associates International, Inc. 10NOV04 14:36:29 PAGE 1
Endevor MCF Catalog Synchronization UTILITY LOG RELEASE 7.0 SERIAL B7000C
SYN0000I BEGINNING PHASE 1
SYN0002I ENVIRONMENT ENV1 MCF ELEMENT TO CATALOG SYNCRONIZATION STARTING
SYN0003I TOTAL CATALOG SEGMENTS CREATED FOR ENVIRON ENV1 : 0
SYN0004I TOTAL CATALOG SEGMENTS UPDATED FOR ENVIRON ENV1 : 0
SYN0005I TOTAL # OF ELEMENTS PROCESSED FOR ENVIRON ENV1 : 102
SYN0002I ENVIRONMENT ENVA MCF ELEMENT TO CATALOG SYNCRONIZATION STARTING
SYN0003I TOTAL CATALOG SEGMENTS CREATED FOR ENVIRON ENVA : 0
SYN0004I TOTAL CATALOG SEGMENTS UPDATED FOR ENVIRON ENVA : 0
SYN0005I TOTAL # OF ELEMENTS PROCESSED FOR ENVIRON ENVA : 5
SYN0002I ENVIRONMENT ENVZ MCF ELEMENT TO CATALOG SYNCRONIZATION STARTING
SYN0003I TOTAL CATALOG SEGMENTS CREATED FOR ENVIRON ENVZ : 0
04-May-2018 1010/1109
CA Endevor® SCM - 17.0
SYN0004I TOTAL CATALOG SEGMENTS UPDATED FOR ENVIRON ENVZ : 0
SYN0005I TOTAL # OF ELEMENTS PROCESSED FOR ENVIRON ENVZ : 1
SYN0011I TOTAL # OF ELEMENTS PROCESSED, ALL ENVIRONMENTS: 108
SYN0000I BEGINNING PHASE 2
SYN0031I ENVIRONMENT ENV1 CATALOG TO MCF ELEMENT SYNCRONIZATION STARTING.
SYN0032I TOTAL CATALOG SEGMENTS DELETED FOR ENVIRON ENV1 : 0
SYN0033I TOTAL CATALOG SEGMENTS PROCESSED FOR ENVIRON ENV1 : 102
SYN0031I ENVIRONMENT ENVA CATALOG TO MCF ELEMENT SYNCRONIZATION STARTING.
SYN0032I TOTAL CATALOG SEGMENTS DELETED FOR ENVIRON ENVA : 0
SYN0033I TOTAL CATALOG SEGMENTS PROCESSED FOR ENVIRON ENVA : 5
SYN0031I ENVIRONMENT ENVZ CATALOG TO MCF ELEMENT SYNCRONIZATION STARTING.
SYN0032I TOTAL CATALOG SEGMENTS DELETED FOR ENVIRON ENVZ : 0
SYN0033I TOTAL CATALOG SEGMENTS PROCESSED FOR ENVIRON ENVZ : 1
SYN0034I TOTAL CATALOG SEGMENTS PROCESSED, ALL ENVIRONMENTS: 108
04-May-2018 1011/1109
CA Endevor® SCM - 17.0
Change Control Identifiers (CCIDs) provide CA Endevor SCM users with an important project
management tool. CCIDs can function as logical grouping mechanisms by which user-specified
portions of the CA Endevor SCM inventory can be tagged, then viewed, tracked, and manipulated.
In addition to the CCID, you can also specify a comment for CA Endevor SCM actions. Consider using
the comment and the CCID to provide additional information. For instance, the person who performs
an action might use the COMMENT field to note the purpose of the action.
Users can specify CCIDs and/or comments when they request actions. You can decide whether to
require CCIDs and/or comments for all action requests on a system-by-system basis.
You can specify a CCID and/or comment when you request any of these CA Endevor SCM actions:
ADD, UPDATE, RETRIEVE, GENERATE, MOVE, TRANSFER, DELETE, and RESTORE. CA Endevor SCM
updates the CCID and/or comment in up to six places with the CCID and/or comment specified in the
action request. Whether a CCID and/or comment is updated depends on the effect the action has on
the source and outputs managed by CA Endevor SCM.
The following list details CCID and/or COMMENT fields that may be updated:
04-May-2018 1012/1109
CA Endevor® SCM - 17.0
2. Type U in the COMMAND field, enter the environment name in the ENVIRONMENT field, and
press Enter.
The System Definition panel appears.
3. Enter Y in the CCID and/or COMMENT fields, and press Enter to save your changes.
Note: If you do not specify a CCID and/or comment when one is required for the
action you are requesting, CA Endevor SCM displays the Action Prompt panel. To
complete your action request, type a valid CCID and/or comment and press Enter.
Predefine CCIDs
Predefining CCIDs lets you perform the following:
Use a product such as IBM Tivoli Information Management for z/OS; CA Endevor SCM provides an
interface for this product.
Create your own file; CA Endevor SCM provides a user exit capability so you can define your own
CCID definition file.
This section contains information about CCID validation in CA Endevor SCM and about the CCID
definition data set that you can define within CA Endevor SCM.
04-May-2018 1013/1109
CA Endevor® SCM - 17.0
CCID Validation
If you have predefined CCIDs, the CCID definition file is read into memory at CA Endevor SCM startup.
Changes to the definition file during a CA Endevor SCM work session do not take effect until you exit
CA Endevor SCM and then re-enter the system.
CCID validation processing takes effect at the time an action is performed. That is, a batch action
could be built (using the batch or package construction screens), but denied at execution time.
If the system you are working with is defined with CCID required, then a valid CCID must be specified
for all actions requiring a CCID. If the system you are working with is not defined with CCID required,
the CCID is not validated and any value including no CCID (spaces) for the action is allowed.
CCID validation applies only to specific actions. This processing is not applicable with the LIST or
PRINT actions, because you cannot specify a CCID for these actions. Additionally, CCID validation is
not performed for the MERGE action.
Note: CCID validation performed by CA Endevor SCM can be used as a secondary validation
mechanism that is invoked if a no match condition is found in the CA Endevor SCM
InfoMan Interface.
When a CCID is specified in a CA Endevor SCM action, CA Endevor SCM validates that CCID against the
contents of this data set. It determines whether the user is authorized to use the specified CCID with
the inventory area against which the action is being performed.
You must maintain the definition file using the ISPF (or any other) text editor or by creating the file
from your existing project management system. The definition file must be a card-image data set (80-
byte, fixed-format records).
The format of the records in the CCID definition file is variable; the records may be comments
("comment lines") or definitions ("definition lines"). CCIDs are required on every definition line;
optionally, a TSO user and/or CA Endevor SCM element identification information (environment,
system, subsystem, element name, type, and stage) can be given.
1. Allocate that CCID validation data set. Use the standard ISPF data set utilities, option 3.2 from
the ISPF/PDF Primary Options menu. Allocation the data set with the following attributes:
LRECL=80, RECFM=FB, DSORG=PS, and BLKSIZE=any multiple of 80. The data set name must
be the same as that specified for the CIPODSN parameter in the Defaults table. The data set
name can be any valid name that conforms to your site naming conventions.
04-May-2018 1014/1109
1.
Note: When you create the sequential file, be sure to specify a data set name in the
format: project.dataset.type, where type is a unique value. This causes the ISPF
editor to use a unique profile for the data set.
2. Initialize the data set by copying member SAMPCIPO from the iprfx.iqual.CSIQJCL library into
the allocated data set. SAMPCIPO is a sample CCID definition data set that is distributed with
the CA Endevor SCM system. You can use SAMPCIPO to build a data set appropriate to the
needs of your organization. Because CA Endevor SCM requires information to be placed in
certain columns, we recommend that you copy member SAMPCIPO into the data set. By using
this member as a template, you can ensure that the fields in the data set are positioned in the
correct columns. Use the standard ISPF copy utility-option 3.3 on the ISPF/PDF Primary Option
Menu-to copy SAMPCIPO from the sample JCL library (iprfx.iqual.CSIQJCL) into the data set.
Use the ISPF edit service to tailor the data set to meet the requirements of your site.
3. Add the Data Set Name to the Defaults table, by adding the data set name to the CIPODSN
parameter. Do not update the CIPODSN parameter in the Defaults Table before allocating the
CCID validation data set. If CIPODSN contains a non-null entry, CA Endevor SCM assumes that
the entry is a data set name and looks for that data set during initialization. If CA Endevor SCM
cannot find the data set, it generates an error message. Therefore, before using CA Endevor
SCM, ensure that the CCID validation data set is allocated and defined appropriately.
Note: For more information about editing the table, see The Defaults Table.
A sequential data set allows you to use the standard ISPF text editor for editing.
A sequential data set allows you to off-load project management information from an existing
application (such as IBM Tivoli Information Management for z/OS) and construct the data set
using an application program.
Note: To assist in the building of the application program, an assembler macro has been
supplied with the system. The macro resides in the installation source library (iprfx.iqual.
CSIQOPTN) built during Step 1 of the CA Endevor SCM installation process. The member
name of the macro is $CIPOREC.
To write a program to create a CCID definition data set, use the record layout that is specified in
$CIPOREC, using your own data.
04-May-2018 1015/1109
CA Endevor® SCM - 17.0
To register the names of CCIDs. The CCID definition data set can also contain user and/or element
identification data.
As a secondary or backup CCID validation mechanism, with the CA Endevor SCM InfoMan
interface.
If a CCID gets a "no match" condition from the CA Endevor SCM InfoMan interface, CA Endevor
SCM uses the CCID definition data set to check further. If the interface recognizes the CCID, then
CA Endevor SCM bypasses the CCID check.
Using the CCID definition feature with this additional information can assist you in project
management. You can create multiple lines in the CCID definition data set for each valid CCID. For a
CCID value, these successive lines specify the users allowed to work under this CCID, the inventory
items/areas which may be worked on, or both.
For example, assume that a site has two projects: TAX-CHNG-89 and NEW-COMPPLAN. Only people in
the Development Department (TSO user IDs: DEVxxx) are allowed to perform changes as part of
these projects. The inventory areas for the changes are as follows:
Environment = DEMO
Stage number = 1
04-May-2018 1016/1109
CA Endevor® SCM - 17.0
Any line that begins with an asterisk (*) in column 1 is considered a comment line.
Every non-comment line is considered a definition line, and must specify a CCID. The CCID field is
always required.
All other fields on a definition line are optional. If any field is left blank (such as the SUBSYSTEM
field for the first five lines listed in the previous sample), it is ignored.
Name masks (for example, ZSX* or simply * in the previous sample) can be used in any of the
optional fields. Imbedded asterisks are not allowed.
A description of each field and its card position are shown in the data set that follows:
CCID (3)
The name of the CCID. The name must be fully specified, defining a valid CCID. This value must be
specified on every definition line. The same CCID may appear on multiple lines.
Userid (16)
(Optional) If used, only the users whose user ID is specified (whether by full name or with the use
of a name mask) may use the CCID indicated on this line.
Environ (25)
(Optional) Environment name. If used, only elements in the environment specified (whether by
full name or with the use of a name mask) can be updated under the CCID indicated on this line.
# (34)
(Optional) Stage number. If used, only elements in the stage specified (1, 2, or *) can be updated
under the CCID indicated on this line.
System (36)
(Optional) System name. If used, only elements in the system specified (whether by full name or
with the use of a name mask) can be updated under the CCID indicated on this line.
Subsys (45)
(Optional) Subsystem name. If used, only elements in the subsystem specified (whether by full
name or with the use of a name mask) can be updated under the CCID indicated on this line.
04-May-2018 1017/1109
CA Endevor® SCM - 17.0
Type (54)
(Optional) Element type. If used, only elements of the type specified (whether by full name or
with the use of a name mask) can be updated under the CCID indicated on this line.
Element (63)
(Optional) Element name. If used, only elements whose names are specified (whether by full
name or with the use of a name mask) can be updated under the CCID indicated on this line.
ADD
UPDATE
RETRIEVE
GENERATE
MOVE
TRANSFER
DELETE
RESTORE
CA Endevor SCM uses the CCID and/or comment that you specify for the action to update one or
more of the following fields:
The fields that CA Endevor SCM updates depend on the action you specify. The following sections on
specific actions provide details on which of the CCID and/or COMMENT fields are updated, and under
what circumstances.
04-May-2018 1018/1109
CA Endevor® SCM - 17.0
Specifying an Add Action for a New Element— When you specify a CCID and/or comment in an ADD
action for a new element, CA Endevor SCM uses this CCID and/or comment to set the following fields:
GENERATE and COMPONENT LIST DELTA CCID and/or COMMENT fields if the generate processor
is run.
In addition, the first time an element is added to CA Endevor SCM the comment specified is stored
separately. This comment appears in the ELEMENT DESCRIPTION field of the Master Control File
display, and remains with the element as long as it resides in CA Endevor SCM.
Specifying an Add Action for an Existing Element— When you specify a CCID and/or comment in an
ADD action for an existing element, CA Endevor SCM uses this CCID and/or comment to set the
following fields:
CURRENT SOURCE and SOURCE DELTA CCID and/or COMMENT fields if the element has changed.
COMPONENT LIST DELTA CCID and/or COMMENT fields if the component list has changed.
CA Endevor SCM also clears the Stage 1 RETRIEVE CCID and/or COMMENT fields when you add an
existing element.
Important! If you specify the BYPASS GENERATE PROCESSOR option, the ADD action does
not set the generate or component list delta CCID and/or COMMENT fields.
04-May-2018 1019/1109
CA Endevor® SCM - 17.0
CURRENT SOURCE and SOURCE DELTA CCID and/or COMMENT fields if the element has changed.
COMPONENT LIST DELTA CCID and/or COMMENT fields if the component list has changed.
CA Endevor SCM also clears the Stage 1 RETRIEVE CCID and/or COMMENT fields when you UPDATE
an element.
Important! If you specify the BYPASS GENERATE PROCESSOR option, the UPDATE action
does not set the generate or component list delta CCID and/or COMMENT fields.
Specifying a Generate Action without Copyback— When you specify a CCID and/or comment in a
GENERATE action without copyback, CA Endevor SCM uses this CCID and/or comment to set the
following fields:
COMPONENT LIST DELTA CCID and/or COMMENT fields if running the generate processor causes
the component list to change.
Specifying a Generate Action with Copyback— When you specify a CCID and/or comment in a
GENERATE action with copyback, CA Endevor SCM uses this CCID and/or comment to set the
following fields:
GENERATE and COMPONENT LIST DELTA CCID and/or COMMENT fields at the generate location.
CA Endevor SCM also sets current source and source delta CCID and/or COMMENT fields to the value
associated with the element that is copied back.
04-May-2018 1020/1109
CA Endevor® SCM - 17.0
Specifying a Move Action without History— When you specify a CCID and/or comment in a MOVE
action without history, CA Endevor SCM uses this CCID and/or comment to set the LAST ACTION CCID
and/or COMMENT fields. CA Endevor SCM also performs the following actions:
Sets the target CURRENT SOURCE and GENERATE CCID and/or COMMENT fields to their value at
the starting location of the MOVE.
Sets the target SOURCE DELTA and COMPONENT LIST DELTA CCID and/or COMMENT fields to
their last value at the starting location of the MOVE.
Specifying a Move Action with History— When you specify a CCID and/or comment in a MOVE action
with history, CA Endevor SCM uses this CCID and/or comment to set the LAST ACTION CCID and/or
COMMENT fields. CA Endevor SCM also performs the following actions:
Sets the CURRENT SOURCE and GENERATE CCID and/or COMMENT fields to their start location
value.
Moves SOURCE DELTA and COMPONENT LIST DELTA CCIDs and COMMENTs with their respective
delta levels.
Specifying a Transfer Action without History— When you specify a CCID and/or comment in a
TRANSFER action without history, CA Endevor SCM uses this CCID and/or comment to set the
following fields:
GENERATE and COMPONENT LIST DELTA CCID and/or COMMENT fields if the generate processor
is run.
Sets the CURRENT SOURCE CCID and/or COMMENT fields from their value in the previous stage.
04-May-2018 1021/1109
CA Endevor® SCM - 17.0
Sets the SOURCE DELTA CCID and/or COMMENT fields from their last delta value in the previous
stage.
Specifying a Transfer Action with History— When you specify a CCID and/or comment in a TRANSFER
action with history, CA Endevor SCM uses this CCID and/or comment to set the following fields:
GENERATE and COMPONENT LIST DELTA CCID and/or COMMENT fields if the generate processor
is run.
Sets the CURRENT SOURCE CCID and/or COMMENT fields from their value in the previous stage.
Moves SOURCE DELTA CCIDs and COMMENTs with their respective delta levels.
Specifying Synchronize along with the Transfer with History— CA Endevor SCM creates a synchronize
source delta level. When CA Endevor SCM creates this synchronize delta level, it performs the
following actions:
Sets the CCID and/or COMMENT fields from the base value.
Sets the synchronize flag to indicate that this source delta level was created as a result of the
synchronize option.
Important! If you specify the BYPASS GENERATE PROCESSOR, the TRANSFER action does
not set the generate or component list delta CCID and/or COMMENT fields.
GENERATE and COMPONENT LIST DELTA CCID and/or COMMENT fields if the generate processor
04-May-2018 1022/1109
CA Endevor® SCM - 17.0
GENERATE and COMPONENT LIST DELTA CCID and/or COMMENT fields if the generate processor
is run.
CA Endevor SCM sets the CURRENT SOURCE, SOURCE DELTA, and RETRIEVE CCID and/or COMMENT
fields based on the contents of the archive data set from which you restore.
Important! If you specify the BYPASS GENERATE PROCESSOR, the RESTORE action will not
set the generate or component list delta CCID and/or COMMENT fields.
04-May-2018 1023/1109
CA Endevor® SCM - 17.0
04-May-2018 1024/1109
CA Endevor® SCM - 17.0
Element Registration
Contents
Element Registration
The element registration feature enables you to choose whether you want to restrict the use of the
same element name. Duplicate element names can be problematic; however, there are situations
where they are desirable. For example, the same element name is used for a program as well as its
JCL.
When you define a system, CA Endevor SCM provides two options that let you allow or disallow
duplicate element names. One option enables you to control the use of duplicate element names
across subsystems within the system. The other option lets you control the use of duplicate element
names at the processor group level within the system. Both ways of controlling duplicate element
names can be made to apply across systems.
Note: Verify you are using the same message severity level for the system in each
environment where the system appears. If you do not, element actions may behave in an
unpredictable manner. Similarly, if element registration is activated for a system, make
sure it is activated in each environment in which it appears.
By default, element name registration is defined at the system level on the system definition. You can
also specify the element name registration options you want to apply to element name registration
across systems. This is an optional feature you can activate in the optional features table ENCOPTBL
by turning on the option REGISTER_ACROSS_SYSTEMS. If this option is turned on, CA Endevor SCM
ignores the element name registration setting on the system definitions.
04-May-2018 1025/1109
CA Endevor® SCM - 17.0
There are two sets of parameters that you can use to control duplicate element names at the system
and subsystem level:
E (Error)
The same element name exists within another subsystem under the same system; the action
is terminated and an error message is issued.
C (Caution)
The same element name exists within another subsystem under the same system; the action
is performed and a caution message is issued.
W (Warning)
The same element name exists within another subsystem under the same system; the action
is performed and a warning message is issued.
Note: The System Definition panel displays the parameter values in the Duplicate Element
Name Check and Msg Severity Lvl fields.
When this option is turned on, CA Endevor SCM ignores all option settings for element name
registration at the system definitions. The option-severity set in ENCOPTBL will rule over all
systems in all the environments no matter what the element name registration option settings in
the system definitions contain. If the REGISTER_ACROSS_SYSTEMS option is set to OFF, or is not
activated in ENCOPTBL, then the settings on the system definition are used to determine what
rules apply. This option has no impact on the way element registration works at the processor
group level. You can continue to define elements with the same name in the same system
/subsystem if the Duplicate Proc O/P Type check settings allow this.
04-May-2018 1026/1109
CA Endevor® SCM - 17.0
During action processing, if the element already exists at the target location within the same System
under a different Type with the same output Type, the action is terminated or a warning message
issued. This also occurs if an element with the same name and processor output Type, but different
Type, already exists in a different System, provided the optional feature to check across Systems is
enabled in ENCOPTBL.
Optionally, the search can extend to the Subsystem level. In this case, the searches for duplicate
element names at the processor group level extends across Subsystems defined to a specific System.
Specific Subsystems can be excluded from the search.
To enable Element Registration at the processor group level, perform the following steps:
E (Error) - The action is not performed and an error message is issued. The default.
04-May-2018 1027/1109
CA Endevor® SCM - 17.0
E (Error) - The action is not performed and an error message is issued. The default.
This activates Element Registration for processor groups for the System you are updating on
the System Definition panel. If you specify ACROSS SBS=Y, the check will extend to the
Subsystems defined to this System.
2. (Optional) If the ACROSS SBS=Y option is set on the System definition, you can exclude specific
Subsystems from the check. To exclude a Subsystem from the check, set the following option
on the Subsystem Definition panel:
EXCLUDE FROM DUPLICATE ELEMENT PROC O/P TYPE CHECK=Y - Excludes this Subsystem
from the check.
3. (Optional) To activate Element Registration across all Systems at the processor group level,
the following parameter must be set in the Optional Features table (ENCOPTBL):
ENHOPT ELM_REG_CHK_OUTPTYPE_ACROSS_SYSTEMS=ON
Note: For processor groups, you can define an output Type or use the default output Type.
The default processor output Type is a concatenation of the element Type and the
processor group name. Using the default can help you avoid duplicates.
You can implement the processor group option for selected inventory. For the inventory that should
not be checked, leave the output value as it is originally set; that is, a concatenation of the element
type and processor group names. Using the default value ensures there are no registration conflicts.
04-May-2018 1028/1109
CA Endevor® SCM - 17.0
Site Symbolics
Site-defined symbolics are user-defined symbolic values that you reference within dataset name
specifications for base, delta, source output, include libraries, and processors (that is, you can use
them wherever you can use CA Endevor SCM symbolics).
The site symbolics facility enables you to define global symbols that can be used in type and
processor definitions to reference data set name specifications for base, delta, source output, include
libraries, and processors (that is, you can use them wherever you can use CA Endevor SCM
symbolics). Thus, commonly referenced data sets can be defined in a single location significantly
easing maintenance. At execution time, all site symbolics referenced by a processor are stored with
the processor symbolics in the component data. If a site symbolic is also specified as a processor
symbolic, the processor symbolic (and processor symbolic override) take precedence.
When CA Endevor SCM is initialized, the site symbolics are placed into memory. When CA Endevor
SCM is terminated, the site symbolic storage is released. If more than one CA Endevor SCM task is
executing, each task has its own discrete site symbolic storage.
To implement site symbolics, you must define the symbolic and its data value in a table that is
assembled and linked into an authorized load library. Once this is done, you must update the
SYMBOLTBL parameter in the C1DEFLTS table with the name of the site symbolics table. These
actions are described next.
Note: Site symbolics are required only if you are using USS HFS pathname specifications for
element type base or source output file definitions. Otherwise, site symbolics are optional.
Site symbolic names can contain up to twelve characters, including the "#".
Site symbolics are referenced with an ampersand preceding the symbolic name. For example, site
symbolic #VENDORLB is referenced as:
&#VENDORLB
SYMDATA values must be enclosed in quotes if the value contains ampersands or quotes. For
04-May-2018 1029/1109
CA Endevor® SCM - 17.0
SYMDATA values must be enclosed in quotes if the value contains ampersands or quotes. For
example:
the value '&&C1SU'. sets a value of &C1SU
or
the value 'CICS(''SP''),NODBCS' sets a value of CICS('SP'),NODBCS
Quotes or ampersands imbedded in the SYMDATA value must be doubled. For example:
the value '&&C1SU'. sets a value of &C1SU
or
the value '&&&&C1SU'. sets a value of &&C1SU
or
the value 'CICS(''SP''),NODBCS' sets a value of CICS('SP'),NODBCS
If you need to continue a symbol definition on a second line, place a non-blank character in
column 72 and begin the next line in column 16.
symbolname
The symbol name must begin with the # character and is 1 to 11 characters in length. The #
indicates that the symbol is defined in the site-defined symbolics table.
symbolvalue
The data value associated with the site symbolic is 1 to 70 characters in length, with no
restrictions on the content of the data.
If you do not specify a data value for a symbolic, CA Endevor SCM treats it as a null variable. For
example, the following symbolic contains a null value:
ESYMBOL SYMNAME= APA,SYMDATA=' ',
For example:
$ESYMBOL SYMNAME=#VENDORLB,SYMDATA=SYS2.VENDOR.LOADLIB
Use JCL member BC1JTABL in iprfx.iqual.CSIQJCL to assemble and link-edit the site defined symbolics
table. An alternative is to employ an SMP/E USERMOD to accomplish this.
Update C1DEFLTS
After creating the symbolics table, update C1DEFLTS to reflect the table name. Use the SYMBOLTBL=
parameter to define the table name. The Site Information from the C1DEFLTS panel displays the
parameter value in the SYMBOLICS Table field.
04-May-2018 1030/1109
CA Endevor® SCM - 17.0
SMF Recording
Contents
Security records
For each security violation, or each error that is returned from the security exit (exit 1).
Activity records
For each action executed, except for the following actions: Print, Display, Copy, and List. Activity
records are written out at the end of action processing.
The administrator enables the SMF option in the Defaults table (C1DEFLTS). Per Environment,
recording can be enabled for security records, activity records, or both.
1. Edit the SMFREC# parameter in the C1DEFLTS TYPE=MAIN macro to specify an SMF record
number for for your site.
SMFREC# -- Specifies the SMF record number assigned to SMF records written by CA Endevor
SCM at this site. Default is 0, which disables SMF recording.
Talk to a systems programmer at your site to ensure that you are collecting the SMF records
related to the record number specified in the SMFREC# parameter. Recording records is
controlled in SYS1.PARMLIB(SMFPRMxx).
Y
Writes activity records for the Environment.
N
Does not write activity records for the Environment. Default is N.
SMFSEC -- Specifies whether to write SMF security records for this Environment.
04-May-2018 1031/1109
CA Endevor® SCM - 17.0
Y
Writes security records for the Environment.
N
Does not write security records for the Environment. Default is N.
Note: You can use the CSV utility to extract SMF record data corresponding to activity
related to CA Endevor SCM actions or to security violations recorded by CA Endevor SCM.
For more information, see Using the Comma-Separated Value (CSV) Utility (https://docops.ca.
com/display/CE17/CSV+Reporting+Utility).
Record Formats
CA Endevor SCM uses several blocks to build the SMF security and activity records, each comprising
one or more DSECTs. All SMF DSECTs are supplied by the following macros in iprfx.iqual.CSIQOPTN:
$SMFBKDS, $SMFHDDS, $SMFREC1, $SMFREC2, $SMFREC4.
Each SMF record output by CA Endevor SCM starts with a standard SMF header block (DSECT
$SMFHDDS), which contains fields required by SMF, and the Environment and user names for the
Element being processed. CA Endevor SCM records can be identified by the record type field in the
header block (SMHRECTY), which is defined in the Defaults Table for each site. This field is the same
for each CA Endevor SCM SMF record, and identifies the records as being specific to CA Endevor SCM.
Following the header block, each record has a data block that is specific to the record type:
DSECT $SMFREC2 for activity records. For activity records, the $SMFREC2 block encompasses one
or more action-specific blocks.
Note: For more information about each DSECT used to format SMF records, see DSECT
Descriptions (see page 1035).
$SMFHDDS
04-May-2018 1032/1109
CA Endevor® SCM - 17.0
$SMFREC1
Note: For more information about each action block, identified separately, see $SMFBKDS
DSECT: Action-Specific Blocks (see page 1039).
The combined format for SMF activity records, is described using the following DSECTs:
$SMFHDDS
$SMFREC2
There are five different types of action-block detail information, each having a different format, or
DSECT (within the $SMFBKDS DSECT). Each format applies to specific actions, described briefly as
follows. Where two occurrences of a DSECT are used by an action, (2) follows the action name,
below.
Retrieve
(2)
Generate
(2)
Move (2)
04-May-2018 1033/1109
CA Endevor® SCM - 17.0
Transfer
(2)
Archive
(2)
Restore
(2)
2 Last Change Add Information about the last processor executed: processor name,
(SM2LCGDS) date and time of execution, etc. Used for actions that can invoke a
Update processor.
Generate
Move
Delete
Transfer
Restore
3 Processor Add Information about the last processor executed: processor name,
Info date and time of execution, etc. Used for actions that can invoke a
(SM2LPRDS) Update processor.
Generate
Move
Delete
Transfer
Restore
4 Request All General information about the action: CCID, comments, and so
Parameter actions forth.
Info
(SM2REQDS)
5 Alter Info Alter Information specific to the Alter action: Before field value, after field
(SM2ALTDS) value, and match (mask) value.
04-May-2018 1034/1109
CA Endevor® SCM - 17.0
DSECT Descriptions
This section describes each of the DSECTs used to write out SMF activity and security records. In
cases where specific fields are not applicable for the current processing, alphabetic fields are space-
filled and numeric fields are zero-filled.
SMHLEN
Size of the (security or activity) record, in bytes. This includes the size of the header block as well
as the data block:
$SMFREC1-Security records
SMHSEGID
Not used.
SMHSID
Operating system against which the SMF record is written. Always X'02' with release 3.7.
SMHRECTY
Number that identifies this SMF record as specific to CA Endevor SCM. This number is defined to
CA Endevor SCM through the Defaults Table.
SMHTIME
Time the SMF record was created (binary time of day in 100ths of a second-1 = .01 second).
SMHDATE
Date the SMF record was created (packed yyddd).
SMHCPUID
Number to identify the CPU model on which CA Endevor SCM is running.
SMHHDLEN
Size of the header block (DSECT $SMFHDDS), in bytes.
SMHC1VER
Code that identifies the format of the SMF record.
SMH$RF00-This record was created by CA Endevor SCM release 2.2 or a prior release.
04-May-2018 1035/1109
CA Endevor® SCM - 17.0
SMH$RF01-This record was created by CA Endevor SCM release 2.5 or a later release.
SMHCTLTY
Code that identifies the next record format in the SMF record.
SMHCONT
Not used.
SMHSEQ
Not used.
SMHC1ENV
Environment name associated with the current processing.
SMHUSER
User ID associated with the current processing.
SMHSIZE
Size of the $SMFHDDS DSECT.
The following information describes the fields in the security record data block:
SM1RECLN
Size of this data block (DSECT $SMFREC1), in bytes.
SM1RECVN
Version number. Identifies the CA Endevor SCM release that created the record. Valid values are:
1 -- The record was created by a release of CA Endevor SCM prior to release 4.0.
2 -- The record was created by CA Endevor SCM release 4.0 or a later release.
SM1FUNC
Number that identifies the current activity: generally the type of action.
SM1FUNNM
Applicable if SM1FUNC references a CA Endevor SCM action. Name of the current action (ADD,
UPDATE, etc.).
SM1ERRCD
The 4 characters that are used to construct the error code written to the CA Endevor SCM
Execution Report for the current action in the ECBMSGCD field. The error code is formatted as
C1XNNNNS, where:
04-May-2018 1036/1109
CA Endevor® SCM - 17.0
S-Severity code associated with the return code field, ECBRTCD, in DSECT $ECBDS.
SM1ERRLN
Not used.
SM1ERMSG
Error message associated with the current activity for the ECBMSG field.
SM1SITE
CA Endevor SCM site ID, as defined to the Defaults Table.
SM1STGID
Stage number for the current action request: 1 or 2.
SM1STGCD
Applicable if SM1FUNC references a CA Endevor SCM action. Stage ID for the current action
request.
SM1IFUNC
Action information that is used internally by CA Endevor SCM.
SM1ENVM
Environment name for the current processing.
SM1STAGE
Applicable if SM1FUNC references a CA Endevor SCM action. Stage name for the current action
request.
SM1SYSTM
Applicable if SM1FUNC references a CA Endevor SCM action. System name for the current action.
SM1SUBSY
Applicable if SM1FUNC references a CA Endevor SCM action. Subsystem name for the current
action.
SM1STYPE
Applicable if SM1FUNC references a CA Endevor SCM action. Element type for the current action.
SM1ELEMT
(SM1RECVN version 1 records only) Applicable if SM1FUNC references a CA Endevor SCM action.
Name of the Element specified for the current action.
SM1EAOFF
(SM1RECVN version 2 records only) Element area offset. When the offset is added to the
beginning of the record's address, the resulting address points to an area with in the SM1BFAREA.
The Element area is comprised of two adjacent components:
Element name
SM1DSNAM
04-May-2018 1037/1109
CA Endevor® SCM - 17.0
SM1DSNAM
(SM1RECVN version 1 records only) Applicable for security violations that relate to ADD, UPDATE,
RESTORE, ARCHIVE, and RETRIEVE action requests. Data set name associated with the external
file used by the current action.
SM1FAOFF
(SM1RECVN version 2 records only) File area offset. When the offset is added to the beginning of
the record's address, the resulting address points to an area with in the SM1BFAREA. The file area
is comprised of two adjacent components:
File name
SM1DSMEM
(SM1RECVN version 1 records only) Applicable for security violations that relate to ADD, UPDATE,
RESTORE, ARCHIVE, and RETRIEVE action requests. Member name associated with the Element
for which the current action applies, within the above data set. Applicable when the data set is a
library.
SM1NAOFF
(SM1RECVN version 2 records only) Name area offset. When the offset is added to the beginning
of the record's address, the resulting address points to an area with in the SM1BFAREA. The name
area consists of two adjacent components:
File name
SM1BSIZ
Base size of the record.
SM1BFAREA
(SM1RECVN version 2 records only) This is reserved record space containing the various areas
such as Element, file and name.
SM1SIZ
Size of the $SMFREC1 DSECT
The following information describes the activity record data block fields:
04-May-2018 1038/1109
CA Endevor® SCM - 17.0
SM2RECLN
Size of this data block (DSECT $SMFREC2), in bytes, including all action-specific blocks included at
the end (DSECT $SMFBKDS).
SM2RECVN
Version number to identify this data block ($SMFREC2). This value was updated to 2 for addition
of the Alter block. Use the SM2$CURV label to detect that either the record is the current version
(2) or the previous version of the SMF activity record.
SM2FUNC
Number that identifies the current activity: generally the current type of action.
SM2FUNNM
Applicable if SM2FUNC references a CA Endevor SCM action. Name of the current action (ADD,
UPDATE, and so forth).
SM2BLKS
Count of action-specific blocks included at the end of this DSECT: 1-5.
SM2RECHD
Size of this data block (DSECT $SMFREC2), in bytes, excluding the action-specific blocks (DSECT
$SMFBKDS).
SM2IFUNC
Action information that is used internally by CA Endevor SCM.
SM2HDRLN
Size of the $SMFREC2 DSECT, excluding the action-specific blocks
SM2SIZ
Size of the $SMFREC2 DSECT, including all action-specific blocks incorporated at the end.
SM2BLEN
Size of this action-specific block (action-block header, SM2BHDDS, plus the action-block detail
DSECT), in bytes.
04-May-2018 1039/1109
CA Endevor® SCM - 17.0
SM2BTYP
Code that indicates the DSECT used to write out the action-block detail for this action- specific
block:
SM2BVER
Version number to identify this DSECT ($SMFBKDS). This should always be 1 except for the action
block header.
SM2BFLG1
Not used.
SM2BFLG2
Not used.
SM2BHDR
Size of the action-block header ($SM2BHDDS).
SM2SITE
CA Endevor SCM site ID, as defined to the Defaults Table.
SM2STGCD
Stage ID for the current action request.
SM13STGID
Stage number for the current action request: 1 or 2.
SM2SRCHR
Search and Replace utility flag.
SM2$ELEM
Search and Replace utility action on an Element.
SM2$COMP
Search and Replace utility action on an output component.
SM2VER
Version number associated in the MCF with the Element for the action request.
SM2LVL
Number to identify the current level of the Element for the current action request.
SM2STAGE
Stage name for the current action request.
SM2SYSTM
System name for the current action request.
04-May-2018 1040/1109
CA Endevor® SCM - 17.0
SM2SUBSY
Subsystem name for the current action request.
SM2STYPE
Element type for the current action request.
SM2ELEMT
(Version 1 Record Only) Name of the Element specified for the current action request.
SM2EAOFF
(Version 2 Record Only) Element area offset. The Element name for the current action request is
stored in the buffer area located near the end of the record. When the offset is added to the
beginning of this record's address, the resulting address points to an area within SM2EAREA
buffer space. The Element area is composed of two adjacent components:
Element name
SM2PRGRP
Processor group name for the current action request.
SM2DSNAM
(Version 1 Record Only) Applicable for ADD, UPDATE, RESTORE, ARCHIVE, and RETRIEVE action
requests. Data set name associated with the external file used by the current action.
SM2FAOFF
(Version 2 Record Only) File area offset. The file name for the current action request is stored in
the buffer area located near the end of the record. When the offset is added to the beginning of
this record's address, the resulting address points to an area within SM2EAREA buffer space. The
file area is composed of two adjacent components:
The file name may be a traditional data set or an USS path name.
SM2DSMEM
(Version 1 Record Only) Applicable for ADD, UPDATE, RESTORE, ARCHIVE, and RETRIEVE action
requests. Member name associated with the Element for which the current action applies, within
the above data set. Applicable when the data set is a library; blank otherwise.
SM2NAOFF
(Version 2 Record Only) Name area offset. The member name for the current action request is
stored in the buffer area located near the end of the record. When the offset is added to the
beginning of this record's address, the resulting address points to an area within SM2EAREA
buffer space. The name area is composed of two adjacent components:
04-May-2018 1041/1109
CA Endevor® SCM - 17.0
If a member/file name is not applicable to the current action, the offset value is set to zero.
SM2EAREA
(Version 2 Record Only) Space reserved in the record containing various data such as the Element,
file and member name.
SM2ENVLN
Size of the action-specific block (header and detail) if the action-block detail uses the Environment
DSECT ($SM2ENVDS).
SM2CCOM
Current-level comment for the Element.
SM2MLDTE
Current-level date for the Element.
SM2MLTME
Current-level time for the Element.
SM2LUSID
Current-level user ID for the Element.
SM2MLACT
Last action executed for the Element.
SM2MLTOT
Count of source statements for the Element, as of the current level.
SM2LCHLN
Size of the action-specific block (header and detail) if the action-block detail uses the Last Change
DSECT ($SM2LCGDS).
SM2LPRON
(Element) name of the processor last run for the Element.
SM2LPROD
Processor date for the Element.
SM2LPROT
Processor time for the Element.
SM2LPROU
Processor user ID for the Element.
04-May-2018 1042/1109
CA Endevor® SCM - 17.0
SM2LPHRC
Processor return code for the Element.
SM2LPRC1
CA Endevor SCM return code for the Element.
SM2PRCLN
Size of the action-specific block (header and detail) if the action-block detail uses the Processor
Information DSECT ($SM2LPRDS).
SM2RCCID
CCID associated with the current action request.
SM2RCOMM
Comments associated with the current action request.
SM2RFLAG
Not used.
SM2RSISO
Indicates whether the current action requested a signout override: Y (Yes) or N (No).
SM2RSICO
Applicable for a RETRIEVE action. Indicates whether the current action specified copy-only: Y (Yes)
or N (No).
SM2REXPN
Applicable for a RETRIEVE action. Indicates whether the current action requested that INCLUDEs
be expanded: Y (Yes) or N (No).
SM2ROVER
Applicable for a RETRIEVE action. Indicates whether the current action requested an overwrite if a
member by the same name exists already in the output library: Y (Yes) or N (No).
SM2RRTCD
The return code associated with the current action request.
SM2RDEL
Indicates whether the Element was deleted upon completion of the requested action: Y (Yes) or N
(No). This value is X'40' if a delete does not apply for the current action.
SM2REQLN
Size of the action-specific block (header and detail) if the action-block detail uses the Request
Parameter Information DSECT ($SM2REQDS).
SM2REMCH
Indicates whether the Validate action with the Element Master option was specified. Possible
values are: Y (Yes) or N (No).
04-May-2018 1043/1109
CA Endevor® SCM - 17.0
Note: This field is currently not in use and will not be populated.
SM2RSYCH
Indicates whether the Validate action with the Synchronization option was specified. Possible
values are: Y (Yes) or N (No).
Note: This field is currently not in use and will not be populated.
SM2RCMCH
Indicates whether the Validate action with the Component Validation option was specified.
Possible values are: Y (Yes) or N (No).
Note: This field is currently not in use and will not be populated.
SM2RTMSG
Indicates whether the Validate action with the Terse option was specified. Possible values are: Y
(Yes) or N (No).
Note: This field is currently not in use and will not be populated.
SM2RAUTG
Indicates whether the AUTOGEN Element option was specified on the ADD, UPDATE or GENERATE
action. Possible values are: Y (Yes) or N (No). If the value of this field is Y, the value of the
SM2AUTX field will be N.
SM2RAUTX
Indicates whether this where-used Element was generated on behalf of a component Element.
Possible values are: Y (Yes) or N (No). If the value of this field is Y, the value of the SM2AUTG field
will be N.
SM2RNSRC
Indicates whether the NOSOURCE action option was in effect for the Generate, Add, or Update
action. Possible values are: Y (Yes) or N (No).
SM2RSPAN
Indicates whether one of the Autogen Span options was specified on the Add, Update or
Generate action. Possible values are: N (span none), A (span all), S (span Systems), B (span
Subsystems).
SM2AFLD
Contains the field ID requested for an Alter action. An SMF record is created for each field
requested in an Alter action, meaning that one Alter action can create several Alter SMF records.
04-May-2018 1044/1109
CA Endevor® SCM - 17.0
Note: An SMF record is only created if the Alter action is performed and the Master
Control File is updated. No SMF record is created in the following cirsumstances:
SM2AUPDT
Indicates whether the Master Control File was updated. Valid values are Y or N:
Y -- Indicates that the Master Control File record was updated.
N -- Indicates that the Master Control File record was not updated.
SM2ADATA
Label for the beginning of the variable Alter data area. For the Alter action data area, only one
group of fields exists per record, the data area is redefined for each group of fields. These fields
correspond to the Alter action field IDs, refer to SMA2FLD for field ID values.
Generate CCID fields:
SM2ACCGB
Value of the Generate CCID before the Alter action.
SM2ACCGA
Value of the Generate CCID after the Alter action.
SM2ACCGM
Mask value specified as the from-value for the Generate CCID.
SM2ACCLB
Value of the Last Action CCID before the Alter action.
SM2ACCLA
Value of the Last Action CCID after the Alter action.
SM2ACCLM
Mask value specified as the from-value for the Last Action CCID.
04-May-2018 1045/1109
CA Endevor® SCM - 17.0
SM2ACCRB
Value of the Retrieve CCID before the Alter action.
SM2ACCRA
Value of the Retrieve CCID after the Alter action.
SM2ACCRM
Mask value specified as the from-value for the Retrieve CCID.
Description fields:
SM2ADESB
Value of the Description before the Alter action.
SM2ADESA
Value of the Description after the Alter action.
SM2ADESM
Mask value specified as the from-value for the Description.
SM2APRGB
Value of the Processor Group before the Alter action.
SM2APRGA
Value of the Processor Group after the Alter action.
SM2APRGM
Mask value specified as the from-value for the Processor Group.
SM2ASGNB
Value of the Signout Userid before the Alter action.
SM2ASGNA
Value of the Signout Userid after the Alter action.
SM2ASGNM
Mask value specified as the from-value for the Signout Userid.
SM2AUSRB
Value of the User Data before the Alter action.
SM2AUSRA
Value of the User Data after the Alter action.
SM2AUSRM
Mask value specified as the from-value for the User Data.
SM2AUSR_FPOS
04-May-2018 1046/1109
CA Endevor® SCM - 17.0
SM2AUSR_FPOS
From-position specified for the User Data.
SM2AUSR_FTXL
Length of the mask value (from-value) text string for the User Data.
SM2AUSR_TPOS
To-position specified for the User Data.
SM2AUSR_TLEN
To length specified for the User Data.
SM2AUSR_TTXL
Text length of the replacement value specified for the User Data.
SM2AUSR_TPAD
Pad character specified for the User Data. This field is required if the “to” length
(SM2AUSR_TLEN) is greater than the length of the replacement value (SM2AUSR_TTXL)
04-May-2018 1047/1109
CA Endevor® SCM - 17.0
CA Endevor® SCM provides a utility, BSTPCOMP, which compares the contents of two PDS or PDS/E
members or sequential files, and reports the differences between them. The members/files being
compared can be--but need not necessarily be--previously retrieved CA Endevor® SCM elements.
BSTPCOMP accepts two files as input; these files can be PDS or PDS/E members or sequential files.
The files can be fixed or variable length, but cannot exceed an LRECL of 256 (260 for variable-length
files).
BSTPCOMP reports the differences between the two files. The first file, NDVRIN1, is assumed to be
the base file. The second file, NDVRIN2, is assumed to be the changed file. BSTPCOMP reports the
differences in file 2 as compared to file 1.
The files are compared line-by-line, based on the contents of particular (contiguous) characters. The
range of characters included in the compare is defined in terms of a from and through column, but
cannot exceed 256. For example, you might want to compare two files based on the contents of
positions 1-5 only.
If the files compare identically, no output is produced other than the syntax listing (if applicable).
Data is only listed when differences are detected.
The output from BSTPCOMP can be formatted for browse (without ASA characters and headings) or
for hardcopy printout (including ASA characters and headers).
Note: Beware of problems when comparing fixed records to variable records. Spaces are
not equal to nulls.
04-May-2018 1048/1109
CA Endevor® SCM - 17.0
No Overrides Method
By default, BSTPCOMP compares columns 1 through 72, lists changes only, and formats for printing if
the NDVRLST DDname is available. If NDVRLST is unavailable, the output is formatted for BROWSE
and written to file NDVRPCH.
If the input files are variable length, the comparison considers short records to be padded with blanks
up to the through column.
In the following example, BSTPCOMP has been instructed to compare the data in DDname NDVRIN1
with data in DDname NDVRIN2 and report changes (if any) within columns 1 through 72. If there are
changes, the output would be written to DDname NDVRLST with page headings.
Note: NDVRIN1 and NDVRIN2 must be sequential data sets or a partitioned data set with a
member name specified.
//*
//* RESTRICTION:
//* LRECL FOR INPUT FILES (NDVRIN1, NDVRIN2) MAY NOT EXCEED 256
//*
//STEP1 EXEC PGM=BSTPCOMP,REGION=2000K,
//STEPLIB DD DSN=iprfx.iqual.CSIQAUTH,DISP=SHR
//*
//* ONE OF THE FOLLOWING WILL RECEIVE YOUR OUTPUT
//NDVRLST DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=133)
//*
//* YOU MAY HAVE SOME OTHER WAY OF ALLOCATING SORT WORK FILES.
//SORTWK01 DD UNIT=tdisk,SPACE=(CYL,(2,1))
//SORTWK02 DD UNIT=tdisk,SPACE=(CYL,(2,1))
//*
//* THE NEXT TWO DESCRIBE THE FILES YOU WANT TO COMPARE
//NDVRIN1 DD DISP=SHR,DSN=uprfx.uqual.FILE1(MEMBER)
//NDVRIN2 DD DISP=SHR,DSN=uprfx.uqual.FILE2(MEMBER)
/*
04-May-2018 1049/1109
CA Endevor® SCM - 17.0
For more information about the IEBUPDTE option, see The IEBUPDTE Request Card Generator (see
page ).
COLUMN
Specifies the range of columns to compare. If omitted, columns 1-72 are used.
OUTPUT
Specifies which records are to be output. The default is CHANGES only. The other options are:
HISTORY (shows the existing member together with inserts and deletes), and NEW (shows the
new member, highlighting inserts only).
FORMAT
Specifies the output format. The default is DISPLAY which writes the output to file NDVRLST. The
syntax listing is produced first, followed by the original output file in report format--with carriage
control and page headings. The FILE option (that is, BROWSE) writes the data to DDname
NDVRPCH without page headings.
PAD
PAD is applicable to variable length records only. The default is BLANK (which pads short records
with blanks up to the compare length). The options are NULL (which pads with binary zeros) or
“x” (which pads with the specified single character).
SIZE
Specifies a file-size estimate for the sort. By default, this option is ignored.
TITLE
Appears before the first data line as a line of asterisks, followed by the title string and another
line of asterisks. Useful if FORMAT=FILE.
04-May-2018 1050/1109
CA Endevor® SCM - 17.0
RECORD
This clause is provided for DOS-compatibility only.
Note: NDVRIN1 and NDVRIN2 must be sequential data sets or a partitioned data set with a
member name specified.
//COMPARE EXEC PGM=BSTPCOMP,REGION=2000K
//STEPLIB DD DSN=iprfx.iqual.CSIQLOAD,DISP-SHR
//*
//NDVRIN1 DD DSN=OLD.FILE.LIBRARY(MEMBER),DISP=SHR
//NDVRIN2 DD DSN=NEW.FILE.LIBRARY(MEMBER),DISP=SHR
//*
//NDVRLST DD SYSOUT=* **SYNTAX LISTING + COMPARE OUTPUT**
//*SORTWORK FILES USED ONLY IF FILES TOO LARGE FOR IN-MEMORY COMPARE
//SORTWK01 DD UNIT=DASD,SPACE=(TRK,(1,30)
//SORTWK02 DD UNIT=DASD,SPACE=(TRK,(1,30)
//*
//NDVRIPT DD *
COMPARE COLUMN=1 TO 80 OUTPUT=HISTORY.
/*
The sample JCL which follows would produce a file for browsing:
//COMPARE EXEC PGM=BSTPCOMP,REGION=2000K
//STEPLIB DD DSN=iprfx.iqual.CSIQLOAD,DISP-SHR
//*
//NDVRIN1 DD DSN=OLD.FILE.LIBRARY(MEMBER),DISP=SHR
//NDVRIN2 DD DSN=NEW.FILE.LIBRARY(MEMBER),DISP=SHR
//*
//NDVRLST DD SYSOUT=* **SYNTAX LISTING + COMPARE OUTPUT**
//*SORTWORK FILES USED ONLY IF FILES TOO LARGE FOR IN-MEMORY COMPARE
//SORTWK01 DD UNIT=DASD,SPACE=(TRK,(1,30)
//SORTWK02 DD UNIT=DASD,SPACE=(TRK,(1,30)
//*
//NDVRIPT DD *
COMPARE COLUMN=1 TO 80 OUTPUT=HISTORY.
//*OUTPUT OF COMPARE: NOTE: RECORD LENGTH=#COMPARE COLUMNS + 16
//NDVRPCH DD DSN=OUTPUT.FILE.NAME,DISP=(,CATLG),
// UNIT=DASD,SPACE=(TRK,(5,5),RLSE),
// DCB=(LRECL=88,BLKSIZE=6072,RECFM=FB)
//*
The full syntax for the EXEC statement PARM values is shown next:
PARM='output-format,from,thru,rec-count,pad-char'
Specify the PARM values as described next. Separate the values using a single comma, leaving no
spaces between the values.
04-May-2018 1051/1109
CA Endevor® SCM - 17.0
output-format
The two-character code that indicates the type of comparison information you want reported
(character 1) and the format of the output file (character 2). The default is CD.
Specify the first character (type of information you want) as follows:
C-Print only the changes between the two files: that is, those lines that are in file 2 but not in
file 1, or those lines that are deleted from file 2.
B-Print (browse) the contents of file 2, highlighting those lines that are not in file 1 by printing
“%INSERT” to the left of those lines: “%” lets you scan for changes easily; “INSERT” indicates
that the line was new in file 2.
The entire contents of file 2, highlighting those lines that are not in file 1 by printing “%
INSERT” to the far left.
Lines that were in file 1 but not in file 2, highlighting these lines with “%DELETE” to the far
left.
F-The output file is in browse format and does not have any ASA characters or headers. The
output is written to DDname NDVRPCH
D-The output file is formatted for print, and includes ASA characters and headers. The output
is written to DDname NDVRLST.
from
Starting character for the compare. BSTPCOMP begins its search at this position in both files. The
default is 1.
thru
Ending character for the compare. BSTPCOMP ends its search with this position, within both files.
For variable-length records, if the record in one file is longer than that in the other, and the
through character extends beyond the end of the record, BSTPCOMP pads according to the pad-
char specification before performing the compare.
The default thru specification is 72.
rec-count
Largest number of records in either file. The default is 10000. Estimate high when specifying this
value.
pad-char
Pad character used for variable-length records, as described previously for the through
parameter. Specify this as follows. The default is BLANK.
BLANK--Blanks
04-May-2018 1052/1109
CA Endevor® SCM - 17.0
nnn
The hexadecimal equivalent of nnn, where nnn is a 1-3 character decimal value. Specify 64 to pad
with X'40', 255 to pad with X'FF', and so forth.
COPYRIGHT (C) CA, INC., E N D E V O R mm/dd/yy 11:58:23 PAGE 1
RELEASE X.XX SERIAL XXXXXX
BSTPCOMP - FILE COMPARE UTILITY
COMPARE OUTPUT=CHANGES . 00350002
INSERT MAIN $FUNCSTG PLSIZE=4 000006
DELETE MAIN $FUNCSTG 000006
INSERT WORD3 DS F 000010
INSERT SPACE 3 000012
INSERT MAIN999 $FEND 000014
DELETE $FEND 000012
%****** RECORDS: FILE 1 = 00014 FILE 2 = 00016 INSERTS = 00004 DELETES = 00002 ******
The following report is returned when you specify OUTPUT=NEW or output-format code BD (New
Browse Report). It lists the contents of file 2, highlighting any lines that are not in file 1 with “%
INSERT.”
COPYRIGHT (C) CA, INC., E N D E V O R mm/dd/yy 11:58:27 PAGE 1
RELEASE X.XX SERIAL XXXXXX
BSTPCOMP - FILE COMPARE UTILITY
COMPARE OUTPUT = NEW . 00490002
COMPTEST TITLE 'PROGRAM TO DEMONSTRATE COMPARE UTILITY' 000001
COMPT $MODNTRY LINKAGE=SUB 000002
TITLE 'DSECTS: DCB ' 000003
DCBD DSORG=PS 000004
TITLE MAIN: ENTRY FROM CALLER' 000005
%INSERT MAIN $FUNCSTG PLSIZE=4 000006
GLOBALS DS 0D 000007
04-May-2018 1053/1109
CA Endevor® SCM - 17.0
WORD1 DS F 000008
WORD2 DS F 000009
%INSERT WORD3 DS F 000010
$FUNC 000011
%INSERT SPACE 3 000012
SR R15,R15 RETURN CODE = SUCCESS 000013
%INSERT MAIN999 $FEND 000014
$MODEND 000015
END 000016
%****** RECORDS: FILE 1 = 00014 FILE 2 = 00016 INSERTS = 00004 DELETES = 00002 ******
The following report is returned when you specify OUTPUT=HISTORY or output-format code HD
(History Report). It lists the contents of file 2, highlighting inserts from file 2 and deletes from file 1.
COPYRIGHT (C) CA, INC., E N D E V O R mm/dd/yy 11:58:23 PAGE 1
RELEASE X.XX SERIAL XXXXXX
BSTPCOMP - FILE COMPARE UTILITY
COMPARE OUTPUT = HISTORY . 00630002
COMPTEST TITLE 'PROGRAM TO DEMONSTRATE COMPARE UTILITY' 000001
COMPT $MODNTRY LINKAGE=SUB 000002
TITLE 'DSECTS: DCB ' 000003
DCBD DSORG=PS 000004
TITLE MAIN: ENTRY FROM CALLER' 000005
%INSERT MAIN $FUNCSTG PLSIZE=4 000006
%DELETE MAIN $FUNCSTG 000006
GLOBALS DS 0D 000007
WORD1 DS F 000008
WORD2 DS F 000009
%INSERT WORD3 DS F 000010
$FUNC 000011
%INSERT SPACE 3 000012
SR R15,R15 RETURN CODE = SUCCESS 000013
%INSERT MAIN999 $FEND 000014
%DELETE $FEND 000012
$MODEND 000015
END 000016
%****** RECORDS: FILE 1 = 00014 FILE 2 = 00016 INSERTS = 00004 DELETES = 00002 ******
3000
The input files are identical for the columns compared. No reports were produced.
3001
An input or output file could not be opened. Ensure that the DD statements are correct for all files
and try again.
3002
The number of records in one or both of the input files exceeds the maximum count specified by
the rec-count parameter. Increase the count and try again. It is better to estimate high rather
than low.
3003
The LRECL for an input file exceeded 256 (260 for variable-length). You cannot use this file as
input.
04-May-2018 1054/1109
CA Endevor® SCM - 17.0
3005
The record format for an input file is Undefined. The record must specify Fixed or Variable.
3006
An input parameter is missing or invalid (for example, thru >from). Check your syntax against the
previous parameter descriptions, correct the problem, and resubmit the job.
3007
BSTPCOMP completed its compare successfully and found differences between the files. This is
the standard return code.
Note: When editing programs using ISPF, verify the option NUMBER ON is in effect. The
element type should define columns 1-80 as the compare columns.
1. In the first step, a CA Endevor® SCM element is printed to a temporary file using the PRINT
action in SCL, CA Endevor® SCM's Software Control Language. When specifying the PRINT
action, name masking can be used to select more than one element. Additionally, multiple
PRINT requests can be included in this first step.
2. In the second step, the IEBUPDTE Request Card Generator reads the file created by the first
step and creates IEBUPDTE control cards. If option CHANGES was specified in Step 1 on the
SCL request, then ./ UPDATE IEBUPDTE control cards are generated. If option BROWSE was
specified in Step 1, then ./ ADD IEBUPDTE control cards are generated.
Certain statements within the sample JCL control the generation of IEBUPDTE control cards:
The DDname C1PRINT specifies the output file created by Step 1. If a level is not specified, then
the current level is printed. The DCB attributes for this file are LRECL=133, RECFM=FB.
The DDname C1CHGSI specifies the temporary file created by Step 1 as shown on the DDname
04-May-2018 1055/1109
CA Endevor® SCM - 17.0
The DDname C1CHGSI specifies the temporary file created by Step 1 as shown on the DDname
C1PRINT.
Output created by the IEBUPDTE Request Card Generator is written to the DDname C1UPDTO.
The DCB attributes associated with this file are LRECL=80, RECFM=FB.
The PARM accepted as input by the program BC1PFUDP specifies the position of the sequence
number within the element. Two parameters can specify the beginning position and length of the
sequence numbers. PARM rules are as follows:
The first parameter, as shown in the JCL, is SEQBEG=. The default for SEQBEG is 73.
The second parameter is SEQLNG=. The default for SEQLNG is 7. Valid range for SEQLNG is 1-
8.
The JCL in member BC1JFUP2, found in the iprfx.iqual.CSIQJCL library, you to generate the following:
1. Two files, NDVRIN1 and NDVRIN2 are compared and the differences are written to a
temporary file. NDVRIN1 and NDVRIN2 must be sequential files or partitioned datasets with a
member name provided.
2. The IEBUPDTE Request Card Generator reads the file created by the first step and creates ./
UPDATE IEBUPDTE control cards.
Certain statements within the sample JCL control the generation of IEBUPDTE control cards: These
are as follows:
The DDname NDVRIPT is where the compare columns are specified. The parameters OUTPUT
CHANGES and FORMAT IEBUPDTE must be specified as shown in the example.
The DDnames NDVRIN1 and NDVRIN2 specify the two files to be compared. (Refer to the utility
BSTPCOMP for more information.)
The DDname NDVRPCH specifies the output file created by Step 1. The DCB attributes for this file
are LRECL=88, RECFM=FB.
The DDname C1CHGSI specifies the temporary file created by Step 1 as shown on the DDname
C1PRINT.
DDname C1UPDTO. The DCB attributes associated with this file are LRECL=80, RECFM=FB.
The PARM accepted as input by the program BC1PFUDP specifies the position of the sequence
number within the element, and the member name associated with the ./ UPDATE card. Three
parameters can be specified. PARM rules are as follows:
04-May-2018 1056/1109
CA Endevor® SCM - 17.0
The first parameter, as shown in the JCL, is SEQBEG=. The default for SEQBEG is 73 .
The second parameter is SEQLNG=. The default for SEQLNG is 7. Valid range for SEQLNG is 1-
8.
The third parameter is NAME=. This parameter controls the member name generated on the .
/ UPDATE control card. This parameter is required.
4
3000
9
3001
10
3002
11
3003
12
3005
13
3006
0
3007
04-May-2018 1057/1109
CA Endevor® SCM - 17.0
BSTXCOPY can be used to copy between PDS load libraries and PDSE load libraries, from PDSE to
PDSE, and from PDSE back to PDS. BSTXCOPY can copy aliases but the original loadlib member must
be present in the From library.
The following JCL shows how to execute this utility. The first library in the STEPLIB contains the
Endevor site-specific modules (C1DEFLTS, ENDICNFG, and so on):
//COPYEX EXEC PGM=NDVRC1,PARM=BSTXCOPY
//STEPLIB DD DISP=SHR,DSN=YOUR.ENDEVOR.CSIQAUTU
// DD DISP=SHR,DSN=YOUR.ENDEVOR.CSIQAUTH
// DD DISP=SHR,DSN=YOUR.ENDEVOR.CSIQLOAD
//SYSPRINT DD SYSOUT=*
//SYSUT3 DD UNIT=VIO,SPACE=(CYL,(1,2))
//SYSUT4 DD UNIT=VIO,SPACE=(CYL,(1,2))
//IND1 DD DISP=(OLD,PASS),DSN=YOUR.PDS.LOADLIB (PDS)
//IND2 DD DISP=(OLD,PASS),DSN=YOUR.PDS.LOADLIB (PDS)
//OUTDD DD DISP=(OLD,PASS),DSN=YOUR.NEW.PDSE.LOADLIB (PDSE)
//SYSIN DD *
COPY INDD=((IND1,R)),OUTDD=OUTDD
COPY INDD=((IND2,R)),OUTDD=OUTDD
For more information about the input syntax and restrictions, see Using Processor Utilities.
04-May-2018 1058/1109
CA Endevor® SCM - 17.0
Using CONCALL, you can invoke your programs from non-authorized libraries. Generally, programs
that are invoked directly from NDVRC1 must reside in an authorized library. This utility enables you to
bypass the STEPLIB (or LINKLST) residency requirement for the program that is specified in the
execution parameter. CONCALL can be used to invoke any program from a specified library. CONCALL
can also be used be used with the NDVRC1 server program to invoke batch programs from a non-
authorized library.
04-May-2018 1059/1109
CA Endevor® SCM - 17.0
Note: The Expand Include utility program is functionally stable. CA Support will answer
questions and diagnose and correct defects, in accordance with the CA Technologies
Support Policy and Terms. However, we will not provide any additional modifications that
alter the syntax logic to accommodate specific customer implementations.
The Expand Includes utility is a batch function that expands CA Panvalet ++INCLUDE or CA Librarian -
INC statements and, optionally, COBOL COPY statements.
If you are a CA Panvalet user and have converted your source management functions to CA
Endevor® SCM, use this utility to expand ++INCLUDE statements that are embedded in existing
application source code.
If you are a CA Librarian user and have converted your source management functions to CA
Endevor® SCM, use this utility to expand -INC statements that are embedded in existing
application source code.
If you use COBOL and have COPY statements embedded in the application source code, use this
utility to expand those statements.
The Expand Includes utility writes the expanded code to either a sequential data set or a partitioned
data set member.
If you use CA Librarian to expand your COBOL COPY statements, you may use the Expand Includes
utility to expand the COPY statements. The Expand Includes utility also supports the REPLACING/BY
keyword. For more information, see Processing Methods for Replacing Phrases (see page 1064)
If the SUPPRESS keyword is found, then processing of the COPY statement is bypassed, and the COPY
statement is written to the destination file as-is.
04-May-2018 1060/1109
CA Endevor® SCM - 17.0
Important! The Expand Includes utility does not support the CA Librarian SEQ1,SEQ2 option
on the -INC statement. The SEQ1,SEQ2 option provides a range of sequence numbers from
the INCLUDE member to be included in the output file. The Expand Includes utility always
includes the entire member.
b. If an ++INCLUDE, -INC, or COPY statement is found, the utility searches the ENXINCnn
libraries for a member name.
c. If a member name is found, the utility incorporates the source file into the output file.
After reading all source records, the utility stops processing when the end of the file is
reached.
The following scenario is typical of why you use the Expand Includes utility:
You have a COBOL program with source that contains CA Panvalet ++INCLUDE statements or CA
Librarian -INC statements. You want to use the source as is, and you do not want to go into the
source file to change the ++INCLUDE or -INC statements to COPY statements.
In this situation, you would place the utility in the COBOL compile procedure, before the compile
step, to expand references to the CA Panvalet or CA Librarian members in the source code.
In order for the Expand Includes utility to replace a portion of a string, the replacing string in the
COPY statement must contain, at minimum, the first word of the string followed by a hyphen (-) as a
delimiter. Suppose you wanted to replace the original text above with this string:
04-May-2018 1061/1109
CA Endevor® SCM - 17.0
COPY DEF REPLACING DOG-
BY CAT-
Similarly, suppose you want to replace the original text with this string:
COPY DEF REPLACING DOG-HAS-
BY CAT-WITH-
If the replacing clause contains quotes around strings, the search will be for the presence of quotes
around a string. For example:
01 HEADER-RECORD3 COPY PAPHDR3 REPLACING '02' by '03'
If the COPY statement contains a level number and group name, the following rules are observed:
AND the format of the first non-comment line in the copied member is:
0x DATA-NAME-2 ...
AND the format of the first non-comment line in the copied member is:
0y DATA-NAME-2 ... (0x is different from 0y)
04-May-2018 1062/1109
CA Endevor® SCM - 17.0
THEN a new line will be written to the output containing just DATA-NAME-1, followed by the line
from the copy member:
0x DATA-NAME-1.
0y DATA-NAME-2 ...
Rule 3-- If the COPY statement contains a procedure label, AND the format of the COPY statement is:
PROCEDURE-LABEL. COPY MNO.
THEN a line will first be written to the output containing just procedure label:
PROCEDURE-LABEL.
Default Location mode, which is the default processing mode. In this mode, the source data set,
or input file, is identified by the ENXIN DD statement and the destination data set, or output file,
is identified by the ENXOUT DD statement.
Control Statement mode. In this mode, the utility is controlled by a set of EXPAND INCLUDES
requests that are specified in the ENXSCLIN DD statement.
The utility determines the processing mode by the presence of the ENXSCLIN DD statement in the
JCL. If the ENXSCLIN DD statement is allocated in the JCL, the utility executes using Control Statement
mode. Otherwise, the utility executes in Default Location mode.
The record length of the destination data set should be at least as large as the record length of
the source data set and at least as large as the largest record length of the INCLUDE data sets. If
either of these conditions is not met, a caution message is issued and the output records may be
truncated.
Note: The ENXIN and ENXOUT DD data sets can be only sequential, partitioned, or
CONWRITE resultant members within processors. You cannot use CA Librarian or CA
Panvalet data sets as input to the Expand Includes utility.
04-May-2018 1063/1109
CA Endevor® SCM - 17.0
When scanning for a match, the matching string must be separated from other strings with
spaces.
When strings are enclosed in quotes, the quotes are are included in the scan.
When strings are enclosed in quotes, the quotes are removed before scanning.
The expansion is processed the same as the COBOL II compiler processes COBOL II COPY
replacing syntax.
Librarian CCOPY
This is the default, but it is also selected by including a EN$CCOPY DD statement in the execution
JCL.
VSCOBOL COPY
To select this method, include a EN$COBOL DD statement in the execution JCL.
COBOL II COPY
To select this method, enable the option COPY_COBOL2_REPLACE on in the ENCOPTBL options
table.
04-May-2018 1064/1109
CA Endevor® SCM - 17.0
Checking the CA Endevor® SCM Defaults Table - During initialization, the Expand Includes utility
checks the CA Endevor® SCM Defaults Table to determine whether CA Librarian or CA Panvalet
support is active. The LIBENV= parameter indicates whether support is active and, if so, for which
application. If neither CA Librarian nor CA Panvalet is active, the utility issues an error message
and terminates immediately.
Embedding and Looping INCLUDE Statements - The Expand Includes utility expands embedded
INCLUDE statements. An embedded INCLUDE statement occurs when a member expanded by an
++INCLUDE, -INC, or COPY statement contains another ++INCLUDE, -INC, or COPY statement.
The utility also detects looping INCLUDE statements. A looping INCLUDE statement occurs when
one member includes another member which, in turn, includes the first member. In this situation,
the utility issues an error message and immediately stops processing.
Superset Support - The Expand Includes utility provides support for CA Panvalet Supersets as
follows:
1. If the INCLUDE Library is a CA Panvalet data set, the utility provides full superset support.
2. If the INCLUDE library is a partitioned data set, the utility provides limited support. The
utility ignores the superset name and expands only the member name. For example, assume
the source program contains the following statement:
++INCLUDE superset.member1
The Expand Includes utility expands the statement only by looking for member1 in the INCLUDE
libraries.
Security - The Expand Includes utility does not perform any security checking. The utility relies on
your site's system (RACF, CA Top Secret, CA ACF2) to enforce data set access.
Monitoring Components in the Expand Includes Utility - When using the Expand Includes utility in
a processor, both CA Librarian and CA Panvalet components have the ability to collect component
data for expand include utility or CONWRITE. Component monitoring is also available using
CONWRITE with PARM='EXPINCL(y)'.
04-May-2018 1065/1109
CA Endevor® SCM - 17.0
The utility checks the LIBENV= parameter in the CA Endevor® SCM Defaults Table to determine which
indicator to look for.
The Expand Includes utility also looks for COBOL COPY statements, if the EXPANDCOPY parameter
was specified in the JCL PARM= statement or if the OPTIONS EXPAND COPY STATEMENTS clause was
specified in the EXPAND INCLUDES request.
The format for COBOL COPY statements is similar. The member name must be on the same line as
the word COPY.
If the member name specified on the ++INCLUDE or COPY statement is invalid or cannot be found in
any of the INCLUDE libraries, the utility writes the invalid record to the destination file. The utility
then issues a caution message and continues to process the source file.
If the member name specified on the -INC or COPY statement is invalid or cannot be found in any of
the INCLUDE libraries, the utility issues an error message and terminates processing.
Remember that the Expand Includes utility does not support the CA Librarian SEQ1,SEQ2 option on
the -INC statement. The utility always includes the entire member.
04-May-2018 1066/1109
CA Endevor® SCM - 17.0
If the member name specified for the COPY statement is invalid or cannot be found in the INCLUDE
libraries, the Expand Includes utility ignores the error. The COPY statement is written as is to the
destination file. The error will most likely be detected by the compiler program.
Note: For examples of rules and formats, see COPY Statement Examples (see page 1061).
nn can be a two digit number between 00-99 inclusive, or two alphabetic characters in the following
series:
AA-AZ
BA-BZ
CA-CZ
DA-DZ
To resolve ++INCLUDE, -INC, or COPY statements, the utility searches up to 204 INCLUDE libraries.100
in numerical sequence followed by 104 in alphabetical sequence.
Note: In the ENXINCnn DD statement, the execution JCL must include at least one valid
ENXINCnn DD statement. In addition, the ENXINCnn DD statement cannot specify a
concatenated data set. Finally, the ENXINCnn DD statements can contain a combination of
partitioned and CA Panvalet or CA Librarian data sets.
04-May-2018 1067/1109
CA Endevor® SCM - 17.0
You do not need to begin the sequence numbers with 00 nor must you have a complete sequence.
For example, you can specify the following DD statements ENXINC04, ENXINC01, ENXINCBC in the
JCL. The Expand Includes utility searches the library named in statement ENXINC01 first, then the
library named in ENXINC04, then the library named in ENXINCBC.
The member name specified on the ++INCLUDE and -INC statements can be no longer than eight
characters. If the INCLUDE member name is greater than eight characters, the Expand Includes
utility truncates the name and issues a warning.
Both DD statements can refer to a sequential data set, a partitioned data set, or a partitioned data
set with an explicit member name.
The JCL that executes the Expand Includes utility in Default Location mode can be found in member
ENBXDLM1, in the JCL library iprfx.iqual.CSIQJCL.
You must specify a member name if you are using a partitioned data set--and that member name
must be explicit (that is, no wildcard). If the input file is a partitioned data set but an explicit member
has not been provided in the ENXIN DD statement, the utility checks the PARM= statement for a
member name.
If the execution JCL contains a PARM= statement that specifies a member name and a member name
is also included in the ENXIN DD statement, the utility ignores the member specified on the PARM=
statement.
04-May-2018 1068/1109
CA Endevor® SCM - 17.0
If Then
ENXIN DD is a sequential data set ENXOUT DD must be sequential or partitioned
data set with an explicit member name.
ENXIN DD is a sequential data set and ENXOUT You receive an error message.
DD is a partitioned data set without an explicit
member name
ENXIN DD is a partitioned data set and the ENXOUT DD can be either a sequential or
member is identified in the PARM= statement or partitioned data set.
in the ENXIN DD statement
ENXOUT DD is a partitioned data set and an The utility creates a member with the same name
explicit member name is not provided on that DD as the input member. The utility always replaces
statement the destination member.
ENXIN DD is a partitioned data set with no You receive an error message.
member specified, and no member is named in
the PARM= statement
ENXIN DD is a partitioned data set with an The PARM= member name is ignored.
explicit member name and the PARM= statement
contains a member name
Note: For more information about the Expand Includes SCL, see Expand Includes SCL (see
page 1071).
The JCL that executes the Expand Includes utility in Control Statement mode can be found in member
ENBXCSM1, in the JCL library iprfx.iqual.CSIQJCL.
04-May-2018 1069/1109
CA Endevor® SCM - 17.0
Specify a wildcarded member name in the FROM DSNAME MEMBER clause in the EXPAND
INCLUDES action.
If the execution JCL contains a PARM= statement that specifies a member name, in addition to the
control statements in the ENXSCLIN DD statement, the utility ignores the member specified on the
PARM= statement and issues a warning message.
If errors are found in the SCL, CA Endevor® SCM continues parsing the statements, but does not
process them. Results of the validation process are presented on the Expand Includes Control
Statement Summary Report.
JCL Parameter
The JCL PARM= statement is used for two purposes:
PARM= Parameter
The PARM= parameter appears as follows in the JCL:
PARM='ENBX1000member'
If you want to expand COBOL COPY statements, type the parameter as follows:
PARM='ENBX1000member,EXPANDCOPY'
The EXPANDCOPY portion of the parameter tells the Expand Includes utility to expand any COBOL
04-May-2018 1070/1109
CA Endevor® SCM - 17.0
The EXPANDCOPY portion of the parameter tells the Expand Includes utility to expand any COBOL
COPY statements found in the specified member.
Specifying a member in the PARM= parameter is optional. In the previous example, the member to
be processed is included. If you want to expand COPY statements but do not want to specify a
member, type the parameter shown as follows:
PARM='ENBX1000,EXPANDCOPY'
Note that you must type the leading comma in the parameter even if you do not specify a member
name.
Member Name
The variable member in the PARM= parameter specifies the name of the member to be processed.
The member name can be no longer than eight characters in length and must be explicit--you cannot
wildcard this value. Use only the following characters in the member name:
A-Z, 0-9, $, @, #
If the PARM= parameter is coded and the ENXSCLIN DD statement is present in the JCL, the member
name in the PARM= parameter is ignored.
If you are working with a partitioned data set in Default Location mode, you can specify a member
name in one of two places: the PARM= parameter or the ENXIN DD statement. If you do not enter a
member name in the PARM= statement, you must specify the name in the ENXIN DD statement. If
you do not specify a member name in either place, you receive an error message. If you are working
with a sequential data set in Default Location mode, you do not need to enter a member name.
You can enter as many EXPAND INCLUDES statements as necessary. These statements are specified in
the ENXSCLIN DD statement.
The Expand Includes utility parses and validates all requests before it begins executing them. If there
is a syntax error in any request or an error is found validating a request, none of the statements are
executed. The utility attempts to parse all of the control statements before terminating, however.
When the requests have been successfully parsed, the utility executes them. Requests are executed
as long as the highest return code is less than or equal to 12.
Note: If a member name is specified on the PARM= parameter and you have allocated the
ENXSCLIN DD statement, the Expand Includes utility ignores the member name in the
PARM= statement.
04-May-2018 1071/1109
CA Endevor® SCM - 17.0
Note: For more information about syntax conventions, see SCL Reference (https://docops.ca.
com/display/CE17/SCL+Reference).
EXPAND INCLUDES
The name of the action. You must code this clause.
FROM Clause
The FROM clause identifies the input, or source, data set. This clause is required. Specify either a
DDNAME or a DSNAME, but not both. The following table explains the FROM clause:
04-May-2018 1072/1109
CA Endevor® SCM - 17.0
MEMBER name
Identifies the member(s) to be processed from a partitioned data set. This clause is required.
The member name must meet the following specifications:
The member name can be no longer than eight characters. You can use a wildcard.
The MEMBER clause applies only if the input data set specified in the FROM DSNAME clause is
a partitioned data set. If the data set specified is sequential, the MEMBER clause is ignored
and a warning message issued.
If the member name is fully specified, the member must exist in the input data set. If the
member name is wildcarded, at least one member matching the wildcard criteria must exist in
the input data set. If the explicit member does not exist, or no matches can be found, you will
receive an error message.
TO Clause
The TO clause identifies the output, or destination, data set. This clause is required. Specify either a
DDNAME or a DSNAME, but not both. The following table explains the TO clause:
TO DDNAME ddname
Identifies the destination data set by DD name. Specify the name of a preallocated DD statement.
TO DSNAME dsname
Identifies the destination data set by data set name. Specify the name of an existing data set,
using standard CA Endevor® SCM naming conventions. If the data set name contains embedded
periods, enclose the name in quotation marks.
The data set referred to must be either sequential or partitioned. The data set record format can
be either fixed or variable. The record length must be at least as long as the record length of the
input data set and at least as large as the INCLUDE libraries associated with the ENXINCnn DD
statements. If the data set record length is not large enough for either condition, the Expand
Includes utility truncates the output records and issues a caution message.
MEMBER name
Identifies the name of the output member. This clause is optional.
The member name must meet the following specifications:
The member name can be no longer than eight characters and cannot be wildcarded.
The MEMBER clause applies only if the output data set specified in the TO DSNAME clause is a
partitioned data set and if the input data set is either a sequential data set or a partitioned
data set with an explicit member name (that is, not wildcarded). If the input data set is a
partitioned data set and the MEMBER clause contains a wildcarded member name, you will
receive an error message.
If the FROM DSNAME MEMBER clause contains a wildcarded member name or if the FROM
DSNAME is a partitioned data set and the FROM MEMBER clause is not specified, the TO
MEMBER clause cannot be specified. You cannot rename multiple output members. In this
situation, you will receive an error message.
04-May-2018 1073/1109
CA Endevor® SCM - 17.0
OPTIONS Clauses
The Expand Includes syntax contains two optional clauses:
REPLACE MEMBER
Tells the Expand Includes utility to replace an existing member in the output data set. This clause
applies only to partitioned data sets. If the destination data set is a sequential data set, this clause
is ignored.
If this clause is not specified and the member being created currently exists in the output data
set, the EXPAND INCLUDES action fails for that member. Processing continues for other members
associated with the request.
Execution Report
Contains information about the execution of each request.
If the utility is executing in Default Location mode, the report contains information about the
single request.
If the utility is executing in Control Statement mode, the utility generates detailed information
about each EXPAND INCLUDES request.
These reports are written to the ENXMSGS1 DD statement. If the execution JCL includes an
ENXMSGS2 DD statement, the utility writes the Expand Includes Summary Report to that file.
04-May-2018 1074/1109
CA Endevor® SCM - 17.0
Statement Number
The statement number associated with the EXPAND INCLUDES action. If the utility is running in
Default Location mode, the statement number is always 1.
Member Name
The name of the input member. This field is blank if the input file is a sequential data set.
Return Code
The return code associated with the EXPAND INCLUDES request for the data set or member.
04-May-2018 1075/1109
CA Endevor® SCM - 17.0
04-May-2018 1076/1109
CA Endevor® SCM - 17.0
CA Panvalet Libraries
The maximum number of CA Panvalet libraries that CA Endevor® SCM can open at one time is 16.
Therefore, the number of open data sets in one ANALYZE statement is restricted to 16. There is no
limit to the number of ANALYZE statements you can use, however. If you have more than 16 CA
Panvalet libraries, use a second ANALYZE statement to scan the additional libraries.
The analysis phase of the conversion process produces a reference data set that contains a list of
members. These members have been analyzed for specific information; analysis is done
alphabetically. During this phase, the conversion process identifies members that are supersets as
well as members that reference supersets. Appropriate messages are returned when the list is
generated, as shown in the following table:
Member Message
Is a superset CAE$0003 MEMBER member name IS A
SUPERSET
Is not a superset No message
References a member that has already been analyzed and CAE$0004 MEMBER member name
is a superset REFERENCES
To illustrate how the conversion process handles supersets, assume you have a file with 26 members,
A-Z. The members are analyzed and messages are issued as follows (see the previous table to match
the message with the message number):
04-May-2018 1077/1109
CA Endevor® SCM - 17.0
Note: When Member Z is analyzed, the only message issued indicates that the member is a
superset. No message is issued indicating that Member D references Member Z. CA
Endevor® SCM does not “backtrack” to issue a message when a previously referenced
superset is analyzed.
Analyze Phase
This section describes the first phase of the conversion process that analyzes the members in your
inventory to identify the following:
INCLUDE members
COPY members
This analysis is performed by the CA Endevor® SCM Inventory Analyzer, which is invoked by the
conversion job stream. The conversion job stream consists of four steps, briefly described as follows:
1. Delete SCL output data sets. In this step, existing output data sets are deleted so new ones
can be created.
2. Build reference data set. In this step, a list of analyzed members is created that will be used as
input in the next step.
3. Identify INCLUDE and COPY members, and build SCL. In this step, INCLUDE and COPY
members are identified using the information generated in the previous step. Load SCL is
created for input into CA Endevor® SCM.
4. Identify superset members. In this step, superset member and unresolved members
(members referenced but not found) are identified.
Submit the job stream for execution when all information has been entered for all four steps.
The conversion job stream is contained in member ENJSUCNV in the JCLLIB provided on the
04-May-2018 1078/1109
CA Endevor® SCM - 17.0
The conversion job stream is contained in member ENJSUCNV in the JCLLIB provided on the
installation tape.
Important! Throughout the conversion job stream, there are several statements that begin
with the words ESTABLISH TYPE. These statements are the rules used by the CA Endevor®
SCM Inventory Analyzer to identify members that contain INCLUDE or COPY statements
and to classify the members with a CA Endevor® SCM type. These rules are the only rules
needed for the conversion process. Do not change these rules.
Element Classification
In Step 3 of the conversion job stream, CA Endevor® SCM location and inventory information is
designated for the members in the reference data set.
You identify the CA Endevor® SCM environment, system, subsystem, and, optionally, processor
group to be assigned to each member. The inventory locations must be defined to CA Endevor®
SCM. You must know how you will classify the members before you begin the conversion process.
If CCIDs are required, you must also specify a CCID to be associated with the element.
CA Endevor® SCM elements require a type. The conversion job stream identifies the element type
to be assigned to the member.
The job stream takes the language attribute associated with the CA Panvalet or CA Librarian
member. That attribute is prefixed with I, if it is an INCLUDE statement or C, if it is a COPY
statement. The entire value becomes the CA Endevor® SCM element type.
For example, if the CA Panvalet language is COBOL and the member is an INCLUDE, the type
assigned is ICOBOL.
Note: If you are a CA Librarian user, there may be members in your library that do not
have a language associated with them. Check the SCL that is generated by the conversion
job stream. If no language is assigned, one of two TYPE values appears:
PROC Definition
This section describes the PROC definition portion of conversion job stream and the variables for
which you need to provide values before submitting the job.
The following JCL shows the PROC definition portion of the conversion job stream:
// (JOBCARD)
//*
//*********************************************************************
//* THIS JCL MUST BE TAILORED PRIOR TO SUBMITTING THIS JOB *
//* *
//* 1. CHANGE TDISK TO A UNIT NAME FOR WORK DASD *
//* FOR BEST PERFORMANCE, SPECIFY A VIO DEVICE *
04-May-2018 1079/1109
CA Endevor® SCM - 17.0
//* FOR BEST PERFORMANCE, SPECIFY A VIO DEVICE *
//* *
//* CHANGE iprfx.iqual TO YOUR CA Endevor® SCM INSTALL PREFIX *
//* *
//* *
//* 2. CHANGE PDISK TO A UNIT NAME FOR DATA SETS WHICH *
//* WILL CONTAIN CA Endevor® SCM LOAD SCL STATEMENTS USED FOR *
//* INPUT INTO THE CA Endevor® SCM LOAD UTILITY JOB *
//* *
//* CHANGE PVOLSER (OR REMOVE VOL=SER=PVOLSER) TO A VALID *
//* VOLUME SERIAL NUMBER *
//* *
//* CHANGE UPRFX.UQUAL TO THE APPROPRIATE INDEX LEVELS *
//* AT YOUR SITE *
//* *
//* 3. TAILOR THE THREE LINES THAT CONTAIN THE TEXT *
//* 'DSN1' 'DSN2' 'DSN3' TO REFLECT THE ACTUAL LIBRARY *
//* NAMES FROM WHICH YOU ARE CONVERTING. *
//* *
//* *
//* 4. ON THE ASSIGN STATEMENT USED IN STEP TWO, SPECIFY *
//* THE ACTUAL ENVIRONMENT, SYSTEM, SUBSYSTEM, STAGE ID *
//* AND CCID VALUES THAT ARE TO BE USED TO CONSTRUCT THE *
//* LOAD UTILITY SCL. *
//* *
//*********************************************************************
//ANALYZE PROC
//*
//C1BM7000 EXEC PGM=NBURC1,PARM=C1BM7000
// DYNAMNBR=1500,REGION=4096K
//*
//CONLIB DD DSN=iprfx.iqual.CSIQLOAD,DISP=SHR
//*
//C1TPDD01 DD UNIT=tdisk,SPACE=(CYL,3),
// DCB=(RECFM=VB,LRECL=260,BLKSIZE=6160)
//C1TPDD02 DD UNIT=tdisk,SPACE=(CYL,5),
// DCB=(RECFM=VB,LRECL=260,BLKSIZE=6160)
//C1TPLSIN DD UNIT=tdisk,SPACE=(CYL,3),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160)
//C1TPLSOU DD UNIT=tdisk,SPACE=(CYL,5)
//C1PLMSGS DD SYSOUT=*
//*********************************************************************
//* OUTPUT DATA SETS *
//*********************************************************************
//C1MSGS1 DD SYSOUT=*
//C1SUMARY DD SYSOUT=*
//C1PRINT DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171)
//SYSABEND DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//BSTERR DD SYSOUT=*
// PEND
Tailor this JCL by providing values for all occurrences of the following variables:
iprfx
Highest-level qualifier used to assign data set names for installation files at your site.
iqual
Second-level qualifier used to assign data set names for installation files at your site.
tdisk
Unit name for temporary disk data sets.
04-May-2018 1080/1109
CA Endevor® SCM - 17.0
//STEP1 EXEC PGM=IDCAMS
//*********************************************************************
//* DELETE SCL OUTPUT DATA SETS *
//*********************************************************************
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE uprfx.uqual.INCL.SCLSTMTS
DELETE uprfx.uqual.NONINCL.SCLSTMTS
SET MAXCC = 0
The Load SCL created in Step 3 of the conversion job stream is written to one of the following data
sets:
uprfx.uqual.INCL.SCLSTMTS
uprfx.uqual.NONINCL.SCLSTMTS
Each time you run this job stream, new data sets are created. Step 1 deletes the existing data sets so
the new data sets can be created without a problem.
uprfx
Highest-level qualifier used to assign data set names for CA Endevor® SCM user files at your site.
uqual
Second-level qualifier used to assign data set names for CA Endevor® SCM user files at your site.
04-May-2018 1081/1109
CA Endevor® SCM - 17.0
LIB = COPY.
ESTABLISH TYPE REMAINDR GROUP THATSALL WHEN
PAN = '' AND LIB = ''.
DEFINE PAN INCLUDE WHEN
'&C1FDSN$IO'. = 'PAN'
AND
SOURCE TEXT CONTAINS
'++INCLUDE' IN COLUMN 8 INVOKE EXIT=C1BM7CAE
.
DEFINE LIB INCLUDE WHEN
'&C1FDSN$IO'. = 'LIB'
AND
SOURCE TEXT CONTAINS
'-INC' IN COLUMN 1 INVOKE EXIT=C1BM7CAE
.
DEFINE LIB COPY WHEN
'&C1FDSN$IO'. = 'LIB'
AND
'&C1FDSN$LANG'. = 'CBL'
AND
SOURCE TEXT CONTAINS
' COPY ' IN COLUMNS 7 THROUGH 68
INVOKE EXIT=C1BM7CAE WITHOUT
'*' IN COLUMN 7 LINE CURRENT
.
//*
//*
Step 2 creates a list of members that have been analyzed to determine whether they are INCLUDE
members, COPY members, supersets, or members that reference supersets. You indicate the names
of the data sets to be analyzed.
If more than one FROM data set is specified and if the same member exists in more than one data
set, the program takes the first occurrence of the member. The analyzed members are listed
alphabetically, as detail records in a reference data set. The reference data set is used as input for the
next step in the conversion process.
tdisk
Unit name for temporary disk data sets.
Two types of records are created in this step: a header record and detail records. The header record
assigns symbolic names to the data in the detail records. Each detail record contains the information
listed as follows, in the order shown, for each unique occurrence of the member:
Member name
04-May-2018 1082/1109
CA Endevor® SCM - 17.0
Language
Comment
The following example illustrates a typical record in the reference data set:
BEND--What happens--OTH
//STEP3 EXEC ANALYZE
//*********************************************************************
//* IDENTIFY INCLUDE AND COPY MEMBERS, BUILD LOAD SCL *
//*********************************************************************
//BSTPUNCH DD DSN=&&BSTPUNCH.,DISP=(OLD,PASS)
//INCLMBRS DD DSN=uprfx.uqual.INCL.SCLSTMTS,DISP=(,CATLG),
// UNIT=pdisk,vol=ser=pvolser,SPACE=(TRK,(3,2),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160,DSORG=PS)
//PGMMBRS DD DSN=uprfx.uqual.NONINCL.SCLSTMTS,DISP=(,CATLG),
// UNIT=pdisk,vol=ser=pvolser,SPACE=(TRK,(3,2),RLSE),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160,DSORG=PS)
//BSTIPT01 DD *
*
SET ASSIGN
ENV = 'ENVNAME'
SYS = 'SYSNAME'
SBS = 'SBSNAME'
04-May-2018 1083/1109
CA Endevor® SCM - 17.0
SBS = 'SBSNAME'
CCID = 'CCID' .
*
SET REFERENCE DDNAME BSTPUNCH.
*
ANALYZE MEMBER *
FROM DSNAME 'DSN1' 'DSN2' 'DSN3'
.
*
//BSTRULES DD *
DEFINE INCLUDE SUPERSET WHEN
'&CAESUPER'. EQ 'Y'
.
ESTABLISH TYPE COPY GROUP NOPROC WHEN
'&CAECOPY'. = 'Y' AND INCLUDE NOT = SUPERSET
.
ESTABLISH TYPE INCLUDE GROUP NOPROC WHEN
'&CAEINC'. = 'Y' AND INCLUDE NOT = SUPERSET
.
//BSTMODEL DD *
%DDNAME=INCLMBRS,COND=SUCCESS
LOAD MEMBER &C1MEMBER
FROM DSNAME '&C1FDSN'.
TO ENVIRONMENT &ENV.
SYSTEM &SYS.
SUBSYSTEM &SBS.
TYPE &C1ELTYPE(1.,1)&CAELANG(1.,7)
OPTIONS CCID '&CCID'.
COMMENT '&CAEDESC'.
.
%DDNAME=PGMMBRS,COND=FAILURE
LOAD MEMBER &C1MEMBER
FROM DSNAME '&C1FDSN'.
TO ENVIRONMENT &ENV.
SYSTEM &SYS.
SUBSYSTEM &SBS.
TYPE &CAELANG(1.,8)
OPTIONS CCID '&CCID'.
COMMENT '&CAEDESC'.
Step 3 identifies the INCLUDE members and COPY members within the data sets indicated. This step
also assigns CA Endevor® SCM location and inventory information to the members and creates the
SCL used to load members into CA Endevor® SCM.
Each SCL statement is written to one of two data sets, depending on whether the member is an
INCLUDE or COPY member or neither:
If the member is an INCLUDE or COPY member, it is written to the data set uprfx.uqual.INCL.
SCLSTMTS.
If the member is not an INCLUDE or COPY member, it is written to the data set uprfx.uqual.
NONINCL.SCLSTMTS.
uprfx
Highest-level qualifier used to assign data set names for CA Endevor® SCM user file at your site.
uqual
Second-level qualifier used to assign data set names for CA Endevor® SCM user files at your site.
04-May-2018 1084/1109
CA Endevor® SCM - 17.0
pdisk
Unit name for permanent disk data sets. These data sets will contain CA Endevor® SCM Load SCL
statements.
pvolser
Volume serial number of the disk. Either enter a valid volume serial number or delete the
parameter VOL=SER=PVOLSER.
ENVNAME
Environment name.
SYSNAME
System name.
SBSNAME
Subsystem name.
CCID
CCID to be associated with the element.
DSN1, DSN2,...DSNn
The name(s) of the data sets you want scanned. Use the same data set names you coded in Step
2.
Note: You must enter the data set names in the same sequence as they were entered in
Step 2.
CA Endevor® SCM creates SCL for the CA Endevor® SCM Load utility. The SCL is formatted according
to one of the two output model definitions that are included in this step of the conversion job
stream. An output model definition is simply a template that defines the format of the load
commands.
The first output model definition is used for members that are INCLUDE or COPY members. The
second output model definition is used for members that are not INCLUDE or COPY members.
04-May-2018 1085/1109
CA Endevor® SCM - 17.0
Step 4 identifies those members that are supersets and any members that are unresolved. A member
is considered unresolved when it has been referenced as part of an INCLUDE statement but cannot
be found.
04-May-2018 1086/1109
CA Endevor® SCM - 17.0
For this step, you need only code the data set names you used in Step 2 and Step 3. You must enter
the data set names in the same sequence as entered in the previous steps.
For unresolved members, CA Endevor® SCM writes messages to the Execution Log, identifying the
member by member name.
For superset identification, CA Endevor® SCM writes messages to one of two DDnames, depending
upon whether a member is a superset.
If the member is not a superset, the following message is written to DDname NOTSUPER:
MEMBER member-name IN DATASET dataset-name IS NOT A SUPERSET MEMBER.
Load Phase
The second phase of the conversion process loads the members classified in the first phase into CA
Endevor® SCM.
The first phase of the conversion process classified members according to whether the member was
an INCLUDE or COPY statement and created Load SCL. The Load SCL was then written to one of two
data sets, depending on whether the members were INCLUDE or COPY members, or neither. The next
step in the conversion process is to load these members directly into CA Endevor® SCM, which is
done using the CA Endevor® SCM Load utility.
Load Utility
The CA Endevor® SCM Load utility allows you to load one or more members, from data sets external
to CA Endevor® SCM, directly into any stage that is defined within a CA Endevor® SCM environment.
You do not need to reassemble or recompile your programs. And, you can date/time stamp--or
footprint--all corresponding library members in your source, object, and load libraries as the
members are loaded.
Note: The Load utility JCL is provided on the installation tape, in member BC1JLOAD of the
JCLLIB.
The actual load requests have already been generated, using the formats provided in Step 3 of the
conversion job stream, and written to a data set. You need only to tailor the JCL and submit the job
for execution.
iprfx
Highest-level qualifier used to assign data set names for installation files at your site.
iqual
04-May-2018 1087/1109
CA Endevor® SCM - 17.0
iqual
Second-level qualifier used to assign data set names for installation files at your site.
uprfx.uqual.INCL.SCLSTMTS
The name of the data set that contains the load statements (output from phase 1 of the
conversion process).
The following describes the report name and when the report is produced:
Validate Phase
The third phase of the conversion process checks if the members have been loaded correctly loaded
into the CA Endevor® SCM.
After you have run the Load utility, you should check to be sure that all members were loaded into
CA Endevor® SCM correctly. Use the Member Validation Program to validate that all of the members
in a single data set have been loaded and exist in a specific CA Endevor® SCM environment.
To achieve the best results, the Member Validation Program must be run immediately after you have
loaded a data set's members into CA Endevor® SCM. The program produces a report that provides
specific information about each member in the data set. The accuracy of the report can be affected
by subsequent actions against the elements.
04-May-2018 1088/1109
CA Endevor® SCM - 17.0
The Member Validation Program assumes that the CA Endevor® SCM element name is the same as
the data set member name. The program does not support members that were renamed when
placed into CA Endevor® SCM.
0
All members in the source data set were found in the CA Endevor® SCM environment specified.
4
One or more members were not found in the environment specified.
12
The Member Validation Program encountered an error.
Note: The Member Validation Program execution JCL is provided on the install tape in
member ENBRVDSN in the JCLLIB.
'ENBRVDSN environment_name'
The CA Endevor® SCM environment that will be searched for members. If you do not code this
parameter, or the value is invalid, you receive an error message.
Specify an up to eight character, valid CA Endevor® SCM environment name.
CONLIB DD
04-May-2018 1089/1109
CA Endevor® SCM - 17.0
CONLIB DD
Standard JCL statement.
Change IPRFX and IQUAL to the qualifiers you are using for your site.
ENVMSGS1
The destination of the Member Validation Report. The DD statement usually allocates a SYSOUT
data set.
No tailoring required.
ENVDSN00
The data set that is to be validated.
Specify the name of a data set (source.dataset.name) generated by the conversion job stream.
The data set must be partitioned, CA Panvalet, or CA Librarian.
The Member Validation Report classifies each member in the data set into one of three categories:
The member was found as an element and the element was loaded into CA Endevor® SCM from
the source data set.
The member was found as an element but the element was not loaded from the source data set.
The report displays every occurrence of the element. In most situations, only one of the elements is
valid. The other elements will be marked with the following message:
Found . . . but not loaded from the source data set
04-May-2018 1090/1109
CA Endevor® SCM - 17.0
Load Utility
Contents
The CA Endevor® SCM Load Utility enables you to load one or more members (elements), from data
sets external to CA Endevor® SCM, directly to any stage that is defined within a CA Endevor® SCM
environment. Using this utility, you can quickly populate CA Endevor® SCM environments without the
need to reassemble or recompile your programs. And, you can date/time stamp--or footprint--all
corresponding library members in your source, object, and load libraries as the members are loaded.
Security is invoked when the Load Utility is executed. If using ESI, a PRIMARY_OPTIONS call is issued.
For this ESI call, the MENUITEM is LOAD.
Before using the CA Endevor® SCM Load Utility, the inventory structures that you want to populate
within CA Endevor® SCM must be defined.
Note: For more information about defining inventory structures, see Administrating (see
page 36).
This section describes the CA Endevor® SCM Load Utility request syntax, detailing the structure of and
rules concerning the LOAD MEMBER command. The final section provides a working example of the
Load process, on a step-by-step basis.
LOAD requests can be created manually, using the LOAD request syntax, or can be generated by the
CA Endevor® SCM Inventory Analyzer as part of the analysis process. The method used is at your
discretion; the results of the load processing are the same.
The CA Endevor® SCM Load Utility is simple to operate and involves two basic steps:
04-May-2018 1091/1109
CA Endevor® SCM - 17.0
LOAD MEMBER FINARP00 THRU FINARP99
FROM DSNAME 'PROD.SRCLIB'
TO ENVIRONMENT 'DEMO' SYSTEM 'FINANCE' SUBSYSTEM 'ACCTREC'
TYPE 'COBOL' STAGE 'P'
OPTIONS CCID 'LOAD'
COMMENT 'AUTOMATED CA SCMMF IMPLEMENTATION
PROCESSOR GROUP 'COBNBL01'
FOOTPRINT 'PROD.LOADLIB' .
This request tells the Load Utility to perform the following actions:
Load the members to the CA Endevor® SCM location specified by the TO information.
Create version 1.0 of an element in CA Endevor® SCM, for each member that matches the criteria
specified.
Associate with each element the indicated CCID, comment, and processor group.
Footprint each applicable member (that is, member for which a match is found in the footprint
library) in the library specified by the FOOTPRINT clause.
After all LOAD requests are coded, and before they are executed, CA Endevor® SCM validates both
the syntax and the content of each request. Syntax validation ensures that the request syntax is
correct. Content validation ensures that the data sets specified do exist and that the CA Endevor®
SCM location specified is valid.
The first two reports indicate syntax and data errors, respectively. The last two reports provide detail
and summary information for each request in the input data set.
If a member specified in the LOAD request is found in the CA Endevor® SCM TO location indicated,
creating duplicate members, the LOAD request for that member is bypassed. The occurrence of
duplicate members can be caused by overlapping Load requests; that is, when two requests involve
one or more of the same members. Occasionally, duplicate members may be the result of repeated
execution of the same Load syntax. Duplicate member warning messages are issued when either
situation occurs.
04-May-2018 1092/1109
CA Endevor® SCM - 17.0
The ACTION statement is always LOAD MEMBER. This is the only statement that the Load Utility
executes.
SET statement establishes default values for subsequent action statements. These statements are
never executed by the Load Utility.
CLEAR statements clears the information designated by a related SET statement. These
statements are never executed by the Load Utility.
The remainder of this section illustrates the LOAD statement syntax and explains all required and
optional clauses within the statement. A brief overview of the reports produced by the Load Utility is
provided also. Read this section carefully to gain a full understanding of the syntax. Learning and
using this syntax can be an invaluable and powerful tool.
04-May-2018 1093/1109
CA Endevor® SCM - 17.0
Note: If you want the member(s) in this FROM data set to be footprinted, you must code
this data set name in the FOOTPRINT clause.
Indicates the CA Endevor® SCM location to which the member(s) will be loaded. If you do not provide
(all) TO information here, a SET TO clause with the required data must have been previously coded.
You must specify full environment, system, subsystem, type, and/or processor group names, up to
eight characters each; you cannot use a name mask or a place holder when defining any portion of
the CA Endevor® SCM location.
STAGE is optional in the TO field. If you do not specify a stage ID in this clause or in the SET TO
statement, the ID for Stage 2 is used.
04-May-2018 1094/1109
CA Endevor® SCM - 17.0
OPTIONS
CCID ccid
You can specify a CCID to group related modules that are being loaded, for reporting
purposes. CCIDs can be up to 12 characters in length.
COMMENT comment
You can specify a comment to further define the member(s) being loaded. Comments can be
up to 40 characters in length, and must always be enclosed in quotes.
Be sure the processor group you code is a valid processor group within the element type record
being loaded. Otherwise, you receive an error message.
If you leave this field blank, the system defaults to the processor group defined on the element's
type record.
Important! The footprint DSN clause should not be either a base or delta library.
Set Statements
SET statements are global default statements that establish values for subsequent request
statements. SET statements are never executed.
A SET statement establishes default values for keyword parameters, such as FROM or TO. If
information is required and not specifically coded within a LOAD request, a corresponding SET
statement must precede that request. If you code the LOAD statement first, without required
information, you receive an error message.
04-May-2018 1095/1109
CA Endevor® SCM - 17.0
References are made throughout this section to the “actual LOAD statement.” An actual LOAD
statement begins with the word LOAD and ends with a period, and includes all data between these
two items. If you code a SET statement within the actual LOAD statement, you receive an error
message.
You code specific values in the actual LOAD statement, which override the corresponding values
in the SET statement.
CA Endevor® SCM encounters another, like SET statement, which overrides the existing SET
statement.
CA Endevor® SCM encounters a CLEAR statement for that particular SET statement.
The following SET statements can be used with the LOAD action:
SET FROM DSNAME
SET TO
SET OPTIONS
SET FOOTPRINT
SET TO Statement
The syntax of the SET TO statement is shown next:
SET TO ENVIRONMENT env-name
SYSTEM sys-name
SUBSYSTEM subsys-name
TYPE type-name
[STAGE stage-id].
The information specified in the SET TO statement indicates the CA Endevor® SCM location to which
all members in the subsequent LOAD requests will be loaded. This location applies until another SET
TO statement, a CLEAR ALL statement, or a CLEAR TO statement is encountered, or until processing
ends. Or, you can override any portion (or all) of the CA Endevor® SCM location within the actual
LOAD statement.
04-May-2018 1096/1109
CA Endevor® SCM - 17.0
You must specify full environment, system, subsystem, type, and/or processor group names; you
cannot use a name mask or a place holder when defining any portion of the CA Endevor® SCM
location. If you do not specify a stage ID in the SET TO clause or in the actual LOAD statement, the
system uses the ID for Stage 2.
With the exception of the stage ID, any location information you do not specify in a SET TO clause
must be coded in the LOAD request.
The SET OPTIONS statement allows you to specify that a particular CCID, comment (enclosed in
quotes), and/or processor group be applied to all members to be loaded, for all subsequent LOAD
requests. These options are in effect until another SET OPTIONS statement, a CLEAR ALL statement,
or a CLEAR OPTIONS statement is encountered, or until processing ends. Or, you can override any of
the SET options by coding a different, corresponding value(s) in the actual LOAD statement.
OPTIONS are not required in LOAD actions. Therefore, you are not required to have previously coded
a SET OPTIONS statement if you did not specify OPTIONS information in the LOAD request.
CA Endevor® SCM interprets the clause as having no library indicated. If no library is designated,
footprinting cannot take place. And, the SET FOOTPRINT statement cannot be in effect because the
FOOTPRINT clause is specified in the LOAD command, thereby overriding that statement.
04-May-2018 1097/1109
CA Endevor® SCM - 17.0
Footprint information is not required in Load actions. Therefore, you are not required to have a SET
FOOTPRINT statement if you did not specify footprint information in the LOAD request.
Clear Statements
A CLEAR statement clears the information that is designated by a SET statement. When you are
working with a series of requests and need to remove the data established in a SET statement, simply
code a parallel CLEAR statement. The CLEAR statement remains in effect until a new, related SET
statement is encountered or until processing ends.
CLEAR statements apply only to SET statements. Similar information entered in a LOAD request is not
affected by a CLEAR statement.
The following CLEAR statements can be used with the LOAD action:
CLEAR ALL
CLEAR FROM
CLEAR TO
CLEAR OPTIONS
CLEAR FOOTPRINT
CLEAR ALL
CLEAR ALL clears all information established by all previous SET statements. Be sure that you
either specify all required information in all subsequent LOAD statements or code new SET
statements for all required information.
CLEAR FROM
CLEAR FROM clears all SET FROM information previously coded.
CLEAR TO
CLEAR TO clears all SET TO information previously coded.
CLEAR OPTIONS
CLEAR OPTIONS clears all SET OPTIONS information previously coded.
CLEAR FOOTPRINT
CLEAR FOOTPRINT clears all SET FOOTPRINT information previously coded.
04-May-2018 1098/1109
CA Endevor® SCM - 17.0
Note: For examples on their use, see Example of the Load Utility Process (see page 1101).
Several CA Endevor® SCM panels and reports, mostly related to footprints, reflect the use of the CA
Endevor® SCM Load Utility to populate environments. A load indicator ── the field LD which appears
as part of the footprint ── indicates whether a particular element/member was loaded into CA
Endevor® SCM (Y, yes) or generated within CA Endevor® SCM (blank, no).
The panels affected include the CA Endevor® SCM-Footprint Display, as well as any other panels that
show footprint information.
The log lists all requests coded, including requests containing invalid data. In addition, any syntax
errors found by the parser are flagged. A brief explanation of the error appears on the line
immediately following the error, denoted by the prefix BSTPPARS.
For each invalid request, the report lists the LOAD request number (automatically assigned by the
system), the invalid data, and the total number of data errors found in that request. A final line at the
end of the report indicates the total number of requests that contained errors.
04-May-2018 1099/1109
CA Endevor® SCM - 17.0
This report expands the LOAD request, reformatting the clauses into a standard structure--which is
the structure shown in the “Load Request Syntax” section. All relevant SET information is applied to
the LOAD statement, and appears in the printed syntax.
The remainder of the report, for each request, lists informational messages that relate what happens
as each step of the load process occurs. Be sure to read these messages, as error and problem
conditions are noted here also.
Note: Especially when processing large quantities of LOAD requests and/or members, you
should use this report in conjunction with the CA Endevor® SCM Load Execution Summary.
Using this combination of reports facilitates looking for, and finding, those requests that
may contain processing errors.
The total number of members in the request that were successfully loaded.
The total number of members in the request that failed the loading process.
The number of members in the request that were footprinted. (Note that only members that are
successfully loaded can be footprinted.)
The number of successfully loaded members that failed the footprinting process.
It is beneficial to use this report in combination with the CA Endevor® SCM Load Execution Report.
You can use the Execution Summary to quickly find any requests with errors, then refer back to the
more detailed Execution Report to determine where and when the error occurred.
04-May-2018 1100/1109
CA Endevor® SCM - 17.0
In the following example, you enter a LOAD request using the THROUGH clause, to load a range of
members (FINARP00 through FINARP99) into CA Endevor® SCM:
LOAD MEMBER FINARP00 THROUGH FINARP99
FROM DSNAME 'PROD.SRCLIB'
TO ENVIRONMENT 'DEMO' SYSTEM 'FINANCE' SUBSYSTEM 'ACCTREC'
TYPE 'COBOL' STAGE 'P'
OPTIONS CCID 'LOAD '
COMMENT 'AUTOMATED CASCMMF IMPLEMENTATION '
PROCESSOR GROUP 'COBNBL01 '
FOOTPRINT 'PROD.LOADLIB'
.
These members are being loaded into the DEMO environment, Stage P, Finance system, ACCTREC
subsystem, and are assigned a type of COBOL. Each member has both a CCID and a comment, and is
associated with the processor group COBNBL01. The members are being loaded from data set PROD.
SRCLIB and will be footprinted in the load library PROD.LOADLIB.
Quotes are optional for data sets unless you have embedded blanks or periods within the literal.
The data set names in this example contain embedded periods; therefore, these values are
enclosed in quotes.
If no processor group is specified, the member(s) is associated with the default processor group
for the type specified.
Members can be footprinted in source and object libraries as well as load libraries. Simply enter
the appropriate library names in the FOOTPRINT clause.
04-May-2018 1101/1109
CA Endevor® SCM - 17.0
//CONLIB DD DSN=iprfx.iqual.CSIQLOAD,DISP=SHR
//C1BMLIN DD *
(PLACE INPUT DATA HERE)
//C1BMLLOG DD SYSOUT=*
//C1BMLSYN DD SYSOUT=*
//C1BMLDET DD SYSOUT=*
//C1BMLSUM DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//
//* BC1JLOAD
The Load Utility Reports help you review the processing of your LOAD requests. With these reports,
you can pinpoint problems and errors before you begin working with CA Endevor® SCM. Interpreted
and used properly, the load reports enable you to load accurate and valid data.
The following table summarizes which reports are produced under which circumstances, where B
indicates that the report is produced:
Report/Condition Syntax Errors Invalid Data Syntax Errors and Syntax and Data
Only Only Invalid Data Correct
CA Endevor® SCM Load B B B B
Execution Log
CA Endevor® SCM Data Not B Not produced Not produced
Validation Report produced
CA Endevor® SCM Load Not Not Not produced B
Execution Report produced produced
CA Endevor® SCM Load Not Not Not produced B
Execution Summary produced produced
These request numbers are particularly useful when looking for requests containing incorrect data.
You can use the CA Endevor® SCM Load Execution Log in conjunction with the CA Endevor® SCM Data
Validation Report to pinpoint those requests causing problems.
04-May-2018 1102/1109
CA Endevor® SCM - 17.0
In the following report, the LOAD request was loaded successfully. The LOAD syntax appears first, in
the order in which it was coded. Several informational messages follow, one for each member to be
added in the LOAD request. Each message indicates that the member requested has been created,
and lists the version number and stage associated with the member. The final message, which is the
last line of the report, indicates that the load processing for the request was completed successfully.
If there had been an error in the syntax, however, a report similar to the one illustrated next would
have been produced.
In the following example, the LOAD request contains a syntax error in the FROM DSNAME clause. The
next line indicates the error; note the line beginning with BSTPPARS.
In this case, no comment was specified although the keyword COMMENT was coded. The system
looked for a comment and applied the next word it found in the syntax--the word FROM, based on
the FROM DSNAME entry immediately following the OPTION COMMENT clause. The FROM DSNAME
command then is misread. Because the from DSNAME command requires both words (FROM and
DSNAME) in the clause, the system considers this an error in command wording and therefore an
error in syntax.
Note, in the last line of the report, that the processing for this request failed and execution of the job
terminated. Even if several other LOAD requests with no errors had been included in the input data
set, this one error still would prevent execution of the job.
Assume that an incorrect system name (“BADSYS”) was specified. a CA Endevor® SCM Data Validation
Report would be produced.
The first line indicates the number assigned to the LOAD request. Use this number to go back to the
CA Endevor® SCM Load Execution Log to find the request and check your data. In this example, only
one LOAD request has been entered; therefore the request number is 1.
The second line notes the error. In the example, this message indicates that the system specified in
the request does not exist. If there were additional data errors in this request, they too would be
listed here.
The third line indicates the total number of errors in this request only. Only one error exists in the
example, as is reflected by the message. If two data errors existed in the request, the request total
would reflect that fact.
The final line of the report lists the total number of requests that contained errors. Again, because
04-May-2018 1103/1109
CA Endevor® SCM - 17.0
The final line of the report lists the total number of requests that contained errors. Again, because
the example contains only one request, the DATA REPORT FINAL TOTAL is 1.
The LOAD request has been expanded and reformatted to fit the standard structure (shown in the
“Load Request Syntax” section). No SET information was coded for this request. If SET information
had been coded, it would appear in the appropriate clauses in the syntax.
Note the informational messages following the request. Details about processing for each member
are listed; in the example, each step of the process for every member was successful. Be sure to read
these messages carefully, as error and problem conditions are noted here as well as informational
messages.
This report summarizes the results of processing the requests in the input data set, and provides the
following information for every request (by request number):
The return code for the request. In this example, the return code is 0000, which indicates that
processing was successful.
The total number of members requested in the LOAD request. In this example, a range of
members was requested, resulting in a total of 5 members to be loaded.
The total number of members successfully loaded. In this example, all 5 members requested
were successfully loaded.
The total number of members not loaded, due to an error. In this example, no members failed
processing.
The number of members for which footprinting was attempted. Footprinting is attempted only
for those members that were loaded successfully and for which a FOOTPRINT clause (or SET
FOOTPRINT statement) was coded. In this example, footprinting was attempted for all 5
members, as the previous criteria was met for each member. Therefore, footprints attempted
reflects a total of 5.
The number of members for which footprinting failed. Again, this total is based on the number
of members eligible for footprinting. In this example, no members failed the footprinting process.
04-May-2018 1104/1109
CA Endevor® SCM - 17.0
For example, assume that the Load Utility is loading a data set that contains linkage editor control
statements and the FOOTPRINT statement is pointing to the associated load module library. In this
case the Load Utility attempts to footprint the member in the load module library that has the same
name as the input element name. However, if the linkage editor control statements contain a NAME
statement that created a load module that was different than the control statement member name,
the Load Utility may not find the correct load module to footprint. The Footprint Override Exit could
be used to supply the correct member name to be footprinted by the Load Utility.
The exit must be reentrant and reusable. It is called in 31-bit addressing mode.
On entry to the exit, register 1 points to a two-word parameter list. The parameter list and all
parameters are in 24-bit addressable storage. The parameter list is defined next:
Word 1
Contains the address of the Load Exit Control Block. The control block is mapped by the
@LOADDS macro.
Word 2
Contains the address of a 400 byte work area that is available for the exit. The area is on a double-
word boundary and is initialized to binary zeroes for each invocation of the exit.
If the exit decides that the default footprint element name is to be overridden, it must update field
EXMBRNM in the Load Exit Control Block with the appropriate member name and set the return code
to four. The maximum allowable member name length is eight characters. The EXMBRNM field,
however, is 10 bytes long and should be right-padded with blanks.
The exit should set one of the following return codes in register 15 before returning to the Load
Utility. If the exit wants to override the default element name, it must set a return code of four.
0
The exit does not want to override the member name.
4
The exit wants to override the member name to be footprinted.
04-May-2018 1105/1109
CA Endevor® SCM - 17.0
8
The exit encountered an unrecoverable error. The Load Utility will footprint the default member.
C1BMLXIT Exit
The exit reads link-edit control cards and extracts the module name specified in the NAME control
statement. If found, the exit sets a return code of four to indicate to the Load Utility that an override
member name is to be footprinted. The program uses an internal table to determine the element
types that are associated with linkage editor control statements. Refer to the program code for
information on how to update the table and about the method of operation and program limitations.
The exit can be assembled and link-edited using standard procedures. The load module name that is
created must be named C1EXITL1 and it must be placed in the CA Endevor® SCM CONLIB library. The
program must be link-edited with the RENT, REUS, AMODE(31), and RMODE(24) attributes.
04-May-2018 1106/1109
CA Endevor® SCM - 17.0
Trace Facilities
The trace facilities help you isolate problems by monitoring selected processes. When a trace facility
is active, information is recorded in a system trace output file.
Important! The trace formats of all traces are subject to change at any time. Therefore, we
recommend that you do not use trace output in a production setting or write programs
that interpret the trace output. Also, you should be selective in which traces you enable,
because activating traces that are not needed results in unnecessary overhead.
To enable a trace facility, use the following syntax depending on whether you want to trace batch or
foreground processing:
To route the output of the trace to a data set, replace sysout as follows:
DDnames
Specifies the name of the trace. The following traces are valid:
EN$TRALC
Traces dynamic allocation.
EN$TRAUI
Traces the Alternate ID. Also traces logon and logoff information.
EN$TRESI
Traces ESI (Endevor External Security).
04-May-2018 1107/1109
CA Endevor® SCM - 17.0
EN$TRFPV
Traces component validation.
EN$TRITE
Traces if-then-else evaluation.
EN$TRLOG
Traces logon and logoff information.
EN$TROPT
Traces Endevor table definitions.
EN$TRSMF
Writes SMF records. This trace requires the following dsname:
//EN$TRSMF DD DISP=SHR,DSN=....,LRECL=27994,BLKSIZE=27998,RECFM=VB
//* Writes SMF records to //EN$TRSMF.
//* Requires DCB or existing file !
EN$TRSYM
Traces symbolic resolution.
EN$TRXIT
Traces Exits.
In cases of abnormal software termination (ABEND), a calling path trace back is generally produced.
The trace back data is written to an output media selected from the following list in order of
availability:
You should have this trace information available when you call your CA Endevor SCM Administrator.
04-May-2018 1108/1109
CA Endevor® SCM - 17.0
The call trace displays the modules and subfunctions at the point of ABEND. The fields in bold type
vary with each trace, and are explained as follows:
BC1PSM10
Identifies the module that produced the abend.
ABEND CODE=MACR
Identifies the abend code.
NUMBER=3009
Identifies the user abend number associated with the abend.
04-May-2018 1109/1109