Program Development Extension

PROGRAM DEVELOPMENT EXTENSION (PDX) USER MANUAL RELEASE 4.0

PROGRAM DEVELOPMENT EXTENSION

USER MANUAL

Winkler-Davis

San Francisco, California

(415) 572-3553

PROGRAM DEVELOPMENT EXTENSION (PDX) USER MANUAL RELEASE 4.0

PREFACE

This manual describes Program Development Extension (PDX). It addresses PDX functions as separate, but interrelated, steps. To minimize searching for individual panels to accomplish a given function, panels and key actions required for each task are grouped and illustrated. Users are encouraged read the Overview section, however, before attempting to research a particular function.

RELEASE 3.3 ENHANCEMENTS

Release 3.3 is a major upgrade to prior releases. Its installation requires compiling all COBOL programs and a one-time database conversion, using an installation utility. The new features provided are:

• Automatic Delta Generation.

• Automatic Cross Reference (XREF Command).

• Automatic Related Library Allocation.

• External BROWSE and EDIT functions, allowing authorized developers direct access to PDX entities.

• An external language translation command, allowing authorized developers to compile programs from inside other tools or directly from ISPF panels.

• A command to quickly compress PDS datasets.

• A new PDX Repository Interface (API).

• A set of host and workstation commands and programs allowing synchronization of materials being developed on the host for workstation install or materials being developed on the workstation for host installation.

• A new DEFINE command allowing definition of entities to be worked on without typing.

The new features are described in the appropriate sections of this manual.

RELATED DOCUMENTS

PDX System Administration Guide

Provides System Administrators with functions and procedures for initializing and maintaining PDX parameters, such as Authorization, Change Archival, Library and Data Base backup and restoration.

PDX System Programmers' Guide

Provides detailed Program Logic, Data Base Layouts and performance suggestions.

ACKNOWLEDGMENTS

Contributors

Winkler-Davis acknowledges the participation of the individuals who contributed to this document and who offered many valuable suggestions for features which have been included in PDX.

Vendor Interfaces

LIBRARIAN is a trademark of Applied Data Research, Inc.

PANVALET is a trademark of Pansophic Systems, Inc.

ACF2 is a trademark of Computer Associates International, Inc.

RACF is a trademark of International Business Machines, Inc.

Top Secret is a trademark of Computer Associates International, Inc.

DB2 is a trademark of International Business Machines, Inc.

IDMS is a trademark of Culinet, Inc.

______

PROGRAM DEVELOPMENT EXTENSION (PDX) USER MANUAL RELEASE 4.0

PREFACE i

SECTION 1 - OVERVIEW 1

SECTION 2 - START 9

SECTION 3 - DEFINE 17

SECTION 4 - DEVELOP 25

SECTION 5 - REVIEW 39

SECTION 6 - APPROVE 41

SECTION 7 - INSTALL AND BACKOUT 43

SECTION 8 - ENTITY ATTRIBUTES AND RELATIONSHIPS 45

SECTION 9 - ARCHIVE AND RETRIEVAL 47

SECTION 10 - RELEASE-CONTROL SEGMENTS 49

SECTION 11 - DELTA PROCESSING 53

Appendix A Library Types and Relationships 59

Appendix B CLIST Procedures 61

Appendix C Batch Messages 62

Appendix D Online Messages 64

PREFACE i

SECTION 1 - OVERVIEW 1

SECTION 2 - START 9

SECTION 3 - DEFINE 17

SECTION 4 - DEVELOP 25

SECTION 5 - REVIEW 39

SECTION 6 - APPROVE 41

SECTION 7 - INSTALL AND BACKOUT 43

SECTION 8 - ENTITY ATTRIBUTES AND RELATIONSHIPS 45

SECTION 9 - ARCHIVE AND RETRIEVAL 47

SECTION 10 - RELEASE-CONTROL SEGMENTS 49

SECTION 11 - DELTA PROCESSING 53

Appendix A Library Types and Relationships 59

Appendix B CLIST Procedures 61

Appendix C Batch Messages 62

Appendix D Online Messages 64

______

PROGRAM DEVELOPMENT EXTENSION (PDX) USER MANUAL RELEASE 4.0

SECTION 1 - OVERVIEW

1.1 Purpose

Program Development Extension (PDX) facilitates changes to the data processing production environment, including Development, Test, Approval, and Installation.

PDX supports managment and control of the orderly implementation of production changes. It supports the development process and ensures that the source and execution entities correspond and valid copies of current and previous production entities are available.

1.2 Composition

The PDX System consists of computer programs, interactive ISPF panels, messages and skeletons. A control data base is used to store information about changes and their entities. A set of data security rules ensures that actions are authorized.

1.3 Control Features

PDX control is accomplished by a set of ISPF panels which enable authorized users to:

• Obtain copies of production entities.

• Edit test versions in controlled staging libraries.

• Compile and link (or otherwise translate) test versions.

• Perform appropriate tests from staging libraries.

• Mark the entities ready for installation at the correct time and sites.

Authorized personnel may review and approve changes in Ready Status. Only authorized personnel may then install the reviewed and approved changes. PDX also performs the following functions:

• Ensures that backup copies of production are created before changes are made.

• Enables quick and orderly backout of changes when necessary.

PDX host Panels are driven by a set of COBOL programs, plus some Assembler subroutines. The COBOL programs have program path authority to update the PDXcontrolled libraries (which may NOT be updated by any other means). Each time a controlled library is modified, PDX creates an audit record, thus ensuring production library integrity.

The PDX Data Base, CLIST libraries and override libraries contain:

• Library Names and Relationships.

• Entity History.

• Entity Attributes.

• Compiler Options.

• Threshold Condition Codes.

• Entity Deltas.

• Change Segment Entities and Status.

• Language processor and preprocessor parameters.

These data include everything required for executing source language translations and installs into production in accordance with enterprise and application standards.

The control data base also stores lists of users authorized to perform PDX functions and the scope (e.g., application or group) within which the function is valid.

There are six levels of parametric control data:

1.Global

2.Group

3.Application

4.Segment

5.Segment Library Type

6.Segment Entity

Standard parametric data controlling the operation of compiles, link edits and other "source" to "target" translations reside at the Global level and, optionally, at any of the other lower levels. Thus, overrides at any of the above levels are permitted. A translated entity of a change segment has an associated "standards level" that is determined by the highest number of the override data encountered by the PDX source conversion process. The change segment as a whole assumes a standards level equal to the highest standards level of any of its elements.

In addition, detailed parametric data may be stored and retrieved for each PDX Entity.

1.4 Benefits

Combined as a system, the PDX panels, controlled libraries, Installation automated security rules (RACF or operating system security package), the PDX control database and PDX procedures:

• Ensure that production source and execution entities correspond,

• Maintain the specified number of production back-level copies,

• Maintain all entities required to reconstruct a load entity from source,

• Provide an integrated, consistent means for developers to specify, prepare and test changes,

• Maintain a complete and accurate audit trail of production library modifications, and

• Highlight non-standard changes when changes are made (the READY function) and allow for reporting non-standard changes on an audit report.

1.5 Change Functions

Production change development functions available to Users are displayed on the PDX Primary Menu Panel:

Figure 1(A). PDX Primary Menu Panel

Functions of each option are as follows:

CONTROL •Provide Change Control Number to PDX

•Specify (add/change/delete) Change Segments

•Inquire concerning Change Segments

PROCESS • Add, Change or Delete entities of a segment

• Fetch Elements from Production into Segement Libraries

• Fetch Entities from another Segment into Segment Libraries

• Edit Segment Entities

• Compile, link and test programs

• Import Entities to Segment Libraries

• Export Entities from Segment Libraries

• Checkout Entities to Workstation

• Checkin Entities to Workstation

• Promote Entities to Quality Assurance Segments

• READY Segment

STATUS • Review, or (for Segments in progress) modify Segment Status data including description, installation windows, remote site specifications or remarks

• Approve Segments

• Install Segments

• Backout Segments

LIBRARIES • Allocate, delete, or reallocate Segment Libraries

• Import complete PDS datasets

• Copy segment definitions from another segment

REVIEW • Display segments matching selection criteria

• Browse changes in progress, or installed

ADMIN • Review Production Library parameters

• Update Production Library parameters

• Review User Authorizations

• Update User Authorizations

OPTIONS • Review User Profile data

• Modify User Profile data

ENTITIES • Entity attributes

• Entity history

• Entity relationships

• Translation of production source entities

TUTORIAL • Obtain assistance for using the PDX System

1.6 Program Function (PF) Keys

PDX is menudriven, with commands that can be entered on one or more PDX panels. See Section 2.2, "Command Summary," for a list of PDX commands.

Program Function (PF) Key usage is standard.

FUNCTION KEY ENTRY

______

HELP/TUTORIAL PF1

SCROLL UP PF7

SCROLL DOWN PF8

EXIT TO THE PREVIOUS PANEL PF3

EXIT TO THE PRIMARY PANEL PF4

