Hi all,
Thanks for your input.
What we did was the following:
1. We copied all the files to a different directory with posix.
2. Deleted the posix directory
3. Deleted the mpe group
4. Created the original directory in posix
5. Copied all the files to that directory
The negative result is that the files are not visible with listf command.
But they are visible with listfile command.
The directory is used for ftp and we don't have issues not having the files
as MPE files.
Kind regards,
Eric Jansen
Technical Consultant
Computer Design & Integration, LLC
696 Route 46 West, Teterboro, NJ 07608
Phone: 201-931-1420 x313
Fax: 201-931-0101
Pager: 973-205-1236
[log in to unmask]
www.cdillc.com
> -----Original Message-----
> From: Barry Lake [mailto:[log in to unmask]]
> Sent: Monday, December 18, 2000 2:00 PM
> To: Mark Bixby; [log in to unmask]; [log in to unmask]
> Subject: Re: POSIX maximum file length
>
>
> At 9:56 AM -0800 12/18/00, Mark Bixby wrote:
> >"Jansen, Eric" wrote:
> >> We are on 5.5pp7 (yes, I know it will be obsolete soon).
> >>
> >> Does anybody know a solution for the maximum
> filenamelength of 32 character
> >> in POSIX?
> >> Or, is this resolved on 6.0?
> >
> >The limit for HFS filenames contained within MPE groups
> >(/ACCOUNT/GROUP/hfsfilename) or MPE accounts
> (/ACCOUNT/hfsfilename) is 16
> >characters, not 32.
> >
> >But for HFS files stored in HFS directories, the filenames
> can be up to 255
> >characters. So you can do things like
> >/ACCOUNT/GROUP/hfsdirectory/superduperreallylonghfsfilename below MPE
> >groups as
> >long as you use an HFS directory to store the long-named files.
>
>
> While HFS object names are limited to 255 characters (unless they're
> directly under root, an account or a group, in which case
> they're limited
> to 16 characters), the overall HFS path can be as long as
> 1023 characters.
>
> Beware, however, that the CI has a maximum command buffer of
> 511 bytes, so
> you can't specify an HFS pathname greater than 511-(length of
> CI command).
> You can get around this by doing a CHDIR to a deeply nested
> directory and
> then use a relative HFS path rather than an absolute path.
> Depending upon
> what you're doing, you might also be able to get around it by
> dropping into
> the shell, in which case you get a much larger command buffer
> to work with
> (I think it may be 8k?).
>
>
> Barry Lake [log in to unmask]
> Allegro Consultants, Inc. www.bogus.allegro.com
> (408)252-2330
> --------
> Attempting to reduce spam influx.
> Remove ".bogus" to create valid address.
>
>
|
