Variables not resolved after upgrade

After performing an upgrade, global variables are not resolved.

Cause and solution:

During the upgrade, all the security file statements relating to your global variables were copied by the installation wizard into a default variable table in the new security file. Global variables are disabled and can only be used through the variable tables. If you subsequently rebuilt the security file using the output from your previous dumpsec as input to the new makesec, you will have overwritten the security statements relating to your default variable table, so no user has access to the default variable table.

If you have a backup of your security file from prior to when you ran makesec, run dumpsec from that, and merge your old dumpsec output file with your new one, as described in the upgrade procedure in the IBM Workload Scheduler: Planning and Installation.

If you do not have a backup, create the default variable table security statement, following the instructions about configuring the security file in the IBM Workload Scheduler: Administration Guide.