AWSBIS - Customize messages

This section lists error and warning messages that might be issued by the customize component.

The message component code is BIS.

AWSBIS002E

An internal error has occurred. Customize failed to run the following UNIX command during the installation: "command" Correct the problem and rerun customize.

The command can be any of the following:

  • chgrp
  • chmod
  • chown
  • filepriv (UnixWare only)
  • mkdir
  • mv
  • rm

Customize issues this message in any of the following circumstances:

  • It is unable to set permissions, ownership or group of the HCL Workload Automation files.
  • It could not create one or more directories.
  • It could not delete or rename one or more files.

Customize stops. The installation is not completed.

Determine why the system command specified in command failed and rerun customize.

Capturing the output from the customize command will help you to determine the error. Do the following:

  1. Run this command: script -a <file_name> where <file_name> is the fully qualified path and file name of the file where you want to capture the customize output (for example, /tmp/custOut.txt).
  2. Re-issue the customize command with all the arguments used before.
  3. When customize fails, issue the exit command to close the output file.
  4. Open the file and read the output from customize.

AWSBIS003E

The following HCL Workload Automation configuration file does not exist: "file_name".

Customize is attempting to customize a HCL Workload Automation configuration file, but the file does not exist in the <TWS_home>/config directory.

A possible reason is that the HCL Workload Automation tar file was corrupted while being copied to the workstation, or an error occurred during the unpacking of the file.

file_name can be any of the following:

  • jobmanrc
  • JnextPlan
  • loadbal
  • localopts
  • NetConf
  • ntmulti
  • ntsingle
  • Security
  • Sfinal
  • StartUp
  • unixlocl
  • unixrsh
  • unixrsh.wrp

These files must all be in the <TWS_home>/config directory before running customize.

Customize stops. The installation is not completed.

Check that all the configuration files listed above exist in the <TWS_home>/config directory, and are legible. If any files are missing or corrupted, delete the <TWS_home> directory and all its contents and restart the installation process described in the Planning and Installation Guide.

The Planning and Installation Guide for details of the installation process.

AWSBIS009E

Customize could not create a symbolic link to the following program: "program".

Customize could not create a symbolic link for one or more of the following HCL Workload Automation programs from the directory: <TWS_home>/bin to the directory: <TWS_home>/../bin:

  • datecalc
  • jobstdl
  • maestro
  • mat
  • mbatch
  • morestdl
  • parms

program is one or more of the programs listed above.

Customize stops. The installation has completed some steps but HCL Workload Automation is not usable.

Determine the reason why customize could not create a symbolic link, using the tools of the operating system.

When you have resolved the problem, delete all files in the product directory and restart the installation.

AWSBIS010E

Customize could not create a symbolic link to the following program, because a link already exists: "program".

Customize could not create a symbolic link for one or more of the following HCL Workload Automation programs from the directory: <TWS_home>/bin to the directory: <TWS_home>/../bin:

  • datecalc
  • jobstdl
  • maestro
  • mat
  • mbatch
  • morestdl
  • parms

program is one or more of the programs listed above.

This probably indicates that links made for a previous version of HCL Workload Automation were not deleted when the old version was uninstalled or upgraded.

Customize stops. The installation has completed some steps, but HCL Workload Automation is not usable.

Use the following procedure:

  1. Use operating system tools to determine which links exist.
  2. Use the following commands to remove the existing links:rm <TWS_home>/usr/bin/matrm <TWS_home>/usr/bin/mbatchrm <TWS_home>/usr/bin/datecalcrm <TWS_home>/usr/bin/maestrorm <TWS_home>/usr/bin/morestdlrm <TWS_home>/usr/bin/jobstdlrm <TWS_home>/usr/bin/parms
  3. Delete all files in the product directory.
  4. Restart the installation.

AWSBIS012W

User %s not found in /etc/passwd. Trying Yellow Pages.

AWSBIS013E

The user ID cannot be found in /etc/passwd and Yellow Pages (NIS). Either it is not installed or it is not accessible from the PATH system variable.

The Yellow Pages is a centralized database of files including the passwd, group, and other system files. In a networked environment, these files are centralized on a NIS server which makes them available to all the machines on the network, for ease of maintenance. Users can also have the same password across the network.

Customize could not find the HCL Workload Automation user's login ID in the file /etc/passwd. It then tried to look up the user ID in Yellow Pages, but Yellow Pages was not installed or accessible on the system.

The user ID must be in either /etc/passwd or Yellow Pages.

Customize stops. The installation is not completed.

Define the HCL Workload Automation user in the /etc/passwd file, or in Yellow Pages.

