Frequently Asked Questions for ZFS

Q: How do I execute server user profiles from a PDS?

A: We recommended that you copy the server user profiles from the PDS to the ZFS directory /ibi/profiles, and rename them to add the extension .prf (for example, user_id.prf). Alternatively, you can use the following technique to execute user profiles from a PDS:

  1. In the IRUNJCL member, allocate DDNAME //MVSPROF to the PDS containing user profiles.

    For example:

    //MVSPROF DD DISP=SHR,DSN=high_level_qualifier.EDAPROF.DATA
  2. Add the highlighted lines to the global server profile, edasprof.prf:
    APP MAP MVSPROF fex=//dd:mvsprof  

APP MAP MVSAPP mas=//dd:master;fex=//dd:focexec;acx=//dd:access; 

... 

APP PATH IBISAMP MVSAPP  

-SET &USERID='12345678';

-SET &USERID=GETUSER(&USERID); 

EX MVSPROF/&USERID

Q: What permissions are specified for application component files?

A: Application component files, such as FOCEXEC procedures (.FEX), Master Files (.MAS), and Access Files (.ACX), reside in the /ibi/apps/applicationname directory, where they are created with a permission of 666 minus the UMASK setting.

For example, if the UMASK value is 022, each application component is created with a permission of 644.

Caution: When using the above UMASK values, if one user ID creates application components, all other users will be able to read them, but not to write, update, or refresh.

You can provide write access by changing the value of UMASK at installation time, or manually in IRUNJCL. For example:

//TSCOM300  EXEC PGM=TSCOM300,

//          PARM='ENVAR("_EDC_UMASK_DFLT=0022")/'

//STEPLIB   DD DISP=SHR,DSN=EDABXV.SRV93.HOME.LOAD

Q: Can I monitor server startup by checking the MVS SYSLOG?

A: Yes.

The following messages are written to the SYSLOG when

  • The Server starts successfully:
    (EDA13023) ALL INITIAL SERVERS STARTED
  • The Server does not start:
    (EDA13171) UNABLE TO START IWAY SERVER