CICS TEST 摘要

由于最近自己写了一个BSM的联机程序，需要了解一些测试模块，特搜集整理如下：
How to use the CICS service transactions for testing
CICS provides four service transactions that you'll use as you test your programs. You use the first two,
CESN and CESF, to sign on and off of CICS. You use the third one, CEMT, to manage the status of CICS
resources. And you use the fourth one, CECI, to execute CICS commands interactively.
CESN and CESF: The sign on and sign off transactions
The master terminal transaction, more commonly know as CEMT, lets you control a variety of CICS
functions. To do that, you start CEMT and then enter CEMT commands.
The first command in this figure, SET PROGRAM NEWCOPY, causes CICS to read a fresh copy of a
program from disk. You should issue this command whenever you recompile a program while CICS is
running. Otherwise, CICS may continue to use the previous version of the program. 
The next two commands let you enable or disable a program or transaction. They're particularly useful when a
programming error forces a program into a pseudo?conversational loop that doesn't provide for the final exit
from the program. A loop like this can tie up a terminal indefinitely, restarting the same program over and
over again every time you press an attention key.
The last command in this figure, INQUIRE, lets you display status information for files, programs, and
transactions. If you enter the name of a specific file, program, or transaction, its status is displayed on the
screen. However, you can also display the status of all files, programs, or transactions that match a pattern you
specify. To do that, you include an asterisk (*) wildcard in the name.
nother CICS service transaction that's useful for program development is CECI, the command?level
interpreter. You can use it to issue CICS commands from outside a program. For example, you might want to
use it to issue a SEND MAP command to test a map before you've written the program that will process it.
CICS provides an area called temporary storage that programs can use to store data temporarily. Temporary
storage is divided into one or more temporary storage queues, or just TS queues. Each TS queue contains one
or more records
For an application like this to work, the CICS system must have definitions for the application's resources:
files, programs, mapsets, and transactions. In most installations, systems programmers create these definitions
when new programs are developed or change them when existing programs are modified. To do that, they can
use an online facility called Resource Definition Online, or RDO. With RDO, the systems programmer runs a
special CICS transaction (CEDA) to define CICS resources interactively using full?screen panels. These
definitions are stored in a file known as the CSD (CICS System Definition) file and can then be installed as
CICS system tables like the Program Control Table (PCT), Processing Program Table (PPT), and File Control
Table (FCT) you learned about earlier in this book.
Systems programmers can also define resources using a cataloged procedure named DFHCSDUP. Unlike
RDO, DFHCSDUP can be run while the CICS region is active, and it can be used to define several resources
at once. The job that invokes DFHCSDUP can also be saved or printed to provide documentation of the
resource definitions.

ref 
Murach-CICS-for-COBOL-programmer.pdf