The Network Print Facility has a logging facility that writes messages in a log file to track the system activity regarding temporary print data sets. The messages record when a print data set is created, deleted, placed on the queue, and successfully or unsuccessfully transmitted. See Network Print Facility logging for more information on these messages.

The log file data set has sequential organization (PS), a fixed block format (FBA), a logical record length (LRECL) of 133, and a block size (BLKSIZE) of 1330. Because the log file is not a VSAM data set, you do not need to allocate space for it. It can be dynamically allocated by specifying the log file with the //EZAPPLOG DD statement in the JCL to start the capture point applications and queue manager.

The log file cannot be shared. Therefore, you will need a unique log file for each startup procedure.

If the //EZAPPLOG DD statement is missing, the capture point applications will run but the system will not log the activity.