Port number

110 views
Skip to first unread message

PaulJ

unread,
Jan 5, 2009, 2:00:07 PM1/5/09
to jBASE
Hi,

Some simple questions about "port number", maybe there are simple
answers?!

We're using jBase 4.1.19. At this level, can anyone explain how the
jBase port number is allocated? I think there used to be a jPML
command which helped determine this allocation, but that this is now
superseded? Does the jBase term "port number" have anything at all to
do with the AIX view of a "port number" e.g. port 80 as default port
for http listening? Is the jBase "port number" really just an
identifier for a particular jBase session?

Regards,

Paul
Message has been deleted
Message has been deleted

pat

unread,
Jan 6, 2009, 12:01:45 AM1/6/09
to jBASE
Correct. The jBASE port number is simply an identifier to identify a
particular jBASE session

As a VERY simple summary, on jBASE 4.1 and above the 'next free port
number is allocated to your session'
The 'free ( and used ) port allocations' are maintained under the
'proc' directory ( under the 'JBCRELEASEDIR' directory )
[ So DON'T amend the contents of this directory ( as if anyone would,
would they ? ;-) ) whilst any jBASE processes are currently running ]

The jBASE port number does NOT have any 'connection' to a Unix /
Windows port number / socket

[ The jBASE port number does have similarities to the Unix 'tty device
number' eg /dev/pts/7 ]

Pat.

Senthil Kumaran

unread,
Jan 5, 2009, 11:57:49 PM1/5/09
to jB...@googlegroups.com
USE
 
JBC_PORTNO to assign the potr number..
 
This port number is session specific

PaulJ

unread,
Jan 6, 2009, 6:46:28 AM1/6/09
to jBASE
Pat,

Thanks for the swift response. Interesting. I was aware that the
device number visible thru jBase does indeed correspond to the AIX
view of a device (the number you see is the same as the reference in
the /dev/pts directory), but was not sure whether port was AIX visible
or not.

It is indeed much clearer to regard it as a "session identifier", and
pointing me at the jbase proc directory was helpful in understanding
how this all fits together.

Cheers,

Paul

PaulJ

unread,
Jan 6, 2009, 1:45:33 PM1/6/09
to jBASE
Senthil,

The internal port allocation is not reliant on JBCPORTNO - it can't be
because in our environment and lots of others (looking at posts on
this forum) the value is "Not Set". I think JBCPORTNO can
(optionally) be used to override the normal allocation and direct what
port number (or range of numbers) is used by particular users.
Although why anyone would want to do this I really have no idea.

Regards,

Paul
Reply all
Reply to author
Forward
0 new messages