I looked into the problem, and I think if you specify "PROFILE VARSTORAGE(LOW)" at the beginning of your REXX exec, you will be able to run without changing the convert program to flip in and out of 31 bit and not have to worry about it during the life of that particular exec. (make sure you change the program back).
This appears to be the result of the change in z/OS 1.8 that added support for moving the storage obtained for parms above the line. The VARSTORAGE(LOW) will make it run like the pre-1.8 method for the life of the exec that issues the PROFILE VARSTORAGE(LOW) command only. It does not effect the rest of the system and won't effect the TSSO address space (except for your exec). It works on my test system that I have installed the current CBT version of TSSO on with your sample exec. To answer the other person's question, there are pieces of TSSO that have not worked correctly for quite some time, there are control block changes that we have "patched" the module for, but all we really have done is skip some functions to make the "more important" functions work. Brian ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
