×
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.
Found a message in the archives that says that the QTFTP jobs are used by a default of 200
connections. However, the same message mentions that the are pre-start jobs and at least on my v5r2
system, the QTFTP jobs are shown as type "Batch - Server" not "Prestart Batch - Server" in iNav.
So the questions:
Are the jobs indeed reused 200 times?
Anyway to control this? For prestart jobs there is a MAXUSE parameter, but as I said, the QTFTP jobs
don't appear to be prestart jobs.
Here's the deal. I have a trigger attached to a file that gets data loaded via FTP. The trigger
program returns with INLR = *OFF, which is fine for a given connection. However, I'd like to have the
trigger program unloaded at the end of the connection and restarted for the next.
I suppose I could make use of ILE activation groups in some manner, but I know triggers are supposed
to run in ACTGRP(*CALLER) for commitment control reasons. That is not an issue here as FTP doesn't
use CC right?
So if my trigger program was compiled, ACTGRP(FTPTRG), then couldn't I have a FTP exit point do a
RCLACTGRP FTPTRG when the next user signs on?
Anybody see any issues with this?
Is there another way?
Lastly, this process will need to work on a v4r5 (yes v4r5) box.
Thanks,
Charles Wilt
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307
wiltc@xxxxxxxxxx <mailto:wiltc@xxxxxxxxxx>
This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.
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.