Running the sample programs

GDDM V3R2 Base Application Programming Guide

Running the sample programs

GDDM V3R2 Base Application Programming Guide
SC33-0867-01

Note that the COBOL programs must not be run under CICS unless the STOP RUN statements have been replaced by a GO BACK statement or an EXEC CICS RETURN.

When the programs are run, the GDDM load (or core-image) library must be available. The same library is used for nonreentrant and reentrant programs. The first two sample programs make use of a file containing saved data streams. Except under VM/CMS, this file must be created before running the programs. The first program (ADMUSC1, ADMUSF1, ADMUSP1) also optionally generates a print file.

Under CICS, the programs must be added to the program control table (PCT) and processing program table (PPT). The GDDM load library (or core-image library) must be specified when CICS is started. For the saved data stream, the GDDM VSAM file (by default, ADMF) must have been created and entered in the CICS file control table (FCT); this is part of the installation procedure.

Under IMS, the programs must be added to the IMS program library, and the transaction codes and ACB set up during IMS system definition. Also, a database must be assigned and initialized to contain the saved data stream. These actions are part of the installation procedure.

Under TSO, the GDDM load library should be available (for example, in a STEPLIB). It is also necessary to have created a partitioned data set to contain the saved GDF data. As specified in Appendix C, "Programming with GDDM under TSO" in topic C.0, this has a record length of 400. A suitable space allocation for the program is one directory block and 100 400-byte data blocks. The DDname ADMGDF should be allocated to the data set before execution. If a print is requested, the print queue data set (ADMPRINT.REQUEST.QUEUE) must have been created and initialized.

Under VM/CMS, the GDDM TXTLIBs must be included in the GLOBAL libraries during execution, as described above, together with the language libraries. Program loading may be prolonged if a module is not generated. Files containing saved GDF and print data are generated dynamically by GDDM.

To allow enough storage for GDDM, PL/I execution must specify ISASIZE; a value of 10K bytes is usually sufficient.

For information on the ADMUTMT/V sample programs, see "Running sample program 8 under TSO" in topic A.5.2, and "Running sample program 8 under VM/CMS" in topic A.5.4.

Notices | Terms of use | Support | Contact z/OS