Sponsored Content
Full Discussion: Encountered error!
UNIX Standards and Benchmarks UNIX & LINUX Benchmarks (Version 3.11) UNIX Benchmarks Encountered error! Post 302087908 by puspendu on Thursday 7th of September 2006 04:37:28 AM
Old 09-07-2006
Encountered error!

I used this on an AIX machine and encountered the following error.

$ ls -l
total 600
-rwxrwxrwx 1 e26936 dba 1491 Feb 07 1992 MANIFEST
-rwxrwxrwx 1 e26936 dba 8148 Apr 05 1992 Makefile
-rwxrwxrwx 1 e26936 dba 4852 Sep 06 2003 README
-rwxrwxrwx 1 e26936 dba 934 Sep 06 2003 README.submittal
-rwxrwxrwx 1 e26936 dba 13657 Apr 05 1992 Run
-rwxrwxrwx 1 e26936 dba 120991 Sep 06 2003 a.zip
-rwxrwxrwx 1 e26936 dba 90133 Apr 06 1992 awk.Z
drwxrwxrwx 2 e26936 dba 512 Sep 07 13:54 doc
drwxrwxrwx 2 e26936 dba 512 Sep 07 13:54 pgms
drwxrwxrwx 2 e26936 dba 512 Sep 07 13:51 results
-rwxrwxrwx 1 e26936 dba 19246 Apr 06 1992 sort.Z
drwxrwxrwx 2 e26936 dba 512 Sep 07 13:54 src
drwxrwxrwx 2 e26936 dba 512 Sep 07 13:54 testdir
drwxrwxrwx 2 e26936 dba 512 Sep 07 13:54 time
drwxrwxrwx 2 e26936 dba 512 Sep 07 13:52 tmp
$ make
Checking distribution of files
./pgms exists
./src exists
./testdir exists
./doc exists
/bin/sh: test: 0403-004 Specify a parameter with this command.
exists
./results exists
gcc -o ./pgms/arithoh -DTIME -O -Darithoh ./src/arith.c
In file included from /usr/local/lib/gcc-lib/powerpc-ibm-aix4.3.2.0/3.0.1/include/sys/signal.h:309,
from /usr/include/signal.h:34,
from src/timeit.c:27,
from src/arith.c:31:
/usr/include/sys/context.h:169: parse error before "sigset64_t"
/usr/include/sys/context.h:172: parse error before '}' token
make: 1254-004 The error code from the last command is 1.


Stop.
$
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

554 Unallowed chars encountered

My Exchange v5.5 IMS server received an inbound internet-based message that it could not processed. The message header appeared to be corrupt and had a line that read, "Diagnostic-Code: smtp;554 Unallowed chars encountered." The message header also mentions UTF-7. All internet-based messages are... (1 Reply)
Discussion started by: abibbens
1 Replies

2. Solaris

Encountered a strange problem with doing a restore

Hi Unix Guru's, I have encountered a strange problem with doing a restore on a local sunu machine. We have 2 live system (v880, v450) and 1 test system v440. All the machines are sun4u and using sun os 8.0 We have 2 backup device. One Bcakup device connected with v880 and another backup... (0 Replies)
Discussion started by: cpandian
0 Replies

3. UNIX for Dummies Questions & Answers

Read lines till a blank line is encountered

Hi, I have reached at a specified offset from the start of file. My requirement is that I want to read only those lines, which have the string READ / ALTER / UPDATE. As soon as, none of these literals are found in the subsequent line, I want to stop reading. Is there any feature of grep which... (1 Reply)
Discussion started by: saurabhsinha23
1 Replies

4. UNIX and Linux Applications

Invalid stack address encountered

Hello All, One of our applications is not able to start after trying to set p4 port. This is the log that is reported: JLaunchISetP4Port: set p4 port 50004 ------------------------------------------- Signal 15 encountered. => 64 bit R/3 Kernel => 64 bit AIX Kernel => Heap limit ... (0 Replies)
Discussion started by: RoshniMehta
0 Replies

5. Shell Programming and Scripting

select contents between two delimiters (not working if newline in encountered)

Hi, I am facing difficulties in selecting the contents between two delimiters when there is a new line occurs.. Eg: >more sample.txt abcd -- this is the first line % efgh-- this is the second line and not able to print % ijkl -- this is the 3rd line % when i search for abcd and... (8 Replies)
Discussion started by: Balaji PK
8 Replies

6. AIX

Error encountered in creating a filesystem

