7. Writing Field-developed Applications › 7.4 Testing, Documenting and Deploying the FDA
7.4 Testing, Documenting and Deploying the FDA
At this point, you have written and validated your
field-developed application code. In this section, you will
o verify that the code is valid
o write documentation to include in the CA MICS documentation
set
o deploy the FDA in production
To perform a final test, consider running the CA MICS
operational jobs against data that you create to test its
functions, including the duplicate data checks and exception
and management objective reports.
To document your field-developed application in standard
CA MICS guides, follow these guidelines:
Add documentation to the Database Structure and Content
Guide.
The members you edit or create in sharedprefix.MICS.DOC.TEXT
are:
IZ - add a section reference to the section you are
adding.
For example, IZ might contain:
+-------------------------------------------------+
|$HEDR Chapter 35. USER COMPONENTS |
| |
| XYZ Corporation has written and installed |
| the following user components on its CA MICS |
| system: |
| |
| Product Information Area |
| ----------------------------------------------- |
| UNP - User NPA Component UNP - 3705 Activity |
| UNI - Incidents |
| UCA - Lines, etc. |
| ULO - Logon Tracker ULO - Logon Info |
| USM - HSM Activity USM - HSM Activity |
| |
| For more information, refer to the following |
| sections: |
| |
| 1 - UNP Information Area |
| 2 - UNI Information Area |
| 3 - UCA Information Area |
| 4 - ULO Information Area |
| 5 - USM Information Area |
| |
+-------------------------------------------------+
IZn - write an overview of the FDA's information area.
For example, IZ1 might contain:
+-------------------------------------------------+
|$HEDR 35.1 - UNP Information Area |
| |
| This section identifies each file in the UNP |
| Information Area of the UNA Product. |
| |
| This information area provides .... |
| |
| The files in this information area are described|
| in the following sections: |
| |
| 1 - UNC File - 3705 Activity |
| 2 - UN_ File - ... |
| 3 - UC_ File - ... |
+-------------------------------------------------+
IZnf - write an overview of the information area's file.
For example, IZ11 might contain:
+-------------------------------------------------+
|$HEDR 35.1.1 - UNC File (3705 Activity) |
| |
| The 3705 Activity File (UNPUNCxx) contains data |
| elements that describe ... |
| |
| The following sections describe: |
| |
| 1 - File Organization |
| 2 - Data Elements List |
| 3 - Usage Considerations |
+-------------------------------------------------+
IZnf1 - call in the file's generated organization list
For example, IZ111 might contain:
+-------------------------------------------------+
|$HEDR 35.1.1.1 - File Organization |
| |
| $SMEM #INS000S |
| $SMEM #INSUNCS |
| $FIG Figure 35-x. UNPUNC File's Organization |
+-------------------------------------------------+
IZnf2 - call in the file's generated element list
For example, IZ112 might contain:
+-------------------------------------------------+
|$HEDR 35.1.1.2 - Data Elements List |
| |
|$SMEM #INS000E |
|$SMEM #INSUNCE |
|$FIG Figure 35-x. UNPUNC File's Data Elements |
+-------------------------------------------------+
IZnf3 - write notes about how to use the file
For example, IZ113 might contain:
+-------------------------------------------------+
|$HEDR 35.1.1.3 - Usage Considerations |
| |
| When using the UNPUNC File, ... (special |
| considerations) |
| |
| Do not use this file to ... |
| |
| To retrieve information from this file, ... |
+-------------------------------------------------+
PICIZ - add a call to your new section
For example, PICIZ might contain:
+-------------------------------------------------+
|$PAGE |
|$LMEM ITITLE0Z Title Page |
|$LMEM ITITLE0Z Title Page |
|$$TOC Table of Contents Generator |
|$SPAG |
|$PAGE 35 001 |
|$SMEM IZ USER COMPONENTS |
|$SMEM IZ1 UNP Information Area |
|$SMEM IZ11 UNC File |
|$SMEM IZ111 File Organization |
|$SMEM IZ112 Data Elements List |
|$HEDR IZ113 Usage Considerations |
|$SMEM IZ12 UN_ File |
|$SMEM IZ121 File Organization |
|$SMEM IZ122 Data Elements List |
|$HEDR IZ123 Usage Considerations |
|$SMEM IZ2 UNI Information Area |
|$SMEM IZ21 UN_ File |
|$SMEM IZ211 File Organization |
|$SMEM IZ212 Data Elements List |
|$SMEM IZ213 Usage Considerations |
| ... |
+-------------------------------------------------+
PICIXD - add a Data Dictionary for your FDA by adding
calls to data elements existing in or added by
you to sharedprefix.MICS.DIC.TEXT
For example, PICIXD might contain:
+-------------------------------------------------+
|$PAGE |
|$LMEM ITITLEXD Database Structure and Content Gui|
|$LMEM ITITLEXD Database Structure and Content Gui|
|$SPAG |
|$$TOC |
|$PAGE D 001 |
|$SMEM IXD Data Dictionary |
|$SMEM IXD1 The Structure of the Data Dictiona|
|$SMEM IXD2 Common Data Elements |
|$DMEM ASID Address Space Identification |
|$DMEM CHANNEL Physical Channel Address |
|$DMEM COMMAND Command/Transaction Name |
|$DMEM DAY Day of Month |
| ... |
|$SMEM IXD34 The ADMCYC (Cycles Log) File |
|$DMEM IHLCYCLE MICS Cycle |
|$DMEM IHLLOWTS Input Data Low Time Stamp |
|$DMEM IHLHITS Input Data High Time Stamp |
|$SPAG |
|$SMEM IXDZ Field Developed Applications |
|$DMEM UNPABNDC Abend Code |
|$DMEM UNPABNDN Abend Message Number |
|$DMEM UNPADSOA ADS/Online Application Name |
|$DMEM UNPAVDCT Average Conversational Respons Tim|
|$DMEM UNPCOST Processing Charges |
|$DMEM UNPCRSTM Conv. Transaction Response Time |
| ... |
|$SPAG |
+-------------------------------------------------+
To deploy the FDA in production, follow these steps:
o Redefine the FDA in sharedprefix.MICS.GENLIB(DBTABLE)
If you placed the FDA in its own test database unit,
follow the guidelines in section 2.3.3.3 of the PIOM for
changing the FDA's unit identifier from T (test unit) to
either P (primary unit) or U (standard database unit).
o Rebuild the database unit jobs to include your FDA
- Submit the job in prefix.MICS.CNTL(JCLGENB) to generate
installation JCL members.
- Submit the job in prefix.MICS.CNTL(COPYLIBU) to move
CA MICS parameter library members that relate to your
FDA.
- Submit the job in prefix.MICS.CNTL(CYCLEGEN) to generate
database unit definitions.
- Submit the job in prefix.MICS.CNTL(BACKUP) to back up the
database unit definitions.
- Submit the job in prefix.MICS.CNTL(RESTORE) to restore
the new specifications to the new database unit.