Date: Mon, 19 Jul 2010 06:42:14 -0400
Reply-To: CICS List <CICS-L@LISTSERV.UGA.EDU>
Sender: CICS List <CICS-L@LISTSERV.UGA.EDU>
From: Kevin Evans <kevin.evans@LEO.GOV>
Subject: Re: Exits
In-Reply-To: <36AE37E2679C4D0DB42B5AEC86323440@GarrettFamily.us>
Content-type: text/plain; charset=us-ascii
In our case, our PLTPI code ONLY does an EXEC CICS START for the "real" code
that we wish to run at initialization time. This allows our code to only run
after CICS is fully initialized.
K
-----Original Message-----
From: CICS List [mailto:CICS-L@LISTSERV.UGA.EDU] On Behalf Of Robert
Sent: Saturday, July 17, 2010 3:16 PM
To: CICS-L@LISTSERV.UGA.EDU
Subject: Re: Exits
Hi Brad, I know others have responded already with various ideas. Are you
sure you're looking at the right spot in your code? I ask because its just
not possible for an LR (Load Register) instruction to generate a 0C4
(protection exception program check) abend. Can't happen. Assuming your
exit module has command level calls and was linked to include the execute
interface stub, have you allowed for the length of the stub in your offset
calculations?
Other ideas: When you put your entry into the PLT(PI), did you put it before
or after the entry for DFHDELIM? Entries prior to DFHDELIM get control
during stage 2 of initialization with a slightly different environment - for
example, they will be autoinstalled if not already in the CSD (regardless of
whether or not program autoinstall is enabled) and they will always run as
if they were defined with the attributes LANGUAGE(ASSEMBLER) STATUS(ENABLED)
CEDF(NO) DATALOCATION(BELOW) EXECKEY(CICS) EXECUTIONSET(FULLAPI) regardless
of how they may be defined in the CSD (if at all). PLT programs that run
run during stage 3 of initialization (listed in the PLT after DFHDELIM) will
have all their CSD attributes honored as defined.
Regards,
Robert Garrett
-----Original Message-----
From: CICS List [mailto:CICS-L@LISTSERV.UGA.EDU] On Behalf Of Brad Terry
Sent: Thursday, July 15, 2010 3:56 PM
To: CICS-L@LISTSERV.UGA.EDU
Subject: Exits
Hello Everyone,
After years working with CICS I am now working on my first CICS exit.
I've been trying to play with DFH$SXP6, I've got it in place but then
figured out that I also need a PLT program in place to activate this exit.
I've modified DFH$PCPI and placed my exit name where it belongs, but when
the region starts up the PLT program get an 0C4 because of an illegal macro
call or reference to the CSA or TCA. The offset is 2C, which is in the
section to "establish code addressibility". This is generated code that I
haven't even written. It is a Load Register command that is proceeded by a
USING statement :
USING *-(DFH0003C-DFHEI0003A+4),3
LR 3,15
I have specified SP on the translator step which I thought was supposed to
get me around these situations. I'm running TS 3.2 with options CICS,SP on
the translator step, and DECK,OBJECT,LIST,XREF(FULL),ALIGN on the assembly
step. Any help with this would be greatly appreciated.
Thanks,
Brad Terry
Baptist Health
Little Rock AR
--------------------------------------------
IMPORTANT DISCLAIMER NOTICE
--------------------------------------------
The information, both of the message and any attachments, contained in this
message is intended only for the use of the individual or entity to which it
is addressed. This message may contain information that is privileged,
confidential and exempt from disclosure under applicable law.
If the reader of this message is not the intended recipient or an agent
responsible for delivering it to an intended recipient, or has received this
message in error, you are hereby notified that we do not consent to any
reading, dissemination, distribution or copying of this message and any such
actions are strictly prohibited. If you have received this message in
error, please notify the sender immediately and destroy the transmitted
information.
