Você está na página 1de 52

Altair (Modulo de Clientes)

MANUAL DE ERRORES
ERRORES DE SISTEMA

001 Se produce al ejecutar una MACRO READ. Las causas mas corrientes son: 001-1 Error de lectura o grabacion. 001-3 Error de lectura o grabacion. 001-2 Error de lectura o grabacion.

001-4 Error de datos en una cinta o en un disco. Para que el sistema se salte el bloque que da el error hay que poner en la DCB del fichero el parametro eropt=skp. Poner block o records. 001-5 Se produce cuando se intenta leer un fichero del que ya se ha detectado el EOF o AT END. Tambien puede producirse si las longitudes de registro logico o fisico especificados en programa o ficha DD no coinciden con las del fichero.

002 Se produce al ejecutar una macro I/O debido a una longitud de registro erronea. 002-4 Se ha encontrado un registro invalido al leer un archivo con registros de longitud variable. El registro puede ser menor de 4 bytes o mayor a la longitud especificada en la DCB. 002-14 Se ha intentado grabar un registro mayor al la longitud especificada en BLKSIZE. 002-18 Se ha intentado grabar un registro mayor al 32 Kb o menor a 4 bytes (5 si usa caracter ASA). 002-2C Error en OPEN de ISAM por excesivas pistas de overflow por cilindro (CYLOFL en DCB), por BLKSIZE no multiplo de LRECL o por que BLKSIZE supera la longitud de una pista.

004 Error de open. 004E Utility batch memory execution abended. Job with duplicate utilid found in sysutil. Cuando una utilidad ha tenido un problema queda pillada, y esta parada, siempre que se intente ejecutar da error, hay que liberarla. Para liberarla en el LOG se pone en la linea de comandos /) DISP UTIL(*) Asi se busca la utilidad, una vez encontrada estara en situacion STOPPED, se reconoce por el nombre ejem 'LOADSEGU', con: /) TERM UTIL(LOADSEGU) Se libera y termina, es muy importante liberar solo la afecta127068056.doc.doc Pag. :1 de 52

Altair (Modulo de Clientes) da ya que las demas que esten puede que necesiten esa situacion o esten corriendo. 013 Se produce al ejecutar una macro open. Las causas mas corrientes son: 013-10 Se da dummy a un fichero de salida sin especificar en la DCB el parametro blksize. A un fichero dummy se le puede dar cualquier blocaje. 013-14 La sentencia DCB en el JCL no es correcta. 013-18 El miembro especificado en el parametro DSN no se encuentra en la libreria particionada indicada. 013-1C Al abrir un fichero particionado, se produce un I-O error al buscar en el directorio el nombre del miembro 013-20 En el open de un fichero secuencial. Puede tener cualquiera de las tres causas siguientes: A) Para ficheros con RECFM=FB: el blksize no es multiplo de la longitud del registro. B) El numero de posiciones descritas a nivel 01 en la data division no coincide con la longitud en la etiqueta de cabecera del fichero del JCL en la DCB. C) Para registros de longitud variable no se han especificado los 4 bytes de mas que necesita el sistema. 013-34 Falta la DCB en alguna ficha DD en un proreg.

028 Error de paginacion I/O.

031 Se produce al ejecutar una macro open para un fichero indexado. Las causas mas corrientes son: No hay espacio para encontrar ese fichero. Hay registros duplicados o un error de secuencia.

03B Se produce al ejecutar una macro open para un fichero secuencial indexado. Las causas mas corrientes son: El fichero no esta bien creado. El fichero no esta bien cerrado. El blksize es menor que la longitud del registro. La longitud del registro especificado es cero.

127068056.doc.doc

Pag. :2 de 52

Altair (Modulo de Clientes)

El blksize especificado no es multiplo de la del registro.

03D Se produce al ejecutar una macro open para un fichero indexado. En la DCB no se ha especificado el subparametro DSORG=IS. 056 Error en OPEN VSAM. 056-84 Se ha intentado abrir un fichero VSAM que ya estaba abierto (O. EJ. para el CICS). Es necesario darle un verify para cerrarlo.

0C1 Error de operacion. Puede producirse por falta de alguna DD, por escribir en un fichero no abierto, etc. En la salida impresa aparece el siguiente mensaje : XXXXXXXX DD statement missing, donde XXXXXXXX es el nombre del fichero cuya DD falta.

0C2 Verificar la ficha exec del jcl.

0C3 Problema con algun modulo. Volver a compilar y ejecutar.

0C4 Error de proteccion. Las causas mas corrientes son: - Se ha hecho una read de un fichero antes de abrirlo. - Se ha intentado operar con un dato definido en un fichero que no se ha abierto. - No se ha especificado una DD para un fichero. - En ficheros de longitud variable, se ha definido un area de FD menor que el maximo registro del fichero. - Se ha intentado acceder a una tabla por un indice diferente del 'INDEXED'. - Desbordamiento de una tabla (aunque la ready trace no lo diga, exhibir los indices). - La definicion del fichero es menor que el registro, que al leer se solapa sobre el area de procedure. - La linkage de un modulo es mayor que el espacio de linkage que se le reserva en el programa principal (se solapa sobre el area de procedure).

127068056.doc.doc

Pag. :3 de 52

Altair (Modulo de Clientes) 0C5 Error de direccionamiento. Si en el programa existe una tabla, al introducirle datos se puede haber desbordado por no controlarse el indice, estropeando las direcciones de algunas instrucciones de la procedure division.

0C7 Error de datos. Las causas mas corrientes son: - Se ha intentado hacer una operacion aritmetica con un campo cuyo contenido no es numerico. - Un campo numerico utilizado en una comparacion no contiene digitos. - Se ha intentado mover un campo cuyo contenido no es numerico.

0CB Division por cero. En un sort: fichero de entrada vacio.

106 Se produce al ejecutar una macro LINK, LOAD, ATTACH o XCTL. Motivado por un I-O error cuando el programa busca un modulo ejecutable en una libreria. 106-0C Falta de memoria virtual. Poner el parametro Region. 106-0D El programa de control encuentra un registro invalido en el modulo. 106-0E El programa de control encuentra una direccion invalida en el modulo. 106-0F Error de carga de algun modulo o incorregible error de I-O.

10A Error en una macro GETMAIN. El programa necesita mas memoria.

122 El trabajo ha sido cancelado con dump por el operador.

137 Se ha producido un error de I-O al procesar fin de volumen en una cinta. 137-04 I-O error al grabar etiqueta de cola. 137-08 I-O error al posicionarse la cinta. 137-0C I-O error al posicionarse la cinta. 137-14 I-O error al leer etiqueta de cabecera.

127068056.doc.doc

Pag. :4 de 52

Altair (Modulo de Clientes)

137-18 I-O error al posicionarse en el primer registro. 137-1C Etiqueta de cola invalida. 137-20 Etiqueta de cabecera invalida.

1F1 Nombre cinta inexistente

213 Se produce al ejecutar una macro open para un fichero en un dispositivo de acceso directo. Las causas mas corrientes son: - El fichero esta catalogado, pero no existe en el directorio del volumen al que apunto el catalogo - No se encontrara el fichero en el directorio del dispositivo especificado en el vol. - Se intenta acceder a un fichero VSAM definido en el programa como secuencial. 213-04 No existe un fichero utilizado por el programa que se trata de ejecutar. - Se intenta ejecutar un programa que tiene un error de compilacion. - No se han cerrado los ficheros. - No existen los ficheros que se van a listar o borrar. - Al emigrar el fichero se puede dar el caso de que al hacer RECALL lo meta en otro volumen al indicado en creacion y quede el apuntador en otro. O bien que en el JCL se indique un volumen distinto al que se encuentra.

222 El trabajo ha sido cancelado sin dump por el operador. Normalmente, el operador indica el motivo por el que se ha cancelado el job.

237 Se produce al procesar una etiqueta de un fichero en cinta. Puede ser debido a un fallo del armatio o a que la cinta este estropeada. 237-04 Se produce al procesar la etiqueta de cola de un fichero en cinta (error en contador de bloques). Puede haberse perdido un bloque de datos debido a un error hardware. 237-08 En una coleccion de ficheros concatenados, la etiqueta de uno de ellos (excepto el primero) no coincide con el DSN reflejado en la sentencia DD.

127068056.doc.doc

Pag. :5 de 52

Altair (Modulo de Clientes)

295 Las causas mas corrientes son: - Se ha intentado leer un fichero despues de una macro close o despues de fin de fichero. - No coinciden las areas tampones de una macro read y una macro write.

2F3 Bloqueo del sistema.

322 El paso ha sido cancelado al exceder el tiempo maximo de ocupacion de cpu permitido por el sistema o por el parametro TIME.

413 Se produce al ejecutar una macro open sobre un fichero (cinta). Las causas mas corrientes son: 413-04 Pide montar un disco en una direccion que tiene montado un residente. 413-08 I-O error en el posicionamiento de una cinta al principio de un fichero. 413-0C Igual que el 413-08. 413-10 Igual que el 413-08. 413-24 Se ha especificado en la ficha DD una densidad de grabacion diferente a la que tiene la cinta. - La cinta montada en el armario no tiene reflexivo. 413-28 Se han asignado menos unidades de las requeridas.

513 Mal posicionamiento de una cinta.

522 Cancelacion por tiempo de espera de algun recurso.

606 Falta de memoria al ejecutar un programa.

613 El label requerido no es utilizable por estar mal grabado.

127068056.doc.doc

Pag. :6 de 52

Altair (Modulo de Clientes)

622 Terminal TSO cancelado por el operador o desconexion de sistema.

637 Se han concatenado ficheros con atributos incompatibles.

706 Programa no ejecutable.

714 I-O error en un fin de fichero. Posiblemente producido por la unidad de cinta.

722 El job ha sido cancelado al exceder el numero de lineas especificado en la opcion OUTLIM=XXXXX de la ficha sysout o sysdbout. Produce volcado de memoria.

802 El modulo llamado en un EXEC no existe

804 Insuficiente memoria virtual. Parametro REGION insuficiente.

806 Se produce al intentar ejecutar un modulo que no existe en la libreria especificada. Las causas mas corrientes son: 806-04 El programa o modulo no existe en la libreria. 806-08 I-O error al intentar cargar el programa en la libreria.

80A Falta de espacio en memoria para ejecutar el trabajo.

813 El DSN especificado en la ficha DD no coincide con el que figura en la etiqueta del fichero de cinta. Nombre mal puesto. Si se esta pidiendo una cinta desde pruebas ver que esten bien los cuatro cualificadores y el vol ser.

837-08 El fichero a grabar pide mas de cinco cintas y no esta especificado en el parametro 'vol=(,,,x)', donde 'x' es el numero de cintas que puede requerir.

878 Falta de memoria. Aumentar el valor del parametro region en la

127068056.doc.doc

Pag. :7 de 52

Altair (Modulo de Clientes) ficha job del jcl o ponerlo.

913 Password incorrecta. A13 El numero de fichero especificado no existe en la cinta.

B37 Falta de espacio en disco. Se utilizo todo el espacio (primario y secundario) y fue insuficiente, o no han podido tomarse todas las extensiones por no haber espacio en el volumen. Generalmente se produce porque un fichero de salida impresa necesita mas espacio.

C03 No se ha cerrado algun fichero. Va acompaado de un QSAM error file status is 90.

D37 Se ha llenado el espacio reservado para un fichero y no se han indicado incrementos o no hay espacio en el disco.

E37 Falta de espacio. E37-04 Un fichero agoto el espacio de un volumen y no puede utilizar volumenes adicionales al no haberse especificado en el JCL. E37-08 Un fichero que habia ocupado todo el espacio de un volumen, al extenderse a otro volumen se ha encontrado un archivo con el mismo nombre. E37 Tambien puede dar este error cuando en un fichero particionado se agotan los bloques de directorio.

U0005 Ocurrido al pasar un sort. Ver si se ha puesto la coma despues del parentesis que encierra los sort fields

U0007 Ocurrido al pasar un sort. - Hay un error de sintaxis en los parametros. habia puesto SIZE=(1,1,A) y tenia que ser SIZE=E100

U0187 Se ha detectado una tabla incorrecta de verbos, generada por el compilador.

127068056.doc.doc

Pag. :8 de 52

Altair (Modulo de Clientes)

