|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Well a few of us anyway, the 400 types that got here by way of the mainframe almost always, the other folk that came by way of the PC to college then to work, no way! :-) -----Original Message----- From: Vernon Hamberg [mailto:vhamberg@attbi.com] Sent: Monday, April 29, 2002 1:19 PM To: midrange-l@midrange.com Subject: RE: I got those data queue blues? Comments? Your people use comments? :-) At 01:12 PM 4/29/02 -0400, you wrote: >This message is in MIME format. Since your mail reader does not understand >this format, some or all of this message may not be legible. >-- >[ Picked text/plain from multipart/alternative ] >Al, one other thing you might look at is any program that uses the data >queue, it will at the very least contain the size of the data queue and may >have comments about other things related to the queue. > >-----Original Message----- >From: Weatherly, Howard [mailto:hweatherly@dlis.dla.mil] >Sent: Monday, April 29, 2002 9:19 AM >To: 'midrange-l@midrange.com' >Subject: RE: I got those data queue blues? > > >This message is in MIME format. Since your mail reader does not understand >this format, some or all of this message may not be legible. >-- >[ Picked text/plain from multipart/alternative ] >Yes! here is a screen shot of the dump from the command: > > Data Queue Display - TAA 4/29/02 >09:14:16 > > > Queue: LMTD615DQ Lib: TLMTDDTA Nbr of Entries: 0 Seq: *FIFO > > Max Entry Length: 200 Key Length: 0 Force: *NO Sender ID: *NO > > Text: Data Queue for Trigger Buffer > > 1=Display more entry data =Arrived on >Queue= > Opt Entry Entry Data Date Time > > ***** No entries on queue ***** > > > > > > > > > > >-----Original Message----- >From: Denis Robitaille [mailto:DRobitaille@cascades.com] >Sent: Monday, April 29, 2002 9:06 AM >To: midrange-l@midrange.com >Subject: RE: I got those data queue blues? > > >Does that TAATOOLS also give other information regarding the structure >of the dataq? (FIFO, LIFO KEYED) and if KEYED, does it give the length >of the key? > >Denis Robitaille >Directeur services techniques >Cascades Inc >819 363 5187 > > > >>> hweatherly@dlis.dla.mil 04/29/02 08:47am >>> >This message is in MIME format. Since your mail reader does not >understand >this format, some or all of this message may not be legible. >-- >[ Picked text/plain from multipart/alternative ] >Don't know if it is in fact damaged, but if you have TAATOOLS, use >DSPDTAQ, >give it the queue name and library and it will show you what is in the >queue, also tell you the queue length. Dennis suggested you restore >from >backups, and if the data on the backup is in sync with what should be >there >that is a good plan, if the data is old, you would be wasting time >because >it is to simple to recreate the queue once you know the size. CRTDTAQ, >give >it the size location and any other info needed and you are off and >running. > >- >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.