On Jul 10, 2006, at 1:10 AM, Ismet Kursunoglu wrote:
(substitute the actual file name for /tmp/file.txt):
S MYIO="/tmp/file.txt"
O MYIO W $T
C MYIO
GTM>S MYIO="/home/myvista/testIO.txt"
GTM>O MYIO W $T
1
GTM>C MYIO
GTM>H
[EMAIL PROTECTED]:~/foia06152006$ ls -la ~/testIO.txt
-rw-r--r-- 1 myvista myvista 0 2006-07-09 23:21 /home/myvista/testIO.txt
Yes, I know I'm (back) up in the middle of the night.
The point of this test was to see if you can open the file at the MUMPS level, and it seems you can. If you're interested, a definitive test would be
S MYIO="/home/myvista/testIO.txt"
O MYIO
U MYIO W !,"Hello there!"
C MYIO
Then, go ahead and check the contents of the file.
No matter how I setup the "HFS device" it continues to show
[DEVICE IS BUSY]
I suspect that Kernel is not wanting to open this device. This may seem like foolish question, but are you actually closing the device (D ^%ZISC) after opening it?
************
OUTPUT FROM WHAT FILE: DEVICE//
SORT BY: NAME//
START WITH NAME: FIRST//
FIRST PRINT FIELD: .01 NAME
THEN PRINT FIELD:
Heading (S/C): DEVICE LIST//
DEVICE: HFS Host File Server
HOST FILE NAME: /home/myvista/hfs.dat// INPUT/OUTPUT OPERATION: R//W
[DEVICE IS BUSY]
************
So then I wondered if could an IO task be occupying the device?
Maybe. Keep that one in mind. Better yet, log in from another window and try it again.
Checking Taskman. Current $H=60455,85003 (Jul 09, [EMAIL PROTECTED]:36:43)
RUN NODE=60455,84990 (Jul 09, [EMAIL PROTECTED]:36:30)
Taskman is current..
Checking the Status List:
Node weight status time $J
AKC:giant RUN [EMAIL PROTECTED]:36:30 7601 Main Loop
Checking the Schedule List:
Taskman has no tasks scheduled.
Checking the IO Lists:
There are no tasks waiting for devices.
Checking the Job List:
There are no tasks waiting for partitions.
Checking the Task List:
There are 4 tasks currently running.
On node AKC:giant there is 1 free Sub-Manager(s). Status: Run
******
I can certainly and have been successfully writing, reading and executing
files as the user (myvista) who is running GT.M on the system.
Is this something to do with how the device is setup with reference to the
device number and somehow when I try it doesn't properly set $IO ?
Which defaults to the terminal i.e.
GTM>W $IO
/dev/pts/1
And is it this variable that needs to be set to 10 so to gain access to the
HFS device?
No, that's the current device (think standard input/output).
Select DEVICE NAME: HFS Host File Server /home/myvista/hfs.dat
ANOTHER ONE:
STANDARD CAPTIONED OUTPUT? Yes// (Yes)
Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and Record Number
(IEN)
NUMBER: 10 NAME: HFS
$I: /home/myvista/hfs.dat ASK DEVICE: YES
ASK PARAMETERS: NO SIGN-ON/SYSTEM DEVICE: NO
LOCATION OF TERMINAL: Host File Server
ASK HOST FILE: YES ASK HFS I/O OPERATION: YES
OPEN COUNT: 10 SUBTYPE: P-OTHER
TYPE: HOST FILE SERVER
Now, this looks odd. Why is the OPEN COUNT equal to 10? I'd @-sign out this field, sign out and start over.
I have been reading the GT.M documentation which is very interesting,
but I still don't know why I can't write out a file. I'll read chapter 13 in Walters
and see if I can't find out more.
--
Ismet B. Kursunoglu, MD, FCCP
Medical Director
Alaska Clinic, LLC
3750 E. Country Field Circle, STE B
Wasilla, Alaska 99654-6659
voice (907)357-7240
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
_______________________________________________
Hardhats-members mailing list
