This patch has the following fixes for Mover: Binary files are doubling in size using sftp file transfer and becoming corrupt. Issue found in Release: 2.2.0
The problem seems related to a dataset created as an unblocked RECFM=F that is subsequently reblocked. It also seems specific to the z/OS 1.2 / DFSORT release 14.0 LPAR. According to the Ultimizer messages, Ultimizer seems to be changing the block size from 400 to 27998 (RECFM=VB - ?). I was able to replicate the abend using the JCL at the end of the note below.
This issue was especially problematic in V822 due to the small event (J-AREA size ) limit, and is one of the main items improved by 8.2.3. With either release, running the $MAINT job to keep the total number of events below the limit should prevent this from happening. The limit in V822 is approximately 300,000, and the limit in V823 is 1,000,000 events.
Version Manager GUI Causes the Screen to Flicker on a Multi-processor Windows Workstation [1019671] Version Manager Process Size Too Big [1019048] PCLI Locks Up if User Input is Needed [1007521]
DEF325785: duplicate key value violates unique constraint "vrs_2_ppc_pk" when running CBL DEF323341: VM delta library initialized incorrectly DEF320546: Desktop Client Reviews: EXT4700070E: The request to Dimensions CM Pulse was not successful
What is New or Updated in this Patch? 5466 Cannot create a project investment under a Program investment when Request View is set to a custom summary view. 5393 The doc store was not being initialized in every case 5367 Issue data is not retained when transitioning from Issue to Investment
You must ensure that all of your JCL that does a delete/define on the SSV files have the correct IDCAMS definition. You will also need to update the delivered CNTL members INITIAL3 and SVRSTOR as they still have the definitions for versions of SSM/SSV that were appropriate for releases prior to ZMF 7.1.3.03. i.e. the site master record size in ZMF 7.1.3.03 should not be RECORDSIZE(100 4089).