U0203 Un intento de dividir por cero (que causaria normalmente un abend 0CB) ha sido detectado, y no se ha especificado la condicion on size error. El registro 14 contiene la direccion de la instruccion que ha causado el error en el programa. U0295 El codigo de retorno (RC12) ha sido cambiado de positivo a negativo. El abend puede seguir a un mensaje del terminal. Normalmente se produce al intentar leer despues de detectarse el fin de fichero. Tambien puede ser por mala especificacion en la ficha DD correspondiente.

U0300 Error DLI.

U0303 La hora que figura en el volumen en el que esta guardado un fichero VSAM, no concuerda con la hora que grabo el sistema en el registro del catalogo de ficheros.

U0304 La hora que figura en los componentes de un fichero VSAM y la hora que figura en los componentes de un indice no concuerdan. Indicando que uno de los dos ha sido actualizado por separado del otro.

U0430 Falta la tarjeta dd referente al VSAM que sostiene el buffer de la base de datos. En la reorganizacion de bases puede ser falta de memoria.

U0476 El orden de los parametros de una call al dli esta cambiando. (Puede ser que se equivoque el nombre de lenguaje en la PSB, o en la misma call se haga referencia al ...tdli en otro lenguaje). U0480 Falta alguna dd de salida.

U0519 Una ejecucion ha llegado al final de la procedure sin que apareciera alguna de la sentencias siguientes: STOP RUN GOBACK EXIT PROGRAM Existe un error en el flujo logico del programa. El codigo objeto generado por el compilador produce un abend. Puede haberse producido un aviso sobre esta situacion en tiempo de ejecucion.

127068056.doc.doc

Pag. :9 de 52

Altair (Modulo de Clientes) U0844 Base de datos llena.

U0929 Fallo en compilacion de PSB. Puede estar con otro nombre o algo asi.

U1002 Falta clausula block 0 records en fd. Longitud erronea en algun fichero o ficha de control.

U1006 Un indice apunta fuera de la tabla.

U1013 El texto del mensaje indica el error de returd code. El comando del Cics y el nombre de la libreria de subrutinas. Para mas informacion mirar el manual de mensajes del Cics. El JOB ha sido cancelado.

U1015 Llamada recursiva a un programa activo.

U1017 Display/Accept erroneo. Falta sentencia DD de SYSOUT o SYSIN.

U1020 Se lee despues de fin de fichero. Error open. Falta stop-run

U1033 Se ha compilado el programa con MODE 24 y tenia que ser MODE 31.

U1035 Open/Close erroneo. Mirar jcl. Comprobar nombre de fichero que da en el error y ver si existe esa ddname en el JCL y si su longitud de registro es la correcta. 1 - AFTER en sentencia WRITE del fichero. 2 - Nombre no definido en el jcl. 3 - Longitud erronea. 4 - Blocaje erroneo.

U1037 El programa no tiene final de flujo (STOP RUN o GOBACK).

U1301 Existe un error para un fichero que es VSAM o QSAM no previsto en las declaratives.

127068056.doc.doc

Pag. :10 de 52

Altair (Modulo de Clientes)

U3361 El nombre de la pcontrol no es el mismo que el nombre del programa cobol en uso y symdmp no es cancelado.

U3440 No hay disponible suficiente memoria principal, o se ha producido un requerimiento getmain o freemain invalido.

U3505 Se ha detectado un error de flujo de control.

U3710 DLI. Se ha detectado un program check. No todos los ficheros han sido abiertos o definidos en el jcl. Error e/s definicion fichero, si un fichero de salida es de longitud variable, en el jcl no se pone el LRECFL.

U3711 DLI. No hay cics.

U3714 DLI: AJCN Llenado log. Poner checkpoint. ADLP Ver PSB'S. 775 (ADLA) poner checkpoint o reducir el numero a partir del cual se realizan (contarlos en las lecturas). 828 Hay claves duplicadas al hacer la insert.

U3717 Comprobar letra de compilacion. Si tiene checkpoint controlar las PCB(1) y PCB(2). Mal catalogado con: DLI - USING en la ENTRY DLI/DB2 - USING en la PROCEDURE

U3723 Bases cerradas. Mal la PSB. Si codigo 805 faltan recursos.

U3795 Pcb mal.

IKF115I - QSAM ERROR - El jcl ha cogido un programa que no corresponde. Mirar en el program-id a ver si es el bueno o hay otro

127068056.doc.doc

Pag. :11 de 52

Altair (Modulo de Clientes) nombre, aunque en el jcl este bien puesto. RETURN CODE 90 : Resulto que el nombre en DD era distinto del nombre en ASSIGN TO del programa.

127068056.doc.doc

Pag. :12 de 52

Altair (Modulo de Clientes)

SQL Return Codes


Structures Query Language (SQL) return codes are returned in the SQL communication area (SQLCA). The SQLCA is an area in the application program (defined by the application program) for use of DB2. The SQL return code is returned in the SQLCODE field of the SQLCA. The SQL return codes are listed below. Successful Execution SQLCODE 000 SUCCESSFUL EXECUTION. Ejecucion correcta. Warning SQLCODES - Codigos de atencion (Llevan signo) Warning SQLSTATE - Codigos de atencion (Estan entre parentesis) +100 ROW NOT FOUND FOR A FETCH, UPDATE OR DELETE, OR THE RESULT (02000) OF A QUERY IS AN EMPTY TABLE +162 TABLESPACE database-name.tablespace-name HAS BEEN PLACED IN CHECK PENDING +304 A VALUE WITH DATA TYPE data_type1 CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE THE VALUE IS NOT WITHIN THE RANGE OF THE HOST VARIABLE IN POSITION position_number WITH DATA TYPE data_type2 +402 LOCATION location IS UNKNOWN +403 THE LOCAL OBJET REFERENCED BY THE CREATE ALIAS STATEMENT DOES NOT EXIST +558 THE WITH GRANT OPTION IS IGNORED BECAUSE GRANT IS TO PUBLIC +560 THE WITH GRANT OPTION IS IGNORED FOR UPDATE (COLUMN_LIST) +561 THE ALTER AND INDEX PRIVILEGES CANNOT BE GRANTED TO "PUBLIC AT ALL LOCATIONS" +625 THE DEFINITION OF TABLE table-name HAS BEEN CHANGED TO INCOMPLETE +802 EXCEPTION ERROR exception_type OCURRED DURING operation_type OPERATION ON data_type DATA, POSITION position_number (01501) Al hacer SELECT o INSERT, hay alguna variable truncada, por no coincidir las longitudes -007 STATEMENT CONTAINS THE ILEGAL CHARACTER character -010 THE STRING CONSTANT BEGINNING string IS NOT TERMINATED -060 INVALID type SPECIFICATION: spec -084 UNACCEPTABLE SQL STATEMENT -101 THE STATEMENT IS TOO LONG OR TOO COMPLEX

127068056.doc.doc

Pag. :13 de 52

Altair (Modulo de Clientes)

-102 THE LENGTH OF THE STRING CONSTANT BEGINNING string IS GREATER THAN 254 CHARACTERS OR 124 GRAPHIC CHARACTERS -103 literal IS AN INVALID NUMERIC LITERAL -104 STATEMENT CONTAINS THE INVALID CHARACTER OR TOKEN token-1. (37501) TOKEN token-2 WAS EXPECTED. Error sintactico. -105 INVALID STRING -107 THE NAMA name IS TOO LONG. MAXIMUN ALLOWABLE SIZE IS size -109 clause CLAUSE IS NOT PERMITTED -110 INVALID HEXADECIMAL LITERAL BEGINNING string -111 A COLUMN FUNCTION DOES NOT INCLUDE A COLUMN NAME -112 THE OPERAND OF A COLUMN FUNCTION IS ANOTHER COLUMN FUNCTION OR DISTINCT FOLLOWED BY AN EXPRESION -113 INVALID CHARACTER FOUND IN NAME: name -115 A PREDICATE IS INVALID BECAUSE THE COMPARISON OPERATOR operator IS FOLLOWED BY A PARENTHESIZED LIST OR BY ANY OR ALL WITHOUT A SUBQUERY -117 THE NUMBER OF INSERT VALUES IS NOT THE SAME AS THE NUMBER (53002) OF OBJET COLUMNS -118 THE OBJET TABLE OR VIEW OF THE INSERT, DELETE, OR UPDATE STATEMENT IS ALSO IDENTIFIED IN A FROM CLAUSE -119 A COLUMN IDENTIFIED IN A HAVING CLAUSE IS NOT INCLUDE IN THE GROUP BY CLAUSE -120 A WHERE CLAUSE OR SET CLAUSE INCLUDES A COLUMN FUNCTION OR A WHERE CLAUSE INCLUDES A REFERENCE TO COLUMN [column-name] WHICH IS DERIVED FROM A COLUMN FUNCTION IN A VIEW DEFINITION -121 THE COLUMN name IS IDENTIFIED MORE THAN ONCE IN THE INSERT OR UPDATE STATEMENT -122 A SELECT STATEMENT WITH NO GROUP BY CLAUSE CONTAINS A COLUMN NAME AND A COLUMN FUNCTION IN THE SELECT CLAUSE OR A COLUMN NAME IS CONTAINED IN THE SELECT CLAUSE BUT NOT IN THE GROUP BY CLAUSE -125 AN INTEGER IN THE ORDER BY CLAUSE DOES NOT IDENTIFY A COLUMN OF THE RESULT -126 THE SELECT STATEMENT CONTAINS BOTH AN UPDATE CLAUSE AND AN ORDER BY CLAUSE -127 DISTINCT IS SPECIFIED MORE THAN ONCE IN A SUBSELECT -128 INVALID USE FOR NULL IN A PREDICATED

127068056.doc.doc

Pag. :14 de 52

Altair (Modulo de Clientes)

-129 THE STATEMENT CONTAINS TOO MANY TABLE NAMES -131 STATEMENT WITH LIKE PREDICATE HAS INCOMPATIBLE DATA TYPES -132 A LIKE PREDICATE IS INVALID BECAUSE THE FIRST OPERANDO IS NOT A COLUMN OR THE SECOND OPERAND IS NOT A STRING -133 A COLUMN FUNCTION IN A SUBQUERY OF A HAVING CLAUSE IS INVALID BECAUSE IT INCLUDES AN EXPRESSION THAT APPLIES AN OPERATOR TO A CORRELATED REFERENCE -134 IMPROPER USE OF LONG STRING COLUMN column-name OR A HOST vaRIABLE OF MAXIMUM LENGTH GREATER THAN 254 -136 SORT CANNOT BE EXECUTED BECAUSE THE SORT KEY LENGTH IS GREATER THAN 4000 BYTES -137 RESULT OF CONCATENATION TOO LONG -138 THE SECOND OR THIRD ARGUMENT OF THE SUBSTR FUNCTION IS OUT OF RANGE -150 THE OBJET OF THE INSERT, DELETE, OR UPDATE STATEMENT IS A VIEW FOR WHICH THE REQUEST OPERATION IS NOT PERMITED -151 THE COLUMN column-name CONNOT BE UPDATE BECAUSE IT IS EITHER OR INCLUDED INTHE PARTITIONING KEY OF A PARTITIONES TABLESPACE DERIVED FROM A SQL FUNCTION OR EXPRESSION -153 THE CREATE VIEW STATEMENT DOES NOR INCLUDE A REQUIRED COLUMN LIST -154 THE CREATE VIEW FAILED BECAUSE THE VIEW DEFINITION CONTAINS A UNION, OR UNION ALL, OR A REMOTE OBJETC -156 THE ALTER TABLE, DROP TABLE, LOCK TABLE, OR CREATER INDEX STATEMENT IDENTIFIES A VIEW THE STATEMENT DOES NOT IDENTIFY A TABLE -157 ONLY A TABLE NAME CAN BE SPECIFIED EN A FOREIGN KEY CLAUSE. object-name IS NOT THE NAME OF A TABLE -158 THE NUMBER OF COLUMNS SPECIFIED FOR THE VIEW IS NOT THE SAME AS THE NUMBER OF COLUMNS SPECIFIED BY THE SELECT CLAUSE -159 THE NAME SPECIFIED ON DROP VIEW IS A TABLE NAME -160 THE WITH CHECK OPTION CANNOT BE USED FOR THE SPECIFIED VIEW -161 THE INSERT OR UPDATE IS NOT ALLOWED BECAUSE A RESULTING ROW DOES NOT SATISFY THE VIEW DEFINITION -164 auth-id1 DOES NOT HAVE THE PRIVILEGE TO CREATE A VIEW WITH QUALIFICATION auth-id2 -170 THE NUMBER OF ARGUMENTS SPECIFIED FOR function-name IS INVA LID

