RE: Data Transfer

It wasn't hard as you spell the exact same way I do :-) :-)

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Friday, September 06, 2013 12:48 PM
To: Midrange Systems Technical Discussion
Subject: Re: Data Transfer

And a good thing you can get past all the typos in that note. Geesh I have to be more careful, especially with the language professors on the
list watching..... ;-)

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 9/6/2013 11:33 AM, Don Wereschuk wrote:

It's not that I missed it (not entirely), it's just that I assumed that both boxes were on the same APPN network (and I do know what ASSUME does - I've learned that lesson many times :-) ). I now have to look into the configurations that you have so conveniently laid out for me. Thank you (and Larry Bolhuis) for the info.


******************************************
Don Wereschuk
ISD - Programmer/Analyst
Simcoe Parts Service Inc.
Phone: 705-435-7814 Ex: 302
Fax: 705-435-5029
mailto:dwereschuk@xxxxxxxxxxxxxxx
******************************************
If I'd have done what I said I should have done, then I'd be sitting
here saying I should have done what I did do.





-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Friday, September 06, 2013 9:23 AM
To: Midrange Systems Technical Discussion
Subject: Re: Data Transfer

Ah, you may have missed the restriction number 4 in the documentation, "Both systems intended to participate int he save and restore operation must be connected to the same APPN network"

That requires the network attributes to be set correctly (my even require an IPL) and come communication lines and devices. Even I can set it up so it does not take genius to do, but must be done correctly. So:

Network attributes:
System name: mysystem
Local Location name: mysystem
Default Local Location: mysystem
Nodetype: *NETNODE
Allow Any net: *NO
Allow APPN Virtual Support: *YES
Allow HPR Transport *YES
Virtual Controllers Auto Create: 100 ( I usually use 100, set to taste )
I set the country ID as well: US

These are the target controllers
Controllers:
CRTCTLAPPC CTLD(ENTERPRISE)
LINKTYPE(*VRTAPPN)
AUTODLTDEV(10000)
TEXT('Enterprise Extender Controller')
CRTDEVAPPC DEVD(mysystem)
RMTLOCNAME(mysystem)
CTL(ENTERPRISE)
TEXT('Device for HPRIP to mysystem')
CRTCTLAPPC CTLD(V7R1PROD) LINKTYPE(*HPRIP)
RMTINTNETA('###.###.###.###')
LCLINTNETA(###.###.###.###) RMTNETID(APPN)
RMTCPNAME(mysystem) CPSSN(*YES)
NODETYPE(*NETNODE) BEXROLE(*NETNODE)
TMSGRPNBR(1) TEXT('Connection to mysystem')

You need the controllers on both sides of the transaction.

That's enough to get you started. BTW if this looks a bit familiar to Larry Bolhuis, he wrote it, I just plagiarized it.




Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 9/6/2013 8:01 AM, Don Wereschuk wrote:

It appears that the SAVRSTOBJ is the best solution.(Thanks to all who suggested this) I tried to run a test and got an error on the transfer :

SAVRSTOBJ OBJ(A*) LIB(MYLIB) RMTLOCNAME(MYLOCNAME) OBJTYPE(*FILE) SAVACT(*LIB)
ACCPTH(*YES) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(SPSL)

Route to specified location not found.

An error occurred during the SAVRSTOBJ operation.

We changed the location name using CHGNETA to be MYLOCNAME but this didn't seem to help. Does anyone know if I have to IPL for this to take effect or is there something else I have to do here?

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