Skip to main content

Rumba 8.2.0  -  "File Transfer" "Send" process

if the transfer fails because the destination dataset is too small, I get a B-37 abort message.  When I then try to access the source PC file, the Rumba "File Transfer Error" message says "Unable to open" the PC file.  When I try to access the PC file using Microsoft Word, the error-message says the PC file "is currenlty in use.  Try again later". It appears that Rumba is not freeing the PC file when the transfer fails.  The only way to access the PC file is to shutdown and restart my PC.  Is there a "fix" for this problem?

 

in use by another process.ame dataset. If the mainframe dataset is not large enough, the transfer fails but the PC file cannot be accessed. (See attachment).


#Rumba

Rumba 8.2.0  -  "File Transfer" "Send" process

if the transfer fails because the destination dataset is too small, I get a B-37 abort message.  When I then try to access the source PC file, the Rumba "File Transfer Error" message says "Unable to open" the PC file.  When I try to access the PC file using Microsoft Word, the error-message says the PC file "is currenlty in use.  Try again later". It appears that Rumba is not freeing the PC file when the transfer fails.  The only way to access the PC file is to shutdown and restart my PC.  Is there a "fix" for this problem?

 

in use by another process.ame dataset. If the mainframe dataset is not large enough, the transfer fails but the PC file cannot be accessed. (See attachment).


#Rumba

One option is to be very patient and wait for the file transfer to time out, then the file will be freed. I think the transfer times out after 90 seconds, but it could be longer. I can't find where the timeout delay is configured. If it doesn't time out after a few minutes you might want to use Task Manager to select the Rumba process and end it in lieu of booting your PC.

Rumba 8.2.0  -  "File Transfer" "Send" process

if the transfer fails because the destination dataset is too small, I get a B-37 abort message.  When I then try to access the source PC file, the Rumba "File Transfer Error" message says "Unable to open" the PC file.  When I try to access the PC file using Microsoft Word, the error-message says the PC file "is currenlty in use.  Try again later". It appears that Rumba is not freeing the PC file when the transfer fails.  The only way to access the PC file is to shutdown and restart my PC.  Is there a "fix" for this problem?

 

in use by another process.ame dataset. If the mainframe dataset is not large enough, the transfer fails but the PC file cannot be accessed. (See attachment).


#Rumba

When the "Send" transfer process timed out after 90 seconds, a "File Transfer" box was displayed saying "Timed-out waiting for host screen" with two buttons (Retry or Abort).  I clicked Abort.

I then used Task Manager, selected the Rumba process and I pressed End Process.

But that did not free the PC file.

Rumba 8.2.0  -  "File Transfer" "Send" process

if the transfer fails because the destination dataset is too small, I get a B-37 abort message.  When I then try to access the source PC file, the Rumba "File Transfer Error" message says "Unable to open" the PC file.  When I try to access the PC file using Microsoft Word, the error-message says the PC file "is currenlty in use.  Try again later". It appears that Rumba is not freeing the PC file when the transfer fails.  The only way to access the PC file is to shutdown and restart my PC.  Is there a "fix" for this problem?

 

in use by another process.ame dataset. If the mainframe dataset is not large enough, the transfer fails but the PC file cannot be accessed. (See attachment).


#Rumba

When the "Send" transfer process timed out after 90 seconds, a "File Transfer" box was displayed saying "Timed-out waiting for host screen" with two buttons (Retry or Abort).  I clicked Abort.

I then used Task Manager, selected the Rumba process and I pressed End Process.

But that did not free the PC file.

Rumba 8.2.0  -  "File Transfer" "Send" process

if the transfer fails because the destination dataset is too small, I get a B-37 abort message.  When I then try to access the source PC file, the Rumba "File Transfer Error" message says "Unable to open" the PC file.  When I try to access the PC file using Microsoft Word, the error-message says the PC file "is currenlty in use.  Try again later". It appears that Rumba is not freeing the PC file when the transfer fails.  The only way to access the PC file is to shutdown and restart my PC.  Is there a "fix" for this problem?

 

in use by another process.ame dataset. If the mainframe dataset is not large enough, the transfer fails but the PC file cannot be accessed. (See attachment).


#Rumba

When the "Send" transfer process timed out after 90 seconds, a "File Transfer" box was displayed saying "Timed-out waiting for host screen" with two buttons (Retry or Abort).  I clicked Abort.

I then used Task Manager, selected the Rumba process and I pressed End Process.

But that did not free the PC file.

Rumba 8.2.0  -  "File Transfer" "Send" process

if the transfer fails because the destination dataset is too small, I get a B-37 abort message.  When I then try to access the source PC file, the Rumba "File Transfer Error" message says "Unable to open" the PC file.  When I try to access the PC file using Microsoft Word, the error-message says the PC file "is currenlty in use.  Try again later". It appears that Rumba is not freeing the PC file when the transfer fails.  The only way to access the PC file is to shutdown and restart my PC.  Is there a "fix" for this problem?

 

in use by another process.ame dataset. If the mainframe dataset is not large enough, the transfer fails but the PC file cannot be accessed. (See attachment).


#Rumba

It takes Rumba a long time to successfully Abort as well. Did you wait for the dialog box to close after clicking on Abort before trying to access the file?

Rumba 8.2.0  -  "File Transfer" "Send" process

if the transfer fails because the destination dataset is too small, I get a B-37 abort message.  When I then try to access the source PC file, the Rumba "File Transfer Error" message says "Unable to open" the PC file.  When I try to access the PC file using Microsoft Word, the error-message says the PC file "is currenlty in use.  Try again later". It appears that Rumba is not freeing the PC file when the transfer fails.  The only way to access the PC file is to shutdown and restart my PC.  Is there a "fix" for this problem?

 

in use by another process.ame dataset. If the mainframe dataset is not large enough, the transfer fails but the PC file cannot be accessed. (See attachment).


#Rumba

Yes.  the "File Transfer" dialog box closed a second or two after I clicked Abort.

Terms & ConditionsAccessibility statement