Everyone: There is a tool that fully integrates wtih all scheduler and change management software to automatically make any required changes to JCL for any environment (devl, test, unit test, QA, User Acceptance, Prod, etc.), so the programmers will never have to remember what changes need to be made for any required or desired processing characteristics.
Regards, Mitch McCluhan, Legacy Modernization Consultant www.lcmg.us -----Original Message----- From: Paul Gilmartin <paulgboul...@aim.com> To: IBM-MAIN <IBM-MAIN@LISTSERV.UA.EDU> Sent: Mon, Oct 7, 2013 1:33 pm Subject: Re: JCL Symbol Resolution On 2013-10-07 14:02, Roberts, John J wrote: But what about unit testing? For one, I don't want to run unit test jobs from ontrol-M, since our license will count these against our limit. And I don't ant to force our developers to edit the JCL before submission, since (a) it ould be a PITA, and (b) they would surely forget to cancel the edit, corrupting he member. ACF should be your friend here. And remind them to use VIEW instead f EDIT. > I think that some kind of ISPF EDIT MACRO could do this work, but I have orgotten how to do this. I am hoping that this is a common enough problem that omeone else may have developed a solution they could share. ohn M. has a pretty good solution. It should, however, at least tart with a MACRO command. I'd leave off the SUBMIT to leave the programmer a chance to review efore SUBMIT. -- gil ---------------------------------------------------------------------- or IBM-MAIN subscribe / signoff / archive access instructions, end email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
