 
| Subject: | |
| From: | |
| Reply To: | [log in to unmask][log in to unmask], 19 May 1998 15:38:23 -0700350_- My system came with the 1.2 quantum fireball and I went to a western digital 2.5. Very disapointed with speed and noise. I now have the Quantum Fireball 6.4 and it's fast and roomy. No problems. I've heard nothing but good things. And I love quantums. Just because you had a bad experience with one, don't misjudge a good product. [...]42_19May199815:38: [log in to unmask] |
| Date: | Tue, 26 May 1998 12:44:11 -0700 |
| Content-Type: | text/plain |
| Parts/Attachments: |
|
|
Michael Anderson writes:
> FYI, It seems that using COBOL II/iX(ANSI85), on MPE/iX 5.5, you can't
> move an FDNAME into another 16 bit item in Working Storage, without
> writing a subprogram.
First, thank you for sharing the final solution!
If you're not keen on having a subprogram just to get the file number,
I just tried a hack that worked fine. Of course, I don't know that it
will *always* work.... ;)
Since you can pass the FD name to a routine, I passed it to... PUTJCW.
FINDJCW was then used to retrieve the value. To verify this was indeed
the "real" file number, I passed it to PRINTFILEINFO, which gave a
tombstone for the expected file.
The call to PUTJCW was pretty vanilla:
FD MYFILE.
...
CALL INTRINSIC "PUTJCW" USING JCW-NAME
MYFILE
JCW-STATUS.
and FINDJCW expects a 16-bit logical:
05 MYFILE-FILENUM PIC 9(4) COMP.
...
CALL INTRINSIC "FINDJCW" USING JCW-NAME
MYFILE-FILENUM
JCW-STATUS.
Just a thought...
--Glenn Cole
Software al dente, Inc.
[log in to unmask]
|
|
|
