RE: Object Connect -- MIDRANGE-L

Alexei,

And fully qualified names was the problem, the problem was so simple I over
looked it, I feel pretty stupid right now, but hea.....
....an issue no more !!

thanks
Neil

-----Original Message-----
From: Alexei Pytel [mailto:pytel@us.ibm.com]
Sent: 29 October 2001 17:09
To: midrange-l@midrange.com
Subject: Re: Object Connect



RMTLOCNAME parameter accepts fully qualified location names, as in
nnnnnnnn.cccccccc, where nnnnnnnn is the network
identifier (ID) and cccccccc is the remote location name.

Try to specify fully qualified location name for the target system.

    Alexei Pytel





                    "Carley, Neil"
                    <neil.carley@misys.       To:
"'MIDRANGE-L@midrange.com'"
                    com>                       <MIDRANGE-L@midrange.com>
                    Sent by:                  cc:
                    midrange-l-admin@mi       Subject:     Object Connect
                    drange.com


                    10/26/2001 06:35 AM
                    Please respond to
                    midrange-l





Hi group,

Perhaps someone could offer some advice on the following please ?
Both machines V4R5 and latest PTF's
I have a no of as/400's here on site and I have set up object connect
between them with no trouble, however I can't seem to get it working to
another one of our as/400's at a remote site, we are connected via our WAN
and all other comms (sndnetf and pass through etc.) are working fine. One
thing I suspect is that all our box's on this site are network id APPN and
the remote box has it's netid set as GBIBM100, if you strpasthr form here
to
there obviously you have to specify the network id on the command, however
there doesn't seem to be this option on the SAVRSTXXX commands and I think
this may be why its failing ????
I'll copy the joblog below
has anyone had a similar experience or have any suggestions ?

thanks
Neil

JOBLOG:

SAVRSTLIB LIB(ITSTEMP) RMTLOCNAME(KAPSH)
Ownership of object TXIDQ in QTEMP type *USRQ changed.
Ownership of object RESPQ in QTEMP type *USRQ changed.
Route to specified location not found. - CPF8933 for reference

Function check. CPF8933 unmonitored by QSVRCS at statement *N, instruction
  X'093D'.
Unable to establish connection from SLOUGH1 to KAPSH.
An error occurred during the SAVRSTLIB operation.
mailto:neil.carley@misys.com
http://www.misys.com/
This email message is intended for the named recipient only. It may be
privileged and/or confidential. If you are not the intended named recipient
of this email then you should not copy it or use it for any purpose, nor
disclose its contents to any other person. You should contact Misys
International Banking Systems as shown below so that we can take
appropriate
action at no cost to yourself.
Misys International Banking Systems Ltd,1 St George's Road, Wimbledon,
London, SW19 4DR, England. Email: ibs.postmaster@misys.com
mailto:ibs.postmaster@misys.com. Tel: +44 (0) 20 8879 1188 Fax: +44 (0) 20
8947 3373
Misys International Banking Systems Ltd is registered in England and Wales
under company no. 971479


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.