fname lname ([EMAIL PROTECTED]):

> 1) [5.03/docs/compout.html 2nd section, 2nd paragraph] This
> paragraph states that the 2nd field of the CRO contains information
> regarding the remaining columns. From the CRO reports I have
> generated, I've noticed that there are more fields than defined by
> the characters w/in the second field.

> For example, in the line "D|RP|330|192|2001|08|20" RP says we can
> expext 'number of requests' and 'percentage of bytes' (two fields)
> though we have two fields then a date occupying 3 fields. In the
> line "r|lRbD|1|1527|0.00|2001|09|15|00|02|/images/c.gif", we have
> level, number of requests, percentage of bytes, date, but  the final
> field, directory, is not mentioned.

All reports also include the final field that is the data item for
each row in the report. In the Request Report, you have to have the
each requested item, no? And in the Daily Report the date that the
requests are totalled for?

> Is there somewhere w/in the documentation that defines the format of
> each of the different reports? I was able to determine the sytax of
> 21 of the 44 CRO reports by examining my sample data, but was not
> able to determine the remaining 23.

I'm pretty sure they all follow the same format. Each row defines the
columns for the row and adds one of more fields for the data item in
that row. Columns can take up more than one field when they are of a
date/time type. Date/time columns (or data) will never be more than 5
fields and always uses only as many as needed to define the data.

The only tricky ones are some of the new time reports which have
interesting syntax to uniquely define the date.


> My goal was to create a custom lookup table, mapping report type to
> complete field format, but in the process of working through this,
> it seems as though makeing my own assertions about what each line of
> data will look like seems to reinvent the purpose of this second
> field, so I assume I am not thinking of this correctly, or missing
> something, and making things more difficult.

> Any thoughts?

The second field will change depending on what values the user has
defined on *COLS commands in their Analog config. So you can't
predeclare them in a lookup table. You have to parse the CRO, which is
why the field is provided. (I don't think there is any extra
information in CRO, except maybe the '*' predecate on rows that define
non-column data, like FLOORs and LR, but that's to make future
expansion easier.)


> 2) In Browser Summary CRO report, what does the hierarchy level (l)
> signify? I understand how it relates to directories, but not clear
> on its significance here.

Browsers look like this:

Netscape
        4.x
           4.0
           4.1
        6.x
           6.0
           6.1
MSIE
        4.x
           4.0
        5.x
           5.0
           5.01
           5.5
        6.x
           6.0
           
So there's a level, just like directories to indicate the hierarchy.
See the SUBBROW command in Analog's documentation for a better
understanding of how this works.


> 3) In the same report, Browser Summary CRO, 'N' stands for 'number
> of item in the list' -- what does this signify? what does it mean if
> it is null (empty)? I don't have enough data available in my report
> output to deduce its meaning.

Normally only the first level in the hierarchy ('Netscape', 'MSIE')
are numbered. If you are going to number each row, then you should
number only the rows that are listed with a number if the 'N' column
exists. If not, number then as you choose.


BTW, you might want to look at Report Magic
(http://www.reportmagic.org/) to see how CRO is put into use. The
source is open, so you might be able to glean more understanding of
the format from there too.

Also, if you want I can send you a CRO file that contains almost every
possible field, data, or item that Analog could put in there.

-- 

Jeremy Wadsack
Wadsack-Allen Digital Group

+------------------------------------------------------------------------
|  This is the analog-help mailing list. To unsubscribe from this
|  mailing list, go to
|    http://lists.isite.net/listgate/analog-help/unsubscribe.html
|
|  List archives are available at
|    http://www.mail-archive.com/[email protected]/
|    http://lists.isite.net/listgate/analog-help/archives/
|    http://www.tallylist.com/archives/index.cfm/mlist.7
+------------------------------------------------------------------------

Reply via email to