14 Work with the Software Versions Repository

This chapter contains these topics:

• Section 14.1, "About the Software Versions Repository (SVR),"

• Section 14.2, "About the SVR Screen,"

• Section 14.3, "Working with Repository Services,"

• Section 14.4, "Accessing Cross Reference."

14.1 About the Software Versions Repository (SVR)

Navigation

From Master Directory (G), choose Hidden Selection 27

From Advanced & Technical Operations (G9), choose Computer Assisted Design

From Computer Assisted Design (G92), choose Software Versions Repository

The SVR indicates what environments a requested member is located in and whether the environment is production or development. The SVR is used extensively for documentation and plays an important role in the JD Edwards World Design and Development tools.

• The Software Versions Repository Master (F9801) file is a master directory of all programs, files, screens, reports and copy modules.

• The Software Versions Repository Detail (F9802) file stores the member locations for each member master record.

14.2 About the SVR Screen

The upper fields of SVR identify the member and display the associated configuration items. The system stores this information in the Software Versions Repository Master (F9801) file.

The lower fields of SVR list the libraries in which the member is maintained. The system stores this information in the Software Versions Repository Detail (F9802) file.

Figure 14-1 Software Versions Repository screen

Description of "Figure 14-1 Software Versions Repository screen"

Field	Explanation
Member ID	The identification such as program number, file number, and report number that is assigned to an element of software. Screen-specific information The source file containing the source member. At JD Edwards World software, three source files reside inside the JDFSRC library. They are: JDECPY for copy modules JDESRC for other source code F98CRTCMD for precompiler commands
Description	The description of a record in the Software Versions Repository file. The member description is consistent with the base member description.
Function Code	Designates the type of object being defined. See User Defined Codes, system code '98', record type 'FN' for a list of valid values.
Function Use	Designates the use of the object. For example, the object may be used to create a program, a master file, or a transaction journal. Screen-specific information Indicates how the member is being used.
System Code	A user defined code (98/SY) that identifies a JD Edwards World system. Screen-specific information Designates the system number associated with the member. Use F1 in the field to view valid codes.
Reporting System	A code that designates the system number for reporting and jargon purposes. See UDC 98/SY.
Base Member Name	The RPG name associated with the particular object. For data files, enter the based on physical file. For physical and logical files, the name is the same as the physical file name. For join files, use the name of one of the physical files. Screen-specific information This field simply allows for logical grouping of members. For screens, reports, RPG programs, and CL jobs, this name is usually the RPG program name associated with a particular member. For logical files, this name is the physical file upon which it is based and is required.
File Prefix	A prefix associated with a particular system. The prefix is placed before the data dictionary data item name to give the field a unique name across J.D. Edward's World systems.
Maint/RSTDSP	A designation of the type of maintenance on a logical view. These codes are as follows: 0 – No maintenance; or the logical is created dynamically 1 – Immediate maintenance 2 – Delayed maintenance -- USE WITH CAUTION Also used for RSTDSP and DFRWRT on Display Files 1 – RSTDSP = *NO -- Use with OVERLAY. Do not use with PUTOVR/OVRDTA DFRWRT =*YES A – RSTDSP =*NO -- Same as above DFRWRT =*NO B – RSTDSP = *YES DFRWRT = *NO S – For Compiling SQL RPG and PLI programs
Omit Option	Designates records in Software Versions Repository file which are not included on new releases. These codes are as follows: H – Held from all releases X – Omit from all releases S – Omit Source from all releases O – Omit Execution Object from all releases
Generation Sev	Allows you to override the error severity level that determines when a compile will be terminated without completion. For example, if you enter 20, the compile will complete normally even though you have received errors of severity 19 or lower. If left blank, the command default is used for the type of program being compiled.
Copy Data (Y/N)	Indicates if a file and its data is copied into production. A value of N moves the file without data. When creating a production data library from JDFDATA, this field is used primarily by program P98102, Create Production Library.
Optional File	Valid codes are: Y – Designates a file as an Optional Data File if there are some situations where the file may not be needed at a client installation. The explanation of these situations can be found in the Generic Rate/Message information for that file for Generic Rate/Message Type 96/OF. All of these files that exist in a specified library can be listed in the Optional File Report on menu G9645. O – Designates that the file is designated for omission. Examples are compile files or special files like JD Edwards World User Profiles file. Screen-specific information Designates if the file may not be needed at a client installation. The explanation of these situations can be found in the Generic Rate/Message information for that file for Generic Rate/Message Type 96/OF. All of these files that exist in a specified library can be listed in the Optional File Report on menu G9645.
Common File	A file with a value of Y copied into the user's designated common library when the Create User Production Library job, P98102, is run.

14.2.1 What are the Navigation Functions?

The following functions facilitate navigating within the SVR.

Command Line

To use an IBM command line in SVR, choose JD Edwards World Command Line (F2).

Repository Services

To display information about repository services, choose Repository Services (F6).

Optional File Information

To access a listing of optional files for a specific system, choose Optional File Information (F8).

Automatic Reinquiry

