16 Understand JD Edwards World Libraries
This chapter contains these topics:
16.1 What Libraries Does JD Edwards World Install?
After the software restore, the following three libraries exist. They are:
The source library contains source code. Within the JDFSRC library, JD Edwards World has three multi-member source files.
JD Edwards World specifies the source library (JDFSRC) with a library type of SRC.
For example, the object library that contains executable objects for your JD Edwards World software includes:
-
RPG programs (contain a prefix of P)
-
CL programs (contain a prefix of J)
-
Display files (contain a prefix of V)
-
Reports (contain a prefix of R)
JD Edwards World specifies an object library with a library type of OBJ.
This is a pristine data library that contains test data files for your JD Edwards World software.
16.2 About Your Library Environments
After installation of the software is complete, you must create an environment for the software. An environment is a named collection of libraries that contain files, programs, screens, and reports, all under a specific software release level. An environment also includes all attributes that determine how that environment is set up, such as printer overrides and JD Edwards World users.
The library types are:
| Library Types | Description |
|---|---|
| Production Library | A library (also referred to as a data library) you create to contain your live JD Edwards World data files. A special JD Edwards World program facilitates this process by creating all of the necessary data files that belong in your production library. |
| Common Library | A library you create to contain your live JD Edwards World data files that are common to more than one environment. These are data files such as your Data Dictionary or help files. They are also referred to as control files. By maintaining these types of files in one location, you facilitate standardization and conserve on disk space. |
| Security Library | A library you create to contain your live JD Edwards World user profile files. Sharing the user profiles between environments can minimize user profile maintenance. If you are setting up multiple environments that have separate object libraries at different release levels, you must have separate sets of security libraries. For example: if you have two versions of JD Edwards World software such as A9.3 and A9.2 you will probably need more than one security library. See Section 16.2.1, "Security Library Considerations" for more information. |
How many environments, production, or common libraries you choose to maintain depends on your database and company philosophy.
16.2.1 Security Library Considerations
You should consider the following when setting up libraries for your system:
-
Single security libraries are advantageous when J98INITA is the Initial Program on the IBM user profile. IBM object security might be necessary in addition to the JD Edwards World security options to complete the user security requirements.
-
Multiple security libraries require you to perform maintenance and security tasks for each environment. If each environment has a different security scenario, you should not use a single security library. If separate security libraries are necessary, you must have a matching object library with the QJDF data area naming the security library in the User Profile Library field.
-
Environments that are at the same release level, allow you to store other files in the security library for maintenance or control purposes. For example, the Software Versions Repository, Function Key Security, and Action Code Security files can be in the security library. Any files in the security library should apply to all environments and should not be in any other user data library. The pristine JDFDATA library should contain all of the JD Edwards World files.
16.2.2 Examples of Library Lists for Environments
Caution:
Never use JDFDATA in a production library list. JDFDATA contains pristine objects and should not be used in your production environment.Never put custom code in the JDFOBJ or JDFSRC libraries, or your own data in the JDFDATA library. Upgrades of JD Edwards World software remove and replace objects and data from these libraries, which could cause you to lose customized software or data. Do not put objects in the JDFINS and JDEINSTAL libraries, which are replaced when you upgrade to future releases. Your custom upgrade plans in the JDFINS library are preserved.
Production Environment - No Custom Code
| Library | Description |
|---|---|
| QTEMP | IBM Temporary Library |
| JDFOBJ | JD Edwards World Object Library |
| CLTCOM | Client's Common Library |
| CLTDTA | Client's Data Library |
| CLTSEC | Security Library |
| JDFSRC | JD Edwards World Source Library (Optional) |
| QGPL | IBM General Purpose Library |
Production Environment - With Custom Code
| Library | Description |
|---|---|
| QTEMP | IBM Temporary Library |
| CLTOBJ | Client's Custom Object Library |
| JDFOBJ | JD Edwards World Object Library |
| CLTCOM | Client's Common Library |
| CLTDTA | Client's Data Library |
| CLTSEC | Security Library |
| CLTSRC | Client's Custom Source Library |
| JDFSRC | JD Edwards World Source Library (Optional) |
| QGPL | IBM General Purpose Library |
| Library | Description |
|---|---|
| QTEMP | IBM Temporary Library |
| DEVOBJ | Client's Custom Objects in Development |
| TSTOBJ | Test Objects |
| CLTOBJ | Client's Custom Object Library |
| JDFOBJ | JD Edwards World Object Library |
| DEVCOM | Client's Common Library for development |
| DEVDTA | Client's Data Library for development |
| CLTSEC | Security Library |
| DEVSRC | Client's Custom Source in Development |
| CLTSRC | Client's Custom Source Library |
| JDFSRC | JD Edwards World Source Library (Optional) |
| QGPL | IBM General Purpose Library |
| Library | Description |
|---|---|
| QTEMP | IBM Temporary Library |
| TSTOBJ | Test Objects |
| CLTOBJ | Client's Custom Object Library |
| DEVCOM | Client's Common Library for development |
| JDFOBJ | JD Edwards World Object Library |
| DEVDTA | Client's Data Library for testing |
| CLTSEC | Security Library |
| QGPL | IBM General Purpose Library |