dbTalk Databases Forums  

proplus cd-rom

comp.databases.pick comp.databases.pick


Discuss proplus cd-rom in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Steveh@buspro.biz
 
Posts: n/a

Default proplus cd-rom - 11-02-2006 , 01:10 PM






We are having trouble accessing data on a cd-rom on a proplus 7.2.1
installation using proplus.
We can access the cd-rom data directly through the linux shell, so i am
assuming the hardware
is all ok and there is a D3 proplus glitch.
Our intention was to use the OSFI to import a large data file instead
of trickling it in on accuterm.
It would appear the MOUNT-CD command is performing as designed: it
locates the correct cd-rom device (cd-rom = /dev/hdc) and it creates a
q-pointer as follows:

CDROM
001 q
002
003 unix:/mnt/cdrom

LIST DM,CDROM, returns the error message [201]
'unix:/mnt/cdrom' is not a file name

the sparse proplus documentation on the subject indicates this will
work. I can't find any documentation on OSFI itself, only some fleeting
mentions of the hosts file.

Has anybody successfully set up the cdrom in proplus for OSFI access?
If so, would you be willing to supply the missing pieces?


Reply With Quote
  #2  
Old   
Steveh@buspro.biz
 
Posts: n/a

Default Re: proplus cd-rom - 11-02-2006 , 03:05 PM






Thanks Glen, just tried that and LIST DM,CDROM, results in the same
error
[201] '/mnt/cdrom' is not a file name

I suspect the same thing that I believe you are looking at, and that is
the proplus path required in attribute 3 of the Q-pointer is not
correct. I've tried variations of the path, but can't seem to find a
path that works with proplus to allow access to the cdrom data file
via OSFI. Everything I have tried results in the same [201] error.

D3 doesn't seem to have much documentation regarding path syntax that
proplus is expecting.



Glen B wrote:
Quote:
Drop the unix: and try again.

Glen

Steveh (AT) buspro (DOT) biz> wrote in message
news:1162494601.918746.292620 (AT) b28g2000cwb (DOT) googlegroups.com...
We are having trouble accessing data on a cd-rom on a proplus 7.2.1
installation using proplus.
We can access the cd-rom data directly through the linux shell, so i am
assuming the hardware
is all ok and there is a D3 proplus glitch.
Our intention was to use the OSFI to import a large data file instead
of trickling it in on accuterm.
It would appear the MOUNT-CD command is performing as designed: it
locates the correct cd-rom device (cd-rom = /dev/hdc) and it creates a
q-pointer as follows:

CDROM
001 q
002
003 unix:/mnt/cdrom

LIST DM,CDROM, returns the error message [201]
'unix:/mnt/cdrom' is not a file name

the sparse proplus documentation on the subject indicates this will
work. I can't find any documentation on OSFI itself, only some fleeting
mentions of the hosts file.

Has anybody successfully set up the cdrom in proplus for OSFI access?
If so, would you be willing to supply the missing pieces?



Reply With Quote
  #3  
Old   
Frank Winans
 
Posts: n/a

Default Re: proplus cd-rom - 11-02-2006 , 04:02 PM




<Steveh (AT) buspro (DOT) biz> wrote
Quote:
proplus 7.2.1
locates the correct cd-rom device (cd-rom = /dev/hdc) and it creates a

CDROM
001 q
002
003 unix:/mnt/cdrom

LIST DM,CDROM, returns the error message
[201] 'unix:/mnt/cdrom' is not a file name

Taking the error message seriously makes me suppose
you need to do !mount -r /dev/hdc /mnt/cdrom
at the TCL prompt.

I think your unix:/mnt/cdrom is perfect as-is.
You can also skip making this qpointer and instead
change your LIST command to LIST unix:/mnt/cdrom

If it is mounted then doing !ls /mnt/cdrom
{spelling note -- that is "!ls", being lowercase for "!LS" }
should show the top level directory contents of that media.

