No. Scratch means a brand new V7R1 on an empty machine.
Initialized. New disk configuration.
The vendor Journal software is installed on both systems then
a restore of Nonsys is done with omits for several "Q" libraries
like QGPL, QUSRSYS, etc. (I think that's where it went wrong but
I don't know for sure since I wasn't there.) Then vendor software
on production machine is supposed to start rebuilding all the
libraries, etc. on the DR box. That started off and then it all
fell apart with TCP errors.







From: Gqcy <gmufasa01@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 12/12/2014 04:28 PM
Subject: Re: TCP Problem with DR system
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



so you didn't restore completely from backup,
you put on a V7R1 "scratch" (meaning a <different> QUSRSYS, QSYS that
was on the backup???), then restored what?




On 12/12/2014 4:06 PM, broehmer@xxxxxxxxxxxxxxx wrote:
It was a V7R1 "scratch" install on an 8202 E4A that included
C/A (Client Access) and before the package was installed
the system was functioning perfectly.
RSTAUT was the last step that was run.

Sorry to belabor this. I was just hoping someone had problems
involving TCP where a reinstall of all or part of it was done.

I just did 5770SS1 option 12 delete/add and reapplied PTF's and it still
doesn't work. No hostservers are showing. No communication except
for LAN console. I'm thinking I'll have to rebuild the system from
scratch this weekend...again! (3rd time).









From: Evan Harris<auctionitis@xxxxxxxxx>
To: Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>
Date: 12/12/2014 03:55 PM
Subject: Re: TCP Problem with DR system
Sent by: "MIDRANGE-L"<midrange-l-bounces@xxxxxxxxxxxx>



What does it was working before including C/A mean - what procedure was
run
to "include C/A" ?

Have you run a RSTAUT since then ? (WAG)

If TCP was working can you detail what you did since then to make it not
work ?

On Sat, Dec 13, 2014 at 10:48 AM,<broehmer@xxxxxxxxxxxxxxx> wrote:

Long story short is it is a well known journaling package
that required a scratch system and several procedures were
followed and that has led to what I think is an orphaned
system. The vendor can't get on the box because TCP
doesn't work and they don't understand what happened. It
was working before including C/A and now it's an island
no one can get to. Pinging shows access both in and out.

My thought was that I could find a way to get TCP back up
for further investigation by the vendor. I'm now considering
that the vendor does the install by cookbook and that whatever
went south probably isn't something they have a handle on.

So it looks like a long weekend and, by the way, the journal
transactions are building up on the production box.





From: Evan Harris<auctionitis@xxxxxxxxx>
To: Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>
Date: 12/12/2014 03:32 PM
Subject: Re: TCP Problem with DR system
Sent by: "MIDRANGE-L"<midrange-l-bounces@xxxxxxxxxxxx>



Ok, so what was the recovery procedure you followed ?


On Sat, Dec 13, 2014 at 10:21 AM,<broehmer@xxxxxxxxxxxxxxx> wrote:

If you try to start servers (STRTCPSVR) and prompt for server
application the list on the DR box is blank. No *BOOTP,
*CIMOM,*DHCP,etc.
It's like some file got corrupted or deleted and none of the servers
are
there anymore. My thought was to just restore TCP (5770TC1) but
I don't think that will help since that product is just the
connectivity
utilities not the actual TCP.






From: Evan Harris<auctionitis@xxxxxxxxx>
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
Date: 12/12/2014 03:14 PM
Subject: Re: TCP Problem with DR system
Sent by: "MIDRANGE-L"<midrange-l-bounces@xxxxxxxxxxxx>



Hi

I don't understand your question all that well; I'm not entirely sure
what
you mean by "hostservers don't show up".

What recovery procedure did you run to build the DR system ?
Did your startup program run OK ?
Have you started TCP ?
Have you started Subsystem QSERVER ?
Have you run the STRHOSTSVR command ?

Did you need to remap hardware resources to line description ?

I could ask more questions hoping to ask "the right question" that
will
reveal what is wrong, or you could provide more information about what
you
did and what you are seeing that is not correct.



On Sat, Dec 13, 2014 at 9:42 AM,<broehmer@xxxxxxxxxxxxxxx> wrote:

I have a question that maybe, if I'm lucky, can be answered by
someone
who
has
had this happen to them before I have to recreate the DR system from
scatch.
On a disaster recovery box TCP hostservers don't show up after
restoring
from the production box. The DR system was a complete working
system
before
the restore and now, while one can ping from the DR box to the
Production
box
no hostservers are shown and none can be started and client access
does
not work.
Given that something is terribly wrong with the restore, how can one
reinstall
TCP hostservers or is this even worth trying?



"CONFIDENTIALITY NOTICE: This e-mail transmission (and/or the
attachments
accompanying it) contain confidential information belonging to the
sender.
The information is intended only for the use of the intended
recipient.
If
you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution or the taking of any action in
reliance
on the contents of the information is strictly prohibited. Any
unauthorized interception of this transmission is illegal under the
law.
If you have received this transmission in error, please promptly
notify
the
sender by reply e-mail, and then destroy all copies of the
transmission."
--
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.



--

Regards
Evan Harris
--
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.




"CONFIDENTIALITY NOTICE: This e-mail transmission (and/or the
attachments
accompanying it) contain confidential information belonging to the
sender.
The information is intended only for the use of the intended
recipient.
If
you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution or the taking of any action in
reliance
on the contents of the information is strictly prohibited. Any
unauthorized interception of this transmission is illegal under the
law.
If you have received this transmission in error, please promptly
notify
the
sender by reply e-mail, and then destroy all copies of the
transmission."
--
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.



--

Regards
Evan Harris
--
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.




"CONFIDENTIALITY NOTICE: This e-mail transmission (and/or the
attachments
accompanying it) contain confidential information belonging to the
sender.
The information is intended only for the use of the intended recipient.
If
you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution or the taking of any action in
reliance
on the contents of the information is strictly prohibited. Any
unauthorized interception of this transmission is illegal under the
law.
If you have received this transmission in error, please promptly notify
the
sender by reply e-mail, and then destroy all copies of the
transmission."
--
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 thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].