This folder contains VMAC7072.EBC.BIN and VMAC7072.SAS.TXT files from MXG 40.04 and are REQUIRED to circumvent ERRORS in MXG 39.09 or earlier, when you install APARs OA61811 and OA52602, PTFs UJ07881 (z/OS 2.3), UJ07990 (z/OS 2.4) or UJ07989 (z/OS 2.5). The folder also contains FORMATS.EBC.BIN and FORMATS.SAS.TXT and if if you are at 37.37 or earlier you will need to copy either the file FORMATS.EBC.BIN or FORMATS.SAS.TXT and update your FORMAT library. The circumvention works for MXG 35.12 and later for New Datasets; for earlier MXG, you need the 40.04 install. BUT THOSE FILES ONLY CIRCUMVENT THE MXG ERROR AND WE STRONGLY RECOMMEND THAT INSTEAD OF JUST CIRCUMVENTING THE ERROR, YOU SHOULD INSTALL 40.04, WHICH IS MUCH SIMPLER THAN THE CIRCUMVENTION AND PROVIDES MANY OTHER IMPORTANT UPDATES (E.G. SUPPORT FOR CICS/TS 6.1, z16 PROCESSOR, etc.). USE THE FORM AT HTTPS://WWW.MXG.COM/SOFTWARE_DOWNLOAD_REQUEST FOR 40;04. To circumvent, you need to copy the correct VMAC7072 file into your "USERID.SOURCLIB(VMAC7072). The file VMAC7072.SAS.TXT is the ascii text for execution on ASCII. File VMAC7072.EBC.BIN is the EBCDIC text for execution on z/OS. The VMAC7072.EBC file must be copied as BINARY into your z/OS tailoring PDS library as USERID.SOURCLIB(VMAC7072). Change 40.078 MXG 39.09 and earlier fail with APAR OA61811/OA62502, VMAC7072 due to an MXG error for SMF 72 Subtype 3 TYPE72GO that Jun 25, 2022 failed to test for new fields after the last segment, which caused INPUT mis-alignment and invalid data values. PTFs: z/OS 2.3 UJ07991 PTFs: z/OS 2.4 UJ07990 PTFs: z/OS 2.5 UJ07989 -WE STRONGLY SUGGEST YOU INSTALL THE CURRENT MXG 40.04 WHICH AVOIDS THE COMPLEXITY OF THE BELOW CIRCUMVENTION AND PROVIDES SIGNIFICANT OTHER ENHANCEMENTS AFTER YOUR . BACKLEVEL VERSION. PLEASE USE THE FORM AT HTTPS://WWW.MXG.COM/SOFTWARE_DOWNLOAD_REQUEST You can circumvent this MXG error by: -Downloading files at http://www.mxg.com/downloads/ The APAR inserted new fields in SMF 72 Subtype 3 TYPE72GO that exposed an MXG coding error that failed to test for new added fields after the last new segment, causing the INPUT misalignment and invalid data values to be created. There MAY be INVALID DATA FOR R723IFAT messages or other fields printed, but those are accidental and there might not be ANY log messages that the error occurred. And even if there are INVALID DATA messges, they do not set a CONDITION CODE, so there may be no clue on the log that the error occurred. MXG 39.39 thru MXG 40.03 correctly input the new data. but only this change or MXG 40,04 has the protection for additional new fields.