Just a week or two ago someone else posted the same question. To
eliminate the lookup ambiguity of the NULL device, either name or rename other
OS NULL devices to something different from NULL, like NT NULL, _or_ remove the
mnemonic NULL from these other OS NULL devices. You want to have exactly
one device that satisfies the lookup value NULL. For Linux that is the one
that has $I equal to /dev/null.
----- Original Message -----
Sent: Friday, June 17, 2005 10:46
AM
Subject: [Hardhats-members] Re: CPRS
logon error
I'm on a local network and there is
no firewall
Steps of installation found in worldvista site
OS of the
vista server: Red Hat 9
Version of CPRS: 1.0.25.28
GTM>D STRT^XWBTCP(9200)
Start
TCP Listener...
Checking if TCP Listener has started...
TCP Listener
started successfully.
GTM>W $Zv
GT.M V5.0-FT02
Linux x86
GTM>D
^XPAREDIT
--- Edit Parameter Values ---
Select PARAMETER DEFINITION NAME:
XWBDEBUG RPCBroker debug
logging
----------------- Setting XWBDEBUG for System:
JIHAD.HCZ.MA -----------------
Enable Broker Logging: Yes// very
verbose very
Verbose
-------------------------------------------------------------------------------
--------------
When I try to
connect the log gives:
GTM> D VIEW^XWBLOG
Log from
Job 3148 5 Lines
14:17:33 = Log start: Jun 17, [EMAIL PROTECTED]:17:33
14:17:33 =
XWBTCPL
14:17:38 = Port Open: 9200
14:24:26 = Hdr:{XWB}00058|
Msg:TCPconnect^192.168.1.69^2338^facture11.hcz.ma^
14:24:26 =
accept
Return to continue, Next log, Exit: Continue//
and:
Log from Job 3176 3
Lines
14:24:26 = Log start: Jun 17, [EMAIL PROTECTED]:24:26
14:24:26 =
XWBTCPC
14:24:26 = Callback: 192.168.1.69 :2338
Return to continue, Next
log, Exit: Continue//
and finally, my NULL device
parameters:
Select DEVICE NAME:
NULL
1
NULL NT SYSTEM
//./nul
2 NULL
GTM-UNIX-NULL Bit Bucket (GT.M-Unix)
/dev/null ROU
3 NULL-DSM Bit
Bucket _NLA0:
CHOOSE 1-3: 2
GTM-UNIX-NULL Bit Bucket (GT.M-Unix)
/dev/null ROU
NAME: GTM-UNIX-NULL//
LOCATION OF
TERMINAL: Bit Bucket (GT.M-Unix) Replace
Select MNEMONIC:
NULL//
LOCAL SYNONYM:
$I: /dev/null//
VOLUME SET(CPU):
ROU//
SIGN-ON/SYSTEM DEVICE: NO//
TYPE: TERMINAL// ^
________________________________________________
Nancy:
Also, please try setting the log
parameter to very verbose which is 3 on a
scale of 0-3 and see what you get
then. Also, please remind us what you have
install and on what system
- a recent FOIA on Cache and Windows or some other
version on GTM and Linux
or what? And are you on a local network or remote
and are you using
the new listener or not? How are you starting the
listener?
What version of CPRS are you using?
Select OPTION NAME:
^
GTM>D
^XPAREDIT
--- Edit Parameter Values ---
Select PARAMETER DEFINITION NAME:
XWBDEBUG RPCBroker debug logging
-----------
Setting XWBDEBUG for System: CMM.FO-ALBANY.MED.VA.GOV
-----------
Enable Broker Logging: very verbose// ??
This parameter
controls if the RPC Broker records log data
in
^TMP("XWBDBUG",$J).
Enable Broker Logging: very verbose// 3 very
verbose
On Thursday 16 June 2005 03:00 pm, Kevin Toppenberg
wrote:
> "Vista"-- what is your real name? yassir?
>
> Can
you log in from a terminal (i.e. do you have your
> login and passwords
correct?) try do ^ZU to test
> this.
>
> Any firewalls
in place on the server or the desktop
> PC?
>
>
Kevin
>
> --- vista <[EMAIL PROTECTED]> wrote:
> >
Hi,
> >
> > I can't logon with CPRS into the RPC broker
server,
> > when I try to view broker log with D VIEW^XWBDLOG
i
> > have the following error:
> >
> > Log from
Job 3314 3 Lines
> > 11:58:01 = Log start: Jun 16,
[EMAIL PROTECTED]:58:01
> > 11:58:01 = XWBTCPC
> > 11:58:01 =
Callback: 192.168.1.69 :1333
> > Return to continue, Next log, Exit:
Continue//
> >
> > where 192.168.1.69 is the client
IP,
> > (Please help, I've installed and configured the
> >
vista server 3 weeks ago and til now I can't connect
> > CPRS to
it)
> >
> > yassir
