Previous PageTable Of ContentsNext Page

    Verify the SafeSFS Installation:


The following steps should be performed from a userid that was previously defined on a SAFADMIN record in the SAFESFS CONTROL file

Step 1: Logoff the SAFESFS server virtual machine.

Step 2: Issue the command SAFESFS INIT.
The SAFESFS INIT command will cause the SAFESFS server to be autologged and the SafeSFS product to be initialized.

Note: If you get an error message like:
SAFSFS304E CPI Communications error "CM_PRODUCT_SPECIFIC_ERROR"; Return Code: 20
This indicates that the communications directory (UCOMDIR/SCOMDIR) has not been updated correctly. The solution to this may be as simple as issuing SET COMDIR RELOAD, or as complicated as needing to update the appropriate file and issue the SET COMDIR command. You may also need to add an IUCV ALLOW record to the SAFESFS CP directory entry. If you continue to get errors please contact Safe Software technical support for assistance.

Step 3: Issue the command SAFESFS version.
You should see a response similar to the following:
SAFESFS EXEC Version: 1.2.00
SAFESERV EXEC Version: 1.2.00
SAFESYS MODULE Version: 1.2.00

Step 4: Add rules to the GLOBAL ADMIN rules file
Issue the SafeSFS commands listed below to add rules to the GLOBAL ADMIN rule file:
SAFESFS ADD ADMIN ACCEPT USER userid READ *:fspace.
SAFESFS ADD ADMIN DENY USER MAINT READ *:SECRET.

Step 5: Issue the command SAFESFS GETRULES GLOBAL ADMIN
This will place you into the SafeSFS fullscreen panel, allowing you to manipulate the GLOBAL ADMIN rules. You may try adding, deleting, updating, and modeling rules.

Step 6: Issue the command SAFESFS GETRULES GLOBAL ADMIN ( EDIT
This will place you into the GLOBAL ADMIN rules file in XEDIT. You may make any changes you want. When you file it, the rules will be updated.

Step 7: Verify the SafeSFS SFS ESM Exit installation.
Issue the CMS command QUERY AUTHORITY dirid. Where Dirid is a valid directory in your SFS file pool, for example, QUERY AUTHORITY TFP:JOHN.. You should see a P under the R, W, NR, and NW headers. This indicates that an external security manager is controlling the object.

Step 8: Verify the SafeSFS HTML Documentation. (Optional)
Use your web browser to view the SafeSFS HTML Documentation to make sure it is accessible and displays the documentation properly.

Previous PageTable Of ContentsNext Page