RE: Forklift upgrade effect on communications?

[CWilt@xxxxxxxxxxxx]

Rob,

Thanks for the reply.  Actually, the hardware vendor (MAPSYS) is going to do
the actual move.  But I have done this myself in the past by, as you
suggest, following the Backup/restore procedures very carefully during a
move from a model 400 to a 270.

But as I said, at this new company.  They do a lot more dial up than I'm
used to.

So what I'm looking for is enough info to give myself that good-feeling that
things aren't going to be problems ;-)

Just waiting to see if anything blows up is not really an option for us.

Charles


> -----Original Message-----
> From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
> Sent: Thursday, December 18, 2003 11:22 AM
> To: Midrange Systems Technical Discussion
> Subject: Re: Forklift upgrade effect on communications?
> 
> 
> First and foremost the backup and recovery guide actually has 
> a checklist 
> for doing exactly what you want to do.  I don't mean the 
> checklist for a 
> complete restore.  I mean the one for moving to a new system. 
>  Follow it 
> very carefully.
> 
> In theory you should be able to complete the restore, do a 
> WRKHDWRSC *CMN 
> and a WRKLIND and match up the new resource names.  However, 
> if you are 
> using some sort of EDI package that regen's the line on a 
> regular basis 
> you might have to step through their menu's and change the 
> resource names 
> there also.
> 
> As far as bi-sync and SNA go, I wouldn't waste your time 
> trying to learn 
> them.  They're good for what they do, but the world is moving 
> on.  You 
> should be able to support the existing by limping along.  If 
> time were 
> unlimited, I would say, sure learn it.  However your time 
> would be better 
> served by learning something else.  Your company would 
> probably be better 
> served by just calling your EDI software vendor, or IBM on 
> your support 
> contract, if some existing process blows up.
> 
> Now I expect the SNA fans to come screaming.  And if you 
> still insist on 
> learning, then perhaps they can be of assistance.
> 
> Rob Berendt
> -- 
> "All creatures will make merry... under pain of death."
> -Ming the Merciless (Flash Gordon)
> 
> 
> 
> 
> CWilt@xxxxxxxxxxxx 
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 12/18/2003 10:48 AM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> 
> 
> To
> midrange-l@xxxxxxxxxxxx
> cc
> 
> Fax to
> 
> Subject
> Forklift upgrade effect on communications?
> 
> 
> 
> 
> 
> 
> All,
> 
> We're getting ready to replace our current 830 with a new 810.
> 
> Planning on a save/restore to new system.  We'll be keeping 
> the system 
> name
> the same but of course will have a new serial number.  We do a 
> considerable
> amount of dial-up comms using bi-sync and SNA protocols.  Is there 
> anything
> to be concerned about as far as communions, system directory, and/or
> anything else?
> 
> As an aside, I'm new here and one thing I'm lacking is experience with
> bi-sync and SNA comms.  My last position was new to the 400 
> so we were 
> using
> TCP/IP for just about everything.  Can anybody recommend 
> books, links, ect
> to help get me up to speed?
> 
> Thanks,
> Charles Wilt
> _______________________________________________
> 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.
> 
> 
> _______________________________________________
> 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.
>