Preparing the sample applications for the CICS environment

Before you run the CICS sample programs, you must log on to CICS using a LOGMODE of 32702. This is because the sample programs have been written to use a 3270 mode 2 screen.

To prepare a sample application that runs in the CICS environment, perform the following steps:

1. Create the symbolic description map and the physical screen map for the sample by assembling the BMS screen definition source (supplied in library thlqual.SCSQMAPS, where thlqual is the high-level qualifier used by your installation). When you name the maps, use the name of the BMS screen definition source (not available for Put and Get sample programs), but omit the last character of that name.
2. Perform the same steps that you would when building any CICS WebSphere MQ for z/OS application--these steps are listed in Building CICS applications. The library members that you will use are listed in Table 50, Table 51, Table 52, and Table 53.
3. Identify the map set, programs, and transaction to CICS by updating the CICS system definition (CSD) data set. The definitions you require are in the member thlqual.SCSQPROC(CSQ4S100). For guidance on how to do this, see WebSphere MQ for z/OS System Setup Guide.

   Note:

   For the Credit Check sample application, you will get an error message at this stage if you have not already created the VSAM data set that the sample uses.

4. For the Credit Check and Mail Manager sample applications, ensure that the queues they use are available on your system. For the Credit Check sample, they are defined in the member thlqual.SCSQPROC(CSQ4CVB) for COBOL, and thlqual.SCSQPROC(CSQ4CCB) for C. For the Mail Manager sample, they are defined in the member thlqual.SCSQPROC(CSQ4CVD). To ensure that these queues are always available, you could add these members to your CSQINP2 initialization input data set, or use the CSQUTIL program to load these queue definitions.

   For the Queue Attributes sample application, you could use one or more of the queues that are supplied for the other sample applications. Alternatively, you could use your own queues. However, note that in the form that it is supplied, this sample works only with queues that have the characters CSQ4SAMP in the first eight bytes of their name.

QLOP abend

When the CICS sample applications supplied with WebSphere MQ for z/OS use MQI calls, they do not test for the return codes that indicate that the queue manager is not available. If the queue manager is not available when you attempt to run one of the CICS samples, the sample abends with the CICS abend code QLOP. If this happens, you must connect your queue manager to your CICS system before you attempt to start the sample application again. For information about starting a connection, see WebSphere MQ for z/OS System Administration Guide.

Names of the sample CICS applications

The source and JCL files that are supplied for each of the sample CICS applications are listed in the following tables:

Table 50. Source and JCL for the Put and Get samples

Table 51. Source for the Queue Attributes sample

Table 52. Source and JCL for the Mail Manager (CICS) sample (COBOL only)

Table 53. Source and JCL for the Credit Check CICS sample