Humm, Humph... My perspective is that you are essentially requesting a service from MVS/JES. To paraphrase, that request is: "run this job". Rather than enhancing the trigger monitor, I suggest abstracting the layer that is responsible for satisfying the request into a program that you control. This can be done in batch or even more easily in CICS, eliminating the need for MA12 altogether.
The model I have in mind is that MA12 or CKTI, starts the program that processes the request and submits the job to an internal reader. In it's simplest form, the name of the job/proc or whatever (YOUR DESIGN) can be stored in the envrdata, userdata, and/or trigdata. (But not in the applicid--that's where the name of your SIL abstraction layer is stored). In a more sophisticated model, you can define a JOB.SUBMISSSION queue to pass job-submission request messages (YOUR DESIGN). With that approach you can even include, JCL, parameter cards, data records, etc., in-line (as part of the request message). In effect (and with due dilligence to security), you have a general purpose utility that any MQ-enabled process anywhere can submit jobs to MVS. By including in-line data records behind the IEBGENER utility, you even have a makeshift file transfer application--simple, but works. regards, Dennis > -----Original Message----- > From: Roger Lacroix [SMTP:[EMAIL PROTECTED] > Sent: Wednesday, August 27, 2003 1:55 PM > To: [EMAIL PROTECTED] > Subject: Re: MA12 Batch triggering > > Humm, > > I think you misunderstood me. I meant that you stop using MA12 and write your > own trigger monitor program (C or PLI or COBOL). Your new trigger monitor > program would use the APPLCID and/or USERDATA as they wish. > > But most companies don't want to have a custom written trigger monitor. Plus > you would need a compiler / linker on the mainframe. > > If you want help writing the code, let me know. > > later > Roger... > > > Quoting "Potkay, Peter M (PLC, IT)" <[EMAIL PROTECTED]>: > > > I would love to do the simple one Rog. > > > > If I put @TSMT00.MQ.CNTL(MQEX702V) in USERDATA, but what would I put in > > APPLCID? > > > > This assume MQEX702V can be submitted stand alone. > > > > > > -----Original Message----- > > From: Roger Lacroix [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, August 27, 2003 4:11 PM > > To: [EMAIL PROTECTED] > > Subject: Re: MA12 Batch triggering > > > > > > Hi, > > > > Over the years, I have written a couple of trigger monitors to submit JCL > > (with > > a JOB card) rather than a PROC. > > > > It is really straight forward. You can make a simple one or a more robust > > trigger monitor. The simple one would have the PDS(member) in the USERDATA > > field. For the complex one, you would just specify the member and then the > > program would search a list of PDS(s) for the member. > > > > Either way, the program will read the member then submit it to the INTRDR > > (Internal Reader). > > > > I wish I could post the code but I can't (it's not mine). > > > > later > > Roger... > > > > > > Quoting "Potkay, Peter M (PLC, IT)" <[EMAIL PROTECTED]>: > > > > > No, I never had it working. I mean, I had the job itself working A-OK when > > I > > > submitted SUB from inside the member. But someone told me I could not just > > > submit a JCL member like this from a process definition. I had to change > > it > > > to a proc, which are the changes I made below and the reason I posted the > > > first few lines of the member MQEX702B. I think I made the correct changed > > > to it to make it a proc (removed the job card, added PROC to the first > > line > > > and added PEND to the end) > > > > > > > > > Actually I wish I was able to make this work by simply be able to do > > > something like TSO SUB @TSMT00.MQ.CNTL(MQEX702B) in the proccess > > definition, > > > but I guess this is not possible. (This is assuming MQEX702B was back in> > > its > > > original state when it could be run standalaone by just submitting the > > > member.) > > > > > > > > > > > > -----Original Message----- > > > From: Bullock, Rebecca (CSC) [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, August 27, 2003 3:22 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: MA12 Batch triggering > > > > > > > > > Peter, I don't use MA12 and we're not a JES3 shop, but was it working > > before > > > you shut it down? Could it be that a different userid is now associated > > with > > > it, and that userid is causing it to fail in the SMF exit? I'd talk to the > > > SMF exit person and see what would trigger a failure and take it from > > there. > > > -- Rebecca > > > > > > -----Original Message----- > > > From: Hill, Dave [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, August 27, 2003 3:07 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: MA12 Batch triggering > > > > > > > > > Peter - > > > > > > Process name and content > > > EMAIL.SMTP.MSGS > > > USED TO PROCESS MAINFRAME EMAI > > > TO USERS IN > > > > > > MVS > > > //*S010EXE EXEC PGM=MQMAIL > > > //EMAIL DD SYSOUT=(Q,SMTP) > > > //SYSOUT DD SYSOUT=* > > > //UTLITYF DD DUMMY > > > > > > -----Original Message----- > > > From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, August 27, 2003 2:45 PM > > > To: [EMAIL PROTECTED] > > > Subject: MA12 Batch triggering > > > > > > > > > The trigger monitor is up and running. I can send the shutdown message to > > it > > > via CKTIEND and it shuts down as expected. So I start it back up and try > > to > > > drop a message into the triggered queue. The triggered queue name is > > > MQT1.LOCAL.QUEUE and the process definition is named MQT1.LOCAL.QUEUE as > > > well. > > > > > > > > > The problem is, the JCL it produces upon recieving a trigger message > > fails. > > > I suspect because my process definition is incorrect? > > > > > > The JCL I would like to kick off is in @TSMT00.MQ.CNTL(MQEX702B). Here are > > > the first few lines of it: > > > > > > 000001,//MQEX702B PROC > > > > > 000002,//****************************************************************** > > > 000003,//** THIS JCL WILL EXECUTE RN0722PC, WHICH CALLS RN0702PP, THE MQ > > * > > > 000004,//** WRAPPER FOR BATCH PROCESSING. > > * > > > 000005,//** IT ASSUMES THAT THE MA12 SUPPORT PAC WILL BE TRIGGERING IT > > * > > > 000006,//** THAT IS WHY THERE IS NO JOBCARD AT THE TOP. MA12 MAKES THE > > CARD > > > > > 000007,//****************************************************************** > > > 000008,//RN072201 EXEC PGM=DFSRRC00,REGION=9000K, > > > 000009,// PARM=(DLI,DSNMTV01,RF0001P1) > > > 000010,//STEPLIB DD DSN=SYS1.SCSQANLE,DISP=SHR > > > > > > > > > > > > > > > Here is the process def. (I have tried about 800 different variations, > > this > > > is the latest): > > > > > > DEF PROCESS(MQT1.LOCAL.QUEUE) > > > APPLICID('//BTACLIB JCLLIB [EMAIL PROTECTED]') > > > USERDATA('//S1 EXEC PROC=MQEX702B) > > > APPLTYPE('z/OS') > > > > > > > > > Here is the output of the job as it fails bb interpretor: > > > //J7900027 JOB J7211ZZRJB12345678,'P PPOTKAY X77906', * > > > // MSGLEVEL=1,MSGCLASS=H,[EMAIL PROTECTED] > > > //*MAIN CLASS=DB2A > > > //*MAIN SYSTEM=ST1 > > > //* > > > //* JOB SUBMITTED BY CKTIBAT. > > > //* PROCESS: MQT1.LOCAL.QUEUE > > > //* TRIGGERING Q: MQT1.LOCAL.QUEUE > > > //BTACLIB JCLLIB [EMAIL PROTECTED] > > > //S1 EXEC PROC=MQEX702B > > > /*EOF > > > 1 //J7900027 JOB J7211ZZRJB12345678,'P PPOTKAY X77906', > > > // MSGLEVEL=1,MSGCLASS=H,[EMAIL PROTECTED] > > > //*MAIN CLASS=DB2A > > > //*MAIN SYSTEM=ST1 > > > //* > > > //* JOB SUBMITTED BY CKTIBAT. > > > //* PROCESS: MQT1.LOCAL.QUEUE > > > //* TRIGGERING Q: MQT1.LOCAL.QUEUE > > > 2 //BTACLIB JCLLIB [EMAIL PROTECTED] > > > 3 //S1 EXEC PROC=MQEX702B > > > IEFC025I INSTALLATION MODIFIED JCL - //************ JOBCARD > > > ERROR-5 ** > > > > > > > > > and the error messages.... > > > STMT NO. MESSAGE > > > 3 IEFC042I JOB CANCELLED BY INSTALLATION EXIT - IEFUJV > > > 3 IEFC029I EXIT ERROR: IEFUJV ATTEMPTED TO INSERT JCL COMMENTS - > > > STATEM > > > 3 IEFC607I JOB HAS NO STEPS > > > > > > > > > > > > > > > Peter Potkay > > > MQSeries Specialist > > > The Hartford Financial Services > > > [EMAIL PROTECTED] > > > x77906 > > > IBM MQSeries Certified > > > > > > > > > > > > > > > This communication, including attachments, is for the exclusive use of > > > addressee and may contain proprietary, confidential or privileged > > > information. If you are not the intended recipient, any use, copying, > > > disclosure, dissemination or distribution is strictly prohibited. If > > > you are not the intended recipient, please notify the sender > > > immediately by return email and delete this communication and destroy all > > > copies. > > > > > > Instructions for managing your mailing list subscription are provided in > > > the Listserv General Users Guide available at http://www.lsoft.com > > > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > > > > > Instructions for managing your mailing list subscription are provided in > > > the Listserv General Users Guide available at http://www.lsoft.com > > > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > > > > > > > > > > > ************************************************************************** > > > This e-mail and any files transmitted with it may contain privileged or > > > confidential information. It is solely for use by the individual for whom > > > it is intended, even if addressed incorrectly. If you received this e-mail > > > in error, please notify the sender; do not disclose, copy, distribute, or > > > take any action in reliance on the contents of this information; and > > delete > > > it from your system. Any other use of this e-mail is prohibited. Thank you > > > for your compliance. > > > > > > Instructions for managing your mailing list subscription are provided in > > > the Listserv General Users Guide available at http://www.lsoft.com > > > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > > > > > Instructions for managing your mailing list subscription are provided in > > > the Listserv General Users Guide available at http://www.lsoft.com > > > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > > > > > > Instructions for managing your mailing list subscription are provided in > > the Listserv General Users Guide available at http://www.lsoft.com > > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > > > Instructions for managing your mailing list subscription are provided in > > the Listserv General Users Guide available at http://www.lsoft.com > > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
