Re: CPYFRMIMPF question.

[Vernon Hamberg <vhamberg@xxxxxxxxx>]

Do you need to be enrolled in the system directory for this? I could not
get into QDLS in WRKLNK. I could not ftp to it from Windows. I suspect
CPYFRMPCD would have the same configuration need.

At 12:02 PM 3/27/02 -0500, you wrote:


>yeah, that's a simple ftp or whatever though...then he can just copy it
>over flat...
>
>
>
>On Wed, 27 Mar 2002, Vernon Hamberg wrote:
>
> > CPYFRMPCD has to be in the QDLS document /folder 8.3 file system.
> >
> > At 11:20 AM 3/27/02 -0500, you wrote:
> >
> >
> > >Rick,
> > >
> > >why not move it to the IFS and use CPYFRMPCD ??
> > >
> > >
> > >
> > >On Wed, 27 Mar 2002, Richard B Baird wrote:
> > >
> > > >
> > > > Hey all,
> > > >
> > > > I want to copy a pc file (Flat, fixed length, fixed format) to a
> physical
> > > > file on the 400 (flat, fixed length fixed format).
> > > >
> > > > I want to use *libl to let the os find the file, rather than specifying
> > > > library name.
> > > >
> > > > I've tried CPYFRMSTMF, and it does the copy just the way I want it
> to, but
> > > > it wants a full qualified path name -
> > > > qsys.lib/mylib.lib/myfile.file/mymember.mbr   - no option for *libl.
> > > >
> > > > I've tried CPYFRMIMPF, and it lets me specify *libl on the qualified
> > > > library/file parm, but it requires a field definition file.
> > > >
> > > > My question is, if my file is not delimited, is flat, no field
> conversion
> > > > is needed, why do I need a field definition file?  am I missing a
> parameter
> > > > or something?
> > > >
> > > > Thanks guys!
> > > >
> > > > Rick
> > > >
> > > > _______________________________________________
> > > > 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.
> >
>
>_______________________________________________
>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.