Closed as fixed if next.
1. Not recognizing the -INC in a BMS map (or else just giving wrong error message) 2. Not accepting 3278 as a TERM value in BMS Maps. 3. "Breakage" of ABMSParser.dll during a Verification Parse. 1. The "-INC" statement was used in a FEW (I think 3) BMS Maps. This was flagged with the following error message: Unsupported Construction '-INC' Apparently, there is NO problem using this construction on "z" and it seems logical that it should work with ATW. Note that the message was NOT that the copybook could not be opened (which is what I would have expected). 2. On one of the BMS Macros, a "term" value of 3278 was used (instead of 3270) and this was flagged as an error. We changed it to 3270 but it is not clear why 3278 should not work. 3. For one of the BMS macro files, we received the following error (and ONLY the following error): Internal error: ABMSParser.dll : ABMSParser().
We have successfully reproduced the errors for this case. The DLL error was caused by two programming mistakes. On line 682, there is an extra comma after IC. Remove this and the line should read ATTRB=(UNPROT,NORM,IC) The second was on line 686, also cause by an extra comma. Change the line to read ATTRB=(UNPROT,NORM) Making these changes will allow the file to verify correctly. The Internal Error that is cause by these syntax errors is not very helpful, but Birch gives a more meaningful error message. As for the three -INC errors. We have successfully reproduced these issues in both Sycamore and Birch. We are submitting them to Development for investigation. For the time being, if you just comment out those lines, then the files will verify correctly. The correct screens are created and should be fine for the Proof of Concept. In the mean time, our Development team will be looking into fixing this error.
BMS map errors
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels