Here's what I found in the Xpediter/CICS 7.0 Installation guide - that's all I have access to from home, although we're actually running version 7.1; the program DBUGPLTS mentioned below doesn't ring a bell with me, but that doesn't mean anything - sometimes I have to look at my id badge to remember my name:

-snip-

Shutdown of XPEDITER/CICS via the PLT is not supported. Do not put DBUGPPM2 in the PLTSD table.

Note: Modification of the PLTSD will be required if the XPEDITER Script Facility or Log Facility is enabled later in this installation procedure.

-end snip-

Try to lay your hands on the installation guide for the version of Xpediter that you're running. That will have the information that will answer your questions for sure. If you don't have it, read on.

I may have missed it, but what is your environment/Xpediter version? We are OS/390 2.8, CICS/ESA 4.1.0 and CICS/TS 1.3, and Xpediter/CICS 7.1.

If the above snip from the 7.0 installation guide still holds with the version you're running, why don't you try this, if you have a tech support crash-and-burn region for testing new third party software releases:

Start it up with the same PLTPI as the region that crashes with SA03. If it includes initializing Xpediter from PLTPI, manually enter the XPOF transaction to turn it off. Then shut the region down. If you still get SA03, it isn't Xpediter that's causing it. Then you can use the brute force method if you don't want to have to wade through a dump. Comment out all the entries in your startup PLT (unless you have a *lot* of entries in your startup PLT), then restore them one at a time, restarting the region and shutting it down each time until you get SA03 - the last entry restored will be for the software that is the culprit. It ain't pretty, but it works.

I hope this helps.

Tim Fansler

Bob Juch wrote:

> If I wasn't in-between contracts right now, I'd be able to check the below statement easily. > > >>If Xpediter is the culprit, then you might want to ensure the following is > >>in the shutdown PLT: > >> > >>DFHPLT TYPE=ENTRY,PROGRAM=DBUGPLTS > > This *sounds* right. The startup PLT entry for Xpediter initializes it before its first use. If you don't use it, the first person to type in XPED will have a longer wait. That's usually OK. The shutdown is also optional as long as you don't mind the A03s. > > Bob Juch > CICS Central > http://www.CICSCentral.com > > -----Original Message----- > From: CICS List [mailto:CICS-L@LISTSERV.UGA.EDU]On Behalf Of Elliott, > Simon L > Sent: Monday, June 12, 2000 9:32 AM > To: CICS-L@LISTSERV.UGA.EDU > Subject: Re: SA03 abends at shutdown > > Neat tip Paul, I'll remember that one. > > As mentioned before, in my copy of the installation guide, p2.16, > there's a reference to a PLT program. Unfortunately it doesn't say what it's > called or where to find a sample entry. > > There's also references on page 1.5 and chapter 16 to a transaction, > DBPA, that appears to build a program for PLT startup. This transaction > appears to link a module of Xpediter parms that can be inserted into the > startup PLT. > > I get the impression that use of a startup/shutdown PLT program is > an optional thing. > > Simon Elliott > TGL TSG CICS/DB Support > Cap Gemini Southbank > London > Tel. (44) 020 7917 4255 > > Standard disclaimer: Any opinions expressed are not necessarily those of my > employer.