|
No problem! Good Luck, Patrick Weatherly, Howard wrote: > > Patrick, > > No messages in "anywhere!!!" but we did try compling the > transaction into QSYS and that seems to have worked although > I believe I am getting a Function Mgt Header before I get > the real data. Unfortunatly or fortunatly the change to QSYS > corresponded to us also running a comm trace, I can see the > flow, and all for now seems well! > > Err except that ball is now back in my court! > > Thanks for the pointers. > > ____________________________________________________________ > _____________ > Howard Weatherly > > hweatherly@dlis.dla.mil > hweath@ibm.net > > X4324 > > <<Re: CICS APPC LU 6.2 / Distributed Transaction > Processing>> > > ------------------------------------------------------------------------ > > Subject: Re: CICS APPC LU 6.2 / Distributed Transaction Processing > Date: Fri, 14 Aug 1998 11:42:11 -0400 > From: Patrick Townsend <townsend@patownsend.com> > Reply-To: MIDRANGE-L@midrange.com > To: MIDRANGE-L@midrange.com > > I'm sorry I don't know the application (MQ Series?), but you > could still > have a problem even if your library is defined to it. It all > depends on > how the allocate is formatted. One way to find out is to > turn on a line > trace and try again. When you print the line trace you > should see the > allocate request flowing and be able to determine if library > name is > included in the allocate request. > > Any error messages in QSYSOPR? > > Patrick > > Weatherly, Howard wrote: > > > > Patrick, > > > > Last night (or this morning) the mainframe guy set his > > transaction to log messages to a tsq and we discovered > that > > it is indeed getting an error on the ALLOCATE, what is > > strange is that the queue output indicates a system busy > > error. > > > > The objects (trans) on the 400 are in my library but our > > CICS tables are pointing there and I have all object, > would > > there still be a problem if not in Q..... ? > > > > > ____________________________________________________________ > > _____________ > > Howard Weatherly > > > > hweatherly@dlis.dla.mil > > hweath@ibm.net > > > > X4324 > > > > <<Re: CICS APPC LU 6.2 / Distributed Transaction > > Processing>> > > > > > ------------------------------------------------------------ > ------------ > > > > Subject: Re: CICS APPC LU 6.2 / Distributed Transaction > Processing > > Date: Thu, 13 Aug 1998 21:32:59 -0400 > > From: Patrick Townsend <townsend@patownsend.com> > > Reply-To: MIDRANGE-L@midrange.com > > To: MIDRANGE-L@midrange.com > > > > Howard, > > > > I've done LU6.2 communications with MVS/CICS but not in > the > > exact > > environment you are describing. However, it sounds like > the > > Allocate is > > failing to the AS/400. Do you have any messages in the > > QSYSOPR message > > queue related to the allocate attempt? If so, can you > > describe the sense > > data or any other diagnostic information on the AS/400 > side? > > Also, what > > error messages are you getting on the MVS side? Sense data > > is especially > > helpful in analyzing these problems. > > > > In general, look for a mode entry that allows both sides > to > > initiate > > sessions. Make sure the TP you are trying to allocation is > > in a library > > that can be resolved (is in the QSYSLIBL or QUSRLIBL). > Also, > > check to > > make sure security information is correct. > > > > Hope this helps, > > Patrick > > > > Weatherly, Howard wrote: > > > > > > Does anyone have any experience with LU6.2 between an > > AS400 > > > and MVS using CICS Distributed Transaction Processing? > > What > > > I am looking for is what might be needed in the CICS > > tables > > > on the MVS side being the Front end Transaction. > > > > > > We currently have managed to get the connection working > > via > > > CONVERSE but we need another transaction on the MVS side > > > that is not as timely in responding; Consequently, the > > SEND > > > on the 400 starts the remote transaction which goes > about > > > it's business, ends, and is restarted by yet another > > > process. The processing program then ALLOCATES, CONNECTS > > but > > > when it comes to the SEND, the little devil refuses to > > start > > > the 400 RECEIVE transaction. > > > > > > Any insite into what possible things might need to be in > > the > > > CICS tables on the mainframe will be appreciated. > > > > > > > > > ____________________________________________________________ > > > _____________ > > > Howard Weatherly > > > > > > hweatherly@dlis.dla.mil > > > hweath@ibm.net > > > > > > X4324 > > > > > > +--- > > > | This is the Midrange System Mailing List! > > > | To submit a new message, send your mail to > > MIDRANGE-L@midrange.com. > > > | To subscribe to this list send email to > > MIDRANGE-L-SUB@midrange.com. > > > | To unsubscribe from this list send email to > > MIDRANGE-L-UNSUB@midrange.com. > > > | Questions should be directed to the list > owner/operator: > > david@midrange.com > > > +--- > > > > -- > > > > Patrick Townsend > > mailto:townsend@patownsend.com > > Patrick Townsend & Associates, Inc. > > http://www.patownsend.com > > +--- > > | This is the Midrange System Mailing List! > > | To submit a new message, send your mail to > > MIDRANGE-L@midrange.com. > > | To subscribe to this list send email to > > MIDRANGE-L-SUB@midrange.com. > > | To unsubscribe from this list send email to > > MIDRANGE-L-UNSUB@midrange.com. > > | Questions should be directed to the list owner/operator: > > david@midrange.com > > +--- > > -- > > Patrick Townsend > mailto:townsend@patownsend.com > Patrick Townsend & Associates, Inc. > http://www.patownsend.com > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to > MIDRANGE-L@midrange.com. > | To subscribe to this list send email to > MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- -- Patrick Townsend mailto:townsend@patownsend.com Patrick Townsend & Associates, Inc. http://www.patownsend.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.