Infosys Technologies Ltd.

Endevor Package

Date : 09th June, 2000

Prepared By : Manish Nema
Reviewed By :

Version 0.0 a

BoK on Endevor Package Ver 0.00a Page 1 of 15

Infosys Technologies Ltd.

Modification Log

Ver. Date Author Reviewed by Description of Changes

0.0a 06/09/2000 Manish Nema Initial version

BoK on Endevor Package Ver 0.00a Page 2 of 15

Infosys Technologies Ltd.

Table of contents

ENDEVOR/MVS ENVIRONMENTAL DESIGN......................................................................................................................................................................4

PACKAGE:................................................................................................................................................................................................................................ 4
Things to do before creating the package:....................................................................................................................................................................... 4
Creating the package:......................................................................................................................................................................................................... 5
Casting the package:.......................................................................................................................................................................................................... 7
Reviewing/Approving the package:................................................................................................................................................................................. 10
Execution of package:....................................................................................................................................................................................................... 11
Committing packages....................................................................................................................................................................................................... 13
Package Backout.............................................................................................................................................................................................................. 13
Package Shipment:........................................................................................................................................................................................................... 14
Package action/status summary..................................................................................................................................................................................... 15

BoK on Endevor Package Ver 0.00a Page 3 of 15

Infosys Technologies Ltd.

ENDEVOR/MVS Environmental Design

Package:

A package is a set of members or elements on which you can perform similar ENDEVOR actions, that may require approval before
being executed. You can create a package by building batch SCL streams containing the actions to be executed.

Go to option Endevor; 4 ;4 from the ISPF panel, Following screen will appear.

Things to do before creating the package:

Go to option 1 for displaying the package information and enter the package name, this is just to make sure that the package you
are going to create does not exist.

BoK on Endevor Package Ver 0.00a Page 4 of 15

Infosys Technologies Ltd.

Creating the package:

Creating a package involves:

Identifying the elements to be included in the package.

Building a file of actions to be performed against the elements.
Identifying the package as standard or emergency.
Specifying dates between which the package must be executed.

You can also create a package by copying an existing package. For this use option C for Copying the package and enter the input
package id.
BoK on Endevor Package Ver 0.00a Page 5 of 15
Infosys Technologies Ltd.

After creating the package, the status changes to In-Edit. You can modify a package as long as it has a status of In-Edit.

Go to option 2. Create or Modify the Package and give the Package name.

Go for option B (Build Package Action).

BoK on Endevor Package Ver 0.00a Page 6 of 15

Infosys Technologies Ltd.

The following Screen will appear:

Select option 5, for moving element from one staging library to another. This is same as using Endevor batch submission option.

Casting the package:

Casting a package prepares the package for review and subsequent execution. When you cast a package, ENDEVOR:

Determines whether approvers have been assigned to the inventory area(s) included in the package.
Makes sure that any approvers have authority to perform the package actions against the package inventory areas.
Checks the integrity of the package components.
Makes sure that the package contains the most recent versions of all components.

A package cannot be edited once it is cast.

Go to option 3 for Casting the package and press Enter. Following screen will appear,
BoK on Endevor Package Ver 0.00a Page 7 of 15
Infosys Technologies Ltd.

Put the option as C and press Enter.

Message will be displayed on the screen on successful casting else browse the output error messages.

1. Determining approvers

The first step in casting a package is to determine if approvers are associated with the inventory areas referenced in the package.

Action Inventory Area

Add/Update Target
Restore Target
Generate:
With COPYBACK Target
Without COPYBACK Source
Move Target
Delete Source

BoK on Endevor Package Ver 0.00a Page 8 of 15

Infosys Technologies Ltd.

Signin Source
Transfer:
With DELETE Source and Target
Without DELETE Target
Archive:
With DELETE Source

2. Component validation

If component validation is active, ENDEVOR examines the component list associated with each element specified in a Move action.
ENDEVOR does not allow a package to be cast if any components

Reside at the same stage as the source of the Move action and have not been included in the package. In this case,
ENDEVOR appends commented Move SCL for the omitted input component.
Are missing or have been modified (the time stamp in the component list footprint does not correspond to either the Generate or
Move time stamp in the MCF) since the element was generated. ENDEVOR issues error messages about this condition.

When a cast fails for either of these reasons, review the package and do one of the following:
Generate the element to pick up the latest version of a component.
Cast the package without validation (if allowed).
Cancel the package if a component has been deleted.

3. Security checking

The ENDEVOR C1DEFLTS Table contains a flag *PKGCSEC* that indicates whether action should be checked at package cast
time, to determine whether the person casting the package as the authority to perform all actions contained in that package.

If PKGCSEC=Y, ENDEVOR checks each action in the package. If the person is not authorized to perform all actions, he/she cannot
cast the package. If PKGCSEC=N, ENDEVOR does not check action security.

4. Integrity checking

After the package is cast, it contains either a copy of the footprint of the source element or a checksum value for source members
from an external data set.

BoK on Endevor Package Ver 0.00a Page 9 of 15

