In a recent note Ray Mullins said: > Date: Thu, 12 May 2005 16:03:50 -0700 > > Because...PARM was originally intended for passing of small values of data. > If you needed to pass more data than 100 bytes, that was a job for a control > That was then. This is now.
> card data set. Only the C/C++ compiler (from what I've seen in my > experience) has that capability. > Which capability? Pass or Receive? For examples of both, I've routinely passed much over 100 bytes from Rexx "address ATTCHMVS ASMA90" to HLASM, which properly received and processed it. I know, painfully, because when I attempted to report a HLASM bug (several releases ago; now well fixed), HLASM support asked me to re-create it with JCL. When JCL choked on the PARM length, I fired off a SEV2 on the JCL error message, citing HLASM's request that I supply the equivalent JCL. (The bug did _not_ depend on the PARM length; I was ultimately able to re-create it with a parm <=100 characters.) -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
