T.R | Title | User | Personal Name | Date | Lines |
---|
344.1 | Problem searching for topic | GIDDAY::SETHI | Man from Downunder | Fri Mar 27 1992 01:33 | 15 |
| G'day Terry,
Just a minor point is it possible to give the topic a title that other
people can search on. Forexample it contians FCS, trace file etc.
The reason why I am asking you and all concerned is to make it easier
for others to search for a particular topic that maybe of some use to
them. As an example when I am searching a conference I do a search
notes$library:ALL-IN-1 FCS to find a topic(s) concerned with FCS. By
doing this you make life easier for all of us. I hope that you can see
why I had to make this entry.
I hope that you get an answer thanks :-)
Sunil
|
344.2 | 1 changed 998 to go! | AIMTEC::WICKS_A | Vote Bill'n'Opus for a weirder USA | Fri Mar 27 1992 03:11 | 10 |
| Sunil,
Good Idea.
Your wish is my command. I guess I should also go back and change the
title of all Terry's other notes (:==:) but it's gone 10pm already.
Regards,
Andrew.D.Wicks
|
344.3 | My daily Terry question :-) | CHRLIE::HUSTON | | Fri Mar 27 1992 13:30 | 50 |
|
Hi Terry,
these are pretty easy, but only because I happen to be the one who
wrote the trace stuff :-)
>Each session has an ID number that is a long numeric string in the trace file.
>How are these session numbers generated. Are they unique for ever or do you
>potentially get repeats if a server is stopped and started or another server
>is used.
The session ID is the address of the session block that is created by
the server when you call OafcOpenCabinetW. Therefore, it is unique as
long as you have the session open. In reality, the probability of it
being re-used is fairly slim, but can't be guarenteed to be unique
once you end your session.
>Each task in the session also has an ID number. How are these generated? My
>testing had a session where the tasks were numbered from 11 using odd numbers
>only. Is this because there were other tasks that did not produce trace
>output or does the algorithm prefer odd numbers? :-)
The task ID starts at 11 and each task ID is guarenteed to be unique
within its session. All sessions have there first task as 11.
Why you saw only odd numbers? Who knows, I believe they should be
bumped by one for every task, you should get a trace record for every
task the server does if tracing is enabled. It is no real problem that
they went up by 2 as long as they are unique, I will check into it
just to double check though.
>There is a field labled File Cabinet Name (in the formatted report) that seems
>to be the node name and ALL-IN-1 username. Is this correct and if so is that
>really a file cabinet name? Does the value of this field change with
>distribution level 1?
That is the filecabinet name that the user connected to. It is made up
of the node name the server is running on and the ALL-IN-1 username
of the person requesting the connection. That is how we know which
server and A1 usernaem to use.
This field currently will never change. In the past we supported
DNS filecabinets in which the filecabinet name was an object in the
DNS namespace. Who knows what will happen when the future becomes
reality. So I guess the answer for now is that it will always look like
that.
--Bob
|
344.4 | OK I'll try harder | AIMTEC::PORTER_T | Terry Porter, ALL-IN-1 Support, Atlanta CSC | Fri Mar 27 1992 15:55 | 13 |
| Re .1
Good point, I'll try to put in better note titles in the future (I'm sure there
will be lots more questions :-)
Re. .3
Thanks again Bob.
So there is no guarentee that two different session in a single trace will not
have the same ID, but the chances of that happening are fairly slim.
Terry
|