Scribd
Upload
138 views2 pages

Readme

This document summarizes the files used for the model CICS programs presented in a desk reference. The program files and mapsets are organized by program name into folders, while subprograms are in one folder and copy/data files are each in their own folder. Preparing the CICS system with resource definition and VSAM files is required to run the model programs on a mainframe. Special care needs to be taken when assembling the BMS mapset for one program to avoid compiler errors.

Uploaded by

api-3853979
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
138 views2 pages

Readme

This document summarizes the files used for the model CICS programs presented in a desk reference. The program files and mapsets are organized by program name into folders, while subprograms are in one folder and copy/data files are each in their own folder. Preparing the CICS system with resource definition and VSAM files is required to run the model programs on a mainframe. Special care needs to be taken when assembling the BMS mapset for one program to avoid compiler errors.

Uploaded by

api-3853979
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

CICS Desk Reference Programs

This document summarizes the files used for the model programs that are presented in units 5 and
6 of Murach’s CICS Desk Reference. The program files and mapsets are stored in folders by
program name; the subprograms are in a single folder; the copy members are in a single folder;
and the data files are in a single folder.
If you want to run the model programs on a mainframe, you’ll need to prepare your CICS system
beforehand. In particular, you’ll need to define the CICS resources required by each program
through RDO, and you’ll need to define, create, and load the VSAM files.
One thing to note: When you assemble the BMS mapset for the order entry program, the
symbolic map that’s produced will overwrite the programmer-generated symbolic map that we’ve
provided. That, of course, leads to compiler errors because the data names used in the program
won’t match up with the symbolic map names. So be sure to keep a backup copy of the
programmer-generated symbolic map before you assemble the mapset. Then, you can replace the
BMS-generated symbolic map with the programmer-generated one we’ve provided.

Program files and mapsets


CUSTMNT2
Custmnt2.cbl A customer maintenance program using traditional design; Trans-id: MNT2
Mntset2.bms The BMS mapset for the traditional maintenance program
Mntset2.cpy The symbolic map for the traditional maintenance program

CSTMNTP_CSTMNTB
Cstmntp.cbl The presentation logic portion of the customer maintenance program using
modular design; Trans-id: CMNT
Cstmntb.cbl The business logic portion of the customer maintenance program using
modular design
Cmntset.bms The BMS mapset for the modular maintenance program
Cmntset.cpy The symbolic map for the modular maintenance program

INVMENU
Invmenu.cbl A menu program for an invoicing application; Trans-id: MENU
Menset1.bms The BMS mapset for the menu program
Menset1.cpy The symbolic map for the menu program

CUSTINQ2
Custinq2.cbl A customer inquiry program that uses browse commands; Trans-id: INQ2
Inqset2.bms The BMS mapset for the customer inquiry program
Inqset2.cpy The symbolic map for the customer inquiry program

ORDRENT
Ordrent.cbl An order entry program; Trans-id: ORD1
Ordset1.bms The BMS mapset for the order entry program
Ordset1.cpy The programmer-generated symbolic map for the order entry program

Subprograms
Syserr.cbl A generalized error handling program
Getinv.cbl A subprogram that retrieves the next invoice number (for the ORDRENT
program)
Intedit.cbl A subprogram that edits integer data (for the ORDRENT program)
Numedit.cbl A subprogram that edits numeric decimal data (for the ORDRENT program)

Copy members
Attr.cpy A copy member for attribute settings, presented in figure 2-14 of Murach’s
CICS Desk Reference
Errparm.cpy A copy member for error handling values (for the SYSERR subprogram and
all programs except INVMENU)
Custmas.cpy The record description for the customer master file (for all programs except
INVMENU)
Invoice.cpy The record description for the invoice file (for the ORDRENT program)
Product.cpy The record description for the product file (for the ORDRENT program)
Invctl.cpy The record description for the invoice control file (for the ORDRENT
program and the GETINV subprogram)

Data files
Custmas.dat Data for the customer master file
Invoice.dat Data for the invoice file
Product.dat Data for the product file
Invctl.dat A single record for the invoice control file

You might also like