Frequently Asked Questions

This issue only applies to Portus running on Linux, AIX or Solaris. If your license does not have any Adabas or Natural drivers enabled, this issue does not apply.

If the sagenv file is not available during the Portus install, Adabas or Natural drivers may not work correctly until this file is made available. For example, you have installed Portus before installing Adabas.

Follow these steps to enable a new sagenv file in an existing Portus installation.

1. Edit [INSTALL_HOME]/xmiddleEnv.sh

2. Append the following to the end of this file (assuming sagenv file is /opt/softwareAg/sagenv.new) :

   if test -e "/opt/softwareAg/sagenv.new"; then
   source /opt/softwareAg/sagenv.new &> /dev/null
   fi

3. Save and close this file.
4. Stop and then Start the Portus server. See here for more information.
5. Modify [INSTALL_HOME]/apache2/conf/adabas_soa_gw.conf and change the User directive to use the "sag" user.

6. Change the file permissions of Portus files and directories

   chown -R sag [INSTALL_HOME]

7. Review the error_log for errors/warnings.
8. Adabas or Natural drivers should now be added successfully. See here for more info.

During the FTP of Portus to z/OS, the machine identifier will be set to the hostnam or IP address of the FTP server.

This text will be displayed on messages appearing in the JESMSGLG.

To change this, modify the SYSPARM member of the CONF dataset and set this as required. It is recommended that this is set to the hostname or IP address of the z/OS machine.