Subject: Re: JES2 Exit 53 problem
I stand corrected - I thought I had created Exit #53 when we migrated to z/OS 1.4. Anyway, I have used the similar code in Exit #3 since 1988. Yes, I assembled Exit #53 with a USER Environment and it is loaded in the LPA. LOADMOD(JES2X003) STORAGE=PVT LOADMOD(JES2X053) STORAGE=LPA JES2X053 $MODULE ENVIRON=(USER,ANY) JES2X003 $MODULE ENVIRON=JES2 I guess I will just call this a feature. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2 Exit 53 problem
Yes, I am doing what is described in the exit sample. Further, I strategically generated a S0C1 to view the contents of the XPL and the area pointed to by X053JXWR. Everything looks fine. Basically, the exit exits after this. As I stated in my one of my previous posts, this code has been working on a 1.7 system for 3 years, a 1.4 system for 3 years. As a matter of fact, this code has been running like this since 1988. The only changes I have made is to accommodate the use of the XPL and the exit running in the USER environment. I am going to open an ETR with JES2. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2 Exit 53 problem
On Wed, 14 Jul 2010 08:17:30 -0700, Mark Yuhas mark.yu...@paccar.com wrote: Yes, I am doing what is described in the exit sample. Further, I strategically generated a S0C1 to view the contents of the XPL and the area pointed to by X053JXWR. Everything looks fine. Basically, the exit exits after this. As I stated in my one of my previous posts, this code has been working on a 1.7 system for 3 years, a 1.4 system for 3 years. As a matter of fact, this code has been running like this since 1988. The only changes I have made is to accommodate the use of the XPL and the exit running in the USER environment. Mark, EXIT53 did not exit in z/OS 1.4 nor in 1988, so I don't see how you could have been running it since then. You didn't answer a question I asked from earlier. Is this failing in a test environment, or did you upgrade the production environment with no other changes from 1.7 other than a reassembly / relink of this EXIT53? Or did it only exist as EXIT03 in 1.7? If using it as EXIT53 is new, don't forget that exits running in the user environment must be loaded into common storage. Assuming you have both an EXIT03 and EXIT53 with similar code, you load it as follows: LOADMOD(MYEXIT03) STORAGE=PVT LOADMOD(MYEXIT53) STORAGE=CSA Since you can load new exits dynamically, maybe you should assemble / link the sample as is and see if it works in your environment.I'm pretty sure this is a user error of some sort. Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2 Exit 53 problem
/DJOBDEF /HASP835 JOBDEF /HASP835 JOBDEF ACCTFLD=OPTIONAL,BAD_JOBNAME_CHAR=?,CNVT_ENQ=FAIL, /HASP835 JCLERR=YES,JNUMBASE=4487,JNUMFREE=4080,JNUMWARN=80, /HASP835 JOBFREE=4081,JOBNUM=5000,JOBWARN=80,PRTYHIGH=10, /HASP835 PRTYJECL=NO,PRTYJOB=NO,PRTYLOW=1,PRTYRATE=48, /HASP835 RANGE=(1,4999),RASSIGN=YES,DUPL_JOB=DELAY -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2 Exit 53 problem
Mark, have you looked at the sample in SYS1.SHASSAMP(HASX53A)? It does exactly what you're trying to do. The only thing I could think of is that something else is messing with your msg field or flag after you're done with it. I assume TEXTAREA_MESSAGE is DC CL80? Mary Anne -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2 Exit 53 problem
Yes, upon entry R0 points to the XPL. However, I save it in XPL_ADDRESS. I should have also stated this is JES2 1.9. This code has been working on a 1.7 system for 3 years. And, for another 3 years on a 1.4 system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2 Exit 53 problem
On Mon, 12 Jul 2010 09:09:11 -0700, Mark Yuhas mark.yu...@paccar.com wrote: Yes, upon entry R0 points to the XPL. However, I save it in XPL_ADDRESS. I should have also stated this is JES2 1.9. This code has been working on a 1.7 system for 3 years. And, for another 3 years on a 1.4 system. z/OS 1.4? You mean working as EXIT3? I know of know specific EXIT53 changes going from z/OS 1.7 to z/OS 1.9, but there was a general action for anything that examined the JCT eye catcher. Is you failure on a test system, or in a production system that was migrated? What does a $DJOBDEF output look like? Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2 Exit 53 problem
Doesn't reg 0 point to the XPL ??? -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Mark Yuhas Sent: Saturday, July 10, 2010 11:43 PM To: IBM-MAIN@bama.ua.edu Subject: JES2 Exit 53 problem Maybe another set of eyes can show me the error of my ways. I have written JES2 Exit #53 to validate the accounting field of the JOB statement. The exit performs as designed except for a nagging problem. I want to pass an error message to be added to the JCL data set. According to the JES2 Exit Manual: When passing a return code of 12, your exit routine can pass an installation-defined error message to JES2 to be added to the JCL data set rather than the standard error message. To send an error message, generate the message text in your exit routine, move it to area pointed to by X053JXWR, and set the X053XSEM bit in X053RESP to one. I have included the code I have written to do this: L R1,XPL_ADDRESS L R2,X053JXWR-XPL(,R1) MVC 0(80,R2),TEXTAREA_MESSAGE OI X053RESP-XPL(R1),X053XSEM Yes, the return code is 12 as evidenced by this message: /HASP119 MYUHASTU DELETED - ILLEGAL JOB CARD ACCT FIELD, RC=12 I have checked and rechecked this code and the contents of storage via SVC dumps. All looks good but the message is not being added to the JCL data set. Any suggestions? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
JES2 Exit 53 problem
Maybe another set of eyes can show me the error of my ways. I have written JES2 Exit #53 to validate the accounting field of the JOB statement. The exit performs as designed except for a nagging problem. I want to pass an error message to be added to the JCL data set. According to the JES2 Exit Manual: When passing a return code of 12, your exit routine can pass an installation-defined error message to JES2 to be added to the JCL data set rather than the standard error message. To send an error message, generate the message text in your exit routine, move it to area pointed to by X053JXWR, and set the X053XSEM bit in X053RESP to one. I have included the code I have written to do this: L R1,XPL_ADDRESS L R2,X053JXWR-XPL(,R1) MVC 0(80,R2),TEXTAREA_MESSAGE OI X053RESP-XPL(R1),X053XSEM Yes, the return code is 12 as evidenced by this message: /HASP119 MYUHASTU DELETED - ILLEGAL JOB CARD ACCT FIELD, RC=12 I have checked and rechecked this code and the contents of storage via SVC dumps. All looks good but the message is not being added to the JCL data set. Any suggestions? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2 Exit 53
Exit 53 operates in a different environment than Exit 3. Exit 3 is in the JES2 Environment. Exit 53 is in the USER environment. The different environments require different services, different LOAD parms, register contents, and especially information passed in the exit list. RTFM - JES2 Installation Exits. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
JES2 Exit 53
I'm not an assembly programmer but am trying to help modify our JES2 exit 3 to move it to exit 53. What I need is an example of an exit 53 that checks to see if a job came from an internal reader and if it did, was the job that owned the reader a CICS region (our CICS regions are started as batch jobs). As I say, I'm not very familiar with assembly code (I know enough to be dangerous!). We have someone else looking at the code, but he doesn't know a lot about JES2 exits. Anyone have such a beast? Here's the first part of the old exit 3: HASPE053 $ENTRY BASE=(R12) $SAVE USING HCT,R11 USING PCE,R13 USING JCT,R10 LRR12,R15 USING REGISTER LRR8,R1 SAVE R1 L R15,PCEDCT ADDRESS OF DCT USING DCT,R15 EX5302DS0H TMPCEID,PCEINRID INTERNAL READER SUBMITTING JOB ? BNO EX53RETN ... NO L R15,PCEDCT DCT ADDR CLI DCTDEVN,C'I' BATCH JOB INT RDR ?? BNE EX53RETN NO, HANDLE ONLY BATCH INT RDR. DROP R15 CLI JCTJUSID,C' 'USER NAME THERE ? BHINSTUSID NO, INSERT USER ID. CLI JCTPASS,C' ' PASS WORD THERE ?? BHEX53RETN DONE. What do I need to change to make this an exit 53? I understand R11 now points to the HCCT. So I think the first part of the code needs to look like this: HASPE053 $ENTRY BASE=(R12) $SAVE USING HCCT,R11 L R10,R0 USING XPL,R10 L R10,X053JCT USING JCT,R10 We have already set the ENVIRON=USER. I also assume we need to test whether the JCT is not zero, but what else needs to change? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2 Exit 53
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Michael Babcock Sent: Monday, October 22, 2007 9:20 AM To: IBM-MAIN@BAMA.UA.EDU Subject: JES2 Exit 53 I'm not an assembly programmer but am trying to help modify our JES2 exit 3 to move it to exit 53. What I need is an example of an exit 53 that checks to see if a job came from an internal reader and if it did, was the job that owned the reader a CICS region (our CICS regions are started as batch jobs). As I say, I'm not very familiar with assembly code (I know enough to be dangerous!). We have someone else looking at the code, but he doesn't know a lot about JES2 exits. Anyone have such a beast? Look at the JRW. Code from my JES2 exit 20 looks like (changes needed for exit 53!): L R5,PCEDCT USING DCT,R5 CLI DCTDEVTP,DCTINR INTERNAL READER? BNE X20RC00 NO - CAN'T BE CA7! * USING XPL,R1 L R6,X020AREA DROP R1 * USING JRW,R6 CLC =C'CA7',JRWSJNAM BEX20RC00 YES - DO NOTHING REF: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/HAS2C170/65.3 -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
