What to do when you receive a "CADD342S SAPI task I/O Error"

Document ID : KB000031745
Last Modified Date : 14/02/2018
Show Technical Document Details

From time to time and for a variety of different reasons, your SAPI tasks may issue this error when it encounters a problem with a dataset that it is trying to process out of the JES queue and into the CADDSPL dataspace (LDS files). When received, the I/O error message may have different qualifying text suffixes on them such as:





When a CADD342S error is received, there will be other associated messages that help you identify the problem entry in the JES queue. Look for the following associated messages:

CADD360I  SAPx taskid job=jobname(jobid),step=stepname

CADD361I  SAPx taskid ddn=ddname(Dsid),proc=procstepname

CADD362I  SAPx taskid dsn=dsname


When these errors are received, the bottom line is that there is something wrong with the dataset and the SAPI task is not going to be able to process the data into the LDS files. Consequently, there will likely be some followup action that you will need to take to prevent the same error from occurring again upon restarting the affected SAPI task.

To prevent the error from being received again, you are going to have to DELETE the entry with TYPE=RCVY from the appropriate Dispatch 'Report Input Display Facility' (RIDF) queue. To delete the TYPE=RCVY entry:

A. Access the 'VOPMI100-Subtask Status Screen' (via option 8.1 from the main menu), tab down next to the appropriate Dispatch subtask (either RPI1,RPI2,RPI3, MSG or one of the ARCH tasks), type an 'E' next to it, and hit the ENTER key to temporarily end the task. You want to do this so that when you initially modify the RCVY entry before deleting it, the Dispatch subtask does not attempt to process this partial entry which might then result in additional errors being received or the Dispatch subtask itself abending.

B. With the potentially affected Dispatch subtask stopped, access the appropriate VOPMI200 screen (via option 8.2 from the main menu and then specifying the correct queue type), tab down next to the problem report= / jobname= type=RCVY entry and type an 'F' in the OPT column and hit enter.  Notice that the TYPE will change to USER. You can then tab back down next to the entry and DELETE it by typing a 'D' in the OPT column next to that same entry.                                                   

C. As a followup, you may also see an entry for this same report/job out on the JES HOLD or OUTPUT queue with odd values in the DEST and/or FORM fields (values such as $$R1RPI1 for DEST and $$6ZGAAA for FORM for example). As previously mentioned, the SAPI task will not be able to process this particular entry from JES so you should probably consider deleting it to prevent any re-occurrence of the I/O errors.

D. Once you are sure the problem entry in JES has been neutralized (either held or deleted), access the VOPMI100 screen in Dispatch again (as per item 'A' above) and restart both the appropriate SAPI task and the Dispatch subtask by typing an 'S' next to them and hitting the ENTER key.