RelNotes 2.21

=====================================================================

== EloCap - 2.21 ==

=====================================================================

Release Notes - EloCap 2.21

06/23/2009

Summary of changes in 2.21:

. Fixed problem with -dset matching. Bug in code prevented -dset

matching from always working correctly.

=====================================================================

== EloCap - 2.20 ==

=====================================================================

Release Notes - EloCap 2.20

09/17/2008

Summary of changes in 2.20:

. Fixed progam abort when using ASCII capture files. Issue was

introduced in version 2.00.

=====================================================================

== EloCap - 2.10 ==

=====================================================================

Release Notes - EloCap 2.10

09/09/2008

Summary of changes in 2.10:

. Added SESSION as an additional field that may be specified with

the -info option. If the option "-info SESSION" is specified

for a capture file, the Eloquence audit information is written

to the 8 character SESSION capture file field. SESSION is only

available when -exthdr is specified and begins at position

87 by default, or position 89 if -yyyy is also specified.

. Added the -progterm <string> option to cause the command line

returned by Eloquence FWUtil to be searched for a program

name termination string. If <string> is found in the command

line, the characters preceding <string> are written to the

capture file PROG header field. The program name is delimited

by a space with a maximum of 24 characters written to the

field. If <string> is not found, then the program

name without the directory is written to PROG, with a maximum

of 24 characters. For example, if EloCap is run with

"-progterm .acu" and the the command line is:

runcbl_AMXW805 -c //TAHP/PROG/MECO0020.acu -x -b -y

then "//TAHP/PROG/MECO0020" is written to the capture file PROG

field because it is bounded by a space and ".acu".

=====================================================================

== EloCap - 2.00 ==

=====================================================================

Release Notes - EloCap 2.00

08/12/2008

Summary of changes in 2.00:

. Added end of file checking when writing to a message file. When

a message file reaches the 2-gigabyte limit, EloCap issues an

error and stops processing unless -rollover is specified on

the command line.

. Added the -rollover option to roll over to another file when a

message capture file is full. The -rollover option causes the

current capture file to be closed and a new one started when the

2-gigabyte file limit is reached. The name of the next file

is 1 greater than the current file if current file name ends in

a number. If the current file name does not end in a number,

then "1" is appended to the current file name. If the next

file in sequence already exists, it is not used and the next file

name is used until an available name is found. File name

extensions such as ".log" are ignored when calculating the next

file name. Here are some examples:

Capture file name Next Capture file name

capture capture1

capture1 capture2

capture9 capture10

capture09 capture10

capture.msg capture1.msg

capture99.msg capture100.msg

cap1 cap4 (if cap2 and cap3 already exist)

Note: -rollover does no apply to ASCII capture files.

=====================================================================

== EloCap - 1.90 ==

=====================================================================

Release Notes - EloCap 1.90

07/16/2008

Summary of changes in 1.90:

. Added the -info option to allow information from the Eloquence

environment variable EQ_AUDIT_INFO to be put into the capture file

header. When Eloquence writes a forward log record, the value of

the environment variable EQ_AUDIT_INFO is also written to the log

file. The -info option is used to write this value to one of the

header fields in the capture file.

The syntax of the -info option is:

-info <header field> where <header field> indicates into which

capture file header field to write the info and must be

either DBNAME, DBUSER or PROG. Each of these fields is

24 bytes long so the maximum length of the information

written to the capture file header is 24 bytes. The

offsets into the capture file depend on whether or not

-yyyy is also specified. The offsets are:

No -yyyy -yyyy

Field Size Offset Offset

DBNAME 24 7 7

PROG 24 63 65

DBUSER 24 95 97

=====================================================================

== EloCap - 1.80 ==

=====================================================================

Release Notes - EloCap 1.80

06/19/2008

Summary of changes in 1.80:

. On HP-UX, EloCap now uses the 64-bit file system for ASCII capture

files so that more and 2 gigabytes may be written to a capture file.

This is enabled by calling fopen64() instead of fopen().

=====================================================================

== EloCap - 1.70 ==

=====================================================================

Release Notes - EloCap 1.70

06/12/2008

Summary of changes in 1.70:

. Fixed a data corruption issue when binary data was written to

a message file.

. Added the -dumprecs option to dump raw records in hex as they are

read from the Eloquence log files and written to the capture files.

=====================================================================

== EloCap - 1.60 ==

=====================================================================

Release Notes - EloCap 1.60

02/27/2008

Summary of changes in 1.60:

. Added the -bwfmt option to convert I, J, and K with leading spaces

and zeroes. Also converts P and Z items with leading spaces

stripped.

See the ReadMe file (ReadMe.EloCap) section on ASCII Capture Files for

details of the ASCII file and -bwfmt implementation.

=====================================================================

== EloCap - 1.50 ==

=====================================================================

Release Notes - EloCap 1.50

02/06/2008

Summary of changes in 1.50:

. Fixed the exit status of EloCap. In previous releases EloCap always

exited with at status of 1. EloCap has been fixed to exit with

a status of 0 if there were no errors and 1 if there were any

errors.

=====================================================================

== EloCap - 1.40 ==

=====================================================================

Release Notes - EloCap 1.40

07/03/2007

Summary of changes in 1.40:

. Fixed a problem using -recnum. In previous releases, the -recnum

option did not work as documented.

=====================================================================

== EloCap - 1.30 ==

=====================================================================

Release Notes - EloCap 1.30

05/16/2007

Summary of changes in 1.30:

