Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
How to access (with ftp from PC) the files/ Folders in QDLS ?
1,188 views
Skip to first unread message
Silenus paparias
Dec 13, 2011, 8:22:20 AM12/13/11
to
Hello.
With ftp i can transfer Physical Files which are on LIBS to PC as txt
format, but the files are not readble!
.
I think the PFs must be first convertet from EBCDIC to ASCII, with
CPYTOPCD in QDLS and then tranfered with FTP to a PC?
(OR IS THERE A ANOTHER WAY ???)
IF so,
How can access with ftp the folders which are on QDLS to put or get
txt files ?
Thnaks.
With ftp i can transfer Physical Files which are on LIBS to PC as txt
format, but the files are not readble!
.
I think the PFs must be first convertet from EBCDIC to ASCII, with
CPYTOPCD in QDLS and then tranfered with FTP to a PC?
(OR IS THERE A ANOTHER WAY ???)
IF so,
How can access with ftp the folders which are on QDLS to put or get
txt files ?
Thnaks.
Silenus paparias
Dec 13, 2011, 8:22:20 AM12/13/11
to
iseriesflorida
Dec 13, 2011, 10:42:20 AM12/13/11
to
transfers to/from.
CRPence
Dec 13, 2011, 1:05:41 PM12/13/11
to
On 13-Dec-2011 05:22 , Silenus paparias wrote:
>
> With FTP I can transfer Physical Files which are on LIBS to PC as
> txt format, but the files are not readable!
The term "physical file" is very nebulous. For a "source physical
file", which is intended to contain "text" data, the "PF-SRC" data in
the members will transfer as record-delimited data with expected
translation, given the CCSID properly identifies the data within.
> I think the PFs must be first converted from EBCDIC to ASCII, with
> CPYTOPCD in QDLS and then transferred with FTP to a PC?
While deprecated, that may be an option. Though once in /QDLS file
system, the PC should be able to use the old client mapping to map the
old 8.3 file system; i.e. the PC can "see" and thus access the file on
the mapped drive, so no FTP would be required.
Again, that depends greatly on what the "physical files" actually
are. If they are PF-DTA "flat files" [files not externally described],
copying the data to any text stream or fixed-record-length file for
which CCSID tagging is enabled could be another option.
> (OR IS THERE A ANOTHER WAY ???)
Before making a good recommendation, I think knowing a specific
example of the file definition might be necessary.
More generically, a database file with multiple column\field
definitions which is not a "source physical file" [or "source logical
file"] should first be "exported", then the "exported text data"
transferred. If the physical file is a "source physical file", then
presumably the file needs to be tagged with the appropriate CCSID [and
perhaps data corrected to match]; CHGPF SRCFILE(*NONE) CCSID(_theCCSID_)
would assign a CCSID to the file, but would not change nor correct any
of the data to match the CCSID being assigned.
If an intermediate copy is made from a non-described\flat file,
instead of the old 8.3 [/QDLS Folder and DLO] file, using another stream
file support is recommended. CPYTOSTMF [and I think CPY] into a
directory other than /QDLS may be an option. Then like with /QDLS, the
PC can map a drive to the folder. Or using /QNTC, the data can be
copied into a file created on the share which defines that PC.
> If so, How can access with FTP the folders which are on QDLS to put
refers to the path and file name. Also the user would have to be added
to the system directory; ADDDIRE. For FTP PUT from the client to the PC
with an FTP server, the LCD subcommand can set the current directory for
the session into the QDLS: LCD /QDLS For FTP GET from the PC client,
the CD subcommand can set the current directory at the server for the
session: CD /QDLS
Regards, Chuck
>
> With FTP I can transfer Physical Files which are on LIBS to PC as
> txt format, but the files are not readable!
The term "physical file" is very nebulous. For a "source physical
file", which is intended to contain "text" data, the "PF-SRC" data in
the members will transfer as record-delimited data with expected
translation, given the CCSID properly identifies the data within.
> I think the PFs must be first converted from EBCDIC to ASCII, with
> CPYTOPCD in QDLS and then transferred with FTP to a PC?
While deprecated, that may be an option. Though once in /QDLS file
system, the PC should be able to use the old client mapping to map the
old 8.3 file system; i.e. the PC can "see" and thus access the file on
the mapped drive, so no FTP would be required.
Again, that depends greatly on what the "physical files" actually
are. If they are PF-DTA "flat files" [files not externally described],
copying the data to any text stream or fixed-record-length file for
which CCSID tagging is enabled could be another option.
> (OR IS THERE A ANOTHER WAY ???)
example of the file definition might be necessary.
More generically, a database file with multiple column\field
definitions which is not a "source physical file" [or "source logical
file"] should first be "exported", then the "exported text data"
transferred. If the physical file is a "source physical file", then
presumably the file needs to be tagged with the appropriate CCSID [and
perhaps data corrected to match]; CHGPF SRCFILE(*NONE) CCSID(_theCCSID_)
would assign a CCSID to the file, but would not change nor correct any
of the data to match the CCSID being assigned.
If an intermediate copy is made from a non-described\flat file,
instead of the old 8.3 [/QDLS Folder and DLO] file, using another stream
file support is recommended. CPYTOSTMF [and I think CPY] into a
directory other than /QDLS may be an option. Then like with /QDLS, the
PC can map a drive to the folder. Or using /QNTC, the data can be
copied into a file created on the share which defines that PC.
> If so, How can access with FTP the folders which are on QDLS to put
> or get txt files ?
To use /QDLS, set that as the directory of IFS to\from which the FTP
refers to the path and file name. Also the user would have to be added
to the system directory; ADDDIRE. For FTP PUT from the client to the PC
with an FTP server, the LCD subcommand can set the current directory for
the session into the QDLS: LCD /QDLS For FTP GET from the PC client,
the CD subcommand can set the current directory at the server for the
session: CD /QDLS
Regards, Chuck
Silenus paparias
Dec 14, 2011, 7:12:52 AM12/14/11
to
qdls/T24?
I have tryed on the ftp profile unter HomeDir with "QDLS/T24" but this
goes always to *same .
thanks.
iseriesflorida
Dec 14, 2011, 8:34:25 AM12/14/11
to
On Dec 14, 7:12 am, Silenus paparias <olympiada1...@gmail.com> wrote:
> thanks.- Hide quoted text -
>
> - Show quoted text -
Take a look at chgusrprf, then look for the keyword home directory
(homedir).
>
> - Show quoted text -
Take a look at chgusrprf, then look for the keyword home directory
(homedir).
CRPence
Dec 14, 2011, 1:11:38 PM12/14/11
to
On 14-Dec-2011 04:12 , Silenus paparias wrote:
>
> How to set that the ftp-working directory is QDLS/T24 without to do
> cd qdls/T24?
Per mention of CD versus LCD, I infer this is the FTP server working
>
> How to set that the ftp-working directory is QDLS/T24 without to do
> cd qdls/T24?
directory; that, and the FTP client current directory should reflect the
CD established before invoking STRTCPFTP.
Well, first.... the directory is in the /QDLS file system under the
IFS "Integrated File System" root, not QDLS. Thus the FTP subcommand to
establish the desired current directory is:
CD /QDLS/T24
I do not recall the FTP server ever honoring the HOMEDIR [Home
directory]; i.e. I recall explicitly complaining that the HOMEDIR()
established for the USRPRF had no affect. I always just coded any
script or explicitly used CD; this was almost always a requirement
anyway, to ensure consistency between NAMEFMT and CD, because a script
can not *assume* how the server is configured. However I just tried an
FTP to a v5r3 system [though probably there is a FTP server exit
registered on that system], the Home Directory was being honored when
the Change FTP Attributes (CHGFTPA) [e.g. under CFGTPC option-20,
option-10] has been used to set *both* the "Initial Name Format" NAMEFMT
parameter to *PATH and "Initial directory" CURDIR parameter was set to
*HOMEDIR.
> I have tried on the ftp profile under HomeDir with "QDLS/T24" but this
> goes always to *SAME.
The default value for HOMEDIR() parameter on the CHGUSRPRF and CHGPRF
commands is *SAME. That is the correct default for almost every CHGxxx
command, in order to avoid unexpected and problematic changes.
Although both CHGUSRPRF and CHGPRF have a "prompt override program"
which should set the value from *SAME to the current value as retrieved
from the User Profile named\specified on the USRPRF() parameter, they do
not by v5r3 :-( I can try to explain why, if desired. However, the
DSPUSRPRF should show the explicitly-set value, not the value *SAME.
So as with the CD, the value in the HOMEDIR() must be the
explicit\full path from the root, not an apparent relative path where
the slash '/' character is omitted as prefix; i.e. specify the
HOMEDIR('/QDLS/T24') where the slash '/' character is the prefix to QDLS.
Finally, to ensure that Home Directory is in effect
automatically\implicitly at the FTP server for the user that signed in
with that HOMEDIR() specified for the User Profile, the server
configuration for the FTP application must also be updated, as noted
earlier in this reply.
Regards, Chuck
0 new messages