program development extension · web viewuser manual winkler-davis san francisco, california (415)...

PROGRAM DEVELOPMENT EXTENSION (PDX) USER MANUAL RELEASE 4.0

PROGRAM DEVELOPMENT EXTENSION

USER MANUAL

Winkler-DavisSan Francisco, California(415) 572-3553


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 GuideProvides 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' GuideProvides detailed Program Logic, Data Base Layouts and performance suggestions.

ACKNOWLEDGMENTS

ContributorsWinkler-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 InterfacesLIBRARIAN is a trademark of Applied Data Research, Inc.

_________________________________________________________________________________

Copyright 1991, 2009, Winkler-Davis, Inc. Page i


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.

_________________________________________________________________________________

Copyright 1991, 2009, Winkler-Davis, Inc. Page ii


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

_________________________________________________________________________________

Copyright 1991, Winkler-Davis, Inc. Page iii


Appendix B - CLIST Procedures.................................................................................................. 61

Appendix C - Batch Messages.................................................................................................... 62

Appendix D - Online Messages................................................................................................... 64

_________________________________________________________________________________

Copyright 1991, Winkler-Davis, Inc. Page iv


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 PDX-controlled 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.

_________________________________________________________________________________

Copyright 1991, Winkler-Davis, Inc. Page 1


• 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.Global2.Group3.Application4.Segment5.Segment Library Type6.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 menu-driven, 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 PF1SCROLL UP PF7SCROLL DOWN PF8EXIT TO THE PREVIOUS PANEL PF3EXIT TO THE PRIMARY PANEL PF4GO 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 7-digit 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 DevelopmentDefine/prepare ProgrammersMake Ready Project LeadersApprove Quality AssuranceInstall Implementation SupportBackout Implementation SupportEmergency Procedures Production Support

_________________________________________________________________________________



_________________________________________________________________________________



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.

9. Importing an Entire Library. For conversions or for a vendor package, use the LIB IMPORT

_________________________________________________________________________________



function to define the elements of the change, allocate the segment library, and physically copy the elements from an external library to the segment library. Select LIBRARIES ("L") on the primary panel. Then select IMPORT LIBRARY ("I") and follow instructions.

10. Copying a Previous Definition. For a segment with a lot of elements that is to be just like or almost like a previous segment, copy the definition from the previous segment. Select LIBRARIES ("L") from the primary menu. Then select COPY CHANGE and follow instructions.

11. Enter Definition. If this is a relatively small number of entities, just enter the entity names, the library types and the clist names on the process panel. Once a few have been entered, you can overtype the ones there to provide a "ditto mark" effect.

2.2 Command Summary

The following commands may be entered while in TSO EDIT within TSO:

PDXCOMP Compresses the current EDIT dataset. Use this command if you experience an E37 ABEND while editing a source entity.

COMPILE Translate the entity being edited. This command is provided as a convenience for initial diagnostic compiles. Care must be exercised because the compiler return code will be masked on the process panel if you exit EDIT after the translation is complete.

The following commands may be entered on any PDX panel:

OPTIONS Use this command to set up or modify your PDX profile. See primary panel, Option O, for help on this subject.

The following commands may be entered on the STATUS panel (Option S from the primary panel):

INSTALL Submit a batch job to install the current segment (which must be in approve status). The user must have INS authority.

BACKOUT Backout the current segment.

The following commands may be entered on the PROCESS panel (Option P from the primary panel):

TRANS {libtype}

In this case, libtype must be a library type that exists in the current segment. ALL members of this libtype are translated (compiled and linked, etc.).

XREFUpdate the repository cross-reference for this segment. For example, the relationship pointers for copy members in the segment that are used by programs in the segment are updated.

VERIFY Perform extended checking in the elements in the segment. Verify checks that members are present in the staging libraries for each entity on the process panel, that compiles and links have been performed in the proper sequence and that all required related entities are present in the segment.

ALLOC Allocate segment staging library or libraries for this segment.

BACKOUT Issue this command on the status panel. The segment is backed out. The user must have INS authority.

COPYCHG This command allows copying the definition of another change into the current change.

_________________________________________________________________________________



READY Ready should be executed on the process panel. It checks to make sure all entities have zero return codes and places the segment in ready status if so. The user must have RDY authority to issue this command.

PROMOTE Issue this command on the "from" segment to promote entities from this segment to the "target" quality assurance segment. See Section 10, Release Control Segments.

SEGPRINT All the information for each entity of the segment is printed.

TRANS

XREFPerform cross referencing for this segment. The relationships for all copy members in the segment will be updated.

LOCATE {libtype-prefix} {member-prefix}

The two parameters determine the first libtype (and member, if specified) to be displayed. All the members originally displayed are still scrollable; only the position of the display is modified.

DEFINE {libtype}

The following commands may be issued outside of PDX. This means they can be incorporated into other tools or can be made options on ISPF panels:

PDXED {segment} {libtype} {member}

Edit the specified entity that has been defined in a segment that is in development mode.

PDXTRAN {segment} {libtype} {member}

Translate the specified entity that has been defined in a segment that is in development mode.

2.3 Authorization Requirements

All Users must be defined to the PDX System and

1. Have a Time Share Option (TSO) ID,

2. Be familiar with standard ISPF panels and commands,

3. Be further authorized to perform PDX functions within a specified scope.

The scope of a User function authorization may be global, or restricted to

• Group(s)• Application(s)• Change Control Number(s)

• PDX Change Segment Number(s)

Change functions include:

DEF • Define a New Change

CHG • Allocate Change Libraries

_________________________________________________________________________________



• Define Change Elements • Edit, Compile and Link Change Elements

RDY • Make a Change READY

APR • Approve a Change

INS • Install a Change

BKO • Backout a Change

UPD • Update Entity Attributes in database

2.4 System Access

To access the ISPF/PDF Primary Options Menu under TSO, logon to TSO and execute ISPF to display the ISPF Primary Menu panel.

Now select the PDX option provided by your installation. In the example, the "PDX" option should be selected, and will display the following panel:

Figure 2(B). PDX Primary Menu Panel

2.5 Options

The PDX options panel enables user data to be entered and maintained as part of the TSO profile. The information is then readily available for automatic entry on successive PDX panels.

_________________________________________________________________________________



Figure 2(C). Programmer Profile Panel

FIELD DESCRIPTION_____ ___________________________________________________________

JOB CARD Job Card information for Batch submission.

REVW APPLIDS3-character Application IDS to control selection criteria for REVIEW option on PDX primary menu. Enter consecutive 3-character application codes for any applications you may be interested in reviewing. See Section 5.0, REVIEW.

The Programmer Option Panel may be accessed from any other PDX panel via the OPTIONS command.

_________________________________________________________________________________



_________________________________________________________________________________



SECTION 3 - DEFINE

3.1 Overview Changes are defined in four major steps:

1. ESTABLISH A NEW CHANGE SEGMENT

2. ENTER BASIC SEGMENT DATA (SITES/WINDOWS)

3. DEFINE SEGMENT ELEMENTS

4. DEFINE SEGMENT LIBRARIES

The Control number is obtained from a source outside of PDX. For example, IBM's INFO Control System may be used for administrative control of the change process (other than the actual development and install process controlled by PDX). The Change Control Number is the primary key to its contained segments. One or more PDX Change Segments may be part of the Change Control number.

3.2 Establish Change Segments

On the PDX primary menu panel, select CONTROL ("C"), TAB once, type the change control number and ENTER. Example: "C", TAB, 13130, ENTER. The change control number may be left-justified with trailing blanks.

The following panel will be displayed:

_________________________________________________________________________________



Figure 3(B). Define or Review Change Segments Panel To enter a new segment, overtype the sample information. To add a segment, overtype an existing segment with the new information.

More than one segment for a single change control number is a requirement if some of the elements of a change must be installed at a different time than others. For example, if the online portions of a change are to be installed on Thursday night and the corresponding batch portions on Friday night, then two segments are required.

FIELD DESCRIPTION____________ _______________________________________________________

CHANGE (program-inserted)CONTROL NO.

CHANGE Enter description of INFO Change DESCRIPTION

ACTION CODE A (for ADD)

GRP Group

APL Application

SEGMENT (Clear Text) Enter all Segment descriptions related to the Change. Repeat from 'A' (above); overtype each segment description.

(Enter) New Segment is generated for each 'A' entered. System responds

"Change Defined". 3.4 Define Basic Segment Data

The basic data about your change segment includes the segment window information (when and where to install the segment), its description, and some brief comments to indicate its priority.

To enter the basic data, select the STATUS panel, either from the PDX primary panel or by using the "=" function from any other panel. You may then enter or modify the fields on the screen. The data on this screen may be modified any time during development. It should be verified carefully and finalized by the developers prior to using the READY command to freeze the change segment.

_________________________________________________________________________________



Figure 3(E). Change Status Panel

FIELD DESCRIPTION________ _______________________________________________________

SITES AND WINDOWS Installation Sites: XX = Site Code

(See your administrator for code list)

AFTDATE Installation must occur on or after this date.

AFTTIME Installation must occur at or after this time.

BEFDATE Installation must occur on or before this date.

BEFTIME Installation must occur on or before this date.

REMARK Optional. "HOT", "AFTER POST RUN", etc.

RMT STATUS The status of remote sites for the change segment. "AUTO" means that the segment is to be installed at the remote site. Only other value presents concurrent installation at the remote site. After the install command, PEND means the change is being installed at the remote sites. xxFL means the remote site install failed at xx (the two character site code assigned by your installation). INST means the segment is installed at the remote site.

3.5 Define Entities Each entity of a segment must be defined to the system before fetching, editing, compiling, or other

_________________________________________________________________________________



