Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

when I use ex-updat:a1,all; & ex-updat:bp,all; I get error message,any help Thanks!

Status
Not open for further replies.

kevinjing

Technical User
Feb 28, 2015
10
CN
when I use ex-updat:a1,all; & ex-updat:bp,all; I get error message,any help Thanks!

<ex-updat:bp,all;
EX-UPDAT:BP,ALL;
H500: AMO UPDAT STARTED
F02: ACCESS ERROR; DMS ERROR CODE: 61
AMO-UPDAT-111 UPDATING HARD DISK DATABASE
EXEC NOT COMPLETED;
<ex-updat:A1,all;
EX-UPDAT:A1,ALL;
H500: AMO UPDAT STARTED
F02: ACCESS ERROR; DMS ERROR CODE: 61
AMO-UPDAT-111 UPDATING HARD DISK DATABASE
EXEC NOT COMPLETED;

so I check the DDSM:

DIS-DDSM;
H500: AMO DDSM STARTED
CONTROLLER: 1 IS ACTIVE LOAD DEVICE, LOAD AREA IS: :pDS:
TYPE: HD SS-NO : <2GIGA> SIZE : 2000 MB ( 32000*64KB) GRAN : 512
NON-RMX PARTITIONS:
SYSTEM ID SYSTEM NAME BEGIN / NO OF SECTOR(S) SIZE
H'12 UNIXWARE H' 3E823F H' 139C5 39 MB ( 627*64KB)
H'63 UNIXWARE H' 3FBC04 H' 4237662 33902 MB (542444*64KB)
H'63 UNIXWARE H' 4633266 H' 44E1D9 2204 MB ( 35267*64KB)
AREA: A NAME : A1H1A STATUS : I N S E R V I C E
AREA-SZ: 0 MB (2 *64KB) A-GRAN: 512
AREA: E NAME : A1H1E STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:pDS:
ACTIVATED LOGICAL NAMES:
:pDS:
AREA-SZ: 200 MB (3200 *64KB) A-GRAN: 4096
AREA: F NAME : A1H1F STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:DBDA:,:DBD:,:TMD:,:pAS:,:AMD:,:DMP:
ACTIVATED LOGICAL NAMES:
:DBDA:,:DBD:,:TMD:,:pAS:,:AMD:,:DMP:
AREA-SZ: 62 MB (992 *64KB) A-GRAN: 4096
AREA: G NAME : A1H1G STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:CGD:
ACTIVATED LOGICAL NAMES:
:CGD:
AREA-SZ: 150 MB (2400 *64KB) A-GRAN: 4096
AREA: H NAME : A1H1H STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:DMS:,:DSY:
ACTIVATED LOGICAL NAMES:
:DMS:,:DSY:
AREA-SZ: 70 MB (1120 *64KB) A-GRAN: 4096
AREA: I NAME : A1H1I STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:SCR:
ACTIVATED LOGICAL NAMES:
:SCR:
AREA-SZ: 701 MB (11217*64KB) A-GRAN: 4096
AREA: J NAME : A1H1J STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:GLA:
ACTIVATED LOGICAL NAMES:
:GLA:
AREA-SZ: 200 MB (3200 *64KB) A-GRAN: 4096
AREA: K NAME : A1H1K STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:DIAG:
ACTIVATED LOGICAL NAMES:
:DIAG:
AREA-SZ: 616 MB (9868 *64KB) A-GRAN: 4096
CONTROLLER: 6
TYPE: HD SS-NO : <MO1G3> SIZE : 1183 MB ( 18932*64KB) GRAN : 2048
AREA: A NAME : A1H6A STATUS : B L O C K E D B Y A M O
AREA-SZ: 0 MB (2 *64KB) A-GRAN: 2048
AREA: E NAME : A1H6E STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
:pDS:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 200 MB (3200 *64KB) A-GRAN: 4096
AREA: F NAME : A1H6F STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
:DBDA:,:DBD:,:TMD:,:pAS:,:AMD:,:DMP:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 62 MB (992 *64KB) A-GRAN: 4096
AREA: G NAME : A1H6G STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
:CGD:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 150 MB (2400 *64KB) A-GRAN: 4096
AREA: H NAME : A1H6H STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
:DMS:,:DSY:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 70 MB (1120 *64KB) A-GRAN: 4096
AREA: I NAME : A1H6I STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
:MOD-SCR:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 701 MB (11217*64KB) A-GRAN: 4096

AMO-DDSM -111 DISK STATUS
DISPLAY COMPLETED;

Then I dea-dssm & act-dssm & cha-dssm,but ex-updat:a1(bp),all; also not work.

any idea Thanks.
 
Have a check in the UW Assistant - is there a backup running already there
Also do a
TSN;
in Comwin
 