If it is defined in Yellow Pages, ensure that the directory where the Yellow Pages executable program is stored is included in the PATH system variable.

Rerun customize.

AWSBIS014E

The following user ID cannot be found in either /etc/passwd or the Yellow Pages: "user_name".

The Yellow Pages is a centralized database of files including the passwd, group, and other system files. In a networked environment, these files are centralized on a NIS server which makes them available to all the machines on the network, for ease of maintenance. Users can have the same password across the network.

Customize could not find the HCL Workload Automation user's login ID either in the file /etc/passwd or in the Yellow Pages.

The user ID must be in either /etc/passwd or Yellow Pages.

Customize stops. The installation is not completed.

Define the HCL Workload Automation user in the /etc/passwd file, or in Yellow Pages.

AWSBIS015E

The user running customize is not logged in as root.

See message text.

Customize cannot start.

Log off and log in again as root and run customize again.

AWSBIS016E

Customize cannot use the chown command.

The chown command was either not found following the PATH environment variable or /etc/chown did not have execute permission.

Customize stops. The installation is not completed.

Determine what has caused the error and either add the directory that contains the chown command to the PATH environment variable or ensure that the user running customize has execute permission for the command.

Rerun customize.

AWSBIS017E

The following user ID, for which you want to install HCL Workload Automation, does not exist or does not belong to any group: "user_name".

user_name is the missing user ID.

Customize stops. The installation is not completed.

Verify that the intended HCL Workload Automation user ID has been added to the /etc/passwdfile, and the /etc/group or to their equivalents in Yellow Pages (NIS).

Verify that the groups command runs correctly on the intended HCL Workload Automation user ID.

Rerun customize.

AWSBIS020E

The supplied HCL Workload Automation home directory does not exist.

Either you have supplied the wrong directory to Customize, or you have not created the directory.

Customize stops. The installation is not completed.

Depending on the reason for the error, either rerun Customize, specifying the correct directory, or create the HCL Workload Automation home directory and extract the tar file into it before rerunning Customize.

AWSBIS021E

An error occurred running one of the commands required for the installation.Determine which command had failed by examining the error messages issued previous to this one. Correct the problem and resubmit the command.

See message text.

Customize stops. The installation is not completed.

Determine which command failed by examining the error messages issued previous to this one. Correct the problem and resubmit the command.

AWSBIS023E

Unable to install %s properly.

AWSBIS024E

Customize has been launched with the '-m <module_name> option incorrectly specified more than once.

See message text.

Customize does not start.

Rerun Customize, supplying the -m <module_name> option only once.

The Planning and Installation Guide for details of the syntax of customize.

AWSBIS025E

Customize has been issued with the following incorrect option: "option".

See message text.

option is the name of the incorrect option.

Customize does not start.

Run customize -U to see the valid command line options, or see the Planning and Installation Guide.

The Planning and Installation Guide for details of the syntax of customize.

AWSBIS026E

The HCL Workload Automation home directory does not exist.

Either you have supplied the wrong directory to Customize, or you have not created the directory.

Customize stops. The installation is not completed.

Depending on the reason for the error, either rerun Customize, specifying the correct directory, or create the HCL Workload Automation home directory and extract the tar file into it before rerunning Customize.

AWSBIS033E

An error occurred while trying to extract HCL Workload Automation from the following tar file: "tar_file_name".

The problem might be caused by the file not being present or because of lack of disk space to unpack it.

tar_file_name is the name of the tar file.

Customize stops. The installation is not completed.

Check that the file exists at the location you specified and that there is sufficient disk space available to extract it in the file set where you want to install HCL Workload Automation. If there is insufficient space, create some and rerun customize, or rerun customize, changing the options to install HCL Workload Automation in a different file set with sufficient space.

AWSBIS034E

Customize encountered an error while installing HCL Workload Automation. Determine the details of the error by examining the error messages issued previous to this one. Correct the problem and rerun customize.

See message.

Customize stops. The installation is not completed.

Determine the details of the error by examining the error messages issued previous to this one. Correct the problem and rerun customize.

AWSBIS035E

Tar file %s.Z not found. Continuing with installation...

AWSBIS038E

Customize script for module %s could not be found. exiting ...

AWSBIS042E

Customize failed to decompress the following tar file: "tar_file_name".

The problem might be caused by the file not being present or because of lack of disk space to decompress it.

tar_file_name is the name of the tar file.

Customize stops. The installation is not completed.

Check that the file exists at the location you specified and that there is sufficient disk space available to decompress it in the file set where you want to install HCL Workload Automation. If there is insufficient space, create some and rerun customize, or rerun customize, changing the options to install HCL Workload Automation in a different file set with sufficient space.

