To
prepare the application and system table entries you should do the following:
- Translate, assemble or compile, and link-edit each program. Make sure
that there are no error messages on any of these three steps for any program
before you begin testing.
- Use the DEBUG and EDF options on your translator step, so that you can
use translator statement numbers with execution diagnostic facility (EDF)
displays.
- Use the COBOL compiler options CLIST and DMAP so that you can relate storage
locations in dumps and EDF displays to the original COBOL source statements,
and find your variables in working storage.
- Use the RDO DEFINE PROFILE command to generate a profile for your transactions
to use, and make sure the definitions are INSTALLed.
- Use the RDO DEFINE TRANSACTION command for each transaction in your application,
and make sure the definitions are INSTALLed.
- If your system does not use program autoinstall, use the RDO DEFINE PROGRAM
command for each program used in the application, and make sure the definitions
are INSTALLed.
- If your system does not use program autoinstall, use the RDO DEFINE MAPSET
command for each map set in the application, and make sure each definition
is INSTALLed.
- Use the RDO DEFINE FILE command, or put an entry in the FCT, for each
file used. If you use RDO, make sure the definitions are INSTALLed.
- Build at least a test version of each of the files required.
- Define each of the transient data destinations to be used by the application.
- Put job control DD cards in the startup job stream for each file used
in the application.
- Prepare some test data.
[[ Contents Previous Page | Next Page Index ]]