×
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.
donna lester wrote:
When I try to FTP a file from my PC to AS/400 library,
I want to know if there is a command where I can specify
the IASP since we have several IASPs on our system.
After establishing the FTP authentication, there is the option of
issuing a "QUOTE RCMD SETASPGRP ASPGRP(TheIASP)" request to establish
which independent ASP [aka namespace]. Also, the FTP exit program
should be able to do that as well [unconditionally, or if for example
something about an incoming request can be used to infer any
requirements for which ASP, then establish such iASP routing].
However when using the path form of object names instead of the
Library/Object naming, the iASP can be accessed directly. For example
in the FTP script first issue the "quote site namefmt 1" and then the
"get /TheIASP/QSYS.LIB/Library.LIB/Object.FILE" or "get
/TheIASP/usr/me/afile" to directly name from which iASP to find the data.
If there were multiple independent FTP servers where each could be
configured with its own IP&name to establish [via the exit program if
the iASP was not a server attribute] for each ASP group. In that manner
one could initiate an FTP TheIASP.TheDomain to directly establish the
default namespace. IMO it would have been nicer to have most server
jobs when switching to the authenticated user, to establish the Initial
ASP group (INLASPGRP) various other associated values like INLLIB &
CURLIB from the *JOBD like is done for interactive jobs.
Regards, Chuck
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.