Adabas NUCSTAT report


We’ve recently moved from a mainframe to Unix environment. One of the things I used to use a lot was the NUCSTAT report which gave useful information like the distribtion of command by source, file, thread and type.

Does anybody know if there is an equivalent report on Adabas for Unix?

I think it got generated as part of the weekly shutdown on the mainframe, but ideally I’d like to run it weekly and refresh the values as the Unix Adaabs dataabse doesn’t shut down very often.

You can use the DBA Workbench to get this information piece by piece, but you’ll have to create a script to have it all in a single report.

Report --> Session…

Report --> Statistics…

Hi Ralph, thanks for the reply.

I’ve tried to go into ADADBA, but I get an error

Workbench cannot be started because environment variable DISPLAY is not defined.

Looking at the documentation for ADADBA it says

The Adabas Workbench is no longer supported with Version 6.2. On those platforms for which the DBA Workbench was delivered for Version 6.1, the Workbench will still be delivered, but the functionality is frozen to the functionality that was available with Version 6.1. New features that were introduced for Version 6.2, such as date/time fields, are not supported.

We went straight in at v6.3 so I think that’s saying we won’t have it, but we obviously do because I get an error when trying to run it.

Any idea what DISPLAY should be set to? I’m just running it from the command line using PuTTy.

Doing some more digging around ADADBA and DBA workbench it seems that it has been replaced by a new product called AMA which we don’t have.

The DBA workbench is still there, but it needs a graphical environment, so PuTTy won’t suffice.

I haven’t done this in a very long time, and then it was from a shell on a standalone machine.

To get your machine name:
hostname -s

export DISPLAY=“your-machine-name:0”

Then invoke ADADBA.

As stated in the documentation, an X-Server must be running (for the graphical interface).

If you can’t get to the physical machine, see about a Remote Desktop Connection.

Ian, you’ll have to translate this to a shell script, but it should give you a good idea of what is available. The parameters are in-stream only for ease of posting. You get one massive report called “Ian.prt”.

@REM Generated by DBA Workbench 
CALL "C:\ProgramData\Software AG\Adabas\\db111\assign.bat"

rem  ==========  Database Reports
echo dbid=111                     > Ian.prm
echo display=activity            >> Ian.prm
echo display=bp_statistics       >> Ian.prm
echo display=high_water          >> Ian.prm
echo display=dynamic_parameter   >> Ian.prm
echo display=static_parameter    >> Ian.prm
echo display=plog_statistics     >> Ian.prm
echo display=fp_statistics       >> Ian.prm
"C:\Program Files\Software AG\Adabas\V62101\\bin\adaopr.exe"  < Ian.prm >> Ian.prt

rem  ==========  Database Session
echo dbid=111                     > Ian.prm
echo display=tt                  >> Ian.prm
echo display=commands            >> Ian.prm
echo display=cq                  >> Ian.prm
echo display=hq                  >> Ian.prm
echo display=icq                 >> Ian.prm
echo display=uq                  >> Ian.prm
echo display=uq_files            >> Ian.prm
echo display=uq_time_limits      >> Ian.prm
echo display=uq_full             >> Ian.prm
echo display=file_io             >> Ian.prm
"C:\Program Files\Software AG\Adabas\V62101\\bin\adaopr.exe"  < Ian.prm >> Ian.prt

rem  ==========  Adarep
echo dbid=111                     > Ian.prm
echo free_space                  >> Ian.prm
echo files=*                     >> Ian.prm
echo checkpoints=*               >> Ian.prm
"C:\Program Files\Software AG\Adabas\V62101\\bin\adarep.exe"  < Ian.prm >> Ian.prt

rem  ==========  File Information
echo dbid=111                     > Ian.prm
echo file=*                      >> Ian.prm
echo usage=(DS,NI,UI)            >> Ian.prm
echo descriptor=*                >> Ian.prm
"C:\Program Files\Software AG\Adabas\V62101\\bin\adafin.exe"  < Ian.prm >> Ian.prt

del Ian.prm