Endevor User Guide

Spiegel Endevor Developers User Guide
Revision History Table

REVISION DATE AUTHOR SUMMARY OF CHANGE
January 14, James E. Smith Original Document
2002 Jr.
June 7, 2002 Will DeVries Added/Updated the following sections:
Error: Reference source not found - Error:
Reference source not found
Appendix Error: Reference source not found -
Error: Reference source not found
Last Saved Date: 7/16/2007 09:49:00 AM ii

REVISION DATE AUTHOR SUMMARY OF CHANGE
Appendix Error: Reference source not found - Error:
January 2003 John Langton 4.6.1 Error: Reference source not found
Lori Brandt Updated DB2 Plan-Name and Bind-Type
sections.
“ 4.7.2 Error: Reference source not found How binds
are done.
John Langton 4.7.3 Error: Reference source not found SAR and
SDSF bind job names.
July 2003 Lori Brandt 4.5.4 The OPTIONS Element
4.6.2 DB2 Bind Overview
Areas still in work or being researched

TOPIC Section – Starting Page
Error: Reference source not found Error: Reference source not
found
Error: Reference source not found Error: Reference source not
found
Error: Reference source not found Appendix Error: Reference
source not found
Last Saved Date: 7/16/2007 09:49:00 AM iii

Table of Contents
1. SCOPE.............................................................................................................................................................1
1.1 Why should I use this User Guide?...........................................................................................................1
1.2 When and who should use this User Guide?.............................................................................................1
1.3 How do I use this document?....................................................................................................................1
2. APPLICABLE DOCUMENTS......................................................................................................................3
2.1 Functional Design.....................................................................................................................................3
2.2 Endevor Documentation from Computer Associates................................................................................3
3. INTRODUCTION...........................................................................................................................................4
3.1 Spiegel Endevor Development Life Cycle................................................................................................4
3.1.1 Endevor Development Life Cycle.....................................................................................................4
3.1.2 Crisis Life Cycle...............................................................................................................................6
3.2 What is Endevor........................................................................................................................................8
3.3 What is Quick-Edit....................................................................................................................................8
3.4 When to use Quick-Edit and when to use Endevor...................................................................................9
3.4.1 When to use Quick-Edit....................................................................................................................9
3.4.2 When to use Full Panel Endevor Batch............................................................................................9
3.4.3 When to use Full Panel Endevor....................................................................................................10
4. PROCEDURE DESCRIPTION...................................................................................................................11
4.1 Promoting Changes through the SDLC...................................................................................................11
4.1.1 Editing an Element in the UNIT Stage...........................................................................................11
4.1.2 Targeting the Production Load Library.........................................................................................16
4.1.3 Package Processing to Promote to NTGN.....................................................................................17
4.1.4 Package Automation.......................................................................................................................24
4.1.5 Moving Elements Manually from UNIT to NTGN..........................................................................25
4.1.6 Tracking Package Progress............................................................................................................28
4.1.7 Package Commit Guidelines...........................................................................................................32
4.2 Crisis changes..........................................................................................................................................33
4.2.1 Making a Crisis Change.................................................................................................................33
4.2.2 Removing an Element from Crisis..................................................................................................39
4.2.3 Moving an Element from Crisis to Production...............................................................................40
4.3 Other Functions Available......................................................................................................................45
4.3.1 Creating a new element..................................................................................................................45
4.3.2 Generate - UNIT stage only............................................................................................................48
4.3.3 Package Processing........................................................................................................................51
4.3.4 Package Backout Information........................................................................................................52
4.3.5 Delete action...................................................................................................................................53
4.3.6 Retrieving an element from Endevor..............................................................................................55
4.3.7 Adding an element back into Endevor............................................................................................61
4.3.8 Managing Signouts.........................................................................................................................67
4.4 How to get more information from Endevor and Quick-Edit.................................................................68
4.4.1 Display functions............................................................................................................................68
4.4.2 Browse, Change and History Panels..............................................................................................69
4.4.3 List Listing and List Output commands..........................................................................................75
4.4.4 Element Master Display.................................................................................................................78
4.4.5 Summary of Element Levels............................................................................................................80
4.4.6 Displaying past versions of an element..........................................................................................82
4.4.7 Getting signout information............................................................................................................84
4.4.8 ACMQ for Impact Analysis.............................................................................................................88
4.4.9 Endevor Reports.............................................................................................................................94
4.4.10 How to Print Endevor Inventory - Compile Listing........................................................................98
Last Saved Date: 7/16/2007 09:49:00 AM iv

4.4.11 How to Print Endevor Inventory - Program Source.....................................................................102
4.4.12 How to Compare Endevor Elements.............................................................................................110
4.5 Retrofits.................................................................................................................................................117
4.5.1 What is a Retrofit?........................................................................................................................117
4.5.2 Responding to a retrofit................................................................................................................118
4.5.3 Controlling Program Attributes...................................................................................................119
4.5.4 The OPTIONS element.................................................................................................................119
4.5.5 Managing the OPTIONS content..................................................................................................126
4.6 DB2 Overview......................................................................................................................................128
4.6.1 Add / Update DCLGEN................................................................................................................128
4.6.2 DB2 Bind Overview......................................................................................................................129
4.6.3 DB2 Bind Job Names....................................................................................................................131
4.6.4 DB2 Bind Failure.........................................................................................................................132
4.6.5 Backout of Packages containing DB2 Programs.........................................................................133
4.7 Handling Production Elements.............................................................................................................134
4.7.1 How to Archive a Production Element that is no longer used.....................................................134
4.7.2 How to Browse a Production Compile Listing.............................................................................135
4.7.3 How to Correct an Element in the Wrong Production System/Sub System..................................138
4.8 Handling Special Software in Endevor.................................................................................................147
4.8.1 AFP Procedures............................................................................................................................147
4.8.2 APS Procedures............................................................................................................................149
4.8.3 SDF II Procedures........................................................................................................................152
4.9 Troubleshooting Endevor Problems......................................................................................................166
4.9.1 How to do a Security Trace..........................................................................................................166
4.9.2 Easytrieve.....................................................................................................................................167
4.9.3 SQL Error -805.............................................................................................................................169
4.9.4 SQL Error -927.............................................................................................................................177
A. APPENDIX — SUPPLEMENTARY INFORMATION.....................................................................179
I. Attempting to Overlay Someone Else’s Work..........................................................................................180
II. Automatic Notifications........................................................................................................................181
III. Backups of Original Source Files.........................................................................................................182
IV. COBOL LE Differences........................................................................................................................183
V. Endevor Batch Jobs...............................................................................................................................188
VI. Endevor Location Names......................................................................................................................189
VII. Links to Additional Information...........................................................................................................191
VIII. Package Messages.............................................................................................................................192
IX. Package Names.....................................................................................................................................193
X. Quick Edit Commands..........................................................................................................................195
XI. Sample Job Card...................................................................................................................................196
XII. SIGNIN to change ownership...............................................................................................................197
XIII. Stages and their activities..................................................................................................................199
XIV. Subsystems and their Corresponding Locations for Testing.............................................................200
B. Appendix — Glossary of Terms.............................................................................................................201
Last Saved Date: 7/16/2007 09:49:00 AM v

List of Figures
FIGURE 2-1: ISPF PRIMARY OPTION MENU PANEL.................................................................................................3
FIGURE 3-1: ENDEVOR DEVELOPMENT LIFE CYCLE................................................................................................5
FIGURE 3-2: THE CRISIS LIFE CYCLE.......................................................................................................................7
FIGURE 3-3: ENDEVOR QUICK-EDIT PANEL - OPTIONS............................................................................................9
FIGURE 3-4: ENDEVOR FULL PANEL ENVIRONMENT SELECTION MENU...............................................................10
FIGURE 4-1: ENDEVOR MAIN MENU PANEL..........................................................................................................11
FIGURE 4-2: ENDEVOR MAIN MENU PANEL..........................................................................................................11
FIGURE 4-3: ENDEVOR QUICK-EDIT PANEL – ELEMENT OPTIONS........................................................................12
FIGURE 4-4: ELEMENT SELECTION LIST PANEL.....................................................................................................13
FIGURE 4-5: COBOLLE SOURCE WITH INCLUDES NOT EXPANDED.....................................................................14
FIGURE 4-6: COBOLLE SOURCE WITH INCLUDES EXPANDED..............................................................................14
FIGURE 4-7: SOURCE BEING INSERTED..................................................................................................................15
FIGURE 4-8: ENDEVOR QUICK-EDIT BATCH SUBMIT PANEL.................................................................................15
FIGURE 4-9: ENDEVOR QUICK-EDIT PANEL – PACKAGE OPTIONS........................................................................17
FIGURE 4-10: PACKAGE FOREGROUND OPTIONS MENU PANEL – CREATE/MODIFY OPTION................................18
FIGURE 4-11: CREATE/MODIFY PACKAGE PANEL – BUILD PACKAGE ACTIONS OPTION......................................19
FIGURE 4-12: SCL GENERATION PANEL – MOVE OPTION.....................................................................................20
FIGURE 4-13: MOVE ELEMENTS PANEL – MOVE ELEMENT OPTION.....................................................................20
FIGURE 4-14: ELEMENT SELECTION LIST PANEL – MOVE OPTION........................................................................21
FIGURE 4-15: CREATE/MODIFY PACKAGE – EDIT PACKAGE OPTION....................................................................21
FIGURE 4-16: PACKAGE FOREGROUND OPTIONS MENU – CAST OPTION..............................................................22
FIGURE 4-17: CAST PACKAGE PANEL....................................................................................................................23
FIGURE 4-18: ENDEVOR QUICK-EDIT PANEL.........................................................................................................25
FIGURE 4-19: ELEMENT SELECTION LIST...............................................................................................................25
FIGURE 4-20: ISPF BROWSE PANEL.......................................................................................................................26
FIGURE 4-22: ENDEVOR QUICK-EDIT BATCH SUBMIT PANEL...............................................................................27
FIGURE 4-24: ENDEVOR QUICK-EDIT – TRACKING PACKAGE PROGRESS..............................................................28
FIGURE 4-25: ELEMENT SELECTION LIST PANEL – MASTER DISPLAY..................................................................28
FIGURE 4-26: MASTER DISPLAY FOR ELEMENT – OUTPUT PACKAGE...................................................................29
FIGURE 4-27: ENDEVOR QUICK-EDIT –PACKAGE OPTIONS...................................................................................29
FIGURE 4-29: PACKAGE DISPLAY PANEL – DISPLAY ACTIONS.............................................................................30
FIGURE 4-30: PACKAGE ELEMENT INFORMATION..................................................................................................31
FIGURE 4-31: ENDEVOR QUICK-EDIT PANEL – PACKAGE OPTIONS FOR A CRISIS CHANGE...............................33
FIGURE 4-33: CREATE/MODIFY PACKAGE PANEL – BUILD PACKAGE ACTIONS OPTION......................................35
FIGURE 4-34: SCL GENERATION PANEL – MOVE OPTION.....................................................................................36
FIGURE 4-35: MOVE ELEMENTS PANEL - MOVE ELEMENT OPTION......................................................................36
FIGURE 4-36: ELEMENT SELECTION LIST PANEL – MOVE OPTION........................................................................37
FIGURE 4-37: PACKAGE FOREGROUND OPTIONS MENU – CAST OPTION..............................................................38
FIGURE 4-38: TRANSFER ELEMENTS PANEL...........................................................................................................39
FIGURE 4-39: ENDEVOR REL39 SELECTION MENU PANEL....................................................................................40
FIGURE 4-40: ENDEVOR FOR OS/390 ENVIRONMENT SELECTION PANEL..............................................................41
FIGURE 4-41: ENDEVOR FOR OS/390 PRIMARY OPTIONS MENU PANEL...............................................................41
FIGURE 4-42: BATCH OPTIONS MENU PANEL........................................................................................................42
FIGURE 4-43: SCL GENERATION PANEL................................................................................................................42
FIGURE 4-44: TRANSFER ELEMENTS PANEL...........................................................................................................43
FIGURE 4-45: ELEMENT SELECTION LIST PANEL...................................................................................................43
Last Saved Date: 7/16/2007 09:49:00 AM v

FIGURE 4-49: ENDEVOR QUICK-EDIT COPY ELEMENT PANEL..............................................................................46
FIGURE 4-51: ENDEVOR QUICK-EDIT PANEL – GENERATE ELEMENT OPTION......................................................48
FIGURE 4-52: ELEMENT SELECTION LIST PANEL – GENERATE ELEMENT OPTION................................................49
FIGURE 4-53: ENDEVOR QUICK-EDIT BATCH SUBMIT PANEL...............................................................................50
FIGURE 4-54: ENDEVOR QUICK-EDIT PANEL - DELETE OPTION............................................................................53
FIGURE 4-60: RETRIEVE ELEMENTS PANEL...........................................................................................................58
FIGURE 4-61: ELEMENT SELECTION LIST PANEL...................................................................................................59
FIGURE 4-62: CONFIRMATION PANEL....................................................................................................................59
FIGURE 4-69: ADD/UPDATE ELEMENTS PANEL......................................................................................................64
FIGURE 4-70: MEMBER SELECTION LIST PANEL....................................................................................................65
FIGURE 4-71: CONFIRMATION PANEL....................................................................................................................65
FIGURE 4-74: ENDEVOR QUICK-EDIT PANEL – ELEMENT OPTIONS......................................................................69
FIGURE 4-75: ELEMENT SELECTION LIST PANEL – BROWSE/CHANGE/HISTORY OPTIONS....................................70
FIGURE 4-76: ELEMENT BROWSE PANEL...............................................................................................................70
FIGURE 4-77: ELEMENT HISTORY PANEL...............................................................................................................71
FIGURE 4-78: ELEMENT CHANGE PANEL...............................................................................................................72
FIGURE 4-79: COMPONENT BROWSE PANEL..........................................................................................................73
FIGURE 4-80: COMPONENT HISTORY PANEL..........................................................................................................74
FIGURE 4-81: ELEMENT SELECTION LIST PANEL – LIST LISTING AND LIST OUTPUT OPTIONS............................75
FIGURE 4-82: LIST LISTING OPTION.......................................................................................................................76
FIGURE 4-83: LIST OUTPUT OPTION.......................................................................................................................76
FIGURE 4-84: ELEMENT SELECTION LIST PANEL – ELEMENT MASTER DISPLAY OPTION....................................78
FIGURE 4-85: MASTER DISPLAY FOR ELEMENT PANEL.........................................................................................79
FIGURE 4-86: ELEMENT SELECTION LIST PANEL – SUMMARY OF ELEMENT LEVELS OPTION..............................80
FIGURE 4-87: SUMMARY OF ELEMENTS LEVELS PANEL........................................................................................81
FIGURE 4-88: SUMMARY OF ELEMENT LEVELS PANEL – DISPLAYING PAST VERSIONS.......................................82
FIGURE 4-89: LEVEL 2 VERSION OF THE ELEMENT SOURCE.................................................................................83
FIGURE 4-90: ISPF ENDEVOR MAIN MENU – SIGNOUT INFORMATION.................................................................85
FIGURE 4-91: SIGNOUT INFORMATION PANEL.......................................................................................................85
FIGURE 4-92: SIGNOUT REPORT SELECTION – USER OPTION................................................................................86
FIGURE 4-93: SIGNOUT REPORT SELECTION – ELEMENT OPTION.........................................................................86
FIGURE 4-94: SIGNOUT INFORMATION PANEL.......................................................................................................87
FIGURE 4-95: CA-ENDEVOR FOR MVS PRIMARY OPTIONS MENU.......................................................................89
FIGURE 4-96: CA-ENDEVOR USER OPTIONS MENU PANEL – ACMQ OPTION......................................................89
FIGURE 4-97: CA-ENDEVOR FOR MVS ACA QUERY FACILITY PANEL................................................................90
FIGURE 4-98: CA-ENDEVOR USER OPTIONS MENU PANEL – FOOTPRINTED COMPONENTS OPTION....................90
FIGURE 4-99: ACM-RELATED FOOTPRINTED COMPONENTS PANEL.....................................................................91
FIGURE 4-100: ACMQ QUERY RESULTS PANEL....................................................................................................91
FIGURE 4-101: CA-ENDEVOR USER OPTIONS MENU PANEL – NON-FOOTPRINTED COMPONENTS OPTION.........92
FIGURE 4-102: ACM-RELATED NON-FOOTPRINTED COMPONENTS PANEL...........................................................93
FIGURE 4-103: ACM QUERY RESULTS PANEL......................................................................................................93
FIGURE 4-104: ENDEVOR REL39 SELECTION MENU PANEL..................................................................................94
Last Saved Date: 7/16/2007 09:49:00 AM vi

FIGURE 4-105: ENDEVOR FOR OS/390 ENVIRONMENT SELECTION.......................................................................94
FIGURE 4-106: ENDEVOR FOR OS/390 PRIMARY OPTIONS MENU.........................................................................95
FIGURE 4-107: ENDEVOR USER OPTIONS MENU....................................................................................................95
FIGURE 4-108: ENDEVOR REPORTING INTERFACE PANEL.....................................................................................96
FIGURE 4-109: ENDEVOR REL39 SELECTION MENU PANEL..................................................................................98
FIGURE 4-110: ENDEVOR FOR OS/390 ENVIRONMENT SELECTION PANEL............................................................98
FIGURE 4-111: ENDEVOR FOR OS/390 PRIMARY OPTIONS MENU PANEL.............................................................99
FIGURE 4-112: BATCH OPTIONS MENU PANEL......................................................................................................99
FIGURE 4-113: SCL GENERATION PANEL............................................................................................................100
FIGURE 4-114: PRINT ELEMENTS PANEL..............................................................................................................100
FIGURE 4-115: MEMBER SELECTION LIST PANEL................................................................................................101
FIGURE 4-116: BATCH OPTIONS MENU PANEL....................................................................................................101
FIGURE 4-117: ENDEVOR REL39 SELECTION MENU PANEL................................................................................102
FIGURE 4-118: ENDEVOR FOR OS/390 ENVIRONMENT SELECTION PANEL..........................................................102
FIGURE 4-119: ENDEVOR FOR OS/390 PRIMARY OPTIONS MENU PANEL...........................................................103
FIGURE 4-121: SCL GENERATION PANEL............................................................................................................104
FIGURE 4-123: ELEMENT SELECTION LIST PANEL...............................................................................................105
FIGURE 4-128: FOREGROUND OPTIONS MENU PANEL.........................................................................................107
FIGURE 4-130: ELEMENT SELECTION LIST PANEL...............................................................................................108
FIGURE 4-131: ENDEVOR FOREGROUND PRINT REQUEST OPTIONS PANEL.........................................................109
FIGURE 4-133: PARALLEL DEVELOPMENT MANAGER - PRIMARY OPTION MENU PANEL...................................110
FIGURE 4-134: BUILD WIP - WIP SPECIFICATION PANEL...................................................................................111
FIGURE 4-135: BUILD WIP - ROOT SPECIFICATION PANEL.................................................................................112
FIGURE 4-136: BUILD WIP - DERIVATION 1 SPECIFICATION PANEL...................................................................113
FIGURE 4-137: PARALLEL DEVELOPMENT MANAGER - PRIMARY OPTION MENU PANEL...................................114
FIGURE 4-138: EDIT WIP - EDIT - ENTRY PANEL................................................................................................114
FIGURE 4-139: EDIT WIP - MEMBER SELECTION LIST PANEL............................................................................115
FIGURE 4-140: PARALLEL DEVELOPMENT MANAGER WIP SUMMARY PANEL...................................................115
FIGURE 4-141: PARALLEL DEVELOPMENT MANAGER WIP SUMMARY (CHANGES ONLY) PANEL......................116
FIGURE 4-142: ELEMENT SELECTION LIST – OPTIONS ELEMENT.....................................................................126
FIGURE 4-143: ISPF EDIT SESSION – CHANGING AN OPTIONS ELEMENT.........................................................126
FIGURE 4-147: DISPLAY OPTIONS MENU PANEL.................................................................................................136
FIGURE 4-148: ENDEVOR - FOOTPRINT DISPLAY PANEL.....................................................................................137
FIGURE 4-149: LIBRARY SELECTION LIST PANEL................................................................................................137
FIGURE 4-150: ENDEVOR QUICK-EDIT PANEL – PACKAGE OPTIONS..................................................................138
FIGURE 4-151: PACKAGE FOREGROUND OPTIONS MENU PANEL – CREATE/MODIFY OPTION............................139
FIGURE 4-152: CREATE/MODIFY PACKAGE PANEL – BUILD PACKAGE ACTIONS OPTION..................................139
FIGURE 4-153: SCL GENERATION PANEL – TRANSFER OPTION..........................................................................140
FIGURE 4-154: TRANSFER ELEMENTS PANEL.......................................................................................................141
FIGURE 4-155: CREATE/MODIFY PACKAGE PANEL – EDIT PACKAGE OPTION....................................................142
FIGURE 4-156: EDIT PACKAGE PANEL – EDIT PACKAGE OPTION........................................................................142
FIGURE 4-157: CREATE/MODIFY PACKAGE PANEL – ADD NOTES TO PACKAGE OPTION...................................143
FIGURE 4-158: PACKAGE NOTE TEXT PANEL......................................................................................................143
FIGURE 4-159: TRANSFER ELEMENTS PANEL.......................................................................................................144
FIGURE 4-160: CREATE/MODIFY PACKAGE PANEL – ADD NOTES TO PACKAGE OPTION...................................145
Last Saved Date: 7/16/2007 09:49:00 AM vii

FIGURE 4-161: PACKAGE NOTE TEXT PANEL......................................................................................................145
FIGURE 4-162: RETRIEVE ELEMENTS PANEL.......................................................................................................149
FIGURE 4-163: NNI ISPF MAIN MENU PANEL....................................................................................................154
FIGURE 4-164: SDF POP-UP MENU......................................................................................................................154
FIGURE 4-165: SDFII MAIN MENU PANEL..........................................................................................................155
FIGURE 4-166: SDFII SPECIFY LIBRARIES PANEL...............................................................................................155
FIGURE 4-168: SDFII IDENTIFY PANEL................................................................................................................156
FIGURE 4-169: SDFII SELECT A PANEL EDITOR DIALOG PANEL........................................................................158
FIGURE 4-171: SDFII IDENTIFY OBJECT FOR GENERATION PANEL....................................................................159
FIGURE 4-172: SDFII SPECIFY GENERATION PARAMETERS PANEL.....................................................................160
FIGURE 4-173: SDFII SPECIFY GENERATION PARAMETERS PANEL (CONTINUED)..............................................161
FIGURE 4-174: SDFII LIST GENERATION MESSAGES PANEL...............................................................................162
FIGURE 4-176: ENDEVOR QUICK-EDIT PANEL.....................................................................................................163
FIGURE 4-178: ENDEVOR QUICK-EDIT COPY PANEL...........................................................................................164
FIGURE 4-180: SECURITY TRACE MESSAGES.......................................................................................................166
FIGURE 4-181: ORIGINAL EASYTRIEVE PROGRAM (WITH ERROR).......................................................................167
FIGURE 4-182: CORRECTED EASYTRIEVE PROGRAM (WITHOUT ERROR).............................................................168
FIGURE 4-183: SPIEGEL GROUP MAINFRAME PRIMARY OPTION MENU..............................................................169
FIGURE 4-184: COMMON MAINFRAME UTILITIES................................................................................................170
FIGURE 4-185: DB2 PRODUCTS MAIN MENU......................................................................................................170
FIGURE 4-186: DB2 APPL ADMINISTRATION.......................................................................................................171
FIGURE 4-187: BMC SOFTWARE ADMINISTRATIVE PRODUCTS FOR DB2...........................................................171
FIGURE 4-188: CATALOG MANAGER 7.1.01 PRIMARY MENU.......................................................................172
FIGURE 4-189: PACKAGE LIST..............................................................................................................................172
FIGURE 4-190: DESCRIBE PACKAGE.....................................................................................................................173
FIGURE 4-191: BROWSE PANEL............................................................................................................................174
FIGURE 4-192: BROWSE PANEL............................................................................................................................175
FIGURE A-1: OVERLAYING ANOTHER USER EXAMPLE........................................................................................180
FIGURE A-2: AUTOMATIC NOTIFICATION EXAMPLE............................................................................................181
FIGURE A-3: CHANGING OWNERSHIP EXAMPLE..................................................................................................197
Figure A-4: Signin Elements Panel......................................................................................................................197
Last Saved Date: 7/16/2007 09:49:00 AM viii

List of Tables
TABLE 1: DISPLAY FUNCTIONS..............................................................................................................................68
TABLE 2: OUTPUT SELECTION LIST PANEL FIELDS................................................................................................77
TABLE 3: SIGNOUT OPTIONS..................................................................................................................................84
TABLE 4: ACM RELATIONSHIPS (EXAMPLES).......................................................................................................88
TABLE 5: RMDS REPORTS.....................................................................................................................................97
TABLE 6: RETROFIT COURSE OF ACTION.............................................................................................................118
TABLE 7: OPTIONS ELEMENT EXAMPLES IN ENDEVOR.....................................................................................119
TABLE 8: OPTIONS ELEMENT MEMBER SYNTAX...............................................................................................120
TABLE 9: OPTIONS ELEMENT STAGES...............................................................................................................125
TABLE 10: DB2 PARMS........................................................................................................................................130
TABLE 11: APS MODULES...................................................................................................................................150
TABLE 12: APS TYPES IN ENDEVOR....................................................................................................................151
TABLE 13: TEST LEVEL APS DATASETS..............................................................................................................151
TABLE 14: ENDEVOR DEVELOPMENT LIBRARIES.................................................................................................153
TABLE 15: COBOL LE FUNCTIONS.......................................................................................................................185
TABLE 16: ENDEVOR BATCH JOBS.......................................................................................................................188
TABLE 17: PACKAGE NAME FORMAT..................................................................................................................193
TABLE 18: STAGES AND THEIR ACTIVITIES..........................................................................................................199
Table 19: Subsystems and their Corresponding Locations for Testing...............................................................200
Last Saved Date: 7/16/2007 09:49:00 AM ix

To Be Defined (TBD) / To Be Resolved (TBR) List
TBD / TBR No. Paragraph Description

No.
TBD-001
TBR-001
Last Saved Date: 7/16/2007 09:49:00 AM x

1.0 Error: Reference source not found
 Scope
1. Why should I use this User Guide?
The purpose of this User Guide is to:
 Provide an overview of the Spiegel implementation of the Endevor tool.
 Provide an overview of the Quick-Edit functions and panels.
 Provide examples and references using Quick-Edit.
 Provide examples and references using Endevor.
2. When and who should use this User Guide?

This User Guide should be used to assist a developer in creating, retrieving, editing and
controlling source code. This User Guide is to ensure compliance to the Spiegel Group of
Investment Companies, Inc. (VGI) policies associated with source code control.
The Configuration Management Policies applicable to source code control from the SDLC
RC are:
 Baseline source code is stored in a Configuration Management version controlled
repository using the approved version control tool.
 The version control tool is used to retrieve source code from the repository prior to
changes being made.
 Source code components required to build the current production version of the
software product shall be identified with a unique identifier (i.e. Package ID). This
identifier is used by the Elevations Team to identify source code changes between
Elevations.
 Define Promotion models to be used for elevating source. The promotion model shall
be consistent with that found in the SDLC RC.
 Application Disaster Recovery Documents are created for new applications.
Modifications to existing applications will require an update to the Application
Recovery Document.
 The Production Services Team is responsible for all source code promotions to
Production.
Endevor attributes associated with this policy and described in this User Guide are:
 Retrieving an element
 Creating a new element
 Building, casting and validating a package
 Displaying inventory
 Generate code in the Unit (UNIT) stage
 Deleting code
 The browse, change and history panels
 The List Listings and List Output commands
 The Element Master Display
 Summary of Element Levels
Last Saved Date: 7/16/2007 09:49:00 AM 1

 Controlling program compile attributes (Options)
3. How do I use this document?

This User Guide is structured into 4 basic sections. Section Error: Reference source not found
defines the scope of this guide. Section Error: Reference source not found contains a list of
applicable documents that may be required to implement this guide. Section Error: Reference
source not found contains an explanation of Quick-Edit and Endevor along with the Spiegel
Elevation Processes. Section Error: Reference source not found contains the procedure
description, a process flow diagram and the basic tasks to be executed. In addition, the
Appendices contain value names, notifications, a glossary of terms and the Functional Design.
This User Guide should be used by the following IT organizations to effectively manage the Endevor system:
 Technical Services
 Corporate-Wide
 Applications Development
 IT Admin
 Production Services
 Computer Operations

 Applicable Documents
Documentation, other than this guide, that the reader may find helpful is the Functional
Design document and the CA Endevor documentation that is made available by Computer
Associates.
1. Functional Design
The Functional Design document provides a high-level presentation for the overall design of
the CA-Endevor implementation at Spiegel. A copy of the Functional Design can be found in
Appendix C??? of this guide.
2. Endevor Documentation from Computer Associates

The text in this manual references documentation from Computer Associates. In particular,
the following CA manuals are referenced:
 CA Endevor for MVS Quick-Edit

 CA Endevor for MVS Administration Guide
 CA Endevor for MVS Quick Reference Guide for Users
 CA Endevor for MVS Packages
 CA Endevor for MVS Inventory Analyzer
 CA Endevor for MVS User Guide
The above documents are available on the OS/390 system and may be accessed by following
these instructions:
Menu ISPF-Util Compilers Options Status Help

------------------------------------------------------------------------------
SPIEGEL GROUP MAINFRAME PRIMARY OPTION MENU
Option ===> U;1
0 Settings Terminal and user parameters

1 View Display source data or listings
2 Edit Create or change source data
3 ISPF-Util Perform ISPF utility functions
6 Command Enter TSO or Workstation commands
7 Dialog Test Perform dialog testing
A APP-TOOLS Application Programming tools
B Business ISPF based Business Functions
C Database Database Tools
D DASD Storage Related Functions
O OPS Operations & System Programmers tools
U Utilities Common Mainframe Tools & Utilities
X Exit Leave ISPF
I Index Roadmap of Old Panels to New Panels

Y OLD Last Chance to go to the Old Panels
Enter X to Terminate using log/list defaults
Figure 2-1: ISPF Primary Option Menu Panel

Enter “U;1” as a single command at the command line. This will get you to the Book
Manager intro panel, from this point go to the EN390 bookshelf. This bookshelf has the
updated Endevor documentation.

 Introduction
1. Spiegel Endevor Development Life Cycle
1. Endevor Development Life Cycle
The standard development life cycle as defined here refers to the Endevor software Life
Cycle, by which software is created and maintained.
The following steps should be used in creating a change to a production application:
 Create a change record and obtain approvals. This may be a change calendar entry, a
work order for a new project or project charter or other applicable change record
associated with the application.
 Retrieve or create a new Endevor Element. Retrieve the version of the element
(typically the latest) that currently exists along the development path.
 Edit an Element. The retrieval, edit and update of an element may be simplified using
the Quick-Edit tool. Assign a CCID relating to a change, to change the record.
 Unit Test. Perform unit test on the change in the UNIT stage according to the Spiegel
Standard Test Approach.
 Create an Endevor Package to move to the NTGN stage. When unit test is complete,
an Endevor package of all associated changes is created to move the code to the NTGN
stage. Any developer can move the code to the NTGN stage. The Package ID relates to
the change record/CCID or to a collection of CCIDs.
 Integration Test. Perform integration testing in the NTGN stage according to the Spiegel
 Create an Endevor Package to move to the ASTG stage. When integration testing is
complete, an Endevor package consisting of all associated changes is created to move the
code to the ASTG stage. Appropriate Package approvals are obtained. QA moves the
code to the ASTG stage (a temporary holding stage for QA). The Package ID relates to
the change record/CCID or to a collection of CCIDs.
 Create an Endevor Package to move to the ACPT stage. When QA is ready to do
acceptance testing, an Endevor package consisting of all associated changes is created to
move the code to the ACPT stage. Appropriate Package approvals are obtained. QA
moves the code to the ACPT stage where acceptance testing is conducted. The Package
ID relates to the change record/CCID or to a collection of CCIDs.
 Acceptance Test. Perform acceptance testing in the ACPT stage according to the Spiegel
 Create an Endevor Package to move to the PSTG stage. When final system testing is
complete, an Endevor package of all associated changes is created to move the code to the
PSTG stage. Appropriate Package approvals are obtained. Production Services moves
the code to the PROD stage.
 Create an Endevor Package to move to the PROD stage. Appropriate Package
approvals are obtained. Production Services moves the code to the PROD stage. The
Application Disaster Recovery Procedure, updated for the promotion.

 Post Elevation Verification. When the promotion is complete, an evaluation should be
made to confirm the proper installation for all the components.

DEVELOP QA PROD OBSOLETE
(NT) (AS) (AC) (PS) (PR) (AR)

UNIT NTGN ASTG ACPT PSTG PROD NULLARCH
(U) (N) (A) (Q) (S) (P) (Stage (A)
Not
Used)
ADMIN CRISIS N
O
(EM) T
ETST EMER E
ADM1 ADM2
1
(A) (M) (C) (E)
Figure 3-2: Endevor Development Life Cycle

Note 1 –the package name for a move/transfer from EMER to UNIT starts with EU.
See Section Error: Reference source not found Error: Reference source not found in Appendix
Error: Reference source not found for package naming standards.
ENVIRONMENT name is in the box above each stage.

The names in each stage are (by line):
Top – The two-character stage ID used as the first two characters of package
names.
Middle – The four-character stage name.
Bottom – The one character stage ID.

2. Crisis Life Cycle
All developers can access the Crisis area; access is automatic. If there is more than one approver group, all
changes requested by developers must be approved for the CRISIS area. If an emergency change already exists
in the CRISIS area for an element, the developer trying to make a new change will be forced to include the
changes already present. Crisis changes require package actions; this ensures that persons other than the
requestor must be aware of changes to an element prior to its completion.
The Crisis Life Cycle is reserved for emergency, off-hour fixes to production inventory. During the daily
morning problem meeting of the following business day, a decision will be made as to what direction the Crisis
change will take next.
The choices include:
1. A temporary fix only and is not to be elevated to production.

An appropriate time will be determined for the fix to be moved to the OBSL stage and then deleted
from the Crisis stage.
2. A permanent fix following an Endevor package approval and the fix will be moved to the PSTG
stage.
This action will initiate a Retrofit action targeting all stages below PROD. For more information
regarding Retrofits, see Section Error: Reference source not found Error: Reference source not
found.
3. A permanent fix the developer will be required to apply again in the Standard Development Life
Cycle.
Once the fix is moved along the Standard Development Life Cycle from Unit to PROD, the change
in the Crisis stage can be deleted.
CRISIS – Developers will implement emergency software changes in the CRISIS stage
ETST, where Endevor compiles the program elements and produces the load module
for execution in Spiegel’s production CICS or batch flow. Developers then create a
package and contact Operations with package ID and any other necessary information.
The package is approved and moved by Operations to the EMER stage for execution in
production.
PROD – Spiegel’s production applications are normally executed from software in this stage.
Note: Elements left in the CRISIS environment will be deleted after 4 business days unless
prior arrangements have been made.

The configuration for the CRISIS Life Cycle is shown

below.
A.M.
STAT
MEETIN
G
CRISIS PRODUCTION
ETST EMER PSTG PROD
Figure 3-3: The Crisis Life Cycle

2. What is Endevor
CA-Endevor is an integrated set of management tools from Computer Associates that is used
to automate, control and monitor your applications’ development process. You can do the
following using CA-Endevor:
 Automatically compare and track your changes against production, thus creating an online
change history. This speeds up the debugging process and enables you to always know
who changed what, when and why.
 Prevent conflicting changes to the same system component.
 Browse and manipulate all components relating to an application from a single screen,
saving you time and ensuring that changes are complete.
 Automate the creation of executables.
 Ensure that the source, executable and any other output associated with element listings,
for example, correspond.
 Apply the same procedures (including: automating compiles, impact analyses and
standards checking functions) to any component type, dramatically simplifying the
promotion process.
 Put change packages and approvals online, eliminating change-related paperwork.
 View or retrieve prior levels of any element.
 Report on element definition, content and change history.
 Enforce change control procedures.
 Support concurrent development
For further information about Endevor and the suite of “add-on” products in the Endevor
family, refer to the documents from Computer Associates listed in Section Error: Reference
source not found Error: Reference source not found.
3. What is Quick-Edit
Quick-Edit is an add-on product to CA-Endevor. CA-Endevor for MVS Quick-Edit is an
ISPF dialog that allows you to update, generate or display an Endevor element. Quick-Edit
simplifies the steps required to change an element by consolidating several CA-Endevor
functions into a single interaction, for example, if an object needs to be edited, the following
steps would be taken in Quick-Edit:
 Edit the object from within CA-Endevor.
 Automatically generate the object upon exiting editor.
Using only full panel Endevor, without Quick-Edit, the steps below are required to manipulate an object. These
steps become one step under Quick-Edit.
 Edit the object with the ISPF editor.

 Add the object back to Endevor.
 Use the FOREGROUND or BATCH commands to GENERATE the object.


---------------------------- Endevor Quick-Edit -------------------------------

Command ===> _________________________________________________________________
Dialog Commands:
D Dialog Defaults AO Action Options P Package Options
Element Options:
blank Element list B Browse CR Create E Edit C Changes
G Generate # Delete M Masters O Move S Summary H History
LC List Components LL List Listing LO List Outputs LI List Inputs
ENDEVOR Location: List Options:

ENVIRONMENT.. ________ WHERE CCID IS............... ____________
SYSTEM....... ________ WHERE PROCESSOR GROUP IS.... ________
SUBSYSTEM.... ________ BUILD USING MAP............. Y (Y/N)
ELEMENT...... __________ RETURN FIRST FOUND.......... Y (Y/N)
TYPE......... ________ DISPLAY SYSTEM/SUBSYS LIST.. N (Y/N)
Action Options:
CCID......................... ____________
Comment...................... ________________________________________
Processor Group.............. ________
Override Signout............. N (Y/N)
-
Figure 3-4: Endevor Quick-Edit Panel - Options

Above is an example of the Endevor Quick-Edit panel and the options that can be accessed
from this panel
4. When to use Quick-Edit and when to use Endevor
1. When to use Quick-Edit

Quick-Edit simplifies the steps required to change an element by consolidating several
functions into a single interaction. It is best to use Quick-Edit whenever possible - for long or
short-term development on independently developed inventory items. Quick-Edit uses a
minimum number of screens. It is fast and is capable of supporting most functions. Quick-
Edit makes it difficult to place copies of Endevor inventory to datasets beyond Endevor’s
control.
2. When to use Full Panel Endevor Batch

Full Panel Endevor batch is for short-term development on a high volume of inventory that
requires a similar change. For example, when making a one-line change to a hundred JCL
elements, it is easier to use full panel Endevor to create one batch submit than to use Quick-
Edit a hundred times.

------------------- Endevor for OS/390 Environment Selection Row 1 to 11 of 11
Option ===> Scroll ===> PAGE
Select an environment to continue. Enter the END command to exit.

