12-02-2009
PCC-F-NOERRFILE, unable to open error message file
Hi,
I was compiling few C programs in the unix server and getting the following error message
HTML Code:
rm: /home/a0xxx28/AVT/SEEDLIBRARYDB/LIB/*.a non-existent
proc MODE=ANSI CODE=ANSI_C INCLUDE=/home/a0xxx28/PVT/SEEDLIBRARYDB/INCLUDE
INCLUDE=/home/a0xxx28/PVT/SEEDLIBRARY/INCLUDE INCLUDE=/home/a0xxx28/PVT/UT/INCLUDE DEFINE=SQL DEFINE=AIRFLITE_REL_3
DEFINE=PFM -DPFM_PVTDT iname=costdistDB.pc
PCC-F-NOERRFILE, unable to open error message file, facility PR2
*** Error exit code 1"
Can anybody guide me to resolve this issue?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am trying to build a tuxedo server which in turn depends on several Pro*C programs. I am doing it on HP-UX system.
It looks to me that the ORACLE_HOME is set properly.
But I am getting error message when trying to build.
PCC-F-NOERRFILE, unable to open error message file, facility PR2
exit... (1 Reply)
Discussion started by: asutoshch
1 Replies
2. Programming
While compiling and executing i get the following error.
Error at line 1200, column 1 in file xxx.pc
{
1
PCC-S-02201,Encountered the symbol "{" when expecting one of the following:
; , = < [
please help (1 Reply)
Discussion started by: musavir19
1 Replies
3. UNIX for Dummies Questions & Answers
@
@
@
@
@
@
@
@
@
@
@
@
@
@
@
@
@
@
@
@ (6 Replies)
Discussion started by: bobo
6 Replies
4. Solaris
I am using the "find" command below and it respond with the error message " find: cannot open /: Stale NFS file handle"
what does it mean?
what can I do about it?
Need advice, thanks.
below are the command that I enter, the respond and the error message:
root@ScripServer:/# find / -name... (1 Reply)
Discussion started by: ezsurf
1 Replies
5. UNIX for Advanced & Expert Users
I am working on a unix server.
I killed all the processes with my id on the machine.
After that I tried to delete a file, I got an error:-
file not removed.Text File busy.
Deletion of directory prompted:-
Directory not empty.
Can anyone help me regarding this...???
Thanks,
Vikas (11 Replies)
Discussion started by: vikasrout
11 Replies
6. UNIX for Dummies Questions & Answers
I get this message when I write myshell.c program "VM pagefault:SIGSEGV bad add 0x0 err 0x4 nopage read myshell PM: ciredump signal 11 for 1725 /myshell memory fault (core dumped)"
/* RCS information: $Id: myshell.c,v 1.2 2006/04/05 22:46:33 elm Exp $ */
#include <stdio.h>
#include <unistd.h>... (1 Reply)
Discussion started by: rosecomp
1 Replies
7. Solaris
Hello guys,
Thanks for all your precious tips.
I hope you can give me some advice again.
This time I am having an issue with a SUN FIRE V240 (SOLARIS 10).
The server doesn't boot, normally , first we had a file system error
====================+FIRST ERROR... (6 Replies)
Discussion started by: feg
6 Replies
8. Red Hat
Hi,
I am unable to create/open any file in vi editor for normal user, though using root I am able to create/open any file, using redhat 5.5,
example
vi test
it showing nothing after entering command (9 Replies)
Discussion started by: manoj.solaris
9 Replies
9. UNIX for Dummies Questions & Answers
I am trying to direct a AIX display to my XWindows and I am at a dead end now!
So this what I've done so far:
1. In putty settings, I set "Enable X11 forwarding" and also set "X diplay location" to "localhost:0" (without quotes, of course)
2. Via putty, connected to my AIX server
3. On... (1 Reply)
Discussion started by: shoefiend
1 Replies
10. Shell Programming and Scripting
Hi,
I am trying to open small size file only in vi editor on solaris or Linux machine
but it giving message "Terminal too wide" and then I have to come out.
As shown below:-
-rwxr-x--- 1 rkycadm rkycprd 2445 Sep 12 04:06
$ vi file.txt
Terminal too wide
:q!
----------... (2 Replies)
Discussion started by: RahulJoshi
2 Replies
LEARN ABOUT OSX
mpi_alloc_mem
MPI_Alloc_mem(3OpenMPI) MPI_Alloc_mem(3OpenMPI)
NAME
MPI_Alloc_mem - Allocates a specified memory segment.
SYNTAX
C Syntax
#include <mpi.h>
int MPI_Alloc_mem(MPI_Aint size, MPI_Info info, void *baseptr)
Fortran Syntax (see FORTRAN NOTES)
INCLUDE 'mpif.h'
MPI_ALLOC_MEM(SIZE, INFO, BASEPTR, IERROR)
INTEGER INFO, IERROR
INTEGER(KIND=MPI_ADDRESS_KIND) SIZE, BASEPTR
C++ Syntax
#include <mpi.h>
void* MPI::Alloc_mem(MPI::Aint size, const MPI::Info& info)
INPUT PARAMETERS
size Size of memory segment in bytes (nonnegative integer).
info Info argument (handle).
OUTPUT PARAMETERS
baseptr Pointer to beginning of memory segment allocated.
IERROR Fortran only: Error status (integer).
DESCRIPTION
MPI_Alloc_mem allocates size bytes of memory. The starting address of this memory is returned in the variable base.
FORTRAN NOTES
There is no portable FORTRAN 77 syntax for using MPI_Alloc_mem. There is no portable Fortran syntax for using pointers returned from
MPI_Alloc_mem. However, MPI_Alloc_mem can be used with Sun Fortran compilers.
From FORTRAN 77, you can use the following non-standard declarations for the SIZE and BASEPTR arguments:
INCLUDE "mpif.h"
INTEGER*MPI_ADDRESS_KIND SIZE, BASEPTR
From either FORTRAN 77 or Fortran 90, you can use "Cray pointers" for the BASEPTR argument. Cray pointers are described further in the For-
tran User's Guide and are supported by many Fortran compilers. For example,
INCLUDE "mpif.h"
REAL*4 A(100,100)
POINTER (BASEPTR, A)
INTEGER*MPI_ADDRESS_KIND SIZE
SIZE = 4 * 100 * 100
CALL MPI_ALLOC_MEM(SIZE,MPI_INFO_NULL,BASEPTR,IERR)
! use A
CALL MPI_FREE_MEM(A, IERR)
ERRORS
Almost all MPI routines return an error value; C routines as the value of the function and Fortran routines in the last argument. C++ func-
tions do not return errors. If the default error handler is set to MPI::ERRORS_THROW_EXCEPTIONS, then on error the C++ exception mechanism
will be used to throw an MPI:Exception object.
Before the error value is returned, the current MPI error handler is called. By default, this error handler aborts the MPI job, except for
I/O function errors. The error handler may be changed with MPI_Comm_set_errhandler; the predefined error handler MPI_ERRORS_RETURN may be
used to cause error values to be returned. Note that MPI does not guarantee that an MPI program can continue past an error.
SEE ALSO
MPI_Free_mem
Open MPI 1.2 September 2006 MPI_Alloc_mem(3OpenMPI)