AWSBIS044E

There is a syntax error in the customize options: -noexp should be specified only with a -new install

You specified the -noexp option when updating an installation. The -noexp option can only be specified with the -new option when running a new installation of HCL Workload Automation.

Customize stops. The installation is not completed.

If this is an update, rerun customize without the -noexp option.

The Planning and Installation Guide for details of the syntax of customize.

AWSBIS045E

There is a syntax error in the customize options: the -uname option is not followed by a user ID, or the supplied user ID commences with a hyphen.

A user ID must be supplied with the -uname option. If the user ID that you tried to use commences with a hyphen -, chose a different user ID that does not commence with a hyphen, or should change the user ID so that it does not commence with a hyphen.

Customize stops. The installation is not completed.

Rerun customize, specifying a valid user ID after the -uname option, that does not commence with a hyphen.

The Planning and Installation Guide for details of the syntax of customize.

AWSBIS046E

There is a syntax error in the customize options: either the -update and -new options have both been specified, or one of them has been specified more than once.

See message.

Customize stops. The installation is not completed.

Rerun customize specifying either the -new or the -update option only once.

The Planning and Installation Guide for details of the syntax of customize.

AWSBIS047E

There is a syntax error in the customize options: the -thiscpu option cannot be used with the -update option.

You specified the -thiscpu option with the -update option. The -thiscpu option can only be used during a new installation (with the -new option) to specify the name of the HCL Workload Automation workstation for that installation.

Customize stops. The installation is not completed.

If you are updating an installation, rerun customize without the -thiscpu option.

If you are running a fresh installation, specify the -new option, without the -thiscpu option.

The Planning and Installation Guide for details of the syntax of customize.

AWSBIS048E

There is a syntax error in the customize options: the -thiscpu option is not followed by a workstation name, or the supplied workstation name commences with a hyphen.

A workstation name must be supplied with the -thiscpu option. If the workstation name that you tried to use commences with a hyphen -, chose a different workstation name that does not commence with a hyphen, or should change the workstation name so that it does not commence with a hyphen.

Customize stops. The installation is not completed.

Rerun customize, specifying a valid workstation name after the -thiscpu option, that does not commence with a hyphen.

The Planning and Installation Guide for details of the syntax of customize.

AWSBIS049E

There is a syntax error in the customize options: the -master <workstation_name> option can only be specified with -new option.

You specified the -master <workstation_name> option (which identifies to which master domain manager you want the workstation where you are conducting the installation to belong) while running an update installation (with the -update option).

Customize stops. The installation is not completed.

If you are updating an installation, rerun customize without the -master <workstation_name> option.

If you are updating an installation, and you want at the same time to change the master domain manager for this workstation, you must first upgrade the installation, and then change the master domain manager.

If you intended to run a fresh installation, specify the -new option, with the -master <workstation_name> option.

The Planning and Installation Guide for details of the syntax of customize.

AWSBIS050E

There is a syntax error in the customize options: you are running a fresh installation (with the -new option) but have not supplied either the -master <workstation_name> option or the -thiscpu <workstation_name> option, which are both mandatory for a fresh installation.

See message.

Customize stops. The installation is not completed.

If you intended to update an existing installation, you must rerun customize using the -update option, but without the -master or the -thiscpu options.

If you intended to run a fresh installation, specify the -new option with the -master <workstation_name> and -thiscpu <workstation_name> options.

The Planning and Installation Guide for details of the syntax of customize.

AWSBIS051E

There is a syntax error in the customize options: the -master option is not followed by a workstation name, or the supplied workstation name commences with a hyphen.

A workstation name must be supplied with the -master option. If the workstation name that you tried to use commences with a hyphen -, chose a different workstation name that does not commence with a hyphen, or should change the workstation name so that it does not commence with a hyphen.

Customize stops. The installation is not completed.

Rerun customize, specifying a valid workstation name after the -master option, that does not commence with a hyphen.

The Planning and Installation Guide for details of the syntax of customize.

AWSBIS052E

There is a syntax error in the customize options: the -netman option is not followed by a directory name, or the supplied directory name commences with a hyphen.

A directory name must be supplied with the -netman option. If the directory name that you tried to use commences with a hyphen -, chose a different directory name that does not commence with a hyphen, or should change the directory name so that it does not commence with a hyphen.

Customize stops. The installation is not completed.

Rerun customize, specifying a valid directory name after the -netman option, that does not commence with a hyphen.

The Planning and Installation Guide for details of the syntax of customize.

AWSBIS053E

