HP NonStop SSL Reference Manual page 88

---
--- EOF reached, done
---
The second runtime argument can be used to create a new EDIT file containing the log file contents. The following
example shows how to convert the whole log file into an edit file (note that this can take some time for large files):
42> showlog pxyslog logedit
comForte SHOWLOG log file converter Version T9999A05_16Apr2009_comForte_SHOWLOG_
0022
starting at binary offset 0
starting at offset 0
writing out-file 'logedit'
---processing in-file 'pxyslog'
---
--- EOF reached, done
---
43> fi logedit
$data1.ssl
CODE
logedit
44>
The third and last runtime arguments can be used to limit the part of the file which is converted. This is helpful for the
viewing large log files. The following example shows dumping a large log file. Only a limited number of log messages
(totaling 10000 bytes) after a given offset (5000000) are shown:
33> run showlog telslog * 5000000 10000
comForte SHOWLOG log file converter Version T9999A05_16Apr2009_comForte_SHOWLOG_
0022
dumping at most 10000 bytes
---processing in-file 'telslog'
(output not shown here)
---
---finishing dump of file before end-of-file
---
---done 34>
Rather than using byte offsets, SHOWLOG can also use timestamp as filters for which parts of the log file to display.
The command
SHOWLOG logfile * "30Jan07 20:00" "30Jan07 21:00"
will only display log messages between the two given timestamps.
Note: By using '*' as the second runtime argument the output is written to the home terminal. When using the byte offset
parameter or the byte offset parameter and length parameter, the out file parameter must be entered as well.
88 • Monitoring
EOF
101 5506688 23Jun2010 13:05 110,110 aaaa
LAST MODIFIED OWNER RWEP PExt SExt
4 16
HP NonStop SSL Reference Manual