Identifying the problem

JES2 issues messages for a variety of reasons. In some cases, JES2 may just be passing along information it received from another part of the system that encountered an error. Other times, what looks like an error may actually be confirmation of a normal occurrence. Consider the following questions before you collect any problem data:

Is the function not doing what is expected? Sometimes what you expect to happen may not be what should happen. Before treating the situation as an error, verify that the current design is working as expected by reviewing z/OS JES2 Introduction or z/OS MVS Initialization and Tuning Guide
Are there any other indications of the error? There could be messages from other components that not only confirm an error, but identify where the error occurred. Use the messages from other components to pinpoint the problem before reporting the problem to the IBM Support Center.
Has this happened before? Examining your installation's documentation about previous JES2 problems could uncover a similar situation to help you solve the current problem.
Has anything changed? Applying maintenance to your system might cause problems. If possible, after you collect any problem data, remove the changes and restart the system. If the problem does not recur, then determine what went wrong when you applied the maintenance. Problems applying maintenance contains information about what you need to determine the cause of the error.
Is JES2 running with the correct versions of the JES2 common storage modules, both from IBM and from the installation? z/OS MVS Initialization and Tuning Guide discusses the placement of the IBM® HASCxxxx load modules (CSA or LPA, above or below 16 megabytes of virtual storage); z/OS JES2 Macros discusses the placement of the installation modules that must be in common storage. If there are multiple versions or levels of JES2 at your installation, wrong levels of modules might be used (even though version checking is done during JES2 initialization). This can cause the system to perform differently than you expect.
Were any modifications applied that may have caused the error? You may not be able to answer this particular question until after collecting all problem data and looking at it to determine the cause of failure. You will need a copy of any modifications made if you report the problem to the IBM Support Center.
Is the problem occurring all the time or only in some instances? Do all commands receive the same error or only certain commands? Do all commands against devices receive the same error or only certain commands? Do all devices receive the same error?

If you suspect the problem is a JES2 problem, the following table directs you to the appropriate topic for the problem symptom. Also, see Collecting problem data for information about problem data useful for diagnosing JES2 problems.

Symptom	Problem Area
JES2 ends abnormally Message $HASP088 Message $HASP095	Abends
Checkpoint problems during JES2 initialization Errors during JES2 initialization JES2 ends abnormally during initialization Message $HASP479 Problem starting JES2	Initialization problems
JES2 enters checkpoint reconfiguration dialog	Checkpoint reconfiguration diagnostic procedures
JES2 does not respond to commands JES2 waiting and jobs do not start	Waits
Cannot purge an old output data set Functional subsystem (FSS) address space abends I/O error on printer, punch, or reader Job on printer, but printer not processing Job output marked “non-selectable” Printed or punched output not what expected Print Services Facility™ (PSF) printer status is “draining” instead of “inactive” Wrong destination on output	Output problems
Functional subsystem (FSS)-controlled printer is not printing FSS or functional subsystem application (FSA) abends	Print services facility (PSF) printer problems
JES2 looping Processor busy during initialization	Looping problems
JES2 disastrous error ($DISTERR) Message $HASP096	Disastrous errors
Resource shortages Lack of $HASP100 message Message $HASP050 in system log (SYSLOG) Message $HASP304 for internal reader shortages Spool shortages	Resource shortages
Bind image failure Incorrect or garbled output to node or remote I/O errors on nodes or remotes Message $HASP094 Message $HASP223 Message $HASP528 Message $HASP676 Message $HASP679 Message $HASP686 Node flooded Node or remote status “hung” or “draining” Unable to establish connection with a node Unable to transmit to a non-JES2 node	Remote (RJE) and node (NJE) problems
Failure to create or delete data space Message $HASP477	Data space errors
Access violations and warnings for JES2 output work selection JES2 Device Work Selection Screening External Writer Work Selection Screening SYSOUT Application Program Interface (SAPI) requests (SSI function code 79) Access logging for: JES2 device work selection screening External Writer work selection screening SYSOUT Application Program Interface (SAPI) requests (SSI function code 79) Message $HASP186	Using the JES2 DEBUG facility
Jobs running slower than usual Jobs taking a long time to enter the system from different sources (including local input devices) Printers slowing down or pausing during output processing Slow response to commands Your customers complain of poor response time Holding checkpoint for extended periods	Performance problems
Failure while applying maintenance	Problems applying maintenance

See z/OS JES2 Messages to obtain information about each message.