4 comments on “Blog
  1. Frank Ternest says:

    Hi Nigel,

    impossible to install OMVS utilities (blocked at the execution of the exe). (Read error)
    Do you have some hints



    • Nigel says:

      Hi Frank,

      OK, without knowing the precise details of the error and when it happens I can only guess.

      It sounds like something on your end is taking exception to the installation and blocking. My first guess would have to be your system is trying to validate the signed package. To do this you’ll need my root certificate. The installation is simply a signed Nullsoft package, so pretty standard stuff.

      Second guess would have to be, not running installation as ‘administrator’. First time you install, it needs admin in order to create directory under \Program Files but there after it doesn’t. You should be able to create the directory and install with user rights.

      Then, once installed, in order to run, you’ll need to have the Microsoft runtime libraries installed.

      Are you only having problem with OMVS utilities, or does the same apply to the RACF utilities?

      Any more info you can give around either your environment (e.g. which version of Windows) or your error?


  2. Bob Bertrand says:

    A colleague of mine asked for my help – he’s installing your RACF package. It installs to %programfiles% w/o issue. But if I understand correctly, you then at USE time (not install time) edit and put files under the %programfiles%\RACF folder structure. This structure is READ ONLY and can only be written to by programs executing as ADMIN. The INI files – it is unclear – do they specify the input and output file names relative to the %CD% (current dir)? Thanks for any insight.

    • Nigel says:

      The original concept was to have the programs in one location and the data in another. There is nothing to say you have to put the programs under Program Files, but where ever you put them its best if they are easily found from your PATH.

      Yes, when running any of the programs, they look for the racf.ini file in the current directory. That makes sense if you have multiple RACF databases you are generating reports from so you can keep all the reports together in the same directory.

      racf.ini points to the input IRRDBU00 unload file. As I tend to group everything for a database in a directory I normally refernce the input file as relative file in the current directory, but you can use absolute path if you prefer and put you input file anywhere you want. I sometime do this if I want to keep a particular snapshot for audit purposes and be able to generate reports relative to a specific date of unload.

      Hope that helps explain the rationale behind the design.

Leave a Reply