Re: how does one code the .INI for a Comet Anywhere remote station


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Bob A on August 31, 2012 at 13:18:14:

In Reply to: Re: how does one code the .INI for a Comet Anywhere remote station posted by Grant Foraker on August 31, 2012 at 12:12:55:

Grant:

thanx for the speedy response!

I want to make sure that I understand this....

I have a .INI with much the same information as this for the definition of the CometAnywhere NODE on the COMET server (although I have one more line with a type "7" record defining the CA Host) On my system, this is defined just like any other node, with the exception of the fact that the CA Node has types 3, 5, and 7 records. Up until now, I've only looked at the .INI on the COMET server, and, since there was some software downloaded remotely that was tailored for being a CA workstation, I never even thought about ever needing a .INI/SYSGEN for the remote stations.

As I'm now downloading a full COMET installation on each of the remote workstations.... I'll need to put together a .INI for each remote terminal.... so that I can do a SYSGEN and get COMET to come up and access the central Server.

I was thinking that I'd have to code something a lot more like the "Minimum .INI file" from the wiki:

[DIRECTORIES]
01 = C,C:\comet\REL\;
[NODE]
Name = MIN;
[COMET SYSTEM OPTIONS]
First Partition = P00;
# of Partitions = 1;

[CONSOLE SESSION OPTIONS]
Session = T00, P00, 5, F0,80,FF,F0,B0;
[END]

where the [NODE] name would be the same on all systems, and each [NODE] would have the same [CONSOLE SESSION OPTIONS] (probably 3 or 4) since I don't think I worry if some actually have more than others since I typically see that we're running with 25 out of 25 CA sessions taken up at any given time.

so, I only have to define the C:\COMET\REL directory, and define:

[COMET SYSTEM OPTIONS]
First Partition = P00;
# of Partitions = 4;
and all 25 sessions under the [CONSOLE SESSION OPTIONS]
and my single [PRINTERS]:
Printer = LP1,W,N,,#,,;

what I don't get is how to number the [CONSOLE SESSION OPTIONS]..... for the local connects, I have a range of Partitions and Sessions for each user. As an example, my personal node, which is locally connected, is defined as:
[COMET SYSTEM OPTIONS]
First Partition = P17;
# of Partitions = 4;
First Terminal = T17;
# of Terminals = 4;

[CONSOLE SESSION OPTIONS]
Session = T17,P17,5 ,F0,80,FF,F0,B0;
Session = T18,P18,5 ,F0,80,FF,F0,40;
Session = T19,P19,5 ,F0,80,FF,F0,20;
Session = T20,P20,5 ,F0,80,FF,F0,30;

this makes perfect sense... I have specific sessions and partitions.

But, I thought that the central idea of CometAnywhere is to specify a total number of partitions and sessions on the COMET Host, but they would actually be retrieved remotely from a pool of (in my case 25) available sessions, as needed. so this is achieved by putting a range of Partitions and Sessions and they are grabbed up as needed:

[COMET SYSTEM OPTIONS]
First Partition = 900;
# of Partitions = 031;
First Terminal = 900;
# of Terminals = 015;

but this seems to be how I'd define it on the COMET host.... I'm trying to figure out the numbering scheme on the remote CometAnywhere systems....


Thanx

Bob "A"


Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?  

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):





Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]