Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Damaged DISK // Marking a new pack a HALT/LOAD unit
65 views
Skip to first unread message
Andres Abello
Jan 15, 2013, 7:56:49 AM1/15/13
to
Hi Everybody, The pack where I have my MCP is damaged, I managed to copy the MCP to another pack, and mark it as a MC so MCP will load in that pack and not the original,
but still some services start from my DISK(Pack) and not from the new one, I need all services start from the new pack so I can replace the damaged Disk. Any one have a clue? Why is not loading all services from the new DISK??
Andres Abello
Jan 15, 2013, 7:57:26 AM1/15/13
to
MCP 14
Paul Kimpel
Jan 15, 2013, 9:28:13 AM1/15/13
to
Andres Abello wrote:
>
> Hi Everybody, The pack where I have my MCP is damaged, I managed to copy the MCP to another pack, and mark it as a MC so MCP will load in that pack and not the original,
>
> but still some services start from my DISK(Pack) and not from the new one, I need all services start from the new pack so I can replace the damaged Disk. Any one have a clue? Why is not loading all services from the new DISK??
>
The short answer to your last question is that there is a lot more to
>
> Hi Everybody, The pack where I have my MCP is damaged, I managed to copy the MCP to another pack, and mark it as a MC so MCP will load in that pack and not the original,
>
> but still some services start from my DISK(Pack) and not from the new one, I need all services start from the new pack so I can replace the damaged Disk. Any one have a clue? Why is not loading all services from the new DISK??
>
the system software on an MCP system than just the MCP codefile. In
particular, there are numerous system library files. There is also a
bunch of configuration data that needs to be moved, some of which you
cannot access directly, because it is not stored under the file system.
Most system services are mapped to file locations through the SL
command, so I suspect that is why you still have a lot running on the
old disk. Those SL entries will need to be redesignated. Many of those
libraries require additional parameters on the SL command, which you can
view by using the SL* variant.
Here are some questions, the answers to which will help determine the
approach that should be used:
1. In what way is the original disk "damaged"?
2. What, exactly, do you have on the original disk?
* JOBDESC? (this is the job queue data)
* DL designations?
* Print System data (BACKUPLIST, etc.)?
* Logs?
* DMSII Audit Trails?
* System utilities (DUMPALL, FILEDATA, etc.)?
* Application programs or data?
* Anything else?
3. Do you need the replacement disk to have the same family name as the
original disk?
4. What from the original disk is now running on the new disk and can
you afford to wipe all of that out and start over?
5. How much system downtime can you afford to deal with this issue?
Depending on how the original disk is damaged, one possible approach is
to mirror the original disk onto another drive, then break the mirror by
removing the original drive, and then disable the original drive so that
the system would not have to contend with two disks with the same label.
A UR would suffice to disable the original disk. An LB or RC would also
work, depending on whether you needed to preserve what was left on the
original disk.
This mirror approach would copy all of that system configuration data
that is outside of the file system. I have never tried to do this on a
running Halt/Load unit, but see no reason why it shouldn't work. Note
that if OP MIRRORING is not currently set, it must be set and a
halt/load performed to enable the setting.
--
Paul
Andres Abello
Jan 15, 2013, 10:47:19 AM1/15/13
to
Hi Paul, thanks...
I finally was able to load the MCP in the new disk, and named DISK, so no problem with that, the only think I can get up is the PRINT system, due that is imposible to copy those files into the new disk. (tried with cd but CD is not working)
Regarding your questions..
1. In what way is the original disk "damaged"?
Some sectors are not working and in the ODT is showing PKxx Media Error. I tried to copy most of the libraries and stuff but is not letting me.
2. What, exactly, do you have on the original disk?
Everything
3. Do you need the replacement disk to have the same family name as the
original disk?
Yes.. Is mandatory...
4. What from the original disk is now running on the new disk and can
you afford to wipe all of that out and start over?
Basically I need all the applications that were working in the olddisk work in the new one, so we dont have to make a Cold-Start and re-install everything back...
5. How much system downtime can you afford to deal with this issue?
No issues with time..
I finally was able to load the MCP in the new disk, and named DISK, so no problem with that, the only think I can get up is the PRINT system, due that is imposible to copy those files into the new disk. (tried with cd but CD is not working)
Regarding your questions..
1. In what way is the original disk "damaged"?
2. What, exactly, do you have on the original disk?
3. Do you need the replacement disk to have the same family name as the
original disk?
4. What from the original disk is now running on the new disk and can
you afford to wipe all of that out and start over?
5. How much system downtime can you afford to deal with this issue?
Paul Kimpel
Jan 16, 2013, 8:48:07 AM1/16/13
to
my prior post. Make sure that OP 34 (MIRRORING) is set -- it requires a
halt/load if it's not currently set to make it effective. Then check out
the MIRROR ODT command, particularly MIRROR CREATE and MIRROR RELEASE.
--
Paul
0 new messages