!umount /mnt/cdrom
or
!umount /dev/hdc

at the TCL prompt
will reverse the effects of the !mount command. You
will not be allowed to eject the tray while the mount is in
effect. You may enjoy putting a dummy file in /mnt/cdrom/
while no media is mounted, by doing
!echo put a disk in the cdrom drive > /mnt/cdrom/nodisk.txt
so your LIST DM,CDROM, will have a single 'item' nodisk.txt
when issued with no media present.
Just do !mount with no other words to get current status.




Reply With Quote
  #4  
Old   
Ross Ferris
 
Posts: n/a

Default Re: proplus cd-rom - 11-02-2006 , 04:06 PM



Have you/can you use OSFI references to directories in "normal"
(unmounted) file paths .... I've never used ProPlus, and I know it
SHOULDN'T make a difference, but if D3 will "see" /tmp properly, I'd be
inclined to cp the file from the CD to /tmp & process from there

(like I said, I have absolutely ZERO basis for this, and yet... if you
are on support, have you tried a quick call to RD ?)


Reply With Quote
  #5  
Old   
Frank Winans
 
Posts: n/a

Default Re: proplus cd-rom - 11-02-2006 , 04:10 PM



Oops! I forgot to mention you may also need to create that directory;
try doing !mkdir /mnt/cdrom
at the TCL prompt. If it doesn't complain then that was the problem.
Now go ahead and do the mount. If you never mount floppies or anything
else you can just do mounts to /mnt instead of to /mnt/cdrom and save
some typing. Then LIST unix:/mnt instead of LIST unix:/mnt/cdrom

And if as I suspect your 003 unix:/mnt/cdrom

is ok as-is, you can doublecheck by changing it it unix:/tmp
and then your LIST DM,CDROM, will show what files
are in /tmp instead. <<Takes the tricky cdrom hardware
out of the debugging process...>>

"Frank Winans" wrote
Quote:
Taking the error message seriously makes me suppose
you need to do !mount -r /dev/hdc /mnt/cdrom
at the TCL prompt.



Reply With Quote
  #6  
Old   
Steveh@buspro.biz
 
Posts: n/a

Default Re: proplus cd-rom - 11-02-2006 , 04:51 PM



Thanks Frank,

Great ideas on isolating the nature of the problem.
Here are the results from the linux shell at tcl:
:!mount
/dev/hda1 on / type ext2 (rw)
none on /proc type proc (rw)
/dev/hdc on /mnt/cdrom type iso9660 (ro)
:!ls /mnt
cdromfloppy
:!ls /mnt/cdrom
hd110106.txt

I moved down throught the directory structure to the file hd110106.txt
which is the file on the cdrom I an trying to access through D3
proplus. I can see the file fine through the linux shell.

I liked your idea of taking the cdrom out of the picture, here are the
tcl results:
:LIST unix:/tmp
[201] 'unix:/tmp' is not a file name
:!ls /tmp
CX_FLAG d3.install.errs d3virt1.sh.old sav.pick0.0


It seems that D3 proplus can't follow the path or is not receiving the
path in the syntax it is expecting.

Frank Winans wrote:
Quote:
Oops! I forgot to mention you may also need to create that directory;
try doing !mkdir /mnt/cdrom
at the TCL prompt. If it doesn't complain then that was the problem.
Now go ahead and do the mount. If you never mount floppies or anything
else you can just do mounts to /mnt instead of to /mnt/cdrom and save
some typing. Then LIST unix:/mnt instead of LIST unix:/mnt/cdrom

And if as I suspect your 003 unix:/mnt/cdrom

is ok as-is, you can doublecheck by changing it it unix:/tmp
and then your LIST DM,CDROM, will show what files
are in /tmp instead. <<Takes the tricky cdrom hardware
out of the debugging process...

"Frank Winans" wrote
Taking the error message seriously makes me suppose
you need to do !mount -r /dev/hdc /mnt/cdrom
at the TCL prompt.


