PI94973: DIFFICULTIES INSTALLING BIG SQL IN A CENTRALLY MANAGED ENVIRONMENT

APAR status

• Closed as program error.

Error description

• It can be difficult to install Big SQL on a tightly controlled
  environment; in particular, when there are specific
  requirements controlling user and group IDs, or security
  concerns, such as how to set up SSH.
  With this enhancement, users will be able to customize the Big
  SQL installation in the following ways:
  - Prevent the creation of the bigsql user and bigsql admin
  group - the user is responsible for creating them in advance
  - Customize the bigsql admin group name and ID
  - Prevent the setup of SSH for the bigsql user - the user is
  responsible for setting this up in advance
  - Prevent the modification of the /etc/service file, for the
  case where another mechanism is used to maintain services, such
  as LDAP
  To take advantage of these customizations, users will need to
  do the following:
  1. Create a batch script file bigsql-install.sh
  2. In the script, set any of the following variables:
  (i) BIGSQL_CREATE_USER
  - whether the Big SQL user & group should be set up
  - if not set, value defaults to 1 (yes)
  (ii) BIGSQL_SETUP_SSH
  - whether SSH should be set up for the Big SQL user
  - if not set, value defaults to 1 (yes)
  (iii) BIGSQL_ADD_SVC_ENTRIES
  - whether entries should be added to /etc/services
  - if not set, value defaults to 1 (yes)
  (iv) BIGSQL_ADMINGROUP_ID
  - the numeric id to use for the admin group
  - if not set, the value defaults to 43210
  (v) BIGSQL_ADMINGROUP_NAME
  - the name to use for the admin group
  - if not set, the value defaults to bigsqladm
  3. Copy this file to the /etc/profile.d directory on all hosts
  where Big SQL will be installed, primary and secondary heads
  and all workers. It is critical that the file exists on all
  hosts where Big SQL will be installed, and that the contents be
  the same on all hosts. Failure to comply with this requirement
  will result in a non-functional install.
  4. Proceed with the Big SQL install as usual
  

Local fix

Problem summary

• See error description
  

Problem conclusion

• The problem is fixed in Version 5.0.3 and later fix packs.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• UNKNOWN
  

Fix information

• Fixed component name

  IBM BIG SQL

• Fixed component ID

  5737E7400

Applicable component levels