On Tuesday, 05/05/2009 at 05:19 EDT, Steve Harman <steve.har...@mutualofomaha.com> wrote:
> We have a vm 5.2 system (yes, now unsupported) running RSCS v3.2. I've > been told that we need to be off the old release of RSCS by the end of June > or we'll incur a monthly fine. Apparently you discontinued your license to use RSCS v3.2 a bit too early. > RSCS is now packaged with the base OS. Packaged, yes, but you still have to license the RSCS feature to use the NJE/RJE functions. > Seems like ProgDir shouldn't use it [HLASM] in the examples. It is getting more and more difficult to maintain compatibility with Assembler F. We feel justified in using z/Architecture features and functions, as well as things as simple as long variable names or mixed case. This is especially true of things that talk to CP. None of that, not even AMODE/RMODE, are understood by Assembler F, yet AMODE/RMODE are important in virtual machines > 16MB. If you write exits for IBM products, you need to seriously consider a modern assembler. As others have noted, HLASM isn't your only choice. > Am I headed in the right direction, or am I wasting a lot of my time? If > I get my exits assembled, how do I get the FL540 RSCS to hook them in? Appeal to your IBM rep. If you have licensed the RSCS feature of z/VM 5.4, then they may be willing to let you run RSCS v3.2 (unsupported, of course) for a reasonable migration period. Or perhaps you are already at the end of an agreed-to migration period? Alan Altmark z/VM Development IBM Endicott
