DEC VAX/VMS Sites

Hello
There is a Forte customer in Australia who would like to correspond with
other VAX/VMS Forte sites. The purpose of this correspondence will be to
exchange tips and techniques for using Forte on VAX/VMS machines. Please
respond to me if you can help.
Cheers,
Eric
Eric Gold
Technical Director
Forte Software Pty Ltd
Sydney, Australia
Voice: 61-2-9926-1400
Fax: 61-2-9926-1401

The equivalent of the -xld option is -vax=debug. I can't find
anything in the new compiler regarding the environment
variable LOGICALNAMEMAPPING.
Bob Corbett

Similar Messages

Migrating DEC-DBMS on VAX/VMS to Oracle 8i on AIX

Does anybody have experience of migrating existing DEC-DBMS database on VAX/VMS platform
to Oracle 8i database on AIX platform?
If so can you please provide details such as:
Issues in such migration
If any tools / products are available for automating such migration
Thanks.
Ajay

Hi,
We do have some old toolkits
http://otn.oracle.com/tech/migration/toolkits/content.html
These should help you.
John

VMs crashing randomly with no dump file

Hi all,
I have 11 Windows Server 2008 R2 standard with SP1 VMs sitting on 2 Win Serv 2008 physical servers that keep crashing randomly, nothing on the events logs that can help.
The reboot happen very randomly but always around 12:30AM, I checked the logs on the physical server but couldn't find anything.
Any idea ?
Thanks

Or anti-malware scan?
If you run programs in the management operating system, you should run your antivirus solution there and add the following to the antivirus exclusions:
Virtual machine configuration files directory. By default, it is C:\ProgramData\Microsoft\Windows\Hyper-V.
Virtual machine virtual hard disk files directory. By default, it is C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks.
Snapshot files directory. By default, it is %systemdrive%\ProgramData\Microsoft\Windows\Hyper-V\Snapshots.
Vmms.exe
Vmwp.exe
.:|:.:|:. tim

I need and VMS FTP recommendations for Macbook pro

I need to access a VMS site using FTP for Macbook Pro. Any software suggestions?
thanks!

You need a scanner to scan those slides and make either JPGs or TIF files from them.
Do you have a scanner that can do that and that works with Mac.

Java Runtime errors in Windows (error=2,3,...)

Hello,
I had a Java progam that makes calls to external programs (of the type of question 2 in the FAQ), but for which I have no access to the code (it is intended for Unix). I have Java installed including the docs (except search API). My question is:
error=2, error=3, error=193 are IOEXceptions which mean something like file not found, not an executable file, the processe returned an exception, etc. Where can I find a translation of those cryptic numbers in plain English, within the docs?. Searching the Internet is not efficient ... TIA
LT

