Hicom300 logging Hista

[Hic300]

Hi guys,
Strange situation.
Could not great hista file. When try to add from CHA-ASSGN:SATIC,DPT4,CFILE,C-FBTHIST,10000; i got F02: IT WAS NOT POSSIBLE TO SET UP FILE C-FBTHIST. and as a result could not add hista, got F1: FILE C-FBTHIST UNKNOWN. Dis sta-init:a1h1f, does not help.
Any ideas??
Thanks and regards,

 

[sbcsu]

REG-HISTA;

You might have to add hista ?

ADD-HISTA:10000,DEACT;

 

[member 1453342]

Assgn definitely comes before hista.

Sounds like a problem with the disc area.

I would enter the same commands as me, post your log file, let's see where yours differs.

  <dea-dssm:a1,1,f;
DEA-DSSM:A1,1,F;
H500:  AMO DSSM  STARTED

AMO-DSSM -111       DISK SWITCHOVER                                             
DEACTIVATE COMPLETED;
  <sta-init:a1,a1h1f;
STA-INIT:A1,A1H1F;
H500:  AMO INIT  STARTED
H01: CREATE AND WRITE FNODE FILE
H02: INIT FOR <:A1H1F:> COMPLETED
H03: INIT FINISHED
STATUS  =  H'0000
AMO-INIT -111       HARD DISK AREA INITIALIZING                                 
START COMPLETED;
  <act-dssm:a1,1;
ACT-DSSM:A1,1;
H500:  AMO DSSM  STARTED
H04: AREA <:A1H1E:> ALREADY ACTIVATED
H18: AREA <:A1H1F:> IS ACTIVATED
H04: AREA <:A1H1G:> ALREADY ACTIVATED
H04: AREA <:A1H1H:> ALREADY ACTIVATED
H04: AREA <:A1H1I:> ALREADY ACTIVATED
H04: AREA <:A1H1J:> ALREADY ACTIVATED
H04: AREA <:A1H1K:> ALREADY ACTIVATED

AMO-DSSM -111       DISK SWITCHOVER                                             
ACTIVATE COMPLETED;
  <CHANGE-ASSGN:SATIC,DPT4,CFILE,"C-FBTHIST",9999999;
CHANGE-ASSGN:SATIC,DPT4,CFILE,"C-FBTHIST",9999999;
H500:  AMO ASSGN STARTED
H02: FILE C-FBTHIST HAS BEEN SET UP.

AMO-ASSGN-111       INPUT/OUTPUT DEVICE ASSIGNMENT                              
CHANGE COMPLETED;
  <

 

[Hic300]

Thanks to all,
Did it 20 times, unsuccessful. Because I cod not great c-fbthist file I can not add hista.

 

[member 1453342]

That’s strange.

What does dis-ddsm a1 look like?

What’s the software version ?

 

[Hic300]

dis-ddsm:a1 norm, area a1h1e and a1h1f in service. a1h61 is locked. Hipath 4300 Version 1.0.09.
I can great regen file in F area and download it, but c-fbthist could not be greated.

 

[member 1453342]

Can you post the dis ddsm.

 

[Hic300]

 

[sbcsu]

REG-ASSGN:SATIC;
Please

 

[member 1453342]

I wanted to see if
- HD was the active load device (it is)
- You had all the area names added with DLSM (you do)
- There was nothing weird with conflicting area sizes of DB and actual used value (there is not).

So it looks OK.

- I would check if any file can be created, try FILE instead of CFILE, try against DPT1/2, try a different name (no C- for a normal file) etc just to see if it works.
- Consider ADP reload.

Your line does not enter for me in V8 software, file size is too small. You should ? your AMO and check what is allowed.

<CHA-ASSGN:SATIC,DPT4,CFILE,C-FBTHIST,10000;
M34: VALUE NOT WITHIN ADMISSIBLE RANGE                                          
LEN = ?
LEN             : LENGTH OF FILE
CHARACTERISTIC  : REQUIRED                                   
POSSIBLE VALUES : 100000-9999999
LEN =

 

[Hic300]

Thanks all,
No, it looks like with HDD area size etc everything is ok, I have same pbxs with same version and there everything with hista and assgn is ok. I do not know why I can not great c-fbthist file, even I can grat regen file on the same area F.

 

[Hic300]

Your line does not enter for me in V8 software, file size is too small. You should ? your AMO and check what is allowed.

 

[member 1453342]

Next step for me would be a reload of the ADP.

 

[Hic300]

ADP reloaded several times, even pbx was fully restarted.

 

