Joe,
Are you making the Commit onto a Day 0 AW70 ? The Day 0 would be an AW70 that
has been reloaded from scratch, writing over all old data on the hard drive.
Or are you doing a Commit software install onto a hard drive that already has a
Foxboro system installed on it?
If a Day 0 Commit - - then on the Commit diskette, all the stations hosted
by this AW70 and all the software packages to be loaded onto this AW70 must be
marked as "NOTYET" in IIF.pkg. After a successful installation, you perform
a reconcile and all the packages and stations that were successfully installed
get marked "DONE" and any future software install onto this hard disk in the
AW70 keep the "DONE" unless you modify a parameter of a successfully installed
item, then the IIF.pkg is marked "REINST" for that package. (Typical if you
add a new station to monitor to a System Monitor package or add a new screen
for System Monitor WP.)
A Commit software install was never designed to remove packages or stations or
nodes from a host hard drive. You have to do a whole lot of things manually on
the host(s) to get this done correctly and there is no real procedure to follow
to ensure you get it all done 100%. Some people have done this but it is not
simple nor easy. So that is why a Day 0 is onto a hard drive that has been
reloaded from scratch. When that happens, you lose all client data, so the
Service group at Foxboro developed a procedure to save all client stuff off the
drive(s) before the reload and then selectively copied good stuff back onto the
drive(s) after a successful Day 0 Commit and reboot. This again is a very
complicated procedure.
If you are not wiping out the hard drive on your AW70 - - - then at the
very least you need to go through the Reconcile process to get good data to
update the System Definition files. You should check the IIF.pkg file to
ensure it is marked correctly. If you plan to add a new CP then give it a new
name. Do not just delete a CP40B in System Definition and add a CP60 (for
example) with the same name as the CP40B. Give it a new name, then got to the
System Monitor and delete the CP40B name and add the CP60 name. But there are
many thing for which you cannot do this type of software install. You cannot
delete a multi-node configuration and make a single node configuration and you
cannot take a single node to multi-node.
The best thing to do is save your data (displays, scripts etc. anything that is
not default Foxboro). Ensure a good UPLOAD, CHECKPOINT for each station hosted
by this AW70 and perform a Day0 Commit for all hosts (hard drives) on your
system. There is a selection in System Definition - "Make Day0" or some
similar text so you run that on your definition before you start making
changes. If it is a true Day 0 (hard drive wiped out) then you can delete a
CP40B and add a CP60 with the same name or delete stations or delete nodes or
add nodes since there is zero data for the old configuration on the AW70's hard
drive.
Terry
From: Joe@xxxxxxxxxxxxx
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Windows NT AW70 V6.4 SysDef changes and commit
Date: Fri, 23 Sep 2016 16:31:54 -0700
Russ,
Sooooooooooooooo... I revisited the SysDef and I guess I missed a couple of
things. I made some changes and performed another commit. I definitely am
getting closer now because...
- sldb now shows the CPs and their correct host so...
- the ICC now lists the hosted CPs and...
- IIF.cur shows all DONE.
I believe at this point the SysDef and commit process is successful.
Although the ICC and FoxSelect list the CPs now, they cannot communicate
with the CPs "ICC = Communication to CP (-1071) Failed". And I tried
/opt/fox/ciocfg/api/load_all to the CPs and it just hangs. And the CPs will
not boot to the Checkpoint files I copied from the original AW70 host. I
finally figured out the reason is...
The CPs are not on-line. If I open the System Management Display it still
shows "System Monitor not Responding". So the only thing missing at this
point is the System Monitor so I can put the CPs on-line. I specifically
remember assigning one to the new AW70, giving it a name and adding the CP
Stations to monitor. So I am not sure what I still missed but I will
revisit the SysDef again tonight...
Thanks again for the help getting me this far...
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A. Adams
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Boulay, Russ
Sent: Friday, September 23, 2016 12:18 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Windows NT AW70 V6.4 SysDef changes and commit
If your sldb file did not have anything that correctly represents the system
hosting, especially no CP's or Workstations in that file, then your sysdef
is not correct.
The sldb file comes directly off the commit diskette and is built according
the Sysdef stations that have been assigned to each other and smon hosting.
So sysdef is not right
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Joseph M. Riccardi
Sent: Friday, September 23, 2016 12:10 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Windows NT AW70 V6.4 SysDef changes and commit
Just for the record, I attempted to rerun the commit procedure and at the
1st prompt for a diskette I get the message "The current package blah, blah,
blah has been successfully installed in a previous installation. Do you
want to set this package to Day 0 status?" I assume "No" but nothing makes
sense. Ditto for other diskettes. The packages are marked as "DONE" in the
IIF.cur but they are not showing up in the System after rebooting.
Of the changes, the CIO_Config/CSA move appears to be working but the System
Monitor and CP host changes are not despite the IIF.cur marked as "DONE".
Sooooooooo...
The setup log.txt shows the following errors: *****(There are no Release
Level Diskettes, only (4) Revision Level Diskettes 11001-11004. Are they
the same? Does it indicate I have a bad set of Release/Revision Level
Diskettes? Where can I get replacements?)*****
INFO:C:\TEMP\_ISTMP9.DIR\tar.exe xf \\.\A: ./OS1CS ./ACSA7 ./AADM7 ./AW70
INFO: Tar returned error on disk set: Release Level Diskette.
INFO:C:\TEMP\_ISTMP9.DIR\tar.exe xf \\.\A: ./OS1CS ./ACSA7 ./AADM7 ./AW70
INFO: Tar returned error on disk set: Release Level Diskette.
INFO:C:\TEMP\_ISTMP9.DIR\tar.exe xf \\.\A: ./OS1CS ./ACSA7 ./AADM7 ./AW70
INFO: Tar returned error on disk set: Release Level Diskette.
INFO:C:\TEMP\_ISTMP9.DIR\tar.exe xf \\.\A: ./OS1CS ./ACSA7 ./AADM7 ./AW70
INFO: Tar returned error on disk set: Release Level Diskette.
INFO:C:\TEMP\_ISTMP9.DIR\tar.exe xf \\.\A: ./OS1CS ./ACSA7 ./AADM7 ./AW70
INFO: Tar returned error on disk set: Release Level Diskette.
INFO:C:\TEMP\_ISTMP9.DIR\tar.exe xf \\.\A: ./OS1CS ./ACSA7 ./AADM7 ./AW70
INFO: Tar returned error on disk set: Release Level Diskette.
INFO:C:\TEMP\_ISTMP9.DIR\tar.exe xf \\.\A: ./OS1CS ./ACSA7 ./AADM7 ./AW70
INFO: Tar returned error on disk set: Release Level Diskette.
INFO:C:\TEMP\_ISTMP9.DIR\tar.exe xf \\.\A: ./OS1CS ./ACSA7 ./AADM7 ./AW70
INFO: Tar returned error on disk set: Release Level Diskette.
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A. Adams
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Joseph M. Riccardi
Sent: Thursday, September 22, 2016 5:49 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Windows NT AW70 V6.4 SysDef changes and commit
Russ and Terry, et al... Gents, please don't give up on me yet. I think I
am close...
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Joseph M. Riccardi
Sent: Thursday, September 22, 2016 11:21 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Windows NT AW70 V6.4 SysDef changes and commit
Russ and Terry,
Thanks for the help and suggestions. I will address both of your comments
below...
1st I would like to review what I see at this point...
- I double checked the SysDef configuration and everything looks good,
just as I changed them. The System Monitor was reassigned to the new AW70,
the CPs are all hosted by the new AW70, the old AW70 is gone, and all of the
checked and verified columns are "Yes" with a modified date of yesterday.
:-)
- The d:/usr/fox/sp/IIF.pkg file shows the new AW70, all CPs/FBMs that were
re-hosted, and ASMON7 (System Monitor?) as NOTYET. ;-( I see a number of
the standard software packages as DONE, including AICC7 (ICC?). During the
commit process I inserted all of the appropriate diskettes (i.e., System
Monitor, ICC, CP60, etc.) when prompted and all installed without errors.
At this point my conclusion is that the SysDef process and the move CSA
process was successful, but the commit process failed miserably. Why?
Status...
- When I call up the System Management Display the System Monitor is not
shown, getting error "System Monitor not responding". That makes sense
since ASMON7 = NOTYET.
- When I open the CIO_Config it appears that all of the Compounds are
listed but when I pick one I get "CSA Error - CSgetcmpd Failed". That makes
sense since CSA move OK but AICC7 = NOTYET.
- If I select the CIO_Station_Config there are no CPs listed.
- All of the /usr/fox/sp/*lns files look correct.
- sldb is a new file to me but it only shows the Stations hosting volumes.
What should it show?
- All CPs are empty and not even on line.
- I moved the Checkpoint files from the old AW70 to the new one to reboot
them as soon as I resolve the commit process issues. Or I was hoping to do
a Load_All from the Save_All files I created and then checkpoint them so the
Checkpoint files are up to date.
It sure looks to me like I am close if I can figure out why the commit
process failed. Any ideas? Or just do it again?
Thanks
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A. Adams
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
*** Confidentiality Notice: This e-mail, including any associated or
attached files, is intended solely for the individual or entity to which it
is addressed. This e-mail is confidential and may well also be legally
privileged. If you have received it in error, you are on notice of its
status. Please notify the sender immediately by reply e-mail and then delete
this message from your system. Please do not copy it or use it for any
purposes, or disclose its contents to any other person.
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