The following supplied netman home directory cannot be found or is not a directory: "netman_home_directory".

AWSBIS054E

There is a syntax error in the customize options: the -company option is not followed by a company name, or the supplied company name commences with a hyphen.

A company name must be supplied with the -company option. If the company name that you tried to use commences with a hyphen -, chose a different company name that does not commence with a hyphen, or should change the company name so that it does not commence with a hyphen.

Customize stops. The installation is not completed.

Rerun customize, specifying a valid company name after the -company option, that does not commence with a hyphen.

The Planning and Installation Guide for details of the syntax of customize.

AWSBIS055E

There is a syntax error in the customize options: the -execpath option is not followed by a path name, or the supplied path name commences with a hyphen.

A path name must be supplied with the -execpath option. If the path name that you tried to use commences with a hyphen -, chose a different path name that does not commence with a hyphen, or should change the path name so that it does not commence with a hyphen.

Customize stops. The installation is not completed.

Rerun customize, specifying a valid path name after the -execpath option, that does not commence with a hyphen.

The Planning and Installation Guide for details of the syntax of customize.

AWSBIS056E

Error: Invalid option, specify -m <module-name>

AWSBIS057E

Error: Invalid option, specify -group <install-group>

AWSBIS058E

There is a syntax error in the customize options: you are running a fresh installation (with the -new option) but have not supplied either the -master <workstation_name> option or the -thiscpu <workstation_name> option, which are both mandatory for a fresh installation.

See message.

Customize stops. The installation is not completed.

If you intended to update an existing installation, you must rerun customize using the -update option, but without the -master or the -thiscpu options.

If you intended to run a fresh installation, specify the -new option with the -master <workstation_name> and -thiscpu <workstation_name> options.

The Planning and Installation Guide for details of the syntax of customize.

AWSBIS059E

Customize failed to decompress the following tar file: "tar_file_name".

The problem might be caused by the file not being present or because of lack of disk space to decompress it.

tar_file_name is the name of the tar file.

Customize stops. The installation is not completed.

Check that the file exists at the location you specified and that there is sufficient disk space available to decompress it in the file set where you want to install HCL Workload Automation. If there is insufficient space, create some and rerun customize, or rerun customize, changing the options to install HCL Workload Automation in a different file set with sufficient space.

AWSBIS060E

The following components directory identified in the UNISON_COMPONENT_FILE variable is not a directory, or does not exist: "directory_name".

Customize found that the UNISON_COMPONENT_FILE variable is set, but that the path name it contains is incorrect, because the directory component of the pathname is not a directory or does not exist.

directory_name is the name of the directory that is incorrect or does not exist.

Customize stops. The installation is not completed.

Set the UNISON_COMPONENT_FILE variable correctly, and export it, and then rerun customize. Alternatively, delete the variable and rerun customize, which will use the default value documented in the Planning and Installation Guide .

The Planning and Installation Guide for details of how to use customize.

AWSBIS061W

No component group name was provided. Using the following default group name: %s.

AWSBIS062E

An entry was found in the components file for the specified group, but it contained incorrect data.

See message.

Customize stops. The installation is not completed.

Check the entry in the components file under the specified group, and verify that it is correct. Rerun customize.

AWSBIS063E

More than one entry was found in the components file either for the following specified location: "directory_name" or the following group: "group_name".

See message.

directory_name is the name of the HCL Workload Automation home directory that has more than one entry in the file. group_name is the name of the group that has more that one entry in the file.

Customize stops. The installation is not completed.

Check the HCL Workload Automation entries in the components file, and ensure that the locations and groups are not repeated.

AWSBIS064W

HCL Workload Automation is installed under a different component group %s.Changing the component group name to be %s.

AWSBIS065W

You are trying to install HCL Workload Automation in the following location: "directory_name" under the following group: "group_name". However, there is already an instance installed in that location and group.

See message.

directory_name is the name of the directory that already holds a HCL Workload Automation installation. group_name is the name of the group under which a HCL Workload Automation installation already exists.

Customize stops. The installation is not completed.

Rerun customize, selecting a different location or a different group for the HCL Workload Automation installation, or both.

AWSBIS066E

HCL Workload Automation is already installed in %s. You can only update this installation.

AWSBIS067E

There is more than one entry for Netman in the same group.

AWSBIS068W

Netman is already installed in this group %s at location %s.

AWSBIS070E

The netman directory was not found. Copy the netman directory and run customize again

AWSBIS071E

Netman customize failed during execution. Correct the problem and run again.

AWSBIS072E

An error occurred while creating or updating the components file.

