Re: STRPASTHR question

I think you have it right...but I don't have time to verify it all right
now...

I don't think that the value of CPNAME matters, as long as the names match
(from controller on your end to controller on their end, and
vice-versa)...that's the key.

I also think you have the Directory & Distribution stuff right...


------ Original Message -----
From: <tomh@simas.com>
Newsgroups: gmane.comp.hardware.ibm.midrange
To: <midrange-l@midrange.com>
Sent: Thursday, August 29, 2002 11:03 AM
Subject: Re: STRPASTHR question


> >IIRC,
> >On the customer's system, change the local location name in the APPC
> device
> >description to be CUSTNAME instead of *NETATR...then reconfigure your end
> to
> >use CUSTNAME as the remote location name instead of S123456.
> >
> >Steve Landess
>
>
> Here's the command used to create the controller and device descriptions:
>
> (theirs)
> CRTCTLAPPC CTLD(SOLUTIONS) LINKTYPE(*SDLC) ONLINE(*NO) +
>              SWITCHED(*YES) SHM(*NO) APPN(*NO) +
>              MAXFRAME(521) RMTNETID(APPN) +
>              RMTCPNAME(S999999) EXCHID(&EXCHID) +
>              SWTLINLST(SOLUTIONS) INLCNN(*ANS)  +
>              CNNNBR(&NBR) ROLE(*NEG) STNADR(23) +
>              AUTOCRTDEV(*ALL) TEXT(&CTLDSC) +
>              CODE(*EBCDIC) PREDIALDLY(6) +
>              REDIALDLY(120) DIALRTY(2) SWTDSC(*YES) +
>              DSCTMR(30 30) POLLPTY(*NO) POLLLMT(0) +
>              OUTLMT(*POLLLMT) CNNPOLLRTY(7) +
>              NDMPOLLTMR(*CALC) CMNRCYLMT(2 5)
>
> CRTDEVAPPC DEVD(SOLUTIONS) RMTLOCNAME(S999999) ONLINE(*NO) +
>              LCLLOCNAME(*NETATR) RMTNETID(APPN) +
>              CTL(SOLUTIONS) MODE(*NETATR) +
>              MSGQ(*LIBL/QSYSOPR) APPN(*NO) SNGSSN(*NO) +
>              SECURELOC(*NO) TEXT('Solutions pass-thru') LOCADR(00)
>
>
> (ours)
> CRTCTLAPPC CTLD(CUSTNAME) LINKTYPE(*SDLC) ONLINE(*NO) +
>              SWITCHED(*YES) SHM(*NO) APPN(*NO) +
>              MAXFRAME(521) RMTNETID(APPN) +
>              RMTCPNAME(S123456) EXCHID(&EXCHID) +
>              INLCNN(*DIAL) DIALINIT(*IMMED) +
>              CNNNBR(&NBR) ROLE(*NEG) STNADR(23) +
>              AUTOCRTDEV(*ALL) TEXT(&CTLDSC) +
>              CODE(*EBCDIC) PREDIALDLY(6) +
>              REDIALDLY(120) DIALRTY(2) SWTDSC(*YES) +
>              DSCTMR(30 30) POLLPTY(*NO) POLLLMT(0) +
>              OUTLMT(*POLLLMT) CNNPOLLRTY(7) +
>              NDMPOLLTMR(*CALC) CMNRCYLMT(2 5)
>
> CRTDEVAPPC DEVD(CUSTNAME) RMTLOCNAME(S123456) ONLINE(*NO) +
>              LCLLOCNAME(*NETATR) RMTNETID(APPN) +
>              CTL(CUSTNAME) MODE(*NETATR) +
>              MSGQ(*LIBL/QSYSOPR) APPN(*NO) SNGSSN(*NO) +
>              SECURELOC(*NO) TEXT('Customer pass-thru') LOCADR(00)
>
>
>
> On their end, they need to change the LCLLOCNAME(*NETATR) to
> LCLLOCNAME(CUSTNAME), and the RMTLOCNAME(S999999) to RMTLOCNAME(SOLUTIONS)
> On our end, we need to change the LCLLOCNAME(*NETATR) to
> LCLLOCNAME(SOLUTIONS), and the RMTLOCNAME(S123456) to RMTLOCNAME(CUSTNAME)
>
> Correct?
>
>
> Do I need to make any changes to the RMTCPNAME parameters in the
> controller descriptions?
>
>
> Assuming that I make the LCLLOCNAME changes (above):
>
> Directory entries:
> Do I use the ADDDIRE USRID(*ANY CUSTNAME) SYSNAME(CUSTNAME) on our system?
> Do they use ADDDIRE USRID(*ANY SOLUTIONS) SYSNAME(SOLUTIONS) on their
> system?
>
>
> Distribution queue:
> Do I use ADDDSTQ DSTQ(CUSTNAME) RMTLOCNAME(CUSTNAME)
> LCLLOCNAME(SOLUTIONS)?
> Do they use ADDDSTQ DSTQ(SOLUTIONS) RMTLOCNAME(SOLUTIONS)
> LCLLOCNAME(CUSTNAME)?
>
>
> Distribution route:
> Do I use ADDDSTRTE SYSNAME(CUSTNAME) FAST(CUSTNAME) STATUS ....?
> Do they use ADDDSTRTE SYSNAME(SOLUTIONS) FAST(SOLUTIONS) STATUS .... ?
>
>
>
>
>
> _______________________________________________
> 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.
>