[member 1453342]

Maybe we miss config from some other AMO then.

Can you post a regen of the ADP? I mean post the file copied off with comwin-ft?

 

[Hic300]

Link to ADP

I did not fount any connected commands, only assgn, signl and hista((.

 

[Hic300]

I think the only way is to prepare new muster disk with same version and load database and then load pbx with new prepared hdd, but unfortunately version is too old and I do not know where to find it and have not any proper tools to prepare muster hdd ((( But it should work (((

 

[member 1453342]

I do not have any more software and hardware as old as yours, UV1.0 SA9 I think, and 4300 cabinet. So I picked the parts of the ADP that would run into a newer CPCI, and of course, all OK, ASSGN worked as it should. But, that is what I expected anyway.

You said you had similar/same PBX. If you regen one of those, and WINDIFF the ADP regen - are they the same? APC etc, the same?

I have no idea what is wrong with this.

I think you have H300 experience already, so you know, it will REGEN in two parts, the ADP and the SWU. On a blank disc, we have a default ADP and a blank SWU. We do not care too much about the ADP, we can always change it. SWU is the important stuff.

So if you have a working PBX, same software, architecture, you could take a DDRSM copy from that good node, load it in this bad node, make a CHA-DBC, reswwudb=yes, and erase the SWU DB. Then make a GENDB from your SWU regen, and correct the ADP with just the parts you need. That will work.

Or as something else to try, you could copy the blank ADP file onto your existing ADP, make it default, reload the ADP, test if the problem has gone, reconfigure the ADP with just the parts you need. This might work, but a lot of the files/OS remain the same, it depends where the problem with ASSGN really is, but it would be an interesting experiment.

The ADS/SWU files are stored twice, in RES and ABS, so you have to overwrite the ADP DB twice, make sure both copies are default

  <sta-copy:":pds:LEER/BS.ZDAADS00",":PDS:APSZ/ISU/BS/RES/ZDAADS00";
STA-COPY:":PDS:LEER/BS.ZDAADS00",":PDS:APSZ/ISU/BS/RES/ZDAADS00";
H500:  AMO COPY  STARTED
COPY STARTED
DEST. FILE <:PDS:APSZ/ISU/BS/RES/ZDAADS00> EXISTS: OVERWRITE ?
ANS = c
<:PDS:LEER/BS.ZDAADS00> COPIED TO
     <:PDS:APSZ/ISU/BS/RES/ZDAADS00>
COPY FINISHED
STATUS  =  H'0000
AMO-COPY -111       COPYING OF FILES                                            
START COMPLETED;
  <sta-copy:":pds:LEER/BS.ZDAADS00",":PDS:APSZ/ISU/BS/abs/ZDAADS00";
STA-COPY:":PDS:LEER/BS.ZDAADS00",":PDS:APSZ/ISU/BS/ABS/ZDAADS00";
H500:  AMO COPY  STARTED
COPY STARTED
DEST. FILE <:PDS:APSZ/ISU/BS/ABS/ZDAADS00> EXISTS: OVERWRITE ?
ANS = c
<:PDS:LEER/BS.ZDAADS00> COPIED TO
     <:PDS:APSZ/ISU/BS/ABS/ZDAADS00>
COPY FINISHED
STATUS  =  H'0000
AMO-COPY -111       COPYING OF FILES                                            
START COMPLETED;
  <exec-rest
TYPE = unit
UNIT = a1
RSLEVEL = reload
PRSTATE = ;
EXEC-REST:UNIT,A1,RELOAD,;
H500:  AMO REST  STARTED
 H01: RELOAD HAS BEEN INITIATED

So that will reload the ADP as a blank, new, DB. Your ADP config will have to be put back in. And yours is a mono proc so you will have to reload the whole thing, you can't reload just the ADP.

That blank ADP file should be there on V1, you can check it.

Before you do any of this, you should take a DDRSM copy (or two) from the bad node, and make sure it reloads OK.

 

[Hic300]

Many thanks Morienti and all other guys,
Problem that PBX is too far from me and I have only remote access to PBX. And version is too old and MO is not working (as traditional problem of Hicom). So the way is only to prepare new HDD on my test pbx (same, Hipath 4300), load DB and send it to site to install it instead old HDD and load pbx with new HDD.
I wrote here because I thought that i miss some command and it should work. It seems there is some problem in the base muster.
Thanks to all and sorry to waste your time.

 

[member 1453342]

No time wasted here. It’s an interesting problem.

You could always blank the ADP remotely with the leer file if you have the testicles. SWU should be unaffected.