Read through these requirements before running a generated CICS program. CICS documentation and your site's CICS administration staff are the authoritative source for information on how to set up CICS tables and startup JCL.
You must allocate QMFHPO.SRAALOAD (which contains the BMS maps used by the generated programs) to the CICS Module Load Library list (DFHRPL). The load library that contains the programs that you generate and prepare must also be allocated.
All generated CICS programs interact with the user via the following three BMS maps:
Generated programs refer to each of these maps in a single mapset named RAAM330. This module can be found in QMFHPO.SRAALOAD.
PPTs for all of these maps must be assembled and added to the appropriate CICS regions. These PPT entries can be found in QMFHPO.SRAASAMP.
PPTs for programs that you generate and prepare must also be assembled and added to your CICS session.
You must add transaction IDs for the programs you generate.
You must add resource control entries for the programs you generate.
When running a CICS program, you are prompted for host variable values, one at a time, in sequence. Each host variable in the program is displayed on a CICS map along with its data type. You must specify a value for each variable.
Generated CICS programs are completely pseudo-conversational. They terminate the task (EXEC CICS RETURN...) each time that a map is sent. Because DB2 automatically closes cursors at task termination, these programs must read all of the DB2 data before the first screen of data is displayed. In fact, the data is read from DB2, formatted according to the form specifications, and placed in auxiliary temporary storage for browsing.
This implementation has many advantages. For example, when browsing the report, you are actually browsing the data stored in temporary storage. All of the DB2 I/O has finished by the time the first screen of report data is displayed. Because the cursor is closed, all shared page locks are released by this time.
Because of this implementation, however, there is a restriction on the number of rows of report data. CICS limits the number of rows that can be written to temporary storage queues to 32767. This limits the report to 32767 lines. To enhance the performance of generated CICS programs, CICS system programmers should verify that auxiliary temporary storage is properly allocated and tuned to handle these programs.