Package Development using ENDEVOR

Create a Package

 Creation of a package involves Identification of the elements that need to be included in the package and identifying the set of actions to be performed on each of these elements. Each package is identified by a package ID. Endevor also provides a facility to copy an existing package to a new package.

Casting a Package

             Casting a package is the step that prepares the package for approval by a defined approver. It verifies the integrity of the components in the package and also makes sure that the proper and recent most versions are included in the package. A package cannot be modified after it has been cast.

Approval of a Package

Each package is defined with a set of approvers who could approve the package after verifying the integrity of the package.

           

Execute

            Execution of a package involves submitting a batch job that would execute the instructions that are available in the package. All the actions specified on the elements in the package would be performed at this stage.

Endevor Functions

Version maintenance

This function of Endevor helps you to Track your changes against production, creating an online change history, enabling you to know what was changed, by whom, when, and why.

Tracking Changes between Various Versions

Endevor also keeps track of changes to an element made in different versions of the element as compared to the baseline.

Compiling and maintaining footprints

This helps you in the process of automating executables creation. It also ensures that Ensure that the source, executable, and any other form (for example, listings) of an element correspond. It helps you to apply the same procedures (including automating compiles, impact analyses, and standards checking functions) to any component type by using processor groups (Discussed in a separate section called processor groups).

Maintaining Delivery Packages                      

Put change packages and approvals online, eliminating paperwork. This helps you make a list of elements to be delivered and consolidate them to a single package. It also has facilities to approve the package by a defined approver and execute the package.

Source Locking / Releasing – Check in / Check out

                       These functions are to Prevent conflicting changes to the same system component. Please see SIGNIN / SIGNOUT under APPENDIX I to learn more about signin-signout functions.

 Reports

Endevor gives good reporting facilities about the inventories, signin-signout reports etc to analyze the status of the inventory at any point of time.

Genneral Operations of ENDEVOR

RETRIEVE    - also signs element out to retriever (refer to section V for more                               detail)

