I just downloaded the "latest" version of ASMPUT from z/OS 2.3 and have some questions.
First off, let me say this is an 'experiment' to see if it would have caught a couple of bugs I found caused by copy/paste errors. The first thing that caught my eye in reading the HLASM 1.6 documentation was the "don't use the XOBJECT or GOFF option". I hope that means "don't use the ADATA subparameter of the GOFF option" otherwise, 64 bit programs won't work (currently we're using the GOFF option on all programs whether they utilize 64 bit code or not although I do have the ADATA option turned on). Second, reading through the READ.ME file, there are caveats about not working on Windows 2000 or later. Since Windows 10 is current and Windows 11 is now available, am I S.O.L on this program? READ.ME also talks about only working with ADATA files from HLASM 1.4. Since 1.6 has been out for a few years now, this seems goofy to me and really limits the use of ASMPUT (which may be moot based on the other two "issues" presented). If any of this is 'correct' (i.e. only works on Windows XP, doesn't work with GOFF), then why don't they remove the documentation and the ASM.SASMPUT2 libraries? Bottom line is that I am trying to figure out a way to avoid some issues that seem to be more prevalent with the use of branch relative instructions (or long displacement instructions in general). Perhaps the structured programming macros would help, I am looking into that. Thanks for the feedback, *Mark Hammack* Senior z/OS Developer Systemware, Inc. [email protected] 214-478-0955 (c)