GO TO ANY PANEL In any field with = =>, (See above) Enter = plus Panel Identification (and suboption if wanted)

NOTE: PF Keys can be changed using the 'KEYS' command (These PF Key values are separate from the standard ISPF keys.)

1.7 System Terms

GROUP A 3 character code for permitting access to system features for more than one APPLID code. In general, represents a set of applications which can share access to change segment libraries and parametric data.

APPLID 3 character code identifying the Application. There are one or more applications in a GROUP.

ENTITY A member of a production library. A unique object of a change. An entity is an element of a LIBTYPE.

CHANGE 8 character code referring to all segments and Approvals for a Change.

SEGMENT A set of entities to be installed as a unit at one or more locations at a specified time. Identified by a 7digit number. One or more segments may be associated with a change.

SEGMENT LIBRARY Library created by PDX System as directed by an Authorized User. The segment library contains materials being created or modified by the developer.

LIBTYPE The internal name for a target production library or dataset containing "entities".

RELATIONSHIPS A libtype may be related to another libtype (e.g., SOURCE-LOAD) or an entity may be related to another entity. Entities inherit libtype relationships and may also have particular relationships to other entities (e.g., COPY, SOURCE). PDX provides ways to define these relationships.

1.8 Responsibility

Typical responsibilities for various PDX System functions are as follows

FUNCTION TYPICAL ORGANIZATION/POSITION

______

Product Management, Problem and Change Management,

PDX Process Management System Control

Initial System Training PDX Administrator/Team

Provide Control Information System Development

Change Processes System Development

Define/prepare Programmers

Make Ready Project Leaders

Approve Quality Assurance

Install Implementation Support

Backout Implementation Support

Emergency Procedures Production Support

______

PROGRAM DEVELOPMENT EXTENSION (PDX) USER MANUAL RELEASE 4.0

SECTION 2 - START

2.1 Quick Overview

If you have browsed this manual and perhaps have had a chance to go through the PDX tutorial provided for IBM compatible PCs and/or the host tutorial, you may wish to just "dive in" and try the system. This subsection is an overview of the steps required to define, prepare and install a change to the production environment. These are the steps to follow:

1. Define Segment. Select CONTROL on the PDX primary panel. To do this, you must have received your change control number from a source outside of PDX. Enter this number (left justified, if you wish) on the primary panel, and enter a "C" on the command line. Depress ENTER. Then overtype the information you see to define a "segment" and ENTER. When CHANGE DEFINED appears in the upper right corner of your screen, proceed to the next step.

2. Update Install Windows. Select the STATUS option (enter "=S" on the command line and ENTER). On this panel, modify the "window" for the installation time of your change segment to the correct dates and times. ENTER. STATUS UPDATED appears on the upper right hand corner of the panel.

3. Define Entities to be Changed. If this is a conversion and/or you have a lot of entities, perform step 8 and then proceed directly to step 5, bypassing step 4. If this segment is almost like a previously defined segment, perform step 9. Otherwise, select the PROCESS panel (Enter "=P" on the command line) and perform step 10.

4. Allocate Staging Libraries. The entities of your segment are now defined. Allocate a segment library for each library type. Do this by entering ALLOC on the command line. The AUTOMATIC ALLOCATION panel will be displayed. Enter the library type and the approximate number of elements it will contain for each library to be allocated. PDX will allocate related libraries if they are not already allocated. Then END (PF3).

5. Fetch Elements. You may now FETCH entities from production or another change. Alternatively (and with less auditability) you can simply use EDIT/COPY to bring elements into your segment library. Use the "F" line action on the Process panel to FETCH.

6. Translate Source to Executable. For ASIS entities, no further processing is needed. For entities that must be translated, enter "T" next to the source for the entity. A job will be submitted for each entity. If the translation process is correct, a zero return code will appear on the panel for both source and related target entities. If a non-zero return code appears, determine the reason and correct.

7. Test from Staging Libraries. Test the entities of the change segment. For batch load entities, you can STEPLIB to the dataset:

{system-prefix}.{GRP}{APL}.C{segnum}.{libtype}.

For online entities, your CLIST process probably has copied the load entity into your online test library. Test in the normal manner.

8. Ready Segment. When testing is complete, enter READY on the command line of the PROCESS panel. This "freezes" your segment. Notify the person that will approve your change segment that "segment xxxxxxx is ready.". You can then periodically check to see if the segment has been approved or installed. When your segment status is "A", the segment is approved. When your segment status is "I", it has been installed. If production fails, an authorized individual can "backout" the segment, restoring the previous versions of each element in your segment.