-- -------- ----------------------------------------
1 DEVELOP DEVELOP ENVIRONMENT
2 QA QA ENVIRONMENT
3 CRISIS CRISIS ENVIRONMENT
4 PROD PROD ENVIRONMENT
5 EDUCDEV EDUCDEV ENVIRONMENT
6 EDUCQA EDUCQA ENVIRONMENT
7 EDUCPROD EDUCPROD ENVIRONMENT
8 OBSOLETE ARCHIVE ENVIRONMENT
9 MVSTEST SAMPLE TEST ENVIRONMENT
10 MVSPROD SAMPLE PRODUCTION ENVIRONMENT
******************************* Bottom of data *******************************
Figure 3-5: Endevor Full Panel Environment Selection Menu

3. When to use Full Panel Endevor
Full Panel Endevor is best used for long term development outside of Endevor. This
approach should be the last choice for application development. By using Full Panel
Endevor, the developer manages a copy of source outside of Endevor, maintains a sign out for
the element within Endevor and receives notifications for concurrent development and
Retrofit actions against the element in the Endevor UNIT stage. Retrofit actions target the
copy of the source in the UNIT stage and will not impact the source in the developer’s own
library.

Error: Reference source not found Error: Reference source
not found
 Procedure Description
1. Promoting Changes through the SDLC
The following section provides the steps required to promote changes through the Endevor
SDLC. The examples shown and the steps provided are for editing, package processing and
tracking a package.
1. Editing an Element in the UNIT Stage

Quick-Edit is the first choice for tacking Endevor actions.
To enter Quick-Edit, follow the steps below:
1. IMPORTANT: Before proceeding, be sure that your logon procedure is set to
“ENDVOR39”.
2. From the Spiegel Group Mainframe Primary Option Menu, select option A.E.
3. If you are in concurrent development with another user you will see the following screen:
File Edit Edit_Settings Menu Utilities Compilers Test Help

-------------------------------------------------------------------------------
EDIT TEST.USERID1.ENDEVOR.MESSAGES Columns 00001 00072
Command ===> Scroll ===> CSR
****** ***************************** Top of Data ******************************
000001 ------------------------------------------------------------------------
000002 ---------- YOU ARE IN CONCURRENT DEVELOPMENT ON THESE ELEMENTS --
000003 ELEMENT TYPE USERID ENV SYSTEM SUBSYS CCID COM
000004 ------------------------------------------------------------------------
000005 M3711000 COBOLLE USERID1 DEVELOP FINANCE SPGTST05 2002-30 TOM
000006 M3711000 COBOLLE USERID2 DEVELOP FINANCE SPGTST08 2002-30 STO
000007 M3711000 COBOLLE USERID3 DEVELOP FINANCE SPGTST08 2002-30 STO
****** **************************** Bottom of Data ****************************
Figure 4-6: Endevor Main Menu Panel

4. Press PF3. This will take you to the Endevor REL39 Selection Menu.
---------------------- ENDEVOR REL39 SELECTION MENU ------------------------

OPTION ===>
E - ENDEVOR - Endevor Software Management Functions

Q - QUICK-EDIT - Endevor Quick Edit Development Workbench
P - PDM - Endevor Parallel Development Manager Merge utility
S - SIGNOUTS - Show my signouts

ST - SIGNOUTS THEM - Show signouts belonging to someone else
SE - SIGNOUTS elem - Show signouts for an Endevor element
X - EXIT
ENTER END COMMAND TO TERMINATE ISPF.
Figure 4-7: Endevor Main Menu Panel

not found
5. From this panel you can select either “Full panel Endevor (E)” or Endevor “Quick-Edit
(Q)”. Use Q for this action.

not found
Entering Q on the Endevor primary menu command line will display this panel.

Command ===> _________________________________________________________________
Dialog Commands:
Element Options:

ENVIRONMENT.. DEVELOP WHERE CCID IS............... ____________
SUBSYSTEM.... SPGTST01 BUILD USING MAP............. N (Y/N)
TYPE......... COBOLLE DISPLAY SYSTEM/SUBSYS LIST.. N (Y/N)
Action Options:
CCID......................... ____________
Comment...................... ________________________________________
Processor Group.............. ________
-
(C) 1993,2000 Computer Associates International, Inc.
Figure 4-8: Endevor Quick-Edit Panel – Element Options

6. The Element Options listed below may be used either on this panel, or the Element Selection List panel.
# Delete an element.
CR Create a new element.
E Edit an element.
G Generate an element.
M Display Master Control File information for an element.
O Move an element.
B Display the Element Browse panel (BX - component list).
C Display the Element Changes panel (CX - component changes).
H Display the Element History panel (HX - component history).
S Display a Summary of Levels panel (SX - component summary).
LC Display Components list for an element.
LI Display Input Components for an element.
LL Display the Element Listing from the Component List.
LO Display Output Components for an element.

not found
7. Some or all of the fields may be entered in the Endevor Location section of the Endevor Quick Edit
panel. These fields are ENVIRONMENT, SYSTEM, SUBSYSTEM, ELEMENT, and TYPE. See
Section Error: Reference source not found Error: Reference source not found in Appendix Error: Reference
source not found for valid entries for these fields. The ENVIRONMENT field must always be
DEVELOP. If all the fields are fully qualified, any one of the Element Options (summarized at the top of
the screen) may be used. If any of the fields are left blank or wild-carded (*) in the Endevor Location area,
an Element Selection List will be presented like the one shown in Error: Reference source not found Error:
Reference source not found.
o Note that entries in any of the List Options fields will also limit Element Selection List.
o An entry in the Where CCID is field will limit the Element Selection List to the specified CCID.
o An entry in the Where Processor Group is field will limit the Element Selection List to the specified
Processor Group.
o Build Using Map indicates whether Endevor should search the environment map when building the
Element Selection List. Y - Search the map; N - (Default) do not search the map.
o Return First Found indicates whether Endevor should stop searching the map after finding the first
occurrence of an element. Y - (Default) Return the first matching element found; N - search for all
occurrences and return a list.
o Display System/Subsys List indicates whether the system and subsystem selection lists will appear
when the System or Subsystem fields do not contain explicit values. Y - Display system and subsystem
selection lists, N - (Default) do not display the system and subsystem selection lists.
o When editing an element, you must also enter the Action Options CCID and Comment. These fields
are used by Endevor to document the history of changes made to an element.
-------------------------- Element Selection List ------------ Row 1 to 6 of 6

Command ===> ________________________________________________ Scroll ===> PAGE
Element Options:
E Edit Element # Delete B Browse H History M Master
G Generate Element O Move C Changes S Summary
Use BX, CX, HX, LL, LO, LI, LC and SX to browse component list information
Element Message Type Environment Stage System Subsystem VV.LL

-- ---------- ---------- -------- ----------- ----- -------- --------- -----
__ CSSB0010 COBOLLE DEVELOP U FINANCE SPGTST01 01.01
__ CSSB0020 COBOLLE DEVELOP U FINANCE SPGTST01 01.01
__ PEP005 COBOLLE DEVELOP U LOGISTCS SPGTST01 01.02
__ PEP007 COBOLLE DEVELOP N LOGISTCS SPGTST01 01.01
----------------------------- Bottom of the List -----------------------------
Figure 4-9: Element Selection List Panel

8. Also provided on the Element Selection List panel are the Type, Environment, Stage, System,
Subsystem and Version for each element in the list.
9. To edit an element listed, type an “E” next to the Element name. You will be placed into an ISPF edit
session with a temporary copy of the element source.

not found
CSSB0010 TO: DEVELOP/U/CSS/SPGTST01/COBOLLE COLUMNS 00001 00072
COMMAND ===> EXPINC SCROLL ===> CSR
000050 00050 01 ITEM-TRIGGER-REC-IN.
000051 00051 REPLACE ==:OP:== BY ==ITEM==.
000052 00052 ++INCLUDE PI370SCHDC
000053 00053 REPLACE OFF.
000054 00054
000055 00055 FD ITEM-TRIGGER-OUT
000056 00056 RECORDING MODE IS V
000057 00057 LABEL RECORDS ARE STANDARD
000058 00058 BLOCK CONTAINS 0 RECORDS.
000059 00059 01 ITEM-TRIGGER-REC-OUT PIC X(550).
000060 00060
000061 00061 FD BILL-TRIGGER-OUT
000062 00062 RECORDING MODE IS F
000063 00063 LABEL RECORDS ARE STANDARD
000064 00064 BLOCK CONTAINS 0 RECORDS.
000065 00065 01 BILL-TRIGGER-REC-OUT.
000066 00066 REPLACE ==:OP:== BY ==OUT==.
000067 00067 ++INCLUDE PI370TGBLC
000068 00068 REPLACE OFF.
000069 00069
000070 00070 EJECT
000071 00071 WORKING-STORAGE SECTION.
Figure 4-10: COBOLLE Source with Includes Not Expanded

10. If your program was previously stored in Panvalet, it may contain includes. If you want to see the contents
of the includes, enter EXPINC on the Command line.
CSSB0010 TO: DEVELOP/U/CSS/SPGTST01/COBOLLE COLUMNS 00001 00072

COMMAND ===> SCROLL ===> CSR
000050 00050 01 ITEM-TRIGGER-REC-IN.
000051 00051 REPLACE ==:OP:== BY ==ITEM==.
000052 00052 ++INCLUDE PI370SCHDC
=NOTE= 00001 *--------------------------------------------------------------*
=NOTE= 00002 * S P I E G E L, I N C. *
=NOTE= 00003 * *
=NOTE= 00004 * C O P S -- C O M M O N O R D E R P R O C E S S I N G *
=NOTE= 00005 * *
=NOTE= 00006 * S C H E D U L I N G W O R K F I L E *
=NOTE= 00007 * *
=NOTE= 00008 * P A C K A G E R E C O R D DESCRIPTION. *
=NOTE= 00009 *--------------------------------------------------------------*
=NOTE= 00010 * PANVALET NAME: PI370SCHDC, ASSEMBLER EQUIVALENT: N/A *
=NOTE= 00011 * *
=NOTE= 00012 * RELATED INCLUDES: PI370SCHPC *
=NOTE= 00013 * *
=NOTE= 00014 *--------------------------------------------------------------*
=NOTE= 00015 * M O D I F I C A T I O N S U M M A R Y *
=NOTE= 00016 * *
=NOTE= 00017 * .........DESCRIPTION.................. *
=NOTE= 00018 * PGMR: J BURBIE COPS NEW DEVELOPMENT. *
=NOTE= 00019 * DATE: 8/1/93 *
Figure 4-11: COBOLLE Source with Includes Expanded

11. This will place the lines from the includes in your program as =NOTE= lines. Note: You cannot do a find,
or other ISPF commands on these lines. If you want to remove them use the ISPF Reset command.

not found
CSSB0010 TO: DEVELOP/U/CSS/SPGTST1/COBOL COLUMNS 00001 00072
COMMAND ===> END SCROLL ===> PAGE
000174 *
000175 * 05/99 BBHWIRE1 SCP ADD LOGIC FOR INTERFACE CONTROL FILE
000176 * TO ALLOW BBH BANK TRANSMISSION.
000177 * 09/99 BNYWIRE1 SCP ADD LOGIC FOR INTERFACE CONTROL FILE
000178 * TO ALLOW BNY BANK TRANSMISSION.
000179 * 01/00 DCCS0001 SCP ADDITION OF DC TRADE FILE AS INPUT
000180 * (VRPDCSS.N0000.DCTRDE.CAPSTOCK)
000181 * 05/00 CSSCITI1 J@M ADD LOGIC FOR INTERFACE CONTROL FILE
000182 * TO ALLOW CTI BANK TRANSMISSION.
000183 * HAVE A NICE DAY
000184 ******************************************************************
------ * THIS IS A TEST
000186 ENVIRONMENT DIVISION.
000187
000188 CONFIGURATION SECTION.
000189 SOURCE-COMPUTER. IBM-3081.
000190 OBJECT-COMPUTER. IBM-3081.
000191 SPECIAL-NAMES.
000192 C01 IS TOP-OF-PAGE.
000193
000194 INPUT-OUTPUT SECTION.
000195 FILE-CONTROL.
Figure 4-12: Source Being Inserted

12. Complete your changes using normal ISPF edit commands. The example above shows a line of source
being inserted. To save the changes, press the <PF3> key or type “End” at the COMMAND line. Quick-
Edit will place the updated copy of your element into the UNIT stage of the DEVELOP environment. At
this point, your modified element is stored within Endevor, but is not yet generated. A generation is
required for all elements in order to build outputs from the element source. For program elements, the
Generate processor performs the compile and link. The generation of the element is performed in batch.
--------------------- ENDEVOR Quick-Edit Batch Submit -------------------------

Command ===> _________________________________________________________________
Complete the JCL JOB card and press ENTER to submit the jobstream.
Enter the END command to terminate the submit.
//USERIDA JOB (T###,00),'USERID',

