PCE list

The $HASP069 message provides an indication that JES2 is running in a "partial recovery status" mode. When a "not required" PCE fails, JES2 still processes work. That is, upon recovery, JES2 has lost functions associated with PCE processing. When a "required" PCE fails, JES2 fails and terminates.

Contact the system programmer to determine if continued processing is acceptable at an installation level and then diagnose the problem. The following table contains a list of PCEs, their names, whether they are required, and a description of their function.

PCE Description/Name	Required (Yes or No)	Function
Acquire Lock and Initiate Cleanup Executor (ALICE)	N	This PCE is responsible for finishing warmstart for individual jobs which failed to be recovered during normal warmstart processing because of BERT lock or BERT shortage conditions. If this PCE is ended, then these jobs will not be warmstarted on this member. If there are other members, then the ALICE PCE on those members will perform the function.
ARM Support Processor (RESTART)	N	This PCE is responsible for handling Automatic Restart Management (ARM) requests from other address spaces. These requests are handled synchronously by the JES2 address space. If the ARM PCE is ended, jobs that use ARM may hang in ARM registration/deregistration.
ASYNC I/O Processor (ASYNC)	Y	This PCE handles I/O completions for SPOOL, unit record devices, and BSC lines.
BERT Lock Post Processor (BERTLOCK)	N	This PCE handles requests for jobs that are currently locked. If one PCE of this type is ended, then the other PCEs will pick up the work of that PCE. There should be minimal impact to performance. If all PCEs of this type are terminated, then work in the SYSPLEX may hang.
Checkpoint Processor (CKPT)	Y	This PCE performs all I/O to the checkpoint data set. It is also responsible for the checkpoint reconfiguration process.
Command Processor (COMM)	Y	This PCE handles all JES2 commands for this member.
Distributed Available Work Notification Processor (DAWN)	N	This PCE performs the appropriate $#POSTing of all jobs that have space allocated to the spool volume being started. JES2 might not pick up output on a volume that is started for processing. A $S command or a $S dev command causes output to be selected.
Elapsed Time Monitor (TIME)	N	This PCE is responsible for monitoring the execution time for jobs and issuing the $HASP308 message if the estimated time is exceeded. If this PCE is ended, then the $HASP308 message is never issued.
End of Memory Processor (EOM)	N	This PCE is responsible for freeing resources associated with jobs that do not terminate normally and still own JES2 resources at the end of memory. If all PCEs of this type are ended, then these jobs will remain in execution, from a JES2 perspective, and JES2 resources held by these jobs will not be released.
ENF Listen Processor (ENF)	N	This PCE listens for ENFs from WLM to indicate a change in scheduling environment, WLM policy activation, and MVS™ service class resets. If this PCE is ended, then JES2 will be unaware of any policy activations and scheduling environment changes. This could cause jobs to hang on this member.
Event Trace Log (EVTL)	N	This PCE manages the JES2 $TRCLOG data set. It converts trace information from JES2 trace buffers in SYSOUT associated with the $TRCLOG job. If this PCE is ended, then no trace data can be recorded to the $TRCLOG data set.
Execution Services (EXEC)	Y	This PCE is responsible for placing jobs, STCs and TSUs into execution and processing their normal and abnormal termination (including re-queuing jobs to be executed again).
FSS Cleanup at EOM (FCLEANUP)	N	This PCE handles cleaning up FSS address spaces that go through end of memory without performing normal address space termination. If this PCE is ended, then FSS printers that go through the end of memory will hang.
Internal Reader Cleanup Processor (IRCLEAN)	N	This PCE cleans up internal readers that are no longer active. If an internal reader cleanup PCE is ended, a job that is active on the internal reader is not cleaned up until you restart JES2. If all the internal reader cleanup PCEs on a system end, then jobs on internal readers will no longer be cleaned up and internal reader data structures in ECSA does not free. If JES2 is not restarted, ECSA usage will increase and eventually you might need to do an IPL.
JCL Converter (CNVT)	N	These PCEs (with their subtasks) perform JCL conversion for all JOBs, STCs and TSUs. In general, there are two types of converter processors. One processor can wait for MVS resources (like HSM migrates) and ones that can not. If a converter PCE is ended, then the work can be picked up by other converters (possibly converters on other members). If all converter PCEs on a system end, then TSO logons and started task converters may hang. If all the converter PCEs on a system end, then TSO logons and started tasks will hang (as will batch jobs with system affinities).
JESXCF Interface (XCF)	Y	This PCE processes system status messages from JESXCF and maintains the current status or all members of the MAS.
JESXCF Request Processor (XCFCMND)	N	This PCE processes command requests received from JESXCF. It is used to receive information on who owns the checkpoint and initialization queries about where the checkpoint data set currently resides. If this PCE is ended, requests from other members can not be processed. This will have little impact on JES2 operations. However, messages sent to this PCE will accumulate in JESXCF and could eventually result in JESXCF ABENDs.
Job Priority Aging (PRTY)	N	This PCE updates the priority of JOBs on your system in accordance with the JOBDEF initialization statement. Priority aging only occurs on the lowest numbered active member of a MAS. If this PCE is ended, and this is the lowest active member, then priority aging of JOBs will stop. If this is not the lowest active member or if a lower numbered member is started, then there is no impact of this processor ending. SYSOUT priority aging is not affected.
Job Route Receiver (NET.RR)	N	This PCE (with the job route transmitter) handles jobs that are on the NJE transmit queue but are routed locally. This normally occurs when a $R XEQ command is used to change a network routed job to the local node. If this PCE is ended, then the job it is processing is typically hung. Other jobs can be processed by the job route transmitter/receiver on other MAS members.
Job Route Transmitter (NET.RT)	N	This PCE (with the job route receiver) handles jobs that that are on the NJE transmit queue but are routed locally. This normally occurs when a $R XEQ command is used to change a network routed job to the local node. If this PCE is ended, then the job it is processing is typically hung. Other jobs can be processed by the job route transmitter/receiver on other MAS members.
JQE Request processor (JQRP)	N	This PCE processes requests for JQEs from other address spaces other than the JES2 address space. If a JQRB PCE is ended, the job it was processing will remain in its current state and the requesting task (internal reader or NJE/TCP receiver) might hang. If all the JQRB PCEs on a system end, you can submit jobs through internal readers, NJE/TCP job receivers will no longer be able to accept new jobs, and request jobid processing hangs.
Line Manager (MLLM)	N	This PCE handles all BSC and SNA communication (NJE and RJE). If this PCE is ended, then all NJE and RJE communications stop.
MAS Command Processor (JCMD)	Y	This PCE processes job commands (such as $CJ) that require an action to be taken on a member other than where the command was entered.
Miscellaneous (MISC)	N	This PCE is responsible for periodic functions that need to be performed in JES2. It deletes PCEs that are no longer needed, frees locks for PCEs that have ABENDed, frees jobs and SYSOUT that is on the rebuild queue, cleans up deleted dynamic PROCLIBs, and maintains the job number usage index. If this PCE is ended, then local functions performed by this PCE will cease. The cleaning of the rebuild queues and the maintenance of the job number usage index can be performed by miscellaneous PCEs on other members.
Network Path Manager (NPM)	N	This PCE manages NJE signon and routing. If this PCE is ended, then no new NJE sessions can be established and NJE routing cannot be changed. Existing NJE connections will continue to function. If network connections on other nodes start to change (sessions come up or go down), it is possible that jobs and SYSOUT could be mis-routed, resulting in jobs switching between nodes.
Network Resource Monitor (NRM)	N	This PCE checks the availability of NJE devices and initiates their starts appropriately.
NJE Job Receiver (NET.JR)	N	These PCEs handle Jobs being received over a line through NJE. If a job receiver is ended, then it can no longer process new jobs. Depending on the state of the device, other receivers on the same line may hang. If this is the only job receiver on the line, or if all the jobs receivers on a line have ended, then jobs will no longer be received on that line. However, if a line does not have dedicated network receivers and transmitters and the line is restarted, the ended PCE is discarded and a new PCE (if there are any available) will be used.
NJE Job Transmitter (NET.JT)	N	These PCEs handle Jobs being sent out over a line through NJE. If a job transmitter is ended, then it can no longer process new jobs. Depending on the state of the device, other transmitters on the same line may hang. If this is the only job transmitter on the line, or if all the job transmitters on a line have ended, then jobs will no longer be sent on that line. However, if a line does not have dedicated network receivers and transmitters and the line and restarted, the ended PCE is discarded and a new PCE (if there are any available) will be used.
NJE SYSOUT Receiver (NET.SR)	N	These PCEs handle SYSOUT being received over a line through NJE. If a SYSOUT receiver is ended, then it can no longer process new SYSOUT data sets. Depending on the state of the device, other receivers on the same line may hang. If this is the only SYSOUT receiver on the line, or if all SYSOUT receivers on the line have ended, then SYSOUT will no longer be received on that line. However, if a line does not have dedicated network receivers and transmitters and the line and restarted, the ended PCE is discarded and a new PCE (if there are any available) will be used.
NJE SYSOUT Transmitter (NET.ST)	N	These PCEs handle SYSOUT being transmitted over a line through NJE. If a SYSOUT transmitter is ended, then it can no longer process new SYSOUT data sets. Depending on the state of the device, other transmitters on the same line may hang. If this is the only SYSOUT transmitter on the line, or if all SYSOUT transmitters on the line have ended, then SYSOUT will no longer be received on that line. However, if a line does not have dedicated network receivers and transmitters and the line and restarted, the ended PCE is discarded and a new PCE (if there are any available) will be used.
Offload Job Receiver (OFF.JR)	N	These PCEs handle Jobs being read using SPOOL Reload. There is one job receiver per offloader (OFFLOADn). If an offload job receivers is ended, then it stops processing all jobs. Since offload receivers sequentially process records read from an offload tape, this offloader's reload process stops because the receiver has ended. Other offloaders are not affected.
Offload Job Transmitter (OFF.JT)	N	These PCEs handle jobs being written using SPOOL offload. There is one job transmitter per offloader (OFFLOADn). If an offload job receivers is ended, then it stops processing all jobs. Since there is only one transmitter per offload, jobs will no longer be written by this offloader. SYSOUT transmission is not affected. Other offloaders are not affected.
Offload SYSOUT Receiver (OFF.SR)	N	These PCEs handle SYSOUT being read using SPOOL Reload. There is one SYSOUT receiver per offloader (OFFLOADn). If an offload SYSOUT receiver is ended, then it stops processing all SYSOUT. Since offload receivers sequentially process records read from an offload tape, this offloader's reload process stops because the receiver has ended. Other offloaders are not affected.
Offload SYSOUT Transmitter (OFF.ST)	N	These PCEs handle SYSOUT being written using SPOOL offload. There is one SYSOUT transmitter per offloader (OFFLOADn). If an offload SYSOUT transmitter is ended, then it stops processing all SYSOUT. Since there is only one transmitter per offloader, SYSOUT will no longer be written by this offloader. Job transmission is not affected. Other offloaders are not affected.
Output Priority Aging (PRTYO)	N	This PCE updates the priority of SYSOUT on your system in accordance with the OUTDEF initialization statement. Priority aging only occurs on the lowest numbered active member of a MAS. If this PCE is ended, and this is the lowest active member, then priority aging of SYSOUT will stop. If this is not the lowest active member or is a lower numbered member is started, then there is no impact of this processor ending. JOB priority aging is not affected.
Output Processor (HOPE)	N	This PCE creates Job Output Elements (JOEs) for jobs that have completed execution or have been received on an NJE SYSOUT receiver. If an output PCE is ended, then the work can be picked up by other output processors (including those on other members of the MAS). If all output processors are terminated, then jobs will hang in the output phase and their output cannot be printed.
Printer (PRT)	N	Each PCE of this type manages a local printer whether it is in JES or FSS mode. If a PCE of this type is ended, then that printer will stop functioning. Other printers are not affected. A $ADD PRINTER command can be used to define a new logical JES2 printer to manage the physical printer.
Process SYSOUT Processor (PSO)	N	These PCEs handle requests made through the Process SYSOUT SSI (PSO). These requests typically are associated with TSO users (RECEIVE or OUTPUT commands, or SDSF), external writers, and applications that examine SYSOUT. When a PSO PCE is ended, then the address space the PCE was processing requests from, may be hung. If all PSO PCEs are ended, then any PSO request will result in the requesting address space being hung.
Punch (PUN)	N	Each PCE of this type manages a local punch. If a PCE of this type is ended, then that punch will stop functioning. Other punches are not affected.
Purge Processor (PURGE)	N	These PCEs handle the purging of SPOOL space for JOBs and SPIN SYSOUT data sets. If one of these PCE is ended, the unit of work it was purging will hang in purge processing. Depending on the resources held by the PCE at the time it is ended, other purge processors on the same member may also hang. Purge processors on other members will not be affected and can pick up any work not hung on ended PCEs.
Reader (RDR)	N	Each PCE of this type manages a local card reader. If a PCE of this type is ended, then that card reader will stop functioning. Other card readers are not affected.
Remote Console Processor (MCON)	Y	This PCE handles messages and commands that are being sent to RJE, NJE and other members of the MAS. This PCE manages the $MASCOMM job.
Resource Monitor (RESOURCE)	N	This PCE is responsible for tracking resource usage and issues the $HASP050 message if a shortage is detected. If this PCE is ended, then local resources monitored by this PCE will stop. The monitoring of MAS scope resources can be performed by resource monitor PCEs on other members.
RJE Reader (RMT.RDR)	N	Each PCE of this type manages a card reader at an RJE workstation. If a PCE of this type is ended, then that remote reader will stop functioning. Depending on the state of the device, other readers on the same remote may hang. The remote may not be able to completely logoff JES2 and could become unusable until JES2 is hot started.
RJE Printer (RMT.PRT)	N	Each PCE of this type manages a printer at an RJE workstation. If a PCE of this type is ended, then that remote printer will stop functioning. Depending on the state of the device, other printers and punches on the same remote may hang. The remote may not be able to completely logoff JES2 and could become unusable until JES2 is hot started.
RJE Punch (RMT.PUN)	N	Each PCE of this type manages a card punch at an RJE workstation. If a PCE of this type is ended, then the remote card punch will stop functioning. Depending on the state of the device, other printers and punches on the same remote may hang. The remote may not be able to completely logoff JES2 and could become unusable until JES2 is hot started.
Spool Garbage Collector (SNF)	N	This PCE is responsible for recovering SPOOL space that was not freed during normal job purge processing. If this PCE is ended, then these unowned tracks of SPOOL will not be reclaimed on this member. If there are other members, then the SPOOL management PCE on those members will perform the function.
Spool Offload I/O Manager (SOM)	N	This PCE processes asynchronous events related to the JES2 SPOOL offload facility. If this PCE is ended, than all active offload devices will eventually hang. Also, no new offload devices can be started.
SWB Modify Processor (SJFSERV)	N	This PCE handles SWB modify requests for applications such as SDSF. If this PCE is ended, then SWB modify requests can not be processed. Since these requests are asynchronous, no address spaces will be delayed by this. However, since SWB changes are not being made, users of applications such as SDSF may start submitting multiple requests to JES2. These requests each consume some ECSA and if no action is taken for an extended period of time, ECSA can be exhausted.
SYSOUT API Processor (SPI)	N	These PCEs handle SAPI requests from applications. If one PCE of this type is ended, then the application whose request is currently being processed will hang. If all the SAPI PCEs are ended, then any application requesting access to SYSOUT through SAPI will eventually hang.
Spin Output Processor (SPIN)	N	These PCEs handle the processing of spin data sets created locally and those received through NJE. Not all PCEs of this type perform all functions. Only half process jobs received from NJE. If a PCE of this type ends, then the SYSOUT data sets being processed (or in the case of NJE, the job being processed) will hang. If all PCEs of this type end, then no local SYSOUT can be processed. Jobs that create spin output will complete execution but will hang in the spin phase in JES2. Also, ECSA usage can increase rapidly. The NJE function of the spin PCE will be spread across multiple members. If all the spin PCEs in the MAS capable of processing NJE SYSOUT have ended, then through NJE SYSOUT will continue to be received and none will be available for further processing.
Spool Command Processor (SPOOL)	N	This PCE handles operator commands against SPOOL volumes ($S, $Z, $P). In addition it reformats SPOOL track groups that encounter I/O errors (halting SPOOL volumes if serious errors were encountered). If this PCE is ended, then no spool commands can complete (regardless of the member the command was issued on). Also, JES2 will be unable to automatically halt a SPOOL volume in the event of a serious error. If there are I/O errors on spool, then requests to handle these errors will back up the ECSA and could eventually cause ECSA to be exhausted.
SSI Status/Cancel Services (STAC)	N	These PCEs handle status and cancel SSI requests from application address spaces (such as the TSO STATUS and CANCEL commands). If a PCE of this type is ended, then any address space using the status or cancel SSI will hang.
STIMER/TTIMER Processor (TIMER)	Y	This PCE manages JES2 internal timer requests.
Warm Start Processor (WARM)	Y	These PCEs are required during JES2 initialization but not required after initialization completes. These PCEs handle warm start processing and $E MEMBER commands. If an abend occurs during warm start processing, JES2 will terminate. If this PCE is processing a $E command, then the PCE will be ended. If a PCE of this type is ended, then the member it was resetting ($Eing) will not complete reset processing. No other member can reset this member and the member can not be restarted. If all the warm start PCEs are ended, then no $E MEMBER commands will be processed on this member. However, warm start PCEs on other members can process new reset requests.