[comp.databases] Oracle SQL*Forms user defined function keys

drew@hydra.unm.edu (E Drew Einhorn ADV.SCI.Inc) (04/11/90)

They are broken on my machine at work.  I think I have figured out what
I need to do.  I need to add rows to the "esc" table owned by the
system with column "func" equal to "K0" thru "K9" with escape sequences
to match additions to the kermit ".ini" file

Unfortunately the system administrators in control of the system are
very reluctant to make any changes to tables owned by the system.  They
are afraid of breaking it.

I assume Oracle figures out the user's terminal type by looking at the
TERM environment variable, or do they do something unusually strange.
However they do it, it does not appear to be documented in TFM.  I
expect I will have to talk the system administrators into creating a
bogus VT99 terminal description for testing or something like that.

Either that or try to guess the password for the oracle unix login.
Then I can rebuild and replace the VT100.crt file myself.  Guessing may
be easier than it would seem since the oracle password for sys and
system is still manager and change_on_install, respectively.

Actually I would prefer some testimonials, that my approach is sound.
Then I could politely ask them to make my changes and heckle them about
their passwords.  The Army would probably prefer me to be late rather
than sneak past their )-: security :-).

Thanks
drew@hydra.unm.edu

tensmekl@ingr.com (Kermit Tensmeyer) (04/12/90)

In article <2258@ariel.unm.edu> drew@hydra.unm.edu (E Drew Einhorn ADV.SCI.Inc) writes:
>They are broken on my machine at work.  I think I have figured out what
>I need to do.  I need to add rows to the "esc" table owned by the
>system with column "func" equal to "K0" thru "K9" with escape sequences
>to match additions to the kermit ".ini" file
>
>Unfortunately the system administrators in control of the system are
>very reluctant to make any changes to tables owned by the system.  They
>are afraid of breaking it.

	Don't change the working set unless you have the orignal files
	which created the crttab, esc sections of the data tables

	Desc function; (in Sqlplus)
	spool file.fun;
	select * from function;      # This will get the correspondence
	quit;			     #  between function codes and name
>
>I assume Oracle figures out the user's terminal type by looking at the
>TERM environment variable, or do they do something unusually strange.

	Check for a file called default.crt which overrides the TERM
	variable. It's documented somewhere. The method that I found
	is to copy the vt102.sql file to vttest.sql, modify the file
	to reflect that the new name is "whatever"

	"   :g/VT102/ s//VTtest/g  "  is the command in vi.

	execute sqlplus ( or sqldba) 
		sqlplus < vttest.sql | more   ( etc. )

	rerun crt ie     crt sys/XXXXXX VTtest

	and don't make it the default.   Check the dba directory for
	VTtest.crt and copy/rename/move to a terminal name that you can test.
 
>Actually I would prefer some testimonials, that my approach is sound.
>Then I could politely ask them to make my changes and heckle them about
>their passwords.  The Army would probably prefer me to be late rather
>than sneak past their )-: security :-).

	Actually this is the method that I used for development of a crt
	setup that works with Enable on Z-248's for the Army OTJAG. It took
	several weeks to debug both the Enable translate tables and macros
	and the Oracle crt files. If you need the files, I might :-) be
	able to either find the files or you can contact them directly.