8 replies to this topic

[Scott Minter]

Pro-IV version 4.6 rev 5.1.2 (Glovia)

Has anyone written a utility to export the two files:
FUNCTDEF.PRO
SECURITY.PRO

to a text file?

Ultimately I am trying to get a report that shows a function and who has access to the function (by category even better).

I am able to write a superlayer program to export the functdef.pro file, but I cannot access the security.pro file. Any ideas?

[CSuarezdelReal]

Scott,

In my Glovia environment I have a SuperLayer file definition for GL_SECUR which maps physically to security.pro. I have a buch of home-made SL functions that deals with securirty accesing such a file.

Reagrds,

[Joseph Bove]

Scott,

We have access to the ProIV bootstrap defs for things like FUNCTDEF and SECURITY. However, the nature of the agreement with ProIV prevents us from sharing this information.

Have you entered a similar agreement with ProIV?

Regards,

Joseph

[powconcepts]

Hi Scott,

To be able to track who can run a specific function, I do the following:

1) work out what menu the function is on
- using entered function, read serial through MENUSCR looking for entered function.
- then go out to FUNCTDEF to give menu name and details.
2)this can be run a number of times if the menu displayed is a sub menu.
because our menus are customised ... eg: MENUSRT (for user Steve Turner)
the report may show the function was on MENUSRT and I can see Steve Turner can run the function.

We have also migrated from 7.5,8.5,3.2, 5.4 and each time I have been able to extract the security
information for each user and use it to input into the new system. The later version have import
facilities inbuild so this was not necessary. we have customised security for each function,
eg: rather than SO we have SOU and SOQ etc enabling us to have tighter security.
Glovia have in later version also adopted this method of sub categories.

I have exported the function security out to spreadsheet (or different file definition) etc and
used this information to compare the vanilla version of the new Glovia version. This way I can determine new functions and changes in security.

Care should be given on importing information as some of the security and logonf are loaded into
oracle.

I don't know how much information you have been given to date, but if you need any additional
information, please email me and I will be happy to help.


regards,
Nerida

[hwyap]

Dear powconcepts,

I don't get how you can get cross-reference between menu and function. Is it in FUNCTDEF?
Currently, i'm trying to find out what file store cross-reference between menu and function, i don't see it in any field of FUNCTDEF. Please help.



Rgds,

Vivien

[SteveHoughton]

Hi Scott

I have utilities that will export any file that has a file definition in Pro-IV - They work on Pro-IV versions 2.2, 4.0,4.6,5.0 and 5.5. They create csv's and the latest 5.5 version can create excel spreadsheets.

Do an isout of the functdef.pro and security.pro and sent it to me at pro4services@aol.com and I will send you back the csv's, or an excel spreadsheet if you prefer that.

I sell this service for a living so I cannot make the software available for free.

Regards

Steve

[hwyap]

Hi Scott

I have utilities that will export any file that has a file definition in Pro-IV - They work on Pro-IV versions 2.2, 4.0,4.6,5.0 and 5.5. They create csv's and the latest 5.5 version can create excel spreadsheets.

Do an isout of the functdef.pro and security.pro and sent it to me at pro4services@aol.com and I will send you back the csv's, or an excel spreadsheet if you prefer that.

I sell this service for a living so I cannot make the software available for free.

Regards

Steve

Hi, I'm doing a report on cross reference between function and menu.... Is there any file which i can accessed to view these information? I need to know the file name. Is it inside security.pro, cos i can't find any related data in functdet.pro

Edited by hwyap, 03 July 2007 - 10:00 AM.

[SteveHoughton]

The security table looks like this

TRM: CONSOLE F I L E D O C U M E N T A T I O N OPR: SYS

CO- AUTO- ENFORCED EXTERNAL FILE KEY RECORD
DIV SEQ PAGING RECORD FORMAT TYPE LENGTH LENGTH
FILE NAME: SECURITY 15 64
ALTERNATE: RECORD CODE:
DESC: System Security File

---------------------------R E C O R D L A Y O U T--------------------------------
DATA MAX FILL SPECIAL ARRAY
SEQ TYPE VARIABLE NAME LEN CODE DISPLAY-CODE CHECK SIZE
--- ---- -------------------------------- --- --- ------------ -------- ----

001 K @COD 3
002 K @OPRID 3
003 K @SECTYPE 1
004 K @SECCAT 8
005 N @SECLVL 2
006 N @SECLVLA 2
007 N @SECLVLC 2
008 N @SECLVLD 2
009 N @SECLVLL 2

DEFAULT HELP MESSAGE/DEFINITION
FLD MESSAGE TEXT
--- ---------------------------------------------------------------------------
001 company/division code
002 ** NO FILE VARIABLE DICTIONARY ENTRY FOR THIS FIELD **
003 ** NO FILE VARIABLE DICTIONARY ENTRY FOR THIS FIELD **
004 category: (8 chars. max.) category to which the operator has access
005 ** NO FILE VARIABLE DICTIONARY ENTRY FOR THIS FIELD **
006 ** NO FILE VARIABLE DICTIONARY ENTRY FOR THIS FIELD **
007 ** NO FILE VARIABLE DICTIONARY ENTRY FOR THIS FIELD **
008 ** NO FILE VARIABLE DICTIONARY ENTRY FOR THIS FIELD **
009 ** NO FILE VARIABLE DICTIONARY ENTRY FOR THIS FIELD **

E N D O F D O C U M E N T A T I O N F O R F I L E SECURITY

Hope this helps

Steve

[George Macken]

Hi

Firstly, I dont use the Pro-IV Menus, we have our own menu application, so I cannot be 100% certain of the following ....

I believe the Files Used for the Pro-IV Menus are
MENU, MENUDEF, MENUSCR

Your request is to x-ref between security and functdef.
The Function has a security category and this category should be present on the SECURITY for the operator to be able access the function.

You could write a report that list
Function Name (only output function names that are accessible from a menu)
then list for each function the Operatory IDs that have this functions security category (only ouput the operator if this function is on a Menu that is accessilbe by this operator.

Another route to identify the funcions that the Operator has access to.
The Operator has an entry in the LOGONF file. On this file the field @LLNK is the function/menu that will execute once the operator has a successful logon. For example on MDC/SYS/SYS the @LLNK is set to @MAIN. Therefore the operator has access to the fuctions on this menu and its sub-menus AS LONG AS THE Operator also has the matching security category required for the function.

Hope this helps

Rgds

George