127068056.doc.doc

Pag. :15 de 52

Altair (Modulo de Clientes)

-171 THE DATA TYPE, LENGTH, OR VALUE OF ARGUMENT nn OF function-name IS INVALID -172 function-name IS NOT A VALID FUNCTION NAME -180 THE STRING REPRESENTATION OF A DATETIME VALUE INVALID SYSN(22007) TAX -181 THE STRING REPRESENTATION OF A DATETIME VALUE IS NOT A VALID VALUE -182 AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE IS INVALID -183 AN ARITHMETIC OPERATION ON A DATE OR TIMESTAMP HAS A RESULT THAT IS NOT WITHIN THE VALID RANGE OF DATES -184 AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE CONTAINS A PARAMETER MARKET -185 THE LOCAL FORMAT OPTION HAS BEEN USED WITH A DATE OR TIME AND NO LOCAL EXIT HAS BEEN INSTALLED -186 THE LOCAL DATE LENGTH OR LOCAL TIME LENGTH HAS BEEN ONCREASED AND EXECUTING PROGRAM RELIES ON THE OLD LENGTH -187 A REFERENCE TO A CURRENT DATA/TIME SPECIAL REGISTER IS INVALID BECAUSE THE MVS TOD CLOCK IS BAD OR THE MVS PARMTZ IS OUT OF RANGE -198 THE OPERAND OF THE PREPARE OR EXECUTE IMMEDIATE STATEMENT IS BLANCK OR EMPTY -199 ILLEGAL USE OF KEYWORD keyword TOKEN token-list WAS EXPECTED -203 A REFERENCE TO COLUMN column-name IS AMBIGUOUS -204 name IS AN UNDEFINED NAME. Posiblemente la tabla no tenga sinomimo. -205 column-name IS NOT A COLUMN OF TABLE table-name -206 column-name IS NOT A COLUMN OF AN INSERTED TABLE OR AN TABLE IDENTIFIED IN A FROM CLAUSE -207 THE ORDER BY CLAUSE IS INVALID BECAUSE IT INCLUDES A COLUMN NAME BUT IT APPLIES TO THE RESUL OF A UNION OR UNION ALL -208 THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN name IS NOT PART OF THE RESULT TABLE -219 THE REQUIRED EXPLANATION TABLE table-name DOES NOT EXIST -220 THE COLUMN column-name IN EXPLANATION TABLE table-name IS NOT DEFINED PROPERLY -221 "SET OF OPTIONAL COLUMNS" IS EXPLANATION TABLE table-name

127068056.doc.doc

Pag. :16 de 52

Altair (Modulo de Clientes) IS INCOMPLETE. OPTIONAL COLUMN column-name IS MISSING -250 THE LOCAL LOCATION NAME IS NOT DEFINED WHEN PROCESSING A THREE-PART OBJECT NAME -251 TOKEN name IS NOT VALID -301 THE VALUE OF A HOST VARIABLE CANNOR BE USED AS SPECIFIED BECAUSE OF ITS DATA TYPE -302 THE VALUE OF AN INPUT VARIABLE IS TOO LARGE FOR THE TARGET COLUMN -303 A VALUE CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE THE DATA TYPES ARE NOT COMPARABLE -304 A VALUE WITH DATA TYPE data_type1 CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE THE VALUES IS NOT WITHIN THE RANGE OF THE HOST VARIABLE IN POSITION position_numer WITH DATA TYPE data_type2. -305 THE NULL VALUE CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE NO INDICATOR VARIABLE IS SPECIFIED -309 A PREDICATE IS INVALID BECAUSE A REFERENCED HOST VARIABLE HAS THE NULL VALUE -311 THE INDICATED LENGTH OF A HOST VARIABLE IS NEGATIVE -312 UNDEFINED OR UNUSUABLE HOST VARIABLE variable-name -313 THE NUMBER OF HOST VARIABLES SPECIFIED IS NOT EQUAL TO THE NUMBER OF PARAMETER MARKES -314 THE STATEMENT CONTAINS AN AMBIGUOUS HOST VARIABLE REFERENCE -401 THE OPERANDS OF AN ARITHMETIC OR COMPARISON OPERATION ARE NOT COMPARABLE -402 AN ARITHMETIC FUNCTION OR OPERATOR arith-fop IS APPLIED TO CHARACTER OR DATATIME DATA -404 THE UPDATE OR INSERT STATEMENT SPECIFIES A STRING THAT IS TOO LONG column-name -405 THE NUMERIC LITERAL literal CANNOT BE USED AS SPECIFIED BECAUSE IT IS OUT OF RANGE -406 A CALCULATED OR DERRIVED NUMERIC VALUE IS NOT WITHIN THE RANGE OF ITS OBJECT COLUMN -407 AN UPDATE OR INSERT VALUE IS NULL, BUT THE OBJET COLUMN column-name CANNOT CONTAIN NULL VALUES. La tabla no tiene las columnas que queremos insertar. -408 AN UPDATE OR INSERT VALUE IS NOT COMPARABLE WITH THE DATA TYPE OF ITS OBJECT COLUMN column-name

127068056.doc.doc

Pag. :17 de 52

Altair (Modulo de Clientes) -409 INVALID OPERAND OF A COUNT FUNCTION -410 THE FLOATING POINT LITERAL literal CONTAINS MORE THAN 30 CHARACTERS -411 THE CURRENT DATETIME OR USER KEYWORD CON NOT BE USED AS SPECIFIED -412 THE SELECT CLAUSE OF A SUBQUERY SPECIFIES MULTIPLE COLUMNS -413 OVERFLOW OCCURRED DURING DATA TYPE CONVERRSION -414 THE NUMERIC OR DATATIME COLUMN column-name IS SPECIFIED IN A LIKE PREDICATE -415 THE CORRESPONDING COLUMNS, column-number, THE OPERANDS OF A UNION OR A UNION ALL DO NOT HAVE COMPARABLE COLUMN DESCRIPTIONS -416 AN OPERAND OF A UNION CONTAINS A LONG STRING COLUMN -417 A STATEMENT STRING TO BE PREPARED INCLUDES PARA METER MARKES AS THE OPERANDS OF THE SAME OPERATOR -418 A STATEMENT STRING TO BE PREPARED CONTAINS AN INVALID USE OF PARAMETER MARKES -419 THE DECIMAL DIVIDE OPERATION IS INVALID BECAUSE THE RESULT WOULD HAVE A NEGATIVE SCALE -421 THE OPERANDS OF A UNION ALL DO NOT HAVE THE SAME NUMBER OF COLUMNS -501 THE CURSOR IDENTIFIED IN A FECH OR CLOSE STATEMENT IS NOT (24501) OPEN. El cursor no esta abierto (select) -502 THE CURSOR IDENTIFIED IN AN OPEN STATEMENT IS ALREADY OPEN (24502) El cursor ya esta abierto (select)

-503 A COLUMN CANNOT BE UPDATE BECAUSE IT IS NOT IDENTIFIED IN (56012) THE UPDATE CLAUSE OF THE SELECT STATEMENT OF THE CURSOR No se puede actualizar una columna porque no aparece en la sentencia FOR UPDATE OF del cursor -504 THE CURSOR NAME cursor-name IS NOT DEFINED (52008) El cursor no esta definido -507 THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS (24501) NOT OPEN El cursor no esta abierto (update) -508 THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS (24504) NOT POSITIONED ON A ROW El cursor no esta posicionado en una fila (update) -509 THE TABLE IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS (53027) NOT THE SAME TABLE DESIGNATED BY THE CURSOR

127068056.doc.doc

Pag. :18 de 52

Altair (Modulo de Clientes) La tabla indicada en el update o select no es la misma que la especificada en el cursor. -510 THE TABLE DESIGNATED BY THE CURSOR OF THE UPDATE OR DELETE (53028) STATEMENT CANNOT BE MODIFIED La tabla designada por el update o delete del cursor no se puede modificar -511 THE FOR UPDATE CLAUSE CANNOT BE SPECIFIED BECAUSE THE TABLE (53029) DESIGNATED BY THE CURSOR CANNOT BE MODIFIED No se puede especificar la clausula FOR UPDATE OF porque la tabla no se puede modificar -512 STATEMENT REFERENCE TO REMOTE OBJECT IS INVALID -513 THE ALIAS alias-name MUST NOT BE DEFINED ON ANOTHER LOCAL OR REMOTE ALIAS -514 THE CURSOR cursor-name IS NOT IN A PREPARED STATE -516 THE DESCRIBE STATEMENT DOES NOT IDENTIFY A PREPARED STATEMENT -517 CURSOR cursor-name CANNOT BE USED BECAUSE ITS STATEMENT NAME DOES NOR IDENTIFY A PREPARED SELECT STATEMTENT -518 THE EXECUTE STATEMENT DOES NOT IDENTIFY A VALID PREPARED STATEMENT -519 THE PREPARE STATEMENT IDENTIFIES THE SELECT TEMENT OF THE OPENED CURSOR cursor-name -530 THE INSERT OR UPDATE VALUE OF FOREIGN KEY constraint-name (23503) IS INVALID La clave ajena no existe como clave primaria

-531 THE PRIMARY KEY IN A PARENT ROW CANNOT BE UPDATE BECAUSE IT (23504) HAS ONE OR MORE DEPENDENT ROWS IN A RELATIONSHIP contraint-name No se puede actualizar la clave primaria por tener filas relacionadas en la tabla hijo. -532 THE RELATIONSHIP contraint-name RESTRICTS THE DELETION OF (23504) ROW WITH RID X'rid-number' No se puede borrar la clave primaria por tener filas relacionadas en la tabla hijo. -533 INVALID MULTIPLE-ROW INSERT -534 THE PRIMARY KEY CANNOT BE UPDATED BECAUSE OF MULTIPLE-ROW (21502) UPDATE Se intenta actualizar multiples filas de la clave primaria en un solo update. -535 INVALID UPDATE OR DELETE WITH WHERE CURRENT OF -536 THE DELETE STATEMENT IS INVALID BECAUSE TABLE table-name

127068056.doc.doc

Pag. :19 de 52

Altair (Modulo de Clientes) (56104) CAN BE AFFECTED BY THE OPERATION Hay una tabla descendiente afectada en un proceso de borrado en cascada. -537 THE PRIMARY KEY OR FOREIGN KEY CLAUSE IDENTIFIES COLUMN column-name MORE THEN ONCE -538 FOREIGN KEY name DOES NOT CONFORM TO THE DESCRIPTION OF THE PRIMARY KEY OF TABLE table-name -539 TABLE table-name DOES NOT HAVE A PRIMARY KEY -540 THE DEFINITION OF TABLE table-name IS INCOMPLETE BECAUSE IS DOES NOT HAVE A PRIMARY INDEX -541 FOREIGN KEY name IS INVALID BECAUSE IT IS A DUPLICATE REFERENTIAL CONSTRAINT -542 column-name CANNOT BE A COLUMN OF A PRIMARY KEY BECAUSE IT CAN CONTAIN NULL VALUES -551 auth-id DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION operation ON OBJET objet-name Cuando se intenta hacer un bing de un programa que no es de la entidad (ejem-caser) hay que hacer : SET CURRENT SQLID='BRB0902'; GRANT BING, EXECUTE ON PLAN ________ TO PUBLIC nom.prog. -552 auth-id DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION operation -553 auth-id SPECIFIED IS NOT ONE OF THE VALID AUTHORIZATION IDS -554 AN AUTHORIZATION ID CANNOT GRANT A PRIVILEGE TO ITSELF -555 AN AUTHORIZATION ID CANNOT REVOKE A PRIVILEGE FROM ITSELF -556 A PRIVILEGE CANNOT BE REVOKED BECAUSE IT IS NOT POSSESSED BY auth-id -557 INCONSISTENT GRAND/REVOKE KEYWORD keyword PERMITED KEYWORDS ARE keyword-list -558 INVALID CLAUSE OR COMBINATION OF CLAUSES ON A GRANT OR REVOKE -559 ALL AUTHORIZATION FUNCTIONS HAVE BEEN DISABLED -571 THE STATEMENT WOULD RESULT IN A MULTIPLE SITE UPDATE -601 THE NAME OF THE OBJET BE CREATED IS IDENTICAL TO THE EXISTING NAME name OF THE OBJET TYPE objet-type El nombre de la tabla o de la vista esta mal definido. -602 TOO MANY COLUMNS SPECIFIED IN A CREATE INDEX -603 A UNIQUE INDEX CANNOT BE CREATED BECAUSE THE TABLE CONTAINS