Infosys Technologies Ltd.

Before executing the package, ENDEVOR compares this footprint or checksum value with the values stored in the package. If any
differences exist at that time, the package is not executed.

Reviewing/Approving the package:

A package must be reviewed if one or more approver groups are associated with the inventory area(s) included in the package.
Once a package is in the review phase, only designated approvers can access the package and review its contents.

To be approved, a package must:

Receive approval from at least the required approvers.

Receive approval from a quorum of approvers.
Not be denied approval by any approvers

Example:
The approver group PKGQA consists of three approvers. The approver group was established with a quorum size of 2, with one
approver required. This means that in addition to the required
approver, one of the two remaining members of the approver group must approve the package in order for it to be executed.

Go to option 4, for approving the package. The following screen will appear , put A for approving the package.

BoK on Endevor Package Ver 0.00a Page 10 of 15

Infosys Technologies Ltd.

The status will change from In-approval to Approved.

Execution of package:
The package can be either executed online or submitted in batch. The user performing the execution must be an approver and
must have the authority to perform the actions contained in the package.

The outputs of packages that have been executed can be backed out, backed in, or shipped to remote locations.

Go to option 5 for executing the package.

Submit the package using option S

BoK on Endevor Package Ver 0.00a Page 11 of 15

Infosys Technologies Ltd.

Again Press S for submitting a batch job.

The jobcard should have the Job Parm as displayed in the screen below.

BoK on Endevor Package Ver 0.00a Page 12 of 15

Infosys Technologies Ltd.

Committing packages

Package processing provides you with the ability to backout and subsequently backing, change packages. The backout/ backin
option is available only after you have executed a package. All package event information, as well as backout/backin data, is
maintained with the package until you commit the package.

Committing a package removes any backout/backin data while retaining package event information. A package should be
committed only when you are sure that you will no longer need to back it in.

Package Backout

Should you discover a problem once you have executed the package, or if the execution failed, you can back out the package. You
can also reinstate backed out packages, using the back in option.

BoK on Endevor Package Ver 0.00a Page 13 of 15

Infosys Technologies Ltd.

When you back out a package, you must use the BSTCOPY utility, not IEBCOPY.

Note: Package backout deals with ENDEVOR output libraries, not base and delta libraries. If reverse delta format is being used,
the base library member will not be backed out.

1. Why backout does not affect source?

Package backout is designed to restore load modules and other executables to their pre-package execution state. Backout does
not restore the source to its previous image, because the "bad" source is the audit trail of the change. This audit trail should not be
disrupted for any reason, because it allows you to view change history and changes only online, facilitating problem resolution.

ENDEVOR "knows" that the executables have been backed out even if the source isn't, by flagging the element in the MCF.
ENDEVOR warns users who subsequently attempt to retrieve the backed out element that they are working with a backed out copy.

Note: If you want to restore the prior level of source, you can do so online using the Summary of Levels panel on the Retrieve
action. The prior level of source, after retrieval, can then be added back into ENDEVOR, creating a new change level and
preserving the audit trail of the bad change.

2. Backout and package dependencies

As with package commitment, package backout and backin takes into consideration dependencies between packages.

Assume you execute package PKG1, containing elements COPYA, COPYB, COPYC, and COPYF. You then execute package
PKG2, also containing element COPYF, as well as COPYD and COPYE.

You then decide to back out PKG1. Because the execution of PKG2 has affected element COPYF, which is in both packages, you
must back out PKG2 first. Otherwise, COPYF will not be returned to its original, pre-execution state.

Package Shipment:

The package shipment utility uses data transmission programs to distribute package outputs (source, object, listing, or load
modules),or package backout members from a host site to another site. It is designed for users who develop software at a central
site and want to transmit source, object, or executable code either locally or to other (remote) sites.

BoK on Endevor Package Ver 0.00a Page 14 of 15

Infosys Technologies Ltd.

To use the package shipment utility:

Packages must be created with BACKOUT ENABLED=Y.
Packages must have been executed, but not committed
One of these data transmission packages must be available
XCOM 6.2 (CAI)
Bulk Data Transfer (IBM) Version 2, or via NJE/NJI
NetView File Transfer Program Version 1 (IBM)
Network DataMover (Sterling Software)
Remote destinations must be defined

Package action/status summary

If You Do This This Status Changes To Next Action Is

Create package None In-edit Modify or cast
Modify package In-edit In-edit Cast
Cast package
Approval In-edit In-approval Review
No Approval In-edit Approved Execute
Unsuccessful In-edit In-edit Correct and re-Cast
Review package
Approved In-approval Approved Execute
Denied In-approval Denied Reset and correct
Execute package
During execution Approved In-execution --
Successful In-execution Executed Backout, Backin, Ship
Unsuccessful In-execution Exec-failed correct and re-execute
Commit package Executed Committed
Backout package Executed Executed Backin, Ship
Backin package Executed Executed Backin, Ship
Ship package Executed Executed Backout, Backin, Commit

BoK on Endevor Package Ver 0.00a Page 15 of 15