Issue with nmon analysing Post: 302771002

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Analysing truss log

I am facing the following issue when using db2. The JDBC prepared statement command is sending an incorrect value to the database for search. I did a truss on the app and here is the log. I want to know what is the value that is getting passed. is it possible. 26867/68: send(62,...

2. AIX

Another NMON

Anyone ever experienced a core dump when running NMON. I am running AIX 5.3 on an 8 CPU LPAR (P570). This has only recently started to happen.

3. AIX

nmon

Can any one help where i can find articals about nomn I need to know how to read this tools ┌─CPU-Utilisation-Small-View───────────────────────────────────────────────────┐ │ 0----------25-----------50----------75----------100│ │CPU User% Sys% Wait% Idle%| ...

4. UNIX for Dummies Questions & Answers

Help analysing progress of a log file

Is it possible to track the progress of a job (informatica) by analysing the progress of it's log file ? I have a long running job, and no way of tracking how far allong it is. Thanks.

5. HP-UX

Query: Analysing the Core file

Hi, Is there any way to find the mode of the binary file (debug or release) by analyzing the core file generated by that binary on the HPUX11i Platform?

6. UNIX for Dummies Questions & Answers

Analysing Log Files?

I'm not sure if this query is relevant to this forum but here goes anyways... I want analyse log files that do not appear to be of standard format. I have tried using Analog but cannot config it to read the files. Does anyone have any advice on working with log files taken from a Unix...

7. Solaris

Analysing a core dump.

Friends I was trying to analyse a core dump using pstack command in Sol5.9(Sparc) The output is as below. root: pstack core_mumux211_istauth_220_108_1229517198_21922 core 'core_mumux211_istauth_220_108_1229517198_21922' of 21922: istauth fe1afbb8 ttcdrv (c10e0, c1db4, 30ad8, bc950, 0, 0)...

8. Shell Programming and Scripting

Analysing Mail Logs

Hello, I have a list of e-mails. I need to know, which email-s from that list not use. I want to do this things: - take email address from email list - find this address in mail logs - if, there is no record about this e-mail adress in list, show this e-mail address on screen I did...

9. Shell Programming and Scripting

Reading and analysing data in a text file

Hi, I have below type of data in a text file in unix. Emp_Name Emp_Dept Raj 101 Amruta 100 Shilpa 100 Rohit 123 Amol 198 Rosh 101 Gaurav 198 Number of employees can be even more. Need a command or a...

10. Shell Programming and Scripting

Problems in analysing SSH LOG users & time

Attached is the log file that I have generated through the following script: last | head -2 |sed '2q;d' |awk '{ print $1"\t"$2"\t"$3"\t\t"$4"\t"$5"\t"$6"\t"$7"\t"$8"\t" $9"\t"$10"\t"$11}'>>/var/log/logadmin/logtest.txt But now I'm unable to run the following operations on it: 1. Count...

LEARN ABOUT DEBIAN

jlex

JLEX(1) 						      General Commands Manual							   JLEX(1)

NAME

       jlex - lexical analyser generator for Java(tm)

SYNOPSIS

       jlex specfile

DESCRIPTION

       JLex takes the language specification in specfile and generates Java(tm) source code for a lexical analyser corresponding to the specifica-
       tion.

       The lexical analyzer source code is placed in a file whose name is the name of the JLex specification file, with the string  ".java"  added
       to  the	end.  For example, if the JLex specification file is called foo.lex, the lexical analyzer source code file that JLex produces will
       be called foo.lex.java.)

       The resulting lexical analyzer source code should be compiled with a Java compiler.  This produces a lexical analyzer class file, which can
       then  be  used in your application.  If the default settings have not been changed, the lexical analyzer class will be called Yylex and the
       class files will named Yylex.class and Yytoken.class.

       For more information, see the JLex manual in /usr/share/doc/jlex/manual.html.

SEE ALSO

       /usr/share/doc/jlex/manual.html, /usr/share/doc/jlex/bugs.html, /usr/share/doc/jlex/README.

DIAGNOSTICS

       jlex produces diagnostic output to inform you of its progress.

BUGS

       See /usr/share/doc/jlex/bugs.html for information about known bugs in JLex.

       Please report bugs in the Debian version of JLex to the Debian bug tracking system in the first instance.   Otherwise,  please  contact	A.
       Appel <appel@princeton.edu>.

AUTHOR

       JLex was written by Elliot Joel Berk at Princeton University.  It is now maintained by C. Scott Ananian.

       This manual page was written by Charles Briscoe-Smith <cpbs@debian.org>, modified by Colin Watson <cjwatson@debian.org>, and is hereby con-
       tributed to the Public Domain.

       Please see the file /usr/share/doc/jlex/copyright for more information.

TRADEMARK ACKNOWLEDGEMENTS

       "Java" is a trademark or registered trademark of Sun Microsystems, Inc.

								    6 Aug 2001								   JLEX(1)

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Analysing truss log

Discussion started by: buytamil

2. AIX

Another NMON

Discussion started by: johnf

3. AIX

nmon

Discussion started by: habuzahra

4. UNIX for Dummies Questions & Answers

Help analysing progress of a log file

Discussion started by: cosmos328is