127068056.doc.doc

Pag. :20 de 52

Altair (Modulo de Clientes) ROWS WHICH ARE DUPLICATES WITH RESPECT TO THE VALUES OF THE IDENTIFIED COLUMNS -604 A COLUMN DEFINITION SPECIFIES AN INVALID LENGTH PRECISION, OR SCALE ATTRIBUTE -607 OPERATION operation IS NOT DEFINED FOR SYSTEM TABLES -612 column-name IS A DUPLICATE COLUMN NAME -613 THE PRIMARY KEY IS TOO LONG OR HAS TOO MANY COLUMNS -614 THE INDEX CANNOT BE CREATED BECAUSE THE SUM OF THE INTERNAL LENGTHS OF THE IDENTIFIED COLUMNS IS GREATER THEN THE ALLOWABLE MAXIMUN -616 obj-type1 obj-name1 CANNOT BE DROPPED BECAUSE IS REFERENCED BY obj-type2 obj-name2 -618 OPERATION operation IS NOT ALLOWED ON SYSTEM DATA BASES -619 OPERATION DISALLOWED BECAUSE THE WORKFILE DATA BASE IS NOT STOPPED -620 KEYWORD keyword IN stmt type STATEMENT IS NOT PERMITTED FOR A TABLESPACE IN THE WORKFILE DATA BASE -621 DUPLICATE DBID dbid WAS DETECTED AND PREVIOUSLY ASSIGNED TO database-name -623 A CLUSTERING INDEX ALREADY EXIST ON TABLE table-name -624 TABLE table-name ALREADY HAS A PRIMARY KEY -625 TABLE table-name DOES NOT HAVE AN INDEX TO ENFORCE THE UNIQUENESS OF THE PRIMARY KEY -626 THE ALTER STATEMENT IS NOT EXECUTABLE BECAUSE THE PAGESET IS NOT STOPPED -627 THE ALTER STATEMENT IS INVALID BECAUSE THE PAGESET HAS USER-MANAGED DATA SETS -628 A SEGMENTED TABLESPACE MAY NOT BE PARTITIONED -629 SET NULL CANNOT BE SPECIFIED BECAUSE FOREIGN KEY name CANNOT CONTAIN NULL VALUES -631 FOREIGN KEY name IS TOO LONG OR HAS TOO MANY COLUMNS -632 THE TABLE CANNOT BE DEFINED AS A DEPENDENT OR table-name BECAUSE OF DELETE RULE RESTRICTIONS -633 THE DELETE RULE MUST BE delete-rule -634 THE DELETE RULE MUST NOT BE CASCADE -635 THE DELETE RULES CANNOT BE DIFFERENT OR CANNOT BE SET NULL

127068056.doc.doc

Pag. :21 de 52

Altair (Modulo de Clientes) -636 THE PARTITIONING KEYS ARE NOT SPECIFIED IN ASCENDING OR DESCENDING ORDER -637 DUPLICATE keyword KEYWORD (lectura) -638 TABLE table-name CANNOT BE CREATED BECAUSE COLUMN DEFINITION IS MISSING -639 A NULLABLE COLUMN OF A FOREIGN KEY WITH A DELETE RULE OF SET NULL CANNOT BE A COLUMN OF THE KEY OF A PARTITIONED INDEX -644 INVALID VALUE SPECIFIED FOR KEYWORD keyword IN stmt-type STATEMENT -646 TABLE table-name CANNOT BE CREATED IN PARTITIONED/DEFAULT TABLESPACE tspace-name BACAUSE IT ALREADY CONTAINS A TABLE -647 BUFFERPOOL bp-name CANNOT BE SPECIFIED BECAUSE IT HAS NOT BEEN ACTIVATED -652 VIOLATION OF INSTALLATION DEFINED EDIT OR VALIDATION PROCEDURE proc-name -653 TABLE table-name IN PARTITIONED TABLESPACE tspace-name IS NOT AVAILABLE BECAUSE ITS PARTITIONED INDEX HAS NOT BEEN CREATED -660 INDEX index-name CANNOT BE CREATED ON PARTITIONED TABLESPACE tspace-name BECAUSE KEY LIMITS ARE NOT SPECIFIED -661 INDEX index-name CANNOT BE CREATED ON PARTITIONED TABLESPACE tspace-name BECAUSE THE NUMBER OF PART SPECIFICATIONS IS NOT EQUAL TO THE NUMBER OF PARTITIONS OF THE TABLASPACE -662 A PARTITIONED INDEX CANNOT BE CREATED ON A NON-PARTITIONED TABLESPACE tspace-name -663 THE NUMBER OF KEY LIMIT VALUES IS EITHER ZERO, OR GREATER THAN THE NUMBER OF COLUMNS IN THE KEY OF INDEX index-name -664 THE INTERNAL LENGTH OF THE LIMIT-KEY FIELDS FOR THE PARTITIONED INDEX index-name EXCEEDS THE LENGTH IMPOSED BY THE INDEX MANAGER -665 THE PART CLAUSE OF AN ALTER STATEMENT IS OMITTED OR INVALID -666 stmt-verb object CANNOT BE EXECUTED BECAUSE A UTILITY IS IN PROGRESS -667 THE CLUSTERING INDEX FOR A PARTITIONED TABLESCE CANNOT BE EXPLICITLY DROPPED -668 THE COLUMN CANNOT BE ADDED TO THE TABLE BECAUSE THE TABLE HAS AN EDIT PROCEDURE -669 A TABLE IN A PARTITIONED TABLESPACE CANNOT BE EXPLICITLY DROPPED

127068056.doc.doc

Pag. :22 de 52

Altair (Modulo de Clientes) -670 THE RECORD LENGTH OF THE TABLE EXCEEDS THE PAGE SIZE LIMIT -671 THE BUFFERPOOL ATTRIBUTE OF THE TABLESPACE CAN NOT BE ALREADY AS SPECIFIED BECAUSE IT WOULD CHANGE THE PAGE SIZE OF THE TABLESPACE -676 A 32K PAGE BUFFERPOOL MAY NOT BE USED FOR AN INDEX -677 INSUFFICIENT VIRTUAL STORAGE FOR BUFFERPOOL EXPANSION -678 THE LITERAL literal SPECIFIED FOR THE INDEX LIMIT KEY MUST CONFORM TO THE DATA TYPE data-type OF THE CORRESPONDING COLUMN column-name -679 THE OBJET name CANNOT BE CREATED BECAUSE A DROP IS PENDING ON THE OBJET -680 TOO MANY COLUMNS SPECIFIED FOR A TABLE -681 COLUMN column-name IN VIOLATION OF INSTALLATION DEFINED FIELD PROCEDURE. RT: return-code, RS: reason-code, MSG:message-token -682 FIELD PROCEDURE procedure-name COULD NOT BE LOADED -683 INVLID COLUMN TYPE FOR FIELDPROC OPTION, column-name -684 THE LENGTH OF LITERAL LIST BEGINING string IS TOO LONG -685 INVALID FIEL TYPE, column-name -686 COLUMN DEFINED WITH A FIELD PROCEDURE CAN NOT COMPARE WITH ANOTHER COLUMN WITH DIFFERENT FIELD PROCEDURE -687 FIELD TYPES INCOMPARABLE -688 INCORRECT DATA RETURNED FROM FIELD PROCEDURE, column-name, msgno -802 EXCEPTION ERROR 'exception_type' HAS OCCURRED DURING 'operation_type' OPERATION ON 'data_type' DATA, POSITION 'position_number' -803 ONE OR MORE INSERT OR UPDATE VALUES ARE INVALID BECAUSE THE (23505) OBJECT COLUMNS ARE CONSTRAINED SUCH THAT NO TWO ROWS OF THE TABLE CAN BE DUPLICATES WITH RESPECT TO THE VALUES OF THOSE COLUMNS. Se esta insertando o actualizando una clave unica con valores duplicados. Clave duplicada. -804 AN ERROR WAS FOUND IN THE APPLICATION PROGRAM INPUT PARAMETERS FOR THE SQL STATEMENT -805 PROGRAM NAME program-name NOT FOUND IN PLAN plan-name (51002) El programa no esta relacionado con el plan. Falta hacer Bind. -811 THE RESULT OF AN EMBEDDED SELECT STATEMENT IS A TABLE OF MO(21000) RE THAN ONE ROW, OR THE RESULT OF THE SUBQUERY OF A BASIC PREDICATE IS MORE THAN ONE VALUE

127068056.doc.doc

Pag. :23 de 52

Altair (Modulo de Clientes)

-815 A GROUP BY OR HAVING CLAUSE IS IMPLICITLY OR EXPLICITLY SPECIFIED IN AN ENBEDDED SELECT STATEMENT OR A SUBQUERY PF A BASIC PREDICATE -817 THE INSERT, UPDATE, DELETE, DDI, OR AUTHORIZATION STATEMENT CANNOT BE EXECUTED BECAUSE THE IMS/VS TRANSATION IS INQUIRY ONLY -818 THE PRECOMPILER-GENERATED TIMESTAMP x IN THE LOAD MODULE IS (51003) DIFFERENT FROM THE BIND TIME-STAMP y BUILT FROM THE DBRM El timestamp del plan y del modulo no coinciden. No se ha dado new copy. -819 THE VIEW CANNOT BE RECREATED BECAUSE IT REFERENCES A VIEW THAT COULD NOT BE RECREATED -820 THE SQL STATEMENT CANNOR BE PROCESSED BECAUSE calalog-table CONTAINS A VALUE THAT IS NOT VALID IN THIS RELEASE -821 VIEW 'view-creator'.'view-name' HAS BEEN DROPPED DURING MI GRATION. CREATOR 'synonym-creator' OF SYNONYM 'synonym-name' COULD NOT BE RESOLVED -822 THE SQLDA CONTAINS AN INVALID DATA ADDRESS OR INDICATOR VA RIABLE ADDRESS -840 TOO MANY ITEMS RETURNED IN A SELECT OR INSERT LIST -901 UNSUCCESSFUL EXECUTION CAUSED BY A SYSTEM ERROR THAT DOES NOT PRECLUDE THE SUCCESSFUL EXECUTION OF SUBSEQUENT SQL STATEMENTS -902 UNSUCCESSFUL EXECUTION CAUSED BY A SYSTEM ERROR THAT PRECLUDES THE SUCCESSFUL EXECUTION OF SUBSEQUENT SQL STATEMENTS -904 UNSUCCESSFUL EXECUTION CAUSED BY AN ANAVAILABLE RESOURCE (57011) REASON reason-code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME resource-name Recurso no disponible. Puede estar el tablespace pillado. -905 UNSUCCESSFUL EXECUTION DUE TO RESOURCE LIMIT BEING EXCEEDED, RESOURCE NAME = resource-name LIMIT = limit-amount1 CPU SECONDS (limit-amount2 SERVICE UNITS) DERIVED FROM limit-source -906 THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THIS FUNCTION IS DISABLED DUE TO A PRIOR ERROR -907 UNABLE TO DETERMINE IF THE ATTEMPT TO COMMIT UPDATES MADE AT A REMOTE SITE WAS SUCCESSFUL OR NOT -909 THE OBJECT HAS BEEN DELETED -910 THE SQL STATEMENT CANNOT A ACCESS AN OBJECT ON WHICH A DROP OR ALTERL IS PENDING -911 THE CURRENT UNIT OF WORK HAS BEEN ROLLED BACK DUE TO DEAD

127068056.doc.doc

Pag. :24 de 52

Altair (Modulo de Clientes) (40000) LOCK OR TIMEOUT. REASON reason-code, TYPE OF RESOURCE resorce-type, AND RESOURCE NAME resource-name. Timeout. Recurso no disponible, alguien esta utilizando la misma tabla en la misma transaccion, hay que esperar un poco y volverlo a intentar. -913 UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT. REASON CODE reason-code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME resource-name -922 CONNECTION AUTHORIZATION FAILURE: error-type ERROR Poner USER=SYSDBP. -923 CONNECTION NOT ESTABLISHED: DB2 condition REASON reason-co(57015) de, TYPE resorce-type, NAME resource-name. Posiblemente se ha perdido el bing, volver ha hacerlo, no hace falta compilarlo, cuidado con los miembros que tenga, hay que hacer el bing a todos. Mirar nombre del plan y DBRM y la compilacion. -924 DB2 CONNECTION INTERNAL ERROR, function-code, return-code, reason-code -925 COMMIT NOT VALID IN IMS/VS OR CICS/OS/VS ENVIRONMENT -926 ROLLBACK NOT VALID IN IMS/VS OR CICS/OS/VS ENVIRONMENT -927 THE LANGUAJE INTERFACE (LI) WAS CALLED WHEN THE CONNECTING (51006) ENVIRONMENT WAS NOT ESTABLISHED. THE PROGRAM SHOULD BE INVOKED UNDER THE DSN COMMAND El programa se debe invocar bajo DSN

