On Mon, 7 Aug 2006 00:03:26 -0400, Robert A. Rosenberg <[EMAIL PROTECTED]> wrote:
>At 22:37 -0500 on 08/05/2006, Tom Marchant wrote >about Re: WHY IS JCL ALLERGIC TO LOWER CASE?: > >>On Sat, 5 Aug 2006 23:01:10 -0400, Robert A. Rosenberg <[EMAIL PROTECTED]> >>wrote: >>> >>>>I forget what the JES3 equivalent would be but EXIT 6 in JES2 would be >>>>a simple place to put the code if you wanted to have that feature in >>>>your shop. The specs would be interesting. >>> >>>1) Clone the card image >>>2) OC the cloned image with 80X'40' (I do not think any data that >>>would validly appear on the card except for lower case letters would >>>be altered) or use a TR with a LC->UC table if you are paranoid. >>>3) Scan the cloned image for parms that need to be mixed/lower case >>>(Path= and Parm= for example). >>>4) Copy the version in the original for these fields into the cloned copy. >>>5) Optionally also copy comments. >>>6) Replace the original with the updated cloned copy. >>> >>>Note: Before step 1, you can do a sanity-check by TRTing for lower >>>case and bypassing the whole routine if none are found. >>> >>>I'm sure these specs can be refined but I think they are a good start. >>> >>This is not specs. it is rather a proposed implementation of an >>incompletely specified function. e.g. step 3. > >I admit that I commingled "Here is what needs to be done" >specifications with some "Here is how to do it" implementation >details. The only step that needs expansion to get a full set of >instructions on what needs to be done is step 3 (which you noted) >where I gave a generic description and examples in lieu of listing >each JCL Keyword that can take mixed case parameters as opposed to >needing Upper Case values. The major one a left off was that any >quoted string needs to be reset to its content from the original >copy. Are there any other Keywords that take mixed case (both PARM >and PATH take quoted strings at least in the mixed case situation). > You did not write program specifications. You gave your opinion of how to implement the specs once they were written. I would have done it differently. The only "steps" that contain any hint of program specifications are 3 and 5. They are inadequate. Statements 1, 2, 4 and 6 have no place in program specifications. Tom Marchant ---------------------------------------------------------------------- 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
