Re: MA12 Batch triggering
Of course, of course, you are right on the mark. Make sure you spell the address correctly before you replace the mailman. > -Original Message- > From: Randy J Clark [SMTP:[EMAIL PROTECTED] > Sent: Wednesday, August 27, 2003 4:52 PM > To: [EMAIL PROTECTED] > Subject: Re: MA12 Batch triggering > > Wow all this because so far they are unable to get past basically what I > believe to be a syntax error. > > We currently use the MA12 suportpac without any problems. Seems so far to > be straight forward and reliable. One thing we like about it is that it > allows us to NOT submit a production Job to the internal reader - as doing > so is a no-no in this and many other shops. > > The desire here is that all jobs to be 'scheduled' by the production > scheduler. In the case of MA12 triggered jobs the job is scheduled and > immediately released by the production scheduling software, the job is then > archived like any other scheduled production job. > > Additionally most analysts appreciate JCL being in JCL libraries and PROCs > in PROC libraries. Why because when researching a problem nothing causes > more grief than code in JCL libraries or JCL in code libraries as this is > the last place one would think to look. > > But if one desires to reinvent a perfectly good wheel - please send me a > copy as one can never have to many wheels. -smile I am. > > > > > > "Miller, Dennis" > <[EMAIL PROTECTED]To: [EMAIL PROTECTED] > OM> cc: > Sent by: MQSeriesSubject: Re: MA12 Batch triggering > List > <[EMAIL PROTECTED] > N.AC.AT> > > > 08/27/2003 04:27 > PM > Please respond to > MQSeries List > > > > > > > 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 PROT
Re: MA12 Batch triggering
It works!
The problem was in the JOBCARD all along. (Probably something quirky to our
environment all along, but I am posting the solution in case anyone has a
similiar problem and to restore faith in MA12!)
Below is a sample of the JCL that is now being produced by the trigger
monitor. Notice the new JobCard, and lines 2 and 3, which are the parameters
I have coded in MQ that are being passed to the batch trigger monitor. (Line
2 is the APPLCID and Line 3 is the USERDATA).
//JCLLIB [EMAIL PROTECTED] would not work. The space is needed on
between the // and the JCLLIB. If you don't have the space, the following
error comes out:
STMT NO. MESSAGE
2 IEFC605I UNIDENTIFIED OPERATION FIELD
3 IEFC612I PROCEDURE MQEX702B WAS NOT FOUND
Line 4 and everything below is exactly what is in @TSMT00.MQ.CNTL(MQEX702B).
One change I had to make in MQEX702B is I had to remove the instream DD
statements.
For example
71,//DDITV02 DD *
72, DB2A,SYS1,DSNMIN10,,R,-,RN070001,RN0722V1,RN0722PC
was replaced with
70,//DDITV02 DD [EMAIL PROTECTED](DDITV02),DISP=SHR
and the DDITV02 member simply has what was originally in line 72
If you dont replace the instream DD statements, you get Invalid JCL
statements (IEFC601I INVALID JCL STATEMENT)
1 //RN072203 JOB KM111CWPRD,'POTKAY X77906 ',
// MSGCLASS=H,MSGLEVEL=1,[EMAIL PROTECTED]
//***
//** THIS JCL WILL EXECUTE RN0722PC, WHICH CALLS RN0702PP, THE MQ **
//** WRAPPER FOR BATCH PROCESSING. **
//***
//*MAIN CLASS=DB2A
//*MAIN SYSTEM=ST1
//* JOB SUBMITTED BY CKTIBAT.
//* PROCESS: MQT1.LOCAL.QUEUE
//* TRIGGERING Q: MQT1.LOCAL.QUEUE
2 // JCLLIB [EMAIL PROTECTED]
3 //S1 EXEC MQEX702B
4 XXMQEX702B PROC
XX***
and below this is just the rest of mt JCL that I wanted to kick off all
along.
What an experience
-Original Message-
From: Robert Broderick [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 28, 2003 7:27 AM
To: [EMAIL PROTECTED]
Subject: Re: MA12 Batch triggering
Without looking this up and trying to offer a suggestion (wrong or right)
Can you have "BTACLIB" after the "//" on the JCLLIB
card
"//BTACLIB JCLLIB [EMAIL PROTECTED]"
bobbee
>From: Randy J Clark <[EMAIL PROTECTED]>
>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: MA12 Batch triggering
>Date: Wed, 27 Aug 2003 15:32:43 -0700
>
>
>(See attached file: temp.txt)
>
>
>Are you sure your setup is correct. Here is how we do it. Also you
>mentioned a PEND at the end of the PROC are you sure you need this since
>the proc is cataloged not instream.Please note the space between '//
>and exec' we do not user the userdata field at all
>
>
>
>TEST process definition
>DEFINE PROCESS('PR.H_HAL_010_BILL_OF_LADING.000') +
>DESCR('Process for batch job TH1MPU09') +
>APPLTYPE(MVS) +
>APPLICID('// EXEC TH1MPU09') REPLACE
>
>We do the following in our test environment.
>
>
>TEST Proc
>
>//TH1MPU09 PROC
>//*
>//STEP010 EXEC PGM=IEBGENER
>//SYSINDD DUMMY
>//SYSOUT DD SYSOUT=X
>//SYSUT1 DD DSN=TP.HAL.NEW.MINIJCL(TH1MPU09),DISP=SHR
>//SYSUT2 DD SYSOUT=(A,INTRDR)
>//SYSPRINT DD SYSOUT=X
>//
>
>
>In production we execute a proc which adds a production job to our
>production schedule for immediate release.
>
>PRODUCTION
>
>DEFINE PROCESS('PR.H_HAL_010_BILL_OF_LADING.000') +
>DESCR('Process for batch job H1MPU09P') +
>APPLTYPE(MVS) +
>APPLICID('// EXEC CU01AA,MEM=H1MPU09P') REPLACE
>
>
>here is the PRODUCTION proc CU01AA
>
>//CU01AA PROC MEM=
>//* LAST UPDATED BY
>//
>//* ZEKESET STEP TO COMMUNICATE COMMAND REQUEST TO SCHEDULER - ZEKE *
>//
>//CU01AA10 EXEC PGM=ZEKESET
>//SYSOUT DD SYSOUT=M,DEST=CENTRAL
>//SYSUDUMP DD SYSOUT=X,FCB=F800,DEST=CENTRAL
>//SYSABEND DD SYSOUT=X,FCB=F800,DEST=CENTRAL
>//SYSPRINT DD SYSOUT=M,FCB=F800,DEST=CENTRAL
>//SYSIN DD DSN=HP.DPC.A2414(&MEM),DISP=SHR
>//*** END OF PROC
>
>
>
>
>
> Roger Lacroix
> <[EMAIL PROTECTED]To:
>[EMAIL PROTECTED]
> ALWARE.BIZ> cc:
> Sent by: MQSeries Subject: Re: MA12 Batch
>triggering
Re: MA12 Batch triggering
I am using MA12 successfully and pretty much "out of the box".
The only thing I noticed was that your jcl library (@TSMT00.MQ.CNTL) doesn't
match the name in your process def (@TSMT00.MQ.CNT1). I assume this is a
typo in the email.
J
-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:
01,//MQEX702B PROC
02,//**
03,//** THIS JCL WILL EXECUTE RN0722PC, WHICH CALLS RN0702PP, THE MQ *
04,//** WRAPPER FOR BATCH PROCESSING. *
05,//** IT ASSUMES THAT THE MA12 SUPPORT PAC WILL BE TRIGGERING IT*
06,//** THAT IS WHY THERE IS NO JOBCARD AT THE TOP. MA12 MAKES THE CARD
07,//**
08,//RN072201 EXEC PGM=DFSRRC00,REGION=9000K,
09,// PARM=(DLI,DSNMTV01,RF0001P1)
10,//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
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.
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
Re: MA12 Batch triggering
Without looking this up and trying to offer a suggestion (wrong or right)
Can you have "BTACLIB" after the "//" on the JCLLIB
card
"//BTACLIB JCLLIB [EMAIL PROTECTED]"
bobbee
From: Randy J Clark <[EMAIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: MA12 Batch triggering
Date: Wed, 27 Aug 2003 15:32:43 -0700
(See attached file: temp.txt)
Are you sure your setup is correct. Here is how we do it. Also you
mentioned a PEND at the end of the PROC are you sure you need this since
the proc is cataloged not instream.Please note the space between '//
and exec' we do not user the userdata field at all
TEST process definition
DEFINE PROCESS('PR.H_HAL_010_BILL_OF_LADING.000') +
DESCR('Process for batch job TH1MPU09') +
APPLTYPE(MVS) +
APPLICID('// EXEC TH1MPU09') REPLACE
We do the following in our test environment.
TEST Proc
//TH1MPU09 PROC
//*
//STEP010 EXEC PGM=IEBGENER
//SYSINDD DUMMY
//SYSOUT DD SYSOUT=X
//SYSUT1 DD DSN=TP.HAL.NEW.MINIJCL(TH1MPU09),DISP=SHR
//SYSUT2 DD SYSOUT=(A,INTRDR)
//SYSPRINT DD SYSOUT=X
//
In production we execute a proc which adds a production job to our
production schedule for immediate release.
PRODUCTION
DEFINE PROCESS('PR.H_HAL_010_BILL_OF_LADING.000') +
DESCR('Process for batch job H1MPU09P') +
APPLTYPE(MVS) +
APPLICID('// EXEC CU01AA,MEM=H1MPU09P') REPLACE
here is the PRODUCTION proc CU01AA
//CU01AA PROC MEM=
//* LAST UPDATED BY
//
//* ZEKESET STEP TO COMMUNICATE COMMAND REQUEST TO SCHEDULER - ZEKE *
//
//CU01AA10 EXEC PGM=ZEKESET
//SYSOUT DD SYSOUT=M,DEST=CENTRAL
//SYSUDUMP DD SYSOUT=X,FCB=F800,DEST=CENTRAL
//SYSABEND DD SYSOUT=X,FCB=F800,DEST=CENTRAL
//SYSPRINT DD SYSOUT=M,FCB=F800,DEST=CENTRAL
//SYSIN DD DSN=HP.DPC.A2414(&MEM),DISP=SHR
//*** END OF PROC
Roger Lacroix
<[EMAIL PROTECTED]To:
[EMAIL PROTECTED]
ALWARE.BIZ> cc:
Sent by: MQSeries Subject: Re: MA12 Batch
triggering
List
<[EMAIL PROTECTED]
C.AT>
08/27/2003 01:10 PM
Please respond to
MQSeries List
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
&
Re: MA12 Batch triggering
Wow all this because so far they are unable to get past basically what I believe to be a syntax error. We currently use the MA12 suportpac without any problems. Seems so far to be straight forward and reliable. One thing we like about it is that it allows us to NOT submit a production Job to the internal reader - as doing so is a no-no in this and many other shops. The desire here is that all jobs to be 'scheduled' by the production scheduler. In the case of MA12 triggered jobs the job is scheduled and immediately released by the production scheduling software, the job is then archived like any other scheduled production job. Additionally most analysts appreciate JCL being in JCL libraries and PROCs in PROC libraries. Why because when researching a problem nothing causes more grief than code in JCL libraries or JCL in code libraries as this is the last place one would think to look. But if one desires to reinvent a perfectly good wheel - please send me a copy as one can never have to many wheels. -smile I am. "Miller, Dennis" <[EMAIL PROTECTED]To: [EMAIL PROTECTED] OM> cc: Sent by: MQSeries Subject: Re: MA12 Batch triggering List <[EMAIL PROTECTED] N.AC.AT> 08/27/2003 04:27 PM Please respond to MQSeries List 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, Pete
Re: MA12 Batch triggering
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
Re: MA12 Batch triggering
(See attached file: temp.txt)
Are you sure your setup is correct. Here is how we do it. Also you
mentioned a PEND at the end of the PROC are you sure you need this since
the proc is cataloged not instream.Please note the space between '//
and exec' we do not user the userdata field at all
TEST process definition
DEFINE PROCESS('PR.H_HAL_010_BILL_OF_LADING.000') +
DESCR('Process for batch job TH1MPU09') +
APPLTYPE(MVS) +
APPLICID('// EXEC TH1MPU09') REPLACE
We do the following in our test environment.
TEST Proc
//TH1MPU09 PROC
//*
//STEP010 EXEC PGM=IEBGENER
//SYSINDD DUMMY
//SYSOUT DD SYSOUT=X
//SYSUT1 DD DSN=TP.HAL.NEW.MINIJCL(TH1MPU09),DISP=SHR
//SYSUT2 DD SYSOUT=(A,INTRDR)
//SYSPRINT DD SYSOUT=X
//
In production we execute a proc which adds a production job to our
production schedule for immediate release.
PRODUCTION
DEFINE PROCESS('PR.H_HAL_010_BILL_OF_LADING.000') +
DESCR('Process for batch job H1MPU09P') +
APPLTYPE(MVS) +
APPLICID('// EXEC CU01AA,MEM=H1MPU09P') REPLACE
here is the PRODUCTION proc CU01AA
//CU01AA PROC MEM=
//* LAST UPDATED BY
//
//* ZEKESET STEP TO COMMUNICATE COMMAND REQUEST TO SCHEDULER - ZEKE *
//
//CU01AA10 EXEC PGM=ZEKESET
//SYSOUT DD SYSOUT=M,DEST=CENTRAL
//SYSUDUMP DD SYSOUT=X,FCB=F800,DEST=CENTRAL
//SYSABEND DD SYSOUT=X,FCB=F800,DEST=CENTRAL
//SYSPRINT DD SYSOUT=M,FCB=F800,DEST=CENTRAL
//SYSIN DD DSN=HP.DPC.A2414(&MEM),DISP=SHR
//*** END OF PROC
Roger Lacroix
<[EMAIL PROTECTED]To: [EMAIL PROTECTED]
ALWARE.BIZ> cc:
Sent by: MQSeries Subject: Re: MA12 Batch triggering
List
<[EMAIL PROTECTED]
C.AT>
08/27/2003 01:10 PM
Please respond to
MQSeries List
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 tr
Re: MA12 Batch triggering
Thanks Roger, Im gonna give this another shot tomorrow. I am probably missing somethin really small and insignificant. What I was able to get done now is that I have a member that works fine when I manually sub it. I cut and paste its JobCard out and stuck it into MA12's JobCard parameter. MA12 now builds the dynamic JCL by putting the header at the start of this new JCL. All I gotta figure out know is how to get 1 or 2 lines of JCL code that will call out to another set of JCL and then put that info into the MQ process definition. Its not even an MQ issue at this point. I would have the same problem whether I use MA12 or write my own trigger monitor. The crux of the problem is how do I properly call JCL member B from (dynamically-built-by-MA12) JCL member A? I gotta go bug the mainframe gurus here tomorrow. (Our mainframe MQ expert is on vaca this week, so I inherited this task). They'll probably add a period or a / to my JCL and it will work all of a sudden (that always seems to be the nature of the JCL errors anyway - its the stupidest thing that is missing.) That reminds me, go to mp3.com and do a search on "The System Administrator Song". Funny. -Original Message- From: Roger Lacroix [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 27, 2003 4: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
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: > > > > 01,//MQEX702B PROC > > > 02,//** > > 03,//** THIS JCL WILL EXECUTE RN0722PC, WHICH CALLS RN0702P
Re: MA12 Batch triggering
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:
>
> 01,//MQEX702B PROC
>
02,//**
> 03,//** THIS JCL WILL EXECUTE RN0722PC, WHICH CALLS RN0702PP, THE MQ
*
> 04,//** WRAPPER FOR BATCH PROCESSING.
*
> 05,//** IT ASSUMES THAT THE MA12 SUPPORT PAC WILL BE TRIGGERING IT
*
> 06,//** THAT IS WHY THERE IS NO JOBCARD AT THE TOP. MA12 MAKES THE
CARD
>
07,//**
> 08,//RN072201 EXEC PGM=DFSRRC00,REGION=9000K,
> 09,// PARM=(DLI,DSNMTV01,RF0001P1)
> 10,//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.
>
Re: MA12 Batch triggering
I believe there was a member of the NJ MQ User's Group who had written a TSO
method described below. I went to the site but did not see it.
On www.google.com a search brought up a TSO method (looks like PL1) on topic
at the following site:
http://www.mainframeweek.com/code/showcode.php/0014/mw14mq1.txt
-Original Message-
From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 27, 2003 3:33 PM
To: [EMAIL PROTECTED]
Subject: Re: MA12 Batch triggering
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:
01,//MQEX702B PROC
02,//**
03,//** THIS JCL WILL EXECUTE RN0722PC, WHICH CALLS RN0702PP, THE MQ *
04,//** WRAPPER FOR BATCH PROCESSING. *
05,//** IT ASSUMES THAT THE MA12 SUPPORT PAC WILL BE TRIGGERING IT*
06,//** THAT IS WHY THERE IS NO JOBCARD AT THE TOP. MA12 MAKES THE CARD
07,//**
08,//RN072201 EXEC PGM=DFSRRC00,REGION=9000K,
09,// PARM=(DLI,DSNMTV01,RF0001P1)
10,//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
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:
>
> 01,//MQEX702B PROC
> 02,//**
> 03,//** THIS JCL WILL EXECUTE RN0722PC, WHICH CALLS RN0702PP, THE MQ *
> 04,//** WRAPPER FOR BATCH PROCESSING. *
> 05,//** IT ASSUMES THAT THE MA12 SUPPORT PAC WILL BE TRIGGERING IT*
> 06,//** THAT IS WHY THERE IS NO JOBCARD AT THE TOP. MA12 MAKES THE CARD
> 07,//**
> 08,//RN072201 EXEC PGM=DFSRRC00,REGION=9000K,
> 09,// PARM=(DLI,DSNMTV01,RF0001P1)
> 10,//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
>
Re: MA12 Batch triggering
As you may already know, you don''t have to use MA12
for batch triggering. Instead, you can get CICS to
trigger the JCL. I think the latter is just easier set
up.
Just a thought
Ruzi
--- "Bullock, Rebecca (CSC)" <[EMAIL PROTECTED]> wrote:
> 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:
>
> 01,//MQEX702B PROC
>
02,//**
> 03,//** THIS JCL WILL EXECUTE RN0722PC, WHICH
> CALLS RN0702PP, THE MQ *
> 04,//** WRAPPER FOR BATCH PROCESSING.
> *
> 05,//** IT ASSUMES THAT THE MA12 SUPPORT PAC
> WILL BE TRIGGERING IT*
> 06,//** THAT IS WHY THERE IS NO JOBCARD AT THE
> TOP. MA12 MAKES THE CARD
>
07,//**
> 08,//RN072201 EXEC PGM=DFSRRC00,REGION=9000K,
> 09,// PARM=(DLI,DSNMTV01,RF0001P1)
> 10,//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
> subscrip
Re: MA12 Batch triggering
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:
01,//MQEX702B PROC
02,//**
03,//** THIS JCL WILL EXECUTE RN0722PC, WHICH CALLS RN0702PP, THE MQ *
04,//** WRAPPER FOR BATCH PROCESSING. *
05,//** IT ASSUMES THAT THE MA12 SUPPORT PAC WILL BE TRIGGERING IT*
06,//** THAT IS WHY THERE IS NO JOBCARD AT THE TOP. MA12 MAKES THE CARD
07,//**
08,//RN072201 EXEC PGM=DFSRRC00,REGION=9000K,
09,// PARM=(DLI,DSNMTV01,RF0001P1)
10,//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 Li
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:
01,//MQEX702B PROC
02,//**
03,//** THIS JCL WILL EXECUTE RN0722PC, WHICH CALLS RN0702PP, THE MQ *
04,//** WRAPPER FOR BATCH PROCESSING. *
05,//** IT ASSUMES THAT THE MA12 SUPPORT PAC WILL BE TRIGGERING IT*
06,//** THAT IS WHY THERE IS NO JOBCARD AT THE TOP. MA12 MAKES THE CARD
07,//**
08,//RN072201 EXEC PGM=DFSRRC00,REGION=9000K,
09,// PARM=(DLI,DSNMTV01,RF0001P1)
10,//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 availab
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:
01,//MQEX702B PROC
02,//**
03,//** THIS JCL WILL EXECUTE RN0722PC, WHICH CALLS RN0702PP, THE MQ *
04,//** WRAPPER FOR BATCH PROCESSING. *
05,//** IT ASSUMES THAT THE MA12 SUPPORT PAC WILL BE TRIGGERING IT*
06,//** THAT IS WHY THERE IS NO JOBCARD AT THE TOP. MA12 MAKES THE CARD
07,//**
08,//RN072201 EXEC PGM=DFSRRC00,REGION=9000K,
09,// PARM=(DLI,DSNMTV01,RF0001P1)
10,//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
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:
01,//MQEX702B PROC
02,//**
03,//** THIS JCL WILL EXECUTE RN0722PC, WHICH CALLS RN0702PP, THE MQ *
04,//** WRAPPER FOR BATCH PROCESSING. *
05,//** IT ASSUMES THAT THE MA12 SUPPORT PAC WILL BE TRIGGERING IT*
06,//** THAT IS WHY THERE IS NO JOBCARD AT THE TOP. MA12 MAKES THE CARD
07,//**
08,//RN072201 EXEC PGM=DFSRRC00,REGION=9000K,
09,// PARM=(DLI,DSNMTV01,RF0001P1)
10,//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
