Thank you for the explanation! I'll forgo the use of ASMPUT and pursue a different solution for the issue.
Respectfully, *Mark Hammack* Senior z/OS Developer Systemware, Inc. [email protected] 214-478-0955 (c) On Thu, Nov 18, 2021 at 3:49 AM Jonathan Scott <[email protected]> wrote: > Mark Hammack wrote: > > I just downloaded the "latest" version of ASMPUT from z/OS 2.3 and have > > some questions. > > ASMPUT has not been supported at all since 2017, as announced in > APAR PI81310. It was probably last built (or possibly just > patched) in 2004, for HLASM 1.4. The last functional update was > probably the initial z/Architecture support in around 1999. > > It can still be run but needs some Windows compatibility options > enabled. To install it, you probably need to rename ASMPUTW.EXE > to ASMPUTW.ZIP as the self-extracting part does not work any > more. To be able to use it at all one must first assemble the > sample ADATA exit ASMAXADR, which converts the current ADATA > format to the HLASM R4 format, then assemble each program using > that ADATA exit, and download the ADATA files to the > workstation. > > ASMPUT was originally built for OS/2 (I think in Prolog and a > dialect of C) and was ported to Windows. The compiler which was > used on Windows ceased being supported around HLASM 1.4 and > could no longer even be used after licenses expired. Attempts > were made to port ASMPUT to similar supported compilers or to > another language such as Java, but little progress was made, > so in 2017 the previous HLASM team made the decision to admit > defeat and drop support for it. > > The documentation should probably be mostly retained because > ASMPUT can still just about be used, but it needs to clarify the > current situation, and I would agree that it should no longer be > advertised as a useful part of the Toolkit. However, it seems > that when the previous team decided to drop support, they did > not take any action to update any documentation. I have created > a work item to get the documentation and Toolkit information > updated when we can find the time, but I don't know when that > will be. > > Jonathan Scott, HLASM > IBM Hursley, UK >