After HCL Workload Automation is installed successfully, customize runs the ucomp program to update the components file with the location and group of the HCL Workload Automation installation. If the components file does not exist, customize creates it. This message indicates that customize encountered an error during this process while creating or updating the components file. It could be a problem with file space or access permissions.

Check the file system of the <TWS_home> directory to ensure that there is sufficient space, and that the user has write permission. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBIS201E

Calendar %s already exists

AWSBIS202E

Calendar type is required.

AWSBIS203E

Unable to find home directory for TWS user

AWSBIS204E

Unable to read calendars from database

AWSBIS205E

Type %s calendars require the use of the TWS datecalc utility.

AWSBIS206E

Type %s calendars require a HOLIDAYS calendar to be predefined.

AWSBIS207E

Type %s calendars require a -s parameter.

AWSBIS208E

Your HCL Workload Automation license has expired.

AWSBIS235E

Day %s is not in range 1-31.

AWSBIS236E

Argument %s must be greater than zero.

AWSBIS237E

Argument %s is not in range 1-3.

AWSBIS238E

Incorrect option %s.

AWSBIS239E

One or more errors occurred. Calendars database not modified. See below.

AWSBIS240E

Failed to add new calendar to the database.

AWSBIS242W

New production period takes effect now. Waiting 20 seconds.

AWSBIS257E

No argument was supplied with -d.

AWSBIS258E

No argument was supplied with -i.

AWSBIS259E

No argument was supplied with -f.

AWSBIS260E

No argument was supplied with -p.

AWSBIS261E

No argument was supplied with -s.

AWSBIS262E

No argument was supplied with -r.

AWSBIS263E

No argument was supplied with -w.

AWSBIS264E

Calendars of type %s require the %s non-working days (freedays) calendar to be predefined.

AWSBIS273E

More than one calendar option has been specified.Rerun the command, selecting only one option from (-d|-e|-f|-l|-m|-p|-r|-w).

AWSBIS274E

Environment variable TEMP is not set.Set a valid value for TEMP and rerun the command.

AWSBIS275E

No argument was supplied with -freedays. Specify a valid calendar name.

AWSBIS276E

Cannot understand the NLS/Unknown format. Exiting.

AWSBIS277E

The non-working days (freedays) calendar %s is not found in the Symphony file. Run JnextPlan to make it available.

AWSBIS278E

There is a syntax error in the command. See the User's Guide and Reference for the correct syntax.

AWSBIS279E

Cannot determine the remote shell program.

AWSBIS280E

Cannot connect to %s.

AWSBIS281E

There is a syntax error in the command.See the User's Guide and Reference for the correct syntax.

AWSBIS283E

Cannot determine the remote shell program.

AWSBIS286E

There is a syntax error in the command. See the User's Guide and Reference for the correct syntax.

AWSBIS287E

Cannot connect to %s

AWSBIS288E

There is a syntax error in the command. See the User's Guide and Reference for the correct syntax.

AWSBIS290E

No files were found in the file set.

AWSBIS291E

Jobstdl failed running: %s.

AWSBIS299E

No argument was supplied with -day.

AWSBIS300E

No argument was supplied with -name.

AWSBIS301E

No argument was supplied with -num.

AWSBIS303E

There is a syntax error in the command. See the User's Guide and Reference for the correct syntax.

AWSBIS310E

at: You are not authorized to use the at command.

AWSBIS311E

batch: You are not authorized to use the batch command.

AWSBIS319E

rep8 was not found.

AWSBIS320E

The command failed while running %s.

AWSBIS326E

No stdlist directory was found.

AWSBIS329E

No netman stdlist was found in %s.

AWSBIS332E

No manual entry was found for %s.

AWSBIS335E

JnextPlan failed while running: %s.

AWSBIS338E

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBIS339E

File %s does not exist.

AWSBIS340E

There is a syntax error in the command. See the User's Guide and Reference for the correct syntax.

AWSBIS345E

An internal error has occurred. ResetPlan failed while running: %s.

AWSBIS346W

No Symphony file was found.

AWSBIS348E

An internal error has occurred. MakePlan failed while running: %s.

AWSBIS349E

An internal error has occurred. SwitchPlan failed while running: %s.

AWSBIS350W

The application server is not running.

The application server must be running for you to run JnextPlan.

The script CheckPrerequisites stops. You cannot run JnextPlan.

To start the application server, rerun CheckPrerequisites adding the option -start.

AWSBIS358E

JnextPlan was canceled by user.

AWSBIS502E

at: You are not authorized to use the at command.

See message.

The operation is not performed.

Contact the HCL Workload Automation administrator to obtain the required authorization.