Just to add some perspective:
Almost all UNIX platforms provide a file called /usr/include/errno.h (or same name in a subdirectory /usr/include/*/*.h ) as part of the baseline OS. It is only about 100 error codes and is based on the UNIX system calls. This file is provided even for those UNIX platforms (like Solaris) that do not provide any form of C compiler with the OS software (you have to pay extra for the compiler, often a lot extra). Its pedigree goes back to the origins of UNIX.
While Microsoft has a web page with their error code info, they do not provide the file is as part of the baseline OS. I agree that Sun could attempt to provide pointers, maybe as part of a FAQ on their web site. Perhaps Sun does not want to get bogged down with the complexities introduced by a major competitor's legacy issues:
ERRNO.H (for the WIN32 version, about 40 codes, for the C Runtime Library)
ERROR.H (DOS error codes, derived from XENIX, OS/2)
WINERROR.H (12,000 line header file all Win32 codes know at that time, using fields � la DEC's VMS, but includes codes of ERROR.H)
I expect that Sun's implementation of System.exec() calls the Win32 API routine CreateProcess and that probably the only codes you will see returned are defined in ERROR.H

Looking for Xcode training resource using C++

I have been programming for over twenty years in the CAD (Computer Aided Design) field, and I would like to start programming on the Mac. I have owned various Apple computers since 1987 (Apple IIGS, SE30, ... G5), and I used to code on the Mac using Hypercard back in the late 80'sm early 90's. But all my work related programming has been on other computers, UNIX based, DEC VAX, and now for the last ten years the PC using Microsoft Visual Studio and .NET 2003. I'm really not that old, I just started coding when I was very young.
I have always loved the Mac and it is the only computer I have at home. So now I want to start using the Xcode environment. But I would really rather just stick with C++ since that is what I've been using for the last decade or so.
Does anyone have any suggestions on a good resource (book, manual, etc.) that teaches the Xcode environment using C++ instead of Objective-C?
Thanks much,
Tom

Xcode is just an IDE. You probably need to make a decision about what API or application framework you want to use.
If you really must use C++, you'll probably have to use Carbon, which exports C APIs. There are some cross-platform app frameworks in C++, such as Qt or wxWidgets, but they're either not free or provide a poor user experience. There don't really seem to be any recent books which detail modern best practices in Carbon, but take a look at http://www.carbondev.com/site/?page=CarbonBooks
Most people coming to the platform go down the Cocoa route. Really, if you know C (which you do if you know C++) and you are comfortable with OO concepts, then learning the Obj-C language is just a case of sitting down with Apple's guide for an afternoon. Cocoa brings lots of new concepts to the table, but you'll have an initial barrier to learning an API/framework whatever you go with... Sticking to C++ because it's "what you know" is almost certainly disingenuous.
If you really do just want to learn the IDE, then there are various books which cover Xcode and the associated development tools. See http://www.carbondev.com/site/?page=Xcode+Books

TDS Connect Failure Error 17832 - Login Packet used to open the connection is structually invalid

I have a package which uses TDS, Tabular Data Stream, to connect from a VAX VMS system to SQL server and it works for all flavors of SQL server. Except for one server. When I try to connect to this server the application gets disconnected after sending the
Login 7.x message. The server is running Windows 2008 R2 Standard, SP1, 64-bit and is in a domain. SQL Server is 2008 R2 (10.50.4000). SQL Server is configured for "SQL Server and Windows Authentication mode" in Server Properties,
Security, Server authentication. It is set to "allow remote connections to this server". The TCP/IP Client Protocol is enabled in SQL Server Network Configuration, Protocols for MSSQLSERVER. The SQL log shows 2 Logon source errors
upon the connection attempt :
Error: 17832, Severity 20, State 11.
The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 172.19.20.122]
I took a dump of the login packet from the client side package and included it here:
Sending Login7.x message
Sending PktTyp=10 LstPkt=01 PktNum=0001 PktSiz=00B8
0000 b0 00 00 00 01 00 00 71 00 10 00 00 07 00 00 00
0010 a8 00 00 00 00 00 00 00 e0 03 00 00 68 01 00 00
0020 04 09 00 00 56 00 06 00 62 00 02 00 66 00 02 00
0030 6a 00 06 00 76 00 0c 00 00 00 00 00 8e 00 0c 00
0040 a6 00 00 00 a6 00 05 00 00 06 5b e4 96 08 00 00
0050 00 00 b6 00 00 00 4c 00 54 00 56 00 56 00 53 00
0060 42 00 51 00 41 00 b0 a5 b1 a5 47 00 41 00 4e 00
0070 53 00 4b 00 45 00 69 00 68 00 65 00 2d 00 70 00
0080 61 00 2d 00 73 00 71 00 6c 00 30 00 31 00 54 00
0090 44 00 53 00 5f 00 53 00 45 00 52 00 56 00 49 00
00a0 43 00 45 00 53 00 48 00 38 00 34 00 44 00 42 00
0000        q                    h       V   b   f   j
v
0040           [           L T V V S B Q A     G A N S K E i h e - p
0080 a - s q l 0 1 T D S _ S E R V I C E S H 8 4 D B
I found other sites which discussed the connection ring buffers and so, I queried them for any information which might help:
select cast(record as xml) xml_record from sys.dm_os_ring_buffers where ring_buffer_type = 'RING_BUFFER_CONNECTIVITY';
xml_record:
<Record id="53" type="RING_BUFFER_CONNECTIVITY" time="1697484630">
<ConnectivityTraceRecord>
    <RecordType>ConnectionClose</RecordType>
    <RecordSource>Tds</RecordSource>
    <Spid>0</Spid>
    <SniConnectionId>32E3FDFC-2BF2-4EB8-82D2-AE05E73AFCBC</SniConnectionId>
    <SniProvider>7</SniProvider>
    <RemoteHost>172.19.20.122</RemoteHost>
    <RemotePort>1069</RemotePort>
    <LocalHost>156.144.249.81</LocalHost>
    <LocalPort>1433</LocalPort>
    <RecordTime>11/7/2014 15:13:42.729</RecordTime>
    <TdsBuffersInformation>
      <TdsInputBufferError>0</TdsInputBufferError>
      <TdsOutputBufferError>0</TdsOutputBufferError>
      <TdsInputBufferBytes>184</TdsInputBufferBytes>
    </TdsBuffersInformation>
    <TdsDisconnectFlags>
      <PhysicalConnectionIsKilled>0</PhysicalConnectionIsKilled>
      <DisconnectDueToReadError>0</DisconnectDueToReadError>
      <NetworkErrorFoundInInputStream>0</NetworkErrorFoundInInputStream>
      <ErrorFoundBeforeLogin>1</ErrorFoundBeforeLogin>
      <SessionIsKilled>0</SessionIsKilled>
      <NormalDisconnect>0</NormalDisconnect>
      <NormalLogout>0</NormalLogout>
    </TdsDisconnectFlags>
</ConnectivityTraceRecord>
<Stack>
    <frame id="0">0X0000000001E21F3B</frame>
    <frame id="1">0X0000000001E1EE4E</frame>
    <frame id="2">0X00000000010D2984</frame>
    <frame id="3">0X0000000000A8AB94</frame>
    <frame id="4">0X0000000000A8B05E</frame>
    <frame id="5">0X0000000000A8AD57</frame>
    <frame id="6">0X0000000000F651DE</frame>
    <frame id="7">0X0000000000F65395</frame>
    <frame id="8">0X0000000000F68925</frame>
    <frame id="9">0X0000000000F659D6</frame>
    <frame id="10">0X00000000755937D7</frame>
    <frame id="11">0X0000000075593894</frame>
    <frame id="12">0X00000000779159ED</frame>
    <frame id="13">0X0000000077B4C541</frame>
</Stack>
</Record>
I feel the problem is in the configuration of the server's authentication which is requiring something beyond SQL server authentication.
Any help would be appreciated. Thanks in advance.

One other item of note is the "SQL Server Network Configuration (32bit) "on this server is empty -- no "Protocols for MSSQLSERVER" branch like the 64-bit "SQL Server Network Configuration".
This is perfectly normal if all you have is a 64-bit instance on the machine. You would only see items here if you have a 32-bit server.
The odd part is the Native Client Configuration shows up under (32bit) with Client Protocols...
Yes, you always have a 32-bit client, which is to be used with 32-bit applications.
In any case, whether server is 32-bit or 64-bit is immaterial when you connect.
I'm afraid that I have not worked with TDS packets so that I can say what is wrong with this package, and I don't think I will try to read the TDS spec to say what the problem may be. But the issue seems to be that whatever you are using to create
the TDS packets is not doing this fully correctly.
Erland Sommarskog, SQL Server MVP, [email protected]

Using RMI to invocate an object on a a non-JAVA or Windows platform

Hello and how are things? I might be way off base, but I really just want to make sure this cannot be done. What i have is I want to build an Java app that will upload a file to a stream and pass that data over to an VAX VMS system that is non-JAVA. Then once I connected to that server I need to call a program on that server that will process this data stream into the Database. I have been reading up on RMI and that seems to be my solution, but I want to aske some RMI experters. Is this solution seem possible? Thanks
C

Okay that is what I exepected to hear, I just wanted to verify. Now with COBRA does the other system still need som sort of JAVA-RMI or IDL? I guess I will need to research COBRA a little more. Any good sites or just use java.sun.com?

Rdb 6.1 migration to Oracle

When compiling get_table.sc on vax/vms get a sqlbugchk.dmp. Has
anyone else encountered this error?
null

I work in Rdb support for Oracle. I've recreated Marsha's
problem and think this is a parsing problem within the .SC
files that get created.
Can someone that supports this product on this web site contact
me? [email protected]
Thanks,
Don
null

PRO*C MAKE 화일의 비밀

제품 : PRECOMPILERS
작성날짜 : 1995-11-21
Understanding and Modifying Precompiler and OCI Makefiles
Note: This bulletin is also posted under the PCC category (#104220.448).
In order to successfully create a program using the Oracle Precompilers (Pro*C,
Pro*COBOL, Pro*FORTRAN, Pro*Ada, etc.) you need to precompile, compile, and
link your program with the Oracle libraries. On Unix systems, the easiest way
to do this is to use the 'make' utility. Make is a unix command that enables
you to manipulate files automatically. It works by way of a makefile, which is
a file written in a language that 'make' can understand. Oracle provides
makefiles for precompiling, compiling, and linking your programs. They can be
found under the $ORACLE_HOME subdirectory, in
$ORACLE_HOME/proc/demo/proc.mk for Pro*C,
$ORACLE_HOME/procob/demo/procob.mk for Pro*COBOL,
$ORACLE_HOME/profor/demo/profor.mk for Pro*FORTRAN, and
$ORACLE_HOME/proada/demo/proada.mk for Pro*Ada.
All of the makefiles are very similar in terms of the macros that they define,
and how they are used. The remainder of this bulletin will use Pro*C and
proc.mk as an example, but the concepts discussed here are also relevant to the
other languages.
This bulletin is divided into 6 sections and two appendecies:
I. How to use proc.mk for version 1.4, 1.5, and 1.6 of Pro*C
II. How to use proc.mk for version 2.0 of Pro*C
III. How does proc.mk work?
IV. Modifying proc.mk to change the precompile and compile options, and to
add your own libraries
V. Modifying proc.mk for a program which has more than one source module
VI. How to link OCI programs using proc.mk or oracle.mk
VII. Some issues about linking
Appendix A. Source code for the multiple module example
Appendix B. List of useful makefile macros
I. How to use proc.mk for version 1.4, 1.5, and 1.6 of Pro*C
The makefile for these Pro*C versions is set up to create an executable from a
program that is in a single source file. To use it, copy proc.mk from
$ORACLE_HOME/proc/demo into the directory which contains your source code.
This directory also contains electronic versions of the sample programs found
in the "Pro*C Supplement to the Oracle Precompilers Guide". Once you have
copied proc.mk into your directory, you can create your executable by just
typing 'make -f proc.mk <program name>', where <program name> is
the file containing your code, without the .pc extension. For example, if your
code is in my_prog.pc, you would use 'make -f proc.mk my_prog':
unix$ make -f proc.mk my_prog
/u02/7016/bin/proc iname=my_prog.pc ireclen=132 oreclen=132 select_error=no
Pro*C: Release 1.5.10.1.0 - Production on Thu Sep 1 15:09:47 1994
Copyright (c) Oracle Corporation 1979, 1992. All rights reserved.
Precompiling my_prog.pc
/usr/5bin/cc -I. -O -Bdynamic -L/u02/7016/lib -o my_prog my_prog.c /u02/7016/li
b/libsql.a /u02/7016/lib/osntab.o -lsqlnet -lora /u02/7016/lib/libpls.a -lsqlne
t -lnlsrtl -lcv6 -lcore -lnlsrtl -lcv6 -lcore -lm
The above example was done on a Sun with Oracle 7.0.16.6 and Pro*C 1.5.10.1.0.
Your output may look a little different if you are on a different unix system.
After running this command, several files should have been created in the
current directory. my_prog.c is the C output from the precompiler.
my_prog.lis is also generated by the precompiler, and is the listing file that
gives you information about the precompilation. The executable will be called
my_prog.
II. How to use proc.mk for version 2.0 of Pro*C
proc.mk for version 2.0 is much more generic. It is designed to link together
programs that are in multiple modules, without modification. Again, the
makefile itself is found in $ORACLE_HOME/proc/demo, along with the sample
programs. In order to use it for a single module, you would use
'make -f proc.mk EXE=<program name> OBJS=<program name>.o' (after copying
proc.mk to your own directory). For example:
unix$ make -f proc20.mk EXE=my_prog OBJS=my_prog.o
/u03/oracle7.1/bin/proc iname=my_prog.pc
Pro*C: Release 2.0.3.0.0 - Production on Thu Sep 1 15:55:26 1994
Copyright (c) Oracle Corporation 1979, 1994. All rights reserved.
System default option values taken from: /u03/oracle7.1/proc/pmscfg.h
/usr/5bin/cc -I. -O -I/u03/oracle7.1/proc/lib -c my_prog.c
/usr/5bin/cc -Bdynamic -L/u03/oracle7.1/lib -o my_prog my_prog.o -lsql /u03/ora
cle7.1/lib/osntab.o -lsqlnet -lora -lsqlnet -lora -lnlsrtl -lcv6 -lcore -lnls
rtl -lcv6 -lcore `cat /u03/oracle7.1/rdbms/lib/sysliblist`
This will generate the same files as the previous example, plus my_prog.o,
which is an object file containing the compiled form of your code. It is then
linked with the Oracle libraries to create the executable.
III. How does proc.mk work?
To understand proc.mk, first we need to go into some details about how a
makefile works. Makefiles are usually made up of two kinds of entries -
targets and macro definitions.
The general format of a target entry is
<target>: <target1> <target2> ... <targetn>
<command1>
<command2>
<commandm>
Note that there are TABS, not spaces, before each of the <command> lines.
This entry tells make how to create <target> from <target1> through
<targetn>. To do this, make just needs to execute <command1> through
<commandm>. For example, the target entry
my_prog.c: my_prog.pc
proc iname=my_prog.pc ireclen=132 oreclen=132
tells make that to create my_prog.c, if my_prog.pc exists in the current
directory, it just has to run 'proc iname=my_prog.c'. This target rule will be
applied when 'make -f <makefile> my_prog.c' is issued from the unix prompt.
Targets can be chained together as well. For example if you had the target
entry
my_prog.o: my_prog.c
cc -c my_prog.c
in addition to the one above, then make would be able to create my_prog.o from
my_prog.pc by precompiling and compiling. Note that these two entries could
have been combined into
my_prog.o: my_prog.pc
proc iname=my_prog.pc ireclen=132 oreclen=132
cc -c my_prog.c
which would have the same effect.
There are also some special formats for targets, which don't depend on specific
file names. For example, the following sequence of targets creates an object
file from any .pc file:
.SUFFIXES: .pc .c .o
.pc.o:
proc iname=$*.pc ireclen=132 oreclen=132
cc -c $*.c
Note the special syntax here. The .SUFFIXES rule tells make what suffixes
to look for. The .pc.o rule (which has no dependencies) explains how to get
from a .pc file to a .o file. Inside the commands, $* will evaluate to the
filename (without the extension) of whatever file is currently being worked on.
If we put the above example into a file (called example.mk) and run it, we get:
unix$> make -f example.mk my_prog.o
proc iname=my_prog.pc ireclen=132 oreclen=132
Pro*C: Release 1.5.10.1.0 - Production on Mon Sep 19 15:53:22 1994
Copyright (c) Oracle Corporation 1979, 1992. All rights reserved.
Precompiling my_prog.pc
cc -c my_prog.c
unix$
Notice that $* has been replaced with my_prog in the proc and cc commands.
Also note that we had to type 'my_prog.o' on the command line. This is because
the target rule was '.pc.o:'. If it was just '.pc:', then we wouldn't have
needed the .o extension on the command line. But then make wouldn't know that
this command creates a .o file. Make is smart enough to put together a .pc.c
and a .c.o rule to create a .o file from a .pc file.
The other kind of makefile entry is a macro definition. They usually look
like:
MACRONAME=macrotext
This defines the macro MACRONAME to be macrotext. Whenever make sees
$(MACRONAME) (Note the parenthesis), it will be replaced by macrotext. For
example,
PROFLAGS=ireclen=132 oreclen=132
my_prog.c: my_prog.pc
proc iname=my_prog.pc $(PROFLAGS)
will accomplish the same thing as the first example in this section.
'$(PROFLAGS)' will be replaced by 'ireclen=132 oreclen=132' (without the
quotes).
Macros can be defined more than once in a makefile. In that case, the
definition that is last (furthest from the start) will be the one used for the
entire file. Previous definitions are ignored.
IV. Modifying proc.mk to change the precompile and compile options, and to
add your own libraries
NOTE: Be careful of changing too many options, especially the compile and/or
link options. In many cases, changing these to values that are different from
the supplied ones in proc.mk can cause problems. Contact Worldwide Support if
you have questions about any of the compile or link options used in our default
supplied makefiles.
Consider this section of the makefile for Pro*C 1.5.10:
# General suffix rule to build executables from .pc and .c files.
# Usage :
# make -f proc.mk USERID=<user/pass> <prog>
# For example to build an executable from a Pro*C source file named 'abc.pc'
# using scott/tiger for the ORACLE account name. The make command line will
# be:
# make -f proc.mk USERID=scott/tiger abc
# Note: scott/tiger is the default account/password, so that you could
# also use the following command line:
# make -f proc.mk abc
# The executable will be named 'abc'.
.pc:
-$(PROC) iname=$*.pc $(PROFLAGS)
@$(ECHO) $(CC) $(CFLAGS) $(LDFLAGS) -o $* $*.c $(PROLDLIBS)
.c:
@$(ECHO) $(CC) $(CFLAGS) $(LDFLAGS) -o $* $*.c $(PROLDLIBS)
These two target rules tell make how to precompile and compile. See the
previous section for details on how these work. When you run the make, what
actually gets executed are the commands under '.pc:'. The first line is the
precompile, and the second is the compile. If you want to change the
precompiler options, change the PROFLAGS macro. By default, it is set by
PROFLAGS=ireclen=132 oreclen=132 select_error=no $(SQLCHECK) $(PROUSER)
If you want to add the option maxopencursors=20, to change the initial size of
the precompiler cache, you would add it to this line:
PROFLAGS=ireclen=132 oreclen=132 select_error=no maxopencursors=20
Note that I have removed the SQLCHECK and PROUSER macros. They are not
defined by default, so they do not evaluate to anything. You can define them
if you like, which can be used to add additional options such as SQLCHECK and
USERID. See the precompiler manual for more information about the available
precompiler options.
Similarly, you can set compile options with CFLAGS and link options with
LDFLAGS. Appendix B lists other macros used by proc.mk which you may find
useful.
In order to add additional libraries to the link, you can add them to the
PROLDLIBS macro. proc.mk for 1.5.10 (on the Sun) defines this macro as:
PROLDLIBS= $(LIBSQL) $(TTLIBS)
LIBSQL and TTLIBS are other macros previously defined. You can add your own
libraries to this macro to add them to the link:
PROLDLIBS= $(LIBSQL) $(TTLIBS) my_lib1.o my_lib2.o
Better results are obtained if you add your own libraries either after or
before the Oracle libraries. Putting your libraries in between LIBSQL and
TTLIBS can cause undefined symbols.
V. Modifying proc.mk for a program which has more than one source module
Many complicated programs are contained in more than one source module, unlike
the samples. Some of these modules would contain only C functions, and thus
have .c extensions. But the rest would contain embedded SQL as well, and
consequently have .pc extensions. How would you compile and link in a
situation such as this? In the remainder of this section, I present one
solution.
This solution uses the following files, which are included in Appendix A:
File Functions Contained in the File Functions Called by this File
main.c main db_connect, print_names,
db_disconnect
connect.pc db_connect, db_disconnect, none
sqlerror
print_names.pc print_names none
main.h db_connect, db_disconnect,
print_names, sqlerror (This is the header file)
For Pro*C 2.0, proc.mk can compile these together by using the EXE and OBJS
macros. The first target in the makefile (which will be executed if you don't
specify a target on the make line) looks like:
build: $(OBJS)
$(CC) $(LDFLAGS) -o $(EXE) $(OBJS) $(PROLDLIBS)
There are also default rules that tell make how to get from a .pc file to a .o
file:
.SUFFIXES: .exe .o .c .pc
.pc.c:
$(PROC) $(PROFLAGS) iname=$*.pc
.pc.o:
$(PROC) $(PROFLAGS) iname=$*.pc
$(CC) $(CFLAGS) $(PROCINC) -c $*.c
.c.o:
$(CC) $(CFLAGS) $(PROCINC) -c $*.c
So you can define the EXE macro to be the name of the executable, and the OBJS
macro to be the object files used. You can either do this in the makefile
itself (and then run it with 'make -f proc.mk') or, define them on the command
line. To compile the example, use:
make -f proc.mk EXE=main OBJS="connect.o print_names.o main.o"
Note the double quotes around the object lists. This is to pass the spaces as
part of the macro.
For Pro*C 1.5, consider the following, which should be added to the end of the
makefile:
OBJECTS=main.o print_names.o connect.o
main: $(OBJECTS)
@$(ECHO) $(CC) $(CFLAGS) -o main $(OBJECTS) $(PROLDLIBS) \\
$(CLIBS)
main.o: main.c main.h
@$(ECHO) $(CC) $(CFLAGS) -c main.c
connect.o: connect.pc main.h
@$(ECHO) $(PROC) iname=connect.pc $(PROFLAGS)
@$(ECHO) $(CC) $(CFLAGS) -c connect.c
print_names.o: print_names.pc main.h
@$(ECHO) $(PROC) iname=print_names.pc $(PROFLAGS)
@$(ECHO) $(CC) $(CFLAGS) -c print_names.c
If you are not on a Sun as I am, the commands under connect.o and print_names.o
should be the same as those under the '.pc:' target. Under main.o, the command
should be the same as that under '.c:'. Compare the commands given here to
those from my proc.mk, shown at the beginning of section IV.
Again note that there are TABS, not spaces, before the command lines for
precompilation and compilation, in accordance with the makefile format. With
the above lines added to the end of proc.mk, we can create the executable by
issuing 'make -f proc.mk main'. The output I get when running for the first
time (no additional files beyond the original 4 exist) is:
technique /home/csupport/surman/make> make -f proc.mk main
/usr/5bin/cc -I. -O -c main.c
/u02/7016/bin/proc iname=print_names.pc ireclen=132 oreclen=132 select_error=no
Pro*C: Release 1.5.10.1.0 - Production on Wed Sep 21 17:37:02 1994
Copyright (c) Oracle Corporation 1979, 1992. All rights reserved.
Precompiling print_names.pc
/usr/5bin/cc -I. -O -c print_names.c
/u02/7016/bin/proc iname=connect.pc ireclen=132 oreclen=132 select_error=no
Pro*C: Release 1.5.10.1.0 - Production on Wed Sep 21 17:37:06 1994
Copyright (c) Oracle Corporation 1979, 1992. All rights reserved.
Precompiling connect.pc
/usr/5bin/cc -I. -O -c connect.c
/usr/5bin/cc -I. -O -o main main.o print_names.o connect.o /u02/7016/lib/libsql
.a /u02/7016/lib/osntab.o -lsqlnet -lora /u02/7016/lib/libpls.a -lsqlnet -lnlsr
tl -lcv6 -lcore -lnlsrtl -lcv6 -lcore -lm -lm
After running as above, a number of additional files are created. The
files connect.lis and print_names.lis are generated by the
precompiler, along with connect.c and print_names.c. Each of the .c
files is then compiled with the '-c' option to create a .o file. So
we get main.o, connect.o, and print_names.o. Finally, the object
files are linked together to form the final executable, which is
called 'main'.
What are all these files? The .c extension signifies a file
containing pure C code. The main program is in main.c to start with.
The .pc extension signifies a file containing C code with embedded
SQL, suitable for precompiling. The precompiler generates the .c file
from the .pc file. The .lis extension signifies a listing file, also
generated by the precompiler. It contains a trace of the
precompilation attempt. Files with the .o extension are library
files. They contain compiled code, and can be linked together into
one executable. Different compilers can generate .o files, created
from source files written in different languages. All of the .o files
can be linked together, regardless of the original source language.
main.h is the header file. This contains external definitions for
the functions referenced by each module. This is necessary so the compiler
will understand the correct prototype for each function. Note that
it is referenced on the target line for each file. This is so
the files are recompiled when the header file is changed.
The linking is done by the final cc command, located under the make
target main:
@$(ECHO) $(CC) $(CFLAGS) -o main $(OBJECTS) $(PROLDLIBS) \\
$(CLIBS)
The only new thing here is the -o option. This is an option to the
cc command which tells the compiler the name of the output file. In
this case, it is called 'main'. If no output file is specified, the
compiler usually calls it 'a.out'.
Using this method has the advantage that make will only compile those files
which need to be changed. For example, consider the main target:
main: $(OBJECTS)
@$(ECHO) $(CC) $(CFLAGS) -o main $(OBJECTS) $(PROLDLIBS) \\
$(CLIBS)
Whenever one of $(OBJECTS) (in this case, the object files created
by compilation) has changed, make will run the commands under this
target (in this case, the link command).
What this means is that only those files which have been changed will
be recompiled. If you change print_names.pc (try "touch print_names.pc"
from the unix prompt) and run make, you will get only:
unix$ touch print_names.pc
unix$ make -f proc.mk main
/u02/7016/bin/proc ireclen=132 oreclen=132 select_error=no iname=print_names.pc
Pro*C: Release 1.5.10.1.0 - Production on Wed Sep 21 17:48:48 1994
Copyright (c) Oracle Corporation 1979, 1992. All rights reserved.
Precompiling print_names.pc
/u02/7016/bin/proc iname=print_names.pc ireclen=132 oreclen=132 select_error=no
Pro*C: Release 1.5.10.1.0 - Production on Wed Sep 21 17:48:50 1994
Copyright (c) Oracle Corporation 1979, 1992. All rights reserved.
Precompiling print_names.pc
/usr/5bin/cc -I. -O -c print_names.c
/usr/5bin/cc -I. -O -o main main.o print_names.o connect.o /u02/7016/lib/libsql
.a /u02/7016/lib/osntab.o -lsqlnet -lora /u02/7016/lib/libpls.a -lsqlnet -lnlsr
tl -lcv6 -lcore -lnlsrtl -lcv6 -lcore -lm -lm
unix$
Notice that the only thing that was done here was to precompile and
compile print_names.pc, generating print_names.o. Then, since main
depends on print_names.o, the final cc command (which links the final
executable) was also done. So the same make command will only
recompile those modules which have changed. This can be significant
when linking in many modules, some of which can take a long time to
compile. For more information on the make command, I suggest that you
look at a Unix or make manual. One such book is "Managing Projects
with Make", by Andrew Oram and Steve Talbott.
Note that you can create suffix rules for the proc.mk for 1.5, similar to the
ones for Pro*C 2.0. By using suffix rules, it is possible to shorten this
example. The commands for each of the .pc files are identical. Rather
than having a separate entry for each one, you can create general
suffix rules that tell make how to create a .o file from a .pc file, for
example. For more information on how to do this, I recommend that you
consult a book or tutorial on make, such as the book referenced above.
VI. How to link OCI programs using proc.mk or oracle.mk
The libraries used to link OCI programs are very similar to the libraries used
to link Pro*C programs. The main difference is that OCI programs link with
libocic.a, and Pro*C programs link with libsql.a. Both can be found under
$ORACLE_HOME/lib for Oracle7, and $ORACLE_HOME/rdbms/lib for version 6.
For Oracle7, you can use either proc.mk or oracle.mk to link OCI code.
oracle.mk is a makefile found in $ORACLE_HOME/rdbms/lib, and is used mainly for
linking various options into the Oracle RDBMS itself, as well as for linking
the Oracle executables. There are also targets in oracle.mk which will link
the sample OCI programs cdemo1.c through cdemo3.c. Following are these
targets, taken from the oracle.mk for 7.0.16 on Sun:
OCILDLIBS= $(LIBOCIC) $(TTLIBS) $(LLIBCORE)
INCLUDE= -I$(ORACLE_HOME)/rdbms/demo
MAKEDEMO= \\
@if [ "$(NONDEFER)" = "true" -o "$(NONDEFER)" = "TRUE" ] ; then \\
$(ECHO) $(CC) $(LDFLAGS) -o $@ $? $(NDFOPT) $(OCILDLIBS) $(CLIBS); \\
else \\
$(ECHO) $(CC) $(LDFLAGS) -o $@ $? $(OCILDLIBS) $(CLIBS); \\
fi
cdemo1: cdemo1.o
$(MAKEDEMO)
.c.o:
$(CC) -c $(INCLUDE) $(CFLAGS) $*.c
First note the '.c.o' target rule. Note that the INCLUDE macro is here, which
has the -I compiler option to include the directory where the demo header files
are located. The cdemo1 target will execute the MAKEDEMO macro. Based on
whether or not the NONDEFER macro is "true" or "TRUE", the program is linked
either with or without the nondeferred option. Notice that if NONDEFER is true,
then the NDFOPT macro is included in the link. If NONDEFER isn't true, then
NDFOPT isn't included. That's the only difference. If you link with the
nondeferred option, than deferring the parse with the defflg parameter of
oparse() has no effect. See the OCI manual for more information on the
oparse() function and what it does. In most cases, you will want the ability
to defer the parse, and so you wouldn't link with NDFOPT. Other than NDFOPT,
the libraries to link with are OCILDLIBS and CLIBS. So you can use these
macros in your own makefile to link OCI programs.
proc.mk can also be used to link OCI programs. Like oracle.mk, it also defines
OCILDLIBS. The link line would look like the line under the .pc: target used
for Pro*C programs, but would use OCILDLIBS instead of PROLDLIBS:
@$(ECHO) $(CC) $(CFLAGS) $(LDFLAGS) -o $* $*.c $(OCILDLIBS)
Note that proc.mk does not link with the nondeferred option. For version 6,
there are no OCI targets in oracle.mk, so you should use proc.mk as the
template to link OCI programs. For Oracle7, use either proc.mk or oracle.mk.
VII. Some issues about linking
Most unix linkers are one-pass. This means that the linker will only examine
the symbols in your executable once. Because of this, several of the Oracle
libraries need to be included more than once to resolve all of the symbols.
This is because the libraries are mutually referencial - functions in one
library call functions in another, and the second library in turn calls
functions in the first library. As a result, it is not recommended that you
change the order of the libraries in the link. If you add your own libraries,
add them either before or after the Oracle libraries. Don't put them between
Oracle libraries on the link line. The Oracle libraries would be PROLDLIBS for
Pro*C programs, and OCILDLIBS for OCI programs. If you use a utility such as
'nmake', you should be aware of how that differs from 'make', as well. Macro
processing can be different between the two utilities.
You should also be aware that the specific Oracle libraries used vary between
operating systems and Oracle versions. If you upgrade the precompiler and the
database, chances are that the libraries necessary will also change. So you
may have to change any existing makefiles. Always use the proc.mk that ships
with the precompiler as a guide to which libraries are necessary.
There are two different ways to specify a library to be included in the link.
One is to fully qualify the name of the library (such as /u02/7016/lib/libsql.a
in the above example). Another is to use the -l option. If you specify a
library (such as -lnlsrtl) this tells the linker to look for a library called
libnlsrtl.a in the library search path. To add directories to the library
search path, use the -L option. For example, the LDFLAGS macro should contain
-L$(ORACLE_HOME)/lib. This tells the linker to look in this directory to find
libraries specified with -l. Some of the Oracle libraries are fully qualified,
and some are included with -L and -l. Both have the same effect.
You can create your own libraries by using the 'ar' unix command. This utility
allows you to archive several .o object files into one .a library archive.
Consult your unix man pages on 'ar' for more information on this command and
how to use it.
Appendix A: Source code for the multiple module example
Here are the files used in this example:
**** FILE main.h ****
extern void sqlerror();
extern void connect();
extern void print_names();
extern void disconnect();
*** FILE main.c ****
#include <stdio.h>
#include "main.h"
void main() {
int dept;
printf("Hello There!\
printf("Now connecting...\
connect("scott", "tiger");
printf("Enter dept no: ");
scanf("%d", &dept);
print_names(dept);
printf("Disconnecting...\
disconnect();
**** FILE connect.pc ****
#include <stdio.h>
#include "main.h"
EXEC SQL include sqlca;
void connect(username, password)
char *username;
char *password; {
EXEC SQL begin declare section;
VARCHAR un[20];
VARCHAR pw[20];
EXEC SQL end declare section;
strcpy(un.arr, username);
un.len = strlen(un.arr);
strcpy(pw.arr, password);
pw.len = strlen(pw.arr);
EXEC SQL whenever sqlerror do sqlerror();
EXEC SQL connect :un identified by :pw;
void disconnect() {
EXEC SQL commit work release;
void sqlerror() {
printf("SQL error!!\
EXEC SQL whenever sqlerror continue;
printf("% .70s \
",sqlca.sqlerrm.sqlerrmc);
EXEC SQL rollback release;
exit(1);
**** FILE print_names.pc ****
#include <stdio.h>
#include "main.h"
EXEC SQL include sqlca;
EXEC SQL begin declare section;
VARCHAR ename[20];
EXEC SQL end declare section;
void print_names(dept)
EXEC SQL begin declare section;
int dept;
EXEC SQL end declare section; {
EXEC SQL whenever sqlerror do sqlerror();
EXEC SQL DECLARE emp_cursor CURSOR FOR
select ename
from emp
where deptno = :dept;
EXEC SQL OPEN emp_cursor;
EXEC SQL whenever not found goto done_loop;
printf("Employees in dept %d:\
", dept);
for (;;) {
EXEC SQL fetch emp_cursor into :ename;
ename.arr[ename.len] = '\\0';
printf("%s\
", ename.arr);
done_loop:
EXEC SQL CLOSE emp_cursor;
Appendix B. List of useful makefile macros
Note that many of these macros are defined, but not all of them. proc.mk for
Pro*C 2.0, for example, uses PROFLAGS in the precompile targets, but does not
define it.
PROFLAGS: options to be passed to the precompiler, such as ireclen or
sqlcheck
CFLAGS: options to be passed to the compiler, such as -I or -O
LDFLAGS: options to be passed to the linker, such as -L
CC (or RCC): the C compiler (/usr/5bin/cc for Sun)
PROC: the precompiler ($ORACLE_HOME/bin/proc)
LIBHOME: directory in which to find the Oracle libs ($ORACLE_HOME/lib for
Oracle7, $ORACLE_HOME/rdbms/lib for version 6)
LIBxxx: Oracle library libxxx.a fully qualified (such as LIBSQL, equal to
$(LIBHOME)/libsql.a)
LLIBxxx: Oracle library libxxx.a, using -l (such as LLIBCORE, equal to
-lcore)
PROLDLIBS: Oracle libraries necessary to link (defined in terms of other
macros)
OCILDLIBS: Oracle libraries necessary to link programs using the Oracle
Call Interfaces (OCI) (also defined in terms of other macros)
______________________________________________________________________________

Robert B     gin (self) (guest) wrote:
: Robert B     gin (guest) wrote:
: : Since I've last posted, I've installed RedHat 5.2 and
ditched
: : Slackware!
: : (btw, what a breeze - Hat's off to RH! very nice install!).
: : I've then installed oracle, have managed to setup
tnsnames.ora
: : so I can connect via sqlplus to my remote database (on
: VAX/VMS).
: : But now I have Pro*C linker problems with:
: : make -f demo_proc.mk build OBJS=test.o exe=test
: : (blah,blah,blah)
: : /usr/lib/crt1.o(.text+0x36): undefined reference to `main'
: : make: *** [build] Error 1
: : Does anybody out there have a similar problem?
: : Rob
: Duh! forget it... (EXE has to be caps... RTFM)
: (cryptic error message though?)
: works great!!!
Could you please tell me where I can get demo_proc.mk file
for Linux (RedHat)?
Thanks
null

How to use LD_LIBRARY_PATH et al properly

My ultimate goal is to get MonoDevelop working under OS X and also to develop some Macport 'ports' for the application components that MonoDevelop needs but are not there yet. So far I have managed to write the Macport 'ports' and each installs OK (there are problems but they are for elsewhere and I don't beleive that are relavent here).
One of the components needed is Mozilla and it builds (form the Macports port) correctly. However it places a .dylib in /opt/local/lib/mozilla-1.7.12/libgtkembedmoz.dylib and there are no links (hard or soft - at least as far as I can tell) to this file from somewhere else.
Being a Mono project, there is a reference to this file from one of the ".dll" files, with the corresponding 'config' file (gecko-sharp.dll.config) redirecting the reference to the .dylib file. So far so good and all normal.
However the .dylib file cannot be found - and I'm guessing because it is 1 directory level down form where the .dylib files are normally placed (at least by MacPorts) and can be found by all of the other programs.
I could edit the config file to put in the actual file path, but that means it will break when Mozilla is upgraded, and generally does not seem to be the right way to go.
I've tried to use LDLIBRARYPATH, DYLDLIBRARYPATH and DYLDFALLBACK_LIBRARYPATH for get the additional location into the search path, but this breaks everything else (as in apps that were working now report errors in not finding library files). (There seems to be a difference between the behaviour when none of these environment variables are defined and when any one of them is).
Therefore, is there some place I can get an understandable understanding of:
1) what I should be doing to have the system extend the library search paths
2) understand what each of these variables does, and how they interact
BTW, LDLIBRARYPATH is set to /opt/local/lib, but as soon as I add anything onto the end, it seems to break those things that worked before!
Thanks for any advise, pointers and/or references.
Susan

Aussie Susan wrote:
I'm not saying that I have installed anything that uses or requires LD_xxx or DYLD_xxx variables to work. I have installed Mozilla which 'seems' (from my limited experience with OS X and UNIX in general - I'm from the old VAX/VMS days!) to install its libraries in places that are not on the 'normal' search paths.
I know less about Mozilla than you. But I do know that MacOS X doesn't even have to use search paths. You can embed a dynamic library inside an application bundle and then use the installnametool to tell the application where to find it.
Mozilla is a hard one. The macports version could be all screwy. The "original" version could be just as, if not more, screwy. The bigger the project, the more apt they are to make up their own rules and ways of doing things.
This means that:
1) I must be missing something in my understanding of how to install Mozilla and I'm inadvertently letting it something wrong (I always thought the general extract/configure/make/make-install pattern is sufficient until you want to do something beyond the usual)
This is a possibility. There could be something special you need to set in configure to make it (MonoDevelop) work with Mozilla. Or Mono might only work with version 4.1.03-RC2 (for example) of Mozilla on OSX. I don't know. The research I did the other day before getting on my anti-macports soapbox was all from 2005. You may have to track down those 2005-vintage packages before it will work.
2) I have a lack of understanding of how software is expected to work on OS X/UNIX
#2 is certainly true and actually forms the basis of my original question.
The same is true for me. In particular, Apple would prefer people to make Frameworks. What little I do with dynamic libraries I do very carefully because I know how easy they are to break. The fact that you've gotten 81/82 working is remarkable.
The only issue I have with downloading and installing however many packages is finding them in the first place. Again it is probably because I have not yet come to 'think' like a UNIX programmer, I have to use Google to try to locate the distribution for a piece of software, download it, extract it, try the ./configure command and wade through all of the 'can't find XXX with a version number >= n.n.n' type messages, go back to the Internet to try to locate each package, down load it..... all while trying to keep track of where I am.
Yes, that is a problem. Macports is a solution to that problem. However, it (or any similar product) causes its own set of problems. Back before MacOS X days, when I was trying to use Linux, I tried to use all the Linux tools that did the same thing as Macports. You want to install project C, that depends on B, that depends on A, version 2.0. Fine, you let the "portage/etc" tool do all the work and project C is running. However, your DHCP client needed project A, version 1.2 and your Internet doesn't work anymore. Repeat.
The nice thing about the Linux tools is that they work using the standard locations, usually /usr/local. Again, usually, you don't have to mess with LDLIBRARYPATH to get something in /usr/local working.
My Solaris experience tells me that anything requiring a change to LDLIBRARYPATH is going to cost at least $20,000 and run horribly.
It seems to me that, if this work has already been done, then why reinvent the wheel.
I certainly appreciate the ability to gain access to a vast resource pool of programs and information that is around in the UNIX world, but I'm struggling with understanding how it is supposed to work. Where ever you go, you come across GIT, RPM, Fink, MacPorts, and a variety of other systems that all try to solve this same problem so I can't be alone.
The only thing I don't like about Fink and MacPorts is that they use that strange /opt location. The Linux tools like RPM and portage use /usr/local. I would actually really like to have a package manager that kept track of all the open-source packages I've installed, as long as I was sure each installation was a vanilla installation identical to what I would have done by hand. Plus, the Linux tools have been around for a lot longer and are much more robust (and even they break things on a regular basis). Finally, I know you aren't alone. I see a fairly regular stream of people having problems with open-source tools they've installed using macports/fink. I try it on my system (without macports/fink) and it works perfectly. Not much else I can do in that case. They need to ask the macports/fink people for help.
All this still comes back to my original question: where can I get a 'beginner guide' to how the dynamic loader works, how should it work, what is expected of programs to make it work, what variations can be allowed and what should never be even thought of!
I don't think such a thing exists. There is probably a multi-volume 'expert guide' though.
I strongly suspect that the last time Mono worked on OS X was 2005. The core tools and dependencies have evolved since then, but nobody bothered to update it all for MacOS X. Apple threw Intel into the Mix and things don't work anymore. There maybe some hard-core Mono/OSX people who do know how to get it working, but I don't think they are on this discussion forum.
That si why I think the packaging software is a bit is a side issue. The only reason I mentioned it is to try to give you some idea of the context of my question (in other discussions I am often frustrated when someone asks a question but does not give enough context to answer it properly - I would rather be able to ignore information given to me than have to go back and ask for more information).
No problem. I would much rather have long, descriptive messages that the two-liners "I hacked it. It's broken. Can you fix it?" posts.
Sorry about the 'rant'. I really do appreciate the fact that you are trying to help me.
I like rants:) I will do what I can, but I don't think I'm really qualified. The sad fact is that the Mac just isn't as well supported in the open source world. The Linux situation isn't that much better, but it is different. There is always some existing Linux configuration that will work, it just may take you 8-9 tries. On MacOS X, the only working configuration may be the one that you hack up.
For example, there is a nice package (that shall remain nameless) that is supposed to give you the full power of Cocoa in Perl. I'm a big Perl fan so I jumped on it. The latest version was labelled "Now working on Intel Macs!" I found one particular function call that didn't work. I was puzzed and investigated. I worked several hours hacking things up trying to get this one particular function call (out of many) to work. My thinking was that is this one random function is broken, how many others are? Finally, at 2 in the morning I gave up and send an e-mail to the maintainer saying I found found what I thought was a bug, hoping he might know more. He responded right away with a message saying "Yes, it doesn't work on Intel Macs after all. It needs a different library."
I'm confident I could put that new library in and get it working, but I just have other things to do. I've spent too much time on it already. I'll just do my little tools in Objective-C for now and keep Cocoa out of Perl. That is my typical experience. So, if you are having trouble with a project that is much larger than the one I've described, you should probably contact the maintainers and see if it even works at all, and what you need to do to make it work.

Queries related to Oracle 9i Application server

I have some queries related to JDBC and oracle 9i Applcation
server.
1. Does JDBC Driver supporting VAX/VMS comes with the Oracle 9i
App
Server?
2. What JDBC Driver is supported for Oracle 9i Application
Server?
3. Is the JDBC Driver Platform Independent?
4. Can we separate OC4J Servlet engine(Web Container) from
Oracle 9i Application
server and put it on a different machine?
5. What other Servlet engine is compatible with Oracle 9i
Application server?
and finally ...
we are developing application with Oracle database in Sun
Solaris 2.8 OS
and after development we have planned to change the oracle
database to
VAX/VMS OS , Will there be any deployment issue because of OS
inconsistency.
Please reply me asap.It will be greatful to you.We are looking
for answers for a very long time.
Thanks
Anand

Dillip,
You can find some documentation (EJB/Servlet Developers Guide) at http://otn.oracle.com/tech/java/oc4j/content.html. We will be posting Oc4J users guide and services guide very soon.
regards
Debu Panda
Oracle

Sharing files between users - GETTING STRESSED!!!!

Hi guys,
I'm getting REALLY annoyed with Leopard - I have two users on the same iMac, all I want to do is share EVERYTHING without any passwords getting in the way.
Now when I empty the trash on my OWN desktop it asks for a password, when I add photos to my pictures folder it asks for a password, pretty much when I do ANYTHING it asks for a **ing password.
We are both set up as ADMIN users.
I'm really starting to get frustrated with Leopard - such a simple task is so unclear.
Can someone please advise before I throw it out of the window!
Thanks guys..

total 72
drwxr-xr-x+ 18 jackdixon jackdixon 612 1 Mar 09:47 .
0: group:everyone deny delete
1: user:Olli allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
drwxr-xr-x 6 root admin 204 9 Feb 09:20 ..
-rwxr-xr-x+ 1 jackdixon jackdixon 3 28 Dec 15:36 .CFUserTextEncoding
0: group:everyone deny delete
1: user:Olli allow read,write,append,readattr,writeattr,readextattr,writeextattr,readsecurity
-rwxr-xr-x@ 1 jackdixon jackdixon 15364 2 Mar 22:01 .DS_Store
0: group:everyone deny delete
1: user:Olli allow read,write,append,readattr,writeattr,readextattr,writeextattr,readsecurity
drwxr-xr-x+ 2 jackdixon jackdixon 68 2 Mar 21:59 .Trash
0: group:everyone deny delete
1: user:Olli allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
-rwxr-xr-x+ 1 jackdixon jackdixon 103 13 Jan 09:43 .bash_history
0: group:everyone deny delete
1: user:Olli allow read,write,append,readattr,writeattr,readextattr,writeextattr,readsecurity
-rwxr-xr-x+ 1 jackdixon jackdixon 48 1 Mar 09:53 .parallels_settings
0: group:everyone deny delete
1: user:Olli allow read,write,append,readattr,writeattr,readextattr,writeextattr,readsecurity
drwxr-xr-x+ 8 jackdixon jackdixon 272 2 Mar 21:59 Desktop
0: group:everyone deny delete
1: user:Olli allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
drwxr-xr-x+ 20 jackdixon jackdixon 680 27 Feb 22:52 Documents
0: group:everyone deny delete
1: user:Olli allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
drwxr-xr-x+ 57 jackdixon jackdixon 1938 29 Feb 07:16 Downloads
0: group:everyone deny delete
1: user:Olli allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
drwxr-xr-x+ 32 jackdixon jackdixon 1088 2 Mar 20:45 Library
0: group:everyone deny delete
1: user:Olli allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
drwxr-xr-x+ 31 jackdixon jackdixon 1054 15 Feb 20:35 Movies
0: group:everyone deny delete
1: user:Olli allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
drwxr-xr-x+ 10 jackdixon jackdixon 340 2 Mar 21:53 Music
0: group:everyone deny delete
1: user:Olli allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
drwxr-xr-x+ 20 jackdixon jackdixon 680 2 Mar 21:40 Pictures
0: group:everyone deny delete
1: user:Olli allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
drwxr-xr-x+ 5 jackdixon jackdixon 170 28 Dec 17:47 Public
0: group:everyone deny delete
1: user:Olli allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
lrwxr-xr-x+ 1 jackdixon jackdixon 59 28 Dec 15:36 Send Registration -> /Users/jackdixon/Library/Assistants/Send Registration.setup
0: group:everyone deny delete
1: user:Olli allow read,write,append,readattr,writeattr,readextattr,writeextattr,readsecurity
drwxr-xr-x+ 5 jackdixon jackdixon 170 28 Dec 15:36 Sites
0: group:everyone deny delete
1: user:Olli allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
-rwxr-xr-x+ 1 jackdixon jackdixon 2461 1 Mar 09:49 wrapperLog.txt
0: group:everyone deny delete
1: user:Olli allow read,write,append,readattr,writeattr,readextattr,writeextattr,readsecurity
Macintosh:~ jackdixon$

Pro*C linker problems

System is Linux Mandrake 6.0 with Oracle 8i, with the 8i patch
applied.
What a nightmare that install was! Lots of permission problems,
unreadable directories, programs with no execute permission on
them and so on.
I now have a database up and running, and am trying to get Pro*C
working. The code was written on RedHat 5.2 with Oracle 8.0.5,
and worked fine there, so I know it is not a fundamental code
problem!
I have patched the pcscfg.cfg file as detailed in the patch FAQ
(with modifications for the slightly different paths under
Mandrake Linux).
When I compile the Pro*c file, I get many "undefined reference
to 'dbcon'" and "undefined reference to 'ctx'" errors from the
linker. This occurs whether I use a pre-defined list of specific
libraries in my own Makefile, or if I use the standard
demo_proc.mk makefile. I have used nm(1) on every place I can
think of, to try to find the required library/object, but to no
avail.
I appreciate that Oracle have so far only certified Oracle for
Linux against Redhat 6.0, but surely Mandrake can't be THAT
different ;-)
Does anybody have any ideas, known problems etc? I REALLY HOPE
that I don't have to switch to Redhat as the only solution - no
problem with Redhat, it would just require a tedious and
complicated system rebuild, which I don't have the time to do :-(
TIA
Mike Holden
null

Robert B gin (self) (guest) wrote:
: Robert B gin (guest) wrote:
: : Since I've last posted, I've installed RedHat 5.2 and
ditched
: : Slackware!
: : (btw, what a breeze - Hat's off to RH! very nice install!).
: : I've then installed oracle, have managed to setup
tnsnames.ora
: : so I can connect via sqlplus to my remote database (on
: VAX/VMS).
: : But now I have Pro*C linker problems with:
: : make -f demo_proc.mk build OBJS=test.o exe=test
: : (blah,blah,blah)
: : /usr/lib/crt1.o(.text+0x36): undefined reference to `main'
: : make: *** [build] Error 1
: : Does anybody out there have a similar problem?
: : Rob
: Duh! forget it... (EXE has to be caps... RTFM)
: (cryptic error message though?)
: works great!!!
Could you please tell me where I can get demo_proc.mk file
for Linux (RedHat)?
Thanks
null

Sybase sql server to oracle

I am looking for help in migrating some tables from our old sybase database on vax vms to oracle 8i database on windows 2000.
can somebody please help me out on the best way to do this. Migration workbench is ruled out as the version of sybase is not supported and also i do not have the sybase client software.
can somebody give me the bcp out commands to also the sql*loader commands and control file to do this.
email : [email protected]
Thanks

hi - just an fyi
we have SQL Server 2012 and from my reads and understanding OGG supports SQL Server up to 2008. not to say it wouldn't work on higher versions if installed. in the link above check out the SQL Server installation chapter. before purchasing the license I would contact Oracle.
maybe someone here has installed it on a higher version and got it to work. we are currently working on setting up OGG to work on Oracle to Oracle servers.

DEC VAX/VMS Sites

Similar Messages

Maybe you are looking for