functions may be performed. It is not necessary to define all entities at the same time. However, as soon as it is known that an entity will be needed in the segment, it should be defined. PDX cannot provide warnings about emergency changes or work starting on another change unless the entities have been defined using this process.

To define an element, you must have CHG authorization access that includes the scope (Group and Application) that is associated with the entity. Otherwise, you will receive a "User not Authorized" message.

Elements are defined on the PROCESS panel, which can be accessed either by returning to the PRIMARY panel and selecting the PROCESS option or by using the "=" key and the PROCESS option number (in a ===> window). When this selection has been made, the following panel will be displayed:

Figure 3(C). Process Change Elements Panel

FIELD DESCRIPTION________ _______________________________________________________

MEMNAME Name of the element within the library.

LIBTYPE Name of library for this element (up to 8 characters). Identifies the change library used and the production target library for element. See Appendix A, Library Types.

CLST Name of CLIST process to perform on the element (ASIS) means no process to be performed. See Appendix B, CLIST Procedures.

F (Function) A = new entity C = modification of an existing entityD = delete production element

_________________________________________________________________________________



P = Use production version (copy code change)

Your administrator will have established certain "library relationships" that will cause an identically named member to be established in your segment automatically when you add a member. For example, you might add a "SRCE" entity and the "LOAD", "DBRM" and "SRCED" would be automatically added because source entities are related on a one-to-one basis to load entities, DBRMs and source deltas. See Appendix A for more details about library relationships. You may browse the production library administrator information (A.P option) to find the exact relationships for a particular library type.

3.5.1 Online Member Selection

You may enter the DEFINE <libtype> command on the process panel and then enter an external dataset name and select members to be added to your segment.

3.6 Define Staging Libraries

Allocate a Segment Staging Library for each library type. The system will automatically define related libraries unless they are already defined.

Call up the AUTOMATIC LIBRARY ALLOCATION Panel from any PDX panel by entering the ALLOC command on the command line. You will then be presented with the following options:

FIELD DESCRIPTION______________ _______________________________________________________

LIBRARY TYPE ====> Internal Name for Destination Library

NO. OF ELEMENTS==> Approximate Number of Elements Library will contain.

The system allocates space based on the allocation factor established for this library type (which can be viewed via the A.P panel). The allocation factor should approximate the average number of records in a member of the type you are allocating. If your application has unusually large numbers of records per member, increase the count for your allocation. The system uses at least a 50% factor for the secondary allocation and allocates ample directory blocks to hold the number of members specified.

Your segment library will be allocated with the following DSNAME format:

{system-prefix}.GGGAAA.C{segment ID}.{libtype}

where GGG is your group, AAA is your application and {libtype} is the library type you are allocating. Depending on the security rules established for your installation, you may or may not be able to browse the library outside of PDX. You will not be able to modify the library outside of PDX.

3.7 Special Library Functions

The LIBRARIES option from the primary panel offers a menu that allows selection of options that allow for the deletion or compression of change segment libraries, the mass conversion of elements of external PDS libraries (application conversion) and copying the definition of a previous change segment.

3.7.1 Compress or Delete Segment Library

When libraries are allocated using automatic allocation, space is calculated using the production library information as specified on the production library panel (Option 6.2 -- PLIB). The "allocation factor" on the PLIB specification is used to calculate the primary blocks for the library, and then one-half of that amount is used for the secondary allocation. Even so, when a lot of editing or compiling is done, the library may require compression. Use the compress option for this purpose. The PDXCOMP command may be issued within EDIT

_________________________________________________________________________________



to perform this function.

3.7.2 Mass Import from External Library

A facility is provided to define, allocate and import the members of a Partitioned Dataset. This provides an easy way to convert elements to PDX or to refresh existing software when a vendor supplies a new release. To access this function, use the LIBRARIES option of the PDX primary panel. Then select LIB IMPORT. You will be asked to enter the name of the external library, and to select the DEFINE, ALLOCATE, and IMPORT functions in sequence. The DEFINE function will add the elements of the PDS to your (already defined) change segment. ALLOCATE will allocate a library using the count of members obtained during the define operation. IMPORT will copy the members into the library just allocated. When all library types have been so processed, the application is converted.

3.7.3 Copy a Previous Change Definition

Frequently, a change must be made to exactly the same elements as was made at a previous time. For example, a set of table members, or a set of programs using a particular copy member, or a set of otherwise related elements. To define a change segment that is just like a previous one, use the COPY CHANGE option within the LIBRARIES option of the PDX primary panel. You must first define the new segment using the CONTROL option, then supply the old segment number and the elements will be placed into the new segment. You must then define the libraries using the ALLOC command in the usual way.

_________________________________________________________________________________



_________________________________________________________________________________



SECTION 4 - DEVELOP

4.1 Overview When definition is complete, a Change and its Elements are available processing and further development by authorized personnel. Processing may include

• Fetching elements from production or another segment

• Importing/exporting entities from/to other Libraries

• Editing entities in segment staging libraries

• Compiling or otherwise "translating" segment entities

• Testing

• Automatically inserting entities related to another entity

• Cross referencing entities in a segment (XREF command)

• Promoting entities to a quality assurance segment (see Section 10)

These operations are all performed using the Process panel. 4.2 Process Panel Access to the Process panel is from the PDX Primary Menu panel or via the "=" function from any other panel. This panel is used for most development functions, including making modifications to the elements of a change and the translation of source code to executable.

_________________________________________________________________________________



Figure 4(A). Process Change Elements Panel The elements (or "entities") defined in a Segment are displayed. One line is shown for each entity of the Segment. All entities of a large Segment may be displayed by scrolling. Single letters entered in the "L" column (line action) to perform the function selected for the entity on that row.

FIELD DESCRIPTION_________ ___________________________________________________________

ACT ACTION COLUMN

A Add this entity to the segment. Overtype the sample or another entity.

C Change the CLIST for this entity.

D Delete this entity from the segment. (The member within the library, if it exists, will also be deleted.)

F Fetch this entity from Production or another segment to the Segment Staging Library (see Section 4.5).

E TSO Edit this Entity.

B TSO browse this Entity.

T Compile, link, or otherwise translate the Element using CLIST specified under CLIST

(see Appendix B).

I Import the Element from another external or Segment Library (see PDX System Conversion Information).

_________________________________________________________________________________



X Export this Element to another Library from Segment Library. K Force return-code to 'zero' (job control only).

R Automatically add all entities with '02' type relationship codes to this segment. See Section 8.1, Process Library Elements, for how to define entity relation-ships.

G Override "FETCH WARNING". See Section 4.3, Fetch, for a full explanation of this function. H Select History for entity (see Section 11. Delta Processing).

Any of these line actions may be entered for multiple elements. Other fields on this panel are as follows:

SELECTION DESCRIPTION________________ _______________________________________________________

L Line Action MEMNAME Member Name of the EntityLIBTYPE Library Type CLST Clist Procedure Name (see Appendix B) F Function for A = New,

this Element: C = Change, D = Delete

A Last action: S = Batch Job Started,C = Batch Job Complete, E = Edit, R = Ready,A = Approval

RTCD Return Code from Batch JobS Source Status: P = Production,

C = Another Change, U = Unknown,N = NewB = Basis Element Changed

SRCCHNG Change ID from which Element was Fetched X Cross N = None,

Reference G = Good, Status: B = Bad,

U = Unknown. USER TSO User ID for last action DATE Date of last action TIME Time of last action S Element Standards level

1 Used Installation Global Standards2 Overrides at Group Level3 Overrides at Application Level4 Overrides at Change Segment Level5 Overrides at Segment Library Level6 Overrides at Element Level9 Non Standard Procedure; Invalid Fetch

O Element Ownership StatusY Element is "owned" by installing ApplicationN Element is not "owned"

F Fetch Override StatusB Fetch override ("G" action) has been executed.

FLAGS B Base Copy PendingF Fetch Completed

_________________________________________________________________________________



4.3 Fetch NOTE: See Figure 4(B). Process Change Elements Panel above. The PDX Fetch function is used to obtain members from Production Libraries or to add vendor-supplied member(s) to an existing Change Library. FETCH obtains elements from libraries that are under the system's controlled environment. FETCH, rather than IMPORT or EDIT/COPY should always be used after conversion because FETCH activates PDX version control. FETCH displays a panel that enables selection of the version upon which the change is to be based. This panel indicates in what other segments the members are found, enabling inspection of the other segments and determination whether this segment should be implemented before or after the other segments. When the panel is displayed, enter an "F" (fetch) next to the version you wish and ENTER. Note: Elements that have been archived (about 8 days after installation) cannot be fetched from another segment. Fetch Warning: The system provides a warning if the element upon which a present change is based is changed. That is, if a FETCH is done and then the object fetched is modified (EDIT, IMPORT, FETCH or INSTALL), then the CLIST RETURN CODE field is set to 8192 and the SOURCE field (See Below) is set to 'B'. On the PROCESS panel, each Element is controlled by the 'X' column, which indicates whether the basis of the Element been changed. Other codes in the column: P = Valid Fetch from a production library

C = Valid Fetch from another Segment B = FETCH was used and the object fetched was changed

A Fetch warning may be overridden by using the 'G' action code. If used, the F (Fetch) field for this element is set to 'B' and the standards level for the element is set to '9'.

4.4 Test From Change Libraries In general, development personnel have direct EXECUTE access to Segment Libraries, enabling programs to concatenate a steplib to Segment Libraries using established procedures.

Change Library format:

PDX01.AAABBB.CNNNNNNN.XXXXXXXX Where, PDX01 is your installation-selected prefix,

AAA = Group ID

BBB = APPLID

NN---NN = Segment Number (Right-justified, zero fill)

XX---XX = LIBTYPE

