Problem:
When PL/1 programs are running under CICS, output directed to SYSPRINT and PLIDUMP is routed to the TDQs CPLI and CPLD, respectively. This output can be examined from within CICS by using CEBR, and issuing the GET command, to copy the TDQ contents to a terminal-associated TSQ.
However, the browsing facilities available within CEBR are limited, and if the CICS region crashes the data is likely to be lost.
Resolution:
This article describes how data directed to these TDQs can automatically be copied to the SSTM job, and thereby retained across region shutdown and restart, and browsed outside of Enterprise Developer, using 3rd party tools such as Notepad .
1) Compile the attached Cobol program, PRTPLI, and define the transactions PPLI and PPLD, to execute it.
2) Add SYSPRINT and PLIDUMP DD statements to your SSTM JCL, using RECFM=LSEQ (refer to the online documentation for details of how to set up SSTM)
3) Configure the TDQs - Define the TDQs in the DCT resource tab as shown in the attached document, PLI-TDQs.doc.
Recycle the CICS region, and any future output directed to SYSPRINT or PLIDUMP will automatically be moved from the respective TDQ to the equivalent DD statements in the SSTM job. The job output will be retained across region shutdown and restart, and can be viewed via the JES spool browsing facility, or the JES files can be browsed from outside of the ES region, using Notepad , or any other suitable editor.
Also attached to this article is a step-by-step guide to setting up an ES region with the appropriate configuration for using PL/I under CICS, and redirecting SYSPRINT and PLIDUMP output to an SSTM job. See PLICICS.doc.
#EnterpriseDeveloper
#MFDS