Once the system accepts the changes you make to a member and clears the screen, you can inquire on that member by choosing Redisplay Previously Changed Member (F9).

Checklists

To display checklists, choose Checklists (F10). Use this table to create rate or message codes for certain JD Edwards World systems, including benefits, work orders, and product costing. Each system uses the Generic Rates/Messages table differently. Consult the system documentation for information about Generic Rates/Messages.

Member Category Codes

To use member category codes when developing custom code and using the SVR to track development, choose Member Category Codes (F13).

Member Parameters/Key List

To display information about member parameters/key list, choose Member Parameters/Key List (F14). This was developed to document file access paths. It is currently used only in the World Writer conversion process during upgrade, where the F98013 file must contain file keys.

Cross Reference

To cross reference information, choose Where Used (Cross Reference) (F15).

Position Cursor to Action Code

When you inquire on a member, the system positions the cursor in the subfile for the screen. To reposition your cursor in the Action Code field, choose Position Cursor to Action Code (F17).

Maintain Replacement Program Information

To display information about programs that replace obsolete programs, choose Maintain Replacement Program Information (F18).

Previous Member

To access the member stored before the current member, choose Previous Member (F19).

Next Member

To access the member stored after the currently displayed member, choose Next Member (F20).

Flowchart Programs

To graphically display the program flow of systems, choose Flowchart Programs/Illustrate File Models (F23).

14.3 Working with Repository Services

The SVR provides access to the other repository services within JD Edwards World.

Additionally, you can use the Edit function (Option 2) to modify source on a member.

To work with Repository Services

1. On SVR, choose Repository Services (F6).

   The Repository Services screen displays.

   Figure 14-2 Repository Services screen

   
   Description of "Figure 14-2 Repository Services screen"
   
   

2. Enter 1 in the field to the left of your selection.

3. Exit (F3) Repository Services without making a selection.

14.4 Accessing Cross Reference

Navigation

From the Documentation Services menu (G91), choose Object Cross Reference Repository

The Cross Reference is an index of objects that allows you to inquire on an object and display its relationship to other objects. For example, the Cross Reference displays all programs that use the F0101 file or all files that use data item AN8. The Cross Reference also shows flow charts and data models.

To access Cross Reference

On SVR, choose Where Used (Cross Reference) (F15).

• You may also access Cross Reference from SVR, the Data Dictionary, and User Defined Codes.

The following example displays every program that uses Address Book Master File (F0101).

Figure 14-3 Cross Reference screen

Description of "Figure 14-3 Cross Reference screen"

To use this facility, you must run the Cross Reference Rebuild.

14.4.1 About the Rebuild Cross-Reference Index

Navigation

From Master Directory (G), choose Hidden Selection 27

From Advanced & Technical Operations (G9), choose Computer Operations

From Computer Operations (G96), choose Rebuilds and Global Updates

From Rebuilds and Global Updates (G9642), choose Cross-Ref Index

The Rebuild Cross-Reference Index program uses the SVR to build the cross reference index. JD Edwards World has incorporated the benefits of the RPG IV programming language in both its application and its design and development tools. The Rebuild Cross-Reference Index program includes objects generated through RPG IV. Additionally, in the SVR you can access the cross reference for RPG IV using F15.

The Rebuild Cross-Reference Index procedure updates information necessary to use the cross reference search and menu flow chart (F23) facility. It shows relationships between programs and files, commands, and User Defined Code files.

• Rebuild the cross reference if you want the system to reflect your custom work in the cross reference and flow chart.

• Before submitting the Rebuild Cross-Reference Index, you must ensure that the Cross Reference files, F98001, F98002, and F98003 exist on your system.

  • Clear F98001/F98002/F98003 before a reinstall for quicker processing.

• If parameters are left blank in processing options, it reads the record from the SVR file for object and source library.

• If parameters are *LIBL it will pick up the current library list.

• If parameters are specified with libraries, it will only read those libraries.

• Rebuild of the Cross-Reference Index can take many hours (estimate 8 to 14). It is not necessary to perform the procedure so that your JD Edwards World software runs normally, therefore, run the procedure during off-hours of operation.

• JD Edwards World source library (JDFSRC) must exist on your system to run this rebuild.

Figure 14-4 Rebuild Cross Reference screen

Description of "Figure 14-4 Rebuild Cross Reference screen"

14.4.2 What You Should Know About

Topic	Description
Cross Reference screen is blank	You must run the Rebuild Cross-Reference Index program. The Rebuild Cross-Reference Index program does not clear the files, it adds to the file. If you have old data in the cross reference, you must clear the cross reference files first then run the Rebuild Cross-Reference Index program.
Disk space requirements for the Cross-Reference files	To locate the size of each file, enter the following command against the cross-reference files and their attached logical files: DSPOBJD and *SERVICE for Detail and *PRINT for output. Add the figures together. The files are approximately 500 MB or ¾ Gig. The file size varies depending on the number of custom program entries in the SVR and the release of JD Edwards World software over which the system builds the cross-reference.