Reason:
You attempted to invoke CA Dataquery from a terminal of a type which is not supported. CA Dataquery supports 3270-type terminals and printers and SCS printers.
Action:
Initiate CA Dataquery from a 3270-type terminal.
Reason:
CA Dataquery was started with a transaction ID that is not allowed. This could be caused by having the CICS PCT coded incorrectly.
Action:
Correct the PCT and retry.
Reason:
The PPT entry for DQSYSTBL is missing, or the DQSYSTBL module is missing, or the module is invalid.
Action:
Make sure the PPT entry and the DQSYSTBL module are available and retry.
Reason:
CA Dataquery has requested a snap dump because of a database error, DQ027E, an SQL error, DQ093E or because you have requested a diagnostic dump.
Action:
Print the CICS dump data set.
Reason:
The DQOPTLST has TINIT=NO specified, and an attempt was made to initiate CA Dataquery by typing DQRY at a terminal.
Action:
If initiating CA Dataquery from a terminal is desirable, change the DQOPTLST to TINIT=YES and retry.
Note: This error may also occur when a version earlier than 8.1 of DQSYSTBL is being loaded in error.
Reason:
CA Dataquery could not load one of the following IPC modules: PMSTRUC, PMSTBLS, or PMSEDIT, or an error occurred allocating storage for the DQPACB.
Action:
Make sure the IPC modules are available in the CICS region or in libraries concatenated in the JCL for DQBATCH. If the modules are available, increase the amount of storage available to CICS or reduce the number of CA Dataquery sessions. Or, in batch, increase the region size.
Reason:
CA Dataquery could not access the special record on the DQQ table used for assigning a unique terminal ID under TSO.
Action:
Make sure that the database Multi-User Facility is active and that the DQQ table is not full.
Reason:
CA Dataquery encountered an error trying to access the database Multi-User Facility to determine if CA Dataquery is externally secured, or, if externally secured or signon is to be retrieved from external security, an error occurred accessing the external security package, or storage was not available for use by CA Dataquery.
Action:
Make sure that the database Multi-User Facility is active and, on CICS, make sure that the CA Dataquery URT is open. If CA Dataquery is to retrieve the user signon from an external security package, make sure that sufficient storage is available on CICS or in the batch region. The DQ09 dump can be used by CA Dataquery Support to determine the exact cause of the error.
Reason:
CA Dataquery attempted to allocate some transaction storage and it was unavailable.
Action:
Either increase the amount of transaction storage available to CICS or reduce the number of CA Dataquery sessions and retry.
Reason:
CA Dataquery encountered an error reading or writing a temporary storage record. This can be caused by a shortage of temporary storage or of transaction storage.
Action:
Increase the amount of temporary storage available to CICS, or reduce the number of CA Dataquery sessions and retry.
Reason:
An internal logic error has been detected.
Action:
Collect the dump and a description of what was being done when the error occurred, and contact Technical Support CA Dataquery.
Reason:
A CA Datacom/DB return code was detected. The message text gives a brief explanation of the return code represented by nn.
Action:
See the CA Datacom/DB Message Reference Guide for further documentation of the return code.
|
Copyright © 2014 CA.
All rights reserved.
|
|