4.5 CLIST Override for Unit Testing When translating an element, the CLIST name can be over-typed with different CLIST for a one-time Translate. This is useful for compressing a Dataset (CPRS) or executing a "test-only" CLIST like an intertest compile and link. A successful one-time Translate will have a Return Code of 4094. This is the equivalent of a zero return code, except that the segment cannot be placed in READY status until the "official" translate is done.

_________________________________________________________________________________



4.6 Ready Segment Users authorized to place a segment in READY status enter READY on the command line of the Process Change Elements panel. The READY

• Ensures that the CLIST RETCODE field for each element is zero

• Calculates the over-all standards level for the change

• Places the change in Ready Status When the change is READY, elements cannot be changed (but the status may be changed back to DEVELOPMENT if necessary). Final regression testing can be performed while the segment is frozen.

4.7 PDX Language Translation Processes

TRANSLATE PDX uses a CLIST subset language to perform "translations" of source modules into one or more "executable" modules. Examples are compiles, assemblies, CICS map assemblies, link edits, job control checks and others. A CLIST may perform any function that has been established by your installation, including library compresses, source module merging, etc. When elements in a segment are defined, a CLIST Name is required. This name determines exactly what translation is to be performed on the source module. CLISTs have been defined that perform various programming functions. (See Appendix B - CLIST Procedures.)

TRANS COMMAND Sometimes, it is necessary to TRANSLATE all the members of a particular

library type. For example, when an application is first converted, and translations are being done, all of the source members must be translated without change. Another example is when a vendor supplies a new version of source code for an application. To translate all the members of a library, enter: TRANS {libtype} on the process panel.

Example: TRANS SRCE

This action causes PDX to submit a Job for each Element within a Segment with the same LIBTYPE.

TRANSERROR If a non-zero Return Code is received when translating a Member, the CLIST will

create a TRANSERROR message in the body of the TSO commands. This points to the process in which the error occurred. To assist in finding this message, browse the SYSTSPRT dataset and use the command: FIND TRANSERROR. The message will then indicate what caused the error.

If a Return Code 12 and no message is received, the CLIST has an error. When this

occurs, contact your PDX support programmer. Supply the SYSOUT for the job with the problem.

JCL SCAN To use, enter ZCLS (instead of ASIS) for the CLIST name of the JCL and PROCLIB

elements.

After the CLIST name change, enter the T line action to submit the SCAN. If the change is initiated for a job member, and a PROC member with the same name

is in the segment, the system concatenates the segment PROCLIB with the other installation PROCLIBs for the scan process.

_________________________________________________________________________________



If the return code is zero, it will update the return code for the matching PROCLIB member within the change segment.

If the change segment contains only a PROC member, the system inserts a default Job Card enabling the scan to proceed. Your administrator may have set up PDX to submit multiple scans for all jobs that use the PROC being changed.

If a non-zero return code is received, but inspection of the SYSOUT indicates the error is acceptable, enter K on the Line Action column to override. (Standards Level displays 9 to highlight this situation during approval.)

LINK CONTROL If link control is found in a change segment, it will be automatically included with the

object module for a module being translated. This applies only to applications using "load module replace" processing for multiple-control section modules, and only if the "main" module is being translated. The name of the link control library is application-dependent and is determined by your PDX Systems Administrator. See also Section 4.11, Multiple Control Section Load Modules.

LINK CLIST The LINK CLIST creates a multiple-control section load module. (The name of this

CLIST is assigned by your System Administrator.) See Section 4.11, Multiple Control Section Load Modules, for details on this CLIST.

COMPILE ONLYEnables module compilation, or assembly, to produce a listing and a load module without creating a change segment:

• Enter Option 8 - ELEMENTS on the PDX Primary Menu.

• Enter the LIBTYPE, Member Name of the Module to compile, 1 plus the

CLIST Name to be used Example: LIBTYPE SRCE

MEMBER FASA0001 CLIST COB2

(Enter Key) Panel displays the data entered

• Enter T (TRANSLATE) next to MEMBER NAME(s)

(Enter Key)

• If you have allocated a temporary dataset called 'userid.PDX.TEMPLOAD', then your load module will be placed there. You must have change authority for the application owning the module to perform a compile of a production module.

• Output listing is routed to the Sysout Class specified in your PDX options.

4.8 Language Translation Parameters

PDX controls the language translation process by concatenating a set of CLISTs together. The first of these is obtained from the GLOBAL "set" library. Usually, this member will contain your installation's standard parameters for language translation and the standard "threshold" limits for return codes. Following this, PDX concatenates a "group" and an "application" member in front of the translation process itself. The entity attributes of the module you are translating are also used to control the language translation process in a manner defined by your installation. "Entity Attributes", below, explains this in more detail.

_________________________________________________________________________________



If your application has special requirements, contact your administrator. The current settings of the "set" library members are printed when you run your language translation in the AUTPRINT dataset. The CLIST itself is printed in the SYSTSPRT dataset. Current entity attributes are also printed.

4.9 Modules with Aliases

The Load/Alias relationship is set up during Translation. To create an Alias,

1. Define the Module (Source and Load)

