On Thu, 8 Jul 2010 08:55:18 -0500, Arthur Gutowski <aguto...@ford.com> wrote:
>On Wed, 7 Jul 2010 16:52:04 -0400, Tim Brown <tbr...@cenhud.com> >wrote: > >>Is there a way to syntax JES2 statements >>We are trying a new config, the old one starts ok >>The new one gets the cancel or end option and we cant >>determine the error. > > >Other than the helpful ideas posted thus far, IBM's textbook answer is to >define a secondary JES2 subsystem and start it under the current primary. >I've never been able to get this to work 100% - always had to edit certain >parms to resolve conflicts with the primary, which means edited back before >going production, which provided the opportunity to introduce typos or >missing/extra comment markers. Kind of defeats the purpose. > Tim, Art: No need to create a secondary JES2, just simply start JES2 with the new parms, under your current JES2. If there's syntax errors, you'll be able to see the messages, if no syntax errors, it will immediately come down: $HASP425 SUBSYSTEM INTERFACE NOT DORMANT, JES2 ALREADY ACTIVE $HASP085 JES2 TERMINATION COMPLETE Although if you do this on a closely watched system, those messages tend to disturb operators a little bit, it helps to warn them before doing it.... Dana ---------------------------------------------------------------------- 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
