Task: Troubleshoot Your Sterling B2B Integrator and WebSphere MQ File Transfer Edition Configuration

There are several things to check if your transfer is not successful. Common reasons for failure include errors in the WMQFTE User Map, errors in the file name location, and typing errors. WebSphere® MQ File Transfer Edition error messages, which begin with BFG, are shown in WebSphere MQ Explorer. These messages can provide useful troubleshooting information. Consult the WebSphere MQ File Transfer Edition documentation or work with the WebSphere MQ File Transfer Edition administrator when you see these messages.

Transfer Isn't Progressing

If the transfer starts and doesn't seem to be progressing, verify that the WebSphere MQ File Transfer Edition Agent Adapter and the FTP Server Adapter are running.

Is the Source File Location Correct?

A transfer will fail if it can not find the source file. For Sterling B2B Integrator outbound transfers, the source file location is always a mailbox. Make sure the location specified in the transfer is correct.

Is the MQMD User ID and Sterling B2B Integrator User Mapping Correct?

Transfers will fail if the user mapping on Sterling B2B Integrator is incorrect. If you have MQ Explorer installed, right-click on the transfer record in the Transfer Log and select Properties. The properties lists the MQMD User Id for that transfer. Make sure that the MQMD User Id for the transfer is in the WMQFTE User Map and is associated with the correct local user and password.

The Transfer Succeeded But the File Isn't in The Directory You Expect It To Be

By default, WebSphere MQ File Transfer Edition transfers are set to create subdirectories in the destination locations. Make sure you spelled the destination location correctly. If you wanted the file to be placed in "Source" and entered "Soucre", the transfer created a new folder and put the file there. You can prevent this from happening in Sterling B2B Integrator by setting a Policy for the FTP Server Adapter so that it can not create subdirectories.

MQ Explorer shows the error: BFGSS0030W: The agent is already acting as the source agent for the maximum number of file transfer operations and unable to queue further requests, due to the queued transfer limit of 1000 being reached. The new transfer request will not be carried out

If there are too many transfers queued up by the source agent, the WebSphere MQ File Transfer Edition Agent Adapter will start rejecting transfers. The default maximum number of transfers is 1000. If the number of transfers exceeds 1000, transfers are rejected. If you see this error, you can increase the number of transfers by increasing the value of the maxQueuedTransfer parameter for the WebSphere MQ File Transfer Edition Agent Adapter with the 'Additional Agent Properties File' option. Create an agent.properties file with an entry for the maxQueuedTransfer parameter. Set the parameter to a value over 1000. Edit the WebSphere MQ File Transfer Edition Agent Adapter to use the properties file you created.

The WebSphere MQ File Transfer Edition Agent Adapter Queue Manager Script Does Not Run Correctly on z/OS

The WebSphere MQ File Transfer Edition Agent Adapter script can get corrupted if it is not transferred to z/OS in a way that properly converts the file. The file needs to be converted to EBCDIC and to retain the proper end of line markings or it will not work properly. This could be an issue if you download the script to a Windows machine and then FTP it to z/OS. You can do one of two things:

  1. Click the link for the file in the Sterling B2B Integrator dashboard and download the file.
  2. Chose Open With and select WORDPAD.exe as program to use.
  3. From Wordpad, use 'Save As' and select plain text.
  4. Use FTP in text mode to copy the file to z/OS and run appropriate JCL command to have queue manager process the file.
Or
  1. Click the link for the file in the Sterling B2B Integrator dashboard and download the file to the Windows system.
  2. From Windows (DOS) command prompt, run c:\>type <WebSphere MQ File Transfer Edition agent name>-create.msqc | FIND "" /V > <WMQFTE agent name>-create2.msqc.
  3. Use FTP text mode to copy the new <WebSphere MQ File Transfer Edition agent name>-create2.msqc file to z/OS and run the appropriate JCL command to have the queue manager process the file.