A Database Organizer for IMS for z/OS (DBO) Online Reorg (FFOR) failed with a connection error failure.
HPO3006E FAILURE DURING REQUEST PROCESSING - CHECK HPO STC OUTPUT ON sysid
HPO1601E STC CONNECT FAILURE, MVS=sysid, R15=00000320, R0=00030D40
The referenced ITK Started Task issues corresponding error message
HPO6002E CONNECT FAILURE, MVS=sysid, JOB=jobname, RC=00000320, R0=00030D40
In the ITK Started Task output, find the ACTIVITY LOG. This may indicate a problem with the define of the VSAM datasets created by the ITK STC for the Online Reorg. For example:
jobname (JOBnnnnn) CONNECT imsid dbname
ITKname (STCnnnnn) DISCONNECT imsid dbname
F0000001 * FFOR linear VSAM other parameters )
Search for the IDCAMS processing messages in the ITK Started Task output. For example:
DEFINE CLUSTER (NAME('FFOR.HALDB.xxxxxxxx.F0000001') -
KILOBYTES(00200000) LINEAR SHR(2,3) -
DATACLASS(xxxxxxxx) STORAGECLASS(xxxxxxxx) MANAGEMENTCLASS(xxxxxxxx) -
VOLUME(VOL000) * FFOR ...... VSAM ..... .......... )
IDC3211I KEYWORD '*' IS IMPROPER
If you see failed define statements similar to this then this implies that the ITK Started Task is not using a customized HPO Parmlib member.
In your ITK STC joblog the following message indicates which HPO parmlib member you are referencing.
HPO2036I USING HPOPARM MEMBER: name
When the ITK started task is started, it reads a parameter member from the parmlib data set identified by the HPOPARM DD statement. By default, the name of the parameter member is the jobname assigned to the started task. For example, if you use the started task procedure that is distributed in the CIMTSAMP library, the assigned jobname and the name of the HPOPARM member that is referenced is also STCITK. Alternatively, you can explicitly specify the parmlib member as follows:
//HPOPARM DD DISP=SHR,DSN=hlq.CIMTPARM(member-name)
Check that the parmlib member has been customized correctly and that it is being referenced by the ITK Started Task.
Please refer to the documentation to Customize the ITK Started Task