>What is the purpose of moving the parm to an internal field? That >juststrikes me as broken as designed (BAD). You cannot change the >value, it is truly input only.
It was just an example to visualize my imaginary problem case. I seem to remember that I once wrote a program that was accepting some parameters via PARM field. It seemed to be the easiest way to parse the PARM field when I could make sure it always ends in a space, so I defined a 101 byte variable, initialized with spaces. Maybe not the most elegant way, but anyway it required the PARM to be moved. >It also strikes me as more effort than just >using the parm inplace in this age of reentrent and reusable code >styles. Batch programs need not be either reenterant nor reusable. They are loaded once per job step and called (well attached) once. Just wanted to make my statement. I appreciate the PARM length restriction is under discussion. Whatever the solution will be, it will help. Peter Hunkeler Senior IT Specialist, IBM zSeries Technical Sales Support, Switzerland ---------------------------------------------------------------------- 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