127068056.doc.doc

Pag. :25 de 52

Altair (Modulo de Clientes)

DB2 Catalog Table Reference


DB2 maintains a set of tables called DB2 catalog tables that are used as a place to store information about the DB2 system. The catalog tables describe tables, columns, indexed, programs authorizations, and other DB2 objects.Data ub the tables (with the exception of password data) is available to authorized DB2 users using normal SQL query facilities. The DB2 catalog tables are automatically updated by DB2 during normal operation and in response to SQL data definition and and control statements. The following pages list the unqualified names of the catalog tables in alphabetic order. After the name if the table is a description of its purpose and a list of the names of its columns (to be read from left to rigth, by rows). Each table name is qualified by SYSIBM (as in 'SYSIBM.SYSTABLES'), but the qualifiers are amitted from the list.

ABEND's de programas batch con instrucciones DB2.


-----------------------------------------------Se pretende describir una forma de localizar la instruccion y los datos que juegan en ella en caso de que un programa Cobol con instrucciones DB2 se cancele por algun tipo de error. Sin DB2 se utilizar el OFFSET que aparece en las primeras lineas del dump (figura 1) y se contrasta con el CONDENSED LISTING que se obtiene en la compilacion del programa. Asi se obtiene la instruccion y viendo los datos que intervienen se puede localizar su BLL, el registro que los direcciona y en la parte del dump REGS AT ENTRY TO ABEND (figura 2) se ve la direccion y por tanto se pueden localizar los datos. Al tener DB2 el offset no seala la instruccion adecuada. La solucion que se propone es muy complicada, pero de momento la unica que conocemos. Los pasos a seguir son los siguientes: Sumar ADDRESS + OFFSET (figura 1) en hexadecimal. Localizar esta direccion en el dump. Estudiar el primer byte para localizar que codigo de instruccion mediante la tabla de instrucciones (figura 3). Detectar de que tipo de instruccion se trata (figura 4). Obtener los registros base de los datos, sus longitudes y desplazamientos. Localizar las BLL's (REGISTER ASSIGNMENT en la compilacion COBOL). Ojo no sabemos la instruccion que es, pero se pueden tener datos aproximativos.

127068056.doc.doc

Pag. :26 de 52

Altair (Modulo de Clientes)

127068056.doc.doc

Pag. :27 de 52

Altair (Modulo de Clientes)

ERRORES

DL/I

Codigos de estado de DL/I: Con exec se podran controlar los codigos GA, GB, GE, GK, II, LB, NE y TG, el resto daran un abend (DHXX). DFH3795 - DLI. Abnormal terminatcion - status code DHXX. Los valores de 'XX' pueden ser: AB : Segment ioarea required. No se especifico el area de E/S del segmento, la funcion o la PCB. AC : Hierarchical error in segment selection. Segment name error. Error jerarquico. Dislocacion de niveles. Ver orden PCB. Ver nombre segmento EXEC, mirar si REPLACE y falta CMPAT=Y. AD : Invalid call-function. Se especifico un parametro de funcion erroneo. Error fisico de e/s en los metodos de acceso. AH : Command requires segment selection format. Segment selection required. No se proporciono el camino de acceso necesario. AI : Data management open error. Error de apertura en la gestion de datos (jcl) AJ : Invalid qualifield segment selection format. Error en el formato de la ssa AK : Invalid field name in command. Existencia de un nombre de campo no valido AM : Command function not compatible with processing option or segment or path sensitivity. Funcion definida no compatible con las opciones del proceso AO : I/O error. DA : Segment key field has been changed. El campo clave ha sido cambiado. DJ : No preceding successful get command. La peticion anterior no se ha realizado con exito. Se hace delete o repl sin haber leido. DX : Violated delete rule. GA : Crossed hierarchical boundaty into higher level (returned only on commands without segment selection). Cruce de frontera jerarquica hacia un nivel superior. GB : End of data set, last segment reached. Fin de la base. GE : Segment or parent segment not found. No se encontro el segmento solicitado. Final de la base GK : Different segment type at same level returned (returned on unqualified commands only). Se ha recuperado un segmento situado

127068056.doc.doc

Pag. :28 de 52

Altair (Modulo de Clientes) en el mismo nivel pero de diferente tipo. GP : A GNP command and no parent established, or requested segment level not lower than parent level. No se ha establecido segmento padre. II : Segment to insert already exists in data base or is non-unique Segmento duplicado. IX : Violated insert rule. KA : Numeric truncation error during conversion. KB : Character truncation error during conversion. KC : Invalid packed/zoned decimal character during conversion. KD : Type conflict during conversion. KE : Replace violation. LB : Segment insert already exists in data base or is non-unique. El segmento a cargar ya existe. LC : Key field of segments out of sequence. LD : No parent for this segment has been loaded. LE : Sequence of sibling segmente not the same as DBD sequence. NA : Data in search or subsequence field has been changed. NE : Index maintenance cannot find segment. Segmento apuntador inexistente. NI : Index maintenance unable to open index data base. Duplicate key found for index data base. Mas de un segmento apuntador con la misma clave. NO : I/O error. Loading duplicate secondary index ponter segment. Error del metodo de acceso del sistema operativo en el mantenimiento del indice secundario RX : Violated replace rule. TA : PSB not in psb directory. TB : Program not pre-scheduled. TC : Task Psb already scheduled. Se intenta planificar la Psb y ya esta planificada. TE : PSB initialization error. TF : PSB not authorized. TG : Term attempted when PSB not scheduled. TH : Data base access command attempted when PSB not scheduled.

127068056.doc.doc

Pag. :29 de 52

Altair (Modulo de Clientes) PSB no planificada. TI : Invalid path insert call. TJ : DL/I not active. TK : Data base not active. TL : Scheduling conflict with mps task. Intent scheduling conflict. TN : Invalid system sdib address. Data(24). TO : Path replace error. TP : Invalid PCB index or invalid procopt (load). Mirar a ver si CHKP y PCB(2) o CMPAT=Y. TY : Data base non open. TZ : Data base not in fct. V1 : Invalid length for variable length segment. Longitud invalida del segmento de longitud variable. (El campo de clave, si existe, no esta incluido en la longitud minima). (El campo de longitud es mayor que la longitud maxima prevista para el segmento). V2 : Segment length missing or invalid. V3 : Field length missing or invalid. V4 : Invalid length for variable length segment. V5 : Invalid offset (Para longitud variable). V6 : Comcatenatid keylength missing or invalid. V7 : Statistics area length invalid. XD : Error during data base buffer write out. XH : Data base logging not active. bb : Command completed successfully. Proceso realizado correctamente.

NOTAS : ------CMPAT=Y: Esta asociado con la psb de actualizacion (con independencia de que se realice o no checkpoint). Es decir, siempre que se utilice una psb de actualizacion se debe poner CMPAT=Y y reservar la PCB(1) para checkpoint (aunque no se realicen).

127068056.doc.doc

Pag. :30 de 52

Altair (Modulo de Clientes)

127068056.doc.doc

Pag. :31 de 52

Altair (Modulo de Clientes)

ERRORES

DE

ABEND

VSAM

CODIGOS DE ABEND DEL SISTEMA


- S0C1 : OPERATION EXCEPTION. Se produce cuando el programa ---- intenta ejecutar un codigo de operacion que no reconoce. cuando utilizamos el registro base para hacer otras operaciones, escribir un fichero sin abrirlo,...).

- S0C4 : PROTECTION EXCEPTION. Se producira cuando el progra---- ma intenta acceder a un area de memoria que el sistema la tiene protegida por la clave de acceso a memoria.

- S0C5 : ADRESSING EXCEPTION. El programa esta intentando ---- leer una zona de memoria que no existe.

- S0C7 : DATA EXCEPTION. En alguno de los formatos numeri---- cos empaquetados se encuentra un dato que no esta en ese formato.

127068056.doc.doc

Pag. :32 de 52

Altair (Modulo de Clientes)

CODIGOS DE FILE-STATUS
0 Successful completion: 00 - No further information. * Operacion correcta, la operacion se realizo satisfactoriamente. 02 - The input-output statement was successfully executed, but a plicate key was detected. For a READ statement the key value for the current key of reference was equal to the value of the same key in the next record within the current key or reference. For a REWRITE or WRITE statement, the record just written created a duplicate key value for at least one alternate record key for which duplicates are allowed. * Clave duplicada correcta. Se encontro clave duplicada pero se especifico duplicidad de claves. 04 - A READ statemente was successfully executed, but the length of the record being processed did not conform to the fixed file attributes for that file. * La longitud del registro no esta conforme a la descripcion del fichero. 05 - An OPEN statemente is successfully executed but the referenced optional file is not present at the time the OPEN statement is executed. If the open mode is I-O or extend, the file has been created. * Se ha abierto un fichero que no esta presente. 07 - For a CLOSE statemente with the NO REWIND, REEL/UNIT, or FOR REMOVAL phrase or for an OPEN statement with the NO REWIND phrase, the referenced file was on a non-reel/unit medium. * El dispositivo de almacenamiento ded archivo no es una cinta magnetica, sin embarto un CLOSE o un OPEN incluyen una frase correspondiente NO REWIND, REEL, FOR REMOVAL. At end condition: Final de fichero 10 - A sequential READ statement was attempted and no next logical record existed in the file because the end of the file had been reached, or the first READ was attempted on an optional input file that was not present. * Final del fichero. Se encontro el final del fichero intentando una lectura secuencial. 14 - A sequential READ statement was attempted for a relative file and the number of significant digits in the relative record number was larger than the size of the relative key data item

127068056.doc.doc

Pag. :33 de 52

Altair (Modulo de Clientes) described for the file. 15 - * Intento de leer un fichero opcional que no esta presente. 16 - * Una sentencia READ se ejecuto mientras la condicion AT END era verdadera. (Intento de leer despues de fin de fichero). nvalid key condition: * Claves duplicadas 21 - A sequence error exists for a sequentially accessed indexed file. The prime record key value has been changed by the program betwween the successful execution of a READ statement and the execution of the next REWRITE statement for that file, or the ascending requirements for successive record key values were violated. * Error-secuencia. Se intenta grabar un registro con clave menor que el ultimo existente. 22 - An attempt was made to write a record that would create a duplicate key in a relative file or an attempt was made to write or rewrite a record that would create a duplicate prime record key or a duplicate alternate record key without the DUPLICATES phrase in an indexed file. This key value applies to an indexed file in which the alternate key has been declared 'UNIQUE' * Clave duplicada. Se trato de escribir un registro donde ya se habia escrito otro registro (quizas se uso un REWRITE). Se intenta grabar un registro con la misma clave existente. 23 - An attempt was made to randomly access a record that does not exist in the file, or a START or random READ statement was attempted on an optional input file that was not present. * Registro no encontrado. Se intenta leer una clave que no existe. Se intenta leer o situar un fichero vacio. En un Start se pone Greater en la clave y existe clave con high-value se intenta una lectura y previamente se hizo una con high-values. 24 - An attempt was made to write beyond the externally defined boundaries of a relative or indexed file. Or, a sequential WRITE statement was attempted for a relative file and the number of significant digits in the relative record number was larger than the size of the relative key data item described for the file. * Violacion de los limites de un indexado. Se intenta grabar y el fichero no dispone de mas extensiones. Se trato de escribir fuera de los limites del archivo. Permanent error condition: * Error permanente. 30 - No further information. * Existe un error permanente, no hay informacion adicional

127068056.doc.doc

Pag. :34 de 52

