Previous Topic: CA IDMS/DC Messages DC021001 - DC028006Next Topic: CA IDMS/DC Messages DC040101 - DC048008


CA IDMS/DC Messages DC030001 - DC035006

DC030001

TASK: <task-code>; SETIME FAILED ── NO RCE AVAILABLE

Reason:

No RCEs were available to satisfy the request. A possible cause is that a program either is looping while acquiring resources or is failing to free resources. Check for an error in program logic. Alternatively, the system may be using more resources than expected. In this case, increase the RCE count specified in the SYSTEM statement of the SYSGEN.

Module:

RHDCTIMP

Severity:

3

DC030002

SETIME FAILED - START-TASK CODE <task-code> NOT FOUND

Reason:

The named task could not be found in the Task Definition Table (TDT). The module RHDCTIMP was called to initiate a time-requested event (in this case, to start a task), but because the task code could not be found, the time-requested event failed. The probable cause of this error is that the task code either has been misspelled or has not been defined in the SYSGEN.

Module:

RHDCTIMP

Severity:

0

DC030003

SETIME FAILED - START-TASK CODE <task-code> OUT OF SERVICE

Reason:

The named task is out of service. The module RHDCTIMP was called to initiate a time-requested event (in this case, to start a task), but because the task was out of service, the time-requested event failed. Determine why the task is out of service and, if appropriate, enable the task by means of the DCMT VARY TASK command.

Module:

RHDCTIMP

Severity:

0

DC030004

SETIME FAILED - SECURITY VIOLATION ON START-TASK CODE <task-code>

Reason:

The signed-on user is not authorized to execute the named task. The module RHDCTIMP was called to initiate a time-requested event (in this case, to start a task), but because the signed-on user is not authorized to execute the task, the time-requested event failed. See the system administrator to obtain authority to access the named task.

Module:

RHDCTIMP

Severity:

0

DC030005

DC030004 SETIME FAILED - Signon Failure: Task code <task-code>, UserID was <userid>

Reason:

A timer initiated task has failed during SIGNON processing. When processing SETIME START-TASK requests, the USERID is saved. When the designated task is started, RHDCTIMP attempts to SIGNON that USERID. The SIGNON request has failed possibly because the USERID is no longer valid. The task is abended.

Module:

RHDCTIMP

Severity:

3

DC030006

SETIME FAILED - Security Failure: Task code was <task-code>, UserID was <userid>

Reason:

A timer initiated task has failed during SECHECK processing. When processing SETIME START-TASK requests, the USERID is saved. When the designated task is started, RHDCTIMP SECHECKs the USERID against the requested Task Code. The SECHECK has failed possibly because the USERID was not authorized to execute that task. The task is ABENDed.

Module:

RHDCTIMP

Severity:

3

DC030007

SETIME FAILED - #GETLTE Failed: Task code <task-code>, UserID was <userid>

Reason:

A timer initiated task has failed during #GETLTE processing. When initiating a Timer Initiated Task RHDCTIMP performs a #GETLTE to acquire a dynamic LTE which is used as the security and profile anchor. The #GETLTE has failed possibly because storage was not available for the LTE. The task is ABENDed.

Module:

RHDCTIMP

Severity:

3

DC030011

TASK: <task-code>; DTS request failed: <dts-request> - <dts-return-code>

Reason:

An error occurred during the processing of a DTS request issued by a client/server interface. Check for a back-end server failure or problems with a communication link.

Module:

IDMSxCLI, IDMSxSRV

Severity:

5

DC030012

TASK: <task-code>; Invalid IDMS service type or function

Reason:

A request was made from a remote client to perform an IDMS service; however, the service being requested, as identified by the DSICB service type, is unknown. Most probably due to storage being overlaid.

Module:

IDMSxSRV

Severity:

3

DC030013

TASK: <task-code>; Invalid IDMS service request

Reason:

A request was made to perform an IDMS service; however, the first parameter was not a DSICB. Most probably due to storage being overlaid.

Module:

IDMSxSRV

Severity:

3

DC035001

TASK: <task-code>; INVALID TASK CODE SPECIFIED ON ATTACH REQUEST - <requested-task-code>

Reason:

The requested task code is invalid. Ensure that both the task and the program invoked by the task have been defined to the system.

Module:

RHDCTSKC

Severity:

5

DC035002

TASK SECURITY VIOLATION - <task-code>

Reason:

The signed-on user is not authorized to execute the named task. See the system administrator to obtain authority to access the named task.

Module:

RHDCTSKC

Severity:

5

DC035003

PROGRAM <program-name> FOR TASK <task-code> NOT FOUND

Reason:

The named program cannot be found. The probable cause of this error is that the named program either has not been defined to the system or has been disabled.

Module:

RHDCTSKC

Severity:

5

DC035004

INVALID ATTACH PARAMETER SPECIFIED

Reason:

An invalid parameter has been supplied to the online system for the #ATTACH function. Some of the parameters supported in the batch environment are not supported in the online environment. Remove unsupported parameters from the program.

Module:

RHDCTSKC

Severity:

5

DC035005

DETACH FUNCTION NOT SUPPORTED ONLINE

Reason:

The user program has issued a #DETACH call. #DETACH is not supported in the online environment.

Module:

RHDCTSKC

Severity:

5

DC035006

LTE IS UNAVAILABLE

Reason:

An attempt to allocate an LTE for the #ATTACH macro has failed.

Module:

RHDCTSKC

Severity:

5