AWSBCU - SSL messages (symaccs)

This section lists symaccs error and warning messages that might be issued when using SSL.

The message component code is BCU.

AWSBCU001E

Opening "Variable", error: "Error"

AWSBCU002E

Locking "Variable", error: "Error"

AWSBCU003E

Unable to allocate comarea "Comarea"

AWSBCU004E

Could not set file options on "Variable", error "Error"

AWSBCU005E

Closing "Variable", error: "Error"

AWSBCU006E

Purging "Variable", error: "Error"

AWSBCU007E

An error has occurred in the common area used to access the Symphony file.

The error is probably due to a memory corruption. It is a symaccs error.

The program might stop.

If HCL Workload Automation has not yet stopped, stop and restart it. If the error occurs again search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

The chapter in this guide on 'Symphony file corruption'.

AWSBCU008E

Seeking "Variable", record "Record" ("Record2"), error: "Error"

AWSBCU009E

Reading "Variable", record "Record" ("Record2"), error: "Error"

AWSBCU010E

Writing "Variable", record "Record" ("Record2"), error: "Error"

AWSBCU011E

Trying to read a nonexistent record from "Variable", Record "Record" ("Record2").

AWSBCU012E

Write called without update access on "Variable"

AWSBCU013E

Obtaining statistics on "Variable", error: "Error"

AWSBCU014E

End of file on "Variable", record "Record" ("Record2").

AWSBCU015E

Error comarea isn't a symaccs comarea

AWSBCU016E

No write access to "Variable", record "Record" ("Record2").

AWSBCU017E

Attempting to write NIL ("Variable") record to "Record".

AWSBCU018E

Write recnum disagreement on "Variable", recnum "RecNum" ("RecNum2").

AWSBCU021E

Attempting to write past absolute limit on "Variable", record "Record" ("Record2").

AWSBCU022E

No statistics available for record type, for "Variable2", on "Variable".

AWSBCU023W

Stats only kept on production transactions, not for "Variable"

AWSBCU024E

Procedure not implemented.

AWSBCU025E

Lock called and "Object" already locked, record "Record" ("Record2"), error: "Error"

AWSBCU026E

Unknown lock flag for lock on "Object", record "Record" ("Record2"), error: "Error"

AWSBCU027W

Unlock called for "Object", record "Record" ("Record2"), file not locked.

AWSBCU028E

Call to LOCK failed for "Object", record "Record" ("Record2"), error: "Error"

AWSBCU029E

Call to GETLOCK failed for "Object", record "Record" ("Record2"), error: "Error"

AWSBCU030E

Call to RENAME failed on "Object", error: "Error"

AWSBCU031E

Exclusive access needed to install "Object" as Symphony.

AWSBCU032E

File "File" already locked by another process, error: "Error"

AWSBCU035E

Opening "Object", error: "Error"

AWSBCU036E

Seeking "File", record type "RecordType", error: Record not found

AWSBCU037W

Filename "FileName" exceeds "Limit" byte limit, Warning: Filename truncated.

AWSBCU038E

Filepath "FilePath" exceeds "Limit" byte limit. Filepath unusable.

AWSBCU040E

%s:%d sym_e_2_i() unexpected Symphony record type: 0%o

AWSBCU041E

%s:%d sym_i_2_e() unexpected Symphony record type: 0%o

AWSBCU042W

OPENS dependency resolution could fail at runtime because of the syntax used. Action must be taken.

AWSBCU150W

SSL authorization is required to connect to the following workstation "workstation_name"

See message. The most common reason for this error is an inconsistent Security Level. For example, the workstation where mailman is running could be enabled for SSL but the target workstation is not. workstation_name is the name of the workstation you cannot connect to.

The program proceeds to process other workstations.

Use composer or the Job Scheduling Console to verify the security level of the Workstation that cannot communicate. Enable or disable SSL as appropriate and where appropriate, to ensure that both this workstation and the target workstation have compatible SSL settings.

See the chapter on setting security in the Planning and Installation Guide for more information about SSL.