× 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.



Didn't used to always be that way.  And it was determined that it was a 
security breach.  Evidently the ftp engine can't tell if the ftp commands 
are coming in from a script from within a program or being typed in by a 
user at a command line.  So, by changing the assumption from the former to 
the latter, at some release, you have tighter security.  Believe me, 
people figured out how to run commands they weren't authorized to via the 
command line using ftp.  I've been known to use RUNRMTCMD to start QINTER 
when a backup blew.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Frances Denoncourt" <Frances.Denoncourt@xxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
12/16/2004 11:50 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
<midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: V4R5 to V5R2 FTP script error






Almost went with the CHGCMD suggestion - it would have been a simple fix 
and I wouldn't have to modify the rest of the programs. But, we'd like to 
keep the limit on capabilities for command line usage. That's why I ended 
up using CHGCURLIB before the FTP and then CHGCURLIB back to *CRTDFT after 
the FTP in the submitted CL.

But, why does the CHGCURLIB in an FTP script read from a submitted job, 
act like it is from the command line?
Thanks again,

Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404


-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
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-Ups:
Replies:

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.