Operator Interface Errors

Operator interface errors occur while you are using the operator interface to issue commands to IBM® Connect:Direct®. You can find more information on the operator interface in the IBM Sterling Connect:Direct for z/OS® Facilities Guide.

This section lists possible operator interface errors, error messages, possible causes, actions to take, and data to collect to troubleshoot an error.

Task Busy Message

Use the following table to troubleshoot the problem when you receive a Task Busy message after issuing an Operator Interface command.

Error Cause Action Collect
IEE342I Modify rejected - task busy An error in the MCS.SIGNON parameter in the IBM Connect:Direct initialization parameters. Ensure that the MCS.SIGNON parameter reflects a valid userid-password combination with IBM Connect:Direct operator authority. Remove comments from this parameter.
  • IBM Connect:Direct initialization parameters
  • SYSLOG output

User Not Authorized Messages

Use the following table to troubleshoot authorization errors you receive when you issue operator interface commands.

Error Messages
SCBB001I SCBC030I SCBD001I SCBE001I SCBF001I SCBF063I
SCBF064I SCBG001I SCBH001I SCBI001I SCBJ001I SCBK005I
SCBL001I SCBN001I SCBO001I SCBP001I SCBR002I SCBS001I
SCBT005I SCBU003I SCBV001I SCBW001I SCBX001I SCBY001I
SCPA008I SFIA002I SFIA003I SRJA014I SRTA008I SSUB100I
Cause Action Collect
The userid attempting to issue the operator interface commands is not authorized to issue them. Review both the short text and long text messages. Check the userid specified in the MCS.SIGNON parameter of the IBM Connect:Direct initialization parameters file. Determine whether that userid has the authority to issue the command. If you believe it does, run a security trace to determine why the user cannot issue the command.

See Security Traces for information on how to run the trace.

  • IBM Connect:Direct initialization parameters
  • Security trace