× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I got it to work... it was the wrong size. It should be 128. At least
according to what I have.

-----Original Message-----
From: Wills, Mike N. (TC) [mailto:MNWills@taylorcorp.com]
Sent: Monday, October 14, 2002 11:54 AM
To: 'midrange-l@midrange.com'
Subject: RE: Monitoring for a spool file


Yes I am... I am in the process of getting this set up, and I am manually
moving the files....

-----Original Message-----
From: Tyler, Matt [mailto:mattt@wincofoods.com]
Sent: Monday, October 14, 2002 11:46 AM
To: 'midrange-l@midrange.com'
Subject: RE: Monitoring for a spool file


Mike,
        Are you sure that the spooled file is going to the OUTQ in RDY
status?


Thank you,
Matt Tyler
Mattt@wincofoods.com

-----Original Message-----
From: Wills, Mike N. (TC) [mailto:MNWills@taylorcorp.com]
Sent: Monday, October 14, 2002 10:33
To: Midrange - Midrange-L (E-mail)
Subject: Monitoring for a spool file

I remember asking a similar question to this before and can't seem to find
it in the archives. I used an article Brad Stone wrote on monitoring for
spool files and wrote a monitoring program.

My problem I am having is that the outq doesn't seem to be writing an entry
to the dataq. I have the dataq attached, and I know my program is reading
from it, because the ending program will end it. I put the program in debug
and have yet to hit the break (which is on the beginning of a do loop). I
guess my main question is, what should be the size of the dataq for an outq?
And is there anything else I should check to see why I am having problems.

Mike Wills
IT Corporate Support
Taylor Corporation
mnwills@taylorcorp.com
Phone: (507) 386-3187

_______________________________________________
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 thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.