$WTO PARAMETER LIST ERROR symptom records can be caused by problems in JES2 or in JES2 installation exits. Possible causes include the incorrect use of $WTO, $WTOR and $BLDMSG macro instructions and related data, or the incorrect manipulation of a $CMB data area by a JES2 installation exit 10 routine. Typically, multiple $WTO PARAMETER LIST ERROR symptom records are created for a given type of problem. Format log data from the logrec data set using EREP and search for “$WTO PARAMETER LIST ERROR”. See the EREP User's Guide for more information on formatting the log data set.

JES2 validates the $WTO parameter list at key points in JES2 processing and creates a $WTO PARAMETER LIST ERROR symptom record if it discovers an error. Additionally, JES2 corrects some errors. However, JES2 cannot detect or correct every possible error. Some errors cause problems in later processing, including causing JES2 to place CMBs on a queue where they could remain indefinitely. In some cases, this may result in a $HASP050 resource shortage message for CMBs. See Resource shortages for more information on handling resource shortages.