Notifying the print application
When you deliver the data to a print application outside CICS, you might need to notify the application that you have data ready to process.
You do not need to do this if the application runs automatically and knows to look for your data. For example, to print on a printer owned by the MVS job entry system (JES), all you need to do is create a spool file with the proper routing information. JES does the rest.
However, sometimes you need to submit a job to do the processing, or otherwise signal an executing application that you have work for it.
To submit a batch job from a CICS task, you need to create a spool file which contains the JCL for the job, and you need to direct this file to the JES internal reader. You can create the file in any of the three ways listed for spool files in Table 1 , although if you use a sequential terminal, the job does not execute until CICS shuts down, as noted earlier. For files written with spool commands, the information that routes the file to the JES internal reader is specified in the SPOOLOPEN command. For transient data queues and sequential terminals, the routing information appears on the first record in the file, the “JOB card”.
The output to be printed can be embedded in the batch job (as its input) or it can be passed separately through any form of data storage that the job accepts.