Reply With Quote
  #7  
Old   
mg.ryder@gmail.com
 
Posts: n/a

Default Re: proplus cd-rom - 11-02-2006 , 05:32 PM




Quote:
:!mount
/dev/hda1 on / type ext2 (rw)
none on /proc type proc (rw)
/dev/hdc on /mnt/cdrom type iso9660 (ro)
:!ls /mnt
cdromfloppy
:!ls /mnt/cdrom
hd110106.txt

Is your installation of D3 activated? AFAIK the OSFI doesn't work on a
non-activated system



Reply With Quote
  #8  
Old   
Frank Winans
 
Posts: n/a

Default Re: proplus cd-rom - 11-02-2006 , 05:35 PM



<Steveh (AT) buspro (DOT) biz> wrote
Quote:
Here are the results from the linux shell at tcl:
:!mount
/dev/hda1 on / type ext2 (rw)
none on /proc type proc (rw)
/dev/hdc on /mnt/cdrom type iso9660 (ro)
:!ls /mnt
cdromfloppy
:!ls /mnt/cdrom
hd110106.txt

I moved down throught the directory structure to the file hd110106.txt
which is the file on the cdrom I an trying to access through D3
proplus. I can see the file fine through the linux shell.

I liked your idea of taking the cdrom out of the picture, here are the
tcl results:
:LIST unix:/tmp
[201] 'unix:/tmp' is not a file name
:!ls /tmp
CX_FLAG d3.install.errs d3virt1.sh.old sav.pick0.0


It seems that D3 proplus can't follow the path or is not receiving the
path in the syntax it is expecting.

Ouch! Well, erm, is your dm,hosts, item 'unix' as follows?
<spelling note: line 001 is digit zero then digit one>

unix
001 01
002
003 r
004
005
006 Remarks text here...




Reply With Quote
  #9  
Old   
Steveh@buspro.biz
 
Posts: n/a

Default Re: proplus cd-rom - 11-02-2006 , 05:49 PM



Ouch is right!

The unix item in the hosts file matches yours.





Frank Winans wrote:
Quote:
Steveh (AT) buspro (DOT) biz> wrote
Here are the results from the linux shell at tcl:
:!mount
/dev/hda1 on / type ext2 (rw)
none on /proc type proc (rw)
/dev/hdc on /mnt/cdrom type iso9660 (ro)
:!ls /mnt
cdromfloppy
:!ls /mnt/cdrom
hd110106.txt

I moved down throught the directory structure to the file hd110106.txt
which is the file on the cdrom I an trying to access through D3
proplus. I can see the file fine through the linux shell.

I liked your idea of taking the cdrom out of the picture, here are the
tcl results:
:LIST unix:/tmp
[201] 'unix:/tmp' is not a file name
:!ls /tmp
CX_FLAG d3.install.errs d3virt1.sh.old sav.pick0.0


It seems that D3 proplus can't follow the path or is not receiving the
path in the syntax it is expecting.

Ouch! Well, erm, is your dm,hosts, item 'unix' as follows?
spelling note: line 001 is digit zero then digit one

unix
001 01
002
003 r
004
005
006 Remarks text here...


Reply With Quote
  #10  
Old   
Frank Winans
 
Posts: n/a

Default Re: proplus cd-rom - 11-02-2006 , 05:51 PM




<mg.ryder (AT) gmail (DOT) com> wrote
Quote:
:!mount
/dev/hda1 on / type ext2 (rw)
none on /proc type proc (rw)
/dev/hdc on /mnt/cdrom type iso9660 (ro)
:!ls /mnt
cdromfloppy
:!ls /mnt/cdrom
hd110106.txt

Is your installation of D3 activated? AFAIK the OSFI doesn't work on a
non-activated system

Yay! Good question! Verify by doing SYSID and seeing entry
OSFI (Networking) Available

Also try doing !/bin/df at the TCL prompt
and see if / {or /tmp , if there is such a row} is full.




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.