IEFUJV PROCESS OF JECL CARDS

2017-01-08 Thread bILHA ELROY
Z/OS V2.1 Is it possible to process JECL (/*JOBPARM for example) cards in IEFUJV exit ? If so, can we change the card image (not only set a R.C ) in z/os mvs installation exit book it is said that: •The job validation exit (IEFUJV) receives control before each job control statement in the in

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

2017-01-08 Thread Rebecca Martin
I went from 1.13 to 2.2 last May without any issue. You probably have already done this several times, but double check your parmlib members - IEAFIXxx, IEALPAxx, PROGxx. Any chance you have one that includes modifications of an exit or module from JES2 1.13? Also, perhaps review any jobs whe

Re: DNS, Resolver, and /etc/hosts

2017-01-08 Thread Phil Smith
Thanks, Steve and Elardus-those look like the ticket! Will read and try to grok. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

COBOL5 and ceedump

2017-01-08 Thread Steff Gladstone
Are there any whizzes out there who specialize in reading and deciphering CEEDUMPs? I have a question for you. In a COBOL5 CEEDUMP, how do I locate the *index* of an array (i.e., an array that is defined with "indexed by") in the dump? Thanks in advance, Steff Gladstone

Re: IEFUJV PROCESS OF JECL CARDS

2017-01-08 Thread Jesse 1 Robinson
Someone may give you a better answer. We have created our own JECL card (/*SCHENV) that we process entirely within JES2 exits. You can definitely change a JECL card there. We have to, in fact, because our JECL card must be turned into a comment before mainline processing gets control. I’m not

Re: COBOL5 and ceedump

2017-01-08 Thread Mike Schwab
The offset should be in the compiler listing. On Sun, Jan 8, 2017 at 10:51 AM, Steff Gladstone wrote: > Are there any whizzes out there who specialize in reading and deciphering > CEEDUMPs? > I have a question for you. In a COBOL5 CEEDUMP, how do I locate the > *index* of an array (i.e., an arr

AW: COBOL5 and ceedump

2017-01-08 Thread Roland Schiradin
Hi Steff, depending on your service level the index is defined in front of the array. Look at this APAR text Starting with COBOL V5.1, index-names were located in memory immediately following the memory for the associated table, which meant that programs that modify dsta beyond the end of a

Re: AW: COBOL5 and ceedump

2017-01-08 Thread Martin Packer
Would be nice to know the APAR. :-) Cheers, Martin Martin Packer, zChampion, Principal Systems Investigator, Worldwide Cloud & Systems Performance, IBM +44-7802-245-584 email: martin_pac...@uk.ibm.com Twitter / Facebook IDs: MartinPacker Blog: https://www.ibm.com/developerworks/mydeveloperwo

AW: AW: COBOL5 and ceedump

2017-01-08 Thread Roland Schiradin
APAR Identifier .. PI65115 Last Changed 16/08/29 WRITING BEYOND THE END OF A TABLE IN V5.X CAN CORRUPT INDEX NAMES IN THAT TABLE. -Ursprüngliche Nachricht- Von: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] Im Auftrag von Martin Packer Gesendet:

Re: COBOL5 and ceedump

2017-01-08 Thread Bill Woodger
On Sun, 8 Jan 2017 18:51:14 +0200, Steff Gladstone wrote: "In a COBOL5 CEEDUMP, how do I locate the *index* of an array (i.e., an array that is defined with "indexed by") in >the dump?" If you consult the "* * * * * S T A T I C M A P * * * * *" in the compile listing you should get a