ADD/UPDATE          - executes generate processor for program, creates obj and/or dbrm

  and/or load module (refer to section V for more detail); simply adds

  element if generate processor is *NOPROC*

  *NOPROC* = PROCS, UTLS, BINDDECKS, COPYBOOKS, AND MFS

  (NOPROC doesn’t mean no processing.  It means that it’s added to

  Stage U datasets without any action taking place on the element,

  it’s an “as is” move…

GENERATE   - executes generate processor for:

                          Type = Telon, then a compile will take place or

                          Type = Cobol, then a compile and possibly a link will take place

                          Type = Linkcard, then a link will take place

                        - Create either an obj, obj & load module, or just a load module

                        (refer to sections VI and VII for more detail)

********        - VERIFY STAGE U LIBRARIES

MOVE                        - executes move and delete processors

                        - copies from Stage U to Stage C libraries

                        - deletes from Stage U; signs element back in to Stage C

                        (refer to section V.7 for more detail)

EXTERNAL TO ENDEVOR - copy jobs execute to copy dbrms and load modules to production libraries; bind job executes; deletes from Stage C libraries.

Endevor actions

RETRIEVE    - execute in foreground to retrieve element(s) from Stage 2 to your                          external PDS.

ADD/UPDATE          - execute in batch to add element to Stage U or update it if it is                               already in Stage U.

GENERATE   - generate always executes when you add (or update) a program to Stage                            U; you also explicitly use generate when relinking.

MOVE                        - you must use the functions in a package to get an element and its                                      associated outputs (objs, dbrms, loads) to Stage C.

DELETE         - you may use delete to remove an element from Stage U or C.

SIGNIN          - if you have inadvertently signed a member out, you must use a package                            and specify override signout=Y to sign it back in to Stage C.

IBM

IBM has been present in India since 1992. IBM India's solutions and services span all major industries including financial services, healthcare, government, automotive, telecommunications and education, among others. As a trusted partner with wide-ranging service capabilities, IBM helps clients transform and succeed in challenging circumstances. IBM has been expanding its footprint in India - and has a presence in over 200 cities and towns across the country - either directly or through its strong business partner network. IBM India has clearly established itself as one of the leaders in the Indian Information Technology (IT) Industry - and continues to transform itself to align with global markets and geographies to grow this leadership position. Widely recognised as an employer of choice, IBM holds numerous awards for its industry-leading employment practices and policies. The diversity and breadth of the entire IBM portfolio of research, consulting, solutions, services, systems and software, uniquely distinguishes IBM India from other companies in the industry. To know more about business units at IBM India, click on the “About Us” link above.

Designation	IT Specialist - Mainframe - ITD - GD
Job Description	Looking for IT Specialist - Mainframe - ITD - GD
Desired Profile	1 ACF2" Mainframe User ID management 2 Mainframe RACF & ACF2 User ID management admin skills. 3. Min 1 to 4 years of years in relevant skills. 4 Ready for 24/7 Rotational shifts. working for US Customers 5 Very Good communication skills. . * Minimum 1 to 4 years of relevant experience required Required: Bachelor's Degree English: Fluent
Experience	1 - 4 Years
Industry Type	IT-Software/ Software Services
Role	Software Developer
Functional Area	Mainframe
Education	UG - Any Graduate PG - Any PG Course
Location	Bengaluru/Bangalore
Keywords	IT Specialist Mainframe, User ID Management, Mainframe User Administrator
Contact	HR IBM India Pvt Limited

ENDEVOR Inventory Structure

 Inventory Structure Consist of System, Subsystem, Type, and Element           

  

SYSTEM - System is defined here at Pershing as a type of process.  There are

                    9 different processes; therefore there are 9 systems as indicated:

 CIM             - Customer Information Management                       

 CPS              - Customer processing systems

 CTDS           - Customer Trading System

 CSQ             - Customer Service Quality

 FSQ              - Financial Service Quality

 ENT             - Enterprise

 GC               - General Counsel

 IIC               -  Institutional International Customer

 NC               -  National Customer

SUBSYSTEM - A specific application within a system.  A subsystem is

                           defined to a system in which it is used.

  Examples:  TOPS; BOES; MAXX;  PDGM; PACE           

  

TYPE - categories of source code.  Every type is defined to each stage. 

                       

            Examples of  Types

 TYPE                         TYPE DESCRIPTION                                  

             DCLGEN                   DCLGEN                                            

            COPYBOOK             COPYBOOK                                          

            MACRO                      MACRO                                              

MAP                          BMS/GT

            ASMBAT                   ASSEMBLER BATCH                                   

            ASMONL                   ASSEMBLER CICS                                    

            COBBAT                    COBOLI & II BATCH PROGRAMS                        

COBONL                   COBOLI & II ONLINE PROGRAMS                       

            COBBATDB              COBOLI & II - BATCH - ADAMINTS & DB2              

COBONLDB             COBOLI & II - CICS  -  DB2                        

ELEMENT - is the name of the member.  Each element is classified by

System, Subsystem, and Type.

STAGE   -  The stage where the element is located

ENDEVOR Library Structure

ENDEVOR Library Structure consist of  the following types of libraries:

  

Master Control File  - There is one Master Control File (MCF) library for each

Libraries                        stage.  This file stores system, subsystem, type definitions,

                                      the names of the elements currently in that stage, and other

  information.

  

 Package Data Set   -  There is one package data set for the entire system.  This

                                     This file stores all packages the packages that were created

 and related information .

  

 Base and Delta       - There is one set of base and delta libraries associated with each

 Libraries                     type definition.  Every stage has the same type definitions.

                                     Base libraries stores the element source when it is first added

 to Endevor.  Delta libraries store the changes made to the

 source.

  

Output Libraries          These are 'Load' libraries; output generated from the compila-

                                    tion of programs.  There is one load library for each stage.

         

Listing Libraries          These are 'LIST' libraries; listings generated from the compila

                                    tion of programs.  There is one list library for each system; a total of 9 List libraries. 

                                    Each library is defined for each stage. 

ENDEVOR Logical Structure

 Endevor provides a consistent and flexible structure for

classifying software inventory as described below:

Environment - There are three environments defined here at Pershing.

TEST:            Used to promote  ‘forms’            

            DEV:              Used for all element types; with the exception of ‘Forms’

                                    and  standalone  ‘Copybooks’

PROD:           Used for production and Quick-Fix  Execution

             

Stages - There are two stages in each environment - each stage consist of its own

Master Control File (MCF).

CURRENT ENV ===> TEST                      

STAGE 1 INFORMATION:                       

ID:                 T                    

            Name:            TEST                

            Title:              TEST                

            MCF data set name:  ENDEVOR.TEST.MCF    

                                           

STAGE 2 INFORMATION:                       

            ID:                 U                   

            Name:            UAT                 

            Title:              QA/USER ACCEPTANCE  

            MCF data set name:  ENDEVOR.UAT.MCF

CURRENT ENV ===> DEV                        

STAGE 1 INFORMATION:                        

            ID:                  1                    

             Name:            DEV1                 

            Title:              DEVELOPMENT STAGE 1  

            MCF data set name:  ENDEVOR.DEV1.MCF     

                                            

STAGE 2 INFORMATION:                         

            ID:                  2                    

            Name:            DEV2                 

            Title:              DEVELOPMENT STAGE 2  

            MCF data set name:  ENDEVOR.DEV2.MCF 

   

  CURRENT ENV ===> PROD                       

                                              

 STAGE 1 INFORMATION:                        

            ID:                 F                    

            Name:            QF                   

            Title:              QUICK FIX - EMERGENCY

            MCF data set name:  ENDEVOR.QF.MCF       

                                             

            STAGE 2 INFORMATION:                        

            ID:                 P                    

            Name:            PROD                 

            Title:              PRODUCTION           

            MCF data set name:  ENDEVOR.PROD.MCF

   

Mainframe Openings

Experience required for the Job: 2 - 5 years

Job Location: Chennai, Hyderabad

CSC has currently recruiting for Mainframe positions based at Chennai/Hyderabad. 

Job description: 

2 to 5 years of hands on experience in Cobol, JCL, CICS, VSAM and DB2. 

Experience with formal SDLC methodology
Good analytical and communication skills
PL1 experience will be added advantage

Job Location: Chennai/Hyderabad

If interested in this opportunity, kindly send your updated resume along with the below (mandatory) details.

Available date & time for personal interview in CSC Chennai office? (20th Dec - 24th Dec)
Current CTC
Expectation
Notice period

If you are not actively seeking an opportunity, please refer this mail to your friends/colleagues who may be interested in this opportunity.

Thanks & regards,

Ramalingam.
Human Resources - Recruitment.
Unit 2, HRD, SDF Buildings, MEPZ, Tambaram, Chennai 600 045.
Email: rramasubram3@csc.com | Tel: +91 - 44 - 22628080 | Extn - 734722

BENEFITS OF ENDEVOR

. Automatically compares and tracks your changes against production;

   enables you to know what was changed, by whom, and why.

            . Prevent conflicting changes to the same system

              component.

.  Automate the creation of executables.

            . Ensures that the source, executables and listings

              of an element corresponds.

            . creation of executables (loads) is automated.

. Packaging allows multiply elements to be implemented into production

   simultaneously.

           

. Online approvals eliminates change-related paperwork.

.  Ability to view or retrieve prior levels of any element.

.  Report on element definition,content, and change history.

WHAT IS ENDEVOR?

ENDEVOR is an automated software management system that integrates the

software development life cycle and the software management life cycle

within the MVS environment.

INTERPRETATION  - Endevor is an integrated set of management tools

used to automate, control, and monitor your applications development process.

ENDEVOR is implemented and run under MVS, within the TSO ISPF environment and in batch.

ENDEVOR is a  product of Computer Associate - CA

Closing VSAM Files

   Use the CLOSE statement to disconnect your program from the VSAM file.  If

   you try to close a file that is already closed, you will get a logic

   error.  You should check the file status key after each CLOSE statement.

   In the event that you do not close a VSAM file, COBOL will automatically

   close the file for you, giving you a warning-level diagnostic message.

   See "Automatic Closing of Files"  details. 

Deleting Records from a VSAM File

   Open the file for I-O and use the DELETE statement to remove an existing

   record on an indexed or relative file.  You cannot use DELETE on a

   sequential file.

   When ACCESS IS SEQUENTIAL, or if the file contains spanned records, the

   record to be deleted must first be read by the COBOL program.  The DELETE

   then removes the record that was read.  If the DELETE is not preceded by a

   successful READ, the deletion is not done and the status key value is set

   to 92.

   When ACCESS IS RANDOM or ACCESS IS DYNAMIC, and if the records are not

   spanned, the record to be deleted need not be read by the COBOL program.

   To delete a record, the key of the record to be deleted is moved to the

   RECORD KEY data item and the DELETE is issued.  You should check the file

   status key after each DELETE statement. 

Replacing Records in a VSAM File

   To replace records in a VSAM file, use REWRITE in a file that you have

   opened for I-O.  If you attempt to use REWRITE on a file that is not

   opened I-O, the record is not rewritten and the status key is set to 49.

   You should check the file status key after each REWRITE statement.

   °   For files accessed sequentially, you must read the record before you

       issue the REWRITE statement.

   °   For sequential files, the length of the record you rewrite must be the

       same as the length of the original record.

   °   For indexed files, you can change the length of the record you

       rewrite.

   °   For variable-length relative files, you can change the length of the

       record you rewrite.

   To replace records randomly or dynamically, the record to be rewritten

   need not be read by the COBOL program.  Instead, to position the record

   you want to update:

   °   For indexed files, move the record key to the RECORD KEY data item,

       and then issue the REWRITE.

   °   For relative files, move the relative record number to the RELATIVE

       KEY data item, and then issue the REWRITE.

Adding Records to a File

  The COBOL WRITE statement adds a record to a file, without replacing any

   existing records.  The record to be added must not be larger than the

   maximum record size specified when the file was defined.  You should check

   the file status key after each WRITE statement.

     1 Adding Records Sequentially

     2 Adding Records Randomly or Dynamically

             

    1 Adding Records Sequentially

   Use ACCESS IS SEQUENTIAL and code the WRITE statement to add records

   sequentially to the end of a VSAM file that has been opened with either

   OUTPUT or EXTEND. 

   Sequential files are always written sequentially.

  

   For indexed files, new records must be written in ascending key sequence.

   If the file is opened EXTEND, the record keys of the records to be added

   must be higher than the highest primary record key on the file when the

   file was opened.

   For relative files, the records must be in sequence.  If you include a

   RELATIVE KEY data-item in the SELECT clause, the relative record number of

   the record just written is placed in that data item.

           

   2 Adding Records Randomly or Dynamically

   When you write records to an indexed data set and ACCESS IS RANDOM or

  ACCESS IS DYNAMIC, the records can be written in any order. 

Updating Records in a VSAM File

   The COBOL language statements that can be used to update a VSAM file in

   the Environment and Data Divisions are the same.

   Figure shows the statements that you can use in the Procedure Division

   to update VSAM files.

     ________________________________________________________________  

     | Figure 73. Procedure Division Statements Used to Update VSAM Files     |

   |_______________________ ________________________ _______________________|

   | ESDS                  | KSDS                   | RRDS                  |

   |_______________________|________________________|_______________________|

   | ACCESS IS SEQUENTIAL: | ACCESS IS SEQUENTIAL:  | ACCESS IS SEQUENTIAL: |

   |     OPEN EXTEND       |     OPEN EXTEND        |     OPEN EXTEND       |

   |     WRITE             |     WRITE              |     WRITE             |

   |     CLOSE             |     CLOSE              |     CLOSE             |

   |         or            |         or             |         or            |

   |     OPEN  I-O         |     OPEN  I-O          |     OPEN  I-O         |

   |     READ              |     READ               |     READ              |

   |     REWRITE           |     REWRITE            |     REWRITE           |

   |     CLOSE             |     DELETE             |     DELETE            |

   |                       |     CLOSE              |     CLOSE             |

   |_______________________|________________________|_______________________|

   | ACCESS IS RANDOM:     | ACCESS IS RANDOM:      | ACCESS IS RANDOM:     |

   |                       |     OPEN  I-O          |     OPEN  I-O         |

   |                       |     READ               |     READ              |

   |     not applicable    |     WRITE              |     WRITE             |

   |                       |     REWRITE            |     REWRITE           |

   |                       |     DELETE             |     DELETE            |

   |                       |     CLOSE              |     CLOSE             |

   |_______________________|________________________|_______________________|

   | ACCESS IS DYNAMIC     | ACCESS IS DYNAMIC      | ACCESS IS DYNAMIC     |

   | Sequential Processing:| Sequential Processing: | Sequential Processing:|

   |                       |     OPEN  I-O          |     OPEN  I-O         |

   |                       |     READ NEXT          |     READ NEXT         |

   |     not applicable    |     WRITE              |     WRITE             |

   |                       |     REWRITE            |     REWRITE           |

   |                       |     START              |     START             |

   |                       |     DELETE             |     DELETE            |

   |                       |     CLOSE              |     CLOSE             |

   |_______________________|________________________|_______________________|

   | ACCESS IS DYNAMIC     | ACCESS IS DYNAMIC      | ACCESS IS DYNAMIC     |

   | Random Processing:    | Random Processing:     | Random Processing:    |

   |                       |     OPEN  I-O          |     OPEN  I-O         |

   |                       |     READ               |     READ              |

   |     not applicable    |     WRITE              |     WRITE             |

   |                       |     REWRITE            |     REWRITE           |

   |                       |     DELETE             |     DELETE            |

   |                       |     CLOSE              |     CLOSE             |

   |_______________________|________________________|_______________________|