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
//SYSIN    DD 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 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


<< temp.txt >>

_________________________________________________________________ Get MSN 8 and enjoy automatic e-mail virus protection. http://join.msn.com/?page=features/virus

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

Reply via email to