Component Return Codes in EntireX

During startup, the broker detected a create error when invoking the z/OS Name/Token Services facility. The Broker is immediately shutdown.

Ensure that the z/OS Name/Token services facility is available on the version of the z/OS operating system that is running. Also, examine the operating system log. Correct the error and restart the broker. If the cause cannot be determined, contact Software AG support.

During broker startup an error has been detected attempting to open the data set referenced by the SYSPRINT DD statement. The attempted output from the echo of the broker startup parameters, the persistent store parameters, and the broker attribute file parameters to the data set referenced by the SYSPRINT DD statement failed.

Examine the SYSPRINT DD statement, the EntireX Broker log data set and the operating system log. Correct the error and restart the broker. If the cause cannot be determined, contact Software AG support.

During broker startup, at least one error has been detected in the persistent store component.

Examine the output referenced by the SYSPRINT DD statement as well as the broker log data set and the operating system log. Correct the error and restart the broker. If the cause cannot be determined, contact Software AG support.

During broker startup, at least one error was detected in the broker startup parameters.

Examine the output referenced by the SYSPRINT DD statement as well as the broker log data set and the operating system log. Correct the error and restart the broker. If the cause cannot be determined, contact Software AG support.

During broker startup, the broker persistent store parameters were not specified.

The broker persistent store parameters need to be specified in the input data set referenced by the SYSIN DD statement.

During broker startup, an error has been detected in the broker persistent store parameters.

Examine the output referenced by the SYSPRINT DD statement as well as the broker log data set and the operating system log. Correct the error and restart the broker. If the cause cannot be determined, contact Software AG support.

During broker startup, the broker detected a create error when invoking the z/OS Name/Token Services facility in the persistent store component. The broker is immediately shutdown.

Ensure that the z/OS Name/Token services facility is available on the version of the z/OS operating system that is running. Also, examine the operating system log. Correct the error and restart the broker. If the cause cannot be determined, contact Software AG support.

During startup, the broker detected an initialization error. The broker is immediately shutdown.

Examine the broker log data set and the operating system log as well as the output referenced by the SYSPRINT DD statement. Correct the error and restart the broker. If the cause cannot be determined, contact Software AG support.

During startup, the broker detected a storage error in the persistent store component. The broker is immediately shutdown.

Examine the output referenced by the SYSPRINT DD statement as well as the broker log data set and the operating system log. Increase the region size for the EntireX Broker job. Correct any errors and restart the broker. If the cause cannot be determined, contact Software AG support.

During shutdown, the broker detected a delete error when invoking the z/OS Name/Token Services facility. The broker is immediately shutdown.

Ensure that the z/OS Name/Token services facility is available on the version of the z/OS operating system that is running. Also, examine the operating system log. Correct the error and restart the broker. If the cause cannot be determined, contact Software AG support.

During startup, the broker detected that the load libraries are not all APF-authorized in z/OS.

Ensure that all the data sets referenced by the STEPLIB DD statement have been APF authorized in z/OS. Check the spelling of the data set names for accuracy. Correct any error and restart the broker. If the cause cannot be determined, contact Software AG support.

RPC server was successful.

Windows specific: one of the required shared libraries (.DLL) could not be found.

Minor Trouble - RPC server continues.

• At least 1 worker terminated unsuccessfully because of server (implemented by user and called by RPC server) malfunction.

• Parameters inconsistent - being repaired.

RPC server stopped.

• Not even 1 worker could be started.

• Stopped because EntireX Broker unavailable.

• Problems during shutdown processing.

Parameter Trouble - RPC server could not be started.

• Inconsistent parameters specified or not found.

• Usage error.

Serious Trouble.

• Problems with underlying operating system.

• Problems with EntireX RPC Runtime.