If the program wants to parse the parm field using strtok (for example), then the field is no longer read-only. Wayne Driscoll Product Developer Western Metal Supply NOTE: All opinions are strictly my own.
<snip> </snip> What is the purpose of moving the parm to an internal field? That just strikes me as broken as designed (BAD). You cannot change the value, it is truly input only. It also strikes me as more effort than just using the parm inplace in this age of reentrent and reusable code styles. All I'm saying is that it takes two objects to create this error. Your production program must do things incorrectly today AND your production JCL must change. If it works today, then only a change to one of these two (hopefully) controlled objects can break it. Unless you just let your production JCL be changed willy-nilly you are at no risk of exposure. [EMAIL PROTECTED] The most effective type of birth control is learning Cobol. -DT ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