// CLASS=L,MSGCLASS=S,
// NOTIFY=&SYSUID
/*ROUTE PRINT R999
Include additional JCL? N (Y/N)

Another panel will be presented if additional JCL is desired.
Figure 4-13: Endevor Quick-Edit Batch Submit Panel

13. The Endevor Quick-Edit Batch Submit panel appears in preparation for a batch
Generate. Quick-Edit presents the job card information for your review. Change USERID,
Accounting Information, and printer to your specific values. Note: CLASS must be “N”
for programs using IDMS. Once the job is submitted and completes running, unit
testing may begin.

not found
2. Targeting the Production Load Library
Prior to the Endevor conversion, developers could specify to the Spiegel Change management
system which of several production load libraries their program load module should be copied
into. Initially under Endevor, the support was provided for CICS programs only, but later it
was realized that some batch programs also must be placed into the various CICS load
libraries. Features of the Endevor support for the placement of the production load module
include: OPTIONS syntax (See Error: Reference source not found Error: Reference source
not found for details on the OPTIONS element syntax.) that enables selection of one or more
production load libraries.
OPTIONS syntax can select one or more targeted production load libraries, despite the
contents of the Library Assignment table. The format of the syntax is:
PROD-CICS-LIBRARY = ddname
Or
PROD-CICS-LIBRARY = ‘ddname1 ddname2 . . . ddnamen’
Where ddname is a valid name for the program’s processor group. For processor group EBI,
the valid values are:
o CICSPCAT for PN.ENDEVOR.PRODEBI.LOADPCAT

o CICSPCFC for PN.ENDEVOR.PRODEBI.LOADPCFC
o CICSPDB2 for PN.ENDEVOR.PRODEBI.LOADPDB2
o BATCHLIB for PN.ENDEVOR.PRODEBI.LOADLIB
For processor group SPG, the valid values are:
o CICSAIMS for PN.ENDEVOR.PRODSPG.LOADAIMS

o CICSCOMN for PN.ENDEVOR.PRODSPG.LOADCOMN
o CICSCSS for PN.ENDEVOR.PRODSPG.LOADCSS
o CICSOES for PN.ENDEVOR.PRODSPG.LOADOES
o BATCHLIB for PN.ENDEVOR.PRODSPG.LOADLIB

not found
3. Package Processing to Promote to NTGN
At the conclusion of unit testing, the next step is to elevate the element to the NTGN stage.
Endevor packaging is required for movement through all Endevor stages, including moves
from UNIT to NTGN. For further information, see Section Error: Reference source not found
Error: Reference source not found for a description of packaging at Spiegel.
For movement of inventory from the UNIT to the NTGN stage, follow the steps below:

Command ===> P________________________________________________________________
Dialog Commands:
Element Options:

SUBSYSTEM.... NNITST01 BUILD USING MAP............. N (Y/N)
TYPE......... PROC DISPLAY SYSTEM/SUBSYS LIST.. N (Y/N)
Action Options:
CCID......................... ____________
Comment...................... ________________________________________
Processor Group.............. ________
-
Figure 4-14: Endevor Quick-Edit Panel – Package Options

1. At the Endevor Quick-Edit panel, select P Package Options at the Command line.

not found
---------------------- Package Foreground Options Menu ------------------------
Option ===> 2
1 DISPLAY - Display Package Information

2 CREATE/MODIFY - Create or Modify Package
3 CAST - Prepare Package for Review
4 REVIEW - Approve or Deny Package
5 EXECUTE - Submit or Execute Package
6 SHIP - Ship Packages
7 BACKOUT - Perform Backout or Backin Processing
8 COMMIT - Clear Backout Information
9 UTILITIES - Reset, Delete, or Export Package
Package ID ===> NTxxxxxxxxxxx
Limit selection list options. These options are used by the

DISPLAY and UTILITIES functions:
In-Edit......... Y In-Execution.... Y
In-Approval..... Y Executed........ Y
Denied.......... Y Committed....... Y
Approved........ Y Enterprise Pkg.. A
Figure 4-15: Package Foreground Options Menu Panel – Create/Modify Option

2. The Package Foreground Options Menu panel will appear.
3. Select 2 CREATE/MODIFY at the Option line.
4. Enter the name of the NTGN bound package at the Package ID field. The package name
targeting the NTGN stage must begin with “NT”.
For further information regarding package names, see Section Error: Reference source not found Error:
Reference source not found in Appendix Error: Reference source not found.

not found
MODIFY -------------------- CREATE/MODIFY PACKAGE -----------------------------
OPTION ===> B
B - Build Package Actions I - Import SCL

E - Edit Package C - Copy Package
N - Add Notes to Package
PACKAGE ID: NTxxxxxxxxx STATUS: IN-EDIT

DESCRIPTION ===> Required description
PACKAGE TYPE ===> STANDARD
SHARABLE PACKAGE ===> Y (Y/N) APPEND TO PACKAGE ===> N (Y/N)
ENABLE BACKOUT ===> Y (Y/N)
EXECUTION WINDOW FROM ===> 04JAN02 00:00 TO ===> 31DEC79 00:00
INPUT PACKAGE ID ===>
FROM ISPF LIBRARY:

PROJECT ===>
GROUP ===>
TYPE ===>
MEMBER ===>
OTHER PARTITIONED OR SEQUENTIAL DATA SET:

DATA SET NAME ===>
Figure 4-16: Create/Modify Package Panel – Build Package Actions Option

5. The CREATE/MODIFY PACKAGE panel will appear.
Note: Options available for creating package content include the following:
 B – Build Package Actions from the Endevor panels.
 E – Edit Package content using the ISPF Editor.
 I – Import SCL from a dataset. Specify the location of the SCL dataset in the FROM ISPF
LIBRARY files.
 C - Copy Package, to copy the SCL from another package. Specify another package name in the
INPUT PACKAGE ID field.
Any option may be used to create the contents of a package. In the example above, a “B” is entered at the
OPTION line to choose “Build Package Actions”.
Enter the mandatory Description field.
Leave the following fields as the defaults:
Sharable Package = Y This will allow anyone to edit the package.
Append To Package = N This will overwrite the contents of an existing package.
Enable Backout = Y This will allow the package contents to be backed out, as
needed.
For information on all the available options, see the CA-Endevor MVS Packages manual.

not found
------------------------------- SCL GENERATION ------------------------------
OPTION ===> 5
1 DISPLAY - Display an element

2 ADD/UPDATE - Add or update an element into stage 1
3 RETRIEVE - Retrieve or copy an element
4 GENERATE - Execute the Generate Processor for this element
5 MOVE - Move an element to the next inventory location
6 DELETE - Delete an element
7 PRINT ELEMENT - Print elements, changes and detail change history
8 SIGNIN - Explicitly sign-in an element
9 TRANSFER - Transfer elements between two ENDEVOR locations
10 PRINT MEMBER - Print a compressed listing or member
11 LIST ELEMENT - Create List actions for ENDEVOR elements
12 LIST MEMBER - Create List actions for external members
13 ARCHIVE - Archive elements
REQUEST DATA SET: PACKAGE - NTxxxxxxxxx

APPEND: N
Figure 4-17: SCL Generation Panel – Move Option

6. The SCL GENERATION panel appears. To MOVE elements from any stage to the next stage on the
Endevor map, Option 5 is the required action. Select 5 MOVE at the OPTION line.
-------------------------------- MOVE ELEMENTS --------------------------------

OPTION ===> O
ELEMENT DISPLAY OPTIONS:
blank - Element list S - Summary B - Browse H - History
O - Move element M - Master C - Changes
FROM ENDEVOR: ACTION OPTIONS:

ENVIRONMENT ===> DEVELOP CCID ===>
SYSTEM ===> SYNC ===> N (Y/N)
SUBSYSTEM ===> EBITST01 WITH HISTORY ===> N (Y/N)
ELEMENT ===> RETAIN SIGNOUT ===> Y (Y/N)
TYPE ===> PROC SIGNOUT TO ===>
STAGE ===> ACKNOWLEDGE ELM JUMP ===> N (Y/N)
DELETE 'FROM' ELEMENT ===> Y (Y/N)
COMMENT ===>
LIST OPTIONS:
DISPLAY LIST ===> Y (Y/N)
WHERE CCID EQ ===>
WHERE PROC GRP EQ ===>
BUILD USING MAP ===> N (Y/N)
Figure 4-18: Move Elements Panel – Move Element Option

7. The MOVE ELEMENTS panel appears.
8. Select O – Move element at the OPTION line. The panel can be used to identify the
contents of the package. Two alternatives are:
 Leave blank or wild-card (*) at least one of the From Endevor fields. Then, select
from an element list of one or more elements to move.
 Enter a CCID value in the List Options section of the Move Elements panel. This
selects all elements using the same CCID value.

not found
9. In the example below, two elements are being selected for movement. MOVE SCL for the two elements
will be placed into the package.
-------------------------- Element Selection List ------- Row 1 to 13 of 3,085

Element Options:

-- ---------- ---------- -------- ----------- ----- -------- --------- -----
__ CINSP008 COBOLLE DEVELOP U CREDIT NNITST01 01.00
O_ CINSP118 COBOLLE DEVELOP U CREDIT NNITST01 01.00
__ CSSA0B ASM DEVELOP U CREDIT NNITST01 01.00
O_ CSSA0C ASM DEVELOP U CREDIT NNITST01 01.00
__ SERGE1 COBOLLE DEVELOP U CREDIT NNITST01 01.00
__ TSTHEADR COBOLLE DEVELOP U CREDIT NNITST01 01.00
__ TST0400A COBOLLE DEVELOP U CREDIT NNITST01 01.01
Figure 4-19: Element Selection List Panel – Move Option

10. *WRITTEN will appear in the message area when the SCL is successfully written to the
package.
11. Type “END” at the Command line or press the <PF3> key to return to the
CREATE/MODIFY PACKAGE panel.

OPTION ===> E

PACKAGE ID: NTxxxxxxxxx STATUS: IN-EDIT

FROM ISPF LIBRARY:

PROJECT ===>
GROUP ===>
TYPE ===>
MEMBER ===>

DATA SET NAME ===>
Figure 4-20: Create/Modify Package – Edit Package Option

12. To view the SCL statements that have been placed into the package, select E – Edit Package at the
OPTION line.

not found
13. After the package has been successfully created, it is necessary to CAST the package.
Note: The cast performs the component validation for the package and if the component validation is
successful, identifies the approvers for the package. The package is then given an “In-Approval” status.
14. The package CAST action is requested from the Package Foreground Options Menu as
shown below.

Option ===> 3


Figure 4-21: Package Foreground Options Menu – Cast Option

not found
15. The CAST package action is requested from the Cast Package panel as shown below.
CAST -------------------------- CAST PACKAGE ----------------------------------

OPTION ===> C
C - Cast Package S - Display SCL

PACKAGE ID: NTxxxxxxxxxxx STATUS: IN-EDIT

DESCRIPTION: Required Description
PACKAGE TYPE: STANDARD
SHARABLE PACKAGE: Y
VALIDATE COMPONENTS ===> Y (Y/N/W)
USER ID DATE TIME

CREATED: USERID 04JAN02 17:35
LAST UPDATED:
Figure 4-22: Cast Package Panel

Leave the Validate Components field as the default of Y. The following options are also available:
Y Validate components; do not allow the cast if validation fails.
N Do not validate components.
W Validate components; do not fail the cast if there are errors.
16. If the CAST was successful, the message CAST SUCCESSFUL will appear on the
Package Foreground Options Menu panel.
17. If the CAST was not successful, you will be placed in browse mode on a dataset that will
list the Endevor error messages. At this point, use the Edit Package option under
Create/Modify Package to correct the SCL in the package. Then CAST the package
again.
18. There are no approvers required for “NT” packages, so the next step is to execute the
package. This can be done either manually by the developer, or automatically by waiting
for Package Automation to run.
19. After a developer successfully performs the CAST of a “NT” package, Package
Automation will execute and commit the package, and then create and cast a new package
for the moves to the next stage. See Error: Reference source not found Error: Reference
source not found for details on the Package Automation process.

not found
4. Package Automation
A developer creates a package using the NT prefix. See Error: Reference source not found
Error: Reference source not found for details. Package Automation will create all the
subsequent packages based on the original. Note: Package Automation only creates new
packages for “MOVE” actions. Any other action inside a package will stop the creation of a
new package for the next stage.
There are separate jobs to process the different package prefixes. The job to process the packages that install
elements into Production is “demanded in” to CA-7 by Change Management only when needed. The jobs to
process the other packages are also controlled by CA-7. They run on a regular schedule during the day. See
Section Error: Reference source not found Error: Reference source not found in Appendix Error: Reference
source not found for details on the Package Automation jobs.
Note: Only packages using the approved Error: Reference source not found are processed.
The Package Automation jobs will perform the following actions:

 If a selected package is in APPROVED status, the Package Automation process will
execute the package, commit the package, define a new package for the next stage and
cast the new package.
 If a selected package is in EXECUTED status, the Package Automation process will
commit the package, define a new package for the next stage and cast the new package.
Note: Package Automation will stop if it tries to create a package whose name already exists (when the next
package was manually created).
Note: If extended testing is to be done in the “NTGN” stage either move the elements manually (See Error:
Reference source not found Error: Reference source not found for details.), or create a package that uses “NS” as
the prefix for the package name, instead of “NT”. Package Automation will ignore the “NS” package. The
developer will have to move the package through the steps of the package life cycle, manually. The “AS”
package will also have to be created manually.

not found
5. Moving Elements Manually from UNIT to NTGN
A developer can manually move elements from the UNIT to the NTGN stage. All other
moves must be done using packages. Use the following procedure to manually move
elements:

Command ===> _________________________________________________________________
Dialog Commands:
Element Options:

SYSTEM....... FINANCE WHERE PROCESSOR GROUP IS.... ________
SUBSYSTEM.... SPGTST05 BUILD USING MAP............. Y (Y/N)
ELEMENT...... M3711000 RETURN FIRST FOUND.......... N (Y/N)
Action Options:
CCID......................... ____________
Comment...................... ________________________________________
Processor Group.............. ________
-
Figure 4-23: Endevor Quick-Edit Panel

1. At the Endevor Quick-Edit panel, press enter for an Element Selection List.
-------------------------- Element Selection List ------------ Row 1 to 3 of 3

Element Options:

-- ---------- ---------- -------- ----------- ----- -------- --------- -----
O_ M3711000 COBOLLE DEVELOP U FINANCE SPGTST05 01.05
__ M3711000 COBOLLE PROD P FINANCE FINANCE 01.00
__ M3711000 OPTIONS PROD P FINANCE FINANCE 01.01
Figure 4-24: Element Selection List

2. At the Element Selection List panel, select O Move on the line next to the element to be moved.

not found
3. If your Move Action Mode on the Action Options panel is set to “F” for Foreground, you will see the
following panels:
Menu Utilities Compilers Help

-------------------------------------------------------------------------------
BROWSE USERID.C1TEMPR1.QS220.MSGS Line 00000000 Col 001 080
********************************* Top of Data **********************************
08:42:32 C1G0265I PROCESSOR GROUP SPG FOR ELEMENT M3711000 WAS OBTAINED FROM E
08:42:36 SMGR121I ELEMENT M3711000 01.05 CREATED AT LOCATION DEVELOP/N/FINANCE
08:42:36 C1G0143I BEGINNING EXECUTION OF MOVE PROCESSOR MLOAD# OF GROUP SPG.
08:42:36 C1G0006I SYMBOLIC SUBSTITUTION:
08:42:36 C1G0007I SYMBOLIC CCID#BND DEFINED BY PROCESSOR: NO DB2 BIND
08:42:36 C1G0007I SYMBOLIC CCID#LNK DEFINED BY PROCESSOR: COMPILE ONLY
08:42:36 C1G0007I SYMBOLIC DBRMLIB1 DEFINED BY PROCESSOR: &HLQ..&NODE1LD..DB
08:42:36 C1G0007I SYMBOLIC DBRMLIB2 DEFINED BY PROCESSOR: &HLQ..&NODE2LD..DB
08:42:36 C1G0007I SYMBOLIC GROUP DEFINED BY PROCESSOR: &GRP&C1PRGRP.
08:42:36 C1G0007I SYMBOLIC GRPCOM DEFINED BY PROCESSOR: &Z
08:42:36 C1G0007I SYMBOLIC GRPEBI DEFINED BY PROCESSOR: EBI.
08:42:36 C1G0007I SYMBOLIC GRPNNI DEFINED BY PROCESSOR: NNI.
08:42:36 C1G0007I SYMBOLIC GRPSPG DEFINED BY PROCESSOR: SPG.
08:42:36 C1G0007I SYMBOLIC HLQ DEFINED BY PROCESSOR: &HLQX&C1ENVMNT(1,2)
08:42:36 C1G0007I SYMBOLIC HLQXCR DEFINED BY PROCESSOR: PN.ENDEVOR.
08:42:36 C1G0007I SYMBOLIC HLQXDE DEFINED BY PROCESSOR: PN.ENDEVOR.
08:42:36 C1G0007I SYMBOLIC HLQXED DEFINED BY PROCESSOR: PT.ENDEVOR.
08:42:36 C1G0007I SYMBOLIC HLQXPR DEFINED BY PROCESSOR: PN.ENDEVOR.
08:42:36 C1G0007I SYMBOLIC HLQXQA DEFINED BY PROCESSOR: PN.ENDEVOR.
Figure 4-25: ISPF Browse Panel

4. At the ISPF Browse panel, you can scroll through the dataset to verify that the move
worked correctly. When you are done, press PF3 to return to the Element Selection List.
-------------------------- Element Selection List -------------- Element Moved

Element Options:

-- ---------- ---------- -------- ----------- ----- -------- --------- -----
__ M3711000 *MOVED COBOLLE DEVELOP U FINANCE SPGTST05 01.05

5. At the Element Selection List panel, you will see the *Moved message next to the moved element.

not found
6. If your Move Action Mode on the Action Options panel is set to “B” for Batch, you will see the following
panels:

Command ===> _________________________________________________________________

// NOTIFY=&SYSUID
/*ROUTE PRINT R999


7. The Endevor Quick-Edit Batch Submit panel appears in preparation for a batch Move.
Quick-Edit presents the job card information for your review. Change USERID,
Accounting Information, and printer to your specific values. Once the job is submitted
and completes running, check the job output to verify that your element has been moved
correctly.
-------------------------- Element Selection List -------------- JCL Submitted

Element Options:

-- ---------- ---------- -------- ----------- ----- -------- --------- -----
__ M3711000 *Submitted COBOLLE DEVELOP U FINANCE SPGTST05 01.05

8. At the Element Selection List panel, you will see the *Submitted message next to the element being
moved.

not found
6. Tracking Package Progress
Developers may wish to monitor the status and location of software changes.

Command ===> _________________________________________________________________
Dialog Commands:
Element Options:

ENVIRONMENT.. DEVELOP WHERE CCID IS............... CCIDVALUE
SYSTEM....... CREDIT WHERE PROCESSOR GROUP IS.... ________
ELEMENT...... __________ RETURN FIRST FOUND.......... N (Y/N)
Action Options:
CCID......................... ____________
Comment...................... ________________________________________
Processor Group.............. ________
Figure 4-29: Endevor Quick-Edit – Tracking Package Progress

1. Specify a CCID for WHERE CCID IS. Place an “N” in RETURN FIRST FOUND and
press the <Enter> key. The “N” causes all elements using that CCID to be displayed.
You then use the Element Selection List to locate inventory. An example of that panel
appears below.
-------------------------- Element Selection List ---------- Row 1 to 14 of 94

Element Options:

-- ---------- ---------- -------- ----------- ----- -------- --------- -----
__ M162032A COBOLLE PROD P CREDIT CREDIT 01.00
M_ M162032B COBOLLE PROD P CREDIT CREDIT 01.00
__ M1622000 COBOLLE PROD P CREDIT CREDIT 01.00
__ M17426IQ COBOLLE PROD P CREDIT CREDIT 01.00
Figure 4-30: Element Selection List Panel – Master Display

not found
2. The Element Selection List panel appears. Type an “M” next to the desired element name. A master
display shows the last used package name for the element.

not found
----------------- Master Display for Element M162032B ------ Panel 1 of 2
Command ===>
Environment.. PROD Processor Group.. SPG Signout ID.

System....... CREDIT Version.Level.... 01.00 Lock Pkg...
Subsystem.... CREDIT Last Action...... LOAD
Type......... COBOLLE Source Package... NTxxxxxxxxxxxxxx
Stage........ P Output Package... NTxxxxxxxxxxxxxx
Base Comment. NO PANVALET DESCRIPTION
-------------------- Last Element Action - LOAD ------------------------
User ID...... $WALTHE Date/Time... 20DEC01 08:37 CCID.......... 19970731
ENDEVOR RC... 0000 Processor...
Processor RC.
Comment...... NO PANVALET DESCRIPTION
----------------------------- Current Source -------------------------------
User ID...... $WALTHE Date/Time... 20DEC01 08:37 Delta Format.. F
Comment.. NO PANVALET DESCRIPTION CCID.......... 19970731
From DS Name. PN.ENDEVOR.EBICONV.SRCLIBP(M162032B)
-------------------------------- Generate ----------------------------------
UserID....... Date/Time... CCID..........
Comment......
Press ENTER for the next panel
Figure 4-31: Master Display for Element – Output Package

3. The Master Display for Element panel appears. The Output Package field shows the
package used for promotion to the current stage. Press PF3 twice to return to the Endevor
Quick-Edit panel.

Command ===> P________________________________________________________________
Dialog Commands:
Element Options:

ENVIRONMENT.. DEVELOP WHERE CCID IS............... CCIDVALUE
ELEMENT...... __________ RETURN FIRST FOUND.......... N (Y/N)
Action Options:
CCID......................... ____________
Comment...................... ________________________________________
Processor Group.............. ________
Figure 4-32: Endevor Quick-Edit –Package Options


not found
Option ===> 1


Figure 4-33: Package Foreground Options Menu panel – Create/Modify Option

5. At the Package Foreground Options Menu panel, select 1 Display at the Option line.
DISPLAY ----------------------- PACKAGE DISPLAY ------------------------------

OPTION ===>
blank - Display Action Summary B - Display Backout Information

A - Display Approvers S - Display SCL
R - Display Cast Report CI - Display Correlation Information
N - Display Package Notes
PACKAGE ID: NTxxxxxxxxxxxxxx STATUS: EXECUTED
DESCRIPTION: GENERATE CSS AT NEW TEST
SHARABLE PACKAGE: Y
BACKOUT ENABLED: Y
EXECUTION WINDOW FROM: 17OCT00 00:00 TO: 31DEC79 00:00
USER ID DATE TIME

CREATED: USERID 17OCT00 18:38
LAST UPDATED:
CAST: USERID 17OCT00 19:07
APPROVED/DENIED: 17OCT00 19:07
EXECUTED: USERID 17OCT00 19:07 ENDEVOR RC: 0000
BACKED OUT:
BACKED IN:
COMMITTED:
Figure 4-34: Package Display Panel – Display Actions

6. The Package Display panel appears showing the USER ID, DATE and TIME details for
the package steps. If there were problems executing the package (indicated by a Status of
EXEC-FAILED), you can determine which specific action within the package failed by
pressing Enter to Display Action Summary.

not found
DISPLAY ----------------- PACKAGE ELEMENT INFORMATION ----- Row 1 to 1 of 1
COMMAND ===> SCROLL ===> PAGE
PACKAGE ID: NTxxxxxxxxxxxxxx STATUS: EXECUTED

DESCRIPTION: GENERATE CSS AT NEW TEST
|------------ EXECUTION INFORMATION ------------|

STMT BEGIN END
NUMBER ACTION ELEMENT DATE TIME DATE TIME ENDEVOR RC PROC RC
1 MOVE M162032B 17OCT00 18:38 17OCT00 18:38 0000
Figure 4-35: Package Element Information

7. If the Package Element Information panel does not give you enough information to
determine the cause of the package problem, you can review the Package Automation jobs
in SAR. See Section Error: Reference source not found Error: Reference source not found
in Appendix Error: Reference source not found for the job names of the Package
Automation jobs.

not found
7. Package Commit Guidelines
This procedure has not been defined at this time.

not found
2. Crisis changes
The Crisis environment is designed for fixes and short-term modifications to production
executables. To use the Crisis environment, instead of the CA7 override library, follow the
instructions in Error: Reference source not found Error: Reference source not found to set up
a temporary override. When the temporary override is no longer needed, follow the
instructions in Error: Reference source not found Error: Reference source not found to remove
the temporary override.
1. Making a Crisis Change

In order to edit an element in the Crisis Environment follow the instructions found in Section
Error: Reference source not found Error: Reference source not found with the following
exceptions:
1. Use Crisis as the Environment, instead of Develop.
2. The System and Subsystem names are the same in the Crisis Environment.
Endevor packaging is required at Spiegel for Crisis changes. See also Section Error:
Reference source not found Error: Reference source not found. For movement of inventory
from the ETST to the EMER stage, follow the steps below:

Command ===> P________________________________________________________________
Dialog Commands:
Element Options:

ENVIRONMENT.. CRISIS WHERE CCID IS............... ____________
SYSTEM....... MISC WHERE PROCESSOR GROUP IS.... ________
SUBSYSTEM.... MISC BUILD USING MAP............. N (Y/N)
TYPE......... PROC DISPLAY SYSTEM/SUBSYS LIST.. N (Y/N)
Action Options:
CCID......................... ____________
Comment...................... ________________________________________
Processor Group.............. ________
-
Figure 4-36: Endevor Quick-Edit Panel – Package Options for a CRISIS Change

not found
Option ===> 2

Package ID ===> EMxxxxxxxxxxx

Figure 4-37: Package Foreground Options Menu panel – Create/Modify Option

10. The Package Foreground Options Menu panel will appear.
11. Select 2 CREATE/MODIFY at the Option line.
12. Enter the name of the EMER bound package at the Package ID field. The package name targeting the
EMER stage must begin with “EM”.

not found
OPTION ===> B

PACKAGE ID: EMxxxxxxxxx STATUS: IN-EDIT

DESCRIPTION ===> Move procs to Rescue
ENABLE BACKOUT ===> N (Y/N)
FROM ISPF LIBRARY:

PROJECT ===>
GROUP ===>
TYPE ===>
MEMBER ===>

DATA SET NAME ===>

13. The CREATE/MODIFY PACKAGE panel will appear.
Note: Options available for creating package content include the following:
 B – Build Package Actions from the Endevor panels.
 E – Edit Package content using the ISPF Editor.
 I – Import SCL from a dataset. Specify the location of the SCL dataset in the FROM ISPF
LIBRARY files.
 C - Copy Package, to copy the SCL from another package. Specify another package name in the
INPUT PACKAGE ID field.
Any option may be used to create the contents of a package. In the example above, a “B” is entered at the
OPTION line to choose “Build Package Actions”.
Enter the mandatory Description field.
For information on all the available options, see the CA-Endevor MVS Packages manual.

not found
------------------------------- SCL GENERATION ------------------------------
OPTION ===> 5

REQUEST DATA SET: PACKAGE - EMxxxxxxxxx

APPEND: N
Figure 4-39: SCL Generation Panel – Move Option

14. The SCL GENERATION panel appears. To MOVE elements from any stage to the next stage on the
Endevor map, Option 5 is the required action. Select 5 MOVE at the OPTION line.
-------------------------------- MOVE ELEMENTS --------------------------------

OPTION ===> O
O - Move element M - Master C - Changes

ENVIRONMENT ===> CRISIS CCID ===>
SYSTEM ===> MISC SYNC ===> N (Y/N)
SUBSYSTEM ===> MISC WITH HISTORY ===> N (Y/N)
ELEMENT ===> RETAIN SIGNOUT ===> Y (Y/N)
TYPE ===> PROC SIGNOUT TO ===>
STAGE ===> ACKNOWLEDGE ELM JUMP ===> N (Y/N)
DELETE 'FROM' ELEMENT ===> Y (Y/N)
COMMENT ===>
LIST OPTIONS:
WHERE CCID EQ ===>
BUILD USING MAP ===> N (Y/N)
Figure 4-40: Move Elements Panel - Move Element Option

15. The MOVE ELEMENTS panel appears.
16. Select O – Move element at the OPTION line. The panel can be used to identify the
contents of the package. Two alternatives are:
 Leave blank or wild-card (*) at least one of the From Endevor fields. Then, select
from an element list of one or more elements to move.

not found
 Enter a CCID value in the List Options section of the Move Elements panel. This
selects all elements using the same CCID value.

not found
17. In the example below, two elements are being selected for movement. MOVE SCL for the two elements
will be placed into the package.
-------------------------- Element Selection List ------- Row 1 to 13 of 3,085

Element Options:

-- ---------- ---------- -------- ----------- ----- -------- --------- -----
O_ P216B101 PROC PROD P MISC MISC 01.01
__ P216B201 PROC PROD P MISC MISC 01.01
O_ P216B401 PROC PROD P MISC MISC 01.01
Figure 4-41: Element Selection List Panel – Move Option

18. *WRITTEN will appear in the message area when the SCL is successfully written to the
package.
19. Type “END” at the Command line or press the <PF3> key to return to the
CREATE/MODIFY PACKAGE panel.

not found
20. After the package has been successfully created, it is necessary to CAST the package.
Note: The cast performs the component validation for the package and if the component validation is
successful, identifies the approvers for the package. The package is then given an “In-Approval” status.
The package CAST action is requested from the Package Foreground Options Menu as
shown below.

Option ===> 3;c

Package ID ===> EMxxxxxxxxxxx

Figure 4-42: Package Foreground Options Menu – Cast Option

21. If the CAST was successful, the message CAST SUCCESSFUL will appear on the
Package Foreground Options Menu panel.
22. If the CAST was not successful, you will be placed in browse mode on a dataset that will
list the Endevor error messages. At this point, use the Edit Package option under
Create/Modify Package to correct the SCL in the package. Then CAST the package
again.
23. Notify Computer Operations to approve and execute crisis packages.

not found
2. Removing an Element from Crisis
The Crisis environment is designed for fixes and short-term modifications to production
executables. When these executables are no longer needed, they must be removed from the
Crisis environment.
The procedure for removing elements from Crisis is as follows:
1. Have the package that was used to install elements in Crisis, backed out and committed.
(For more information on back out and commit see Section Error: Reference source not
found Error: Reference source not found.)
----------------------------- TRANSFER ELEMENTS -----------------------------

OPTION ===>
T - Transfer element M - Master C - Changes
FROM ENDEVOR: LIST OPTIONS:

ENVIRONMENT ===> CRISIS DISPLAY LIST ===> Y (Y/N)
SYSTEM ===> MDSE WHERE CCID EQ ===>
SUBSYSTEM ===> MDSE WHERE PROC GRP EQ ===> SPG
ELEMENT ===> BUILD USING MAP ===> N (Y/N)
TYPE ===>
STAGE ===> E ACTION OPTIONS:
C - ETST E - EMER CCID ===> ######
TO ENDEVOR: DELETE 'FROM' ELM ===> Y (Y/N)
ENVIRONMENT ===> OBSOLETE GENERATE ELEMENT ===> Y (Y/N)
SYSTEM ===> OVERRIDE SIGNOUT ===> N (Y/N)
SUBSYSTEM ===> PROCESSOR GROUP ===>
ELEMENT ===> SYNC ===> Y (Y/N)
TYPE ===> WITH HISTORY ===> N (Y/N)
STAGE ===> A RETAIN SIGNOUT ===> N (Y/N)
SIGNOUT TO ===>
COMMENT ===> Transfer to Obsolete Archive
Figure 4-43: Transfer Elements Panel

2. Create a package to transfer elements from CRISIS/E to OBSOLETE/A with the
following options set:
TO ENVIRONMENT OBSOLETE
TO STAGE A
CCID
DELETE ‘FROM’ ELM Y
SYNC Y
Other values in the TO Endevor location will default to the values in the FROM Endevor
location.

not found
3. Follow the normal procedure to process the package. After the package is executed, check
to make sure that the elements were transferred correctly.

not found
3. Moving an Element from Crisis to Production
Normally, an Element installed via Crisis must be moved to Production. The Package
Automation process has simplified this task. Package Automation does a look back to Crisis
for any Element being moved into Production. When a PS package (See Section Error:
Reference source not found Error: Reference source not found in Appendix Error: Reference
source not found for package naming standards.) is processed by Package Automation, an
Endevor Transfer to Obsolete action is created, in the new PR package, for each Element in
the PS package that has a corresponding Element in the Crisis Environment. Thus, when the
PR package is executed, the Element is removed from Crisis before the new move into
Production.
The normal process starts with a Transfer of Elements from Crisis to Develop Unit, and then
follows normal install procedure.
The procedure to move an element from Crisis to Production is as follows:
---------------------- ENDEVOR REL39 SELECTION MENU ---------------- --------

OPTION ===> E


X - EXIT
Figure 4-44: Endevor Rel39 Selection Menu Panel

1. At the Endevor Rel39 Selection Menu panel, enter Full Panel Endevor, by typing “E” on
the option line.

not found
Option ===> 3 Scroll ===> PAGE

-- -------- ----------------------------------------
2 QA QA ENVIRONMENT
******************************* Bottom of data ********************************
Figure 4-45: Endevor for OS/390 Environment Selection Panel

2. At the Endevor for OS/390 Environment Selection panel 1, enter the Crisis Environment
by typing “3” on the option line.
-------------- Endevor for OS/390 Primary Options Menu ----------------------

Option ===> 3
0 DEFAULTS - Specify Endevor ISPF default parameters

1 DISPLAY - Perform Display functions
2 FOREGROUND - Execute Foreground Actions
3 BATCH - Perform Batch Action processing
4 PACKAGE - Perform Foreground Package processing
5 BATCH PACKAGE - Perform Batch Package SCL Generation
U USER MENU - Display user option menu
T TUTORIAL - Display information about Endevor
C CHANGES - Display summary of changes for this release of Endevor
X EXIT - Exit the Endevor dialog
Current environment: CRISIS
Use the EXIT option to terminate Endevor for OS/390
Figure 4-46: Endevor for OS/390 Primary Options Menu Panel

3. At the Endevor for OS/390 Primary Options Menu panel, select Perform Batch Action
Processing Option by typing “3” on the option line.
1
This panel displays the environments that you have security to access. Therefore this panel may look different
than the one that you see.

not found
BATCH ----------------------- BATCH OPTIONS MENU ----------------------------
OPTION ===> 1
1 BUILD SCL - Build batch SCL actions

2 EDIT - Edit request data set
3 SUBMIT - Submit job for batch processing
4 VALIDATE - Check request data set for syntax errors
5 BUILD JCL - Enter additional JCL to be included with the job
REQUEST DATA SET:

PROJECT ===> USERID APPEND ===> N (Y/N)
GROUP ===> ENDV INCLUDE JCL ===> N (Y/N)
TYPE ===> CNTL
MEMBER ===> ANYNAME <<< This field is for the scl only

DSNAME ===>
JOB STATEMENT INFORMATION:

===> //USERIDA JOB (T370,00),'USERID',
===> // CLASS=N,MSGCLASS=S,
===> // NOTIFY=&SYSUID
===> /*ROUTE PRINT R131
Figure 4-47: Batch Options Menu Panel

4. At the Batch Options Menu panel, select Build SCL by typing “1” on the option line.
Fill in your personal PDS for Endevor. E.g. ‘USERID.ENDV.CNTL’
Enter a member name.
Press Enter.
------------------------------- SCL GENERATION ------------------------------

OPTION ===> 9

REQUEST DATA SET: USERID.ENDV.CNTL(ANYNAME)

APPEND: N
Figure 4-48: SCL Generation Panel

5. At the SCL Generation panel, select Transfer by typing “9” on the option line

not found
OPTION ===>

ENVIRONMENT ===> CRISIS DISPLAY LIST ===> Y (Y/N)
SYSTEM ===> MDSE WHERE CCID EQ ===>
SUBSYSTEM ===> MDSE WHERE PROC GRP EQ ===>
ELEMENT ===> BUILD USING MAP ===> N (Y/N)
TYPE ===>
STAGE ===> E ACTION OPTIONS:
C - ETST E - EMER CCID ===> ######
TO ENDEVOR: DELETE 'FROM' ELM ===> N (Y/N)
ENVIRONMENT ===> DEVELOP GENERATE ELEMENT ===> Y (Y/N)
SYSTEM ===> MDSE OVERRIDE SIGNOUT ===> N (Y/N)
SUBSYSTEM ===> SPGTST01 PROCESSOR GROUP ===>
TYPE ===> WITH HISTORY ===> N (Y/N)
STAGE ===> U RETAIN SIGNOUT ===> N (Y/N)
SIGNOUT TO ===>
COMMENT ===> Transfer to Develop Unit

6. At the Transfer Elements panel, be sure to mark DELETE ‘FROM’ ELM as “N”,
SYNC as “Y”, and set both the CCID and the Comment.
TRANSFER ---------------------- ELEMENT SELECTION LIST --- Row 1 to 17 of 17

TO Environment: DEVELOP System: MDSE Subsystem: SPGTST01 Stage: U
ELEMENT TO NAME TYPE ENVIRON S SYSTEM SUBSYSTEM VV.LL RC

C328DPTS CNTL CRISIS E MDSE MDSE 01.01 0000
C328DPTU CNTL CRISIS E MDSE MDSE 01.01 0000
FDSTCDXI COPY CRISIS E MDSE MDSE 01.00 0000
MRD0005 JCL CRISIS E MDSE MDSE 01.03 0000
T MRP012 COBOLLE CRISIS E MDSE MDSE 01.06 0000
MRP052 COBOLLE CRISIS E MDSE MDSE 01.03 0008
MRP293 SAS CRISIS E MDSE MDSE 01.01 0004
MRP294 SAS CRISIS E MDSE MDSE 01.02 0000
M3212037 COBOLLE CRISIS E MDSE MDSE 01.01 0000
P3286718 PROC CRISIS E MDSE MDSE 01.02 0000
P803ETL PROC CRISIS E MDSE MDSE 01.01 0000
P803Z410 PROC CRISIS E MDSE MDSE 01.01 0000
******************************* Bottom of data ********************************

7. At the Element Selection List panel, select Transfer by typing “T” on the line next to the
member you wish to transfer.

not found
8. After pressing enter, a message is shown that your request was written.
9. Then, PF3 three times to get back to the Batch Options Menu screen.

OPTION ===> 3

REQUEST DATA SET:

TYPE ===> CNTL

DSNAME ===>


10. At the Batch Options Menu panel, select Submit by typing “3” on the option line.
The message is shown that the job was submitted successfully.
This job will go to the hold queue where it can be viewed.
11. Run change thru normal procedure until PS package has been executed.
12. Add Notes to package indicating Impact Change Number, and back out procedure.
13. Cast your package.
14. Have Change Management personnel execute your package.

not found
3. Other Functions Available

In the following section, additional functions available through Quick-Edit and Endevor are
listed and discussed. These functions are creating, generating, packaging, deleting and
retrieving.
1. Creating a new element

An element can be created using CA-Endevor Quick-Edit.
Note: The Element name for a program will now be the same as the executable name. The
program that would have been named PS370NEW1 in Panvalet is named M370NEW1 in
Endevor. In Panvalet, the includes used to be renamed from PI370INC1 to TI370INC1 when
they were changed. This is no longer applicable in Endevor. All includes will be named
PI999XXXX. Endevor determines whether an include is for test or production by the
Environment/Stage that it is in.
See http://www.corp.spiegel.com/is/isproject/standards/JCL/JCLNamingStandards.pdf for
more naming standards.

Command ===> CR_______________________________________________________________
Dialog Commands:
Element Options:

SYSTEM....... LOGISTCS WHERE PROCESSOR GROUP IS.... ________
SUBSYSTEM.... SPGTST01 BUILD USING MAP............. Y (Y/N)
ELEMENT...... M370NEW1__ RETURN FIRST FOUND.......... Y (Y/N)
Action Options:
CCID......................... 2002999_____
Comment...................... New program_____________________________
Processor Group.............. SPG
-

1. At the Endevor Quick-Edit panel, select the create option, by typing “CR” on the
command line. You must also enter the complete Endevor Location, the CCID (under
Action Options), and Comment.
Note: The element is always added to the Unit Stage (Stage 1) of the Develop Environment.
If the Processor Group field is left blank, it will default to the first three characters of the
Subsystem name.

not found
M370NEW1 TO: DEVELOP/U/LOGISTCS/SPGTST01/COBOLLE New Element
COMMAND ===> copyelm SCROLL ===> CSR
****** ***************************** Top of Data ******************************
''''''
''''''
''''''
''''''
''''''
''''''
''''''
''''''
''''''
''''''
''''''
''''''
''''''
''''''
''''''
****** **************************** Bottom of Data ****************************

2. At the Endevor Quick-Edit panel, you may
a. Use the ISPF COPY command to copy source from an ISPF library
b. Use the Quick-Edit COPYELM command to copy another Endevor element
c. Enter the source one line at a time
If you use the COPYELM command you will see the panel shown below.
---------------------- ENDEVOR Quick-Edit Copy Element ------------------------

Command ===> _________________________________________________________________
ENDEVOR Location:
Environment.. DEVELOP
System....... LOGISTCS
Subsystem.... SPGTST01
Element...... M370OLD1
Type......... COBOLLE
Stage........ U
List Options:
Where CCID is............... ____________
Where Processor Group is.... ________
Build Using Map............. Y (Y/N)
Return First Found.......... Y (Y/N)
Display System/Subsys List.. N (Y/N)
Press ENTER to continue with the COPY function.

Press END to cancel the COPY function and return to ISPF/PDF Edit.
Figure 4-54: Endevor Quick-Edit Copy Element Panel

3. At the Endevor Quick-Edit Copy Element panel, select the element to be copied, by
typing the Environment, System, Subsystem, Element, Type, and Stage under the Endevor

not found
Location. You can use wildcards in any of the Endevor Location fields, if you are not sure
of the element’s location.
M370NEW1 TO: DEVELOP/U/LOGISTCS/SPGTST01/COBOLLE Element M370OLD1 Copied

****** ***************************** Top of Data ******************************
000001 IDENTIFICATION DIVISION.
000002 PROGRAM-ID. M370OLD1.
000003 *REMARKS. THIS IS AN OLD PROGRAM.
000004 *
000005 ENVIRONMENT DIVISION.
000006 CONFIGURATION SECTION.
000007 SOURCE-COMPUTER. IBM-370.
000008 OBJECT-COMPUTER. IBM-370.
000009 SPECIAL-NAMES.
000010 INPUT-OUTPUT SECTION.
000011 FILE-CONTROL.
000012 *
000013 DATA DIVISION.
000014 *
000015 FILE SECTION.
000016 *
000017 WORKING-STORAGE SECTION.
000018 01 WS-VARIABLES.
000019 03 WS-SOMETHING PIC X(4).
000020 03 WS-NOT-IMPORTANT PIC X(8).
000021 SKIP2

4. At the Endevor Quick-Edit panel, make your program changes, save and generate the
element.
For further information, see the CA-Endevor MVS Quick-Edit manual, section 3.18.

not found
2. Generate - UNIT stage only
Generate is an Endevor process for building the outputs associated with an element. For a
COPYBOOK, the output will be the insertion of the copybook into a COPYBOOK library.
For program elements, the Generate might build a DBRM member, one or more load
members and a listing.
Only in the UNIT AND NTGN stages can Quick-Edit foreground be used for performing the
Generate action. In all other stages, an Endevor package action is required.
1. Using Quick-Edit to Generate

To generate an element at the UNIT stage, follow these steps:
---------------------------- ENDEVOR Quick-Edit -------------------------------

Command ===> _________________________________________________________________
Dialog Commands:
Element Options:

ENVIRONMENT.. DEVELOP_ WHERE CCID IS............... ____________
SUBSYSTEM.... EBITST01 BUILD USING MAP............. N (Y/N)
ELEMENT...... ________ RETURN FIRST FOUND.......... Y (Y/N)
TYPE......... *_______ DISPLAY SYSTEM/SUBSYS LIST.. N (Y/N)
Action Options:
CCID......................... ____________
Comment...................... ________________________________________
Processor Group.............. ________
Figure 4-56: Endevor Quick-Edit Panel – Generate Element Option

1. At the Endevor Quick-Edit panel, type “G” at the Command line for fully qualified
Endevor Location information or use the “G” line command from the Element Selection
List, as shown below.

not found
-------------------- Element Selection List ---------- Row 1 to 14 of 28
Command ===> ___________________________________________ Scroll ===> PAGE
Element Options:

-- ---------- ---------- -------- ----------- ----- -------- --------- -----
G INSB0009 COBOLLE DEVELOP U CREDIT NNITST01 01.00
__ INSB0010 COBOLLE DEVELOP U CREDIT NNITST01 01.01
__ INSB0010 OPTION DEVELOP U CREDIT NNITST01 01.02
__ INSB0015 OPTION DEVELOP U CREDIT NNITST01 01.01
__ INSO0000 OPTION DEVELOP U CREDIT NNITST01 01.00
Figure 4-57: Element Selection List Panel – Generate Element Option

Be aware of the following before you request the Generate Element option:
 If you generate an element that is not at the entry stage and the BUILD USING MAP field is set to Y, CA-
Endevor Quick-Edit copies the element back to the entry stage before invoking the generate processor. You
cannot bypass the copyback operation. The generate processor is always executed at the entry stage
associated with the base environment.
For further information, see the CA-Endevor for MVS User Guide.
 If the element does not exist at the entry stage and the BUILD USING MAP field is set to N, the
processor has not executed and the following message is returned:
Element not found

not found
After pressing enter in Error: Reference source not found shown Error: Reference source not found, the
following panel will be displayed:

Command ===> _________________________________________________________________

// NOTIFY=&SYSUID
/*ROUTE PRINT R999


The Endevor Quick-Edit Batch Submit panel appears in preparation for a batch Generate.
Quick-Edit presents the job card information for your review. Change USERID, Accounting
Information, and printer to your specific values. Note: CLASS must be “N” for programs
using IDMS. Once the job is submitted and completes running, unit testing may begin.
2. Using Endevor to Generate

Generate actions can be performed using Endevor in Batch and in package actions.
For further information, see the following references:

 CA-Endevor for MVS Quick Reference Guide for Users, section 1.18 and 1.19,
 CA-Endevor for MVS User Guide, section 6.9
 CA-Endevor for MVS Packages, section 2.4.2

not found
3. Package Processing
Packaging is Endevor’s automated mechanism for bundling a set of instructions to perform a
promotion from one stage to the next. A package contains a set of SCL commands, which
cannot be executed until the appropriate parties indicate approval. Spiegel will use a package
to bundle a set of MOVE commands and then promote objects from one stage to another.
Using CA-Endevor to generate a set of objects to be included in a package can be
accomplished using the CCID. CA-Endevor will automatically generate a specified action
(MOVE) for objects meeting the WHERE criteria (CCID=nnnn).
Note: The previous change management system had a specific order that the objects had to
be added. The order that the move actions are added to the package does not matter.
A Package Cast performs the component validation for the package and if the cast is
successful, it will identify the required approvers for the package and changes the package to
the “In-Approval” status. Only after the cast can approvals be given.
There are five steps in the package life cycle.

1. Create
2. Cast
3. Review
4. Execute
5. Commit (Only Change Management can perform)
For further information, see the CA-Endevor MVS Packages manual, section 1.3 for details.
At Spiegel, the package actions are required for the following Endevor promotions:
 UNIT to NTGN
 NTGN to ASTG
 ASTG to ACPT
 ACPT to PSTG
 PSTG to PROD
 EMER to UNIT
 PROD to ARCH
The format of Spiegel’s package name is provided in Section Error: Reference source not found Error: Reference
source not found in Appendix Error: Reference source not found.
Production packages can be “backout enabled” by activating the Endevor package backout feature for production
bound packages. A backout restores previous executables, but does not change source in the PROD and EMER
stages, or undo any previous Retrofits. Only Production Services and Computer Operations use this feature.
For further information, see the CA-Endevor for MVS Packages manual, section 2.10.

not found
4. Package Backout Information
In order for a package to be backed out the “enable backout” switch must be set to “Y” when
the package is defined. A backout also cannot occur when a package has been committed.
A backout restores previous executables, but does not change source in the PROD and EMER
stages. For a program, this means the loadlib member is backed out
(PN.ENDEVOR.*.LOADLIB), but the Endevor source is not. For JCL and PROCS, this
means the executable JCL member is backed out (PN.ENDEVOR.*.JCLLIB and
PN.ENDEVOR.*.PROCLIB), but the Endevor source is not. A backout also does not undo
any previous Retrofits.
The assumption is that a backout was done as a temporary condition (something needs to be
fixed) and once the “fixed” item is ready for install the first package is “backed-in” and the fix
package is moved immediately after the backin.
If the backout is to be permanent the developer must recover the original source by generating
the -1 version of production back in UNIT and moving it up.
A backout action is usually expected to be a rare event.
Only Production Services and Computer Operations use this feature.

not found
5. Delete action
The delete action in Endevor erases base/delta forms of an element and removes related
information from a Master Control File or component list. Quick Edit is the recommended
tool for performing Delete actions in the UNIT stage. Endevor packaging is required for
deletions in all other stages. Rather than performing deletions from the PROD stage, it is
required that a TRANSFER be used instead. The TRANSFER places a copy of the source in
the ARCH stage for archival, prior to deletion of the element from the PROD stage.
The remainder of this section presents the use of Quick-Edit for performing a Delete action in
the UNIT stage.
1. Using Quick-Edit to Delete

To delete an element use the following instructions:
---------------------------- ENDEVOR Quick-Edit -------------------------------

Command ===> #_________________________________________________________________
Dialog Commands:
Element Options:

ENVIRONMENT.. DEVELOP_ WHERE CCID IS............... ____________
SYSTEM....... CREDIT___ WHERE PROCESSOR GROUP IS.... ________
SUBSYSTEM.... NNITST01_ BUILD USING MAP............. Y (Y/N)
ELEMENT...... TEMP RETURN FIRST FOUND.......... Y (Y/N)
TYPE......... COBOL__ DISPLAY SYSTEM/SUBSYS LIST.. N (Y/N)
Action Options:
CCID......................... trash_________
Comment...................... Have a nice day______________
Processor Group.............. ________
Figure 4-59: Endevor Quick-Edit Panel - Delete Option

1. Type the command associated with the Delete option (#) at the Command line on the
Endevor Quick-Edit panel.
Before using the Delete action for the first time, review the following information:
 Use the Delete action to delete all levels of an element, any associated processor outputs from either stage
and, if the CA-Endevor Automated Configuration Manager (ACM) is being used, the components list for an
element. If ACM is being used, the component list for an element may be elected for deletion.

not found
 You can delete elements in foreground or in batch, by specifying the Delete action mode
on the Action Options panel.
 Use the Action Options panel to further define the type of delete processing to be
performed.
 The Delete action, using Quick-Edit, has a limited range for developers. It can only be
used in the stages that the developers have access to, UNIT, NTGN, ETST and EMER.
For further information, see the CA-Endevor for MVS User Guide, section 6.8.
2. Using Endevor to Delete

Delete actions can be performed using Endevor in Foreground actions, Batch actions and in
package actions.
For further information, see the following references:

 CA-Endevor for MVS Quick Reference Guide for Users, section 1.14 and 1.15
 CA-Endevor for MVS User Guide, section 6.8
 CA-Endevor for MVS Packages manual, section 2.4.2

not found
6. Retrieving an element from Endevor
An element can be retrieved from Endevor and copied into an external data set using foreground and batch
actions. Quick-Edit’s edit function performs an implied Retrieve.
For further information, see the CA-Endevor for MVS Quick Reference Guide for Users,
section 1.36 and 1.37.
Using the Retrieve action in combination with the Add action, instead of Quick-Edit, is
recommended when you have to make the same small change to multiple elements. For
example, when making a one-line change to a hundred JCL elements, it is easier to use full
panel Endevor to create one batch submit than to use Quick-Edit a hundred times.
1. Use the Retrieve action to copy all the Endevor elements to be updated into PDS
members.
2. Use a mainframe tool, like File-aid, to update the PDS members.
3. Use the Add action to copy all the updated PDS members back into Endevor elements.
The following steps show how an element can be retrieved from Endevor using batch actions:

OPTION ===> E


X - EXIT

the option line.

not found

-- -------- ----------------------------------------
2 QA QA ENVIRONMENT
******************************* Bottom of data ********************************

2. At the Endevor for OS/390 Environment Selection panel 2, enter the Prod Environment

Option ===> 3

Current environment: PROD

3. At the Endevor for OS/390 Primary Options Menu panel, select Perform Batch
Action Processing Option by typing “3” on the option line.
2

not found
OPTION ===> 1

REQUEST DATA SET:

TYPE ===> CNTL

DSNAME ===>


Press Enter.
------------------------------- SCL GENERATION ------------------------------

OPTION ===> 3


APPEND: N

5. At the SCL Generation panel, select Retrieve by typing “3” on the option line

not found
------------------------------ RETRIEVE ELEMENTS ------------------------------
OPTION ===> R
R - Retrieve element M - Master C - Changes

ENVIRONMENT ===> PROD CCID ===>
SYSTEM ===> LOGISTCS EXPAND INCLUDES ===> N (Y/N)
SUBSYSTEM ===> LOGISTCS SIGNOUT ELEMENT ===> Y (Y/N)
ELEMENT ===> J370BLK* OVERRIDE SIGNOUT ===> N (Y/N)
TYPE ===> JCL REPLACE MEMBER ===> N (Y/N)
STAGE ===> P S - PSTG P - PROD
COMMENT ===>
TO ISPF LIBRARY: LIST OPTIONS:

PROJECT ===> USERID DISPLAY LIST ===> Y (Y/N)
LIBRARY ===> PDS WHERE CCID EQ ===>
TYPE ===> SOURCE WHERE PROC GRP EQ ===>
MEMBER ===> BUILD USING MAP ===> Y (Y/N)
FIRST FOUND ===> N (Y/N)
TO OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DATA SET NAME ===>
Figure 4-65: Retrieve Elements Panel

6. At the Retrieve Elements panel, enter data in the following fields:
a. From Endevor Enter the source of the Endevor elements.
b. Comment Enter the optional Comment for this Retrieve.
c. CCID Enter the optional CCID for this Retrieve.
d. Expand Includes Enter an “N” to leave includes unexpanded.
e. Signout Element Enter a “Y” to sign out the element.
f. Override Signout Enter an “N” to not override someone else's sign out of
this/these element(s).
g. Replace Member Enter an “N” to not replace an existing member in the PDS.
h. To ISPF Library Enter your personal PDS name. E.g. ‘USERID.PDS.SOURCE’
i. Display List Enter a “Y” to display the Element Selection List panel. Enter
an “N” to Retrieve the Endevor elements as entered in the From
Endevor fields. See below for examples. Note: An “R” must
be entered on the option line, if you enter an “N” in the Display
List field.
j. Where CCID EQ Enter the CCID to restrict the Element Selection List.
k. Where PROC GRP EQ Enter the Processor Group to restrict the Element
Selection List.
l. Build Using Map Enter a “Y” to use the map when building the Element
Selection List.
m. First Found Enter a “Y” to display only the first element found in the map
when building the Element Selection List. Enter an “N” to
display all the elements found in the map when building the
Element Selection List.

not found
If you enter a “Y” in the Display List field, you will see the following panel:
RETRIEVE ---------------------- ELEMENT SELECTION LIST ----- Row 1 to 5 of 5

TO Data set: USERID.PDS.SOURCE
ELEMENT NEWNAME TYPE ENVIRON S SYSTEM SUBSYSTEM VV.LL RC

R J370BLK1 JCL PROD P LOGISTCS LOGISTCS 01.00 0000
******************************* Bottom of data ********************************

7. At the Element Selection List panel, select Retrieve by typing “R” on the line next to the
member you wish to retrieve.
After pressing enter, a message is shown that your request was written.
Then, press PF3 three times to get back to the Batch Options Menu screen.
If you enter an “N” in the Display List field, you will see the following panel:
------------------------------- CONFIRMATION --------------------------------

COMMAND ===>
**************************************************************
* PLEASE NOTE: *
* *
* RETRIEVE action requested. *
* *
* 5 elements have been selected *
* for SCL generation. *
* *
* *
* *
* INSTRUCTIONS: *
* *
* Press the ENTER key to create SCL action *
* statements for all elements selected. *
* *
* Enter END command to cancel the request. *
* *
**************************************************************
Figure 4-67: Confirmation Panel

8. At the Confirmation panel, confirm the elements by pressing Enter.
After pressing Enter, a message is shown that your SCL was generated.
Then, press PF3 two times to get back to the Batch Options Menu screen.

not found
OPTION ===> 3

REQUEST DATA SET:

TYPE ===> CNTL

DSNAME ===>


This job will go to the hold queue where it can be viewed to verify the successful retrieval
of the elements.
At this point you can use a mainframe tool, like File-aid, to update the PDS members. When that is done, you
can use the Add action to copy all the updated PDS members back into Endevor elements. See Error: Reference
source not found Error: Reference source not found for details.

not found
7. Adding an element back into Endevor
An element can be copied from an external data set and added into Endevor using foreground and batch actions.
Quick-Edit’s edit function performs an implied Add.
section 1.8 and 1.9.
After you have used the Retrieve action to copy all the Endevor elements to be updated into
PDS members. See Error: Reference source not found Error: Reference source not found for
details. And after you have used a mainframe tool, like File-aid, to update the PDS members.
You can use the Add action to copy all the updated PDS members back into Endevor
elements.
The following steps show how an element can be added into Endevor using batch actions:

OPTION ===> E


X - EXIT

the option line.

not found

-- -------- ----------------------------------------
2 QA QA ENVIRONMENT
******************************* Bottom of data ********************************

2. At the Endevor for OS/390 Environment Selection panel 3, enter the Develop
Environment by typing “1” on the option line.

Option ===> 3

Current environment: DEVELOP

3. At the Endevor for OS/390 Primary Options Menu panel, select Perform Batch
Action Processing Option by typing “3” on the option line.
3

not found
OPTION ===> 1

REQUEST DATA SET:

TYPE ===> CNTL

DSNAME ===>


Press Enter.
------------------------------- SCL GENERATION ------------------------------

OPTION ===> 2


APPEND: N

5. At the SCL Generation panel, select Add/Update by typing “2” on the option line

not found
---------------------------- ADD/UPDATE ELEMENTS ----------------------------
OPTION ===> A
blank - Member list A - Add an element U - Update an element
TO ENDEVOR: ACTION OPTIONS:

SYSTEM ===> LOGISTCS GENERATE ELEMENT ===> Y (Y/N)
SUBSYSTEM ===> SPGTST02 DELETE INPUT SOURCE ===> N (Y/N)
ELEMENT ===> NEW VERSION ===>
TYPE ===> JCL OVERRIDE SIGNOUT ===> N (Y/N)
STAGE: U PROCESSOR GROUP ===>
UPDATE IF PRESENT ===> Y (Y/N)
COMMENT ===>
FROM ISPF LIBRARY: LIST OPTIONS:

PROJECT ===> USERID DISPLAY LIST ===> Y (Y/N)
LIBRARY ===> PDS
TYPE ===> SOURCE
MEMBER ===> J370BLK* THRU MEMBER ===>
FROM OTHER PARTITIONED OR SEQUENTIAL DATA SET:

DATA SET NAME ===>
Figure 4-74: Add/Update Elements Panel

6. At the Add/Update Elements panel, enter data in the following fields:
a. To Endevor Enter the target of the Endevor elements.
b. Comment Enter the optional Comment for this Add/Update.
c. CCID Enter the optional CCID for this Add/Update.
d. Generate Element Enter a “Y” to generate the element after it has been the
Add/Update.
e. Delete Input Source Enter an “N” to leave the members in the PDS.
f. New Version Applicable for an Add action only. This is the version number
(vv) for the new element. Acceptable values are 01-99. The
default is 01
g. Override Signout Enter an “N” to not override someone else's sign out of
this/these element(s).
h. Processor Group The name of the processor group to be associated with the
element. The default is the first three characters of the
subsystem.
i. Update If Present Applicable for an Add action only. Enter a “Y” to update the
element if it exists in Endevor.
j. From ISPF Library Enter your personal PDS name. E.g. ‘USERID.PDS.SOURCE’
k. Display List Enter a “Y” to display the Member Selection List panel. Enter
an “N” to Add/Update the Endevor elements as entered in the
From ISPF Library fields. See below for examples. Note:
An “A” must be entered on the option line, if you enter an “N”
in the Display List field.

not found
If you enter a “Y” in the Display List field, you will see the following panel:
ADD/UPDATE ---------------- MEMBER SELECTION LIST ------------ Row 1 to 5 of 5

FROM Data set: USERID.PDS.SOURCE

TO Environment: DEVELOP System: LOGISTCS Subsystem: SPGTST02 Stage: U
NEW
MEMBER ELEMENT TYPE COMMENT VERSION
A J370BLK1 JCL
A J370BLK2 JCL
A J370BLK3 JCL
A J370BLK4 JCL
A J370BLK5 JCL
******************************* Bottom of data ********************************
Figure 4-75: Member Selection List Panel

7. At the Member Selection List panel, select Add/Update by typing “A” on the line next to
the member you wish to Add/Update.
If you enter an “N” in the Display List field, you will see the following panel:
------------------------------- CONFIRMATION --------------------------------

COMMAND ===>
**************************************************************
* PLEASE NOTE: *
* *
* ADD action requested. *
* *
* 5 elements have been selected *
* for SCL generation. *
* *
* *
* *
* INSTRUCTIONS: *
* *
* Press the ENTER key to create SCL action *
* statements for all elements selected. *
* *
* Enter END command to cancel the request. *
* *
**************************************************************
Figure 4-76: Confirmation Panel

8. At the Confirmation panel, confirm the elements by pressing Enter.
After pressing Enter, a message is shown that your SCL was generated.
Then, press PF3 two times to get back to the Batch Options Menu screen.

not found
OPTION ===> 3

REQUEST DATA SET:

TYPE ===> CNTL

DSNAME ===>


This job will go to the hold queue where it can be viewed to verify the successful
add/update of the elements.

not found
8. Managing Signouts
Signouts at Spiegel are recorded by Endevor exits for each of the actions listed below:
 CA-Endevor Retrieve actions with a Signout request (default)
 CA-Endevor Add actions
 Quick-Edit sessions
Endevor user exits will automatically enforce the OVERRIDE SIGNOUT action when
necessary.
Sign-ins are performed one of two ways:

A. A package move to the PROD stage when the package name is a production
package name. See Section Error: Reference source not found Error: Reference
source not found in Appendix Error: Reference source not found.
B. A regularly scheduled maintenance jobstream, (TBD), will sign-in elements for the reasons
given below:
1. An element was signed out via Quick-Edit and moved to production without the
proper package name.
2. An element was signed out via Quick-Edit and was deleted or SIGNED IN
and updated by someone else.
3. An element was signed out via an Endevor Retrieve or ADD, is not found in Endevor
outside of PROD and is no longer found in the PDS used with the Retrieve or ADD.
Signout information is available for developers from on-demand displays. See Section Error:
Reference source not found Error: Reference source not found.
Signouts are used in the Notifications of concurrent development and Retrofit actions.

not found
4. How to get more information from Endevor and Quick-Edit
For further information, see the CA-Endevor for MVS Users Guide, section 5.0.
1. Display functions
The display functions available in Endevor from the Display Options Menu are:
Table 1: Display Functions
Option Description
1 ELEMENT Display element/component list information
2 FOOTPRINT Display footprinted members and compressed listings
3 SITE Display site information
4 STAGE Display stage information
5 SYSTEM Display system definitions
6 SUBSYSTEM Display subsystem definitions
7 TYPE Display type definitions
8 PROCESSOR Display processor group definitions
GROUP
9 APPROVER Display approver groups
GROUP
A RELATE GROUP Display inventory area/approver group relationships
E ENVIRONMENT Display information about the current environment
For further information regarding Display Functions in Endevor, see the

CA Endevor for MVS Quick Reference Guide for Users, section 1.16; and
CA Endevor for MVS User Guide, section 5.0.

not found
2. Browse, Change and History Panels

OPTION ===> Q


X - EXIT

1. At the Endevor Rel39 Selection Menu panel, enter Quick-Edit, by typing “Q” on the
option line.

Command ===> _________________________________________________________________
Dialog Commands:
Element Options:

SUBSYSTEM.... NNITST01 BUILD USING MAP............. N (Y/N)
ELEMENT...... CSS* RETURN FIRST FOUND.......... Y (Y/N)
Action Options:
CCID......................... ____________
Comment...................... ________________________________________
Processor Group.............. ________
-
Figure 4-79: Endevor Quick-Edit Panel – Element Options

2. At the Endevor Quick-Edit panel, select the Element List by pressing Enter.

not found
------------------------ Element Selection List ---------- Row 1 to 14 of 28
Command ===> ___________________________________________ Scroll ===> PAGE
Element Options:

-- ---------- ---------- -------- ----------- ----- -------- --------- -----
__ CSSB0009 COBOLLE DEVELOP U CREDIT NNITST01 01.00
B_ CSSB0010 COBOLLE DEVELOP U CREDIT NNITST01 01.04
__ CSSB0010 OPTION DEVELOP U CREDIT NNITST01 01.02
__ CSSO0000 OPTION DEVELOP U CREDIT NNITST01 01.00
Figure 4-80: Element Selection List Panel – Browse/Change/History Options

3. At the Element Selection List panel, the commands, shown above, are available for
viewing element information. A standard Endevor banner precedes the requested
displayed output.
CSSB0010 DEVELOP/U/CREDIT/NNITST01/COBOL LINE 00000000 COL 001 080

Command ===> Scroll ===> PAGE 1
********************************* Top of Data **********************************
*******************************************************************************
*******************************************************************************
** **
** ELEMENT BROWSE 18OCT00 13:42 **
** **
** ENVIRONMENT: DEVELOP SYSTEM: CREDIT SUBSYSTEM: NNITST01 **
** ELEMENT: CSSB0010 TYPE: COBOL STAGE ID: U **
** **
*******************************************************************************
*******************************************************************************
-------------------------- SOURCE LEVEL INFORMATION ---------------------------
VV.LL SYNC USER DATE TIME STMTS CCID COMMENT

----- ---- -------- ------- ----- ----- ------------ --------------------------
01.00 USL5 22AUG00 20:02 1884 TEST TES
01.01 UD6W 08OCT00 17:59 1885 INAHURRY GOT TO MAKE A CHANGE - NOW
01.02 URTC 18OCT00 12:06 1885 INAHURRY HAVE A NICE DAY
GENERATED URTC 18OCT00 12:06 INAHURRY HAVE A NICE DAY
Figure 4-81: Element Browse Panel
 B- Browse – Shows the source for an element.

not found
CSSB0010 PROD/PROD/CREDIT/CREDIT/COBOL LINE 00000125 COL 001 080

+00 ******************************************************************
+00 * READS WIRE ACTIVITY FROM 5 FILES :
+00 *
+00 * -VPRDCSS.N0000.DLYV.REDEMP.PURCH
+00 * -VPRDCSS.N0000.DLYV.EXCHANGE
+00 * -VPRDCSS.N0000.VAST.CAPSTOCK
+00 * -VPRDCSS.N0000.VVAP.CAPSTOCK
+00 * -VPRDCSS.N0000.VVNY.CAPSTOCK
+00 *
%+01 * READS DC TRADE ACTIVITY
%+01 *
%+01 * -VPRDCSS.N0000.DCTRDE.CAPSTOCK
%+01 *
+00 * FIRST OF ALL, THIS PROGRAM CHECKS THE INTERFACE CONTROL FILE
+00 * - IF FLAG = 'N' THEN SET IT TO 'Y' AND CONTINUE
+00 * - IF FLAG = 'Y' THEN ABEND BECAUSE JOB CSSJD020 IS CURRENTLY
+00 * RUNNING(THEREFORE IT HAS EXCLUSIVE CONTROL OVER THE FILES).
+00 *
%+01 * FOR EACH RECORD READ FROM THESE 6 FILES, THIS PROGRAM
%+00-01 * FOR EACH RECORD READ FROM THESE 5 FILES, THIS PROGRAM
+00 * RETRIEVES THE BANK-ID, THE FUND-TYPE, THE T-A ACTIVITY, THE
+00 * MULTI-CLASS INDICATOR AND LINECODE FROM TABLE 01.
Figure 4-82: Element History Panel
 H - History – Shows every line of source that ever belonged to the element – whether
the line is a current line or a deleted line. If levels have been consolidated for the
element, then some of the oldest history information is unavailable.

not found
*******************************************************************************

----- ---- -------- ------- ----- ----- ------------ --------------------------
01.00 UPBR 27OCT00 10:27 1626 10/21/99 US6P: BANK OF NEW YORK
01.01 UPBR 27OCT00 10:27 1763 05/13/00 UECC: BANK OF NEW YORK
01.02 UPBR 27OCT00 10:28 1800 06/05/00 UJ@M: ADD CITIBANK TO CSS
01.03 UPBR 27OCT00 10:28 1875 08/14/00 UJ@M: ADD BEACON TO CSS SY
01.04 UPBR 27OCT00 10:28 1875 08/25/00 UJ@M: FIX TRADE SHEET FILE
THIS ELEMENT HAS NOT BEEN PROCESSED.
+04 - '00/08/2509:01:18UJ@M CSSB00100001100011

+03-04 - '00/08/1409:27:21UJ@M CSSB00100001000011
+03-04 MR0499 PERFORM 8600-WRITE-NTGN-FILE2 THRU 8600-EXIT.
+03-04
+04 GO TO 5000-EXIT
+04 JM0800 ELSE
+04 MR0499 PERFORM 8600-WRITE-NTGN-FILE2 THRU 8600-EXIT.
+00-04 GO TO 5000-EXIT.
******************************** Bottom of Data ********************************
Figure 4-83: Element Change Panel
 C - Changes – Shows the changed lines for a specific element. The revision numbers
that inserted or deleted a line are shown in the display to the left of each line image.
Insertions are indicated by a plus sign (+) followed by the revision number and
deletions are indicated by a minus sign (-) followed by a revision number.

not found
CSSB0010 DEVELOP/UNIT/CREDIT/NNITST01/COBOL LINE 00000000 COL 001 080
Command ===> Scroll ===> PAGE
********************************* Top of Data **********************************
*******************************************************************************
*******************************************************************************
** **
** COMPONENT BROWSE 18OCT00 13:47 **
** **
** ENVIRONMENT: DEVELOP SYSTEM: CREDIT SUBSYSTEM: NNITST01 **
** ELEMENT: CSSB0010 TYPE: COBOL STAGE ID: 1 **
** **
*******************************************************************************
*******************************************************************************
---------------------- COMPONENT LEVEL INFORMATION ---------------------------

----- ---- -------- ------- ----- ----- ------------ --------------------------
-------------------------- ELEMENT INFORMATION ------------------------------
Figure 4-84: Component Browse Panel

 BX - Browse – To Browse a specific component level.

not found
You can also view component list information for the element. Add an X after the command to be performed,
for example:
CSSB0010 DEVELOP/UNIT/FINANCE/NNITST01/COBOL LINE 00000000 COL 001 080

-------------------------- ELEMENT INFORMATION ------------------------------
VV.LL DATE TIME SYSTEM SUBSYS ELEMENT TYPE GROUP STG S

+03 01.03 10NOV00 14:32 FINANCE NNITST01 FINARPPM COBOL NNI 1
+02-03 01.02 10NOV00 13:44 FINANCE NNITST01 FINARPPM COBOL NNI 1
--------------------------- INPUT COMPONENTS ------------------------------
STEP: COMPILE DD=SYSLIB VOL=TST084 DSN=VTSTAPP.TRAINPRD.COPYLIB
MEMBER VV.LL DATE TIME SYSTEM SUBSYS ELEMENT TYPE STG

+03 HEADER1 01.00 02APR92 12:19 FINANCE NNITST01 HEADER1 CPY 2
STEP: LKED DD=SYSLIB VOL=TST083 DSN=VTSTAPP.TRAINPRD.LOADLIB
MEMBER VV.LL DATE TIME SYSTEM SUBSYS ELEMENT TYPE STG

+03 FINARS01 01.00 18SEP00 17:53 FINANCE FINANCE FINARS01 COBOL 2
+03 FINARS02 01.00 18SEP00 17:53 FINANCE FINANCE FINARS02 COBOL 2
Figure 4-85: Component History Panel
 HX - History – Shows the history of a specific component.
 CX - Changes – Shows the changes of a specific component.

not found
3. List Listing and List Output commands

Element Options:

-- ---------- ---------- -------- ----------- ----- -------- --------- -----
LL CSSB0010 COBOLLE DEVELOP U CREDIT NNITST01 01.04
Figure 4-86: Element Selection List Panel – List Listing and List Output Options
1. At the Element Selection List panel, the List Listing and List Output commands are
available.

not found
--------------------------------------------------------------------------------------
BROWSE URTC.C1#1TMPL.QGIA.LIST Line 00000160 Col 001 080
000012 * IGNORE UPPER/LOWER CASE DIFFERENCES: NO
000013 *
000014 * INPUT VERSIONS TO CONSOLIDATION:
000015 * ID FILE/DSN RECORDS LAST MODIFIED BY EQUAL
000016 * ====================================================
000017 * 1 TEMP1 1798 06/05/2000 09:52 UJ@M
000018 * VPRDLIB.MASP.SOURCE(CSSB0010)
000019 * RECORD FORMAT: FB DATA LENGTH: 80
000020 * 2 TEMP2 1658 01/28/2000 14:27 UMRQ
000021 * VTSTCPS.BEACON.CSS.SOURCE(CSSB0010)
000022 * RECORD FORMAT: FB DATA LENGTH: 80
000023 *
000024 * LAST EDITED ON 06/20/2000 AT 06:09 BY UJ@M
000025 * TOTAL NUMBER OF RECORDS IN CONSOLIDATED FILE........
000026 * NUMBER OF ACTIVE (NON-DELETED) RECORDS..............
000027 * NUMBER OF UPDATES MADE TO CONSOLIDATED FILE.........
000028 *
000029 * LAST EXPORTED ON 06/20/2000 AT 06:09 BY UJ@M
000030 * TO UJ@M.SHS.SOURCE(CSSB0010)
000031 *
Figure 4-87: List Listing Option
2. The above panel appears when the LL – List Listing option is chosen. The LL option
displays the Endevor generate (compile and link) listing, if the element was generated in
its current stage.
-------------------------- Outputs Selection List ----------------- Row 1 of 2

Command ===> ________________________________________________ Scroll ===> 0002
Element Options:
L Browse Member
Member Step Ddname Dsname

- ---------- -------- -------- --------------------------------------------
INSBN08B LKED SYSLMOD VPRDEND.UNIT.BAT1.LOAD
INSBN08B SAVLIST C1LLIBO VPRDEND.UNIT.BAT1.LISTLIB
Figure 4-88: List Output Option

3. The above panel appears when the LO – List Output option is chosen. The LO option
displays the outputs that were created for the element by the Generate process.

not found
The table below describes the fields that appear on the Output Selection List panel.
Table 2: Output Selection List Panel Fields
Field Description
Element The Element Options field provides the ability to view any of the
Options output components listed on the Output Selection List panel by
placing an L - Browse Member, to the left of the Member name and
pressing the <ENTER> key. CA-Endevor displays a standard ISPF
browse panel showing the member you selected.
Member Identifies the name of the output component created during processor
execution.
Step Identifies the STEP name of the processor.
DDName Identifies the DDName of the processor.
DSName Identifies the library that contains the output components.
For further information, see the CA-Endevor MVS Quick-Edit manual; section 3.13.

not found
4. Element Master Display

Element Options:

-- ---------- ---------- -------- ----------- ----- -------- --------- -----
M_ CSSB0010 COBOLLE DEVELOP U CREDIT NNITST01 01.04
Figure 4-89: Element Selection List Panel – Element Master Display Option
1. At the Element Selection List panel, an Element Master Display may be requested by typing an “M” next
to the desired Element.

not found
------------------- Master Display for Element CSSB0010 ------ Panel 1 of 2
Command ===> END
Environment.. DEVELOP Processor Group.. COBOL Signout ID.. URTC

System....... CREDIT Version.Level.... 01.04
Subsystem.... NNITST01 Last Action...... EDIT
Type......... COBOL Source Package...
Stage........ 1 Output Package...
Base Comment. TEST
---------------------- Last Element Action - EDIT -------------------------
User ID...... URTC Date/Time... 18OCT00 12:12 CCID.......... INAHURRY
ENDEVOR RC... 0000 Processor...
Processor RC.
Comment...... HAVE A NICE DAY
------------------------------- Current Source --------------------------------
User ID...... URTC Date/Time... 18OCT00 12:12 Delta Format.. R
Comment.. HAVE A NICE DAY CCID.......... INAHURRY
From DS Name. URTC.QERCVY19.RECOVERY
---------------------------------- Generate -----------------------------------
UserID....... Date/Time... CCID..........
Comment......
Press ENTER for the next panel
Figure 4-90: Master Display for Element Panel

2. The Master Display for Element panel provides Master Control File information about the specified
element. These are output-only displays.
Note: There are two panels that show element information. The <Enter> key acts as a
toggle key. Press the <Enter> key from the first panel and the second panel appears.
Press the <Enter> key from the second panel and the first panel appears.
3. When the END command is typed on the Command line from either panel, CA-Endevor
Quick-Edit returns to the panel the original request was made.
The Master display option may be selected from the Endevor Quick-Edit panel or the
Element Selection List.

not found
5. Summary of Element Levels

Element Options:

-- ---------- ---------- -------- ----------- ----- -------- --------- -----
S_ CSSB0010 COBOLLE DEVELOP U CREDIT NNITST01 01.04
Figure 4-91: Element Selection List Panel – Summary of Element Levels Option
1. At the Element Selection List panel, a summary of element levels may be requested by typing an “S” next
to the desired Element listed.

not found
------------------------- Summary of Element Levels ---------- Row 1 to 5 of 5
Command ===> END_____________________________________________ Scroll ===> PAGE
Element Options:
E Edit Element B Browse H History C Changes
Element: CSSB0010
Environment: DEVELOP Stage ID: U
System: CREDIT Subsystem: NNITST01 Type: COBOLLE
VV.LL User Date Time Statements Inserts Deletes Sync

- ----- ---------- -------- ------- ----- ---------- ------- ------- ----
_ 01.00 USL5 22AUG00 20:02 1884 0 0
_ 01.01 UD6W 08OCT00 17:59 1885 1 0
_ 01.02 URTC 18OCT00 12:06 1885 1 1
_ 01.03 URTC 18OCT00 12:08 1885 1 1
_ 01.04 URTC 18OCT00 12:12 1885 1 1
Figure 4-92: Summary of Elements Levels Panel

2. The Summary of Element Levels panel appears. On any detail line the E, B, H or C option may be used.
To return to the Endevor Quick-Edit panel type “END” at the Command line.
For further information, see the CA-Endevor for MVS Quick-Edit manual, section 3.10.

not found
6. Displaying past versions of an element
Many functions can be performed on past versions of an element.
------------------------- Summary of Element Levels ---------- Row 1 to 5 of 5

Command ===> END_____________________________________________ Scroll ===> PAGE
Element Options:
E Edit Element B Browse H History C Changes
Element: CSSB0010
Environment: DEVELOP Stage ID: U
System: CREDIT Subsystem: NNITST01 Type: COBOLLE
VV.LL User Date Time Statements Inserts Deletes Sync

- ----- ---------- -------- ------- ----- ---------- ------- ------- ----
_ 01.00 USL5 22AUG00 20:02 1884 0 0
_ 01.01 UD6W 08OCT00 17:59 1885 1 0
B 01.02 URTC 18OCT00 12:06 1885 1 1
_ 01.03 URTC 18OCT00 12:08 1885 1 1
_ 01.04 URTC 18OCT00 12:12 1885 1 1
Figure 4-93: Summary of Element Levels Panel – Displaying Past Versions

1. At the Summary of Element Levels panel, select the desired element by typing a “B” next to the element
level.

not found
*******************************************************************************
** **
** ELEMENT BROWSE 18NOV00 13:43 **
** **
** ENVIRONMENT: PROD SYSTEM: CREDIT SUBSYSTEM: CREDIT **
** ELEMENT: CSSB0010 TYPE: COBOLLE STAGE ID: P **
** **
*******************************************************************************
*******************************************************************************

----- ---- -------- ------- ----- ----- ------------ --------------------------
01.00 UPBR 27OCT00 10:27 1626 10/21/99 US6P: BANK OF NEW YORK
01.01 UPBR 27OCT00 10:27 1763 05/13/00 UECC: BANK OF NEW YORK
01.02 UPBR 27OCT00 10:28 1800 06/05/00 UJ@M: ADD CITIBANK TO CSS
+00 *-----------------VERSION MERGER RECONCILIATION------------------*

+00 * *
%+02 * CONSOLIDATED ON 05/23/2000 AT 11:57 BY UJ@M *
%+02 * TOTAL NUMBER OF RECORDS IN CONSOLIDATED FILE..........1789 *
Figure 4-94: Level 2 Version of the Element Source

2. The above panel displays the level 2 version of the element source.
section 1.16.

not found
7. Getting signout information
Endevor records a signout for each Endevor RETRIEVE and ADD statement. Signouts are
also recorded for Quick-Edit edit sessions. Displays of current signout information can be
obtained from the SIGNOUTS tool. The various options and views of signout information are
presented below. For example, any developer may see his or her own signouts by requesting
a TSO SIGNOUTS command.
Table 3: Signout Options
Signouts Option View display
none Shows all recorded signouts for the requesting
userid.
userid Shows all recorded signouts for the userid
specified.
ME+ Shows only recorded signouts for the
requesting userid that are also signed out to at
least one other user.
THEM+ Prompts for a userid. Then, shows only
recorded signouts for the specified userid that
are also signed out to at least one other user.
ELEMENT Prompts for an element name. Type is
optional. Then, shows only recorded signouts
for the specified element name and Type if
specified.

not found
OPTION ===> S


X - EXIT
Figure 4-95: ISPF Endevor Main Menu – Signout Information

1. At the Endevor Main Menu, type S, ST or SE at the Option line.
2. “S” will display your signed out elements
3. “ST” and “SE” will display another panel where you can enter another person's ID or an Endevor element
name to get a sign out display for the selected name. (See next page for examples.)
Signout Information Row 1 of 6

OPTION ===>
Element Type Userid Date System Original Stage

Ccid Time Subsystem
ISMO805 COBOL UD6W 2000/11/14 MISC DEVELOP

GO 17:13 NNITST04
TRASH OPTION UD6W 2000/11/17 MISD DEVELOP
GO 12:11 NNITST04
UPBRDC01 OPTION UD6W 2000/11/13 FINANCE DEVELOP
GO 15:14 EBITST02
UPBRDC01 COBOL UD6W 2000/10/31 FINANCE DEVELOP
GO 13:57 EBITST02
******************************* Bottom of data *******************************
Figure 4-96: Signout Information Panel

 The Signout Information panel display.

not found
To view signouts for another person's ID, use ST at the Command line.
---------------------- SIGNOUT REPORT SELECTION FOR USER ----------------------

OPTION ===>
Press enter for your userid, or enter another:
Userid ===> SX1234
(PRESS ENTER or PF3 TO CANCEL OR END)
Figure 4-97: Signout Report Selection – User Option
 Type a user ID to see what elements that user has signed out.
To view signouts for an element, use SE at the Command line.
Figure 4-98: Signout Report Selection – Element Option

----------------------- SIGNOUT REPORT SELECTION ELEMENT ----------------------
OPTION ===>
Enter an Element Name and optionally a Type
Element Name ===> CSSB0010

Type ===>
(PRESS ENTER or PF3 TO CANCEL OR END)
 Type the Element Name to view all signout information for that element. The Type field is optional.

not found
Signout Information Row 1 to 5 of 5

OPTION ===>
Element Type Userid Date System Original Stage

Ccid Time Subsystem
CSSB0010 COBOL URTC 2000/10/18 CREDIT DEVELOP

11:58 NNITST01
CSSB0010 OPTION UD6W 2000/10/08 CREDIT DEVELOP
INAHURRY 17:57 NNITST01
CSSB0010 COBOL UD6W 2000/10/08 CREDIT DEVELOP
INAHURRY 17:59 NNITST01
CSSB0010 OPTION UPBR 2000/10/17 CREDIT DEVELOP
LOAD 19:03 NNITST04
CSSB0010 COBOL UPBR 2000/10/17 CREDIT DEVELOP
CSSCONV11 19:09 NNITST04
******************************* Bottom of data ********************************
Figure 4-99: Signout Information Panel

3. The Signout Information panel appears. The element selected along with all pertinent signout information
is listed.

not found
8. ACMQ for Impact Analysis
1. Introduction
The Automated Configuration Manager (ACM) is a facility used by Endevor to store
relationship information in ACM Root and Cross-reference repositories. Only relationship
information between CA-Endevor elements and other CA-Endevor elements or entities
outside of CA-Endevor are stored. The table below shows example ACM relationships at
SPIEGEL. There are many other relationships that are tracked.
Table 4: ACM Relationships (Examples)
Endevor element Relationship with entity (Component)

COBOL program Endevor COPY elements referenced by a COPY
statement.
COBOL program Non-Endevor copybooks referenced by a COPY
statement.
Program Endevor controlled subroutine.
Program Non-Endevor controlled subroutine.
Endevor automatically collects relationship information at the time of a Generate action. For
example, when Endevor compiles a COBOL program, the relationship information about the
program and its Copybook members is captured and stored within the ACM repository.
An ACMQ Query facility provides capability to quickly perform “where-used” queries

against the ACM repositories. The remainder of this section presents aspects of using the
ACMQ tool at SPIEGEL.
2. Getting to the ACMQ facility
1. Follow these steps to get to the ACMQ facility:

2. Go into Full Panel Endevor, (Follow procedure below).
Make sure your LOGON PROC = ENDVOR39
At the command line, on the Spiegel Group Mainframe Primary Option Menu, enter: A.E
At the command line enter: E (To enter Full Panel Endevor.)
At the command line enter: select any environment

not found
-------------- CA-Endevor for MVS Primary Options Menu -------------------
Option ===> U

4 ENVIRONMENT - Define or Modify Environment information
Use the EXIT option to terminate CA-Endevor for MVS
Figure 4-100: CA-Endevor for MVS Primary Options Menu

3. From The Endevor Primary Options Menu, type a “U” at the Option line.
4. The CA-Endevor User Options Menu panel appears.
----------------------- CA-Endevor User Options Menu --------------------------

Option ===> 2
1 REPORTS - Build CA-Endevor Report Requests
2 ACMQ - CA-Endevor ACM Query Facility
3 DB2 BATCH - CA-Endevor for DB2 Batch Processing
4 ADD/UPDATE - CSP Extension Facility - Add/Update CSP Elements

5 RETRIEVE - CSP Extension Facility - Retrieve CSP Elements
6 DISPLAY - CSP Extension Facility - CSP Name Translation List
7 SUBMIT - CSP Extension Facility - Submit Utility
8 DCOMP - CSP Decomposition Utility

9 COMPARE - CSP MSL Compare Utility
Enter END to return to the CA-Endevor Primary Options Menu
Figure 4-101: CA-Endevor User Options Menu Panel – ACMQ Option

5. Type “2” at the Option line to select ACMQ.

not found
Note: The following screen image is presented for ACMQ processing. At SPIEGEL,
options “1” and “2” are applicable and are presented below.
CA-Endevor for MVS ACM Query Facility*
Select the Query Type:

1. ACM-Related FOOTPRINTed Components
2. ACM-Related Non-FOOTPRINTed Components
3. User-Related FOOTPRINTed Components
4. User-Related Non-FOOTPRINTed Components
5. User-Related OBJECTS
6. User-Related COMMENTS
Press PF3 to exit
* NOT FULLY IMPLEMENTED AT THIS TIME.
Figure 4-102: CA-Endevor for MVS ACA Query Facility Panel
3. Footprinted Component Relationships
----------------------- CA-Endevor User Options Menu -------------------------

Option ===> 1
CA-Endevor for MVS ACM Query Facility

Press PF3 to exit
Figure 4-103: CA-Endevor User Options Menu Panel – Footprinted Components Option
1. From the CA-Endevor User Options Menu panel, type “1” at the Option line. This
option lists footprinted component relationships, where both elements in the relationship
are Endevor managed.

not found
ACM-Related FOOTPRINTed Components
Element . . . . . RET00089
Type . . . . . . . COPY
Environment . . . *
System . . . . . . *
Subsystem . . . . *
Stage . . . . . . *
Printer id . . . .
Print Class . . .
Select the desired action

1 1. Display on screen
2. Send to printer
3. Generate SCL
4. Generate SCL in Batch
Press PF3 to exit
Figure 4-104: ACM-Related Footprinted Components Panel

2. The example above depicts a request to identify all relationships the Endevor copybook element RET00089
has with other Endevor elements (typically COBOL program elements).
BROWSE VAENDV3.S690.S1.ACMOUT Line 00000000 Col 001 079

********************************* Top of Data **********************************
CA-ENDEVOR/MVS ACM Query Facility PAGE # 1
Footprint==> * /* /* /CPY /LPS00089 /*
+=====+============+==========+==========+==========+==========+==========+
| Lvl | Element | Type | Environ | System | Subsys | Stage |
+=====+============+==========+==========+==========+==========+==========+
1 RET00089 COPY PROD RETL RET 2
2 AX117318 COBOL PROD RETL RET 2
2 AX117319 COBOL PROD RETL RET 2
******************************** Bottom of Data ********************************
Figure 4-105: ACMQ Query Results Panel

3. The result of the query is presented by ACMQ in the manner shown above.
Note: The display shows that two Endevor managed COBOL programs have been found, by an Endevor
Generate process, to be users of the Endevor COPY element RET00089.

not found
4. Non-Footprinted Component Relationships
In some cases, the component member in the relationship is not footprinted. Any of the
following situations could render that condition:
 The component member in the relationship is not Endevor controlled. For example, a COBOL program
uses a copybook that has not been placed into Endevor.
 The Endevor Generate processor has not yet been executed to capture component
relationships. A scan is run at the time of conversion to capture copybook relationships as
Non-Footprinted Component Relationships.
----------------------- CA-Endevor User Options Menu -------------------------

Option ===> 2
CA-Endevor for MVS ACM Query Facility

Press PF3 to exit
Figure 4-106: CA-Endevor User Options Menu Panel – Non-Footprinted Components Option
1. From the CA-Endevor User Options Menu panel, type “2” at the Option line. This
option lists ACM-Related Non-FOOTPRINTED Components.

not found
Since the component member may possibly not be an Endevor element, only member and
dataset information are appropriate for the selection criteria of the non-footprint component
relationship query. In the example below, we are providing the name of our copybook
member RET00089 and wild-carding the dataset name.
----------------------- CA-Endevor User Options Menu --------------------------
ACM-Related Non-FOOTPRINTed Components
Member . . . . . . RET00089
Dataset Name . . . *
Printer id . . . .
Print Class . . .
Select the desired action

1 1. Display on screen
2. Send to printer
3. Generate SCL
4. Generate SCL in Batch
To exit Non-FOOTPRINTed Member Query, press F3
Figure 4-107: ACM-Related Non-Footprinted Components Panel

2. The results of the query are displayed on the ACM-Related Non-FOOTPRINTED Components panel.
BROWSE VAENDV3.S690.S1.ACMOUT Line 00000000 Col 001 079

********************************* Top of Data **********************************
CA-ENDEVOR/MVS ACM Query Facility PAGE # 1
Non-Footprint==>RET00089 /*
+=====+============+==========+==========+==========+==========+==========+
| Lvl | Element | Type | Environ | System | Subsys | Stage |
+=====+============+==========+==========+==========+==========+==========+
1 MBR=RET00089 DSN=SCANNED.RESULT.COPY
2 AX117319 COBOL PROD CREDIT CREDIT 2
2 AX117393 COBOL PROD CREDIT CREDIT 2
2 A21173M1 COBOL PROD CREDIT CREDIT 2
2 A2117310 COBOL PROD CREDIT CREDIT 2
Figure 4-108: ACM Query Results Panel

3. The display above shows the first of several programs that use the copybook member RET00089.

not found
9. Endevor Reports
1. Requested Reports
Many standard reports are available from Endevor and can be run at any time.

OPTION ===> E


X - EXIT

1. At the Endevor Rel39 Selection Menu panel, enter Full Panel Endevor by typing “E”
on the option line.


-- -------- ----------------------------------------
2 QA QA ENVIRONMENT
******************************* Bottom of data *******************************
Figure 4-110: Endevor for OS/390 Environment Selection

environment by typing “1” on the option line. Any environment can be used to get into
the reports menu.
4

not found
Option ===> U

Figure 4-111: Endevor for OS/390 Primary Options Menu

3. At the Endevor for OS/390 Primary Options Menu panel, enter User Menu by typing
“U” on the option line.
------------------------- Endevor User Options Menu -------------------------

Option ===> 1
1 REPORTS - Build Endevor for OS/390 Report Requests
2 ACMQ - Endevor for OS/390 ACM Query Facility
3 DB2 BATCH - Endevor for DB2 Batch Processing
4 ADD/UPDATE - CSP Extension Facility - Add/Update CSP Elements

5 RETRIEVE - CSP Extension Facility - Retrieve CSP Elements
6 DISPLAY - CSP Extension Facility - CSP Name Translation List
7 SUBMIT - CSP Extension Facility - Submit Utility
8 DCOMP - CSP Decomposition Utility

9 COMPARE - CSP MSL Compare Utility
Enter END to return to the Endevor Primary Options Menu
Figure 4-112: Endevor User Options Menu

4. At the Endevor User Options Menu panel, enter Reports by typing “1” on the option
line.

not found
------------------------- ENDEVOR REPORTING INTERFACE -------------------------
OPTION ===>
1 MASTER - Build Master Control File report JCL

2 SMF - Build SMF historical report JCL
3 PACKAGE - Build Package report JCL
4 FOOTPRINT - Build Footprint report JCL
5 UNLOAD - Build Unload/Reload report JCL
6 SHIPMENTS - Build Package Shipment report JCL
E EDIT - Edit Report JCL

S SUBMIT - Submit Report JCL for Batch execution
Job statement information:
===> //USERID JOB (P970,01),'USERID',CLASS=C,

===> // MSGCLASS=S,NOTIFY=&SYSUID,REGION=6M
===> //*
===>
Figure 4-113: Endevor Reporting Interface Panel

5. The Endevor Reporting Interface panel appears.
The Endevor Reporting Interface panel shows the major reporting categories. Each
category provides several report types. For information about each of these, see the CA-
Endevor for MVS Reports manual.

not found
2. RMDS Reports
The following reports are run on a regular basis. The output is available in RMDS.
Table 5: RMDS Reports

RMDS
Number RMDS Description Job Name
6160 ENDEVOR CRISIS ACTIVITY FOR LAST 24 J289DCRP
HOURS
6161 ENDEVOR PRODUCTION ACTIVITY FOR LAST J289DPRP
24 HOUR

not found
10. How to Print Endevor Inventory - Compile Listing
Printing of Endevor inventory can be done with full panel Endevor in foreground or batch.

OPTION ===> E


X - EXIT

the option line.


-- -------- ----------------------------------------
2 QA QA ENVIRONMENT
******************************* Bottom of data ********************************

5

not found
Option ===> 3



OPTION ===> 1

REQUEST DATA SET:

TYPE ===> CNTL

DSNAME ===>


Press Enter.

not found
------------------------------- SCL GENERATION ------------------------------
OPTION ===> 10


APPEND: N

5. At the SCL Generation panel, select Print Member by typing “10” on the option line
------------------------------- PRINT MEMBERS -------------------------------

OPTION ===>
Blank - Member list B - Browse member P - Print member
FROM ISPF LIBRARY:

PROJECT ===> USERID
LIBRARY ===> ENDV
TYPE ===> CNTL
MEMBER ===> THRU MEMBER ===>
FROM OTHER PARTITIONED OR SEQUENTIAL DATA SET:

DATA SET NAME ===> 'PN.ENDEVOR.UNIT.SPGTST01.LISTLIB(M3706080)'
LIST OPTIONS:
Figure 4-119: Print Elements Panel

6. At the Print Members panel, enter “PN.ENDEVOR.UNIT.SPGTST01.LISTLIB(member
name)” in the Data Set Name field. Note: You can also enter a wildcard (member prefix
*) to print several members.

not found
BROWSE/PRINT --------------- MEMBER SELECTION LIST --------- Row 1 to 1 of 1
COMMAND INPUT ===> SCROLL ===> PAGE
FROM Data set: PN.ENDEVOR.UNIT.SPGTST01.LISTLIB
|------------------ F O O T P R I N T -------------------|
MEMBER SYSTEM SUBSYS ELEMENT TYPE VV.LL DATE TIME LD
P M3706080 LOGISTCS SPGTST01 M3706080 COBOLLE 01.02 28JAN02 15:43
******************************* Bottom of data ********************************
Figure 4-120: Member Selection List Panel

7. At the Member Selection List panel, select Print by typing “P” on the line next to the
member you wish to print.
Then, PF3 three times to get back to the Batch Options Menu screen.

OPTION ===> 3

REQUEST DATA SET:

TYPE ===> CNTL

DSNAME ===>


This job will go to the hold queue where it can be routed to the printer to get the actual
listing.

not found
11. How to Print Endevor Inventory - Program Source
Printing of Endevor inventory can be done with full panel Endevor in foreground or batch.
1. How to print the program source - batch

OPTION ===> E


X - EXIT

the option line.


-- -------- ----------------------------------------
2 QA QA ENVIRONMENT
******************************* Bottom of data ********************************

6

not found
Option ===> 3

Current environment: EDUCDEV


OPTION ===> 1

REQUEST DATA SET:

TYPE ===> CNTL

DSNAME ===>


Press Enter.

not found
------------------------------- SCL GENERATION ------------------------------
OPTION ===> 7


APPEND: N

5. At the SCL Generation panel, select Print Element by typing “7” on the option line
------------------------------ PRINT ELEMENTS -------------------------------

OPTION ===>
P - Print element M - Master C - Changes
PC - Print changes only
PS - Print element summary
PM - Print master information
PH - Print change history
FROM ENDEVOR:
ENVIRONMENT ===> DEVELOP
SYSTEM ===> LOGISTCS
SUBSYSTEM ===> SPGTST01
ELEMENT ===> C430710A
TYPE ===> *
STAGE ===> U U - UNIT N - NTGN
LIST OPTIONS:
WHERE CCID EQ ===>
BUILD USING MAP ===> Y (Y/N)

6. At the Print Elements panel, select the Element(s) you want to print by typing in the
Environment, System, Subsystem, Element, and Stage.

not found
PRINT ------------------------ ELEMENT SELECTION LIST ------ Row 1 to 1 of 1
ELEMENT TYPE ENVIRON S SYSTEM SUBSYSTEM VV.LL RC

P C430710A CNTL PROD P LOGISTCS LOGISTCS 01.00 0000
******************************* Bottom of data ********************************

7. At the Element Selection List panel, type one of the element display options listed below
on the line next to the element you wish to process:
P Print element
PC Print changes only (Helpful for program QA process.)
PS Print element summary
PM Print master information
PH Print change history

OPTION ===> 3

REQUEST DATA SET:

TYPE ===> CNTL

DSNAME ===>


listing.

not found
2. How to print the program source - foreground

OPTION ===> E


X - EXIT

the option line.


-- -------- ----------------------------------------
2 QA QA ENVIRONMENT
******************************* Bottom of data ********************************

7

not found
Option ===> 2

Current environment: EDUCDEV

3. At the Endevor for OS/390 Primary Options Menu panel, select Execute Foreground
Action Option by typing “2” on the option line.
-------------------------- Foreground Options Menu ----------------------------

Option ===> 7

7 PRINT - Print elements, changes and detail change history
Figure 4-133: Foreground Options Menu Panel

4. At the Foreground Options Menu panel, select Print Element by typing “7” on the
option line

not found
------------------------------ PRINT ELEMENTS -------------------------------
OPTION ===>
P - Print element M - Master C - Changes
PC - Print changes only
PS - Print element summary
PM - Print master information
PH - Print change history
FROM ENDEVOR:
ENVIRONMENT ===> DEVELOP
SYSTEM ===> LOGISTCS
SUBSYSTEM ===> SPGTST01
ELEMENT ===> C430710A
TYPE ===> *
LIST OPTIONS:
WHERE CCID EQ ===>

5. At the Print Elements panel, select the Element(s) you want to print by typing in the
Environment, System, Subsystem, Element, and Stage.
PRINT ------------------------ ELEMENT SELECTION LIST ------ Row 1 to 1 of 1

ELEMENT TYPE ENVIRON S SYSTEM SUBSYSTEM VV.LL RC

P C430710A CNTL PROD P LOGISTCS LOGISTCS 01.00 0000
******************************* Bottom of data ********************************

6. At the Element Selection List panel, type one of the element display options listed below
on the line next to the element you wish to process:
P Print element
PC Print changes only (Helpful for program QA process.)
PS Print element summary
PM Print master information
PH Print change history
After pressing enter, a message is shown that the element was printed.
Then, press PF3 five times to get to the Endevor Foreground Print Request Options
panel.

not found
----------------- ENDEVOR FOREGROUND PRINT REQUEST OPTIONS ------------------
OPTION ===> J
J - Submit job to execute (and delete) foreground PRINT requests

D - Delete PRINT requests (and do not perform PRINT actions)
K - Keep PRINT requests
PRINT OPTION:
SYSOUT CLASS ===> *

===> //USERIDB JOB (T370,00),'USERID',
Figure 4-136: Endevor Foreground Print Request Options Panel

7. At the Endevor Foreground Print Request Options panel, select Submit Job by typing
“J” on the option line. (“J” will automatically display when you enter this screen.) Replace
USERID in the job card with your user id. Press Enter.
listing.

not found
12. How to Compare Endevor Elements
Endevor Elements can be compared with Endevor Parallel Development Manager.

OPTION ===> P


X - EXIT

1. At the Endevor Rel39 Selection Menu panel, enter Parallel Development Manager, by
typing “P” on the option line.
-------------- Parallel Development Manager - Primary Option Menu -------------

Option ===> 1
0 DEFAULTS - Specify user session parameters

1 BUILD WIP - Build Work-in-Process (WIP) file
2 EDIT WIP - Edit Work-in-Process (WIP) file
3 MERGE - Merge Work-in-Process (WIP) file into OUTPUT source file
4 SUBMIT - Build job for batch submission
T TUTORIAL - Tutorial on how to use PDM
C CHANGES - New features for this release of PDM
Processing Mode:
Foreground or Batch ===> F (Foreground/Batch)
---------------------------- Batch Specification ------------------------------

Batch Request Data Set: Batch Options:
Project ===> Append or Replace ===> R (A/R)
Group ===>
Type ===>
Member ===>
Other partitioned or sequential data set:
Data Set Name ===>
Figure 4-138: Parallel Development Manager - Primary Option Menu Panel

2. At the Parallel Development Manager - Primary Option Menu panel, enter the Build
WIP option by typing “1” on the option line.

not found
Build WIP ----------------- WIP Specification Panel ---------------------------
Command ===>
Specify Work-in-Process ("WIP") library below, then press the ENTER key.
WIP Library:
Project ===> USERID
Group ===> ENDV
Type ===> CNTL
Member ===>
WIP Other partitioned or sequential data set:

Data Set Name ===>
Data set options:

If partitioned, replace like-named members ===> Y (Yes/No)
WIP Build options:

Number of Derivation files ===> 1 (1/2)
Create WIP ===> Y (Yes/No)
Automatically Merge ===> N (Yes/No)
Generate WIP reports ===> A (All/Summary/No)
Write stats to data set ===>
Figure 4-139: Build WIP - WIP Specification Panel

3. At the Build WIP - WIP Specification Panel, enter the WIP Library name (Note: If
you leave the member name blank, it will default to the Root element name.), select the
Number of Derivation Files, and enter a “Y” in the Create WIP field. For this example,
that was done by entering the following: “USERID.ENDV.CNTL” in the WIP Library
field, and a “1” in the Number of Derivation Files field.

not found
BUILD WIP ---------------- Root Specification Panel ---------------------------
Command ===>
Specify Root location below, then press the ENTER key.
Build Root from ===> E (Data set/ENDEVOR)
Root Library: Compare Columns:

Project ===> From ===> 7
Group ===> Through ===> 72
Type ===>
Member ===> Thru Member ===>
Root Other partitioned or sequential data set:

Data Set Name ===>
ENDEVOR: List Options:

Environment ===> DEVELOP Where CCID ===>
System ===> MISC CCID Type ===> A (Any/Base/Generate/
Subsystem ===> SPGTST01 Retrieve/Last action)
Element ===> PROGRAM1 Version ===> Level ===>
Type ===> COBOLLE
Stage ===> U U - UNIT N - NTGN
Figure 4-140: Build WIP - Root Specification Panel

4. At the Build WIP - Root Specification Panel, enter the Root location. This is the “old”
element name. For this example, that was done by entering the following: an “E” in the
Build Root from field, a “7” in the From field, a “72” in the Through field, and the
Endevor Location in the Endevor fields.

not found
Build WIP ------------- Derivation 1 Specification Panel ----------------------
Command ===>
Specify Derivation 1 location below, then press the ENTER key.
Build Derivation 1 from ===> E (Data set/ENDEVOR)
Derivation 1 Library:
Project ===>
Group ===>
Type ===>
Member ===> Thru Member ===>
Derivation 1 Other partitioned or sequential data set:

Data Set Name ===>
ENDEVOR: List Options:

Environment ===> DEVELOP Where CCID ===>
System ===> MISC CCID Type ===> A (Any/Base/Generate
Subsystem ===> SPGTST02 Retrieve/Last action)
Element ===> PROGRAM2 Version ===> Level ===>
Type ===> COBOLLE
Stage ===> U U - UNIT N - NTGN
Figure 4-141: Build WIP - Derivation 1 Specification Panel

5. At the Build WIP - Derivation 1 Specification Panel, enter the Derivation 1 location.
This is the “new” element name. For this example, that was done by entering the
following: an “E” in the Build Derivation 1 from field, and the Endevor Location in the
Endevor fields.

not found
-------------- Parallel Development Manager - Primary BUILD WIP Complete
Option ===> 2
0 DEFAULTS - Specify user session parameters

1 BUILD WIP - Build Work-in-Process (WIP) file
2 EDIT WIP - Edit Work-in-Process (WIP) file
3 MERGE - Merge Work-in-Process (WIP) file into OUTPUT source file
4 SUBMIT - Build job for batch submission
T TUTORIAL - Tutorial on how to use PDM
C CHANGES - New features for this release of PDM
Processing Mode:
Foreground or Batch ===> F (Foreground/Batch)
---------------------------- Batch Specification ------------------------------

Batch Request Data Set: Batch Options:
Project ===> Append or Replace ===> R (A/R)
Group ===>
Type ===>
Member ===>
Data Set Name ===>
Figure 4-142: Parallel Development Manager - Primary Option Menu Panel

6. At the Parallel Development Manager - Primary Option Menu panel you will receive a
message saying “BUILD WIP Complete”. Enter Edit WIP, by typing “2” on the option
line.
Edit WIP -------------------- Edit - Entry Panel ------------------------------

Command ===>
ISPF Library:
Project ===> USERID
Group ===> ENDV
Type ===> CNTL
Member ===> (Blank or pattern for member selection list)

Data Set Name ===>
Figure 4-143: Edit WIP - Edit - Entry Panel

7. At the Edit WIP - Edit - Entry Panel, either enter the WIP library member name in the
ISPF library member field, or leave the ISPF library member field blank to go to the Edit
WIP - Member Selection List Panel. For this example, the ISPF library member field
was left blank.

not found
Edit WIP -- USERID.ENDV.CNTL -------------------------------- ROW 00001 OF 00072
Name Prompt Size Created Changed ID
C045A095
C045A930
C045B095
C045B930
C045C095
C045C930
DA124XR
DCD0000
DCD0001
DCD0005
DCD0010
DCD0020
DCD0100
DCD0105
DCD0110
DCD0120
DCD0125
DCD0130
DCD0135
DCD0150
DCD0155
Figure 4-144: Edit WIP - Member Selection List Panel

8. At the Edit WIP - Member Selection List panel, select the member by typing “S” on the
line next to the desired member name.

-------------------------------------------------------------------------------
EDIT USERID.ENDV.CNTL(PROGRAM1) - 01.00 Columns 00001 00072
Command ===> WIPCHANG Scroll ===> CSR
****** ***************************** Top of Data ******************************
000001 *************** PARALLEL DEVELOPMENT MANAGER WIP SUMMARY ***************
000002 ** *
000003 ** ROOT: DEVELOP /U/MISC /SPGTST01/COBOLLE *
000004 ** DERIVATION 1: DEVELOP /U/MISC /SPGTST02/COBOLLE *
000005 ** DERIVATION 2: NOT USED *
000006 ** *
000007 ** ROOT:PROGRAM1 01.00 DER1:PROGRAM2 01.00 DER2:NOT USED *
000008 ** *
000009 ** NUMBER OF WIP RECORDS...... 47 *
000010 ** NUMBER OF DELETED RECORDS... 2,DER1 2,DER2 0,COM 0 *
000011 ** NUMBER OF INSERTED RECORDS.. 2,DER1 2,DER2 0,COM 0 *
000012 ** NUMBER OF CONFLICTS............ 0 *
000013 ** COMPLEXITY FACTOR................ 1 *
000014 ** BUILD RETURN CODE............... 0 *
000015 ** *
000016 ******* ----+----1----+----2----+----3----+----4----+----5----+----6----
000017 IDENTIFICATION DIVISION.
000018
000019 % I-1 PROGRAM-ID. PROGRAM2.
Figure 4-145: Parallel Development Manager WIP Summary Panel

9. At the Parallel Development Manager WIP Summary panel, select a display of only
the changed fields, by typing “WIPCHANG” on the command line.

not found
-------------------------------------------------------------------------------
EDIT USERID.ENDV.CNTL(PROGRAM1) - 01.00 4 CHANGES FOUND
****** ***************************** Top of Data ******************************
- - - - - - - - - - - - - - - - - - - 18 Line(s) not Displayed
000019 % I-1 PROGRAM-ID. PROGRAM2.
000020 % D-1 PROGRAM-ID. PROGRAM1.
000033 % I-1 COPY I921CPY2.
000034 % D-1 COPY I921CPY1.
****** **************************** Bottom of Data ****************************
Figure 4-146: Parallel Development Manager WIP Summary (Changes only) Panel
10. The Parallel Development Manager WIP Summary (Changes only) panel, will use the
ISPF exclude command to display only the changed fields.

not found
5. Retrofits
The following section explains what a retrofit is and how to respond to a retrofit.
1. What is a Retrofit?
A Retrofit is an automated action taken by Endevor to reduce program regressions due to concurrent
development activity.
Changes introduced into production must be found within the versions of the element in any stage/track prior to
PSTG. If not, then an automated merge action is performed/attempted by Endevor to retrofit the production
changes.
The following are the steps taken by Retrofit:

1) A Retrofit will be triggered by the promotion of software changes to the PSTG stage, from the ACPT stage.
The targeted areas of impact from a Retrofit are the ASTG, ACPT, UNIT and NTGN stages.
2) The Endevor Retrofit process examines the targeted areas. A search is made for changed versions of the
software. If none are found, then Retrofit processing is completed.
3) The Endevor Retrofit process uses IBM’s SUPERC to compare a PROD version to a DEVELOP or QA
version. The comparison determines whether a version in the target area contains the promoted element
changes. If it does, then Retrofit takes no action on that version.
4) When a version in a target area is missing the promoted changes, then the following steps may be taken:
a) The version is removed from Endevor by the Retrofit process and written to a Retrofit dataset.
b) An automated merge is made by the process to retrofit the changes into the removed version. The
merged output is placed into a second Retrofit dataset.
c) If the path for the Retrofitted element is available in the UNIT stage, the Endevor Retrofit process will
re-introduce the merged element back into the UNIT stage of Endevor. An automatic compilation
occurs. If multiple elements are retrofitted, the one at the highest stage is allowed to be re-introduced
into the UNIT stage.
d) A notification is prepared for each impacted developer.
e) The developer must execute the appropriate steps outlined in “Section Error: Reference source not
found Error: Reference source not found”.
f) Unit testing must be conducted again.
g) Endevor packages that included the removed elements must be re-examined. These packages must
either be edited to exclude the removed member or be rescheduled to wait for the Retrofitted elements
to “catch up” to the stage the package is working with.
If a developer has the Retrofitted element signed out and has not yet re-introduced it into CA-
Endevor, then the developer receives notification. In this case, the developer is responsible for
“retrofitting” his code.

not found
2. Responding to a retrofit
If you receive notification that an element has been retrofitted, use one of the tables below to
determine an appropriate course of action.
Table 6: Retrofit Course of Action
Retrofit successfully merged and Added your source into stage UNIT
Step Description
1. Examine the changes in the source Added into UNIT, make corrections and RE-
GENERATE the program if necessary.
2. Conduct unit testing on the program.
3. Follow normal measures to promote to NTGN.
Retrofit successfully merged, but could not Add your source into stage UNIT
Step Description
1. Locate the dataset where Retrofit left your source code.
2. Examine the changes in the source and make corrections if necessary.
3. Add your successfully merged source back into the UNIT stage. Either wait
until the occupant in your chosen subsystem moves forward or Add into the
UNIT stage using a different subsystem.
Retrofit could not successfully merge and Add your source into stage UNIT
Step Description
1. Locate the dataset where Retrofit left your source code.
2. Choose a merger tool: CA-PDM or other.
3. Use the merger tool to merge the changes with those recently installed into
PROD. For PDM, the “root” is the -1 level in PROD, “derivation 1” is the
current level in PROD and “derivation 2” is your copy of source.
4. Resolve conflicts reported from the merger tool.
5. Add your merged source into the UNIT stage.

3. Controlling Program Attributes
Each developer may control program attributes by managing the program’s OPTIONS
element within Endevor. Attributes controlled by the OPTIONS element include virtually
every aspect of the program except language. (The Endevor element type specifies language.)
The following section presents the OPTIONS element content and how developers may
manage them.
Note: Since the OPTIONS element is used as input to the Endevor generate, the OPTIONS
element must be moved to production, either in a package with the associated
program, or in a package that will move ahead of the associated program.
4. The OPTIONS element

An example OPTIONS element is shown below:
DB2 = 'Y'
COBOL-COMPILER = COBOLLE
LINK-PARMS = 'LET,LIST,XREF,MAP,RMODE=ANY,AMODE=31'
COBOL-COMPILER-PARMS = 'NOADV,APOST,LIB,MAP,OFF,',
'OPTIONS,REN,RES,NOSEQ,VBREF'
PROD-BIND-TYPE = COMMON
Each program at Spiegel may have its own OPTIONS element to provide specific Generate
attributes to Endevor. For example, if program M370100 is a COBOL element; then
M370100, with content similar to the example above, may be defined as element type
OPTIONS.
More OPTIONS element examples, as mentioned in Error: Reference source not found Error:
Reference source not found can be found in Endevor. They can be viewed in
PROD/P/MISC/MISC, or by browsing PN.ENDEVOR.PROD.OPTIONS.
Table 7: OPTIONS Element Examples in Endevor
Element Description
Name
EXABDB2 ASSEMBLER, DB2
EXABDSN ASSEMBLER, DB2, DSNA
A
EXACAIMS ASSEMBLER, DB2, AIMS
EXACCSS ASSEMBLER, DB2, CSS
EXACOES ASSEMBLER, DB2, OES
EXCAIMDP COBOL, DB2, DSNA
EXCCCAIM COBOL, DB2, CICS, DSNA, AIMS
EXCCCCO COBOL, DB2, CICS, COMMON
M
EXCCCCSS COBOL, DB2, CICS, CSS
EXCCCOES COBOL, DB2, CICS, DSNP, OES
EXCCCOM COBOL, DB2, CICS, DSNA, COMMON
2

Element Description
Name
EXCCCSS2 COBOL, DB2, CICS, COMMON, CSS,
ORDNTRY
EXCCSSDA COBOL, DB2, CICS, DSNP-DSNA
EXCDSNA COBOL, DB2, DSNA
EXCDSNAI COBOL, DB2, DSNA, IDMS
EXCDSNA2 COBOL, DSNA
EXCDSNP COBOL, DB2, DSNP
The content of the OPTIONS element may contain multiple key words and values. Lines may
be entered in free form format and may be continued when necessary by leaving a comma (,)
at the end of a line. A quote character (either single or double quote) must surround values
that contain blanks or special characters. The OPTIONS element syntax is described below:
Table 8: OPTIONS Element Member Syntax
Key Word Values and description
ASSEMBLER-PARM The parameter string for the Assembler.
Example: “NOADV,APOST,LIB,NOSEQ,S,ZWB”
CICS “Y” the program is a CICS program; or “N” the program is a
batch program.
Defaults to “N”.
CICS-TRN-PARMS CICS translator parameter string.
COBOL-COMPILER “COBOLII” – for COBOLII programs (only valid in CRISIS
environment)
“COBOLLE” – for COBOLLE programs
COBOL-COMPILER- The parameter string for the Compiler. Defaults to
PARMS “LIST,NOADV,LIB”
DB2 “Y” the program contains DB2 SQL statements; or “N” – not DB2.
Defaults to “N”.
DB2-PRE-COMPILER- The parameter string for the DB2 precompiler.
PARMS Defaults to
“HOST(IBMCOB),APOST,APOSTSQL,SOURCE,XREF” for
COBOL LE programs, and to
“HOST(COB2),APOST,APOSTSQL,SOURCE,XREF” for
COBOL II.
IDMS “Y” the program contains IDMS statements; or “N” the
program does not contain IDMS statements. Defaults to “N”.
LINK-PARMS The parameter string for the Link Editor. Defaults to
“XREF,LIST,LET”.
PROD-CICS-LIBRARY Valid for programs with the EBI and SPG processor groups
only. (NNI uses only one production CICS load library).
Specifies one or more production CICS load libraries where
the load module must be copied.
For batch programs, the default value is
PROD-CICS-LIBRARY = BATCHLIB.

Any program, CICS or Batch, can have values specified

according to the program’s processor group.
For processor group EBI, the valid values are:

 CICSPCAT for
PN.ENDEVOR.PRODEBI.LOADPCAT
 CICSPCFC for
PN.ENDEVOR.PRODEBI.LOADPCFC
 CICSPDB2 for
PN.ENDEVOR.PRODEBI.LOADPDB2
 BATCHLIB for PN.ENDEVOR.PRODEBI.LOADLIB
For processor group SPG, the valid values are:

 CICSAIMS for
PN.ENDEVOR.PRODSPG.LOADAIMS
 CICSCOMN for
PN.ENDEVOR.PRODSPG.LOADCOMN
 CICSCSS for PN.ENDEVOR.PRODSPG.LOADCSS
 CICSOES for PN.ENDEVOR.PRODSPG.LOADOES
 BATCHLIB for PN.ENDEVOR.PRODSPG.LOADLIB
Examples:
PROD-CICS-LIBRARY = “CICSAIMS CICSOES”
PROD-CICS-LIBRARY = CICSCOMN
Stagename-BIND-TYPE Specifies the DB2 subsystem(s) under which the plan and/or
package will be bound. Each value of bind-type is a value
from column (2) of a Bind table. For Bind tables, see members
NNIBINDS, EBIBINDS and SPGBINDS in
PN.ENDEVOR.ADM2.TABLE. For assistance in determining
which bind-type is needed for your particular module, please
reference the comments at the beginning of the bind table.
The complete syntax is:

Stagename-BIND-TYPE = 'bind-type1 bind-type2 .....bind-
typeN'
Although this syntax allows for multiple bind types, NNI and
EBI do not currently have a need for more than one. In select
circumstances multiple bind types may be warranted a Spiegel.
For example, an online program at Spiegel may need to be
bound under OES and CSS but not AIMS as shown in the third
example below. The bind-type is intended for primary use in
the Production stage or for use with distributed processing in
all stages. A production bind type is required when an element

is generated to avoid an Endevor syntax error. A stage name
prefix must always be used. For example:
PROD-BIND-TYPE = DSNP will cause a non-distributed

batch bind under collection COLBTCH to occur in DSNP.
PROD-BIND-TYPE = ORDNTRY will cause a non-

distributed online bind under collection COLOES to occur
in DSNP.
PROD-BIND-TYPE = ‘CSS ORDNTRY’ will cause non-

distributed online binds to occur under online collections
COLCSS and COLOES in DSNP.
PROD-BIND-TYPE = COMMON will cause online binds

to occur in DSNA under collections COLAIMS, COLCSS
and COLOES and in DSNP under collections COLAIMS,
COLCSS, and COLOES. This bind type will produce six
separate binds.
UNIT-BIND-TYPE = SPGTST01-DB2X will override the

unit bind type of SPGTST01 causing binds to occur (online
if CICS=Y, batch if CICS=N) in DB2T under collection
DB2TQA for batch or COLTST01 for online. In addition a
remote bind will occur in DB2X under collection DB2TQA
for batch, COLTST01 for online modules.
Stagename-BIND-TYPE Note: in the future, more than one bind-type may be used. If
(continued) this is the case, then at least one space must separate them, and
the list of bind-types must be enclosed in quotes. For example:
PROD-BIND-TYPE = ‘AIMS-DSNP AIMS-DBP1’ will

override the Endevor production bind type causing a local bind
under collection COLAIMS in subsystem DSNA to occur with
two remote binds being produced in DSNP and DBP1.
When you are testing a distributed module in test, be aware of

what region your bind will occur in on the remote subsystem.
For example, if you are testing a distributed module in
EBITST01 that will access tables at NNI, your bind type
would be EBITST01-DBT1. Endevor determines which tables
at NNI you will utilize. Since EBITST01 is the problem
environment at EBI, Endevor will bind the distributed package
in the distributed region at NNI, NNITST01. To determine
which distributed tables your plan will use, locate the

DB2_CREATOR_ID column in the Endevor bind table under
the Endevor subsystem you are working in. For example, the
distributed creator id for EBITST01-DBT1 is DBT1T.
For more information on the bind-type parameter and/or its

uses in a distributed capacity, please contact a member of the
DBA group.
Stagename-PLAN-NAME In January 2003, a new Spiegel Endevor bind table was put
8
into place that allowed for distinct DB2 batch collections in
the test environments. This means that Programmer “A” who
binds M1234 in SPGTST02 will no longer overlay M1234
bound by Programmer “B” utilizing the BND screens. To
make this happen, distinct batch collections for each Endevor
region were created. They are as follows:
a) SPGTST01 db2tqa
b) SPGTST02 db2ttst2 (used to be
db2ttest)
c) SPGTST03 db2xqa
d) SPGTST04 db2xprob
e) SPGTST05 db2ttst5 (used to be
db2ttest)
f) SPGTST06db2ttst6 (used to be db2ttest)
g) SPGTST07 db2tprob
h) SPGTST08 db2xtest
Although batch plans in SPGTST02, SPGTST05 and

SPGTST06 will have the same name, i.e. M1234, DB2 is
smart enough to match the timestamp within the load module
to the timestamps for all packages bound under that plan.
Note, this change does NOT allow the same module to be
checked out in multiple Endevor regions simultaneously.
It does, however, allow three different plans to be created
within Endevor at different times with the same name but
distinct packages.
Batch plan suffixes will now be enforced. For example, plans

bound in SPGTST01 will begin with a "U" automatically.
The UNIT-PLAN-NAME parameter need only be used when
the default is not desired.
As of July 2003, the NNI DB2 environment utilizes distinct

suffixes for every test region. (Note, the Spiegel and EBI
regions will be converted to distinct batch plan names for all
8
All online modules are bound as packages and not plans. The Stagename-PLAN-NAME parameter applies to
batch plans only.

TEST regions at a later date.) Assume that you are working
on module PEP015. This plan will take on different names
depending on the environment chosen. For example,
Endevor Env Old New Batch

Subsystem Plan Plan Collection
Name Name
NNITST00 PROB PEP015T BEP015
DBT1T
NNITST01 TEST PEP015T1 MEP015
DBT1T1
NNITST02 TEST N/A * NEP015
DBT1T2
NNITST03 TEST PEP015T3 TEP015
DBT1T3
NNITST04 QA PEP015T4 UEP015
DBT1T4
NNITST05 TEST N/A REP015
DBT1T5
PROD PROD PEP015 PEP015
COLBTCH
PROD PROD PEP015 PEP015
DBT1C
* The T2 and T5 regions were created in June of 2003 and as

a result do not have “old” plan names.
When you code the control cards for the DSN Command
processor, you will need to modify your plan name to match
the region in which you are working. For example, if I want
to execute program PEP015 in NNITST04 my control card
would look like the following:
RUN PROGRAN(PEP015) PLAN(UEP015). These changes
will prepare NNI for the implementation of Call Attach in
2004.
EBI will also take on the same structure as Spiegel, with
distinct collections being utilized in the TEST environment
These changes will ready EBI for the implementation of Call
Attach.
Endevor Env Old New Old New

Subsystem Plan Plan Batch Batch
Name Name Collection Collection
EBITST01 PROB M1234 B1234 COLTBTCH
COLBBTCH

EBITST02 TEST M1234 M1234 COLTBTCH
COL2BTCH
COL3BTCH
EBITST04 QA Q1234 U1234 COLQBTCH
COLQBTCH
COL5BTCH
PROD PROD M1234 M1234 COLPBTCH
COLPBTCH
PROD PROD M1234 M1234 COLEBTCH
COLEBTCH
When you code the control cards for the DSN Command
processor, you will need to modify your plan name to match
the region in which you are working. For example, executing
program M1234 in EBITST01 would yield the following
control card:
RUN PROGRAM(M12324) PLAN(B1234).

Processors will search for an OPTIONS element in the same manner it searches for COPY
elements - by searching through a library concatenation. The table below shows the effect of
the OPTIONS element’s location on Endevor generates.
Table 9: OPTIONS Element Stages
OPTIONS Controls Generates for programs in these stages
element in this UNIT NTGN ASTG ACPT PSTG ETST
stage
UNIT Y
NTGN Y Y
ASTG Y Y Y
ACPT Y Y Y Y
PSTG Y Y Y Y Y
PROD Y Y Y Y Y Y
ETST Y
EMER Y

5. Managing the OPTIONS content
As indicated in the table above, OPTIONS elements located in production may be used
anywhere in the Endevor map to provide the specific attributes for program generation.
Therefore, developers need not concern themselves with the OPTIONS element until it
becomes necessary to change the way a program is generated by Endevor. Quick-Edit can be
used, since the OPTIONS element is an Endevor element.

Command ===> _____________________________________________ Scroll ===> PAGE
Element Options:

-- ---------- ---------- -------- ----------- ----- -------- --------- -----
E_ CSSB0010 OPTION PROD P CREDIT CREDIT 01.02
Figure 4-147: Element Selection List – OPTIONS Element
CSSB0010 TO: DEVELOP/U/CREDIT/NNITST01/OPTION Map Searched

****** ***************************** Top of Data ******************************
==MSG> *---------------------------------------------------------------------*
==MSG> * *
==MSG> * This element was retrieved by searching the environment map. *
==MSG> * The element was taken from environment PROD, stage P, system *
==MSG> * CORP, subsystem CSS, type OPTION. *
==MSG> * *
==MSG> *---------------------------------------------------------------------*
000001 * OPTION CARD FOR ELEMENT: CSSB0010 TYPE: COBOLLE
000002
000003 CICS = Y
000004
000005 DB2 = Y
000006
000007 COBOL-COMPILER-NAME = COBOLLE
000008
000009 IDMS = Y
000010
000011 LINK-PARMS = 'LET,LIST,XREF,MAP,RMODE=ANY,AMODE=31,APOST'
000012
000013 COBOL-COMPILER-PARMS = 'ADV,APOST,AWO,DATA(31),DYN,',
000014 'FSRT,LIB,MAP,NUMPROC(MIG),',
Figure 4-148: ISPF Edit Session – Changing an OPTIONS Element

In the example above, the OPTIONS element is being changed. The termination of the ISPF
edit session causes the modified OPTIONS element to be placed into the UNIT stage.

Normal promotions through the life cycle will cause the OPTIONS element to be promoted to
production.

not found
6. DB2 Overview
1. Add / Update DCLGEN
When a developer requests a new table or an alteration to an existing table, the DBA’s will
make the change and generate a DCLGEN and place it in a library not controlled by
ENDEVOR. They will then notify the developer that the change was complete and the
location of the new/modified DCLGEN (dataset name and member name). The developer has
the responsibility of creating a COPY element in the UNIT stage of the DEVELOP
environment (or the emergency equivalent).

not found
2. DB2 Bind Overview
DBA’s at Spiegel indicated that the execution of one of their REXX routines must be included
in the Endevor generation of DB2 binds. This REXX exec allows the DBA’s to override bind
parameters at the package level by adding rows to internal tables designed for this bind
process. Initially the existing REXX routine named DB2BINDC was used with Endevor
processors for DB2 binds. After initial trials, the DBA’s realized that the REXX routine
needed to behave differently under Endevor, so they made a copy of DB2BINDC, modified it,
and named it DB2BINDE. Like the original version, DB2BINDE requires eleven parameters
when called. The issue under Endevor, then, became how Endevor should construct the
eleven parameters when calling DB2BINDE. The names of the eleven parameters are:
1. DB2SS 5. PLAN_NAME 9. ALLOC_IN_CLIST

2. DB2_ENV 6. MEMBER_NAME 10. DB2_OWNER
3. NEW_CALL_ATTCH 7. RDB2 11. DB2_CREATOR_ID
4. DISTRIB 8. CICS
To provide Endevor processors with values for the eleven parameters of DB2BINDE, three
“DB2BIND tables” were created – one for each of 3 Endevor processor groups - NNI, EBI
and SPG. The physical locations of the 3 “DB2BIND tables” are members NNIBINDS,
EBIBINDS and SPGBINDS of PN.ENDEVOR.ADM2.TABLE. The tables are managed as
Endevor elements in the ADMIN system as type TABLE. The content of each “DB2BIND
table” consists of 4 columns of data that Endevor uses to select records (or rows) from the
table for processing. The 4 columns are referenced as “SEARCH-KEY-FIELDS” in the table
and contain:
1. C1STAGE – the Endevor stage name
2. BIND-TYPE – defaults to the Endevor subsystem name, but can be overridden by
OPTIONS syntax. A PROD-BIND-TYPE entry is required for all DB2 programs.
3. CICS - a “Y” or “N” value derived from the OPTIONS.
4. ELEMENT – the name of the Endevor element. An asterisk can be used on the
“DB2BIND table” as a wildcard.
Also on each record (or row) of the “DB2BIND table” are the parameters for a call to
DB2BINDE.
To make use of the “DB2BIND table”, and to complete the processing for a DB2 bind, a REXX exec named
DB2BIND@ is employed by Endevor processors to perform the following steps:
1. Receives parameters from the Endevor processor:
a. Stage name
b. System name
c. Subsystem name
d. Element name
e. Processor group
f. Userid of person executing the Endevor action
g. DBRM library name
h. Endevor Package name
2. Reads the entire “DB2BIND table” into a REXX Stem array.
3. Reads all OPTIONS into a REXX Stem array.

not found
4. Examines the OPTIONS statements and INTERPRETs each one. The INTERPRET causes each
OPTIONS statement (sometimes covering multiple lines) to become REXX statements, as if they were
lines of code within DB2BIND@. An OPTIONS statement like “CICS = Y”, when INTERPRETed for
example, creates the REXX variable CICS, and gives it a value of “Y”.
5. Determines whether a “BIND-TYPE” clause was specified in the OPTIONS. If yes, then each value of
“BIND-TYPE” is used to search thru the “DB2BIND table”. If any value of “BIND-TYPE” contains a
dash (“-”), then the portion of “BIND-TYPE” that precedes the dash is used for an additional search
through the “DB2BIND table”. For example, a value of “SPGTST01-DB2X” for “BIND-TYPE” causes
a search through the table for the value of “SPGTST01-DB2X”, and a second search through the table
for the value of “SPGTST01”.
Otherwise, if no value for “BIND-TYPE” is found in the OPTIONS, then the Endevor subsystem is
used as the value for BIND-TYPE in the search thru the “DB2BIND table”. A PROD-BIND-TYPE is
required.
When values for Endevor Stage, BIND-TYPE, CICS and element name match the first four columns of
a “DB2BIND table” record (or row), then a match is encountered. Table entries can include wild-card
entries (frequently used for element name) to increase the number of matches during the “DB2BIND
table” search.
6. For each match, DB2BIND@ constructs a jobstream with 4 or 5 steps, and submits the jobstream to the
internal reader. The jobstream is constructed from the following parts:
a. JCL constructed by the DB2BIND@ REXX containing the jobcard and a jobstep that calls
DB2BINDE.
b. Commented lines of JCL that provide names of the Endevor element, stage, package name and
userid of the person who performed the Endevor action.
c. A DB2 bind step also supplied from the DB2BIND@ REXX.
d. The dd statement for the DBRMLIB is placed into the JCL.
e. Two similar jobsteps are added to execute the Spiegel programs M3125000 and M3125010.
M3125000 grants authorization for the newly-bound plan while M3125010 saves old EXPLAIN
information while storing new EXPLAIN information in the PLAN_TABLE. The parameters for
these programs are derived from the merger of OPTIONS and “DB2BIND table” records (or rows).
The first character of the parameter string is derived from the DB2-ENV value, according to the
following:
Table 10: DB2 Parms
DB2- Parm
#
ENV value
1. #### P
2. DVLP T
3. EDUC Q
4. PROB B
5. PROD P
6. QA Q
7. TEST T
8. TST1 T
9. TST2 T
10. TST3 T
The remaining portions of the parameter string are constructed from

DB2SS PACKAGE-NAME “,” PLAN-NAME (if batch),

not found
Or,
DB2SS PACKAGE-NAME (if CICS)
f. If the Endevor stage is “PROD” or “EMER” then a final step is added to the JCL. The step
utilizes a Spiegel PROC named “WTO” to send an alarm to operations if any previous step fails.
7. OPTIONS syntax may override values from the “DB2BIND table”. If an override must be applied at
only one Endevor stage, then an Endevor stage name prefix must be used in the syntax. Otherwise, no
Endevor stage name prefix should be used. For example, if the BIND-TYPE must be “ABC” in the
UNIT stage only, then code:
UNIT-BIND-TYPE = ‘ABC’
Otherwise, if the BIND-TYPE must be “ABC” at all Endevor stages, then code:
BIND-TYPE = ‘ABC’
Examples of variables that can be overridden by OPTIONS statements:

a. BIND-TYPE – by default the BIND-TYPE is the Endevor subsystem. OPTIONS syntax may
assign one or more values, each of which are searched through the “DB2BIND table”. Each value
specified, however, must be separated from the others by at least one space, and each value must be
found on the “DB2BIND table”. For example:
PROD-BIND-TYPE = 'CSS AIMS-DBP1'
b. Stagename-PLAN-NAME - the DB2 Plan name. Example OPTIONS syntax:
Stagename-PLAN-NAME = L1234567. Note, this parameter is only needed in rare
circumstances where the Endevor default plan name is not desired.
3. DB2 Bind Job Names

The Endevor generate processor creates ‘Bind Jobs’ thst run independently of the processor
itself.
Binds in the UNIT stage behaves differently than binds for all other stages. JOB names for
bind JCL in UNIT consist of a user's TSO ID plus one letter. The SYSOUT is displayed in
SDSF, and not saved in SAR.
The JOB name for bind JCL in all other stages is saved in SAR and uses the pattern:
DB2BND#$
# = N for NTGN $ = N for NNI
A for ASTG S for Spiegel
Q for ACPT E for Eddie Bauer
P for PROD and EMER
Binds are not executed for PSTG or ETST.
The following table summarizes bind job names for all stages.
UNIT NTGN ASTG ACPT PROD and
EMER
Spiegel TSO- DB2BNDNS DB2BNDAS DB2BNDQS DB2BNDPS
USERID+S
Eddie Bauer TSO- DB2BNDNE DB2BNDAE DB2BNDQE DB2BNDPE
USERID+E
Newport TSO- DB2BNDNN DB2BNDAN DB2BNDQN DB2BNDPN

not found
News USERID+N

not found
4. DB2 Bind Failure
The notification of production bind failure works as follows:
When a production DB2 bind job (See Section V Endevor Batch Jobs in Appendix A for DB2
bind job names.) fails with a return code equal to or greater than 8, a ‘WTO’ (Write To
Operator) step will execute, generating the following message to the computer operator on the
console of the LPAR in which the job failed:
.ENDEVOR DB2BIND FAILURE PROD M788TO05 PR02052002RC*

.REPLY C TO CONTINUE PROCESSING OR R TO REPEAT DISPLAY
The computer operator at that time will have to manually respond to the outstanding prompt.
This prompt notifies the operator of the bind failure, the fact that it failed in production, the
element name, and the Endevor package associated with that element.
In addition to the console message described above, the following message will be displayed
on the Patrol Explorer Operator Screen:
DB2 Bind failure – Endevor DB2 bind has failed, immediate action is required – contact
application on call.
After the operator responds to the prompt, the job will continue on to failure. At job
conclusion (failure) an impact ticket will be automatically generated with the same
notification of failure. The ticket will also contain the system and job name within it. At this
point the computer operations personnel will have been alerted and on notice of what has
happened, and that there is a problem that needs immediate attention, thus triggering the
existing computer operations notification and escalation procedures. Simultaneously with the
above, email notifications will be sent to the DBA’s and Production Services for follow up.
Production binds for Eddie Bauer and Newport News spawn binds to their education and
training regions, respectively. Test plans/packages are bound in DSNT and DBT1 using the
production DBRM of the new production module. These additional binds keep the education
and training regions in synch with production. The newest application changes are
implemented in these regions as soon as they occur. In the event one of these test binds fails,
a write to operator step will execute generating the following message to the computer
operator on the console of the LPAR in which the job failed:
.ENDEVOR DB2BIND FAILURE TEST M788TO05 PR02052002RC*

.REPLY C TO CONTINUE PROCESSING OR R TO REPEAT DISPLAY

not found
Like production, the operator will have to manually respond to the outstanding prompt. This
prompt notifies the operator of the bind failure. In addition to the message listed above, the
following alert will be written via Auto Operator to the Patrol Explorer Operator Screen:
Test DB2 Bind Failed. Do not call Applications. Email the on call DBA found in
DB2SYS in QREF.
An impact ticket will not be generated in the event a test bind fails. Operations should email
the on call DBA with the name of the Endevor package, the DB2 module name, bind job
name and number, and any relevant error information. The on call DBA will take
responsibility for investigating the bind failure and manually rebinding the test plan/package.

not found
5. Backout of Packages containing DB2 Programs
When a production package, containing a DB2 program is backed out, a bind will
automatically occur as part of the backout.
In the event an -805 is received on a backout, the on-call DBA should be contacted. Note:
This is for “PR” packages only. If you have -805 problems with other packages see Section
Error: Reference source not found Error: Reference source not found first.
See Section Error: Reference source not found Error: Reference source not found for more
information.

not found
7. Handling Production Elements
Some Endevor functions are handled differently once an element is in production. This
section described those differences.
1. How to Archive a Production Element that is no longer used
This procedure has not been defined at this time.

not found
2. How to Browse a Production Compile Listing

OPTION ===> E


X - EXIT

1. At the Endevor Rel39 Selection Menu panel, enter Full Panel Endevor, by typing “E" on
the option line.


-- -------- ----------------------------------------
2 QA QA ENVIRONMENT
******************************* Bottom of data ********************************

2. At the Endevor for OS/390 Environment Selection panel 9, enter the Prod Environment
9
not found
Option ===> 1

Current environment: PROD

3. At the Endevor for OS/390 Primary Options Menu panel, select the display option by
typing “1” on the option line.
--------------------------- DISPLAY OPTIONS MENU ----------------------------

OPTION ===> 2
1 ELEMENT - Display element/component list information

2 FOOTPRINT - Display footprinted members and compressed listings
3 SITE - Display site information
4 STAGE - Display stage information
5 SYSTEM - Display system definitions
6 SUBSYSTEM - Display subsystem definitions
7 TYPE - Display type definitions
8 PROCESSOR GROUP - Display processor group definitions
9 APPROVER GROUP - Display approver groups
A RELATE GROUP - Display inventory area/approver group relationships
E ENVIRONMENT - Display information about the current environment
Figure 4-152: Display Options Menu Panel

4. At the Display Options Menu panel, select the FOOTPRINT option by typing “2” on
option line.
Special Note: At the Endevor for OS/390 Environment Selection panel, you can enter 4;1;2
to get to above panel.
not found
------------------------- ENDEVOR - FOOTPRINT DISPLAY -------------------------
Option ===>
blank - Member selection list

I - Display load module CSECTS and ENDEVOR footprints
L - Display the library member
FROM ISPF LIBRARY:

PROJECT ===>
LIBRARY ===>
TYPE ===>
MEMBER ===> THRU MEMBER ===>
OTHER PARTITIONED DATA SET:

DATA SET NAME ===> 'PN.ENDEVOR.PROD.LISTLIB(M3706080)'
Figure 4-153: Endevor - Footprint Display Panel

5. At the Endevor - Footprint Display panel, enter
“PN.ENDEVOR.PROD.LISTLIB(member name)” in the Data Set Name field. Note: You
can also enter a wildcard (member prefix *) to list several members.
FOOTPRINT -------------- LIBRARY SELECTION LIST ------------- Row 1 to 1 of 1

Library: PN.ENDEVOR.PROD.LISTLIB
I - Display load module CSECTS and ENDEVOR footprints
L - Display the library member
For ENDEVOR Elements:

B - Browse element C - Show changes only S - Show change summary
H - Show change history M - Show Master Record
|--------------------- F O O T P R I N T --------------------|
MEMBER SYSTEM SUBSYSTEM ELEMENT TYPE S VV.LL DATE TIME LD
L M3706080 LOGISTCS LOGISTCS M3706080 COBOLLE 2 01.03 03APR02 16:33
******************************* Bottom of data ********************************
Figure 4-154: Library Selection List Panel

6. At the Library Selection List panel, browse the compile listing by typing “L” on the line
next to the member you want to browse.
not found
3. How to Correct an Element in the Wrong Production System/Sub
System
Occasionally, an element will be loaded into the incorrect production system. For example, a
M312 program may be in PROD/P/MISC/MISC instead of PROD/P/TECH/TECH. One
method of moving an element is to build a package that will transfer an element from one
system to another system without regenerating the element.
The procedure to move all element types starts with the following steps:

Command ===> P________________________________________________________________
Dialog Commands:
Element Options:

ENVIRONMENT.. PROD WHERE CCID IS............... ____________
SYSTEM....... MISC WHERE PROCESSOR GROUP IS.... ________
SUBSYSTEM.... MISC BUILD USING MAP............. N (Y/N)
Action Options:
CCID......................... ____________
Comment...................... ________________________________________
Processor Group.............. ________
-
Figure 4-155: Endevor Quick-Edit Panel – Package Options

not found
Option ===> 2

Package ID ===> PRxxxxxxxxxxx

Figure 4-156: Package Foreground Options Menu Panel – Create/Modify Option

2. At the Package Foreground Options Menu panel, select 2 CREATE/MODIFY at the
Option line.
3. Enter the name of the package at the Package ID field. The package name must begin
with “PR”.
not found
OPTION ===> B

PACKAGE ID: PRxxxxxxxxx STATUS: IN-EDIT

FROM ISPF LIBRARY:

PROJECT ===>
GROUP ===>
TYPE ===>
MEMBER ===>

DATA SET NAME ===>

4. At the Create/Modify Package panel, select B Build Package Actions at the Option line.
5. Enter the mandatory Description field.
not found
------------------------------- SCL GENERATION ------------------------------
OPTION ===> 9

REQUEST DATA SET: PACKAGE - PRxxxxxxxxx

APPEND: N
Figure 4-158: SCL Generation Panel – Transfer Option

6. At the SCL Generation panel, select Transfer by typing “9” on the option line
At this point if you are moving OPTION or COPY elements continue with the instructions in
Error: Reference source not found Error: Reference source not found. If you are moving
another type of element continue with the instructions in Error: Reference source not found
Error: Reference source not found.
not found
1. Move all element types except OPTIONS and COPY
The procedure to move all element types except OPTIONS and COPY continues with the
following steps:

OPTION ===> t

ENVIRONMENT ===> prod DISPLAY LIST ===> N (Y/N)
SYSTEM ===> misc WHERE CCID EQ ===>
SUBSYSTEM ===> misc WHERE PROC GRP EQ ===>
ELEMENT ===> M312xxxx BUILD USING MAP ===> N (Y/N)
TYPE ===> cobolle
STAGE ===> P ACTION OPTIONS:
U - UNIT N - NTGN CCID ===> ######
ENVIRONMENT ===> prod GENERATE ELEMENT ===> N (Y/N)
SYSTEM ===> tech OVERRIDE SIGNOUT ===> N (Y/N)
SUBSYSTEM ===> tech PROCESSOR GROUP ===>
TYPE ===> COBOLLE WITH HISTORY ===> N (Y/N)
STAGE ===> P RETAIN SIGNOUT ===> N (Y/N)
SIGNOUT TO ===>
COMMENT ===> Transfer to Correct System/Subsystem

7. Create a “PR” package to transfer elements from PROD/P/MISC/MISC to
PROD/P/TECH/TECH with the following options set:
CCID ===> <Valid CCID #>

Delete 'From' Elm ===> Y (Y/N)
Generate Element ===> N (Y/N)
Sync ===> Y (Y/N)
Comment ===> <Comment>
8. If you do not have the element name, you can use the following options to display an
element list:
Display List Enter a “Y” to display the Element Selection List panel. Enter
an “N” to Transfer the Endevor elements as entered in the From
Endevor fields. Note: A “T” must be entered on the option
line, if you enter an “N” in the Display List field.
Where CCID EQ Enter the CCID to restrict the Element Selection List.
Where PROC GRP EQ Enter the Processor Group to restrict the Element
Selection List.
not found
Build Using Map Enter a “Y” to use the map when building the Element
Selection List.
9. After the SCL is written, press PF3 until you return to the Create/Modify Package panel.

OPTION ===> E


FROM ISPF LIBRARY:

PROJECT ===>
GROUP ===>
TYPE ===>
MEMBER ===>

DATA SET NAME ===>
Figure 4-160: Create/Modify Package Panel – Edit Package Option

10. At the Create/Modify Package panel, select E Edit Package at the Option line.
EDIT - PACKAGE ID: PRxxxxxxxxx -------------------------- COLUMNS 00001 00072

DESCRIPTION: Required Description
****** ***************************** Top of Data ******************************
000001 SET OPTIONS IGNORE GENERATE FAILED
000002 BYPASS DELETE PROCESSOR
000003 .
000004 TRANSFER ELEMENT 'M312xxxx'
000005 FROM ENVIRONMENT 'PROD' SYSTEM 'MISC' SUBSYSTEM 'MISC'
000006 TYPE 'COBOLLE' STAGE P
000007 TO ENVIRONMENT 'PROD' SYSTEM 'TECH' SUBSYSTEM 'TECH'
000008 TYPE 'COBOLLE' STAGE P
000009 OPTIONS CCID '######'
000010 COMMENTS "Transfer to Correct System/Subsystem" SYNCHRONIZE
000011 BYPASS GENERATE PROCESSOR
000012 .
****** **************************** Bottom of Data ****************************
Figure 4-161: Edit Package Panel – Edit Package Option

11. At the Edit Package panel, insert three blank lines in the beginning of the package.
12. Add the options, highlighted in bold, as the first 3 lines of the package. Be sure to include
the period in column 2 on the third line.
13. Press PF3 when finished editing.
not found
MODIFY -------------------- CREATE/MODIFY PACKAGE ------------ NO SYNTAX ERRORS
OPTION ===> N


FROM ISPF LIBRARY:

PROJECT ===>
GROUP ===>
TYPE ===>
MEMBER ===>

DATA SET NAME ===>
Figure 4-162: Create/Modify Package Panel – Add Notes to Package Option

14. At the Create/Modify Package panel, select N Add Notes to Package at the Option line.
----------------------------- Package Note Text -------------------------------

Command ==>
.........1.........2.........3.........4.........5.........6
1. ____________________________________________________________
2. ____________________________________________________________
3. ____________________________________________________________
4. ____________________________________________________________
5. ____________________________________________________________
6. ____________________________________________________________
7. ____________________________________________________________
8. ____________________________________________________________
Press ENTER to process the Package Notes. When all the note
text has been entered, press ENTER and then enter the END
command.
To cancel the Package Notes, enter the END command.
Figure 4-163: Package Note Text Panel

15. At the Package Note Text panel, create a note for this package, indicating Impact Change Number and back
out procedure. Press Enter.
16. Press PF3 when finished.
not found
2. Move element types of Options or COPY
The procedure to move element types of OPTIONS or COPY continues with the following
steps:

OPTION ===> t

ENVIRONMENT ===> prod DISPLAY LIST ===> N (Y/N)
SYSTEM ===> misc WHERE CCID EQ ===>
SUBSYSTEM ===> misc WHERE PROC GRP EQ ===>
ELEMENT ===> M312xxxx BUILD USING MAP ===> N (Y/N)
TYPE ===> options
STAGE ===> P ACTION OPTIONS:
U - UNIT N - NTGN CCID ===> ######
ENVIRONMENT ===> prod GENERATE ELEMENT ===> Y (Y/N)
SYSTEM ===> tech OVERRIDE SIGNOUT ===> N (Y/N)
SUBSYSTEM ===> tech PROCESSOR GROUP ===>
TYPE ===> options WITH HISTORY ===> N (Y/N)
STAGE ===> S RETAIN SIGNOUT ===> N (Y/N)
SIGNOUT TO ===>
COMMENT ===> Transfer to Correct System/Subsystem

7. Create a “PR” package to transfer elements from PROD/P/MISC/MISC to
PROD/S/TECH/TECH with the following options set:
CCID ===> <Valid CCID #>

Delete 'From' Elm ===> Y (Y/N)
Generate Element ===> Y (Y/N)
Sync ===> Y (Y/N)
Comment ===> <Comment>
8. If you do not have the element name, you can use the following options to display an
element list:
Display List Enter a “Y” to display the Element Selection List panel. Enter
an “N” to Transfer the Endevor elements as entered in the From
Endevor fields. Note: A “T” must be entered on the option
line, if you enter an “N” in the Display List field.
Where CCID EQ Enter the CCID to restrict the Element Selection List.
Where PROC GRP EQ Enter the Processor Group to restrict the Element
Selection List.
not found
Build Using Map Enter a “Y” to use the map when building the Element
Selection List.
9. After the SCL is written, press PF3 until you return to the Create/Modify Package panel.

OPTION ===> N


FROM ISPF LIBRARY:

PROJECT ===>
GROUP ===>
TYPE ===>
MEMBER ===>

DATA SET NAME ===>
Figure 4-165: Create/Modify Package Panel – Add Notes to Package Option

10. At the Create/Modify Package panel, select N Add Notes to Package at the Option line.
----------------------------- Package Note Text -------------------------------

Command ==>
.........1.........2.........3.........4.........5.........6
1. ____________________________________________________________
2. ____________________________________________________________
3. ____________________________________________________________
4. ____________________________________________________________
5. ____________________________________________________________
6. ____________________________________________________________
7. ____________________________________________________________
8. ____________________________________________________________
Press ENTER to process the Package Notes. When all the note
text has been entered, press ENTER and then enter the END
command.
To cancel the Package Notes, enter the END command.
Figure 4-166: Package Note Text Panel

11. At the Package Note Text panel, create a note for this package indicating Impact Change Number, back out
procedure, and the fact this package will be followed by a “PR” package. (See Section Error: Reference
not found
source not found Error: Reference source not found in Appendix Error: Reference source not found for
package naming standards.) Press Enter.
12. Press PF3 when finished.
not found
14. Create a “PR” package to move your elements from PROD/S/TECH/TECH to
PROD/P/TECH/TECH. By assigning a CCID, you will be able to build your move
package easier.
15. Create a note for this package indicating Impact Change Number and back out procedure.
to make sure that the elements were moved correctly.
not found
8. Handling Special Software in Endevor
Please note that the documentation in this section assumes that the user is familiar with the
software products mentioned below.
1. AFP Procedures
This section documents how to change and test an AFP element, using Endevor. This is to
provide an understanding on the way AFP functions.
1. Copy the required AFP element into the Develop environment.
The element will come from:

ENVIRONMENT = PROD,
SYSTEM = MISC,
SUBSYSTEM = MISC,
ELEMENT = element name
TYPE = AFPFDEF (formdef), AFPPDEF (pagedef), or AFPOVER (overlay).
Here is an explanation of the element name:

For Formdefs, Pagedefs and Overlays, the name in the JCL correlates to the name
within the AFP element. This does not necessarily mean that the element name will
be the same.
To find the element name to modify, search Endevor where TYPE = AFP*.
Overlays work like includes. An overlay is used in a formdef or pagedef. It is good

practice to first compile the overlay(s) then compile the formdef or pagedef.
Here is a detailed example:

JCL:
//OUTDD2 OUTPUT CLASS=V,COPIES=1,
// DEST=U501,FORMDEF=EBPO,
// FORMS=PO,PAGEDEF=EBPO,
// PIMSG=(Y,0)
Formdef:
Element name = FSEBPO
FORMDEF EBPO PRESENT LANDSCAPE DIRECTION DOWN
REPLACE YES;
COPYGROUP CG1
DUPLEX NORMAL
BIN 1
not found
JOG YES
CONSTANT BACK;
OVERLAY O1 EBPOFT; Overlay
OVERLAY O2 EBPOBK; Overlay
SUBGROUP FRONT OVERLAY O1;

SUBGROUP BACK OVERLAY O2;
Pagedef:
Element name = PSEBPO
PAGEDEF EBPO WIDTH 11 HEIGHT 8.5 IN DIRECTION DOWN
REPLACE YES;
Overlay: (see example under formdef)

Element name = OSEBPOBK
OVERLAY EBPOBK SIZE 8.80 IN 11.10 IN OFFSET 0 IN 0 IN;
Element name = OSEBPOFT
OVERLAY EBPOFT SIZE 11.10 IN 8.70 IN OFFSET 0.0 IN 0.2 IN;
2. Make the appropriate changes to your element and generate the element.
This will update the load module.
In Endevor:
Type “LO” next to the element name. The load module is the member with a Step
name of COMPILE. This PDS name will be used in your test job.
In JCL:
After the AFP step, use a // USERLIB=(PDS name, …). Note the space between //
and USERLIB! The last line prior to the USERLIB statement will need a comma after
it for continuation.
The PDS name will differ based on Formdef, Pagedef or Overlay. Concatenate PDS’s
together with a comma.
Production Example: (before)

//OUTDD2 OUTPUT CLASS=A,COPIES=1,
// DEST=N3.U23,FORMDEF=EBPO,
// FORMS=STD,PAGEDEF=EBPO,
// PIMSG=YES
Test Example: (after)

//OUTDD2 OUTPUT CLASS=A,COPIES=1,
// DEST=N3.U23,FORMDEF=EBPO,
// FORMS=STD,PAGEDEF=EBPO,
not found
// PIMSG=YES,
// USERLIB=(PN.ENDEVOR.UNIT.EBITST01.FDEFLIB,
// PN.ENDEVOR.UNIT.EBITST01.PDEFLIB,
// PN.ENDEVOR.UNIT.EBITST01.OVERLIB)
3. Run your test job, with the USERLIB statement. If this moves your fields correctly,
you are ready to install. Create a package and proceed with install.
not found
2. APS Procedures
1) To retrieve one or more modules for maintenance:

a) Use full panel Endevor (option E on the Endevor main menu) to retrieve the
module(s).
b) Choose environment 1 (DEVELOP), option 2 (Foreground), action 3 (Retrieve).
------------------------------ RETRIEVE ELEMENTS ------------------------------

OPTION ===>
R - Retrieve element M - Master C - Changes

SYSTEM ===> MDSE EXPAND INCLUDES ===> N (Y/N)
SUBSYSTEM ===> SPGTST01 SIGNOUT ELEMENT ===> N (Y/N)
ELEMENT ===> Mxxxxxxx OVERRIDE SIGNOUT ===> N (Y/N)
TYPE ===> APS* REPLACE MEMBER ===> N (Y/N)
COMMENT ===>
TO ISPF LIBRARY: LIST OPTIONS:

PROJECT ===> TEST DISPLAY LIST ===> Y (Y/N)
LIBRARY ===> ENDEVOR WHERE CCID EQ ===>
TYPE ===> APS**** WHERE PROC GRP EQ ===>
MEMBER ===> BUILD USING MAP ===> Y (Y/N)
FIRST FOUND ===> N (Y/N)
TO OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DATA SET NAME ===>
Figure 4-167: Retrieve Elements Panel

c) Specify the System, Subsystem, Type, and Stage U for the module(s) to be retrieved.
d) Set the following switches for Action Options:
i) Expand Includes – N
ii) Signout Element – N
iii) Override Signout – N
iv) Replace Member – N
e) Set the following switches for List Options:
i) Display List –Y
ii) Where CCID Eq – <blank>
iii) Where Proc Grp Eq – <blank>
iv) Build Using Map – Y
v) Return First Found –N
f) Specify the “To ISPF Library” as TEST.ENDEVOR.APS**** where **** represents
the type of module to be retrieved.
g) If you leave the name of the module blank, you will be given a list of modules from
which to choose. If there are multiple versions of the module in the current migration
not found
path, you will be shown all versions (setting the switch Return First Found to N causes
this). Select the modules you want to retrieve by entering an R to the left of the name.
not found
h) Continue these steps until you have retrieved every module you will need to work on.
i) Note 1: In order to work on a program, screen, data element, or report in APS,
you will also need to retrieve the Application (type APSAPPL). This must be done
even if the application is not going to be changed.
ii) Note 2: Modules in type APSINCL were formerly Panvalet Include modules
and cannot be maintained in APS. If a new version of an Include module is
created, it can be added to Endevor and migrated in the same way as any other
APS module.
i) APS modules, their Endevor types, and the datasets into which they should be
retrieved are listed below:
Table 11: APS Modules
Module Type Endevor Type Dataset
Applications APSAPPL TEST.ENDEVOR.APSAPPL
Data structures APSDATA TEST.ENDEVOR.APSDATA
Included APSINCL not retrieved
modules
Programs APSPROG TEST.ENDEVOR.APSPROG
Reports APSREPT TEST.ENDEVOR.APSREPT
Screens APSSCRN TEST.ENDEVOR.APSSCRN
2) Within APS
a) Set the Project to TEST and the Group to ENDEVOR.
b) You will be required to specify the Endevor Subsystem (SPGTST0n) in APS. This is
necessary to maintain the separate tracks for concurrent development.
c) Open the Application System Painter and edit the required modules.
d) Generate modules and test as necessary.
e) All compiles and assemblies will put the load modules into
TEST.ENDEVOR.LOADLIB.
3) After generating, use Quick Edit to move the changed modules into Endevor.
a) Enter the Environment (Develop), System, Subsystem, module name and Type.
b) The module should already be in Endevor. Use the action Edit. This will bring up the
most recent version of the module in an edit session.
c) Delete all lines of the module and copy the version from TEST.ENDEVOR…
d) Press END to save the module into Endevor. This will also copy the load module into
the proper load lib for the subsystem.
e) Testing can be done at this point. Steps 2 and 3 can be repeated as often as necessary.
f) When testing has been completed and the module(s) are ready to be moved toward
Production, Copy the APS Application into Endevor. In order to force this module
into Endevor even though no changes have been made, enter SAVE on the command
line while editing the module in Quick Edit.
not found
4) Move the modules from UNIT to NTGN. The easiest way to do this, if there are more than
a couple of modules, is to build a Package and submit it.
5) After integration testing, move the modules from NTGN to ASTG. A Package is required
for this move regardless of how many modules you are moving. During the move to
ASTG, all modules will be deleted from the TEST.ENDEVOR.* datasets.
6) All further moves toward Production will follow standard Endevor procedures.
not found
The table below describes the APS types available in Endevor:
Table 12: APS Types in Endevor
Type Description Dataset for Retrieve Movement in Endevor
APSAPPL APS Application APSAPPL Source only
APSDATA APS Data APSDATA Source only
Structure
APSINCL APS Include none none
module
APSPROG APS Program APSPROG Source and load module
APSREPT APS Report APSREPT Source only
Definition
APSSCRN APS Screen APSSCRN Source and load module
Definition
The table below describes the datasets referenced by developers within APS:
Table 13: Test level APS Datasets

Dataset Name Description
TEST.ENDEVOR.APRAPPL APS Application Headers
TEST.ENDEVOR.APRPROG Program Headers
TEST.ENDEVOR.APSAPPL APS Application Detail
TEST.ENDEVOR.APSCNIO Painted Scenarios
TEST.ENDEVOR.APSDATA Painted Data
TEST.ENDEVOR.APSEXPS Online Express Save (APS use
only)
TEST.ENDEVOR.APSPROG Painted Programs
TEST.ENDEVOR.APSREPT Painted Report Mockups
TEST.ENDEVOR.APSSCFE Field Edit Selection
TEST.ENDEVOR.APSSCRN Painted Screens
TEST.ENDEVOR.APSSRC Used by APS
TEST.ENDEVOR.CNTL Used by APS
TEST.ENDEVOR.COBCICS Used by APS
TEST.ENDEVOR.COBMVS Used by APS
TEST.ENDEVOR.COPYLIB Used by APS
TEST.ENDEVOR.DDISYMB Used by APS
TEST.ENDEVOR.DEVMACS Used by APS
TEST.ENDEVOR.GENBMS Generated BMS map source
TEST.ENDEVOR.GENSRC Generated COBOL source
TEST.ENDEVOR.SCRSYMB Used by APS
TEST.ENDEVOR.USERMACS Used by APS
not found
3. SDF II Procedures
1. INTRODUCTION
SDFII is the Screen Definition Facility used by NNI to interactively define and modify CICS
screens or panels. After a screen has been defined or modified, SDFII will generate the BMS
code and data structure (DSECT) needed by Endevor to allow a CICS program to
communicate with the mapping facility.
This section will provide instructions on how to access SDFII to generate or modify a screen
and migrate the screen objects into Endevor. It will not provide instructions on how to use the
SDFII product. For instructions on how to use the SDFII product, please refer to the “Screen
Definition Facility II Primer for CICS/BMS”. This manual can be accessed from Book
Manager (Option U.1 on the NNITSO region).
2. SDFII DEVELOPMENT LIBRARIES

SDFII will reference four sets of test libraries. Each set should correspond to your Endevor
development subsystem. For example, if you are using NNITST01 as your Endevor
development subsystem, then you must use the NNITST01 SDFII development libraries.
1. SDF II Production libraries:

PN.ENDEVOR.PROD.DGIGRP Stores Group Source data
PN.ENDEVOR.PROD.DGIPNL Stores Panel Source data
2. SDFII Test or development libraries:

TEST.ENDEVOR.NNITST0n.DGIGRP Group Source development library
TEST.ENDEVOR.NNITST0n.DGIPNL Panel Source development library
TEST.ENDEVOR.NNITST0n.DGIDSCT DSECT from SDFII generate
TEST.ENDEVOR.NNITST0n.DGIBMS BMS map source from SDFII
Please note that the only module you will copy into Endevor is the BMS code stored in
“TEST.ENDEVOR.NNITST0n.DGIBMS”. Endevor will then obtain the DSECT (screen
structure or copybook) and generate the CSECT (load module).
not found
3. ENDEVOR DEVELOPMENT LIBRARIES FOR SDFII SOURCE
OBJECTS
Endevor will reference four sets of libraries at each migration stage. These libraries will be
populated by Endevor based on the source code generated by SDFII:
Table 14: Endevor Development Libraries
Unit Test Stage (UNIT)
PN.ENDEVOR.UNIT.NNITST0n.DGIGRP Group Source
PN.ENDEVOR.UNIT.NNITST0n.DGIPNL Panel Source
PN.ENDEVOR.UNIT.NNITST0n.COPYLIB DSECT
PN.ENDEVOR.UNIT.NNITST0n.LOADLIB CSECT (load
module)
Integration Test Stage (NTGN)
PN.ENDEVOR.NTGN.NNITST0n.DGIGRP Group Source
PN.ENDEVOR.NTGN.NNITST0n.DGIPNL Panel Source
PN.ENDEVOR.NTGN.NNITST0n.COPYLIB DSECT
PN.ENDEVOR.NTGN.NNITST0n.LOADLIB CSECT (load
module)
Acceptance Test Stage (ASTG)
PN.ENDEVOR.ASTG.NNITST0n.DGIGRP Group Source
PN.ENDEVOR.ASTG.NNITST0n.DGIPNL Panel Source
PN.ENDEVOR.ASTG.NNITST0n.COPYLIB DSECT
PN.ENDEVOR.ASTG.NNITST0n.LOADLIB CSECT (load
module)
QA Approval Stage (ACPT)
PN.ENDEVOR.ACPT.NNITST0n.DGIGRP Group Source
PN.ENDEVOR.ACPT.NNITST0n.DGIPNL Panel Source
PN.ENDEVOR.ACPT.NNITST0n.COPYLIB DSECT
PN.ENDEVOR.ACPT.NNITST0n.LOADLIB CSECT (load
module)
Production Staging (PSTG)
PN.ENDEVOR.PSTG.NNITST0n.DGIGRP Group Source
PN.ENDEVOR.PSTG.NNITST0n.DGIPNL Panel Source
PN.ENDEVOR.PSTG.NNITST0n.COPYLIB DSECT
PN.ENDEVOR.PSTG.NNITST0n.LOADLIB CSECT (load
module)
Production Approval Stage (PROD)
PN.ENDEVOR.PROD.NNITST0n.DGIGRP Group Source
PN.ENDEVOR.PROD.NNITST0n.DGIPNL Panel Source
PN.ENDEVOR.PROD.NNITST0n.COPYLIB DSECT
PN.ENDEVOR.PROD.NNITST0n.LOADLIB CSECT (load
module)
not found
6. To access SDFII, you must sign-on to NNITSO from the Intersession Menu.
----------- Newport News, Inc. - ISPF/PDF Primary Option Menu ---------------
OPTION=> 4.12
USERID - XXXXXXX
0 ISPF PARMS Specify terminal and user parameters TIME - 18:13
1 Browse Display source data or output listings DATE - 02/02/25
2 Edit Create or change source data JULIAN - 02.056
3 Utilities Perform ISPF/PDF utility functions KEYS - 24
4 N N I Newport News, Vendor and IBM utilities
6 Command Enter TSO command or CLIST
T Tutorial Display information about ISPF/PDF
X EXIT Terminate ISPF using log and list defaults
Figure 4-168: NNI ISPF Main Menu Panel

7. At the NNI ISPF Main Menu panel, select the SDF option by typing “4.12” on the option
line.
Vendor/NNI/IBM Utilities
Enter Option ===> 12
--VENDOR-- --N N I-- --I B M--

More: +
1 FDR/ABR CH TS CHANGE LOG 10 PL1
2 NNIDASD
3 Reserved SDF (Old Screen Development
4 FORTE (FILE Facility)
5 QSERV (HIST
6 SAS (ONLI X SDFII (New Screen Development Facility)
7 DATA/IMS EX
8 TMS (TAPE SDFII(P) (SDFII Prototype Facility)
9 TSS (SECU
AB Abend-Aid/S ER
D Ca-Docview
EX Expediter/TSO ST STROBE
F File-Aid SU Spiegel User Panel
G1 Ca-11 PROD DB2 DB2 Products Menu
G2 Ca-11T TEST
H Ca-7
J JCLPrep
TAO EMC/2 Email System
Figure 4-169: SDF Pop-up Menu

8. At the SDF Pop-up Menu, select SDFII (New Screen Development Facility) by typing
“X” next to that option.
not found
Exit Help
-------------------------------------------------------------------------------
SELECT AN SDF II FUNCTION
Option ===> 8
1 PANEL EDITOR Create or edit a panel

2 PANEL GROUP EDITOR Create or edit a panel group
3 PARTITION SET EDITOR Create or edit a partition set
4 AID TABLE EDITOR Create or edit an AID table
5 CONTROL TABLE EDITOR Create or edit a control table
6 GENERATE Generate control block source and data structure
7 LIST OBJECTS List objects in the library
8 SPECIFY LIBRARIES Access libraries
9 UTILITIES Print, Import, Convert, Construct,
Extract, and Modify Objects
10 PROFILE Modify editing defaults
11 SDF II PROTOTYPE Define and run a prototype
13 PRINT REFERENCE Print the online reference
R REFERENCE Obtain SDF II online reference
X EXIT Terminate SDF II dialog
Use PFSHOW ON/OFF to show/hide program function key assignment
Figure 4-170: SDFII Main Menu Panel

9. At the SDFII Main Menu panel, select the Specify Libraries option by typing “8” on the
option line. This will allow you to define your development libraries.
Exit Help
-------------------------------------------------------------------------------
SPECIFY LIBRARIES
Command ===>
ID Library name -------------------------- Description -------- Password

1 'TEST.ENDEVOR.NNITST04'
2 'PN.ENDEVOR.PROD'
3
4
5
6
7
8
9
Optionally, specify AUTOSAVE library

Library name -------------------------- Password
Search for related objects. . 1 1. Search all libraries

2. Start with library of primary object
3. Same library as primary object
Figure 4-171: SDFII Specify Libraries Panel

10. At the SDFII Specify Libraries panel enter your SDFII development and production
library. The development library should correspond with your Endevor development
subsystem. This can be entered in any order. However, it is important to remember
which ID number you assign to each library. Then, select how you want SDFII to search
for your SDFII objects (“1” should be your default). Press “Enter” and PF3 to save your
selection and return to the Main Menu.
not found
Exit Help
-------------------------------------------------------------------------------
Option ===> 1


11. At the SDFII Main Menu panel, select the Panel Editor option by typing “1” on the
option line. This will allow you to create or update a panel.
Exit Help
-------------------------------------------------------------------------------
IDENTIFY PANEL
Option ===> 1
blank Edit existing panel

1 Create new panel from skeleton
2 Create new panel from scratch for CICS/BMS
Identify the panel

Name . . . . . . . . . . OES212
Library . . . . . . . . 1
To create a new panel from skeleton, specify the skeleton

Name . . . . . . . . . . OES212
Library . . . . . . . . 2
To create a new panel from scratch, specify the device type

Device type . . . . . . ALL
Figure 4-173: SDFII Identify Panel

12. At the SDFII Identify Panel, select one of the options on the following page:
not found
To update an existing production panel:
Select option “1”
In the “Identify the Panel” fields,
Enter the panel name you would like to modify
Enter the number of your test SDFII library (see Error: Reference source not
found)
In the “To Create a New Panel from Skeleton” fields,
Enter the production panel name
Enter the number you assigned to your SDFII production library (see Error:
Reference source not found)
Press the “Enter” key to access the Panel Editor Dialog Menu.
To create a new panel using an existing production panel as a model

Follow the above instructions. However, in “Identify the Panel” enter your new panel
name.
In “To Create a New Panel from Skeleton”, enter the existing panel name you would
like to use as a model, i.e.:
New Panel Name: OES213
Skeleton Panel Name: OES212
To create a new panel without using a skeleton

Select option “2”
Enter the name of the panel you would like to create
Enter the library number of your test SDFII library (see Error: Reference source
not found)
To update an existing panel already in a SDFII test library

Leave the option blank
Enter the name of the existing panel
Enter the number of your test SDFII library (see Error: Reference source not
found)
If you receive an “OBJECT NOT FOUND” error message while trying to access an existing
panel, check the SDFII production library to ensure the object is there. You can perform this
test by changing your test library number to the production library number, leave the Option
blank, and press the “Enter” key. If the existing object could not be found in the production
library, it is possible the object is in the old SDF library. To investigate this further, you must
sign off SDFII and sign-on to SDF. If the object is found in the old SDF library, it must be
converted to SDFII. Instructions to convert SDF to SDFII are not included in this document.
not found
File Options Help
-------------------------------------------------------------------------------
SELECT A PANEL EDITOR DIALOG 0 New object created
Option ===> 2
1 CHARACTERISTICS Define panel characteristics
2 FORMAT Define the format of the panel
3 FIELDS Define the fields for the format
4 ATTRIBUTES Define the attributes for the format
5 STRUCTURE Define the data structure of the panel
6 SYSTEM Define target system dependent information
7 TEST Show panel in execution time format
8 INSTANCES Define the panel instances
* FIELD EDITING Define field editing and verification rules
Figure 4-174: SDFII Select a Panel Editor Dialog Panel

13. At the Select a Panel Editor Dialog panel, select the appropriate options to modify an
existing panel or create a new panel. Press PF3 to return to the SDFII Main Menu panel.
Exit Help
-------------------------------------------------------------------------------
Option ===> 6


14. After all the changes have been applied, the panel must be generated to create the data
structure and BMS source code. At the SDFII Main Menu panel, select the Generate
option by typing “6” on the option line.
not found
Exit Help
-------------------------------------------------------------------------------
IDENTIFY OBJECT FOR GENERATION
Command ===>
Identify the source object

Name . . . . . . . . . . OES212
Library . . . . . . . . 1
Type . . . . . . . . . . P G. PANEL GROUP S. PARTITION SET
P. PANEL
Specify the target system here only when you want to generate
for an other target system than specified for the object.
Target system . . . . . 1 blank Take target system from object
0. PROTOTYPING
1. CICS/BMS
2. MFS
3. ISPF
4. GDDM
5. CSP
Figure 4-176: SDFII Identify Object For Generation Panel

15. Identify your test panel name, test library number, and type. If there is only one panel in
the panel group (mapset), you can use TYPE “P”. However, if the panel group consists of
multiple panels, you must use TYPE “G”. There are times when a developer will include
a help screen, etc., with their panel. Option “G” allows the panels to be grouped together
into one mapset. Therefore, the panel names may be OES212A, OES212B, but the group
name might be OES212. If there is a group name enter the group name on this panel.
The group object can be setup by selecting option “2” from the SDFII Main Menu.
Target system must contain option “1”, CICS/BMS. Press “Enter” to display the SDFII
Specify Generation Parameters panel.
If there are multiple panels in a group, then the developer must code the following in their
CICS COBOL program to access the map:
EXEC CICS RECEIVE MAP ('OES212A')

MAPSET ('OES212')
INTO (OES212AI)
END-EXEC
Otherwise, if there is a single panel in a group, then the developer can code the following:
EXEC CICS RECEIVE
MAP ('OES212')
INTO (OES212I)
END-EXEC
Or
EXEC CICS RECEIVE MAP ('OES212')
not found
MAPSET ('OES212')
INTO (OES212I)
END-EXEC
Exit Help
---------------------------------------------------------------------------
SPECIFY GENERATION PARAMETERS OES212
Command ===>
More: +
Object name . . . . . : OES212
Object type . . . . . : PANEL
Target system . . . . : CICS/BMS
Enter '/' to select the generation function.

/ Generate data structure
/ Generate CICS/BMS macros
Specify the options and output libraries.

Then press ENTER to generate, or press END to exit.
Options for data structure

Language . . . . . . COBOL ASM, C, COBOL, PLI, RPG
Enter '/' to select option
Alignment Ignored for C language
Graphic DBCS panels only
Trigraph C language only
Figure 4-177: SDFII Specify Generation Parameters Panel

16. At the SDFII Specify Generation Parameters panel, the object name, type and target
system will be displayed based on what you entered on the SDFII Identify Object for
Generation panel (see Error: Reference source not found).
Select “Generate Data Structure” and “Generate CICS/BMS macros” by keying a “/” in
the selection fields.
Language must equal COBOL.
Press PF8 to continue entering the generate options
not found
Exit Help
---------------------------------------------------------------------------
SPECIFY GENERATION PARAMETERS OES212
Command ===>
More: -
/ SDF/CICS Compatible COBOL language only
Length statement COBOL language only
Field names Field names generated as defined
Output library for data structure

Dataset name or . . . . TEST.ENDEVOR.NNITST04.DGIDSCT
DDname . . . . . . . . .
User exit . . . . . . .
Options for BMS macros

Device type . . . . . . * * for all devices
Output library for BMS macros

Dataset name or . . . . TEST.ENDEVOR.NNITST04.DGIBMS
DDname . . . . . . . . .
User exit . . . . . . .
Figure 4-178: SDFII Specify Generation Parameters Panel (continued)

17. At the SDFII Specify Generation Parameters panel (continued), do the following:
Select “SDF/CICS Compatible” by keying a “/” in the selection field
Enter the Output library for the data structure. This library should correspond to your
Endevor subsystem. For example, if your Endevor subsystem is NNITST01, then your
data structure output library should be “TEST.ENDEVOR.NNITST01.DGIDSCT”. This
is the library that Endevor will search for your DSECT.
Enter the Output library for the BMS macros. This library should correspond to your
Endevor subsystem. For example, if your Endevor subsystem is NNITST01, then your
BMS macros output library should be “TEST.ENDEVOR.NNITST01.DGIBMS”. This is
the library that Endevor will search for your BMS source code.
Press “Enter” to generate your SDFII panel.
not found
Exit Options Help
---------------------------------------------------------------------------
LIST GENERATION MESSAGES OES212
Command ===> Scroll ===>
PAGE
0 Errors detected
Enter '/' to select action
Print messages Will be performed on Exit
Messages . . . . . . . . . . . . . . . . . . COLUMNS 1-2 OF 2, ROW 1 OF 9

Message# Message ----------------------------------------------------
Object name: OES212 type: PANEL library: 1
Data Structure
Output library: TEST.ENDEVOR.NNITST04.DGIDSCT member: OES212
DGICM038 Generation of data structure(s) completed
CICS/BMS map set for device type 3278-2B
DGICM021 PANEL OES212 retrieved from library 1
DGICM117 The generated map contains field names that have been generated
Output library: TEST.ENDEVOR.NNITST04.DGIBMS member: OES2122
DGICM034 Generation of BMS macros completed
END OF DATA ***********************************************************
Figure 4-179: SDFII List Generation Messages Panel

18. If you receive “0 Errors Detected”, your panel has been generated and has created the
highlighted member in the output library. This is the member you will copy into Endevor.
Press PF3 to exit the Generate Screen.
If you receive errors, correct the errors and attempt to generate your panel again. Follow
the instructions beginning at Error: Reference source not found.
19. To migrate your SDFII objects into Endevor sign on to TSO2 from the Intersession Main
Menu Panel.
20. At the Spiegel Group Mainframe Primary Option Menu panel, select Endevor by
typing “A.E” on the option line.

OPTION ===> Q


X - EXIT

21. At the Endevor Rel39 Selection Menu panel, enter Quick-Edit, by typing “Q” on the
option line.
not found
Command ===> CR_______________________________________________________________
Dialog Commands:
Element Options:

SYSTEM....... ORDNTRY WHERE PROCESSOR GROUP IS.... ________
SUBSYSTEM.... NNITST01 BUILD USING MAP............. Y (Y/N)
ELEMENT...... OES212 RETURN FIRST FOUND.......... Y (Y/N)
TYPE......... SDF DISPLAY SYSTEM/SUBSYS LIST.. N (Y/N)
Action Options:
CCID......................... 2000-351AH__
Comment...................... Instructions to Edit a SDFII Screen_____
Processor Group..............
-

22. At the Endevor Quick-Edit panel, enter the complete Endevor Location, the CCID
(under Action Options), and the Comment. The element name will be your SDFII panel or
group name. The type will be SDF.
If the panel does not exist in Endevor, select the create option, by typing “CR” on the
command line to create a new SDFII object. Otherwise, leave the Command field blank.
Press “Enter”.
If the object does not exist, a blank screen will be displayed. If the object exists, delete all the
lines by using the delete line command.
OES212 TO: DEVELOP/U/ORDNTRY/NNITST04/SDF New Element

COMMAND ===> copy SCROLL ===> CSR
****** ***************************** Top of Data ******************************
''''''
''''''
''''''
''''''
''''''
''''''
''''''
''''''
''''''
''''''
''''''
''''''
''''''
''''''
''''''
****** **************************** Bottom of Data ****************************

not found
23. At the Endevor Quick-Edit panel, Enter “COPY” in the Command field.
Menu RefList Utilities Help
Edit/View - Copy
Command ===>
More: +
"Current" Data Set: USERID.QERCVY04.RECOVERY
From ISPF Library:

Project . . .
Group . . . . . . . . . . . . .
Type . . . .
Member . . . (Blank or pattern for member selection list)
From Other Partitioned or Sequential Data Set:

Data Set Name . . . 'TEST.ENDEVOR.NNITST04.DGIBMS(OES2122)'
Volume Serial . . . (If not cataloged)
Data Set Password . . (If password protected)
Line Numbers (Blank for entire member or sequential data set)

First line . . . .
Last line . . . . .
Number type . . . . (Standard, ISPFstd, COBOL, or Relative)
Figure 4-183: Endevor Quick-Edit Copy Panel

24. At the Endevor Quick-Edit Copy panel, enter the SDFII BMS library and member name
of your panel (see Error: Reference source not found). Press “Enter” to copy your BMS
macro into Endevor.
WILLTEST TO: EDUCDEV/U/MISC/SPGTST04/SDF COLUMNS 00001 00072

****** ***************************** Top of Data ******************************
000010 PRINT ON,NOGEN
000020 OES212 DFHMSD TYPE=MAP,LANG=COBOL,MODE=INOUT,SUFFIX=2
000030 TITLE 'SDF: OES212 OES212
000040 OES212 DFHMDI SIZE=(24,80),CTRL=(HONEOM,FREEKB),COLUMN=SAME, *
000050 LINE=NEXT,DATA=FIELD,TIOAPFX=YES,JUSTIFY=(LEFT), *
000060 OBFMT=NO
000070 DFHMDF POS=(1,1),LENGTH=9,INITIAL='SYSTEM :',ATTRB=(PROT,BRT)
000080 * OES212SYSID OES212SYSID
000090 OES212S DFHMDF POS=(1,11),LENGTH=2,JUSTIFY=(LEFT,BLANK),INITIAL='OE', *
000100 ATTRB=(PROT,NORM)
000110 DFHMDF POS=(1,14),LENGTH=1,ATTRB=(ASKIP,BRT)
000120 DFHMDF POS=(1,27),LENGTH=26, *
000130 INITIAL='ORDER ENTRY SELLING SYSTEM',ATTRB=(ASKIP,BRT)
000140 * OES212CURRDATE OES212CURRDATE
000150 OES212C DFHMDF POS=(1,72),LENGTH=8,JUSTIFY=(LEFT,BLANK),ATTRB=(ASKIP,N*
000160 ORM)
000170 DFHMDF POS=(2,1),LENGTH=9,INITIAL='PROGRAM :',ATTRB=(ASKIP,BRT*
000180 )
000190 * OES212PGMCD OES212PGMCD
000200 OES212P DFHMDF POS=(2,11),LENGTH=2,JUSTIFY=(LEFT,BLANK),INITIAL='12', *
000210 ATTRB=(ASKIP,NORM)

not found
25. Your SDFII BMS macro has now been copied into Endevor. Press “PF3” to generate the
Endevor element.
not found
The Endevor Generate Process
The Endevor generate process for SDFII objects will:
o Copy the group source to the appropriate Endevor library.
o Copy the generated DSECT to the appropriate Endevor library.
o Copy all panels to the appropriate Endevor library.
o Assemble the BMS source to produce the CSECT (load module).
o Add the listing to Endevor.
not found
9. Troubleshooting Endevor Problems
1. How to do a Security Trace
To turn on the security trace, enter the following command on any TSO command line:
TSO ESITRACE START
Then, go into Endevor or QuickEdit. You will see messages like these below:
ENCS101I Entity=PROD.ACTION.PROD.MISC.MISC.RETRIEVE
ENCS101I User $WALTHE access is allowed from LAT
ENCS101I RACROUTE RC=0000 RACHECK RC=0000 Reason=0000
ENCS101I Format=0004 Pass=0000 Auth=READ ACEE=00000000
ENCS101I Class=$ENDEVOR Log=NONE Func=ADD
ENCS101I Scale=0....+....1....+....2....+....3....+....4....
ENCS101I Entity=DEVELOP.ACTION.UNIT.MISC.NNITST04.ADD
ENCS101I RACROUTE RC=0000 RACHECK RC=0000 Reason=0000
ENCS101I Format=0004 Pass=0000 Auth=READ ACEE=00000000
ENCS101I Class=$ENDEVOR Log=NONE Func=SIGNOVR
ENCS101I Scale=0....+....1....+....2....+....3....+....4....
ENCS101I Entity=DEVELOP.ACTION.UNIT.MISC.NNITST04.SIGNOVR
Figure 4-185: Security Trace Messages

Whenever you see the word DENIED for a resource you need, copy and paste the text into an
email, and send to Data Security Team.
To turn off the security trace, enter the following command on the TSO command line:
TSO ESITRACE STOP

not found
2. Easytrieve
If the LINESIZE on your REPORT is greater than 132 characters you may receive the
following error:
*******B070 VALUE NOT WITHIN ACCEPTABLE RANGE - LINESIZE
This occurs when you do not code the record format in the FILE statement. The following is
an example of an Easytrieve program where this error will occur:
PARM LINK (PGMNAME1 R)

*
FILE FILEIN
*
FIELD-01 1 3 A HEADING ('FIELD 01')
*
FILE PRT1 PRINTER
*
JOB INPUT FILEIN
*
PRINT REPORT-01
*
REPORT REPORT-01 +
PRINTER PRT1 +
LINESIZE 200
*
TITLE 1 'I N V E N T O R Y R E P O R T'
TITLE 2 'SPIEGEL CORPORATION'
*
LINE 1 FIELD-01 +
FIELD-02 +
FIELD-03 +
FIELD-04 +
FIELD-05
Figure 4-186: Original Easytrieve Program (with error)

not found
This can be corrected by adding the record format to the FILE statement. The following is the
corrected version of the example Easytrieve program:
PARM LINK (PGMNAME1 R)

*
FILE FILEIN
*
*
FILE PRT1 PRINTER FB(201 27939)
*
JOB INPUT FILEIN
*
PRINT REPORT-01
*
REPORT REPORT-01 +
PRINTER PRT1 +
LINESIZE 200
*
TITLE 1 'I N V E N T O R Y R E P O R T'
TITLE 2 'SPIEGEL CORPORATION'
*
LINE 1 FIELD-01 +
FIELD-02 +
FIELD-03 +
FIELD-04 +
FIELD-05
Figure 4-187: Corrected Easytrieve Program (without error)

Note: The record length (201 in this example) must be 1 larger than the LINESIZE (200). This will allow for
the carriage control character. The block length (27939) must be a multiple of the record length (201).
Another alternative to this method is to code FB(201 0) on the FILE statement. Then you must code the DCB
information, including the BLKSIZE, in the JCL.
not found
3. SQL Error -805
A -805 error occurs when the timestamp within the DBRM from which the plan/package is
bound does not match the timestamp in the load module. This section documents a way to
determine why you are receiving -805 errors.
Menu ISPF-Util Compilers Options Status Help

------------------------------------------------------------------------------
SPIEGEL GROUP MAINFRAME PRIMARY OPTION MENU
Option ===> U
0 Settings Terminal and user parameters

1 View Display source data or listings
2 Edit Create or change source data
3 ISPF-Util Perform ISPF utility functions
6 Command Enter TSO or Workstation commands
A APP-TOOLS Application Programming tools
B Business ISPF based Business Functions
C Database Database Tools
D DASD Storage Related Functions
O OPS Operations & System Programmers tools
U Utilities Common Mainframe Tools & Utilities
X Exit Leave ISPF
I Index Roadmap of Old Panels to New Panels

Y OLD Last Chance to go to the Old Panels
Enter X to Terminate using log/list defaults
Figure 4-188: Spiegel Group Mainframe Primary Option Menu

1. At the Spiegel Group Mainframe Primary Option Menu panel, enter Common
Mainframe Tools & Utilities by typing “U” on the option line.
not found
----------------------- Common Mainframe Utilities -----------------------
OPTION ===> DB2
USERID - USERID
1 - BookManager READ (Online Documentation) TIME - 10:03
9 - Invoke PDSTools PDS utility program TERMINAL - 3278
F - File-AID Interactive File Manipulation System DATE - 02/06/07
FA87 - File-AID NEW -- Version 8.7 JULIAN - 02.158
IM - IMPACT Problem Management & Change Scheduling SYSID - S220
Q - SDSF Spool Display and Search Facility
R - CA-VIEW Sysout Archival and Retrieval
SC - Super Catalog Search
CA1 - Tape Management System
CA7 - Job Scheduling System
CA11 - ARTS Automatic Rerun Tracking System
TAO - Totally Automated Office Electronic Mail
SAS - SAS interactive System
IPCS - Problem Analysis
V - Control VPS Printers
X EXIT - Terminate ISPF using log and list defaults
Figure 4-189: Common Mainframe Utilities

2. At the Common Mainframe Utilities panel, enter DB2 Products Main Menu by typing
“DB2” on the option line.
-------------------- DB2 Products Main Menu - S220 - USERID -------------

Product ===> BMC
DB2 SSID ===> DB2T
------------ IBM Products ------------ | SSID ---- Spiegel ---

DB2I - DB2 Product | A DSNA - Prod REMOTE SYSTEM
QMF - Query Management Facility | P DSNP - Prod REMOTE SYSTEM
QMFM - QMF (QMFPRINT DISP=MOD) | Q DB2Q - Prod REMOTE SYSTEM
| T DB2T - Test LOCAL SYSTEM
---------- Vendor Products ---------- | X DB2X - Test LOCAL SYSTEM
FADB2 - FILE-Aid/DB2 | Z DB1Z - Test LOCAL SYSTEM
RDX - File-AID/RDX | Y DB2Z - Test LOCAL SYSTEM
| G DB2G - Test REMOTE SYSTEM
I - Insight for DB2 | 3 DOX3 - Prod REMOTE SYSTEM
BMC - BMC Products | -- Eddie Bauer --
| E DSN - Prod REMOTE SYSTEM
| B DSNT - Test REMOTE SYSTEM
ST - Startool | - Newport News --
BND - CMS Copy/Bind Modules | H DBP1 - Prod REMOTE SYSTEM
TEST - Test Ver. Vendor Products | N DBT1 - Test REMOTE SYSTEM
MISC - Misc. Functions |
HLP - Brief Help
Figure 4-190: DB2 Products Main Menu

3. At the DB2 Products Main Menu panel, enter BMC Products by typing “BMC” on the
Product line. The DB2 SSID is the DB2 subsystem in which you are working. In the
example above, “DB2T” is the DB2 SSID.
not found
---------------------DB2 Appl Administration - S220 - USERID -------------
Product ===> AD
DB2 SSID ===> DB2T
----------- IBM Products ------------ | SSID ---- Spiegel ---

| A DSNA - Prod REMOTE SYSTEM
| P DSNP - Prod REMOTE SYSTEM
| Q DB2Q - Prod REMOTE SYSTEM
| T DB2T - Test LOCAL SYSTEM
---------- Vendor Products ---------- | X DB2X - Test LOCAL SYSTEM
AD - BMC Admin Tools | Z DB1Z - Test LOCAL SYSTEM
AP - Apptune | Y DB2Z - Test LOCAL SYSTEM
EXP - SQL Explorer | G DB2G - Test REMOTE SYSTEM
LOGM - Logmaster | 3 DOX3 - Prod REMOTE SYSTEM
| -- Eddie Bauer --
| E DSN - Prod REMOTE SYSTEM
| B DSNT - Test REMOTE SYSTEM
| - Newport News --
| H DBP1 - Prod REMOTE SYSTEM
| N DBT1 - Test REMOTE SYSTEM
|
Figure 4-191: DB2 Appl Administration

4. At the DB2 Appl Administration panel, enter BMC Admin Tools by typing “AD” on
the Product line.
----------------- BMC Software Administrative Products for DB2-----------------

COMMAND ===> _________________________________________________________________
2 1 DASD MANAGER for DB2 - Manage or monitor DB2 physical objects
2 CATALOG MANAGER for DB2 - Execute DDL or query DB2 Catalog
3 CHANGE MANAGER for DB2 - Manage changes to DB2 objects/structures
DB2 SSID . . . . . . . DB2T (? = SSID List)

DB2 Catalog Access . . DIRECT (Direct)
Use Shared or Individual product ISPF APPLID? S (S/I - Admin Products only)
Figure 4-192: BMC Software Administrative Products for DB2

5. At the BMC Software Administrative Products for DB2 panel, enter CATALOG
MANAGER for DB2 by typing “2” in the option field.
not found
DB2T- ------------ CATALOG MANAGER 7.1.01 Primary Menu --------------------
Command ===>
Select action and type object information. Then press Enter.
Action 0. (L) List catalog objects (blank same as 0)

1. (S) Search for catalog objects
2. (C) Create objects
3. (G) Grant privileges
4. (O) CATALOG MANAGER options processing
5. (D) DB2 Commands
6. (M) Maintain logs menu
7. (Q) List SQL for edit & execution
Obj type PG 11. DB Database 16. TS Tablespace 21. PL Plan 26. ST Strings
12. SG Stogroup 17. SU SysPrivUser 22. AL Alias 27. LO Location
13. TB Table 18. SY Synonym 23. US User 28. CK Checks
14. VW View 19. PG Package 24. CO Column 29. PR Procs
15. IX Index 20. CI Collection 25. DM DBRM
Qualifier M3711000
Initial attach to DB2T
Copyrights (c) 1987-2001 BMC Software, Inc.
as an unpublished licensed work.
All rights reserved.
Figure 4-193: CATALOG MANAGER 7.1.01 Primary Menu

6. At the CATALOG MANAGER 7.1.01 Primary Menu panel, enter data in the following
fields:
o Leave the Action field blank.
o Enter “PG” in the Obj type field.
o Enter the package name in the Qualifier field.
Note: If you are working with a plan that is not bound with an underlying package, type “PL”
instead of “PG” in the Obj type field.
DB2T-R ------------------------ Package List

--------------- Row 1 to 2 of 2
01
CMD will show commands for this list. Type command and press ENTER
Lists: AL CA CI IM IS IX PA PL PR SY TB TR TS UA US VW
LIKE: M3711000
Cm Collection Id Name Ty Version Owner Bnd Date ValidOper
----v----1----v----2----v----3----v----4----v----5----v----6----v----7----v---
DB2TQA M3711000 DB2CMQA 2002-05-30 Y Y
DESCB2TTEST M3711000 DB2CMTS 2002-06-06 Y Y
******************************* Bottom of data ********************************
Figure 4-194: Package List

7. At the Package List panel, enter Describe Package by typing “DESC” on the line to the
left of the package name. This will bring up detailed information about the package in
question.
not found
DB2T-R ----------------------- Describe Package -------------- LINE 1 OF 576
Package = DB2TTEST.M3711000
-------------------------------------------------------------------------------
FROM SYSIBM.SYSPACKAGE
------------------------------------------------------------------------------
Location . . . : Valid . . . . . : Y
Collection Id : DB2TTEST Operative . . . : Y
Package Name : M3711000 Validate . . . : B
Version . . . . :
Package Owner : DB2CMTS Package Size : 2192
Package Creator : ENDSYSU Average Size : 5272
Qualifier . . . : DB2TTEST Release . . . . : C
Sys entries . . : 0 Explain . . . . : Y
Quote . . . . . : N Host Lang . . . : 3
Comma . . . . . : N Character set : A
Mixed . . . . . : N Decimal 31 . . : N
Defer Prep . . : B Remote . . . . : N
Sqlerror . . . : N Isolation . . . : S
Con Token . . . : X'16F7ADAA0500B08C'
Timestamp . . . : 2002-05-28-15.16.18.434693
Bind Timestamp : 2002-06-06-16.23.55.279665
PC Timestamp : 2002-06-06-16.22.51.893442
Figure 4-195: Describe package

8. At the Describe package panel, write down the Con Token (timestamp). The Con Token
for M3711000 looks like X‘16F7ADAA0500B08C’. Note the DBRM library that was
used in binding the module. Is it the one you expected?
not found
sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss
BROWSE PN.ENDEVOR.UNIT.SPGTST05.DBRMLIB(M3711000) CHARS X'16F7ADAA0500B08C
********************************* Top of Data **********************************
------------------------------------------------------------------------------
DBRM...µUSERID M3711000.7Ý¡..^ð..3.......................................1..Ø.J
CCDD000AEECDCC44DFFFFFFF1FAA00B800F000000000000000000000000000000000000000F0080D
42940000425994004371100067DA500C703002000000000000000000000000000000000000100001
------------------------------------------------------------------------------
.. ..............
00444444444444444444444444444444444444444444444444444444444444444400000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
DBRM...W.......§.......DECLARE FIL_CTRL_TB TABLE ( CORP_CD CHAR ( 1 ) NOT NULL
CCDD001E0000000B0001001CCCCDCDC4CCD6CEDD6EC4ECCDC444CDDD6CC4CCCD444F454DDE4DEDD4
42940036000000F50004003A45331950693D3393D320312350D03697D34038190D010D0563054330
------------------------------------------------------------------------------
, ORIG_PRGM_ID INTEGER NOT NULL , RUN_SQNBR SMALLINT NOT NULL , PRGM_ID INTEGER
64DDCC6DDCD6CC4CDECCCD4DDE4DEDD464DED6EDDCD4EDCDDCDE4DDE4DEDD464DDCD6CC4CDECCCD4
B06997D7974D94095357590563054330B0945D285290241339530563054330B07974D94095357590
------------------------------------------------------------------------------
Figure 4-196: Browse Panel

9. Next, browse the actual DBRM member in either the test
(PN.ENDEVOR.UNIT.xxxxxxxx.DBRMLIB where ‘xxxxxxxx’ is the subsystem name)
or production (PN.ENDEVOR.PRODxxx.DBRMLIB where ‘xxx’ is the company name)
DBRM library. Once inside the member, type “HEX ON” on the command line. Once
hexadecimal has been turned on, search for the Con Token you wrote down in #Error:
Reference source not found, i.e. “F x‘16F7ADAA0500B08C’ ”. The Con Token
is located immediately after the DBRM name. For example, if you browse
PN.ENDEVOR.UNIT.SPGTST05.DBRMLIB(M3711000) and look immediately after the
text M3711000, you will find the Con Token. This Con Token should match the one you
pulled from the DB2 catalog.
not found
sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss
BROWSE PN.ENDEVOR.UNIT.SPGTST05.LOADLIB(M3711000) CHARS X'16F7ADAA0500B08C
------------------------------------------------------------------------------
........à...M3711000.7Ý¡..^ð...............Z.XSQLDA ...m.....D............
000000024001DFFFFFFF1FAA00B8000000000000001E0EEDDCC444000900000C0000000000004444
00000008400E4371100067DA500C01000000000000E9072834100000040303140100000000000000
------------------------------------------------------------------------------
------------------------------------------------------------------------------
á0^.qX}Ð2ÉL\µøo.LX|.L\<.°d..K.M..ðo.M...!.J8K.LY..8cM.M.K.M.M.ÜdM.LYm.M.0ÍM...8à
4FB09EDAF7DEA790DE43DE439813D0D03890D01352DFD0DE23F8D1D0D0D2D1F8D1DE90D1F7D103F4
5000870C2130006F37F030C004AA23480C6F4B82A01824380C834048284040C440384F4105410B84
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Figure 4-197: Browse Panel

10. Next, browse the load lib member. This is trickier.
The test load library names can be found in Section Error: Reference source not found
Error: Reference source not found in Appendix Error: Reference source not found.
The NNI production load libraries are:

PN.ENDEVOR.PRODNNI.LOADLIB (batch)
PN.ENDEVOR.PRODNNI.LOADCICS
The Spiegel production load libraries are:

PN.ENDEVOR.PRODSPG.LOADAIMS
PN.ENDEVOR.PRODSPG.LOADCOMN
PN.ENDEVOR.PRODSPG.LOADCSS
PN.ENDEVOR.PRODSPG.LOADLIB (batch)
PN.ENDEVOR.PRODSPG.LOADOES
The Eddie Bauer production load libraries are:

PN.ENDEVOR.PRODEBI.LOADLIB (batch)
PN.ENDEVOR.PRODEBI.LOADPCAT
PN.ENDEVOR.PRODEBI.LOADPCFC
PN.ENDEVOR.PRODEBI.LOADPDB2
For post-Endevor load members, the Con Token will be listed exactly like in the DB2
Catalog, i.e. x‘16F7ADAA0500B08C’. For pre-Endevor load members, the first four
not found
bytes will occur after the last four bytes, i.e. x‘0500B08C16F7ADAA’. I am not sure why
this is, but it is. The timestamp within the load member should match the timestamp
within the DBRM and DB2 catalog.
not found
11. If the Con Token in the DB2 catalog does not match the Con Token in both the DBRM
and load library members, you’ve got a problem. Some common -805 scenarios are listed
below:
o If the load library Con Token matches the Con Token in the DBRM member, but
neither matches the DB2 catalog, you probably need a rebind. i.e. a move has
occurred but perhaps the bind has failed. This used to happen often on an Endevor
backout but has since been fixed. Another scenario might be that someone has
rebound the package from another DBRM library. i.e. a package in the T3 region at
NNI might have been manually bound with the DBRM from T4.
o Double check the load library you are executing with. Is the STEPLIB correct? Is
there a load library member in a library higher in the CICS concatenation which you
are executing?
o You may have more than one load library member (calling and called) within the
calling load library member. This is rare, but it happened recently. Check for
calling/called load library members residing together.
In most cases, regenerating the module will fix the problem.

not found
4. SQL Error -927
Some developers have experienced unsuccessful installs due to DYN being coded in the
COBOL-COMPILER-PARMS keyword of the OPTIONS element. (See Error: Reference
source not found Error: Reference source not found for details on the OPTIONS element
syntax.) This was corrected by changing the OPTIONS element to NODYN (default).
The DYN parm was causing a -927 SQLERROR on execution. Quickref states:
-927 THE LANGUAGE INTERFACE (LI) WAS CALLED WHEN THE

CONNECTING ENVIRONMENT WAS NOT ESTABLISHED. THE
PROGRAM SHOULD BE INVOKED UNDER THE DSN COMMAND
Explanation: In the TSO environment, the user has attempted to execute an application
program without first establishing the correct execution environment by issuing the
DSN command. In the IMS, CICS, or call attachment facility (CAF) environment, the
user has attempted to execute an application program that is not using the correct
language interface module.
System Action: The statement cannot be executed.
Programmer Response: In the TSO environment, DB2 application programs should be

invoked under the RUN subcommand of the DSN command processor. In the IMS,
CICS or CAF environment check that the application was link-edited with or is
dynamically allocating the correct language interface module. The language interface
modules required in each environment are as follows:
o IMS: DFSLI000
o CICS: DSNCLI
o CAF: DSNALI
o TSO: DSNELI
The DYNAM option can result in the incorrect language interface module being
loaded at runtime.
SQLSTATE: 51006
-------------------------------------------------------- End of Quickref
--------------------------------------------------------
Note: Any static calls will need to change to dynamic calls in db2 programs.
The following was taken from DB2 UDB for OS/390 V6 Application Programming and SQL
Guide:
TSO and IMS

not found
You can specify the option DYNAM when compiling a COBOL program if you use
VS COBOL II or COBOL/370, or if you use OS/VS COBOL with the VS COBOL II
or COBOL/370 run-time libraries.
IMS and DB2 share a common alias name, DSNHLI, for the language interface
module. You must do the following when you concatenate your libraries:
o If you use IMS with the COBOL option DYNAM, be sure to concatenate the
IMS library first.
o If you run your application program only under DB2, be sure to concatenate
the DB2 library first.
CICS and CAF
You must specify the option NODYNAM when you compile a COBOL program that
includes SQL statements. You cannot use DYNAM.
Because stored procedures use CAF, you must also compile COBOL stored
procedures with the option NODYNAM.
--------------------- End of DB2 UDB for OS/390 V6 Application Programming and SQL
Guide ---------------------
Error: Reference source not found. Error: Reference source
not found
A. Appendix — Supplementary Information
Topics covered in Appendix Error: Reference source not found include:
Error: Reference source not found Error: Reference source not found
I. Attempting to Overlay Someone Else’s Work
Some CA-Endevor and Quick-Edit actions may fail due to another Spiegel developer working
in the same area. To prevent your request from overlaying another person’s work, your
request will be denied and you will be given a message saying “*OVERLAYING ANOTHER
USER” like the one presented below.
-------------------------- Element Selection List --- *OVERLAYING ANOTHER USER

Element Options:

-- ---------- ---------- -------- ----------- ----- -------- --------- -----
__ CSSB0009 COBOLLE DEVELOP U CORP NNITST01 01.00
E_ CSSB0010 COBOLLE DEVELOP U CORP NNITST01 01.01
__ CSSB0010 OPTION DEVELOP U CORP NNITST01 01.02
__ CSSB0015 OPTION DEVELOP U CORP NNITST01 01.01
__ CSSO0000 OPTION DEVELOP U CORP NNITST01 01.00
Figure A-1: Overlaying Another User Example

Respond by doing one of the following:
1. Choose a different subsystem name
2. Wait until the other user moves from the target area of your request
3. Explicitly SIGNIN the element to transfer ownership. For further information, see Section Error:
Reference source not found Error: Reference source not found in Appendix Error: Reference source not
found.
See Section Error: Reference source not found Error: Reference source not found for further information on how
to use the master display command and who is working the element in the UNIT stage.
II. Automatic Notifications
CA-Endevor and Quick-Edit automatically record “signout” information for activities

performed by each user. When more than one user has an element “signed out”, notifications
are prepared automatically for review. Whenever a Retrofit action occurs, then messages
about the Retrofit actions are also prepared for each impacted user. When a user requests
entry into the CA-Endevor or Quick-Edit panels, then pending Signout and Retrofit messages
are presented first.
Below is an example of automatic notifications for a single user.

Retrofit notification
messages
EDIT
EDIT UD6W.NDVSO001.D730417.S56172
UD6W.NDVSO001.D730417.S56172 Columns
Columns 00001
00001 00072
00072
Command
Command ===>
===> Scroll
Scroll ===>
===> CSR
CSR
******
****** *****************************
***************************** Top
Top of
of Data
Data ******************************
******************************
000001
000001 ELEMENTS
ELEMENTS IN
IN RETROFIT
RETROFIT
000002
000002 ------------------------------------------------------------------------
------------------------------------------------------------------------
000003
000003 ** RETROFIT
RETROFIT ACTION
ACTION ON
ON TESTASM
TESTASM TYPE
TYPE ASM
ASM .. RETROFIT
RETROFIT ACTION
ACTION AJSU4942
AJSU4942
000004
000004 DVLP/1/CORP/TSTBAT2/TESTASM/ASM
DVLP/1/CORP/TSTBAT2/TESTASM/ASM
000005
000005 ** SOURCE
SOURCE PLACED
PLACED INTO
INTO VTSTMIS.RETROFIT.TESTASM.AJSU4942.SOURCE(DER#12)
VTSTMIS.RETROFIT.TESTASM.AJSU4942.SOURCE(DER#12)
000006
000006 ------------------------------------------------------------------------
------------------------------------------------------------------------
000007
000007 ------
------ THE
THE FOLLOWING
FOLLOWING ELEMENTS
ELEMENTS ARE
ARE ALSO
ALSO SIGNED
SIGNED OUT
OUT BY
BY THESE
THESE USERS
USERS ------
------
000008
000008 ELEMENT
ELEMENT TYPE
TYPE USERID
USERID ENV
ENV SYSTEM
SYSTEM SUBSYS
SUBSYS CCID
CCID COM
COM
000009
000009 ------------------------------------------------------------------------
------------------------------------------------------------------------
000010
000010 MAGICJCL
MAGICJCL JCL
JCL UTMQ
UTMQ DVLP
DVLP INST
INST INSBAT1
INSBAT1 TEST
TEST HAV
HAV
000011
000011 TESTASM
TESTASM ASM
ASM UDBZ
UDBZ PROD
PROD CORP
CORP TST
TST PRZ0003
PRZ0003 TES
TES
000012
000012 TESTASM
TESTASM ASM
ASM UPBR
UPBR DVLP
DVLP CORP
CORP TSTBAT3
TSTBAT3
******
****** ****************************
**************************** Bottom
Bottom of
of Data
Data ****************************
****************************
Signout notification
messages
Figure A-2: Automatic Notification Example
Developers who receive Signout messages should contact the other developers involved,
determine who should manually retrofit the code into their own copy and then complete a
manual retrofit action. The manual retrofit can be conducted using any of the CA-PDM,
SUPERC utilities or other utilities.
III. Backups of Original Source Files
This section has not been defined at this time.
See Mike McMahon.

IV. COBOL LE Differences
Cobol LE vs. Cobol II
Here is a list of differences that we have encountered with Cobol LE so far:
1. Replace verb on the copy statement

Previously we coded it like this:
COPY FDCCRJWW REPLACING ==:CCRJW:== BY ==REJ-I-==.
Now we must code it like this:

REPLACE ==:CCRJW:== BY ==REJ-I-==.
FD REJECT-REPORT-FILE.
COPY FDCCRJWW.
REPLACE OFF.
2. Cobol II cannot call a Cobol LE program nor can Cobol LE call a Cobol II
program. This produces unpredictable results.
3. On the FD entry
Block contains zero records
and
Label records clauses treated as comments.
4. Panvalet inserted field: PANVALET-DSN-DATE-LVL is not supported in Endevor.

Programs that use this field will need to have it re-coded.
Cobol LE Functions
Error: Reference source not found below lists each of the Intrinsic Functions provided by
Cobol LE. This table also shows the function type, the argument types, and the returned value
for each function.
Function and argument types are abbreviated as follows:
ALP = alphabetic
NUM = numeric
INT = integer
AN = alphanumeric
A function shown with a single argument type requires a single argument of that type. For
example, if argument type is shown as:
ALP
This indicates that the associated function requires a single alphabetic function.
If multiple argument types are shown for a given function, then that function takes multiple
arguments of the types shown and in the order shown. For example, argument types shown
as:
NUM INT
This indicates that the associated function requires a numeric first argument and an integer
second argument.
An argument type shown as XXX... indicates that a variable number of arguments of that
type are allowed. For example, an argument type shown as:
NUM...
This indicates that the associated function requires a variable number of numeric arguments.
Example:
FUNCTION ASIN (argument)

or
FUNCTION LENGTH(string)
Since the date proper is in the first 8 bytes of the returned date field, the best way to use
Current-date is as follows:
MOVE FUNCTION CURRENT-DATE (1:8) TO WS-DATE
Table 15: Cobol LE Functions

FCTN
Function-Name Type Argument(s) Value Returned
ACOS NUM NUM Arccosine of argument
ANNUITY NUM NUM INT Ratio of annuity paid for periods interest
specified by the NUM argument to an initial
investment of one
ASIN NUM NUM Arcsine of argument
ATAN NUM NUM Arctangent of argument
CHAR AN INT Character of program collating sequence in
position specified by INT argument
COS NUM NUM Cosine of argument
FCTN
CURRENT- AN None Current date/time and difference from
DATE Greenwich Mean Time.
This function returns a 21 byte value as
follows:
1-4 Four numeric digits of the year in the
Gregorian calendar.
5-6 Two numeric digits of the month of the
year, in the range 01 through 12.
7-8 Two numeric digits of the day of the
month, in the range 01 through 31.
9-10 Two numeric digits of the hours past
midnight, in the range 00 through 23.
11-12 Two numeric digits of the minutes past
the hour, in the range 00 through 59.
13-14 Two numeric digits of the seconds past
the minute, in the range 00 through 59.
15-16 Two numeric digits of the hundredths
of a second past the second, in the
range 00 through 99.
17 Either the character “-” or the character
“+”. The character “-” is returned if the
local time indicated in the previous
character positions is behind Greenwich
Mean Time. The character “+” is
returned if the local time indicated is
the same as or ahead of Greenwich
Mean Time.
18-19 If character position 17 is “-”, two
numeric digits are returned in the range
00 through 12 indicating the number of
hours that the reported time is behind
Greenwich Mean Time. If character
position 17 is “+”, two numeric digits
are returned in the range 00 through 13
indicating the number of hours that the
reported time is ahead of Greenwich
Mean Time.
20-21 Two numeric digits are returned in the
range 00 through 59 indicating the
number of additional minutes that the
reported time is ahead of or behind
Greenwich Mean Time, depending on
whether character position 17 is “+” or
“-”, respectively.
FCTN
DATE-OF- INT INT Standard date equivalent (YYYYMMDD) of
INTEGER INT date argument
DAY-OF- INT INT Julian date equivalent (YYYYDDD) of INT
INTEGER date argument
FACTORIAL INT INT Factorial of argument
INTEGER INT NUM The greatest integer not greater than the
argument
INTEGER-OF- INT INT Integer date equivalent of INT standard date
DATE (YYYYMMDD) argument
INTEGER-OF- INT INT Integer date equivalent of INT Julian date
DAY (YYYYDDD) argument
INTEGER-PART INT NUM Integer part of argument
LENGTH INT ALP or Length of argument
NUM or AN
LOG NUM NUM Natural logarithm of argument
LOG10 NUM NUM Logarithm to base 10 of argument
LOWER-CASE AN ALP or Letters in the argument set to lowercase
AN
MAX AN ALP… or Value of maximum argument; note that the
INT INT… or type of function depends on the arguments
NUM NUM… or
AN AN…
MEAN NUM NUM… Arithmetic mean of arguments
MEDIAN NUM NUM… Median of arguments
MIDRANGE NUM NUM… Mean of minimum and maximum arguments
MIN AN ALP… or Value of minimum argument; note that the
INT INT… or type of function depends on the arguments
NUM NUM… or
AN AN…
MOD INT INT INT First argument modulo second argument
NUMVAL NUM AN Numeric value of simple numeric string
NUMVAL-C NUM AN or Numeric value of numeric string with optional
AN AN commas and currency sign
ORD INT ALP or Ordinal position of the argument in collating
AN sequence
ORD-MAX INT ALP… or Ordinal position of maximum argument
NUM… or
AN…
ORD-MIN INT ALP… or Ordinal position of minimum argument
NUM… or
AN…
FCTN
PRESENT- NUM NUM Present value of a series of future period-end
VALUE NUM… amounts, represented by all the arguments
other than the first, at a discount rate specified
by the first argument
RANDOM NUM INT or Random number
none
RANGE INT INT… or Value of maximum argument minus
NUM NUM… Value of minimum argument; note that the
type of function depends on the arguments
REM NUM NUM NUM Remainder of first argument divided by
second
REVERSE AN ALP or Characters of the argument in reverse order
AN
SIN NUM NUM Sine of the argument
SQRT NUM NUM Square root of the argument
STANDARD- NUM NUM… Standard deviation of arguments
DEVIATION
SUM INT INT… or Sum of arguments; note that the type of
NUM NUM… function depends on the arguments
TAN NUM NUM Tangent of argument
UPPER-CASE AN ALP or Letters in the argument set to uppercase
AN
VARIANCE NUM NUM… Variance of arguments
WHEN- AN None Date and time when program was compiled
COMPILED
V. Endevor Batch Jobs
Table 16: Endevor Batch Jobs

Job Name Job Description Run Frequency
DB2 Bind Jobs to execute the bind for DB2 programs After generate and
Jobs See Error: Reference source not found move actions.
Section 4.7.3
J289DCRP Creates the “Endevor crisis activity for last 24 Daily at 06:00.
hours” report.
J289DPRP Creates the “Endevor production activity for last Daily at 06:00.
24 hours” report.
J289DSI1 Deletes outdated Signout entries from Daily Monday thru
10
Endevor’s Signout file. Signout entries for Friday at 03:45.
elements that have been moved to PROD, or
that have been deleted from Endevor locations
are eligible for deletion.
Job Name Package Automation Job Executes Run Frequency

Aapproved Packages
JOBs submitted by CA7
J289SPKA PS* packages. Daily every 15
minutes from 07:00 to
18:00
J289QPKA AC* packages. Triggered by
J289SPKA.
J289APKA AS* packages. Triggered by
J289QPKA.
J289NPKA NT* packages. Triggered by
J289APKA.
JOBs submitted by Change Management
J289BPKA PRWE* (Eddie Bauer Online) packages. On Request.
J289EPKA PRB* (All Batch) packages. On Request.
J289GPKA PRWS* (Spiegel Online) packages. On Request.
J289IPKA PRWN* (NNI Online) packages. On Request.
J289DPKA Currently not in use.
10
See Endevor Administrator User Guide Section 6.6 - Signouts Cleanout job for more details on this job.
VI. Endevor Location Names
Environments:
Crisis Crisis Environment
Develop Develop Environment
Obsolete Archive Environment
Prod Prod Environment
QA QA Environment
Stages:
Environment Stage 1 Stage 2
Crisis ETST (C) Crisis Test EMER (E) Crisis Prod
Develop UNIT (U) Unit Test NTGN (N) Integration Test
Obsolete NULL (X) Null ARCH (A) Archived
Prod PSTG (S) Production Staging PROD (P) Production
QA ASTG (A) QA Staging ACPT (Q) Acceptance Test
Systems:
ADMINTSTTest area for Endevor admins
CREDIT Consumer Credit
CSS Customer Serv Sys
DFSAUDIT Support Processes
EDUC Education
FINANCE Finance
HAMPTON Marketing Group
LOGISTCS Logistics
MARKET Marketing
MDSE Merchandising
MISC Miscellaneous
MRKDEV Marketing Dvlp
NNIMRKU NNI Marketing
ORDNTRY Order Entry
SPGMRKU SPIEGEL Marketing
STORSYS Store Systems
TECH Tech Support
Subsystems:
Develop & QA
EBITST01 Eddie Bauer TST1 CICS/Batch
NNITST01 Newport News T CICS/Batch
NNITST02 Newport News T1 CICS/Batch
SPGTST01 Spiegel TEST1 CICS/Batch
Crisis, Prod, & Obsolete
Subsystem will be the same as system
Processor Groups: 11
EBI Eddie Bauer Processor Group
NNI Newport News Processor Group
SPG Spiegel Processor Group
12
Types:
AFP Advanced Form Processing
AFPFDEF Adv Form Prt Form Definitions
AFPOVER Adv Form Prt Overlay Definitions
AFPPDEF Adv Form Prt PAGE Definitions
APSAPPL APS Application Description
APSDATA APS Data Description
APSINCL APS Include For ++INCLUDE Expansion
APSPROG APS Program Description
APSREPT APS Report Description
APSSCRN APS Screen Description
ASM ASM LE/370 Procesing
BMS CICS BMS Maps
CLIST ISPF Command List
CNTL Control and Parameter Cards
COBOLLE COBOL LE/370 Procesing
COPY COBOL Copybooks
CPLUS C++ Programs
DOC DOCUMENTATION
ETRV Easytrieve
EZLETR Easytrieve Macros
INCLUDE Panvalet Type ++INCLUDES
JCL Job Control Cards
LINKDECK Linkage Editor Control Cards
LOAD Load modules without source
MSG ISPF Messages
OPTIONS Compile and Link Options
PANEL ISPF Panels
PROC Catalogued Procedures
REXX REXX Execute
SAS Statistical Analysis System
SDF SDF II
SKEL ISPF Skeletons
11
Not all Processor groups will be available in every Environment/Stage/System/Subsystem/Type combination.
12
Not all Types will be available in every Environment/Stage/System/Subsystem combination.
VII. Links to Additional Information
1. Application Development Endevor and Impact Change Ticket Standards.

http://www.corp.spiegel.com/is/isproject/standards/EndevorPackageTicketStd.doc
2. List of libraries used as source for the conversion to Endevor 3.9:

\\Sphqois1\group\D801\IS_DOCS\Public\Endevor UG update req\ENDEVOR LIBS.xls
3. Naming standards.
http://www.corp.spiegel.com/is/isproject/standards/JCL/JCLNamingStandards.pdf
VIII. Package Messages
Most package errors are reported on the package CAST action and are reported by the
component validation feature of Endevor packaging. During component validation, Endevor
compares footprint information from the current Endevor inventory with footprint information
gathered at the time of a Generate. If critical discrepancies are found, then an error condition
is returned. Common error conditions are those below.
FPVL003E NO FOOTPRINT MATCH ANYWHERE
There are no Master Control File records for the element that match the location and event
information in the footprint. Generate the element again and CAST the package.
FPVL004E FOOTPRINT ONLY FOUND IN PRIOR STAGE
Only the footprint information matches the Master Control File information for a previous
stage. Generally, this message is given for an input component that was not packaged.
Determine whether the input component should be included in the package. If yes, then
rebuild the package and CAST it again. If not, then the content of your package or the input
component and its related inventory, must be taken to a different map location. If the package
inventory is in the DVLP environment, select a different subsystem.
FPVL005E FOOTPRINT LAST LEVEL DATE MISMATCH
The last level date and time information on the footprint does not match the date and time
information from the Master Control File. Generate the element again and CAST the package.
IX. Package Names
The following data is included here for ease of use only. See Application Development
Endevor and Impact Change Ticket Standards at
http://www.corp.spiegel.com/is/isproject/standards/EndevorPackageTicketStd.doc for the
most up-to-date Package Name standards.
The format of the Spiegel 16-byte package name is:

<Prefix><Window or Batch Indicator><Corporate LPAR Code><RSS Number><Initials><Number>
<Prefix> is a 2-byte prefix that indicates the Endevor stage name that is targeted by the package. See Error:
Reference source not found below. <Window or Batch Indicator> indicates “W” for installations during the
downtime window (on-lines) or “B” for batch installations or installations that can execute at any time.
<Corporate LPAR Code> indicates “S” for Corporate/Spiegel Catalog LPAR, “E” for Eddie Bauer LPAR, or
“N” for NNI LPAR. <RSS Number> is the 4-character year and 4-character number of the RSS associated with
the change. – Example 2002-351 is entered “20020351”. <Initials> indicates the 2 character initials of the
developer. <Number> indicates the sequential number assigned by the developer. This is 2 characters, and must
be unique for each developer’s package.
Table 17: Package Name Format
Package Prefix Package Name Package Name Description
Action Examples For Examples
UNIT to NT NTWS20020351KR01 NT - Prefix, W - Window
NTGN Indicator,
S - Corporate LPAR Code,
20020351 - RSS Number,
KR - Initials, 01 - Number
NTGN to AS ASBE20020351KR02 AS - Prefix, B - Batch Indicator,
ASTG E - Corporate LPAR Code,
ASTG to AC ACWN20020351KR03 AC - Prefix, W - Window
ACPT Indicator,
N - Corporate LPAR Code,
ACPT to PS PSBS20020351KR04 PS - Prefix, B - Batch Indicator,
PSTG S - Corporate LPAR Code,
PSTG to PR PRWE20020351KR05 PR - Prefix, W - Window
PROD Indicator,
E - Corporate LPAR Code,
Package Prefix Package Name Package Name Description
Action Examples For Examples
PROD to AR ARBN20020351KR06 AR - Prefix, B - Batch Indicator,
ARCH N - Corporate LPAR Code,
ETST to EM EMWS20020351KR07 EM - Prefix, W - Window
EMER Indicator,
S - Corporate LPAR Code,
EMER to EU EUBE20020351KR08 EU - Prefix, B - Batch Indicator,
UNIT E - Corporate LPAR Code,
X. Quick Edit Commands
The following commands can be used when editing an element in the Quick Edit. These
commands can be used in addition to the normal ISPF editor commands.
COPYELM - Copy Element

See Error: Reference source not found Error: Reference source not found for
an example.
EXPINC - Expand Includes
an example.
WIPCHANG - Work In Process Changes
an example.
XI. Sample Job Card
Use the following as a job card to submit batch Endevor jobs:

// NOTIFY=&SYSUID
/*ROUTE PRINT R999
Change USERID, Accounting Information (T###,00), and printer (R999) to your specific
values.
Note: When generating (compiling) a program, CLASS must be “N” for programs using
IDMS.
XII. SIGNIN to change ownership
If it becomes necessary to change ownership of an element from one user to another, the following steps may be
taken. Anyone can perform these steps on behalf of another.

Option ===> 4;2;8 Scroll ===> PAGE

-- -------- ----------------------------------------
2 QA QA ENVIRONMENT
******************************* Bottom of data *******************************
Figure A-3: Changing Ownership Example

1. From the main CA-Endevor for MVS Environment Selection panel 13, request the SIGNIN foreground
action screen.
------------------------------ SIGNIN ELEMENTS --------------------------------

OPTION ===>
SI - Sign-in element M - Master C - Changes

ENVIRONMENT ===> DEVELOP OVERRIDE SIGNOUT ===> Y (Y/N)
SYSTEM ===> CREDIT SIGNOUT TO ===>
SUBSYSTEM ===> NNITST01
ELEMENT ===> ELEMENTX
TYPE ===> COBOLLE
LIST OPTIONS:
WHERE CCID EQ ===>
WHERE USER EQ ===>
Figure A-4: Signin Elements Panel

2. Clear the Where User Eq field. Enter the From Endevor information, the receiving userid as the Signout
To, set the Override Signout field to “Y” and press the <Enter> key.
Note: A successful SIGNIN will enable the designated userid to update the source at the specified
Endevor location. The original owner may update the element at the designated location until the new
owner actually applies a change there.
13
XIII. Stages and their activities
This section describes the different activities that occur in the Endevor stages.
Table 18: Stages and their activities

Environment Develop QA Prod Crisis
Stage UNIT NTGN ASTG ACPT PSTG PROD ETST EMER
Compile Y Y Y
Compile with
Y Y
Xpediter
JCLPREP /
Y
JCLCheck
DB2 Bind Y Y Y Y Y Y
Chang
QA
Approvers QA e Oper-
N/A None None Manag N/A
needed 14 Tester Manag ations
e-ment
e-ment
14
These are the approvers needed to move an element into the stage mentioned.
XIV. Subsystems and their Corresponding Locations for Testing.
The value specified for SUBSYSTEM is used by Endevor to target one of the testing areas provided for your
system. Endevor processors will use the following libraries:
Table 19: Subsystems and their Corresponding Locations for Testing
Subsyste CICS DB2 Recommended
m Region Creator Plan Name 15 DDIO 16 Loadlib
EBITST01 CICSTST1 DSNTTEST Element PN.ENDEVOR.EBITST01.DDIO PN.ENDEVOR.UNIT.EBITST01.LOADLIB
EBITST04 CICSUMER DSNTQA Element PN.ENDEVOR.EBITST04.DDIO PN.ENDEVOR.UNIT.EBITST04.LOADLIB
NNITST01 CICST DBT1T ElementT PN.ENDEVOR.NNITST01.DDIO PN.ENDEVOR.UNIT.NNITST01.LOADLIB

NNITST02 CICST1 DBT1T1 ElementT1 PN.ENDEVOR.NNITST02.DDIO PN.ENDEVOR.UNIT.NNITST02.LOADLIB
17
SPGTST01 DB2TQA U####### PN.ENDEVOR.SPGTST01.DDIO PN.ENDEVOR.UNIT.SPGTST01.LOADLIB
SPGTST02 TEST2 DB2TTEST M####### PN.ENDEVOR.SPGTST02.DDIO PN.ENDEVOR.UNIT.SPGTST02.LOADLIB
SPGTST03 TEST3 DB2XQA U####### PN.ENDEVOR.SPGTST03.DDIO PN.ENDEVOR.UNIT.SPGTST03.LOADLIB
SPGTST04 TEST4 DB2XPROB B####### PN.ENDEVOR.SPGTST04.DDIO PN.ENDEVOR.UNIT.SPGTST04.LOADLIB
or DB2X4
SPGTST07 TEST7 DB2TPROB B####### PN.ENDEVOR.SPGTST07.DDIO PN.ENDEVOR.UNIT.SPGTST07.LOADLIB
or DB2T7
SPGTST08 TEST8 DB2XTEST M####### PN.ENDEVOR.SPGTST08.DDIO PN.ENDEVOR.UNIT.SPGTST08.LOADLIB
Developers can choose a subsystem associated with a CICS region, when their intent is to conduct testing within
that region.
PN.ENDEVOR.PROD.LOADLIB
PN.ENDEVOR.PROD.PROCLIB
15
Where “Element” represents the Endevor element name, and “#######”represents the last seven characters of
the Spiegel Endevor element name. See Stagename-PLAN-NAME in Error: Reference source not found for
additional information.
16
The DDIO for all batch programs is TEST.COMPUWAR.ENDEVOR.DDIO.
17
TEST1 does not use the Endevor test loadlibs.
not found
B. Appendix — Glossary of Terms
Access Security Table
An Endevor table that defines Environment(s) for each user that has access. There is one
Access Security Table for each site.
ACM
See Automated Configuration Manager.
Actions
Commands used to maintain or otherwise act against Elements. See Add, Archive, Copy,
Delete, Display, Generate, List, Move, Print, Restore, Retrieve, Signin, Transfer and
Update.
Add
Action used to place members from an external data set under control of Endevor.
Approval
An electronic “signoff” mechanism for Packages. Approval may be required for a Package
before it can be executed.
Approved
The status of a Package after required Approvers have reviewed and “signed off” on a
Package by approving it.
Approver
A person authorized to “signoff” on a Package prior to execution. Signing off on a Package
means reviewing information contained in a Package and approving or denying it.
Approver Group
A collection of one or more Approvers. Approver Groups are defined within each
Environment and can be associated with particular inventory areas.
Approver Group relationship
The relationship established between an Approver Group and one or more inventory areas,
authorizing members of that Approver Group to review (then approve or deny) Packages
related to those inventory areas.
Approver Type
Specifies kinds of Packages that an Approver Group can review. When Approver type is
Standard, that Approver Group can only review Standard Packages related to its authorized
inventory areas. When the Approver type is Emergency, that Approver Group can only
review Emergency Packages related to its authorized inventory areas.
Archive
Action used to write an Element and all related Endevor information to a sequential data set.
Authorization
Ability to perform certain privileged functions within IBM MVS Environment.
Automatic Consolidation
See consolidation.
not found
Automated Configuration Manager
Also referred to as ACM. Optional facility that allows you to monitor selected libraries and
data sets and maintain a Component List for each Element in monitored areas. The
Component List provides an audit trail of program-component information at the time of each
compile. ACM Component Lists are the foundation for:
 analyzing system behavior.
 propagating component changes to all affected programs.
 validating a system for consistent component use.
 recreating past versions of programs.
 moving related source components during promotion.
Backin
Restoring executable members of a Package to state they were in before Package was backed
out. Reverses backout process.
Backout
Returning executable members of a Package to state they were in prior to Package execution.
Base Level
Lowest level of an Element within a particular Stage. This level represents source for
Element in that Stage. If an Element exists in both Stages, there is a Base Level in each
Stage.
Base Library
PDS/E, PDS, CA-Panvalet, CA-Librarian or Endevor LIB (ELIB) file that stores Base
Members for Elements defined to Endevor. A Base Library is defined for each Element Type.
Base Member
Member in a Base Library. Each Base Member corresponds to an Element and contains the
source for the Base Level of that Element. Optionally, Base Member names can be Generated
internally by Endevor and do not correspond to Element name.
Base Regression
Amount (percent) by which statements stored in a new level of an Element change statements
stored in Base Level. See regression percent for more information.
Batch
IBM term referring to an Environment in which non-interactive programs are executed.
Within Endevor, we refer to actions submitted in batch (vs. foreground).
Browse
To view contents of a data set, without being able to change its contents.
Casting a Package
“Freezing” the actions included in a Package. A Package cannot be edited after it is cast.
CCID
See Change Control ID.
CCID Validation
Checking a CCID specified on an action against CCIDs defined in CCID definition data set.
Change Management
not found
Tracking changes to software components and their interrelationships over time. Includes
Configuration Management, Library Management, software distribution and version control.
not found
Change Control ID
Logical grouping mechanism by which user-specified portions of Endevor inventory can be
tagged, then viewed, tracked and manipulated. Use of CCIDs is optional, but may be required
on a system-by-system basis; the same is true of comments.
Change Regression
The amount (percent) by which statements stored in a new level, change the revision made by
previous level. See regression percent for more information.
Command Field
Field appearing in upper left corner (second line) of those Endevor screens on which you can
specify a TSO command. Any appropriate TSO command may be entered in the command
field.
Comment
1-40 character user-defined remark associated with an action, generally describing the reason
for the action. Used in conjunction with CCIDs. See the “Change Control ID” for more
information.
Committed
Status of a Package after it has been committed.
Committing a Package
Process of recording all events related to a given Package and removing all backin/backout
information. After a Package is committed, it can no longer be backed out/backed in.
Component
The output produced by a Generate or Move Processor. This term applies primarily to the
Endevor ACM product. The components of a Generated Element include:
 input components that were included to produce an output of Generate Processor; e.g.,
Copybooks would be considered an input component to a COBOL compiler Element
itself.
 all outputs created by the Generate or Move Processor, e.g., an object deck for a
COBOL compiler.
 processor that Generated or Moved Element Components are referenced by Element
names (including related Endevor location information) or member names.
Component List
A list of all components created by a Generate or Move Processor. The Component List can
be viewed using the PRINT action or through the Display Element/Component panel. This
panel is available only with the Endevor/ACM option.
The Component List provides an audit trail of program-component information at the time of
each compile. ACM Component Lists are the foundation for:
 analyzing System behavior.
 propagating component changes to all affected programs.
 validating a System for consistent component use.
 recreating past versions of programs.
 moving related source components during promotion.
Component Monitoring
Feature of ACM that allows you to check selected data sets for component relationships.
not found
Component Validation
When casting a Package, Endevor compares the Footprints on all Package components to
make sure they correspond to the current Footprints for those components.
Configuration Management
Capture and storage of program-component relationships and the tracking of these
relationships over time.
not found
Consolidation
Endevor facility that allows you to specify a number of Delta Levels to retain when a member
reaches maximum allowable level. If a level is not specified, Endevor automatically
consolidates levels.
Copy
Action used to copy an Element from an archive data set to a data set external to Endevor
Copyback
Act of searching for an Element along map, beginning at a designated Stage, finding the
Element, then copying Element back to initial Stage. Copyback is available as an explicit
option with the Generate action. Endevor also uses copyback when Adding, Transferring and
Moving Elements.
Create a Package
Building the SCL for a Package, then associating this SCL with other Package related
information such as a Package ID and execution window, etc.
Current Level
Most recent source for an Element. This source is identified by Element version number, followed by the
highest-level number assigned. The current level of an Element comprises Base Level plus all subsequent
change levels.
Data Set Validation
Optional capabilities of verifying that retrieved Elements are added/updated from the data set
to which they were last retrieved. This ensures that same copy of the Element (revised as
appropriate) is placed back in Endevor. Data set validation can be specified separately by
System. If this facility is in effect for a System, you can override it to add the Element back
from a different data set, provided you have the proper authority to do so.
Default
Default value is the value that Endevor assumes to be in a field or statement if a user does not
provide an alternative value. On foreground panels, fields are usually “primed” with default
values.
Defaults Table
See C1DEFLTS Table.
Delete
Action used to erase Base and Delta forms of an Element and remove Element information
from a Master Control File or a Component List.
Delete Processor
Processor that is run when an Element is deleted from a Stage. Typically, a Delete Processor
deletes output created by corresponding Generate Processor. See Processors for more
information.
Delta Level
Record of a change to Base Level of an Element. Each change to an Element creates a Delta
Level. Endevor compares the Base Level to the new source and builds a Delta Level
containing just changes to the source. Base Level plus all Delta Levels make up complete
Endevor source for an Element.
not found
Delta Library
PDS/E, PDS, CA-Panvalet, CA-Librarian or Endevor LIB (ELIB) file that stores Delta
Members for Elements defined to Endevor. A Delta Library is defined for each Element
Type.
Delta Member
Member in a Delta Library. Each Delta Member corresponds to an Element and contains all
levels for that Element subsequent to Base Level. Delta Member names are Generated
internally by Endevor and do not correspond to Element name.
Denied
Status of a Package when it has been reviewed, but denied, by an Approver.
Denying a Package
An option for a Package Approver. If one Approver denies a Package, it cannot be executed.
Display
Action used to view Environment definitions, Element information and Footprint-related data.
Element
Members or data sets that have been placed under control of Endevor. Default Element name
is member name. Actions are performed against Elements. Elements are identified by
Environment and Stage in which they are located and by System, Subsystem and Type in
which they are classified.
Element Changes
View of Element information that shows current level of an Element, annotated to indicate
level at which each line was added to source.
Element Component
In Endevor/ACM, that part of a Component List referred to as “Element information”. This
information includes Footprint of Endevor source.
Element History
View of Element information that shows all lines that have ever been present in a piece of
source code, annotated to show level at which line was added and/or deleted from source.
Element Master
View of Master Control File information about an Element.
Element Name
1-10 character name assigned to an Element, used to identify that Element within Endevor. It
is recommended that any output created by Output Management be assigned a name of the
corresponding Element. Element names must be unique within each System, Subsystem and
Type combination. An Element name can include any of the following characters (and only
these characters): A-Z, 0-9, @, # and $.
Element Summary of Levels
Summary view of activity against a piece of source code at all levels. Information provided
includes number of statements at each level, number of lines added and number of lines
deleted.
Emergency Approval
not found
The kind of approval given to Emergency Packages. An Approver Group must be given authority to approve
Emergency Packages. Emergency Package
One of two types of Packages. A Package is identified as Standard or Emergency when it is
created. Emergency Packages require approval from Approver Groups with an Approver
Type of Emergency.
Enable Backout
Option when creating a Package. You can decide whether or not to allow Packages to be backed out.
Endevor Classification
System, Subsystem and Type associated with an Element.
Endevor Listing Libraries
Used to store compiler listings produced by Processors.
Endevor Return Code
Return code issued by Endevor based on results of action processing: 00, 04, 08, 12 or 16.
Endevor return codes are described in Endevor Messages and Codes.
Endevor ESI
See External Security Interface facility.
Environment
The top level of logical structure used to classify Elements in Endevor. Each Environment has
two Stages. There is no limit to the number of Environments. The four defined
Environments and the two stages associated with each Environment are:
DVLP (Development)
UNIT (Stage 1 - Unit Test)
NTGN (Stage 2 - Integration Test)
QA (QA)
ASTG (Stage 1 – QA Staging)
ACPT (Stage 2 - Acceptance Test)
PROD (Production)
PSTG (Stage 1 – Production Staging)
PROD (Stage 2 - Production)
OBSL (Obsolete)
(Stage 1 – is not used)
ARCH(Stage 2 - Archive)
Executing a Package
Running a Package. Packages that execute successfully can be backed out or committed.
Execution Report
Report output when you run Endevor actions. Execution Report documents actions requested
and processing that took place.
not found
Execution Window
Start date/time and an end date/time within which a Package must be executed.
Export a Package
Copying Package SCL into an external data set.
External Approver/External Approver Group
An external approver group is an approver group that has no approvers defined to Endevor.
When Endevor encounters an external approver group, it queries the external security product
(CA-ACF2, CA-Top Secret, RACF) to determine if the user is a member of the approver
group.
External Security Interface
Optional interface used to implement external security at your site. If installed, this interface
replaces the native security facility supplied on installation tape (and implemented through the
security tables), with calls to RACF, CA-ACF2 or CA-Top Secret.
Fetch
See copyback.
Footprint
Encrypted data added by Processors to individual source, object or load modules, to identify
the Endevor Element associated with that module. Endevor uses this data to display or
otherwise process information related to the Element. A Footprint includes (in encrypted
format) the following information: site ID, Environment name, Stage number, System name,
Subsystem name, Element name, Element Type, Element version/level and date and time
Footprint was assigned.
Foreground
IBM term referring to an environment in which interactive programs are executed. You can
run actions in foreground by requesting those actions through Endevor Foreground Options
Menu.
Forward Delta
Method for recording changes that stores a Base version of code then builds current versions
by applying changes made to Base.
Forward Recovery
Process of taking an old level of an Element and making it current (new) level, thereby
backing out any changes made by levels between. To perform forward recovery, you first
retrieve older (to-be-recovered) level, then add or update Element using retrieved source to
create new level.
Generate
Action used to translate source into executables, then populate output libraries with these
executables by executing the Generate Processor for an Element.
Generate Processor
Generate Processors translate source into executables, and then populate output libraries with
these executables.
Group Name
not found
Within definition of Access and User Security Tables, a name associated with a particular
security configuration that applies for multiple users. The name is then associated with any
number of specific userids, to associate those IDs with the group-level security. This is a
convenient way to assign security to several users having identical levels of access to the
Endevor Environment.
Identify Record
An IBM term for a record in a load module that contains user-defined data. An IDR is created
by linkage editor when it encounters an IDENTIFY statement in object deck. Within
Endevor, IDRs are used to store Footprint(s) associated with load modules.
IDR
See identify record.
Image Library
The library that contains the current version of source code.
Import a Package
Creating a Package by copying SCL from an external data set.
Input Component
When using Endevor ACM components that were included to produce an output when
executing Generate or Move Processor. A Copybook, for example, is the input component
when compiling a COBOL program.
Inventory
The software at your site.
Inventory Analyzer
Endevor facility that allows you to analyze your software inventory, classifying it according
to Endevor Types. Used when implementing Endevor or when using Endevor to manage new
inventory.
Inventory Area
Subset of a software inventory, defined by its Endevor location (Environment and Stage) and
classification (System, Subsystem and Type).
Jump
To move an Element from one Stage to another on a map route, when a version of Element
exists at an intermediate Stage that is not part of map route.
Last Action
Most recent action executed for an Element. Once executed, each Type of action is recorded
as last action except ARCHIVE, LIST, PRINT and DISPLAY.
Last Action CCID
CCID specified for last action executed against an Element.
Level
Source for an Element at a particular time. When an Element is first added to a Stage there is
one level, known as the Base Level. Each time Endevor actions change source thereafter, a
new, Delta level is created.
Level Number
not found
Identifier for a specific level of an Element. Endevor assigns each set of a change, a level
number that is one higher than the number assigned to the preceding level.
Library Management
The classification, control and storage of the physical components of software inventory.
List
Action used to list, in the form of action requests, Elements from a MCF or archive data set or
members from a library. If the Automated Configuration Manager facility is installed, List
can also search a Component List based on specified criteria.
List Panel
A panel used by Endevor to display lists of Systems, Subsystems, Types, Elements or
members and are used to make selections. List panels are prepared and processed by ISPF
Table Display Facility.
Location
See Endevor location.
Map
Promotion routes established for software inventory at a site. Environments and Stages are
mapped to each other in C1DEFLTS table. Systems, Subsystems, Types and Processor
Groups are mapped to each other on their respective definition panels.
Mapping Rule
User-defined correspondence between host data set names and remote data set names.
Mapping rules are used when shipping Package outputs.
Master Control File
Endevor file that contains definitions of Stages, Systems, Subsystems, Element Types and
Elements. This file is accessed and updated by Endevor, to manage Element definitions, to
execute Processors and for other miscellaneous functions. There are two Master Control Files
(MCFs) for each Environment - one per Stage.
MCF
See Master Control File.
Move
Action used to move Elements between Stages, within or across Environments.
Move Processor
Move Processors copy outputs, Element information and Component Lists from source
location to the target location of a Move or, optionally, a Transfer action. See entry
“Processors” for more information.
not found
Name Mask
Asterisk (*) character, used as follows:
 to specify all names or all names beginning with a particular character string.
 when requesting Footprint reports, to request all members/CSECTs whose names
begin with a particular character string.
Notification Facility
Endevor facility that allows you to notify users of events that require a response from them.
Output Component
When using Endevor ACM, the components created as a result of executing Generate or
Move Processor. For example, an object deck is output component when compiling a
COBOL program.
Output Library
Any of several libraries used during Output Management, including
Endevor Processor listing library, Processor load library and source output library; as well as
user copy libraries, load libraries, listing libraries, macro libraries, JCL libraries, databases,
etc.
Output Management
That aspect of Endevor that deals with creation and maintenance of various outputs that relate
to an Element. The exact nature of these outputs varies depending on corresponding Element
Type and is defined by the Output Management for that Type. For example, Output
Management might store a copy of current source for Element in the Source Output Library or
it might create a load module for the Element or a listing associated with that load module.
Package
A group of Endevor actions that require approval before it can be executed. Creating a
Package allows you to:
 group specific actions so they can be maintained and tracked as a single unit.
 establish formal approval procedures to ensure data integrity through modifications.
 centralize specific action groups so you can see them across Environments and reuse them.
Package Data Set
Data set where Packages are stored. There is one Package data set per Environment.
Package Events
An audit trail recording “events” that have occurred involving a Package, logged by userid,
date and time. Package events relate to various steps of Package Processing procedure and
include:
Created Executed
Last Updated Backed Out
Cast Backed In
Approved Committed
Package Exits
Exits that are called before and/or after Package functions and sub functions.
Package Names
not found
The format for the Package Name is in Section Error: Reference source not found Error: Reference source not
found in Appendix Error: Reference source not found.
not found
Package Status
Indicates status of a Package at any given time. Status levels for Packages include the
following:
IN-EDITPackage is initially set to this status. It can be modified only when in this
status. When you reset a Package, its status is automatically set to IN-EDIT.
IN-APPROVAL
When a Package is cast, its status changes to IN-APPROVAL, indicating that the
Approvers can now review and approve or deny, Package. No editing can be done
once Package is cast.
DENIED
Status changes to DENIED when an Approver denies approval of Package during review
APPROVED
Status changes to APPROVED when all necessary Approvers (required and optional)
grant approval of Package during review and when the quorum requirement is met for
Package. A Package is also considered approved when it has been cast and no
Approvers have been identified.
IN-EXECUTION
Status changes to IN-EXECUTION when Package execution has begun.
EXECUTED
When Package has been executed successfully, its status changes to EXECUTED.
COMMITTED
When a Package has been committed, its status changes to committed.
Parallel Development Manager (PDM)
Automatically compares and integrates three versions of source code, allowing you to resolve
conflicts resulting from concurrent development or from applying vendor updates to
applications that have been customized in-house.
Partitioned Data Set
Data set in direct access storage that is divided into partitions, called members. Each member
can contain a program, part of a program or data.
PDM
See Parallel Development Manager.
PDS
See partitioned data set.
Print
Action used to print Element or member information.
PROC Statement
Job control statement used in cataloged or in stream procedures. PROC statements can be
used to assign default values to symbolic parameters contained in a procedure. It is also used
to mark beginning of in stream procedures.
not found
Processors
Processors are Standard OS JCL jobstreams that manipulate Elements and their outputs:
object modules, load modules, listings and the like. There are three Types of Processors:
 Generate Processors translate source to executables then populate output libraries with these outputs.
 Delete Processors delete Element and Component List information from Endevor.
 Move Processors copy outputs, Element information and Component Lists from source location to
target location of a move or, optionally, a transfer action.
Endevor supports both Endevor symbolics and user-defined symbolics in Processors. This
capability allows you to write one Processor that you can use in multiple Processor Groups by
changing values assigned to one or more symbolics.
Endevor also provides a set of utilities for use when writing Processors and supports use of instream data in
Processors.
Processor Component
When using Endevor ACM, the Processor Component of a Component List is the “Processor
information” part of Component List. This information includes the Footprint of the
Processor.
Processor Group
Processor Group allows you to associate one or more Processors with a given Type. This is
useful when Elements of one Type may require slightly different Processors. For example, a
site may have COBOL programs coded in batch COBOL and CICS COBOL. In this case, the
Processor Group capability of Endevor would allow you to create a single COBOL Type with
two Processor Groups, one to handle each variation of COBOL code. When you define a
Type to Endevor, you can also identify a default Processor Group for that Type. Using
symbolics when writing the Processors for the default Processor Group can allow you to use
the same Processors, by changing symbolic definitions, for other Processor Groups associated
with this Type.
Processor Group symbolics
Symbolics defined in PROC statements in one or more Processors in a Processor Group.
These symbolics and their default values appear on Processor Group Symbolics panel. By
modifying these default values, you can use one Processor in more than one Processor Group.
Processor Listing Library
Optional library that stores listings output from a CA-supplied Processor named GPPROCSS.
Processor Load Library
The Endevor library that contains a load-module form of each Processor. Modules from this
library are executed when Processors are invoked.
Processor Output Library
Library referred to in a Processor, to which that Processor writes output. Processor output
libraries can be source libraries, executable libraries or listing libraries.
Production Data Sets
Data sets used to store production code. This term is used in Package shipment utility to refer
to host and remote production data sets.
Promote
Move an Element from one inventory area to another inventory area.
not found
Quorum (quorum size)
The minimum number of Approvers required to execute a Package. When a quorum size is
indicated, that number of Approvers must review and approve a Package.
not found
Regression
Term that refers to condition where one set of changes to Element source is overwritten by a
subsequent set of changes. Endevor flags regression when changes stored for a specific level
of an Element overwrite more than a predefined percentage of Element statements. See
regression percent.
Regression Percent
Percent of acceptable change to Element source, defined for each Element Type. This is a
percentage that, if exceeded, results in a caution (level 8) Endevor return code. Each time a
new level is created for an Element, Endevor checks changes stored in that level against this
percent, both in terms of change to statements stored for the Base Level (known as Base
regression) and change to statements stored for the previous level (known as change
regression). If the amount of change in either case exceeds defined percent, Endevor issues a
warning.
Reload
Reload utility allows you to recover an Endevor VSAM control file (Master Control File,
Package data set) or a base/Delta data set that was lost as a result of a physical device failure
or site disaster. Reload action restores data from data sets created by unload process.
Remote Footprint Synchronization
Procedure whereby Footprinted executables are shipped from a remote to a host site, where
Footprint reports are run to compare executable Footprints with host Master Control File
information.
Request Data Set
Data set that contains action requests to be submitted for batch processing. You create
request data sets in foreground, using SCL Generation facility.
Request for Data
Package exit capability, allowing Package exit programs to make multiple, successive
requests for Endevor information on a single invocation of the exit.
Reset a Package
Erase all Package event records, returning the Package to an in-edit status
Resource Security Table
Endevor table defining those Element names that are restricted to particular
System(s)/Subsystem(s), within a specific Environment. Resource Security Table is defined
by Endevor Administrator, using the CONSDEF macro. There can be one Resource Security
Table for each Environment.
Restore
Action used to restore an Element to Endevor from an archive data set.
Retrieve
Action used to copy any level of an Element to an external data set.
Return code
See Endevor return code.
Reverse Delta
not found
A method for recording changes that stores the most recent version of code, rebuilding prior
versions by backing out individual changes from current version.
Review a Package
Review the contents of a Package. After reviewing a Package an Approver either approves or denies.
Route
A series of Environment/Stage locations that make up the Stages in a Software Life Cycle.
Taken together, all routes at a site comprise a map for that site.
not found
SCL
See Software Control Language.
Security
Endevor feature that allows you to restrict action requests and access to Elements. The
security System supplied with Endevor, known as native security, is implemented using three
tables. See entries “Access Security Table”, “Resource Security Table” and “User
Security Table”.
SETUP function
Function invoked at Endevor initialization to build a table of Package exits to be invoked
during a session.
Sharable
Characteristic of a Package. A sharable Package can be edited by people who did not create
the Package.
Ship utility
Endevor utility that allows you to ship Package outputs to remote sites.
Signin
Action used to remove the current sign-out for an Element. You might signin an Element
after you retrieve it, and then find you do not intend to return it to Endevor.
Signout
Assignment of a user ID to an Element, establishing “ownership” of that Element. Signout is
automatic when retrieving Elements from or adding/updating Elements in Endevor.
Site
Location at which Endevor is installed. Site is defined in Defaults Table, where it is assigned a site ID.
Software Control Language
Endevor language used in batch to maintain or otherwise act against Elements within Endevor.
Software Distribution
Automated distribution and synchronization of software changes and tracking of
implementation of those changes.
Software Life Cycle
Stages through which software passes at a site. A Software Life Cycle might consist of
development, testing, quality assurance and production.
Source
Non-executable form of an Element.
Source library
Any of several libraries used during Source Management, including Endevor Base libraries,
Delta libraries and INCLUDE libraries.
Source Management
Aspect of Endevor that deals with creation and maintenance of Element source. Element source is maintained in
an internal format, in Base and Delta libraries.
Source Output Library
not found
Endevor library that contains latest full source version of each Element. This library is
designed for use with Copybooks, macros, procedures, etc., that are copied elsewhere. This
library is optional, but if used, is specified in definition of corresponding Element Type.
Stage
Stage in Software Life Cycle. There are two Stages defined for each Environment. See Environment entry in
Glossary for Stage definitions and names.
not found
Staging Data Sets
Temporary data sets used by shipment utility to store Package outputs before transmitting
them. Shipment utility creates staging data sets at both the host and remote site.
Standard Approval
One of two Types of Package approval. Standard Packages can only be approved by
Approver Groups designated as Standard.
Standard Package
One of two Types of Package. A Package is identified as Standard or as Emergency when it
is created. Standard Packages require approval from Approver Groups with an Approver
Type of Standard.
Subsystem
Part of Endevor classification of an Element. Subsystems are used for specific applications
within a System. For example, there might be a purchase order and accounts payable
Subsystems within the financial System.
Symbolics
Endevor supports two kinds of symbolics in Processors:
Endevor symbolics. Any of several names, preceded by &C1, that are used within Endevor
Processors to represent a value specific to an individual run of Processor. Values are assigned
to Endevor symbolics when Processor is executed.
User symbolics. Defined by users in JCL PROC statements in Processors. Allow one
Processor to be used in multiple Processor Groups. See Processors and Processor Groups.
Synchronize
When Base Level of an Element at a source location differs from current level at the target
location, Endevor does not allow the Element to be transferred or Moved unless you specify
sync=Y. This option tells Endevor to create a “sync level” at the target that reflects
differences. All levels (the change history) associated with the “from” location Element are
then appended to the location Element and renumbered.
System
A means of classifying Elements within Endevor. A System typically represents the
applications at a site. For example, there might be financial and manufacturing applications.
A System must be defined to each Environment where it will be used.
Transfer
Action used to transport Elements from a source location to a target location. Each location
can be either an Endevor location or an archive data set.
Type
Category of source code used as part of classification of an Element in
Endevor. For example, there might be the following Types: COBOL (for COBOL code),
Copybook (for Copybooks) and JCL (for JCL streams).
Type Processing Sequence
Relative sequence of processing for Element Types defined to each System. By defining
sequence of processing in this way, you could ensure, for example, that Copybooks (Type
not found
Copybook) are updated before any COBOL programs (Type COB) that might use those
Copybooks.
Update
Action used to add a member to Endevor when an Element with the same name is located in
the target Stage 1.
Userid
For actions run in foreground, TSO userid for the session. For actions run in batch, job name
or ID specified through the USER= parameter on job card, depending on how your Defaults
Table is set up.
not found
User Menu Facility
User menu facility allows the Endevor administrator to attach user-defined functions to
Endevor TSO/ISPF front end.
User Security Table
Endevor table that defines the Systems and Subsystems to which each user has access and for
each System/Subsystem, the Type of processing (authorization level) allowed. There is one
User Security Table for each Environment.
User Symbolics
See symbolics.
Validate
The VALIDATE function allows you to ensure integrity of one or more existing Endevor
Environments and/or Systems and their related Elements and components. These are the
same checks performed as part of UNLOAD processing, allowing this function to operate in a
standalone mode.
Version
Number used together with level number, to identify Element source. Each new version
creates a new Base Level for an Element.
Version Control
Maintenance, tracking and auditing of modifications to an application over time, allowing
prior development versions to be restored.
Version Number
Identifier for the version assigned to an Element.
VV.LL
Identifier that refers to a particular version (vv) and level (ll) of an Element source.
Wildcard
See name mask.

Endevor User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Endevor User Guide

Uploaded by

Copyright:

Available Formats

Spiegel Endevor Developers User Guide

Spiegel Endevor Developers User Guide

Revision History Table

Last Saved Date: 7/16/2007 09:49:00 AM ii

Areas still in work or being researched

Last Saved Date: 7/16/2007 09:49:00 AM iii

Last Saved Date: 7/16/2007 09:49:00 AM iv

Last Saved Date: 7/16/2007 09:49:00 AM v

Last Saved Date: 7/16/2007 09:49:00 AM v

Last Saved Date: 7/16/2007 09:49:00 AM vi

Last Saved Date: 7/16/2007 09:49:00 AM vii

Last Saved Date: 7/16/2007 09:49:00 AM viii

Last Saved Date: 7/16/2007 09:49:00 AM ix

To Be Defined (TBD) / To Be Resolved (TBR) List

TBD / TBR No. Paragraph Description

Last Saved Date: 7/16/2007 09:49:00 AM x

2. When and who should use this User Guide?

Last Saved Date: 7/16/2007 09:49:00 AM 1

3. How do I use this document?

Last Saved Date: 7/16/2007 09:49:00 AM 2

2. Endevor Documentation from Computer Associates

 CA Endevor for MVS Quick-Edit

Menu ISPF-Util Compilers Options Status Help

0 Settings Terminal and user parameters

I Index Roadmap of Old Panels to New Panels

Enter X to Terminate using log/list defaults

Figure 2-1: ISPF Primary Option Menu Panel

Last Saved Date: 7/16/2007 09:49:00 AM 3

Last Saved Date: 7/16/2007 09:49:00 AM 4

The following steps should be used in creating a change to a production application:

Last Saved Date: 7/16/2007 09:49:00 AM 5

Last Saved Date: 7/16/2007 09:49:00 AM 6

DEVELOP QA PROD OBSOLETE

(NT) (AS) (AC) (PS) (PR) (AR)

Figure 3-2: Endevor Development Life Cycle

ENVIRONMENT name is in the box above each stage.

Last Saved Date: 7/16/2007 09:49:00 AM 7

1. A temporary fix only and is not to be elevated to production.

Last Saved Date: 7/16/2007 09:49:00 AM 8

The configuration for the CRISIS Life Cycle is shown

ETST EMER PSTG PROD

Figure 3-3: The Crisis Life Cycle

Last Saved Date: 7/16/2007 09:49:00 AM 9

 Edit the object with the ISPF editor.

Last Saved Date: 7/16/2007 09:49:00 AM 10

Last Saved Date: 7/16/2007 09:49:00 AM 11

---------------------------- Endevor Quick-Edit -------------------------------

ENDEVOR Location: List Options:

Figure 3-4: Endevor Quick-Edit Panel - Options

4. When to use Quick-Edit and when to use Endevor

1. When to use Quick-Edit

2. When to use Full Panel Endevor Batch

Last Saved Date: 7/16/2007 09:49:00 AM 12

Select an environment to continue. Enter the END command to exit.

Figure 3-5: Endevor Full Panel Environment Selection Menu

Last Saved Date: 7/16/2007 09:49:00 AM 13

1. Editing an Element in the UNIT Stage

File Edit Edit_Settings Menu Utilities Compilers Test Help

Figure 4-6: Endevor Main Menu Panel

---------------------- ENDEVOR REL39 SELECTION MENU ------------------------

E - ENDEVOR - Endevor Software Management Functions

S - SIGNOUTS - Show my signouts

ENTER END COMMAND TO TERMINATE ISPF.

Figure 4-7: Endevor Main Menu Panel