2. For each Alias, define a Member with the Alias Name (Use same LIBTYPE as the Load Module defined in Step 1 (above)

3. Define and create a member in your link control LIBTYPE for the Module, containing at least the

following cards:

ENTRY modname modname = the name of the Module ALIAS aliasname aliasname = the name of the aliasNAME modname(R)

If other linkage editor control cards are needed, they are put into the Member before the NAME card.

After the change is installed, the link control member is not required for subsequent changes (unless content is being modified). The CLISTS will use the production version if the link control member is absent.

On installation of a Module with an Alias, PDX will correctly install the alias if it has been defined as an element in the Load LIBTYPE.

4.10 Entity Attributes

When CLISTS are executed, a number of data variables found in the PDX data base are passed to the CLIST for use in making decisions or for language processor parameters. If CLISTS are active that use these data values, then you should ensure that your module has been assigned the correct attributes before submitting a translate. Module attributes appear on the ELEMENT HISTORY panel (Option 8) or may be viewed and updated (if authorized) or by using the "U" line action on the process panel. This line action passes control directly to the ELEMENT HISTORY panel. Module attributes are optional, and are only meaningful if a CLIST has been defined to interpret the attribute. The attributes that may be entered on the ELEMENT HISTORY panel are:

ATTRIBUTE TYPICAL CLIST INTERPRETATION

DEFAULT CLIST A default CLIST name. If active in your installation, this name will appear on the process panel when the element is defined in a segment.

PROGRAMMING LANGUAGE This field may be used by the CLIST to determine which language processor to use.

PRE-PROCESSOR This field may specify which, if any, preprocessor is to be used with this module. For example, CICS might indicate that the CICS pre-processor is to be executed prior to language translation.

COMPILE OPTIONS The CLIST may insert these options in place of or in addition to the GLOBAL, GROUP or APPLICATION language translation parameters. For example, you might enter LANGLVL(1) if your source code requires this. Also, this field may indicate that this module is a subroutine (TRANS=SUBROUT, for example).

_________________________________________________________________________________



LINK OPTIONS The CLIST may insert these options in place of or in addition to the GLOBAL, GROUP or APPLICATION link edit parameters.

Your enterprise may have defined attiditional attributes. See the entity attribute panel and use HELP to see the attributes available. Also see Section 8, Entity Attributes and Relationships.

4.11 Multiple Control Section Load Modules

PDX supports multiple control section load modules and either separate object module storage or "load module replace" processing. This section describes the alternatives available, how they are selected and how to perform development activities under each alternative. In order to clarify the concepts contained in this section, examples of common alternatives to handling multiple control sections are first presented.

4.11.1 Example of Standard Process

The PDX Administrator has established the following libraries and related libraries:

LIBTYPE LIBRARY NAME RELATED LIBRARY

SRCE APPL.PROD.SOURCE LOADSUBS APPL.PROD.SOURCE OBJECTOBJT APPL.PROD.OBJECT SUBSLOAD APPL.PROD.LOAD (None)LCTL APPL.PROD.LINKCTL LOAD

The developer wishes to define a new load module that contains a main module and three subroutines. The load module is named BIGMOD and the source modules are named COBPRG1, ASMPRG1 AND ASMPRG2. COBPRG1 is the main module. The steps to define, process and READY this segment are:

1. Define a new segment in the normal way.

2. On the PROCESS panel, enter COBPRG1, ASMPRG1 and ASMPRG2 with a SUBS libtype. The system will add three modules with the same name and an OBJECT libtype. Enter BIGMOD with a LCTL library type. The system will add BIGMOD as a LOAD library type.

3. Allocate libraries for SRCE, OBJT, LCTL and LOAD.

4. Import or EDIT/COPY the three source modules into their libraries. Perform TRANSLATES for each source module, using the appropriate CLIST (e.g., COB2, ASMH or TRAN).

5. Import or EDIT/COPY the BIGMOD link control:

ENTRY BIGMODINCLUDE SUBLIB(COBPRG1)INCLUDE SUBLIB(ASMPRG1)INCLUDE SUBLIB(ASMPRG2)

Note: The SUBLIB ddname is installation-dependent.NAME BIGMOD(R)

6. Translate the BIGMOD load module.

7. Test, revise and enter READY when testing is complete. Notify Q/A that the segment is READY.

_________________________________________________________________________________



4.11.2 Example of Standard Process for Revision of a Subroutine

The developer wishes to modify the program ASMPRG2 in the module BIGMOD. To do this, the following steps are necessary:

1. Define a segment in the normal manner.

2. On the process panel, enter ASMPRG2 with a SUBS library type.

3. Enter BIGMOD with a LOAD library type.

4. Allocate libraries for SUBS, OBJT and LOAD.

5. FETCH ASMPRG2 from production, make necessary changes and TRANSLATE.

6. TRANSLATE BIGMOD.

7. Test, revise and enter READY when complete.

4.11.3 Library Relationships for Subroutines and Load Modules

Source and load/object libraries can have either a 1-1 relationship or many-1. In a 1-1 relationship, there are separate source libraries for subroutine source modules and single-source modules. When the 1-1 relationship is in effect, the CLIST defaults to either a subroutine or a load module translation based on whether the source module resides in a subroutine source library or a single source module library.

The system administrator may set up a subroutine source library by entering the name of a related object library with "S" as the relation-type. The same library type is also inserted with a "1" relation-type. This tells the CLIST to perform a subroutine translation and tells the process panel processor to "pop up" the related object library for every source module entered on the panel. For a source-load relationship, only the "1" is entered.

For applications that do not use the 1-1 relationship concept, there is only one source library. A module in this source library may be either a subroutine or a single-source module. The administrator may set up the source-load relationship with a "1" relation type and the source-object relationship with a "O" relation type. This tells the system the names of the libraries to use, but does not specify whether to perform a subroutine or a load module translation for a particular module. The CLIST then uses other information to determine what do, as detailed in the following sections. Alternatively, the PDX Administrator may set up two source library types that point to the same source library (e.g., SOURCE and SUBSRCE). In this case, CLIST processing defaults depending on which libtype is used.

4.11.4 Language Translation Control

There are three choices for applications as to the way in which subroutines and multiple control section load modules can be handled:

1. Separate Link For All Load Modules. In this approach, all language translations produce an object module that is stored as a production entity. The developer must execute a separate link edit translation for each load module even if the program has no subroutines.

2. No Link Edit for Subroutines. The system creates object modules only for subroutines. Single-source programs (e.g., most CICS programs) do not require a separate link-edit or link control. The link edit is defined only for composite modules.

3. No Maintenance of Object Modules. If there is no type "S" or type "O" library related to the source library, "load module replace" processing is assumed. Object modules are not stored in production. Production link control will represent the most recent control sections modified. (Warning. If COBOL DYNAM is specified, the most recent COBOL subroutines will be loaded at execute time, otherwise, the routines first included in the module will be executed.)

_________________________________________________________________________________



The interaction of the library parameters stored by your system administrator, the global and application parameters residing in the "SET" library for the CLIST to be executed, the CLIST itself and the module attributes stored in the database determine the action to be performed and the entities to be moved into production. There are three ways to cause the output of a language translation to result in the storage of an object module in the segment library and the subsequent installation of the object module into a production library:

1. CLIST Name. Certain CLISTS will always perform SUBROUTINE processing, no matter what other parameters are present. In this way, a module can be forced to be differently than as specified in the global or application default. These special CLISTS are CAPS, ASMS and PL1S.

2. Application Standard. If the global, group or application "SET" member for the CLIST to be executed contains 'SET PDXTRANS=OBJECT" then the default is to perform a subroutine translation. If "SET PDXTRANS=LOADMOD" is active, then a "load module replace" translation is the default.

3. Entity Attributes. The standard CLIST will override whatever other parameters are in existence with the module attributes that have been defined in the database for the module to be translated, if present. These attributes are entered in the COMPOPT field on the module history panel, which can be accessed either via the "U" option of the process panel or via Option 8 of the primary panel. If the compile options include PDXTRANS=OBJECT, then a subroutine translation is performed. If PDXTRANS=LOAD is present, then a load module translation is performed.

4.11.5 Summary of Source Translation Rules

The following rules summarize the actions of a language translation CLIST:

1. If there exists no type "S" or type "O" library related to the source library or if PDXTRANS=LOADMOD is in effect then "load module replace" processing is assumed. The object module is stored in a "work" library and is included in any link edit done within the segment.

2. If the CLIST is a subroutine type or object library relationships present for the source library are "1" and "S" then a subroutine translation is performed.

3. If neither of the above is true and the parameter PDXTRANS=OBJECT or PDXTRANS=LOADMOD is present in the COMPOPT field of the module options in the database for the module being translated, then the CLIST acts accordingly.

4. If none of the above is true, then the system global or application default is used, whichever is active.

4.11.6 Link Edit Processing

Link control (either in the segment or in production) is required for a load module that contains multiple control sections, and a separate link edit must be defined for the segment. For a new module or when the link control is to be modified, the link control must also be present in the segment. Link control and load module names must be identical. Except for "load module replace" processing, link control must include all control sections of the load module. The system default for the ddname to be used in the INCLUDE statement is OLDMOD. This name may be reassigned for a given application. An application may also include up to three private application libraries with different, application-assigned ddnames. Any modules in the segment object library or work library (for load module replace) will be concatenated in front of the corresponding production library.

4.11.7 Segment Definition for Multiple Control Section Modules

Use the process panel to define segments. Ascertain the library types for the standard (or your application)

_________________________________________________________________________________



for source modules, subroutines (if different), link control and load modules. Then enter the following, depending on the situation:

ENTITY TYPE ENTER SYSTEM ACTIONSingle Source Module Source Module Defines Load ModuleSubroutine (Single Libtype) Object Module Defines Source ModuleSubroutine (Two Libtypes) Source Module Defines Object ModuleNew Load Module Link Control Defines Load ModuleModified Link Control Link Control Defines Load ModuleLoad Module Load Module None

For all source modules, enter the "T" for translation on the source module line. For load modules, enter the "T" on the load module line.

_________________________________________________________________________________



SECTION 5 - REVIEW

5.1 General

Review Changes is an inquiry panel displaying history and present status of any change in the system.

The PDX Review function enables Change Approvers (Section 6.0) and Change Installers (Section 7.0) to scan and verify system changes to be approved and installed.

When Option 5 REVIEW is selected on the PDX Primary Menu panel, the PDX review panel is displayed with these options:

FIELD DESCRIPTION_____________ _______________________________________________________

PROFILE Y=Select on profile APPLIDs.N=Do not use profile application list.

GROUP/APPLID Select segments for a group, or APPLID.

STATUS Limit review to segments in a specific status.

FROM DATE/TIME The earliest date and time (YYMMDD HHMMSS) to be included. For segments in development status, this date and time applies to the install window. For installed segments, it applies to the installation date and time.

TO DATE/TIME The latest date and time to be included.

(Enter) PANEL(S) WITHIN SELECTED CHANGE CRITERIA.

Use this panel to select the set of changes to be displayed. When the options are selected, ENTER causes a display of the selected changes. For further detail, select the PROCESS or STATUS panel for the change segment.heidi

_________________________________________________________________________________



SECTION 6 - APPROVE

6.1 Change Approval

The segment must be in READY status prior to approval.

After the APPROVAL action, further modification of change elements is impossible. However, developers with READY authority can revert the segment to DEVELOPMENT status, to enable specific elements to be modified. If this action becomes necessary, approved elements remain in APPROVED status. This means that when the segment is again readied, only those elements that have been changed by the developers need be subjected to the review process.

NOTE: See PDX System Administrator Guide.

From the PDX primary menu panel, access the change status panel. Then modify the status field to "A". You should see message "STATUS UPDATED" and the history section below will show your userid and the date and time.

_________________________________________________________________________________



_________________________________________________________________________________



SECTION 7 - INSTALL AND BACKOUT

7.1 Overview

Changes may be installed only by authorized persons and must be in APPROVED status.

When the INSTALL command is entered, PDX submits a batch job - PDXINS. The program uses the PDX data base to determine,

• Which elements will be installed (copied to production libraries)

• Name and type of each library (MVS, PDS, or Librarian)

When the batch install is complete, the change enters Installed Status.

NOTE: See PDX Administrators Guide.

From the PDX primary menu panel, access the change status panel. Then enter the INSTALL command in the command window and ENTER.

7.2 Change Backout

PDX backs out a change by segment. When a change must be removed from production, all related elements of that change are removed at the same time. Enter "BACKOUT" on the STATUS panel to effect a backout of the change segment.

7.3 Remote Site Install

Change segments may automatically be installed at a remote site. For example, if a backup copy of all changes is required at an alternate site, an application may be flagged such that all of its changes, unless overridden by the installer, are installed at the remote site. When the INSTALL command is issued, and the status of the BRP site is AUTO, the system will change the RMT status to PEND. Once the segment is successfully installed at the remote site, the status will be changed to INST.

_________________________________________________________________________________



_________________________________________________________________________________



SECTION 8 - ENTITY ATTRIBUTES AND RELATIONSHIPS

8.1 Option E - Update or Translate Entities

When Option E UPDATE OR TRANSLATE ENTITIES is selected on the PDX Primary Menu panel, the following panel is displayed:

Figure 8(A). Process Library Elements Panel

Enter the following required data:

LIBTYPE - Library Type MEMNAME - (At least one prefix character) CLSTNAME - (Required if Translate Element selected)

When the list of entities is presented, enter one of the following action codes:

FIELD DESCRIPTION____________ _______________________________________________________

BLANK Display Member List

T Translate Element (translation command)

H History Data for Element (History panels)

R Relationship Data (Relationship panels)

_________________________________________________________________________________



8.1.1 Updating Relationship Data Online

Any element that has been defined to the system may have relationship data. These data may be updated by using the "R" line action when the member list is displayed by the above panel. For each member that "R" is entered for, the current relationship information will be displayed. This panel shows one line for each related element, with the types as follows:

01 Required Relation. This means that if the element is in a segment, the all related elements must also be in the same segment.

02 Active. This code means the element may be in a segment or not, depending on whether the "R" line action on the process panel has been used.

Relationship data can also be updated automatically using the XREF command on the Process panel.

8.1.2 Using the XREF Command

Relationship data for a segment may be updated using the XREF command. (In your installation, this may be performed automatically by the READY command.) Enter XREF on the process panel and a batch job will be submitted to update the relationships. You must have "UPD" or "RDY" authority to perform XREF.

8.1.3 Updating Relationships Externally

PDX provides a batch program, AUTXR1, that accepts cross-reference input data (which may be from a PDX-supplied utility or a user-supplied utility) and updates entity relationships accordingly. Contact your administrator to update relationships in this manner.

_________________________________________________________________________________



SECTION 9 - ARCHIVE AND RETRIEVAL

9.1 Segment Archive

On a weekly cycle (or other installation-determined cycle), the segments that were installed during the period prior to the current ending period are copied to tape and merged with other installed segments. After successful merging of the archived segments, the disk datasets, including the journal dataset, are deleted. This means that archived segments are no longer available for on-line (immediate) backout, FETCH or on-line access outside PDX. Retrieval of archived segments is accomplished by using the program AUTRTC. This is a batch program that will restore one or more libraries from one or more archived segments from tape to disk.

9.2 Effect of Archive on Segment Backout and Fetch

Prior to archive, all of the libraries associated with an installed segment are still available on disk. This means that if a subsequent change is made to a module and then the subsequent change is backed-out, PDX can obtain the prior version from the first segment without requiring a tape mount. This also means that the FETCH command can obtain a version of a module from an installed segment at any time before archive. (Fetching from an installed segment would be an unusual procedure. Normally, a module would be obtained from the production version).

9.3 Segment Retrieval

Once segments have been archived, they may be retrieved by executing the batch program AUTRTC. This program will retrieve one or more segments in a single pass through the archive tape. An entire segment may be retrieved, or one or more libraries of a segment may be retrieved. When a prior version of a module is needed, the PDX on-line module history panel may be used to determine the segment number that corresponds to each prior version. When segments are restored, the datasets are named as follows:

{system-prefix}.GGGAAA.Rnnnnnnn.{libtype}

where GGG is the group-id and AAA is the application-id for the original segment. Note that an "R" is used in place of the usual "C" in the segment number portion of the dataset name. If datasets in this format are pre-allocated prior to execution, PDX will use them. Otherwise, PDX will dynamically allocate the requested libraries. Pre-allocation is advised for segment libraries that contain a large number of members, because default allocation factors are used for dynamic allocation.

To execute AUTRTC, use the following job control:

//jobname job (xxx)//stepname EXEC PGM=AUTPGM,PARM=(AUTOFF,AUTRTC)//SYSPRINT DD SYSOUT=*//AUTPRINT DD SYSOUT=*//AUTERR DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD UNIT=SYSDA,SPACE=(80,(1,1))//AUTOUT DD UNIT=SYSDA,SPACE=(19069,(100,100))//SYSUT4 DD UNIT=SYSDA,SPACE=(CYL,(5,5))//AUTCTLCD DD *NNNNNNN LLLLLLLL/*

The control cards contain the segment number to be retrieved in columns 1-7 and the (optional) library type in columns 9-16. If the library type is omitted, the entire segment is retrieved. There is no limit on the number of control cards that may be used, and the control cards may be presented in any sequence.

_________________________________________________________________________________



For large libraries, the AUTRTC utility allows pre-allocation of the receiving dataset.

9.4 Non-Install Feature

Use Non-install to create documentation. This feature enables Library Types to be archived rather than installed and archived.

To use: Required Member LIBTYPE is CHGDOC1 or another special LIBTYPE determined by your installation

Example: PDXDOC CHGDOC1 ASIS

NOTE: These records are archived to tape at Install time.

_________________________________________________________________________________



SECTION 10 - RELEASE-CONTROL SEGMENTS

Release control processing allows change materials to be staged in multiple PDX segments. For example, unit testing can be performed in one or more "smaller" segments and materials "promoted" to a target acceptance/regression testing segment when unit testing is complete and when acceptance testing personnel are ready to receive new unit-tested versions. This feature is especially useful for installation of large application software releases, but may be employed whenever useful. This section describes how to define and use release control segments.

10.1 Defining Release-Control Segments

Release control processing is activated when the "release-id" field of the status panel is non-blank. Other related fields on the STATUS panel are:

RELEASE-ID X(8) The identification of the release to which this segment relates. Must conform to ISPF "name" validation. In particular, the first character must be alpha.

RELEASE-SEGMENT-TYPE X(1) D = DevelopmentA = Acceptance

RELEASE-TARGET-SEG 9(7) The segment to which members will be promoted upon execution of the PROMOTE command. Must be 7 digits numeric.

RELEASE-TARGET-TYPE X(1) The segment type to which members of this type will be promoted upon execution of the PROMOTE command. May be "A" for further acceptance segment or "P" for production.

10.2 Using the Release Identification on Fetch

When FETCH is executed, information about other releases in progress is shown. This allows easy identification of the release to serve as the base for a change and helps avoid errors. The fields displayed are RELEASE-ID AND RELEASE-SEGMENT-TYPE.

10.3 FETCH Required on First Access

In "release-control" segments, a module that already exists in production or in another development segment must be FETCHed (as opposed to IMPORT or EDIT/COPY access). This ensures an "official" copy is obtained upon which to base changes.

For members that already exist in production or in another segment, all "line-actions" on the process panel are inhibited until the member has been fetched. Until the fetch is performed, ISPF message "INITIAL FETCH NOT COMPLETED" will be displayed if a line-action is attempted. The cursor is positioned on the offending line.

To perform FETCH in a release control segment, use the normal procedure described in Section 4.3. Once the job finishes, the "locks" on the entity in the segment are freed.

10.4 Promote Selected Elements to Acceptance

This function allows automatic copying of selected entities from the development segment into the

_________________________________________________________________________________



acceptance segment, without the need to re-compile. PDX checks the integrity of library and entity relationships during the promotion.

To promote an element, use the "P" line action on the PROCESS panel. This action "marks" the member for promotion and freezes the member in the development segment. If an element is marked "P", then any 1-1 or "K" library-related members with the same name will also be marked. Any members with a PDX entity relationship "1" or "2" will also be "forced". The "Q" line is used action to "un-mark" a member. This line action also observes library and entity relationships.

The PROMOTE command submits a batch program that copies the "P" members from the present segment to the RELEASE-TARGET-SEG segment. The batch promote program defines the elements in the target segment (if not already defined), copies the materials to the target segment staging libraries, and "unfreezes" the entities promoted in the development segment.

At this time, there is no "backout" for the promote function. To achieve backout, entities must be manually deleted from the acceptance segment. A future release will provide a backout facility. The VERIFY command ensures integrity of the acceptance segment.

10.5 Create "Install Units" from Acceptance

This feature allows selection of specified elements from the acceptance segment to create separate segments for the items selected, making sure that all of the items have been selected.

To create an install unit, enter a line action from 1 to 9 on the process panel in the acceptance segment. Line action 1 indicates that the selected entities are to be "split" into install unit number 1, etc. Items not selected (blank) are also considered an install unit.

If an entity is marked "1-9", then any 1-1 library-related members will also be marked. Any members with a PDX entity relationship "1" or "2" will also be "forced". The "Q" line action "un-marks" an entity. This line action will also observes library and module relationships.

The MAKEUNIT command submits a batch job to create an install unit. The format for the command is:

MAKEUNIT {x},

where x may be omitted or a number from 1 to 9. If omitted, the "blank" entities in the segment are indicated; otherwise the entities marked with the matching number are indicated.

When the command is executed, new batch program is submitted that copies the selected entities to new segment for each indicated entity. The new segments will be marked as "install units" and will contain the original segment as the "from" segment for the install process.

10.6 Report on Non-Installed Elements (Review Panel)

The PDX REVIEW panel (Option 5 from the primary panel) provides a warning for any segment that is part of a change that has not been installed whenever another segment in the same change has been installed. This "reminds" the installers that one or more "install units" have not yet been installed (i.e., a release is only partially installed).

_________________________________________________________________________________



_________________________________________________________________________________



SECTION 11 - DELTA PROCESSING

PDX delta processing provides online access to deltas between levels of entities under PDX control and online access to the text for prior entity levels. Each time an entity is installed, a new "level" is created. The first install of an entity is level number 01 and each subsequent install creates a level one higher than the previous. "Deltas" are text entities that represent the differences between one level of an entity and another. During development, deltas are created that represent the differences between the "basis" level (either production or another change in progress) and the changed level. The PDX install process stores deltas that represent the differences between the level being installed and the current production level.

To activate this feature, the PDX administrator determines which library types are to be eligible for delta processing and updates the production library administration panel. For designated library types, deltas are automatically created as changes are prepared for installation. The feature supports entities in PDS or PDSE format. Load module library types are not supported.

11.1 Access to Deltas and Text Entities at Different Levels

During development, developers can view a list of prior levels of production entities and, if required, import these entities into current development segments. During change review and approval, administrators may review proposed delta changes to current production entities. Deltas are also available for online browse or for program access by auditors.

Access is gained to prior or future deltas for an entity via the ENTITIES option (Option E from the PDX primary panel) or by using the new "H" line action on the Process (Option 8) panel. The "H" (History) line action on either panel allows access to the list of existing deltas. (For transition ease, the old "F" action code on the process panel will perform the same function as the "H" line action.) For both access paths, a panel is presented that contains a scrollable area with current delta information. The scrollable list is presented in chronological order. The list contains new levels (changes in progress for this entity), the current (production) level and all prior levels (even if the number of prior levels exceeds the installation maximum number of deltas to be stored and the delta has been archived). When the panel is presented, the cursor is on the current production entity with the default "F" action code. If ENTER is depressed, the entity will be FETCHed into the current segment.

The scrollable portion of the panel presented for the FETCH process or for ENTITIES provides the following options:

AC Action Code (See details below).LVL Level Number of the entity (See discussion of level numbers below).VER Version number for the entity (documentation only).RELEASE Release identification ("Release Control" segments only).CHANGE PDX change control number.SEGMENT PDX segment that installed or is working on the entity.DATE Date of install (forecast or actual).TIME Time of the install (forecast or actual).FTCHFRM If the entity has been fetched in an active segment, "PROD" is displayed if the fetch

was from production. Otherwise, the segment from which the fetch was made is displayed.

REM System-generated remarks about the level:

ARCHIVED Delta has been archivedFP Entity was fetched from ProductionFC Entity was fetched from another changePROD This is the production levelBAD FTCH Fetch chain does not match forecast install dates

Changes in progress are displayed above production; install changes are displayed below production.

_________________________________________________________________________________



In the case of changes in progress, the sorting date is the "install after" date on the Status panel in the Install Windows section. For current and prior installed levels, the sorting date is the date the level was installed.

When the entity history screen is presented, the cursor defaults to the "PROD" line with the default "F" action code. Action codes on this panel are:

B Browse Deltas. The delta is presented in TSO Browse.F Fetch. The text of the entity is copied into the staging library. Note: The "F" action

code is valid only for the current level or "plus" levels--changes in progress. Use import to acquire earlier levels.

V View Text. The text for the level requested is presented in TSO Browse. For production or "plus" levels, the text is obtained from the appropriate library. For "minus" levels, the text is reconstructed backward from the production text using as many delta levels as necessary.

I Import Text. Text for a "minus" level is copied into the staging library. Standards level is set to "9". Note: The "I" action code is not valid for "fetchable" levels. Use "F" to acquire the current production or a level with a change in progress ("plus" level).

X Export Text. Text is copied to an external library.S View Status Panel.P View Process Panel (list of entities in segment).

The Fetch and Import Text options are available only when the panel is invoked from within an active segment (via the Fetch line action on the Process panel). When Import is invoked for a prior level, the prior level is constructed and stored in the development change segment staging library. The standards level for the entity is set to 9 (non-standard), reflecting the extraordinary nature of the action. Fetch warning logic remains active if a fetch has already been performed. For the Export action, a second panel is presented, prompting for the dsname of a PDS into which the entity is to be exported.

11.2 Level Number and Version Number Assignment

For changes in progress, the level numbers displayed are assigned based on the "fetch chain" or the forecast date of install. For example, if the entity was fetched from production and production is level 05, its level number will be 06. If the entity has been fetched from a change in progress with level number +07, its level number will be +08. If a discrepancy exists between the forecast install date and the "fetch chain", a warning message ("Bad Chain") will appear under remarks.

Level numbers for production entities may be modified on the history panel (Option 8, line action H) by an authorized individual. Level numbers are from 00 to 99 numeric values only. During change development, level numbers are recalculated and the source member in the staging library is updated every time a module is compiled. At change install time, deltas and level numbers are both re-calculated. The source is then re-generated from the deltas and level numbers re-assigned. The regenerated source is compared to the source in the staging library excluding columns 73-80 (and 1-6 for COBOL) and if not identical, the install is prevented. Otherwise the regenerated source is stored in the staging library, replacing the member already there, and then the usual install is performed. This process ensures that the text, the deltas and the level numbers for installed entities are correct regardless of the installation sequence.

Provision is made to assign version numbers (000-999) to entities. The version defaults to 001 and may only be changed using the history function by an authorized individual. The version number appears in IBM's EDIT window as VVV.LL, where VVV is the version and LL the level for the member. The version number is not used by PDX and is for documentation only.

11.3 Prior Level Delta Storage After Archive

Deltas are installed along with the installation of production entities. At archive time, they are installed into a single PDX VSAM file, with a key identifying the entity and its level. Each installation of the same entity into production creates a new level and a new delta for that entity. The maximum number of deltas to be stored

_________________________________________________________________________________



online for a each library type is controlled by the System Administrator.

The archive process stores deltas in a VSAM KSDS dataset. The fields of a delta record are:

LIBTYPE PDX library typeMEMNAME Member nameINSTDATE Latest production install dateINSTTIME Latest production install timeLEVEL PDX member level numberVERSION PDX version numberRELEASE PDX Release IdentificationSEGMENT PDX segment numberPDXSEQ PDX source record sequence numberTEXT Text of the member

INSTDATE and INSTTIME are negative signed so that the most current level is first in the file. LEVEL is the number of this delta (when a production entity is first changed, delta number -1 is created, etc.). PDXSEQ is a PDX-generated sequence number (0-n) for each record of this level. Record zero is a PDX header record. The text field contains the "delta" images, which are formatted in SUPERC relative format at PDX install time.

A maximum number of levels may be set for each LIBTYPE using the Production Library Administration Panel (Option 6.2). When the maximum is reached, the weekly archive process copies all records for the oldest level to the Delta Archive file and erased. One record is left on file with PDXSEQ=0 and the text field set to "ARCHIVED on yyyy/mm/dd".

Delta libraries are protected via the host security system (and PDX privileged program access) in the same manner as are production libraries. Developers may not access delta libraries for update.

11.4 Production Level Source Storage

The current production source member is stored in its "native" format and library type. Columns 79-80 of current source records contain nn, where nn indicates the "level" (PDX delta number) from which the record was obtained. Developers should not place data in columns 76-80 when editing source entities in "delta" library types. The "construct prior level" functions (line actions "V", "I" and "X" on the entity history panel) start with the current production level and work backwards.

11.5 Delta Storage in Staging Libraries

Deltas are stored in change segment libraries in parallel with source members. A language translation must be performed prior to the READY command for all entities in library types with the delta attribute. Developers should not place data in columns 76-80 when editing source entities in "delta" library types. Any data placed there will be overridden when a source translation is performed. If the source translation is somehow bypassed, the install program will overlay such data, placing the correct level number in 79-80. All entities in delta libtypes must be translated prior to the READY command, even "ASIS" process types.

The delta create process is a COBOL program that invokes SUPERC to create delta images. SUPERC processing is relative. This means that input sequence numbers are ignored. Current language types supported are COBOL, with sequence numbers in columns 1-6 and STANDARD, with sequence numbers in 73-78. Note that columns 79-80 are reserved for the PDX level number.

11.6 Installation of Delta Images

The delta create process runs as a separate job step prior to the install program. The delta create program receives the segment number as an input parameter and interrogates the "PLIB" record (A.P panel data) for each library type about to be installed and a new delta is created for each member of each delta library type. This delta is compared against the delta in the change segment staging library, and a warning message is

_________________________________________________________________________________



provided if there is a difference. The program then reconstructs the new source from the current source and the delta, and ensures that replaced or inserted records have the new level number in column 79-80. Old level numbers are copied from the current source member. The reconstructed member is compared against the new source in the staging library, ignoring columns 73-80 (and 1-6 for COBOL). If any differences are detected, a severe error message with return code 16 is issued, so that the install step will not run. If there are no differences, the reconstructed source is stored in the staging library replacing the existing member.

The delta entities themselves are installed into production libraries in the normal manner. This means that production libraries for delta images must exist. At archive time, deltas are copied from the staging library into the permanent VSAM storage file just before the staging library is deleted.

11.7 Backout of Delta Images

When a segment is backed out, the delta images are backed out in the normal manner, like any other PDS or PDSE entity. Once the delta is copied to the VSAM file, it may no longer be backed out.

11.8 Restart - Backup - Recovery

The entire install process (both job steps) may be restarted any number of times. The system replaces any existing deltas created by a prior run. Backups for delta libraries are the user's responsibility, but the PDX forward recovery process (if job control for the delta step is provided) also recovers the production delta libraries. The VSAM delta file should be backed up just before and/or after the archive step that updates it.

11.9 Merge (Future Upgrade)

This upgrade will allow automatic merging of two levels to create a third. This feature, for example, allows an emergency change to be automatically merged into a change in progress. The option to merge will be presented during FETCH warning resolution processing.

11.10 Delta Editing in Staging Libraries (Future Upgrade)

This upgrade will allow for optional editing of deltas (instead of full source decks) in change staging libraries. With this feature, developers may elect to EDIT the delta member instead of the full source member. The language processing CLISTs or REXX EXECs are set up to create the merged source from the basis member and deltas prior to language translation.

_________________________________________________________________________________



Appendix A - Library Types and Relationships

LIBTYPE PRODUCTION LIBRARY RELATED RELATIONLIBTYPE TYPE

SRCE PROD.STD.SOURCE LOAD 1COPY CDBRM KSRCED D

LOAD PROD.STD.LOAD SOURCE 1SUBS PROD.STD.SUBSRCE OBJECT 1

COPY CDBRM K

OBJT PROD.STD.OBJECT SUBSRCE 1DBRM PROD.STD.DBRM -BCTL PROD.STD.DB2CNTL LOAD 1CCPY PROD.STD.CICSCOPY COPY 1

The libraries shown above are samples. Your system administrator will provide you with a list of production libraries and the use for each library type. Also, you may review the library types and the associated production library name by entering the administrative option and selecting the production library panel.

The relation type codes in the example have the following meanings:

1 One-to-one. If an element exists in a segment and the translation procedure is not "ASIS", then the element must also exist in the related libtype.

C Copy code. If a language translation is performed and the related libtype is found in the segment, then it will be concatenated to the compiles done.

D DBRM. DB2 Data Base Resource Module.

K Return Code. If a translation is performed and the return code is within the global or application threshold, then the return code of the related member with the same name will be set to zero.

L Delta Library. The deltas for this libtype.

O Object module library. In a link-edit, if the related object library is present in the segment, it is concatenated to the SYSLIB ddname.

S Subroutine. The source code contained in this library is subroutine source. A link-edit is not performed. The object module is placed in the related object library.

_________________________________________________________________________________



Appendix B - CLIST Procedures

The PDX System stores a CLIST procedure for each procedure required to transform a 'SOURCE' element into a 'TARGET' element. Examples are Compile, Link Edit and IMS/CICS Tables. Grouped For User convenient reference by Category, procedures presently available are as follows.

ASSEMBLER

ASMH - Assemble

COBOL (CAPEX OPTIMIZER)

COB2 - Compile COBOL batch programsCICC - IMS COBOL CompileCB2C - Compile COBOL command level CICS CICI - Compile COBOL command level CICS program including

IntertestCOBS - Compile batch SubroutinesCOBI - IDMS COBOL compileCPSP - CPCS COBOL compile

JOB CONTROL LANGUAGE (JCL)

JCLS - Scan JCL for errors

MSA APPLICATIONS

These procedures use the MSA utility to extract source code from the MSA VSAM SPL source library, apply the delta changes and pass the merged deck to the language processor.

MASM - AssemblyMCBL - COBOL CompileMCPY - Set up COPYLIB MembersMREO - Reorganize SPLMSIS - Move 'ASIS' for MSA SourceZMLK - Link-Edit for MSA Modules

OTHERS

TRAN - Translate using database entity attributesASIS - No action, the element is processed as is MAP - CICS/BMS GensLINK - Link only for composite Load ModulesCPRS - Compress PDS Dataset

_________________________________________________________________________________



Appendix C - Batch Messages

The following messages may result when a batch CLIST process is performed (Compile, Link, etc.).

PDXCN0031 START CHANGE=XXXXXXX USERID=XXXXXXXX

PDXCN0041 SEND CHANGE=XXXXXXXX USERID=XXXXXXXX

PDXCN005E ***ERRORS ENCOUNTERED***One or more errors, other than errors in the Compiler or other Language Processor were

encountered. See above messages for explanation.

PDXCN008E XXXXXXXHAS ALREADY BEEN APPROVEDA CLIST process cannot be performed for a Change in APPROVED status.

PDXCN009E CMEM RECORD NOT FOUNDSerious data base error - contact Support Programmer

PDXCN012E XXXXXXX IS IN FROZEN STATUSA CLIST process cannot be performed for a change in frozen status.

PDXCN015E JOBLIB, STEPLIB, JOBCAT AND STEPCAT NOT PERMITTEDThis error indicates the online system was not used to submit the install. Possible security violation.

PDXCN016E XXXXXXX HAS BEEN BACKED OUT

PDXCN017E XXXXXXX IS ALREADY INSTALLED

PDXCN018E CLIST NOT EXECUTED BECAUSE THERE WAS A PRIOR ERROR

PDXCN019E XXXXXXXX NOT AUTHORIZED

PDXCN020I CLIST RETURN CODE =

PDXCN024I CLIST - (CLIST record)

PDXCN025E CLIST MEMBER ___________NOT FOUND

PDXCN029E DATASET NOT AUTHORIZED

PDXCN030W NON-STANDARD MEMBER PREFIX

PDXCN0331 NO ERRORS ENCOUNTERED

PDXCN042E STATUS RECORD NOT FOUNDA serious data base error - contact Support Programmer

_________________________________________________________________________________



Appendix D - Online Messages

Messages which may appear on the screen are as follows.

AUTZ001 REQUIRED FIELD The field at the cursor position is required to continue. AUTZ002 MUST BE NUMERIC The fiels at the cursor position must be numeric. AUTZ003 INVALID VALUE The field at the cursor position is not valid. Use HELP for a list of valid values. AUTZ004 INVALID SELECTION You must chose one of the listed values. AUTZ005 USER NOT AUTHORIZED You are not authorized to perform this function. AUTZ006 CANT ALLOC AUTH FILE The authorization file cannot be allocated. Capture the information printed or displayed and contact your administrator. AUTZ007 CANT ALLOC JRNL FILE The journal file for this segment cannot be allocated. Capture the information printed or displayed and contact your administrator. AUTZ008 CANT ALLOC CNTL FILE The control file for this segment cannot be allocated. Capture the information printed or displayed and contact your administrator. AUTZ009 CANT ALLOC DATA BASE The database cannot be allocated. Capture the information printed or displayed and contact your administrator. AUTZ0010 INVALID LENGTH Field must be as defined on panel. AUTZ010 INVALID LENGTH Field must be as defined on panel. AUTZ011 DB VSAM ERROR Cannot read/write vsam file. Cobol file status is shown. Capture the information printed or dispalyed and contact your administrator. AUTZ012 CHANGE DEFINEDYour change has been defined - you may allocate change libs. AUTZ015 CANT DEFINE PANEL VARIABLES An ispf VDEFINE command has failed - contact program support. AUTZ016 ENTER VOLSER OR UNIT Please enter either a volser or a unit value. AUTZ017 CANT ISSUE ISPF VGET ISPF VGET FAILURE - contact support programmer. AUTZ018 CANT ISSUE ISPF VPUT ISPF VPUT FAILURE - contact support programmer.

_________________________________________________________________________________



AUTZ019 LIBRARY ALLOCATED Your library has been allocated and may now be used. AUTZ020 INVALID LIBRARY TYPE The library type you entered is not valid. A valid list may be viewed on the administrator production library panel. AUTZ021 DUPLICATE DATASET NAME This dataset name is already in the catalog. AUTZ022 CANT READ DATABASE An I/O error has occurred. Contact support programmer. AUTZ023 SEGMENT NOT ON FILE This segment is not defined in the data base. AUTZ024 ENTITY NOT FOUND The entity &LIBTYPE &MEMNAME is not in the database. AUTZ025 ALLOCATION FOR &DD FAILEDProbable duplicate dataset name. AUTZ026 JOB SUBMITTED Your job &JOBNAME has been submitted. AUTZ027 SEGMENT STATUS INVALIDSEGMENT status &STATUS invalid for action attempted. AUTZ028 ISPF SELECT FAILURE ISPF select failure - contact support programmer. AUTZ029 STATUS RECORD NOT FOUNDUse CONTROL function to establish new segment.

AUTZ030 DATABASE UPDATED The database has been correctly updated. AUTZ031 STATUS UPDATED SEGMENT &NNNNNNN has been updated to &STATUS status. AUTZ032 INVALID ACTION Action must be either V OR E. AUTZ033 REC FORMAT INVALIDOnly FB, VB OR U format supported. AUTZ034 CANT START DATABASEDatebase error; COBOL status = &XRC. AUTZ035 ISPF TBSORT ERROR ISPF TBSORT RETURN CODE =&XRC; contact administrator. AUTZ036 ISPF TBCREATE ERROR ISPF TBCREATE RETURN CODE =&XRC; contact administrator. AUTZ037 ISPF TBADD ERROR ISPF TBADD RETURN CODE =&XRC; contact administrator. AUTZ038 ISPF TBMOD ERROR

_________________________________________________________________________________



ISPF TBMOD RETURN CODE =&XRC; contact administrator. AUTZ039 INVALID LINE ACTION Line Action must be "A"(ADD),"C"(CHANGE),OR "D"(DELETE). AUTZ040 SEGMENT NOT APPROVED YET Segment must be in approved status to be installed. AUTZ041 SEGMENT NOT READY Segment must be in ready status to be approved. AUTZ042 CANT OPEN DATABASE COBOL VSAM STATUS = &XRC; contact administrator. AUTZ043 INVALID COMMAND Command not recognized - consult user manual. AUTZ044 SEGMENT READY Your segment is now in ready status. AUTZ045 ENTITIES NOT ALL OK PDX is unable to READY the segment; one or more entities has a non-zero return code. AUTZ046 LIBRARY COMPRESSED Your library: &LIBTYPE has been compressed. AUTZ047 COMPRESS ERROR Dataset not compressed. Use extended help to capture dynamic allocation return code and contact administrator. AUTZ048 LIBRARY DELETED Your library: &LIBTYPE has been deleted as requested. AUTZ049 NOT DELETED You exited without deleting the library: &LIBTYPE. AUTZ050 DELETE ERROR Dataset not deleted. Use extended help to capture dynamic allocation return code and contact administrator. AUTZ051 CANT START AUTH FILE VSAM COBL return code = &XRC; contact administrator. AUTZ052 CANT OPEN AUTH FILE VSAM COBL return code = &XRC; contact administrator. AUTZ053 CANT READ AUTH FILE VSAM COBL return code = &XRC; contact administrator. AUTZ054 CANT WRITE AUTH FILE VSAM COBOL return code = &XRC; contact administrator. AUTZ055 NO MEMBERS TO BACKOUT No members were found in the segment to be backed out. AUTZ056 BACKOUT SEGMENT TOO EARLY Segment to be backed out was installed before the next to latest archive. Backout does not work for "old" segments.

_________________________________________________________________________________



AUTZ057 SUBSEQUENT SEGMENT FOUND An entity of the segment to be backed out was modifed after the date of the install. Segments whose entities have been subsequently modified cannot be backed out. AUTZ058 CANT READ ENTITY A DB I-O error has occurred with COBOL VSAM RC=&XRC. AUTZ059 CANT WRITE BACKOUT RECORD A DB I-O has occurred with COBOL VSAM RC=&XRC. AUTZ060 SEGMENT NOT INSTALLED The segment must be in INSTALLED status to perform backout. AUTZ061 CANT READ CHANG REC VSAM COBL return code = &XRC. AUTZ062 CANT FIND PROD LIB LIBTYPE for produciton library not found. Check the spelling of the library type you entered. Then check the PDX administrator production library panel. If the spelling is correct and the library type appears on the panel, contact your support programmer. AUTZ063 BACKOUT JOB SUBMITTED A new backout segment whose segment number has a high-oder digit has been stored in the databas to control the backout of the segment selected. The backout job has been submitted. AUTZ064 CANT SUBMIT BACKOUT The ISPF SELECT command to submit the backout failed. AUTZ065 BACKOUT NOT COMPLETED The EXIT PF key was used to terminate the backout process. AUTZ066 CANT READ INFO NUMBER A database I/O error occurred reading the INFO CNTL number. AUTZ067 CANT READ CONTROL RECORD A database I/O error occurred reading the control record. AUTZ068 CANT WRITE CONTROL RECORD A database I/O error occurred writing the control record. AUTZ069 CANT WRITE INFO NUMBER A database I/O ERROR occurred writing the INFO CNTL NUMBER. AUTZ070 FETCH COMPLETED Entity &MEMNAME was fetched to segment &CHANGID. AUTZ071 CANT COPY TO SAME SEGMENT You must fetch from production or another segment. AUTZ072 RECORD NOT FOUND Database record not found for &LIBTYPE &MEMNAME. AUTZ073 ENTER NEW DATA Record not of file; you nay now enter new data to update database. AUTZ074 FETCH WARNING One or more entities changed after a fetch was completed. Determine whether to ignore the changes or to incorporate them into the entity you are working on. AUTZ075 INITIAL FETCH NOT COMPLETED

_________________________________________________________________________________



You must perform a fetch before this action. AUTZ076 BASE COPY PENDING The base copy has not been completed. Fetch the module again and if the error persists, contact your administrator. AUTZ077 MUST USE DELT CLST Use the DELT CLST with "D" function to delete from production. AUTZ082 CANNOT BUILD TABLE Unable to build ISPF table of entities for this panel; contact support programmer. AUTZ083 INVALID LIBRARY TYPE The libtype must exist on the administration panel. AUTZ084 INVALID EDIT TYPE You are attempting to edit a "TARGET" library type. AUTZ085 EDIT ERROR Unable to edit this member--check allocation and fetch/import. AUTZ086 BROWSE ERROR Unable to browse this member--check allocation and fetch/import.

AUTZ087 INVALID OVERRIDE The override action ("K") is invalid for this libtype. AUTZ088 MIXED IMPORT/EXPORT You can only perform "I" OR "X" actions, not both at the same time. AUTZ089 MIXED IMP/EXP LIBTYPES You cannot import/export multiple members of different libtypes.

_________________________________________________________________________________



Appendix E - Librarian With PDX

1. Translate CLISTS

In using Librarian, the basis library is,

• Production Source Library, if it is a new Change

• An existing Change Library, if a module is being added or replaced

Each Segment ha a Librarian file, if it contains updated Source that will be moved to Production Library at Installation.

PDX Librarian Preprocessor,

• Reads the Member and ensures that appropriate control cards exist

• Generates the -ADD or -SEL card

• For the -SEL card, copies the Source from the basis Library to the Change Library

The update to the Source is permanent. Therefore, each time a Translate executed it,

• Copies the Source from the basis library

• Applies the changes indicated by the control cards

• Updates the Change Library 2. Adding a New Module

(-ADD Generated by PDX)

The following control cards are required at the beginning of the Source: -LANG xxx (xxx = language (COB, ASM) -PGMR yyy (yyy = Programmer Name (14 characters, no blank) -DESC zzz (zzz = Program Description (30 characters)

For Source added ASIS, PDX default is -SEQCHK (Source is not resequenced). For all other Source being added, PDX default is that the Source is assigned new sequence numbers

in the appropriate columns.

3. Updating an Existing Module

(-SEL Generated by PDX)

Required updating control cards are:

-REP -DEL

-INS

4. Default Sequence Columns

Default sequence positions: COBOL: Columns 1 to 6

_________________________________________________________________________________



(starting with Sequence No. 000010, increment by 10) ASM: Columns 73 to 80 (starting with Sequence No. 000010, increment by 10) 5. Optional Control Cards

All optional control cards are required at the beginning of the Source (before any - REP, -INS, -DEL, or other Librarian updating control cards).

-LIST Generates listing of the Librarian Source

-SEQ /ss,nn,ii,mm/ Specifies that default sequence is to be changed to values indicated. (Can be used only when adding a Module.)

ss = Starting Column

nn = Column Length

ii = Sequence Number Increment

mm = Starting Sequence Number

NOTE: If Sequence Numbers are to be stored outside the Record, specify Starting Column 81.

Example: /81,6,10,10/

-SEQCHK Directs Librarian NOT to generate Sequence Numbers; use Sequence Numbers in the Source and check for their presence. (Can be used only when adding a Module.)

-RESEQ Specifies Source is to be assigned new Sequence Numbers. Overrides SEQCHK option (above). (Can be used only when adding a Module.)

-NAME xxxxxxxx Directs that information specified by xxxxxxxx will go in Columns 73

to 80 of the Data Cards being updated.

Note: When your module requires extensive changes or for some other reason it is not desired to use the delta deck approach, use the LEXT CLIST:

LEXT Major changes to a Source Module that needs replacement (REP ALL) of the module on Librarian, can be performed using a Librarian extract CLIST called LEXT. To use,

• Use Option 4.1 to define Change Element(s). Type Name, Libtype,

and the appropriate Translate CLIST and Change.

Example: SRCE COB2 C

• Type 'ALLOC' on Command Line, for each Libtype

• Translate the member on the Process Screen (Option 2), overriding the CLIST Name to LEXT. LEXT will extract the source member from LIBRARIAN and place in the Change PDS. (Produces Return Code 4094)

• Return to the Process Screen. Edit the member to add the -REP ALL

_________________________________________________________________________________



Librarian control card, plus any changes

• Translate the member to recompile the module

*** END ***

_________________________________________________________________________________



Adding a New Module...........................................................................................................70ALLOC9, 23Application Conversion.........................................................................................................23Approve..................................................................................................1, 4, 7, 10, 11, 13, 41APPROVED status.................................................................................................................43Authorizationglobal 13restricted..............................................................................................................................13scope 13Authorization Requirements.................................................................................................12Backout...............................................................1, 5, 7, 10, 11, 13, 19, 43, 47, 50, 58, 67, 68Backup ..................................................................................................................................1Batch Messages....................................................................................................................62Benefits..................................................................................................................................3BRP 43Change Approval..................................................................................................................41Change Functions.............................................................................................................3, 13Change Libraries.....................................................................................................................4CLIST Procedure..............................................................................................................27, 61CommandALLOC11BACKOUT..............................................................................................................................11COMPILE...............................................................................................................................10COPYCHG.............................................................................................................................11DEFINE {libtype}..................................................................................................................12INSTALL................................................................................................................................11LOCATE {libtype-prefix} {member-prefix}...........................................................................12OPTIONS...............................................................................................................................11PROMOTE.............................................................................................................................12READY..................................................................................................................................11SEGPRINT.............................................................................................................................12TRANS ...........................................................................................................................11, 12VERIFY..................................................................................................................................11XREF 11, 12CommandsINSTALL command................................................................................................................43PDXED {segment} {libtype} {member}..............................................................................12PDXTRAN {segment} {libtype} {member}..........................................................................12Compile, ................................................................................................................................4Composition...........................................................................................................................1Control..................................................................................................................................36Control Features.....................................................................................................................1COPY CHANGE......................................................................................................................23Default Sequence Columns...................................................................................................71Definei, 4-7, 9, 10, 12-14, 17-23, 27, 32, 34, 35, 38, 49, 65, 72Define Segments........................................................................................................4, 14, 38Delta Archive........................................................................................................................56DELTA PROCESSING.............................................................................................................53DEVELOPMENT status...........................................................................................................41Edit 4Element..................................................................................................................................5Export4Fetch 4, 9, 26-29, 35, 47, 49, 50, 53-55, 58, 68, 69Fetch Warning......................................................................................................................28History..................................................................................................................................39Import4Install i, 1, 5, 7, 9, 11, 13, 17, 19, 20, 28, 33, 39, 40, 43, 48, 51, 53-58,

62, 67

_________________________________________________________________________________



INSTALL command................................................................................................................43ISPF 12panels1Language Translation.....................................................................................................30, 36Translation Rules..................................................................................................................37Level Number..................................................................................................................53-57Librarian................................................................................................................ ii, 43, 70-72Librarian with PDX................................................................................................................70Library Types.........................................................................10, 21, 23, 36, 38, 48, 53, 57, 59Link 4Modules with Aliases.............................................................................................................32Non-Install............................................................................................................................48Online Messages...................................................................................................................64Optional Control Cards..........................................................................................................71Overview........................................................................................................i, 1, 9, 17, 25, 43PF Keys...................................................................................................................................6Primary Menu.......................................................................................................................14Process Library Elements................................................................................................27, 45Process Panel..............................................9-11, 20, 21, 25, 28, 30, 33-38, 46, 50, 51, 53, 55Program Function (PF) Keys....................................................................................................5Purpose............................................................................................................................1, 23Quick Overview......................................................................................................................9Ready 1, 3, 4, 7, 10-13, 19, 27, 29, 30, 34, 35, 41, 46, 49, 57, 66READY status........................................................................................................................41Remote site..........................................................................................................................43Responsibility...................................................................................................................6, 58Review.............................................................................1, 4, 5, 14, 15, 18, 39-41, 51, 53, 59Review Changes...................................................................................................................39Special Library Functions......................................................................................................23Staging Libraries...................................................................................................................22StatusSTATUS...................................................................................................................................4SummaryPDXCOMP.............................................................................................................................10System Access......................................................................................................................13System Administration Guide .................................................................................................iiSystem Programmers' Guide ..................................................................................................iiSystem Terms........................................................................................................................6Test 4Time Share Option................................................................................................................12Translate CLISTS...................................................................................................................70TSO 12Tutorial.........................................................................................................................5, 9, 14Updating an Existing Module................................................................................................71Updating Relationship Data..................................................................................................46Updating Relationship Data Online.......................................................................................46Version...............................................................................................21, 28, 30, 33, 47, 54-56Version Number...............................................................................................................54-56

_________________________________________________________________________________


program development extension · web viewuser manual winkler-davis san francisco, california (415)...

Documents