Altair (Modulo de Clientes) disponible. 34 - A permanent error exists because of a boundary violation; an attempt was made to write beyond the externally-defined boundaries of a sequential file. * Violacion de limites en un secuencial. Se intenta grabar y el fichero esta lleno. 35 - An OPEN statement with the INPUT, I-O, or EXTEND. Phrase was attempted on a non-optional file that was not present. * Se produce cuando tratamos de leer un fichero VSAM vacio de nueva creacion. Para solucionarlo hay que definirlo como: SELECT OPTIONAL ddname ASSIGN . . FILE STATUS IS st-xxxxxxx. y aceptar el file-status '05' que nos devuelve cuando lo abrimos como correcto. IF st-xxxxxxx = '00' OR = '05' CORRECTO END-IF. 37 - An OPEN statement was attempted on a file that would not support the open mode specified in the OPEN statement. Possible violations are: * Intento de OPEN a un fichero que debe estar en almacenamiento masimo pero no esta. 1. The EXTEND or OUTPUT phrase was specified but the file would not support write operations. 2. The I-O phrase was specified but the file would not support the input and output operations permitted. 3. The INPUT phrase was specified but he file would not support read operations. 38 - An OPEN statemente was attempted on a file previously closed with lock. * Intento de OPEN a un fichero que a sido cerrado (CLOSED) con LOCK. 39 - The OPEN statement was unsuccessful because a conflict was detectd between the fixed file attributes and the attributes specified for that file in the program. These attributes include the organization of the file (sequential, relative, or indexed), the prime record key, the alternate record keys, the code set, the maximun record size, the record type (fixed or variable), and the blocking factor.

127068056.doc.doc

Pag. :35 de 52

Altair (Modulo de Clientes) * Error durante la ejecucion de OPEN, debido a inconsistencia entre la descripcion del fichero y el fichero real.

Logic error condition.

* Ibm definido.

41 - An OPEN statement was attempted for a file in the open mode. * Se trato de hacer un OPEN a un fichero ya abierto. 42 - A CLOSE statement was attempted for a file not in the open mode. * Se trato de hacer un CLOSE a un fichero ya cerrado. 43 - For a mass storage file in the sequential access mode, the lasr input-output statement executed for the associated file prior to the execution of a REWRITE statement was not a successfully executed READ statement. For relative and indexed files in the secuential access mode, the last input-output statement executed for the file prior to the execution of a DELETE or REWRITE statement was not a successfully executed READ statement.

* Se trato de hacer un DELETE o un REWRITE en modo de acceso secuencial, sin que se haya ejecutado con exito una instruccion READ precedente. 44 - A boundary violation exist because an attempt was made to rewrite a record to a file and the record was not the same sisize as the record being replaced, or an attempt was made to write or rewrite a record that was larger than the largest or smaller than the smallest record allowed by the RECORDS IS VARYING clause of the associated file-name. * Una violacion de limite debida al intento de WRITE o REWRITE a un registro de longitud inapropiada. 46 - A sequential READ statement was attempted on a file open in the input or I-O mode and no valid next record had been established because the preceding READ statement was un successful or caused an at end condition. * Intento de READ a un registro no existente. 47 - The execution of a READ statement was attempted on a file not open in the input or I-O mode. * Se trato de hacer un READ o un START a un fichero fuera del modo o INPUT. 48 - The execution of a WRITE statement was attempted on a file not open in the I-O, output or extend mode. * Se trato de hacer un WRITE en un archivo que no se abrio

127068056.doc.doc

Pag. :36 de 52

Altair (Modulo de Clientes) en ninguno de los modos OUTPUT, I/O, o EXTEND 49 - The execution of a DELETE or REWRITE statement was attempted on a file not open in the I-O mode. * Se trato de hacer un DELETE o un REWRITE en un fichero que no estaba en modo I/O.

Implementor-defined condition. 90 - No further information. 91 - For VSAM only: Password faiture. * Falta la password. 92 - Logic error. * Error logico. Se intenta utilizar el fichero y este esta cerrado. Se intenta leer el fichero y detecto un final previo. Se intento un rewrite o un delete y el fichero no se abrio como I-O. Se intento un rewrite y el area es mayor que la definida. Se intento una insercion en un fichero abierto extended y la clave no es mayor que la mayor existente en el fichero. 93 - For VSAM only: Resource not available. * Fichero en uso. El fichero esta siendo usado en exclusiva por otro programa. 94 - For VSAM with CMPR2 compiler-option only: No file position indicator for sequential request. * Perdido el puntero. Una operacion anterior dejo el direccionador de registro mal. 95 - For VSAM only: Invalid or incomplete file information. * Error informacion de fichero. Un fichero con definicion de cluster como ksds, esta siendo abierto como secuencial. La longitud o el desplazamiento de la clave no corresponde con el especificado en la definicion de cluster. El fichero ha sido abierto como output y no esta vacio. 96 - For VSAM only: No DD statement specified or this file. * Falta DLBL. Falta ficha de informacion de fichero en el jcl (ficha dd). 97 - For VSAM only: OPEN statement execution successfull: File integrity verified. * Fichero mal cerrado. El fichero ha sido utilizado en un programa anterior y no fue cerrado satisfactoriamente, el sistema hace un verify automaticamente y continua.

127068056.doc.doc

Pag. :37 de 52

Altair (Modulo de Clientes)

127068056.doc.doc

Pag. :38 de 52

Altair (Modulo de Clientes)

ERRORES DE CICS
DFHxx001 Applid an abend (code aaa/bbb) has occurred al offset X'offset' in module modname. DFHxx002 Applid an severe error (code X'code') has occurred in mole modname. DFHxx003 Applid insufficient storage (code X'code') in module modname. DFHxx004 Applid a possible loop has been detected at offset X'offset' in module modname. DFHxx005 Applid a hardware error has occurred (module modname, code X'code'). MVS store clock was found inoperative. DFHxx006 Applid insufficient storage to satisfy getmain (code X'code') in module modname. MVS code modcode.

CODIGOS DE RETORNO
____________________ + 27 : Posiblemente el programa que esta dando el error esta llamando a otro programa que no esta deficino en cics.

ABEND CODES ______________


AACA - Invalid error code. AAKP - Write I/O error to mt log. AAL1 - Local system has no sessions, or no LU6.2 mode entry AAL2 - Bad response from suspend or resume of allocate task. AAMA - Internal logic error. AAMD - Bad return code DFHDMP AAMF - Internal logic error in DFHAMP AAMG - Internal logic error in DFHAMP AAMH - Internal logic error in DFHAMP AAMI - Internal logic error in DFHAMP AAMJ - Disastrous error while installing file using RDO AAMK - Disastrous error returned from DFHFCDN AAMO - Bad return code from DFHTOR AAMP - Bad return code from DFHPUP AAMT - Bad return code from DFHTMP AAMZ - Bad return code from DFHZCP ABLA - Task purged before a GETMAIN request ABLB - Error in call to storage domain ABMA - TIOA wrong length ABMB - Cursor position larger than current screen size. ABMD - Bad return code from send.

127068056.doc.doc

Pag. :39 de 52

Altair (Modulo de Clientes) ABMG - BMS service not present. ABMI - Not input map. ABML - Invalid output. ABMM - Invalid map. ABMO - Not output map. ABMP - Undefined PA/PF key ABMS - Terminal not found in TCT ABMT - BMS used for non-3270 teminal ABMU - Address out of range. ABMV - Invalid route list entry. ABMX - Invalid set attribute order in text. ABM0 - Map not located. ABM1 - BMS service requested from non-BMS-supported terminal. ABM2 - No user data for BMS request. ABM3 - BMS service requested from non-BMS-supported terminal. ABM4 - Page error. ABM5 - Purge request issued with invalid REQID by BMS. ABM6 - CSPS not defined in PCT. ABM7 - Trailer too large. ABM8 - Justify parameter too large. ABM9 - Trailer too large. ABNA - No route list. ABNB - Invalid TCTTE type for principal facility. ABNC - Access temporary storage queue failed. ABNE - Invalid response from BMS ROUTE or STORE request. ABNF - Send, not in send mode. ABNG - Attach received without data. ABNH - Ship to remote system failed. ABNI - LU6.2 profile not found. ABNJ - Task purged before GETMAIN complete. ABNK - Error on call to storage domain. ABP1 - I/O error in restart data set. ABP2 - Backout failure. ABP3 - Cics internal logic error. ABSA - Cics internal logic error. ACAA - Invalid function code on command analysis request. ACAD - Invalid function code on defauls request. ACAI - Invalid function code on request to DFHCAP. ACHA - Remote server transaction is incorrect level. ACHB - Remote server received frame out of sequence. ACHC - Remote server did not receive acknowiedgement. ACHD - Remote server did not receive response. ACHE - Remote server received unexpected data. ACHF - Remote server sent more than one data frame. ACHG - Remote server sent data when not in mode. ACHH - Remote server has no TIOA for data. ACHI - Remote server received bad return code. ACHJ - Remote server cannot return error condition. ACHK - Logic error in transformer program request. ACHL - Remote server buffer too small. ACHM - Remote server response retry limit exceeded. ACHN - Remote server request retry limit exceeded. ACHO - Remote server reply retry limit exceeded. ACHP - Remote server has insufficient storage. ACHQ - Remote server not supported by DL/I. ACP1 - Bad IC response code. ACP2 - Bad IC response code. ACRA - Principal facility is not terminal. ACRB - Transaction is not remote.

127068056.doc.doc

Pag. :40 de 52

Altair (Modulo de Clientes) ACRC - Invalid response from DFHZCX ACRD - System entry not found. ACRE - Link is out of service. ACRF - No matching AID for ATI initiated remote transaction. ACRG - Dynamic routing program incorrectly initiated. ACRH - Profile could not be found. ACSA - Principal facility is not link. ACSB - Invalid reply to schedule request. ACSC - Invalid request received. ACSD - Logic error in DFHCRS. ACSE - DFHCRS attached in unsupported manner. ACTA - Relay program in TOR had unexpected request from AOR. ACTB - Relay program WRITE, LAST request failed. ACTC - Relay program failed to free session. ACTD - Relay program WRITE, WAIT, READ request failed. ACTE - Relay program failed to free session. ACTF - Relay program failed to free session. ACTG - Relay program received invalid region response. ACTH - Privileged allocate issued against a remote LU6.2 system. ACTI - TCTTE for session not owned by task. ACTJ - Principal facility of relay transaction not a TCTTE. ACUA - Request not supported for transaction routing. ACUB - TCTSE address missing from parameter list for ALLOCATE request ACUC - TCTSE address not that of a remote LU6.2 terminal. ACUD - Profile DFHCICSR was not located in the PCT. ACUE - Request to DFHZTSP to build surrogate TCTTE not met. ACUF - Seccion not allocated - request incorrectly specified. ACUG - Profile for ALLOCATE not found in the PCT. ACUH - Requested session already owned by the TCA. ACUI - Modegroup not found. ACUJ - Maximum session count for modegroup is zero. ACUK - No definition found for terminal-owning system. ACUL - Write, Wait, Read request failed. ACUM - Request to free surrogate TCTTE not satisfied. ACUN - Attempt to free session with TOR failed. ACUO - Attempt to read data from TOR failed. ACUP - Expected rollback not received. ACUQ - Attempt to read data from TOR failed. ACUR - Expected rollback not received. ACUS - Attempt to read data from TOR failed. ACUT - Expected rollback or sync point not received. ACUV - TC issue abend on MRO link failed. ACUW - TC issue error on MRO link failed. ACUX - TC converse failed. ACUY - TC write failed. ACUZ - TC converse failed. ACU0 - TC write, last, wait failed. ACU1 - Attempt to read data from TOR faided. ACU2 - Something unexpected received from the TOR. ACU3 - Invalid state for conversation state machine. ACU4 - Selling of conversation state machine failed. ACU5 - Connection between two systems not installed. ACVA - TC converse failed. ACVB - Invalid attempt to issue signal on MRO link. ACVC - DFHLUC issue signal failed. ACVD - TC read from AOR failed. ACVE - TC WRITE failed. ACVF - TC WRITE, LAST, WAIT failed. ACVG - DFHLUC attempt to free session failed.

127068056.doc.doc

Pag. :41 de 52

