Test CICS® programs
by first fixing logic errors in the EGL debugger, then generating
the programs for your CICS test
region.
The EGL debugger runs only on Windows and Linux. There are steps you must
take in debugging because you cannot directly access CICS resources from the debugger:
- Set your resource association fileType for
the debugger to seqws (workstation sequential
file) for a serial file that you plan to implement as a CICS transient data queue or spool file when
you generate for CICS. Do the
same thing for a print file that you plan to implement as a CICS transient data queue or spool
file at runtime.
- Set your resource association fileType to ibmcobol (remote
VSAM file on the z/OS® or VSE
host) for a relative file that you plan to implement as a CICS temporary storage queue when
you generate for CICS. Note
that Linux does not support
remote VSAM files.
- Set your resource association fileType to ibmcobol (remote
VSAM file on the z/OS or VSE
host) for an indexed or relative file that you plan to implement as
a VSAM file when you generate for CICS.
Note that Linux does not support
remote VSAM files.
When you have fixed any logic errors in your program, generate
your program again, this time for your CICS test
region. In the CICS test region,
you can verify interactions that must be set up specifically for CICS, including I/O with the following
files and devices:
- temporary storage queues
- transient data queues
- spool files
- printers