D3 and mvBase

Hey, Folks, just found a bug in MVSP version 1.8.5 for mvBase. There was an optimization introduced to speed up the process of sending data from mvBase to the Toolkit via MVSP and the Workstation. Prior to 1.8.5, data was sent a byte at a time. Now it's a block transfer. Only problem is the block size is limited to 100K by the environment and MVSP was not enhanced to send multiple 100K blocks. If a larger than 100K block is queued to return, MVSP will fall into the BASIC debugger.

Engineering has been alerted and they're working on it. Meanwhile, if you're using the Toolkit against mvBase and the MVSP version is 1.8.5, you should use your own paging solution to make sure that your return packet does not exceed 100K.

------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------

Update from Engineering: It's actually NOT MVSP 1.8.5 but rather mvBase 3.3.2. There was a correction made to something else that broke this. Engineering is working on an mvBase patch that will fix this problem. So stay tuned!

------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------

Original Message:
Sent: 08-20-2021 14:16
From: Brian Cram
Subject: mvBase MVS Toolkit 100K Packet Size Limit

Hey, Folks, just found a bug in MVSP version 1.8.5 for mvBase. There was an optimization introduced to speed up the process of sending data from mvBase to the Toolkit via MVSP and the Workstation. Prior to 1.8.5, data was sent a byte at a time. Now it's a block transfer. Only problem is the block size is limited to 100K by the environment and MVSP was not enhanced to send multiple 100K blocks. If a larger than 100K block is queued to return, MVSP will fall into the BASIC debugger.

Engineering has been alerted and they're working on it. Meanwhile, if you're using the Toolkit against mvBase and the MVSP version is 1.8.5, you should use your own paging solution to make sure that your return packet does not exceed 100K.

------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------

And the patch is done. It's a one-off patch and as such not something we post on the Community Portal. If you're having this problem, please contact Rocket mvBase Support and we'll give you the patch and help you get it installed.

------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------

Original Message:
Sent: 08-20-2021 14:44
From: Brian Cram
Subject: mvBase MVS Toolkit 100K Packet Size Limit

Update from Engineering: It's actually NOT MVSP 1.8.5 but rather mvBase 3.3.2. There was a correction made to something else that broke this. Engineering is working on an mvBase patch that will fix this problem. So stay tuned!

------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software

Original Message:
Sent: 08-20-2021 14:16
From: Brian Cram
Subject: mvBase MVS Toolkit 100K Packet Size Limit

Hey, Folks, just found a bug in MVSP version 1.8.5 for mvBase. There was an optimization introduced to speed up the process of sending data from mvBase to the Toolkit via MVSP and the Workstation. Prior to 1.8.5, data was sent a byte at a time. Now it's a block transfer. Only problem is the block size is limited to 100K by the environment and MVSP was not enhanced to send multiple 100K blocks. If a larger than 100K block is queued to return, MVSP will fall into the BASIC debugger.

Engineering has been alerted and they're working on it. Meanwhile, if you're using the Toolkit against mvBase and the MVSP version is 1.8.5, you should use your own paging solution to make sure that your return packet does not exceed 100K.

------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------