Subject: | |
From: | |
Reply To: | |
Date: | Tue, 13 Apr 1999 15:07:50 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
At 4/13/99 01:08 PM , Juan Rojas wrote:
>Mark,
>It seems to me that you are limited to 16 characters after the "/".
A while back I ran into a problem with long HFS file names and I think it
was Jeff Vance who set me straight. HFS file names are limited to 16
characters (including any extension) if the file is created in an MPE
Group. This restriction does not apply to HFS file names when the file is
placed in a directory. This is just one of the differences between groups
and directories.
John
>>>> Mark Wilkinson <[log in to unmask]> 4/13/99 11:56:22 AM >>>
>I'm trying to open a temporary file using COBOL in the HFS namespace (it
>makes
>it easier to
>generate unique names). I created a test program which generates a filename
>based on the
>date, time and PIN of the process, then uses "SELECT A-FILE ASSIGN ... USING
>A-FILE-NAME"
>within COBOL to try and open the file.
>
>The results of my test are below...
>
>:run mxtest.nmprg;lib=g
>
>Filename: ./W19990413164830700000083
>File status is 9
>Unable to OPEN file, See File System error [9x] (COBERR 644)
>Program file: MXTEST.NMPRG.Y2KDIFDS
>NS3000 IS NOT PRESENT ON THE SYSTEM (FSERR 423)
>
>+-F-I-L-E---I-N-F-O-R-M-A-T-I-O-N---D-I-S-P-L-A-Y+
>! ERROR NUMBER: 0 RESIDUE: 20302 (WORDS) !
>! BLOCK NUMBER: 1413827872 NUMREC: 8276 !
>+------------------------------------------------+
>**** COB_QUIT 644 ****
>
>ABORT: MXTEST.NMPRG.Y2KDIFDS
>NM SYS a.00aa0288 dbg_abort_trace+$24
>NM USER 238.0097c394 COB_QUIT+$b8
>NM PROG 50d.00005bc8 mxtest+$f0
>Program terminated in an error state. (CIERR 976)
>End Run
>
>This is weird because COBOL *can* handle filenames in the HFS namespace but
>obviously not
>in this context. Why it is complaining about NS/3000 not being on the system
>I
>don't know because
>we *do* have NS/3000..
>
>I also tried opening the same file with a full pathname of
>/tmp/W19990413.....
>COBOL opened this
>file OK and wrote a record to it fine. When I tried to re-open the file, I
>got
>an FSERR 52.
>
>Any ideas as to why this happens?
>
>Mark W.
--------------------------------------------------------------
John Korb email: [log in to unmask]
Innovative Software Solutions, Inc.
The thoughts, comments, and opinions expressed herein are mine
and do not reflect those of my employer(s), or anyone else.
|
|
|