. Option -ascii added to write text capture files. The -ascii option

causes all numeric data to be converted to ASCII characters and

non-printing characters in text fields to be converted to '~'.

Using -ascii causes the capture file to be a text file rather

than a message file.

. The -asciirev option may be used instead of -ascii to reverse the

byte order of binary integers and floating point numbers. (The

need of this option is rare and unlikely.)

. Added the -dirty option to prevent the substitution of non-printing

data with '~' and leaves binary data in the output.

Note: Use of -dirty is not recommended and may create an unusable

capture file.

See the ReadMe file (ReadMe.EloCap) section on ASCII Capture Files for

details of ASCII file implementation.

=====================================================================

== EloCap - 1.20 ==

=====================================================================

Release Notes - EloCap 1.20

04/10/2007

Summary of changes in 1.20:

. Option -showskip added to show statistics for records not written

to any capture file.

. Extended header enhanced to contain user and program information

made available by fwutil version B.07.10.05.

NOTE: fwutil version B.07.10.05 must be installed correctly on

the system to use EloCap 1.20.

Details of changes in 1.20:

. Using -showskip shows statistics for records log records NOT

written to any capture file. The display is similar to the

display for the -capstats option.

. The new fwutil B.07.10.05 made more information available from

the Eloquence log files. This permits EloCap to return the

information in the extended header. The DataBridger extended

header information is layed out as follows:

Extended Header:

Field Size Offset Size Offset

PROG 24 63 24 65

SESSION 8 87 8 89

USER 8 95 8 97

GROUP 8 103 8 105

ACCOUNT 8 111 8 113

JS 1 119 1 121

JSNUM 5 120 5 122

The EloCap extended header information is now as follows:

PROG: Contains the first 24 characters of the program

name with the program directory and options

removed.

SESSION: Contains the first 8 characters of the operating

system user name.

USER Contains characters 1 through 8 of the database

user name.

GROUP Contains characters 9 through 16 of the database

user name.

ACCOUNT Contains characters 16 through 24 of the database

user name.

JS: Unused. Contains a space.

JSNUM: Contains the zero-filled, right justified first

five digits of the PID of the program accessing the

database.

Example:

User : hpuser

Command line : /usr/local/bin/myprog -opt1 -opt2

Database login: DBUSER

PID : 1284

+---+---+---+---+---+---+---+---+

Offset 63: | m | y | p | r | o | g | | | PROG(1)

+---+---+---+---+---+---+---+---+

+---+---+---+---+---+---+---+---+

+---+---+---+---+---+---+---+---+

Offset 87: | h | p | u | s | e | r | | | SESSION

+---+---+---+---+---+---+---+---+

Offset 95: | D | B | U | S | E | R | | | USER

+---+---+---+---+---+---+---+---+

+---+---+---+---+---+---+---+---+

+---+---+---+---+---+---+---+---+

Offset 119: | | 0 | 1 | 2 | 8 | 4 | JS/JSNUM

+---+---+---+---+---+---+

=====================================================================

== EloCap - 1.10 ==

=====================================================================

Release Notes - EloCap 1.10

03/05/2007

Summary of changes in 1.10:

. Database separator changed to ":" from "." in -dset option.

. Option -fga added to put parsed database name in capture file.

. Option -capstats added to show statistics for each capture file.

Details of changes in 1.10:

. A change was made to the -dset parameter to use a colon (:) to

separate the database name from the from the dataset name. The

previous delimiter was a period (.), but this needed to be changed

to support a period in the database name. If either the database

name or the dataset name is left off of the -dset parameter, a

default value of "@" is assumed. See examples below:

-dset parameter specified is interpreted as

---------------------------- ----------------------------

-dset cust -dset @:CUST

Capture the CUST dataset

from all databases.

-dset :cust -dset @:CUST

Capture the CUST dataset

from all databases.

-dset cust: -dset CUST:@

Capture all datasets from

from CUST database.

-dset cust@ -dset @:CUST@

Capture all datasets with a

name beginning with CUST

from all databases.

-dset cust@: -dset CUST@:@

Capture all datasets from

from all databases that have

a name beginning with CUST.

-dset cust@:cust@ -dset CUST@:CUST@

Capture all datasets with a

name beginning with CUST

from all databases that have

a name beginning with CUST.

. The internal maximum database name length has been increased to 256,

but only the first 24 characters of the datbase name are ever written

to the capture file.

. A new capture file option -fga has been added to separate the

database name into file.group.account syntax before adding the record

to the capture file. Without -fga, the first 24 characters of the

database name (with periods, if any) are written to the capture file.

With -fga, the database name is separated into 8 character blocks

delimited by periods. The interpretation of -dset is not affected

by the -fga option. Here are some examples:

Example 1: -fga NOT specified. FILE, GROUP and ACCOUNT indicate

the of fields within the capture file.

Database Capture file

Name FILE GROUP ACCOUNT

CUST CUST

CUST.DATABASE.CSTSYS CUST.DAT ABASE.CS TSYS

CUSTOMER-DATABASE CUSTOMER -DATABAS E

CUST.DB CUST.DB

Example 2: -fga IS specified. FILE, GROUP and ACCOUNT indicate

the of fields within the capture file.

Database Capture file

Name FILE GROUP ACCOUNT

CUST CUST

CUST.DATABASE.CSTSYS CUST DATABASE CSTSYS

CUSTOMER-DATABASE CUSTOMER -DATABAS E

CUST.DB CUST DB