Hi experts, Need help on the below error please. I am creating Filesystem and it fails with the below errors :( Command: failed stdout: yes stderr: no Before command completion, additional instructions may appear below. 0518-506 odmget: Cannot open object class PdAt ... (10 Replies)
Discussion started by: EngnrRG
10 Replies

7. Shell Programming and Scripting

Create new file when three asterisks are encountered.

Hi All, I have a text file which is currently formatted like this: TEXT1 *** TEXT2 *** TEXT3 *** I want text before *** to go into separate files. For example, 1.dat TEXT1 (5 Replies)
Discussion started by: shoaibjameel123
5 Replies

8. Shell Programming and Scripting

awk - continue when encountered division error

Hello, How can I add a logic to awk to tell it to print 0 when encountering a division by zero attempted? Below is the code. Everything in the code works fine except the piece that I want to calculate read/write IO size. I take the kbr / rs and kbw / ws. There are times when the iostat data... (5 Replies)
Discussion started by: tommyd
5 Replies

9. Shell Programming and Scripting

Notify as soon as an error is encountered in a script

Hi, The script below works okay and emails me the log in the end once the script completes but what I'm trying to do is to also notify me via an email as soon as the script encounters any error whatsoever. cat test.list hdisk0 00a6351a2c832da1 rootvg ... (7 Replies)
Discussion started by: mbak
7 Replies
CUBRID_PCONNECT_WITH_URL(3)						 1					       CUBRID_PCONNECT_WITH_URL(3)

cubrid_pconnect_with_url - Open a persistent connection to CUBRID server

SYNOPSIS
resource cubrid_pconnect_with_url (string $conn_url, [string $userid], [string $passwd]) DESCRIPTION
Establishes a persistent connection to a CUBRID server. cubrid_pconnect_with_url(3) acts very much like cubrid_connect_with_url(3) with two major differences. First, when connecting, the function would first try to find a (persistent) link that's already open with the same host, port, dbname and userid. If one is found, an identifier for it will be returned instead of opening a new connection. Second, the connection to the SQL server will not be closed when the execution of the script ends. Instead, the link will remain open for future use (cubrid_close(3) or cubrid_disconnect(3) will not close links established by cubrid_pconnect_with_url(3)). This type of link is therefore called 'persistent'. <url> ::= CUBRID:<host>:<db_name>:<db_user>:<db_password>:[?<properties>] <properties> ::= <property> [&<property>] <properties> ::= alhosts=<alternative_hosts>[ &rctime=<time>] <properties> ::= login_timeout=<milli_sec> <properties> ::= query_timeout=<milli_sec> <properties> ::= disconnect_on_query_timeout=true|false <alternative_hosts> ::= <standby_broker1_host>:<port> [,<standby_broker2_host>:<port>] <host> := HOSTNAME | IP_ADDR <time> := SECOND <milli_sec> := MILLI SECOND ohost : A host name or IP address of the master database odb_name : A name of the database odb_user : A name of the database user odb_password : A database user password o alhosts : Specifies the broker information of the standby server, which is used for failover when it is impossible to connect to the active server. You can specify multiple brokers for failover, and the connection to the brokers is attempted in the order listed in alhosts o rctime : An interval between the attempts to connect to the active broker in which failure occurred. After a failure occurs, the system connects to the broker specified by althosts (failover), terminates the transaction, and then attempts to connect to the active broker of the master database at every rctime. The default value is 600 seconds. o login_timeout : Timeout value (unit: msec.) for database login. The default value is 0, which means infinite postponement. o query_timeout : Timeout value (unit: msec.) for query request. Upon timeout, a message to cancel requesting a query transferred to server is sent. The return value can depend on the disconnect_on_query_timeout configuration; even though the message to cancel a request is sent to server, that request may succeed. o disconnect_on_query_timeout : Configures a value whether to immediately return an error of function being executed upon timeout. The default value is false. Note ? and : that are used as identifiers in PHP connection URL can't be included in the password. The following is an example of a pass- word that is invalid to use as connection URL because it contains " ?:". $url = "CUBRID:localhost:33000:tdb:dba:12?:?login_timeout=100"; Passwords that contain ? or : may be passed as a separate parameter. $url = "CUBRID:localhost:33000:tbd:::?login_timeout=100"; $conn = cubrid_pconnect_with_url ($url, "dba", "12?"); If user or password is empty,you can't delete " :",the following is an example. $url = "CUBRID:localhost:33000:demodb:::"; PARAMETERS
o $conn_url -A character string that contains server connection information. o $userid -User name for the database. o $passwd -User password. RETURN VALUES
Connection identifier, when process is successful. FALSE, when process is unsuccessful. EXAMPLES
Example #1 cubrid_pconnect_with_url(3) url without properties example <?php $conn_url = "CUBRID:127.0.0.1:33000:demodb:dba::" $con = cubrid_pconnect_with_url ($conn_url); if ($con) { echo "connected successfully"; cubrid_execute($con, "create table person(id int,name char(16))"); $req =cubrid_execute($con, "insert into person values(1,'James')"); if ($req) { cubrid_close_request ($req); cubrid_commit ($con); } else { cubrid_rollback ($con); } cubrid_disconnect ($con); } ?> Example #2 cubrid_pconnect_with_url(3) url with properties example <?php $conn_url = "CUBRID:127.0.0.1:33000:demodb:dba::?althost=10.34.63.132:33088&rctime=100" $con = cubrid_pconnect_with_url ($conn_url); if ($con) { echo "connected successfully"; $req =cubrid_execute($con, "insert into person values(1,'James')"); if ($req) { cubrid_close_request ($req); cubrid_commit ($con); } else { cubrid_rollback ($con); } cubrid_disconnect ($con); } ?> SEE ALSO
cubrid_connect(3), cubrid_pconnect(3), cubrid_pconnect_with_url(3), cubrid_disconnect(3), cubrid_close(3). PHP Documentation Group CUBRID_PCONNECT_WITH_URL(3)
All times are GMT -4. The time now is 11:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy