BFGCD0001 - BFGCD9999
- BFGCD0001E
- This task was rejected by the Connect:Direct API with the following error message: <insert_0>
- Severity
- 20 : Error
- Explanation
- If this message does not give enough information, check the accompanying error messages for further information.
- Response
- For further information on resolving this error, see the problem determination information on the product website.
- BFGCD0002E
- Connect:Direct process ''<insert_0>'' has completed but the process end record is missing.
- Severity
- 20 : Error
- Explanation
- The file transfer is considered as failed because statistics information for the Connect:Direct process that is part of the transfer is missing the PRED record.
- Response
- Review the Connect:Direct statistics information for the process to understand the problem. Note that a file transfer from an MQMFT agent to a Connect:Direct node might have succeeded. If the problem persists contact the IBM support center for assistance.
- BFGCD0003E
- Operation: ''<insert_0>'' failed because the system is not connected to the Connect:Direct node.
- Severity
- 20 : Error
- Explanation
- This exception is unexpected. The cause is not immediately known.
- Response
- If the problem persists, see problem determination information in the product documentation.
- BFGCD0004W
- Failed to delete temporary file ''<insert_0>'' when canceling transfer ID ''<insert_1>''.
- Severity
- 10 : Warning
- Explanation
- The Connect:Direct bridge failed to delete the temporary file after the transfer was canceled.
- Response
- Manually delete the file from the Connect:Direct bridge agent temporary directory.
- BFGCD0005W
- You do not have permission to read files that are in, or write files to, the Connect:Direct bridge agent temporary directory ''<insert_0>''.
- Severity
- 10 : Warning
- Explanation
- The user who runs the fteCleanAgent command must have read and write permission for the Connect:Direct bridge agent temporary directory to delete temporary files from the directory.
- Response
- Ensure the user ID you are using to run the fteCleanAgent command has read and write permission for the Connect:Direct bridge temporary directory.
- BFGCD0006E
- Parameter PNODE or SNODE cannot be specified in the transfer request.
- Severity
- 20 : Error
- Explanation
- The Connect:Direct bridge node automatically assigns the PNODE or SNODE parameters for a Connect:Direct file copy process. These parameters are not permitted to be overridden.
- Response
- Remove the specified PNODE or SNODE parameter from the transfer request and submit again.
- BFGCD0007E
- DSNTYPE attribute was specified as ''<insert_0>'' but the required transfer is to a PDS or PDSE.
- Severity
- 20 : Error
- Explanation
- The DSNTYPE can only be specified as PDS or LIBRARY for a transfer to a partitioned data set.
- Response
- Correct the DSNTYPE attribute setting for the transfer request and submit again.
- BFGCD0009E
- The value ''<insert_0>'' specified for the cdNodeLocalPortRange agent property has an invalid format.
- Severity
- 20 : Error
- Explanation
- The value of the cdNodeLocalPortRange property must be a comma-separated list of values or ranges. For example '5000-6000,7000'.
- Response
- Modify the value of the cdNodeLocalPortRange property in the agent properties file. Then restart the Connect:Direct bridge agent.
- BFGCD0010E
- The value ''<insert_0>'' specified for the cdNodeProtocol agent property is invalid.
- Severity
- 20 : Error
- Explanation
- The value of the cdNodeProtocol property must be 'TCPIP', 'SSL' or 'TLS'.
- Response
- Modify the value of the cdNodeProtocol property in the agent properties file. Then restart the Connect:Direct bridge agent.
- BFGCD0012E
- The cdNodeKeystorePassword agent property has not been set.
- Severity
- 20 : Error
- Explanation
- When the value of the cdNodeProtocol property is set to 'SSL' or 'TLS' and the cdNodeKeystore property has been set, a value must be specified for the cdNodeKeystorePassword property.
- Response
- Provide a value for the cdNodeKeystorePassword property in the agent properties file. Then restart the Connect:Direct bridge agent.
- BFGCD0013E
- The cdNodeTruststore agent property has not been set.
- Severity
- 20 : Error
- Explanation
- When the value cdNodeProtocol property is set to 'SSL' or 'TLS' a value must be specified for the cdNodeTruststore property. The cdNodeTruststore property value must be the path to the truststore file.
- Response
- Provide a value for the cdNodeTruststore property in the agent properties file. Then restart the Connect:Direct bridge agent.
- BFGCD0014E
- The cdNodeTruststorePassword agent property has not been set.
- Severity
- 20 : Error
- Explanation
- When the value cdNodeProtocol property is set to 'SSL' or 'TLS' a value must be specified for the cdNodeTruststorePassword property.
- Response
- Provide a value for the cdNodeTruststorePassword property in the agent properties file. Then restart the Connect:Direct bridge agent.
- BFGCD0015E
- Transfer with ID ''<insert_0>'' cannot continue because the associated Connect:Direct process ''<insert_1>'' cannot be released from "held due to error" status. Manually release or delete the process from the Connect:Direct node associated with the Connect:Direct bridge agent.
- Severity
- 20 : Error
- Explanation
- During a transfer, an associated Connect:Direct process was found to have a "held due to error" (HE) status. The Connect:Direct bridge agent attempted to release the process but the process continued to have a "held due to error" (HE) status.
- Response
- Check the identified Connect:Direct process and attempt to either manually release the process or delete it to allow the transfer to complete. Alternatively, cancel the transfer.
- BFGCD0016E
- An invalid DSORG file attribute value of <insert_0> was specified for the transfer request.
- Severity
- 20 : Error
- Explanation
- In a transfer request a DSORG file attribute can only be specified as PS or PO. A value of PO can only be specified when the file is a partitioned data set.
- Response
- Either remove the DSORG file attribute setting for the transfer or change the transfer destination type to agree with the DSORG value. Then submit the transfer request again.
- BFGCD0017E
- The encoding ''<insert_0>'' is not supported on Windows.
- Severity
- 20 : Error
- Explanation
- For text conversion on Windows the specified encoding must have an equivalent Windows code page identifier. For the specified encoding no Windows code page identifier could be found, or the encoding value specified was illegal.
- Response
- Correct the specified encoding value and submit the transfer request again.
- BFGCD0018E
- Connect:Direct process ''<insert_0>'' has gone into "held due to error" status and cannot be released. The process has been deleted.
- Severity
- 20 : Error
- Explanation
- The file transfer is considered as failed because the Connect:Direct process that is part of the transfer has a "held due to error" status and cannot be released.
- Response
- Review the Connect:Direct information for the process to understand the problem. Manually delete the Connect:Direct process that has "held due to error" status. If the problem persists contact the IBM support center for assistance.
- BFGCD0019E
- The specified key ''<insert_0>'' is either not a valid BPXWDYN key, or is not supported for a transfer between MQMFT and Connect:Direct.
- Severity
- 20 : Error
- Explanation
- Keys specified for a file transfer request to or from a data set on a z/OS Connect:Direct node must be valid BPXWDYN keys and be supported by the MQMFT Connect:Direct bridge.
- Response
- Consult the MQMFT product documentation for a list of supported BPXWDYN keys. Correct the transfer request and submit again.
- BFGCD0020E
- The specified variable ''<insert_0>'', for a ''match'' condition, is not a valid intrinsic symbol.
- Severity
- 20 : Error
- Explanation
- Variables specified within the ConnectDirectProcessDefinitions.xml file must be valid MQMFT intrinsic symbols for selecting a Connect:Direct process.
- Response
- Consult the MQMFT product documentation for a list of valid MQMFT intrinsic symbols for Connect:Direct processes. Correct the ConnectDirectProcessDefinitions.xml file within the Connect:Direct bridge agent's configuration directory.
- BFGCD0021E
- The specified variable ''<insert_0>'', for a ''defined'' condition, is not a valid intrinsic symbol.
- Severity
- 20 : Error
- Explanation
- Variables specified within the ConnectDirectProcessDefinitions.xml file must be valid MQMFT intrinsic symbols for selecting a Connect:Direct process.
- Response
- Consult the MQMFT product documentation for a list of valid MQMFT intrinsic symbols for Connect:Direct processes. Correct the ConnectDirectProcessDefinitions.xml file within the Connect:Direct bridge agent's configuration directory.
- BFGCD0022E
- A problem has occurred while attempting to read the <insert_0> Connect:Direct process file. The details of the error are: <insert_1>
- Severity
- 20 : Error
- Explanation
- The Connect:Direct process file cannot be read.
- Response
- Check that the Connect:Direct process file can be accessed by the agent.
- BFGCD0023E
- The file transfer does not define a value for MQMFT intrinsic symbol <insert_1> which is required by the <insert_0> Connect:Direct process file.
- Severity
- 20 : Error
- Explanation
- The Connect:Direct process file requires MQMFT intrinsic symbol values to be defined that are not available for the transfer request. MQMFT transfers only define those intrinsic symbols that are relevant to the transfer request. This problem is most likely caused by the ConnectDirectProcessDefinitions.xml file being incorrectly configured, causing inappropriate Connect:Direct process files to be selected for a transfer.
- Response
- If appropriate correct the transfer request such that the require MQMFT intrinsic symbol is defined, and assigned a value, or contact your MQMFT system administrator to correct the problem. Consult the MQMFT product documentation for an explanation of the MQMFT intrinsic symbols for Connect:Direct processes. Either correct the transfer request and submit again, or submit the transfer request again after the problem with the ConnectDirectProcessDefinitions.xml file has been resolved.
- BFGCD0024E
- The specified type ''<insert_0>'', for a ''node'' is not a valid operating system platform type.
- Severity
- 20 : Error
- Explanation
- Types specified within the ConnectDirectNodeProperties.xml file must be one of: Unix, Windows, or z/OS (also: ZOS, OS/390 and OS390 are valid to specify z/OS).
- Response
- Correct the ConnectDirectNodeProperties.xml file within the Connect:Direct bridge agent's configuration directory.
- BFGCD0025E
- Connect:Direct process ''<insert_0>'' has gone into "held due to error" status and cannot be released. An attempt to delete the process has failed due to: <insert_1>
- Severity
- 20 : Error
- Explanation
- The file transfer is considered as failed because the Connect:Direct process that is part of the transfer has a "held due to error" status and cannot be released.
- Response
- Review the Connect:Direct information for the process to understand the problem. Manually delete the Connect:Direct process that has "held due to error" status. If the problem persists contact the IBM support center for assistance.
- BFGCD0026I
- Connect:Direct messages: <insert_0>
- Severity
- 0 : Information
- Explanation
- This message is a capture of the message text generated for the Connect:Direct process statistical records. When a Connect:Direct process failure has occurred the message text will include the reason.
- Response
- Examine the Connect:Direct messages and take action as appropriate. If necessary examine the Connect:Direct statistics log for the process and consult the Connect:Direct product documentation.
- BFGCD0027E
- The operating system platform type for node <insert_0> is either unknown or not supported.
- Severity
- 20 : Error
- Explanation
- Only nodes for Unix, Windows, and z/OS operating systems are supported where the Connect:Direct bridge agent is required to automatically generate a Connect:Direct process for the transfer. For the problem Connect:Direct node; either its operating system platform type is unknown, meaning it has not been set within the Connect:Direct bridge agent's node network map or is not defined within the ConnectDirectNodeProperties.xml file, or the operating system platform type defined within the Connect:Direct bridge agent's node network map is not supported.
- Response
- If the operating system platform type for the node has not been defined, either define it within the Connect:Direct bridge agent's node network map or the ConnectDirectNodeProperties.xml file. If the operating system platform type for the node has been defined but is not supported, create a custom Connect:Direct process definition and update the ConnectDirectProcessDefinitions.xml file to select the process whenever the problem node is selected. Consult the MQMFT product documentation for details.
- BFGCD0028E
- The source disposition 'DELETE' is not supported in this context.
- Severity
- 20 : Error
- Explanation
- Source disposition 'DELETE' is not valid in transfers from a Connect:Direct node. The transfer might have completed successfully but the source file has not been deleted.
- Response
- Remove the source disposition parameter from the transfer request and submit the transfer again. Alternatively, define a custom Connect:Direct process and manually configure the source disposition of the process.
- BFGCD9999E
- <insert_0>
- Severity
- 20 : Error
- Explanation
- If this message does not give enough information, check the accompanying error messages for further information.
- Response
- For further information on resolving this error, see the problem determination information on the product website.