Thanks Mark for the info as well as your PMR, which I'm trying to avoid
for 'exit support'. See the snippet of code at the bottom for my rework.
In my original post, I overlooked two other ASM errors resulting from the
control block change.
-- Field DCNVSCHE , which I use in processing Scheduling Environment, is
gone. $CIWORK contains *two* fields for SCHENV:
CIWSCHE DS CL16 Scheduling environment
...
CIWJSCHE DS CL16 Scheduling environment
Both fields indicate that they were introduced by OA42098 . I don't know
which of these fields should be used as replacement for field DCNVSCHE .
-- Field DCNVCAT , pointer to the Class Attribute Table, where I use
CATSCHED to determine the default SCHENV for this job class. It looks as
though I can find the appropriate CAT entry via CIWCATA near CIWJSCHE
above.
Snippet of rework code for DCNVMSG, pointer to the message data set ACB:
L R8,20(,R9) Get CIWORK address
USING R8,CIWORK Enable 31-bit DSECT
L R8,CIWCIWB Pt to 24-bit work area
USING CIWORKB,R8 Enable 24-bit DSECT
LA R15,CIWBMSG Load output ACB address
ST R15,OUTACB SAVE OUTPUT ACB ADDRESS
DROP R8 Drop DSECT
For you history buffs, the source indicates that the exit was written by
John V. Hooper at Northwestern Bank circa 1985. Very much modified since
then.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[email protected]
From: Mark Zelden <[email protected]>
To: [email protected],
Date: 06/24/2014 06:15 AM
Subject: Re: Problem with $DTECNV DCNVMSG in JES2 2.1
Sent by: IBM Mainframe Discussion List <[email protected]>
On Sun, 22 Jun 2014 15:50:28 -0700, Skip Robinson
<[email protected]> wrote:
>I posted this question on JES-L but did not get a response. Has anyone
>made this transition from V1 to V2?
>
>.
>.
>J.O.Skip Robinson
>Southern California Edison Company
>Electric Dragon Team Paddler
>SHARE MVS Program Co-Manager
>626-302-7535 Office
>323-715-0595 Mobile
>[email protected]
>----- Forwarded by J O Skip Robinson/SCE/EIX on 06/22/2014 03:48 PM -----
>
>From: J O Skip Robinson/SCE/EIX
>To: [email protected],
>Date: 06/20/2014 04:17 PM
>Subject: Problem with $DTECNV DCNVMSG in JES2 2.1
>
>
>We have an ancient JES2 Exit 6 that makes use of field DCNVMSG in DSECT
>$DTECNV. $DTECNV has changed in 2.1 and DCNVMSG no longer exists. The
>lines in 1.13 are
>
>***** DCNVMSG ***** ACB FOR SYSTEM MSGS DATA SET
> DS 0F DCNVMSG ORIGIN
>DCNVMSG ACB MACRF=(ADR,SEQ,OUT) SYSTEM MESSAGES DATA SET
>
>In Tom Wasik's SHARE pitch in Anaheim, he referred to changes in the
area.
>In particular, some fields have moved to $CIWORK . There I find
>
>***** CIWBMSG ***** ACB for system msgs data set
> DS 0F CIWBMSG Origin
>CIWBMSG ACB MACRF=(ADR,SEQ,OUT) System messages data set
>
>Should I be able to use field CIWBMSG in place of the old DCN field to
use
>the message data set?
>
>
I ran into the same thing with my exit 6. Nothing was supposed to change
unless
you used "JOBDEF INTERPRET=JES". Well, it did change. I ended up
opening a
PMR to find out what was going on (as well as contacting Marna who didn't
know
about this either and is going to write a migration action). I guess I
missed
that pitch at SHARE. I really wish I could clone myself and go to all the
sessions I wanted.
You should be able to use $CIWORK where the names were changed to
protect the innocent. :-) If you are using "JOBDEF INTERPRET=JES"
you will also have to code exit 60. Deja vu all over again / nightmares
of
z/OS 1.7 exit changes - but at least it is optional this time.
Chapter 73 of the exits manual (JES2 exit migration considerations) also
has some information.
Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:[email protected]
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN