Accelerator Loader troubleshooting Use this information to diagnose and correct problems that you experience with Accelerator Loader. Monitoring load job progressMonitor the progress of active Accelerator Loader load jobs.Gathering diagnostic informationIf you encounter a problem and need to contact IBM® Software Support, you must gather certain information about your Accelerator Loader system and the problem before contacting Support. Your Support representative will need this information to correctly diagnose and resolve the problem. U4083 abend or error +CEE0374CA U4083 abend or error +CEE0374C usually indicates that data sets specified on the STEPLIB DD of the ACCEL_LOAD_TABLES WLM are not APF-authorized.Resolving an S322 or SEC6 abendYou can resolve an Accelerator Loader S322 or SEC6 abend. An S322 abend indicates that allotted CPU time was exceeded and the job was canceled. Accelerator Loader sometimes reports an S322 abend as an SEC6 abend. If you get an S322 or SEC6 abend, you can resolve both abends by setting the TIME parameter.Capturing a console dump - started task address spaceYou might need to capture a console dump of an Accelerator Loader started task address space to help Support diagnose a problem that you report.Capturing a console dump - multiple address spacesYou might need to capture an Accelerator Loader console dump that includes multiple address spaces to help Support diagnose a problem that you report.Canceling a hung jobYou can cancel a hung or looping Accelerator Loader job.Cleaning up common storage after a job failsThe Tools Customizer generates several jobs into the SAMPLIB when you select the step Create repository maintenance members on the Product Parameters panel during customization. One of these jobs, HLO#PIPE, runs the pipe cleanup utility program HLOCOMCL. Return codes when loading to offline acceleratorsThe following table lists return codes for load types when loading to one or more offline accelerators. Return codes indicate whether or not the load type will succeed or fail.Resolving errors using STORTIME and IDBACKYou may be able to use Db2 for z/OS subsystem parameters (also called zparms) STORTIME and IDBACK to address job fails that result in certain reason codes or errors.Understanding load library (STEPLIB) requirementsAccelerator Loader started task, batch jobs, and WLM application environments have load library (STEPLIB) requirements and options that can help you configure Accelerator Loader connections with Db2 for z/OS.Testing parallel loading performanceFamiliarize yourself with parameters AQT_MAX_UNLOAD_IN_PARALLEL and ACCEL_LOAD_TASKS to test performance of parallel loading.Accelerator Loader studio and Accelerator Loader server troubleshootingUse this information to diagnose and correct problems that you experience when using the Accelerator Loader studio and the Accelerator Loader server.Managing DSNUTILB interceptionYou can manage DSNUTILB interception by performing some routine and occasional tasks.Reason codes for HLOU5935E messageThe following reason codes trigger the HLOUHMON subtask. This task searches the pipe management control blocks and cancels the ACCEL_LOAD_TABLES processes which were not terminated. Parent topic: Troubleshooting