During startup input dataset recovery processing, the CADDSPL CADZSAPx task encounters a bad file structure within the input report or msgclass dataset and terminates with a the following error message:
CADD326E SAPx taskid SAPI interface error (rc=00,rtrn=0008,reas=0000)
The CADZSAPx task does not startup, displaying these messages in the job log:
CADD357S SAPx taskid Bad file structure type 002 for token 0000923A
CADD360I SAPx taskid job=xxxxxxxx(JOB06396),step=STEP070,token=0000923A
CADD361I SAPx taskid ddn=SYSPRINT( ),proc=xxxxxxxx
CADD362I SAPx taskid dsn=#xxxx.xxxxxxxx.JOB06396.D0000130.?
The CADD357S BAD FILE STRUCTURE messages occur when there is something wrong with the dataset, as it sits in the JES queue, that results in our SAPI task not being able to successfully process that entry into the LDS files.
As a proactive followup action that you can perform to prevent future occurrences of these CADD357S SAPx taskid BAD FILE STRUCTURE errors you will want to make sure that you have corrective APAR RO81633 applied to your Dispatch environment.