You need to review the Control/M CTMAPI function, described in the Control/M User's Guide. This allows you to create/order new 'tables' which essentially define scheduling parameters, such as where the JCL is stored, when to run, dependencies on other jobs etc, time/date restrictions, etc. CTMAPI can be called from Clists, REXX or batch. You can use this to create a 'submit' edit macro to run a stand-alone job, by building a table that just says to run this job now. The job will then go through all the Control/M machinations, including resolving auto-edit variables (those Control/M JCL 'symbols').
There is also the CTMAESIM utility which tests auto-edit variables. I don't think any of the Control/x products are at all well documented. Ant. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Roberts, John J Sent: Tuesday, 8 October 2013 5:33 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: JCL Symbol Resolution We are about to become a new BMC Control-M installation. Part of this involves changing our JCL to reference Control-M symbols. So instead of a plain-jane JOB card, we might have something where the accounting field is supplied as %%ACCT and the JOB CLASS is specified as %%JC. This is all good in PROD, where these symbols are resolved from job definitions by Control-M before submission. But what about unit testing? For one, I don't want to run unit test jobs from Control-M, since our license will count these against our limit. And I don't want to force our developers to edit the JCL before submission, since (a) it would be a PITA, and (b) they would surely forget to cancel the edit, corrupting the member. What I really want is the ability for developers to perform a special "SUBMIT" from their ISPF EDIT session, where: (a) the developer is prompted to resolve the symbols before the JCL text is written to INTRDR, and/or (b) the symbols are resolved from some configuration file before the modified JCL is written to INTRDR. I think that some kind of ISPF EDIT MACRO could do this work, but I have forgotten how to do this. I am hoping that this is a common enough problem that someone else may have developed a solution they could share. Note that I know that there are some things related to Control-M that a simple EDIT Macro could not solve. Stuff like the %%IF-%%ELSE-%%ENDIF sequences and the built in functions for date calculations and character substrings. But these are rare enough that I would be happy with a simple symbol substitution solution. I have asked our sysprogs to pose this question to BMC and CetanCorp. But I suspect that their answer will revolve around their new JCLVERIFY product. If this can work standalone without adding to our license count, that would be great. Otherwise we will need this other solution. Also, I will need to bring this up with the supplier of our current JCL validation utility - the product known as JED (dcmsi.com). This has one nice feature that the new JCLVERIFY lacks, the ability to display the contents of parameter members, both PDS and PANVALET. JED is also capable of validating things like SORT and IDCAMS control statements. John ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send 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