From the DIS-DDSM, your system appears to be a very old version. (Your controller 6 is a 1.3GB MO disk). It may take a while to discover the source of this problem. Your phones may be working fine now, but without a working hard disk (Partition E), recent Moves, Adds, and Changes are being saved in Switching Unit memory ONLY. Meanwhile, understand that if your system should lose power, the system may not boot if the hard disk is corrupted or has failed. The Switching Unit(s) will not retain the database if the system is powered off. Therefore, ALERT #1: do not power off the system!!!

Do you have current backups? If you cannot perform EXE-UPDAT, have you attempted to perform a backup to the MO disk using COPY-DDRSM?

My recommendation: try to perform a Switching Unit and ADS/ADP REGEN. At least you will a copy of all of the system's AMOs if the system crashes. CAUTION: if your Hard Disk is corrupted or damaged, this procedure may not work.

Here's how via COMWIN:

Step 1: DIS-VEGAS;
(there should be two lines of output - the first line should represent your Switching Unit, and the final field (far right) should indicate STATUS = "FREE". The second line should represent the ADS/ADP, and should also indicate "FREE" status.

IF YOU SEE THE FOLLOWING OUTPUT, YOU MAY PROCEED DIRECTLY TO AMO REGEN

DIS-VEGAS;
H500: AMO VEGAS STARTED
SYSTEM NO. AMO APS NO. START USER STATUS
SWU: L12345678987654321 --- P30252B4900B00101 00.00.00 00:00 NOBODY FREE
ADS: L12345678987654321 --- P30252B4900A00101 00.00.00 00:00 NOBODY FREE
AMO-VEGAS-111 ADMIN. OF DATABASE GENERATION RUNS ON SUPPORT SYSTEM
DISPLAY COMPLETED;

-------------------------------------------------------------------------------------------------------
IF YOU SEE THIS OUTPUT, YOU MUST PERFORM AMO DEL BEFORE ATTEMPTING THE REGEN.

DIS-VEGAS;
H500: AMO VEGAS STARTED
SYSTEM NO. AMO APS NO. START USER STATUS
SWU: L12345678987654321 --- P30252B4900B00101 00.00.00 00:00 Billybob FINISHED
ADS: L12345678987654321 --- P30252B4900A00101 00.00.00 00:00 NOBODY FREE
AMO-VEGAS-111 ADMIN. OF DATABASE GENERATION RUNS ON SUPPORT SYSTEM
DISPLAY COMPLETED;


Step 2: (Perform only if DIS-VEGAS indicates a status other than "FREE", such as "FINISHED")

STA-DEL:":A1H1F:VEGAS/DATEI",;


Step 3: Start the Regeneration of AMOs. STA-REGEN:<USERCODE=your name or initials>,<SYSNO=L12345678987654321>,<CONT=N>,,,,,,<UNIT1=ALL>;

Example: STA-REGEN:Billybob,L12345678987654321,N,,,,,,ALL;

When this AMO completes, a file named "ALL.SAMTXT" will be saved on the RMX portion of the hard disk: :A1H1F:L12345/678987654321/RE/

Step 4: To retrieve this file, click "Connection" on the Top Menu of your open ComWin session, then select "Start local Filetransfer".
A new window named "Remote File System" should open. (Note: this window may not open. Instead, an icon may be "flashing" on your Windows Task Bar. Click the icon to open the window).
This "Remote File System" window provides a Windows "Explorer"-like view of the system's RMX structure on hard disk.

Remote_bepee4.jpg


Click to open the folder that represents the first 6 characters of your System Number, such as "L12345".
Next, click the folder that represents the final 11 characters of your System Number, such as "678987654321"
Next, open the folder "RE" (means "RESPONSE")
Now you should see the file "ALL.samtxt". Right-click this file, and select "COPY TO" - Not "Copy" or "Copy as" or "Copy From"!

Select where to save the file on your PC.
When prompted, respond "YES" to convert the file to ASCII.

If you are able to retrieve this file, open it with Wordpad, as it preserves the formatting better than Notepad (my opinion).
Use Wordpad's "REPLACE" function to remove the "M2 1 " or "M1 1 " in front of each line, or any other characters that may appear in front of a line (AMO).
The first few characters in the file may also be removed. The first AMO should be ADD-CODEW; DO NOT DELETE this codeword! Perform "SAVE AS.." to save this edited file using a different File Name.
You should now have the original ALL.samtxt file, and the edited version. It is always a good idea to keep the original file, in case an error was made when editing the file.

Hopefully this process works, so that if your hard disk fails, you will have the AMOs necessary to rebuild the system AFTER resolving the problem.




Good Luck!
 
Manay Thanks to Sbcsu & Iamnothere.

The hipath4k is version 2,and I can get regen file as you say. also if power down the system can go alive with the old datebase. The unify say one of the harddisk area is broken,so I decined to chang harddisk.[sad]
 
Hello,

I've a problem with a Hicom300 v3.5:
If I make a dis-vegas, in the status, I've in the swu, instead of free ou finished, I've the status=unknow.
I've tried to sta-del:":pas:vegas/datei" but without sucess.

Someone have an ideia?

Thanks,
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top