The source for creating system DBD files exists in libraries. The most current copy of the DBD for a system exists in PCP40. The source members use a common naming format, namely, xxxDBDy. xxx is the system indicator (e.g., FRS, LMS, SIS, HRS or ZSS). y is a type indicator, and is not present in all systems. For example, the source for the ZSS DBD is ZSSDBD. For FRS, it is split, FRSDBDF being the source for financial accounting. The scheme for y is system dependent.
To modify the DBD source, directly edit the source member and make the changes. Creation of new elements can be done by copying the definition from an old element. For data translation value changes, the same technique can be used. The layout of each transaction type in the DBD source is contained in the ZSS Technical Reference manual.
To test the DBD changes, certain files must be closed to the appropriate CICS system. Log onto that version of CICS and use the ZFOC transaction to close the files for the application system whose DBD is being updated and for ZSS. Both must be closed for the DBD process to run correctly. If using SPX option SCT, suboption 4, this is not necessary.
The test DBD jobs are in the ISP00 library. The first to run is AU3115Xv or use SPX option SCT, suboption 4.2. Output must be examined to make sure all items edit cleanly. The job return code is 0 even if problems are encountered. If the edit is clean, run AU3120Xv or use SPX option SCT, suboption 4.3. This updates the DBD. Again, you must examine output to make sure no errors were encountered.
If errors are encountered, correct the DBD source and rerun the AU3115/AU3120 process.
When the DBD update is complete, again log onto the appropriate version of CICS and use the ZFOC command to reopen first ZSS files and then the files for the appropriate application system. If you used SPX option SCT, suboption 4.3, this is not necessary.
The v in the job names refers to the version of the JCL to execute. The following table relates ZSS system to JCL version:
| ZSS System Versions | ||
|---|---|---|
| System | Mneumonic | JCL Version |
| 000 | ZSS | 1 |
| 001 | SIS | 2 |
| 002 | FRS | 3 |
| 003 | HRS | 5 |
| 005 | LMS | 4 |
Once changes have been tested and are ready for production, the process can begin. Fill out a migration request for the DBD source(s) that have been changed. Once the source is migrated, ask Production Control to run the DBD cycle for the system desired.
OIT Applications Support
Last Modified:
©2004 All Rights Reserved