Altair (Modulo de Clientes) ACVH - Attempt to free session with TOR failed. ACVK - DFHLUC issue abend failed. ACVL - TC issue abend on MRO link failed. ACVM - DFHLUC issue error failed. ACVN - TC issue error on MRO link failed. ACVO - Invalid response to issue prepare. ACVP - Expected FMH43 not received from AOR. ACVQ - Unexpected bad return code from terminal. ACVR - Unexpected return code from terminal control. ADBA - Attempt to read dynamic log failed. ADBB - DWE chain off TCA corrupted. ADBC - DL/I log record too large for DL/I interface. ADBD - Interface scheduling block not found. ADBE - Invalid file name found in dynamic log. ADBH - Invalid service module identifier. ADBK - Invalid function ID found. ADBL - Invalid error code found. ADCA - Non-zero return code from DBCTL. ADCB - No PSB scheduled for task. ADCC - PSB already scheduled. ADCD - Dadlock detected in DBCTL. ADCE - Non-zero return code from DFHDBAT. ADCI - User abend 3303 returned from IMS. ADCJ - CICS-DBCTL interface terminated. ADCN - Forcepurge request against suspended task, waiting for DBCTL. ADCP - PSB schedule request failed security check. ADCQ - Invalid EXEC DLI SCHD request. ADCR - No active communication with DBCTL. ADDA - Error on call to storage domain. ADDB - Error on call to catalog domain. ADDC - Error on call to loader domain. ADIR - Invalid DFHDI or DFHBMS request. ADLA - A DL/I abend occurred. Poner checkpoint o reducir el numero a partir del cual se realizan (contarlos en las lecturas). ADLD - Program isolation deadlock detected. ADLE - DL/I request for remote database on unknown system. ADLF - DL/I request for remote database, but link down. ADLG - Errors in DL/I argument list for remote database request. ADLH - CICS DL/I restart task could not complete. ADLI - CICS DL/I no esta arrancado. Hay un CICS parado, tienen que arrancarlo y recuperar los ficheros, llamar a sistemas, el CICS puede ser DBDIMS31. ADLK - Invalid IMS subroutine call. ADLL - Bad journal. ADLM - Global catalog read error. ADLP - PSB usage failed security check. Ver PSB's. ADLS - ISB for transaction cannot be found. ADLX - Invalid DL/I request to get or free buffer. ADL1 - Bad return code from WAIT MVS request. ADL2 - Transaction cancelled during IMS request wait. ADMA - Unexpected response from CICS/XRF message manager. ADMB - Unrecognizable mensaje from CICS/XRF message manager. AEC1 - CECI, CEMT, or CEDA transaction attempted on unsupported terminal. AEC2 - CECI, CEMT, or CEDF tried to use too small a screen. AEC3 - COBOL II failed to initialize a thread. AEC4 - COBOL II failed to initialize a run-unit. AEC5 - C/370 failed to initialize a thread. AEC6 - C/370 failed to initialize a run-unit.

127068056.doc.doc

Pag. :42 de 52

Altair (Modulo de Clientes) AED1 - Attempt to use EDF on unsupported terminal. AED2 - EDF has terminated a task. AED4 - Logic error in DFHEDFP. AED5 - Internal logic error in EDF. AED6 - Internal logic error in EDF. AED7 - TWA size too small for CEDF transaction. AEIA - ERROR. AEID - EOF. AEIE - EODS. AEIG - INBFMH. AEIH - ENDINPT. AEII - NONVAL. AEIJ - NOSTART. AEIK - TERMIDERR. AEIL - FILENOTFOUND. AEIM - NOTFND. AEIN - DUPREC. AEIO - DUPKEY. AEIP - INVREQ. AEIQ - IOERR. AEIR - NOSPACE. AEIS - NOTOPEN. AEIT - ENDFILE. AEIU - ILLOGIC. AEIV - LENGERR. AEIW - QZERO. AEIZ - ITEMERR. AEI0 - PGMIDERR. AEI1 - TRANSIDERR. AEI2 - ENDDATA. AEI3 - INVTSREQ. AEI4 - EXPIRED. AEI8 - TSIOERR. AEI9 - MAPFAIL. AEMB - Task abended by DFHUEM during EXEC CICS ENABLE. AEMQ - Task abended by DFHUEM. AEXK - END. AEXL - DISABLED. AEXV - VOLIDERR. AEXW - SUPPRESSED. AEXX - TASKIDERR. AEXY - TASK PURGED. AEXZ - DISASTROUS CICS ERROR. AEX0 - TCIDERR. AEX1 - DSNNOTFOUND. AEYA - INVERRTERM. AEYB - INVMPSZ. AEYC - IGREQID. AEYE - INVLDC. AEYG - JIDERR. AEYH - QIDERR. AEYJ - DSSTAT. AEYK - SELNERR. AEYL - FUNCERR. AEYM - UNEXPIN. AEYN - NOPASSBKRD. AEYO - NOPASSBKWR. AEYP - SEGIDERR. AEYQ - SYSIDERR.

127068056.doc.doc

Pag. :43 de 52

Altair (Modulo de Clientes) AEYR - INCINVREQ. AEYT - ENVDEFERR. AEYU - IGREGCD. AEYV - SESSIONERR. AEYX - USERIDERR. AEYY - NOTALLOC. AEYZ - CBIDERR. AEY0 - INVEXITREQ. AEY1 - INVPARTNSET. AEY2 - INVPARTN. AEY3 - PARTNFAIL. AEY6 - Internal logic error in DFHUEM. AEY7 - NOTAUTH. AEY8 - Too little dynamic storage requested. AEY9 - Invalid EXEC CICS command issued. AEXS - DL/I call parameter storage above 16 megabytes. AEXT - DL/I call parameter list above 16 megabytes. AFCA - File disabled. AFCM - Data tabla load failed. AFCX - Unexpected response from DFHTMP. AFCY - Task purged during file request. AFCZ - Disastrous error response from DFHFCVS. AFC1 - Disastrous error during open or close file. AFC2 - Disastrous error from DFHFCFS on open file request. AFC3 - Disastrous error from DFHFCFS on open file request. AFC4 - Disastrous error from DFHFCVS to DFHFCP. AFC5 - Disastrous error from DFHFCVS to DFHEFC. AFC6 - Disastrous error from DFHFCVS to DFHDBP. AFC7 - Disastrous error response from DFHFCFS. AFC8 - Disastrous error from DFHFCVS to DFHDMPCA. AFC9 - Task attmpted to update file that failed backout. AICA - Runaway task. Caida por tiempo. Bucle. AICB - RETRIEVE WAIT reissued in system shutdown. AICC - Bad response from a TI request. AICD - Bad response from a KE request. AICE - Bad response from a DS request. AICF - Bad response from an XM request. AICG - Exception response from DS with reason code TASK_CANCEL. AISA - Illegal mirror attach - Invalid facility. AISB - Errors detected in data for mirror transaction. AISC - TIOA not received from terminal by mirror transaction. AISD - Mirror program received non-zero return code. AISE - No DL/I fupport for DFHISP. AISF - Facility for mirror is LU6.2, conversation unmapped. AISG - Mirror transaction could not send reply. AISH - Illegal invocation of CSNC. AISI - Invalid function shipping request. AISJ - Session recovery transaction CSRI could not be attached. AISK - Mirror transaction abended. AISL - LU services manager illegally started. AISM - Macro level request for remote system. AISN - CSNC failed to acquire suspend token. AISO - CSNC failed to suspend itself. AISP - Invalid principal facility. AISS - Security violation at start of LU6.2 conversation. AIST - Unexpected return code after DFHTC TYPE=LOCATE. AJCA - I/O error in journal data set. AJCB - Attempt to switch volumes failed. AJCC - Transaction identifier CSJC illegally entered at terminal.

127068056.doc.doc

Pag. :44 de 52

Altair (Modulo de Clientes) AJCD - Error on call to SM domain. AJCE - Task purged before GETMAIN completed. AJCF - Error on call to DS domain. AJCG - Task purged before WAIT request to DS completed. AJCN - Llenado log. Poner checkpoint. AJCR - CRUCIAL journal unavailable. AKCA - DFHKCP not built correctly. AKCB - Task control restart failure. AKCE - Write to system log failed. AKCF - Write to restart data set failed. AKCR - Task control received an invalid request code. AKCS - Deadlock timeout has occurred. AKCT - Terminal read timeout has occurred. AKCV - Bad return code resume of suspended task. AKC1 - DFHKC WAIT when ECB already marked as waiting. AKC2 - Internal CICS logic error. AKC3 - Purge request issued for task. AKC4 - Serious error occurred on transaction attach. AKC5 - Serious error occurred in a DFHKC ENQ call. AKC6 - DFHKC SUSPEND did not precede DFHKC RESUME. AKC7 - Bad response from an XMSU call. AKC8 - Bad response from call to kernel for task purge. AKEA - Program check detected by KE domain. AKEB - Operating system abend detected by KE domain. AKEC - Runaway detected by kernel domain. AKEF - Error detected while performing KE domain request. AKSE - No code for keyword. AMAC - Unsupported macro-level request. AMI1 - Bad response when mirror task resume. AMNA - Exception response from MN domain - invalid DATA1. AMNB - Exception response from MN domain - invalid DATA2. AMNZ - Unexpected error response from MN domain. AMSA - SBA not followed by address. AMSB - Internal logic error in DFHMSP. AOCA - Error opening VSAM ESDS. APCA - Program control restart failure. APCB - DFHPCP not built correctly - DFHPCQ or DFHPCLI missing. APCC - ANS COBOL programs not supported. APCD - Write to system log failed. APCE - Write to restart data set failed. APCF - Program not compiled with PL/I compiler. APCG - Transaction purged. APCH - COBOL II programs not supported. APCI - Request for PL/I program after PL/I = NO or start up. APCJ - C/370 does not recognize program. APCK - Execution of C program disabled. APCL - PL/I shared library support not available. APCM - TYPE parameter of DFHPC macro not recognized. APCN - Resident control count has gone negative. APCO - Program or map exceeds maximun permitted size. APCP - I/O error when loading program. APCQ - Storage request purged. APCR - Invalid request to program control. APCT - Requested program not found, disbled, or zero length. APCU - Storage request failed, not purged. APCV - FREEMAIN request failed due to error from loader. APCY - Macro request from PL/I or COBOL program. APC1 - Request for TGT exceeding 64k in size. APP1 - Abnormal GET response code.

127068056.doc.doc

Pag. :45 de 52

Altair (Modulo de Clientes) APP2 - Data length too small. APP3 - Illegal request to nonprinter. APR1 - Abnormal PUT response code. APSJ - Spooler illegaly invoked. APST - SPOOL command without NOHANDLE. APSU - Invalid JES return code to spooler. APSV - Invalid MVS macro return code to spooler. APSW - Abend in spooler subtask. APSX - Invalid parameter. APSY - Error return, MVS macro. APSZ - Error return, JES. APUA - Internal error. APUB - Internal error. APUC - Internal error. APUD - Unable to load RDO table. APUE - Unable to load RDO table. APUF - RDO table invalid or missing. APUG - Internal error. APUH - Internal error. APUI - Internal error. APUJ - Internal error. APUK - Unable to obtain storage. APUL - Unrecognized resource type code (FLATTEN). APUM - Unrecognized resource type code (TRANCASE). APUN - Unrecognized resource type code (COMPARE). APUO - Unrecognized resource type code (BACKTRANS). APUP - Error processing language definition table. APUQ - Error processing language definition table. APUR - Data type conflict. APUS - Invalid length for keyword. APUT - Invalid keyword existence bit. APUZ - Invalid definition type in CSD record. ARCA - Recovery control restart task failure. ARCB - Transaction backout exit program cannot be enabled. ARLI - CSLG not initiated. ARPA - Severe error when signing off user of CRTE transaction. ARTA - Principal facility not terminal. ARTB - No input TIOA, or data length zero. ARTC - Link not usable. ARTD - Logic error in DFHRTE. ARTE - Error in I/O to or from temporary storage. ARTF - Illegal attempt to use CRTE. ARTG - Profile not found. ASCB - Disaster response from request to storage domain. ASCF - Invalid FREEMAIN address. ASCP - Insufficient contiguous storage for GETMAIN. ASCR - Illegal storage control request. ASFA - Internal logic error in DFHSFP. ASFB - Attempt to execute CICS sign-off without an associated terminal. ASNA - Internal logic error in DFHSNP. ASNB - Attempt to execute CICS signon without an associated terminal ASNC - Signon program failed to send request to user. ASPD - Error resetting dynamic log. ASPE - Rollback without dynamic transaction backout. ASPL - Error writting sync point. ASP1 - Error during sync point. ASP2 - Sync point attempted with invalid ISC links. ASP3 - No sync point in remote system.

127068056.doc.doc

Pag. :46 de 52

Altair (Modulo de Clientes) ASP5 - Principal facility not owned by task. ASP6 - Flush failed. ASP7 - Resource manager failed request. ASP8 - Sync point rollback not supported. ASP9 - Free TCTTE failed. ASRA - Program interrupt. ASRB - Operating system abend. ASRC - Interrupt in PL/I program. ASRD - Ilegal Macro. (Vers. 3.3) ATCA - DFHTC issued during request. ATCB - Two consecutive reads or writes without intervening wait. ATCC - More than one write or read. ATCD - No supporf for VTAM or ZCP function. ATCE - No TIOA for write. ATCF - Illegal DFHTC CTYPE macro. ATCG - Illegal read or write. ATCH - Transaction purge. ATCI - Transaction purge. ATCJ - Illegal autoinstall invocation. ATCK - Illegal write. ATCL - Error during auto journaling or auto logging. ATCM - Error writing sync point. ATCN - Error during auto journaling or auto logging. ATCO - Unsupported function. ATCP - Error writing to system log. ATCQ - Temporary storage error. ATCR - Temporary storage error. ATCS - Send data after request change direction received. ATCT - Surrogate TCTTE creation failed. ATCU - Send in receive mode. ATCV - Application request to remote system failed. ATCW - No DFHPCT TYPE=PROFILE. ATCX - A domain call resulted in an error response. ATCY - Error processing inbound FMH. ATC1 - Terminal control restart task failure. ATC2 - VTAM rejected open request. ATDD - Transient data destination is disabled. ATDI - Illegal transient data destination type. ATDL - Error writing to system log. ATDT - Invalid transient data request. ATDV - Additional information for ATDD. ATDY - Transient data initialization failed. ATDZ - CICS function failed. ATNA - NACP identifier entered, but no error. ATND - Task termination postponed. ATNI - Task terminated by NEP (VTAM). ATNI - Task terminated by TEP or TACP. ATPA - Error occurred estimating the length of a CICS message. ATPB - Error occurred trying to retrieve a CICS message. ATPC - Error occurred estimating the length of a CICS message. ATPD - Error occurred trying to retrieve a CICS message. ATPE - Task purged before GETMAIN completed. ATPF - Error on call to storage domain. ATRA - Task terminated request by DFHTRAP. ATSA - Temporary storage restart task failure. ATSB - Temporary storage restart task failure. ATSC - Task canceled during temporary storage command. ATSD - Bad response from dispatcher domain. ATSL - Error writing to system log.

127068056.doc.doc

Pag. :47 de 52

Altair (Modulo de Clientes) ATSP - DATAID currently in use, or purge not synchronized. ATSS - Error processing VSAM request. ATUF - Insufficient storage for parameter list for DYNALLOC SVC. AUEP - User exit program sent return code UERCPURG to user exit handler. AVSA - Non-terminal facility for mirror transaction. AVSB - Error in data for mirror transaction. AVSD - Nonzero return code for mirror transaction. AVSF - Mirror program attached in unsupported manner. AVSG - Mirror program could not send reply. AVSP - Invalid facility for mirror transaction. AXFA - File control request keylength zero. AXFB - Illegal FMH type. AXFC - Illegal request. AXFD - Illegal request for remote system. AXFE - Transformation does not exist. AXFF - Illegal queue organization. AXFG - Illegal argument number in FMH data. AXFH - Illegal argument in FMH data. AXFI - Zero data length for TD request. AXFJ - Non-SNA error code. AXFK - DL/I request not supported. AXFL - Null chain of data received. AXFM - SYSIDERR condition raised. AXFO - Check on DS and DBA parameters failed. AXFP - No second FMH received. AXFQ - FMH too short or too long. AXFR - Data too long. AXFS - Path call to retrieve large segments, or excessive expansion of segments. AXFT - I/O area too large. AXFU - Invalid two-level cursor. AXFV - Unsupported local databases. AXFW - No length field in read for update. AXFX - Remote system does not support full sync point protocols. AXFY - LU6.2 conversation failure for attach between CICS systems. AXFZ - Invalid function shipping request. AXF0 - Task purged because of insufficient storage in DSA or EDSA. AXF1 - Unexpected return code from storage module DFHSMGF. AXF2 - Task purged because of insufficient storage in DSA. AXF3 - Unexpected return code from storage module DFHSMMC. AXSA - Security control task failed. AXSB - Failure in CICS code associated with RACF checking. AXTA - Data length calculation failed. AXTB - Get TIOA failed. AXTC - Data transform failed. AXTD - No TIOA received. AXTE - Data not long enough. AXTF - No relay process FMH received. AXTG - Data transform failed. AXTH - Term1 ID not found. AXTI - Request byte LUCOPNO invalid. AXTJ - Unexpected combination of bit settings in XTSSTAT and XTSTCOPC. AZCA - DFHZARM conversation state conflict. AZCB - Error data not received or illegal. AZCC - Unsupported function management data. AZCD - DFHZARM invalid data length received. AZCE - DFHZARM length received too large. AZCF - Invalid request to DFHZARL.

127068056.doc.doc

Pag. :48 de 52

Altair (Modulo de Clientes) AZCG - Invalid TCTTE. AZCH - DFHZARM remote system violated LU6.2 architecture. AZCI - Invalid sync level. AZCJ - Structured field not supported. AZCP - Allocation request not satisfied. AZI1 - IRC transmission protocol violated. AZI2 - IRC transmission failed. AZI3 - Conversation failed. AZI4 - IRC link to connected transaction down. AZI5 - IRC input violated protocol. AZI6 - IRC connected transaction abended. AZI7 - Wait during MOR request prematurely terminated. AZI8 - Incorrect format for error log data. AZI9 - Transaction purged during wait. AZIA - Transaction request for storage rejected. AZIB - Transaction purged while waiting for storage. AZTA - Principal facility not terminal. AZTF - Invalid TCTTE GETMAIN or FREEMAIN request. AZTG - Principal facility not intersystem TCTTE. AZTH - Error response from remote terminal control macro. AZTI - Terminal not defined as remotely owned. AZTJ - VTAM request on non-VTAM terminal. AZTK - Non-VTAM request on VTAM terminal. AZTL - Request to invalid terminal. AZTM - Data has no FMH. AZTN - Conversation terminated. AZTO - TCTTE ownership chain error. AZTP - BMS STORE request failed. AZTQ - Invalid BMS data received. AZTR - BMS PAGEOUT request failed. AZTS - Data ship failed. AZTU - Link TCTTE not owned after sync point. AZTV - Invalid FMH received. AZTW - Attach request to task already running. AZTX - Attach request to task already in routing session. AZTY - Maximun APPC sessions limit reached. AZTZ - Relay program DFHCRT attached in unsupported manner. AZT1 - Task attached improperly during transaction routing. DSNC - DB2 abend code. DHxx - EXEC DL/I error or invalid status code, xx = status code. 0100 - Transiator error opening listing data set. 0101 - Transiator program check. 1029 - Error carga programa. Parar y arrancar CICS.

CONDICIONES EXCEPCIONALES ____________________________


DSIDERR - Error de identificacion de ficheros o del conjunto de datos. MANDATOS - Delete, Read, Readnext, Readprev, Rewrite, Startbr, Unlock, Write. DUPKEY - En VSAM - mas registros con la misma clave alternativa. Clave duplicada cuando se usan indices alternativos en

127068056.doc.doc

Pag. :49 de 52

Altair (Modulo de Clientes) Vsam. MANDATOS - Read, Readnext, Readprev. DUPREC - Registro duplicado en el conjunto de datos. MANDATOS - Write. ENDDATA - No mas datos en tareas iniciadas por IC. MANDATOS - Retrieve. ENDFILE - Final de fichero. MANDATOS - Readnext, Readprev. EXPIRED - Intervalo de tiempo expirado. MANDATOS - Delay, Post. IBERROR - Error de Entrada / Salida. MANDATOS - Delete, Journal, Read, Readnext, Readprev, Readq td, Readq ts, Resetbr, Retrieve, Rewrite, Start, Startbr, Unlock, Wait journal, Write, Writeq td, Writeq ts. ILLOGIC - Errores logicos VSAM. Peticion ilogica. MANDATOS - Delete, Endbr, Read, Readnext, Readprev, Resetbr Rewrite, Startbr, Unlock, Write. INVERRTERM - Invalido id de terminal erroneo. MANDATOS - Route. INVMPSZ - Mapa demasiado grande para el area de representacion de la pantalla. MANDATOS - Receive map, Send map. INVREQ - Peticion invalida. (Definicion de areas de datos con Return. Identificacion de una Transid para una transaccion no asociada con un terminal). (la longitud de los datos es cero o excede la longitud del intervalo del control del conjunto de datos auxiliar. MANDATOS - Assign, Cancel, Delay, Delete, Endbr, Post,Read, Readnext, Readprev, Resetbr, Retrieve, Return, Rewrite, Send map, Send page, Send text, Start, Startbr, Wait journal, Write, Writeq ts. INVTSREQ - No hay soporte para peticiones TS-READ. MANDATOS - Retrieve. IOERR - Error de Entrada / Salida en disco, en ts, etc.

ITEMERR - Error en el numero de item en peticion de TS. El numero de items esta fuera de los limites asignados a la cola, o la cola no puede ser encontrada. MANDATOS - Readq ts, Write ts. JIDERR - Error identificacion diario. MANDATOS - Journal, Wait journal. LENGERR - Error longitud. El registro recuperado es demasiado largo para el area de datos del programa indicado en el mandato. MANDATOS - Converse, Issue receive, Journal, Read, Readnext Readprev, Readq td, Readq ts, Receive, Retrieve, Rewrite,

127068056.doc.doc

Pag. :50 de 52

Altair (Modulo de Clientes) Write, Writeq td. MAPFAIL - Datos a ser exhibidos tienen longitud 0, o no contienen una secuencia de comienzo de direccion de buffer (SBA). Esta condicion suele ocurrir al comienzo de una transaccion cuando la primera entrada de terminal procede de una pantalla sin formato. MANDATOS - Receive map. NOSPACE No hay espacio para aadir registros. MANDATOS - Write, Writeq td, Writeq ts. NOSTG No hay memoria. MANDATOS - Getmain. NOTFND Registro no encontrado. MANDATOS - Cancel, Delete, Read, Readnext, Readprev, Resetbr, Retrieve, Startbr. NOTOPEN No abierto. El conjunto de datos especificados no esta abierto. MANDATOS - Delete, Journal, Read, Readnext, Readprev, Readq td, Resetbr, Rewrite, Startbr, Unlock, Wait journal, Write, Writeq td. OVERFLOW Overflow en terminal. MANDATOS - Send map. PGMIDERR El programa no esta en la PPT o esta inutilizable. MANDATOS - Link, Xctl. PQMIDERR Programa no encontrado. MANDATOS - Handle Abend, Link, Load, Release, Xctl. PRMIDERR El programa, mapa o tabla no esta en la PPT, o no esta disponible. MANDATOS - Handle Abend, Link, Load, Release, Xctl. QBUSY Cola vacia. Tambien ocurre si se intenta una peticion de lectura de cola td mientras otra esta escribiendo en esta cola, solo para datos intraparticion, la accion del sistema es esperar hasta que se completa la operacion de salida. MANDATOS - Readq td. QIDERR Error en identificacion Td o Ts. MANDATOS - Delete td, Delete ts, Readq td, Readq ts, Writeq td. QZERO La cola Td esta vacia. MANDATOS - Readq td. RETPAGE Si opcion Set es especificada y hay una o mas paginas dispuestas. MANDATOS - Send map, Send page, Send text. RTEFAIL Si se especifica el terminal que inicia la transaccion. MANDATOS - Route.

127068056.doc.doc

Pag. :51 de 52

Altair (Modulo de Clientes) RTESOME Si alguna de las terminales especificadas no recibe el mensaje. MANDATOS - Route. TERMIDERR Error en id-terminal. MANDATOS - Issue copy, Start. TRANSIDERR Error en id-transaccion. MANDATOS - Start. TSIOERR Error en Ts. MANDATOS - Purge message, Send map, Send page, Send text. ASRA en un entorno CICS. ----------------------Localizar la PSW al comienzo del DUMP. Con sus tres ultimos bytes se tiene la direccion de la siguiente instruccion a la que dio el problema. En assembler y con el listado de la compilacion resulta facil ver cual fue la intruccion que dio problemas. Para localizar los datos problematicos, recurrir a los registros, que tambien se encuentran al principio del DUMP. Como alternativa de puede hacer una aproximacion visual de la working en TRANSACTION STORAGE USER. En Cobol hacerlo por diferencias de entre la direccion de rotura y la de carga. Con esta direccion se mira el listado de compilador y se obtiene la instruccion.

127068056.doc.doc

Pag. :52 de 52