Release 3.1 SPI 10 15 - spansoftware.com · the SQLCODE, SQLSTATE and SQLERRM fields. SPICE uses...

SPICES p a n I n t e g r a t e d C h e c k p o i n t / R e s t a r t E n v i r o n m e n t

SPICE SQL™ & SPICE DL/I™Diagnostic Reference Manual

Release 3.1

SPI 10 15

Span Software Consultants Limited

Lit t le Moss, Peacock LaneHigh LeghKnutsfordCheshireWA16 6PLUNIT ED KINGDOM

T elephone: +44 (0) 1565 832999Fax: +44 (0) 1565 830653email [email protected] website httl://www.spansoftware.com

© Copyright 1991, 2009 Span Software Consultants Limited.All rights reserved. No part of this publicat ion may be re-produced,stored in a retrieval sy st em o r t ransmit ted, in any form or by anymeans, electronic, mechanical, or otherwise, without the prior writ tenconsent of the publisher.

18 June 2009

mailto:[email protected]

http://www.spansoftware.com

ii SPICE SQL™ and SPICE DL/I™ Diagnost ics Reference Manual© 1991,2009 Span Software Consultants Limited 18 June 2009

Preface

Abstract

SPICE is an acronym for Span Integrated Checkpoint/Restart Environment.

SPICE SQL™ and SPICE DL/I™ are software products that simplify the design,implementation and operation of restartable batch application programs in the DB2 andIMS environments, respectively.

This manual is the reference for messages and other diagnostic indicators issued by theSPICE™ products.

Other SPICE Manuals

SPI 08 SPICE SQL™ Product Reference ManualThe principal reference for SPICE SQL, the SPICE product for the DB2 environment.

SPI 09 SPICE DL/I™ Product Reference ManualThe principal reference for SPICE DL/I, the SPICE product for the IMS environment.

SPI 14 SPICE SQL™ & SPICE DL/I™ Getting StartedThe reference for the installation of the SPICE products.

Note:SPICE, SPICE SQL, SPICE DL/I and In-Flight Restart are trademarks of Span Software

Consultants Limited.

IBM, DB2, IMS, CICS, z/OS and OS/390 are trademarks of the International BusinessMachines Corporation.

Contents iii18 June 2009 © 1991,2009 Span Software Consultants Limited

Contents

Chapter 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Using This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1SPICE SQL & SPICE DL/I Program Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 2. SPICE SQL™ and SPICE DL/I™ Messages. . . . . . . . . . . . . . . . . . . . . . 3

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Identification Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

SQL Statement Identification Message 3Job Identification Message 4

Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Messages SPI0000-SPI0099. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Messages SPI0100-SPI0199. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Messages SPI0200-SPI0299. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Messages SPI0300-SPI0399. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Messages SPI0400-SPI0499. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Messages SPI0500-SPI0599. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Messages SPI0600-SPI0699. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Messages SPI0700-SPI0799. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 3. SPICE SQL™ SQLCA and SRACA Codes. . . . . . . . . . . . . . . . . . . . . . 31

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

SPICE CODE, STATE & ERRM Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Chapter 4. SPICE DL/I™ and SPICE Restart API Status Codes. . . . . . . . . . . . . . . 41

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

SPICE Status Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 5. SPICE SQL™ and SPICE DL/I™ User Abend Codes. . . . . . . . . . . . . . . 45

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

User Abend Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 6. SPICE SQL™ and SPICE DL/I™ Internal Failure Codes. . . . . . . . . . . 47

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Internal Failure Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 7. SPICE™ Formatted Dump Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Formatted Dump Sections.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57SPICE Failure Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57SPICE Control Blocks and IMS PSB Contents. . . . . . . . . . . . . . . . . . . . . . . . . 58SCP Control Blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Introduct ion 118 June 2009 © 1991,2009 Span Software Consultants Limited

Chapter 1. Introduction

Using This Manual

This manual is the principal reference for the diagnostic messages and codes issued bySPICE SQL and SPICE DL/I.

• Chapter 1. Introduction on page 1This chapter is an introduction to SPICE diagnostics.

• Chapter 2. SPICE SQL™ and SPICE DL/I™ Messages on page 3The messages issued by SPICE SQL and SPICE DL/I.

• Chapter 3. SPICE SQL™ SQLCA and SRACA Codes on page 31The diagnostic information returned by SPICE to the application program. It isorientated towards programmers writing SQL application programs.

• Chapter 4. SPICE DL/I™ and SPICE Restart API Status Codes on page 41The diagnostic information returned by SPICE to the application program. It isorientated towards programmers writing DL/I application programs.

• Chapter 5. SPICE SQL™ and SPICE DL/I™ User Abend Codes on page 45The abend codes issued by SPICE SQL and SPICE DL/I.

• Chapter 6. SPICE SQL™ and SPICE DL/I™ Internal Failure Codes on page 47The failure codes issued by SPICE SQL and SPICE DL/I.

• Chapter 7. SPICE™ Formatted Dump Contents on page 57The contents of the SPICE formatted dump. It is intended for systems programmersresponsible for notifying the vendors of SPICE SQL and SPICE DL/I of problemsexperienced while executing the products.

A number of entries in this manual suggest that problems be referred to the technicalsupport team responsible for SPICE. These entries highlight situations that couldindicate problems in the SPICE products. Resolution of such problems may require thattechnical support personnel consult with the vendors of the SPICE software.

SPICE SQL & SPICE DL/I Program Diagnostics

When processing SPICE requests issued via SQL statements, SPICE SQL returnsdiagnostic information in the SQL communication area, the SQLCA. It returns the data inthe SQLCODE, SQLSTATE and SQLERRM fields. SPICE uses the same values as thosereturned by DB2, in similar circumstances. Chapter 3 documents the values that thesefields can take.

For SPICE requests issued via DL/I statements, SPICE DL/I returns diagnosticinformation in the request PCB. It returns the data in the status code field. SPICE usesthe same values as those returned by IMS, in similar circumstances. Chapter 4documents the values that this field can take.

When the SPICE Restart API is used to issue SPICE requests, SPICE SQL returnsdiagnostic information in the SPICE Restart API communication area, the SRACA. Itreturns the data in the SRACODE, SRASTATE, SRAERRM and SRASTAT fields. Thevalues conform to those returned by DB2 and IMS, in the SQLCODE, SQLSTATE and

2 SPICE SQL™ and SPICE DL/I™ Diagnost ics Reference Manual© 1991,2009 Span Software Consultants Limited 18 June 2009

SQLERRM fields of the SQLCA and the status code field of the IMS PCB, respectively. Chapters 3 and 4 document the values.

SPICE SQL™ and SPICE DL/I™ Messages 318 June 2009 © 1991,2009 Span Software Consultants Limited

Chapter 2. SPICE SQL™ andSPICE DL/I™ Messages

IntroductionSPICE messages are prefixed “SPInnnnc”, where “nnnn” is the number of the messageand “c” indicates the message type. The message type can be “I”, “W” or “A”. Messages suffixed “I” are for information only. Messages suffixed “W” are warningmessages and indicate a condition that the operator may wish to take action upon, bycancelling the job, or notifying the user, for example. Messages suffixed “A” indicate acondition that the operator must take action upon, reply to a message for instance.

For each SPICE message the following information is provided:Explanation: What the message means; why it occurred; what caused it.

Explanations specific to a particular product are labelled appropriately,SPICE SQL Explanation for instance.

System Action: What SPICE will do as a result of the condition.Programmer and/or Operator Response: What the programmer and/or operator

should do when the condition occurs.

Identification Messages

The messages issued by SPICE to the z/OS operator and z/OS job log are accompaniedby one or more identification messages. These messages are prefixed by the text “. . .”. The following example illustrates their format:

17.42.23 JOB 1234 +SPI0504I SQL REQUEST FAILURE: OMITTED VALUE17.42.23 JOB 1234 + ... SQL SELECT FROM SPIVCOBA STATEMENT NUMBER 089817.42.23 JOB 1234 + ... JOB=SPICETST, STEP=DSNTIRU , PROGRAM=SPICOBA

Example 2.1: SPICE job log message

The example shows both types of identification message. The first documents whichSQL statement caused the message to be written, and the second which job and stepgenerated the message.

SQL Statement Identification MessageSPICE messages that derive from the processing of an SQL statement are immediatelyfollowed by the following message.

... SQL type REQUEST FROM module STATEMENT NUMBER n

• This message identifies the program module, type and number of the SQLstatement that has resulted in the preceding message.• SPICE SQL extracts the reported statement number from the DB2 parameter

list, from field SQL-STMT-NUM. The DB2 pre-compiler generates theparameter list, and the statement number is unique within the module.

Use the following procedure to locate the identified SQL statement in a COBOLprogram:1) Examine the compilation listing for the reported module and locate the instance of

variable SQL-STMT-NUM with the reported value.2) Note the name of the structure of which it is part. It will be in the form

SQL-PLISTnn, where nn is numeric.3) Scan the compilation listing for a statement specifying the structure located in

the preceding step in the format:


CALL 'DSNHLI' USING SQL-PLISTnn4) Observe the SQL statement immediately preceding this call, commented out by

the DB2 pre-compiler. This is the SQL statement identified by the message.

Topic SPICE SQL Programming Diagnostics in SPICE SQL Product ReferenceManual contains further information..

Job Identification MessageThe following message follows most SPICE messages issued to the z/OS operator. Itidentifies the job name, job step name and program name. SPICE identifies the SPICESAM file that the message relates to, when appropriate.

... JOB=jjjjjjjj, STEP=ssssssss , PROGRAM=mmmmmmmm[,PSB=pppppppp] [,SSAM DDNAME=dddddddd]

This message identifies the job, the step and the program using SPICE. SPICE DL/Ialso identifies the IMS PSB. If the condition relates to a SPICE SAM file it alsoidentifies the file DD name.

Messages

• Messages SPI0000-SPI0099 on page 4• Messages SPI0100-SPI0199 on page 9• Messages SPI0200-SPI0299 on page 13• Messages SPI0300-SPI0399 on page 15• Messages SPI0400-SPI0499 on page 17• Messages SPI0500-SPI0599 on page 23• Messages SPI0600-SPI0699 on page 26• Messages SPI0700-SPI0799 on page 27

Messages SPI0000-SPI0099

SPI0000I *ABEND* SPICE INTERNAL ERROR, CODE xSPI0000I *ABEND* SPICE PARSING INTERNAL ERROR, CODE xExplanation: This message is is sued when SPICE determines an error from which it cannotrecover, and which cannot be attributed to an error by the application program, or user. The firs tvariant of the message is is sued by the SPICE application interface, and the second by the SPICEutility program command pars ing routines . The failure codes are documented in Chapter 6 of thismanual.System Action: The SPICE application interface will ABEND with user code 4090, for the firs tvariant of the message. For the second variant the SPICE utility program, SPIUTI00, willABEND with user code 4091.Programmer/Operator Response: Refer the problem to your technical support team respons iblefor SPICE.

SPI0002I DDNAME NOT FOUND FOR SPICE SAM FILEExplanation: An attempt was made to open a SPICE SAM file for which no file was allocated

in the job s tep.SPICE SQL System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of“SR002” in the reques t SQLCA.

SPICE DL/I System Action: SPICE will return a s tatus code of “AI” in the reques t PCB.

SPICE Restart API System Action: SPICE will return an SRACODE of -681, an SRASTATEof “SR002” and an SRASTAT of “AI” in the reques t SRACA.

Programmer/Operator Response: Correct the problem and res tart the job.


SPI0004W SSAM I/O REQUEST WHEN RESTART REQUIREDSPICE SQL Explanation: SPICE loses synchronization with DB2 if the database updates arebacked out, without the SPICE SAM file pos itions , or the res tart program areas , being reset. Thisoccurs when the program issues an SQL “ROLLBACK” statement, or when SPICE detects acondition that reflects database backout, SQLCODE of -911 for ins tance. If the programcontinues process ing, SPICE will be unable to res tart cons is tently. This message is is sued on thefirs t SPICE SAM reques t after SPICE loses synchronization. Synchronization can be res tored bythe program issuing a SELECT to the SPICE_PAM table.SPICE DL/I Explanation: SPICE loses synchronization with IMS if the databases are backedout, without the SPICE SAM file positions , or the res tart program areas , being reset. This occurswhen the program issues a DL/I “ROLB” call, or if SPICE detects a condition that reflectsdatabase backout, PCB s tatus code of “FD” for ins tance. If the program continues process ing,SPICE will be unable to res tart cons is tently. This message is is sued on the firs t SPICE DL/I SAMreques t after SPICE loses synchronization. Synchronization can be res tored by the program re-issuing its “XRST” call.

SPICE Restart API Explanation: SPICE loses synchronization with the database managementsys tem if the database updates are backed out, without the SPICE SAM file pos itions , or theres tart program areas , being reset. This occurs when the program issues a rollback reques t, orwhen SPICE detects a condition that reflects database backout, SQLCODE of -911 for ins tance. If the program continues process ing, SPICE will be unable to res tart cons is tently. This message isissued on the firs t SPICE SAM request after SPICE loses synchronization. Synchronization canbe res tored by the program issuing a program area declaration s tatement.

System Action: SPICE continues execution.

Operator Response: Consult the operating ins tructions for the application.

SPI0005I SPICE SAM FILE CHANGE OF USE SINCE RESTARTExplanation: An attempt was made to open a SPICE SAM file for input, following a res tart,when the file was previous ly open for output, or vice-versa.

SPICE SQL System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of“SR005” in the reques t SQLCA.

SPICE DL/I System Action: SPICE will return a s tatus code of “AI” in the reques t PCB.SPICE Restart API System Action: SPICE will return an SRACODE of -681, an SRASTATEof “SR005” and an SRASTAT of “AI” in the SRACA.Programmer/Operator Response: Correct the problem and res tart the job.

SPI0006I DL/I REQUEST FAILURE: INVALID OPEN I/O AREASPICE DL/I Explanation: An OPEN reques t was is sued, when the I/O area contained otherthan: “INP”, “OUT”, “OUTA” or “OUTM”.SPICE DL/I System Action: SPICE will return a s tatus code of “AI” in the reques t PCB.

Programmer Response: Correct the problem and res tart the job.

SPI0008I *ABEND* APPLICATION REPOSITION REQUEST AGAINST UNIT RECORD SSAMFILE

SPICE DL/I Explanation: A SPICE DL/I “GU” reques t was made agains t a SPICE SAM filethat could not be re-pos itioned, e.g. a JES SYSIN file.SPICE Restart API Explanation: A re-pos ition reques t was made agains t a SPICE SAM filethat could not be re-pos itioned, e.g. a JES SYSIN file.

System Action: SPICE will ABEND with user code 4090.


SPI0009I OPEN REQUEST WHEN FILE ALREADY OPENExplanation: An OPEN reques t was is sued, when the file was already open.SPICE SQL System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of“SR009” in the reques t SQLCA.


SPICE Restart API System Action: SPICE will return an SRACODE of -681, an SRASTATEof “SR009” and an SRASTAT of “AI” in the reques t SRACA.Programmer Response: Correct the problem and res tart the job.

SPI0012W SPICE SAM FILE REPOSITION NOT SUPPORTED, RESTART WILL NOT BEATTEMPTED

Explanation: The SPICE SAM file being opened cannot be repos itioned, e.g. PDS member,concatenated file or JES SYSOUT or SYSIN file. Upon a res tart SPICE will not be able torepos ition the file.

System Action: SPICE continues execution.

Programmer/Operator Response: Consult the operating ins tructions for the application.


SPI0014I *ABEND* SPICE SAM REQUEST FAILURE, INVALID PCB ADDRESSSPICE DL/I Explanation: An attempt has been made to access a SPICE SAM file through aPCB other than that which was used to open it, and is currently in use.



SPI0018I *ABEND* SPICE ROUTINE rrrrrrrr FAILURE, RETURN CODE = nnnnExplanation: SPICE routine “rrrrrrrr” has returned a non-zero return code “nnnn”.


Programmer/Operator Response: Refer the problem to your technical support team respons iblefor SPICE.

SPI0019I *ABEND* UNSUPPORTED REGION TYPESPICE DL/I Explanation: SPICE DL/I was unable to determine the region type.System Action: SPICE will ABEND with user code 4090.


SPI0020I *ABEND* APPLICATION ATTEMPTED TO ACCESS SPICE RESTART PCBSPICE DL/I Explanation: The application program has made a reques t to the SPICE res tartdatabase PCB.System Action: SPICE will ABEND with user code 4090.


SPI0022I DL/I REQUEST FAILURE: INVALID SSAM FUNCTION CODESPICE DL/I Explanation: An invalid function code was used agains t a SPICE SAM file PCB.

SPICE DL/I System Action: SPICE will return a s tatus code of “AD” in the reques t PCB.


SPI0023I DL/I REQUEST FAILURE: I/O AREA OMITTEDSPICE DL/I Explanation: A DL/I reques t was is sued agains t a SPICE SAM file PCB whichomitted a required I/O area.

SPICE DL/I System Action: SPICE will return a s tatus code of “AB” in the reques t PCB.


SPI0024I DL/I REQUEST FAILURE: SSA OMITTEDSPICE DL/I Explanation: A DL/I reques t was is sued agains t a SPICE SAM file PCB thatomitted a required SSA.

SPICE DL/I System Action: SPICE will return a s tatus code of “AH” in the reques t PCB.


SPI0025I DL/I REQUEST FAILURE: TOO MANY SSA'SSPICE DL/I Explanation: A DL/I reques t was is sued agains t a SPICE SAM file PCB thatspecified too many SSA's .SPICE DL/I System Action: SPICE will return a s tatus code of “AJ” in the reques t PCB.


SPI0026I SPICE SAM FAILURE: INPUT REQUEST AGAINST OUTPUT FILE, OR VICE-VERSASPICE SQL Explanation: The application program has issued a FETCH s tatement agains t anopen output file, or an INSERT to an open input file.SPICE SQL System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of“SR026” in the reques t SQLCA.

SPICE DL/I Explanation: The application program has is sued a GN or GU reques t agains t anopen output file, or an ISRT to an open input file.SPICE DL/I System Action: SPICE will return a s tatus code of “AM” in the reques t PCB.

SPICE Restart API Explanation: The application program has is sued an input s tatementagains t an open output file, or vice-versa.

SPICE Restart API System Action: SPICE will return an SRACODE of -681, an SRASTATEof “SR026” and an SRASTAT of “AM” in the reques t SRACA.Programmer/Operator Response: Correct the problem and res tart the job.


SPI0027I DL/I REQUEST FAILURE: I/O AREA INAPPROPRIATESPICE DL/I Explanation: A DL/I reques t was is sued agains t a SPICE SAM file PCB thatspecified an I/O area, when one was not required.SPICE DL/I System Action: SPICE will return a s tatus code of “AT” in the reques t PCB.


SPI0028I SPICE SAM FAILURE: REQUEST AGAINST UNOPENED FILEExplanation: The application program has is sued a close reques t agains t a SPICE SAM file thatis not open, or any reques t agains t a file that could not be opened.SPICE SQL System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of“SR028” in the reques t SQLCA.


SPICE Restart API System Action: SPICE will return an SRACODE of -681, an SRASTATEof “SR028” and an SRASTAT of “AI” in the reques t SRACA.


SPI0030I SPICE SAM FILE OPEN FAILURESPICE SQL Explanation: SPICE SAM was unable to open the file specified in an OPENstatement agains t a SPICE SAM cursor or a SPICE SAM UPDATE s tatement reques ting updatefile open.

This can be caused by re-opening a SPICE SQL sequential file cursor following a commit point. SPICE SQL file cursors remain open following commit points .SPICE SQL System Action: SPICE SQL will return an SQLCODE of “-681” and anSQLSTATE of “SR030” in the SQLCA. Control is returned to the application program.

SPICE DL/I Explanation: An “OPEN” reques t for a SPICE SAM file failed.

SPICE DL/I System Action: SPICE DL/I will return a s tatus code of “AI” in the IMS PCB. Control is returned to the application program.

SPICE Restart API Explanation: An open reques t for a SPICE SAM file failed.

SPICE Restart API System Action: SPICE SQL will return an SRACODE of “-681”, anSRASTATE of “SR030” and an SRASTAT of “AI” in the SRACA. Control is returned to theapplication program.

Programmer/Operator Response: Consult the operating ins tructions for the program.

SPI0031I SPICE SAM RECORD LENGTH EXCEEDS FILE SPECIFICATIONExplanation: The record length of an output reques t agains t a SPICE SAM file exceeds that ofthe file.

SPICE SQL System Action: SPICE will return an SQLCODE of -302 and an SQLSTATE of“SR031” in the SQLCA.SPICE DL/I System Action: SPICE will return a s tatus code of “AF” in the reques t PCB.

SPICE Restart API System Action: SPICE will return an SRACODE of -302, an SRASTATEof “SR031” and an SRASTAT of “AF” in the SRACA.


SPI0032I SPICE SAM FAILURE: RECORD TOO LONG FOR INPUT REQUESTSPICE SQL Explanation: The next record from a SPICE SAM input file is longer than the hos tvariable or hos t s tructure specified in the FETCH s tatement.

This can be caused by ass igning the wrong file to the program. It can also be caused by incorrectspecification of the record I/O area s tructure.SPICE SQL System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of“SR032” in the reques t SQLCA.

SPICE Restart API System Action: SPICE will return an SRACODE of -681, an SRASTATEof “SR032” and an SRASTAT of “AF” in the SRACA.Programmer/Operator Response: Correct the program or file and res tart the job.

SPI0033I SPICE SAM FAILURE: UNSUPPORTED FILE TYPESPICE Explanation: A SPICE SAM statement has been issued agains t a file whose type is notsupported by SPICE SAM.SPICE SQL System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of“SR033” in the reques t SQLCA.


SPICE Restart API System Action: SPICE will return an SRACODE of -681, an SRASTATEof “SR033” and an SRASTAT of “AI” in the SRACA.Programmer/Operator Response: Copy the file to a supported file type and res tart the job.


SPI0035I SPICE SAM OPEN FAILURE, INVALID FILE TYPEExplanation: A SPICE SAM statement has been issued agains t a file whose type is not supportedby SPICE SAM, e.g. ISAM.

SPICE SQL System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of“SR035” in the reques t SQLCA.


SPICE Restart API System Action: SPICE will return an SRACODE of -681, an SRASTATEof “SR035” and an SRASTAT of “AI” in the SRACA.Programmer/Operator Response: Copy the file to a supported file type and res tart the job.

SPI0037I BSAM ABEND IN SSAM PROCESSINGExplanation: An ABEND occurred in BSAM whils t process ing a reques t agains t a SPICE SAMfile.

Poss ible causes of this message are:! During res tart, when a file has been copied incorrectly before res tarting the program. To

copy SPICE SAM files , after abend B37 for ins tance, the procedure detailed in SPICESAM Dataset Recovery/Restart in the appropriate SPICE Product Reference Manualmust be followed.

! Phys ical failure of the dataset.SPICE SQL System Action: SPICE SQL will return an SQLCODE of “-681” and anSQLSTATE of “SR037” in the SQLCA. Control is returned to the application program.

SPICE DL/I System Action: SPICE DL/I will return a s tatus code of “NO” in the IMS PCB. Control is returned to the application program.SPICE Restart API System Action: SPICE will return an SRACODE of -681, an SRASTATEof “SR037” and an SRASTAT of “NO” in the SRACA.


SPI0038I SSAM BSAM I/O ERRORExplanation: SPICE encountered an I/O error whils t process ing a SPICE SAM record reques t. A description of the error will be found in the accompanying “SPI0041I” message.



! Phys ical failure of the dataset.

SPICE SQL System Action: SPICE SQL will return an SQLCODE of “-681” and anSQLSTATE of “SR038” in the SQLCA. Control is returned to the application program.SPICE DL/I System Action: SPICE DL/I will return a s tatus code of “NO” in the IMS PCB. Control is returned to the application program.

SPICE Restart API System Action: SPICE will return an SRACODE of -681, an SRASTATEof “SR038” and an SRASTAT of “NO” in the SRACA.


SPI0039W SSAM FILE CANNOT BE RESTARTED - NO SPICE RESTART DATABASESPICE DL/I Explanation: There is no SPICE IMS res tart database PCB in the PSB. Themessage informs the user that SPICE will be unable to repos ition the indicated file upon anysubsequent res tart from a commit point.

System Action: Control is returned to the application program.


SPI0041I SSAM SYNAD MESSAGE : <SYNADAF text>Explanation: This message documents the error message generated by the BSAM “SYNADAF”macro. It accompanies SPICE message “SPI0038” identifying an I/O error whils t process ing aSPICE SAM reques t. Consult the operating sys tem documentation for an explanation of the“SYNADAF” text.

System Action: See the description of message “SPI0038”.Programmer/Operator Response: See the description of message “SPI0038”.

SPI0042W NON-RESTARTABLE PROGRAM TERMINATEDExplanation: The program, identified in the following job identification message, has completedits execution. The program was not res tartable.




SPI0044W NUMBER OF SSAM BUFFERS SPECIFIED EXCEEDS MAXIMUM, RESET TO 255Explanation: The DCB of the SPICE SAM BSAM file specified more than 255 buffers , themaximum SPICE allows.System Action: SPICE resets the number of buffers to 255, and returns control to the application.

Programmer/Operator Response: Correct the application JCL to prevent the message beingissued again.

SPI0045I SPICE SAM FAILURE: DCB ABEND DURING OPENSPICE Explanation: An ABEND occurred during BSAM file open process ing.

Poss ible causes of this message are:! Invalid file DCB specificationSPICE SQL System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of“SR045” in the reques t SQLCA.


SPICE Restart API System Action: SPICE will return an SRACODE of -681, an SRASTATEof “SR045” and an SRASTAT of “AI” in the SRACA.Programmer/Operator Response: Correct the problem and res tart the job.

SPI0046W *ABEND* BAD RETURN CODE FROM NOTE/POINT/SYNCDEV - RETURN CODE =xxxx, REASON CODE = yyyy

Explanation: SPICE SAM received invalid return code “xxxx”, reason code “yyyy”, from a callto z/OS NOTE, POINT or SYNCDEV.


Operator Response: Consult z/OS documentation for the meaning of the error codesdocumented in the message, correct the problem accordingly, and res tart the job.

SPI0050I NUMBER OF SPICE SAM BUFFERS INADEQUATE FOR REPOSITIONExplanation: Repos ition of a SPICE SAM file, typically performed during res tart, requires morebuffers than are defined. The number of buffers is 8, unless specified explicitly in the programJCL.• This problem can arise following an “x37” abend failure, when the program JCL res tricts the

number of buffers . Recovering the file with the utility “REPRO” command, us ing the defaultnumber of buffers , can result in a repos ition address requiring more buffers than is defined inthe res tart JCL.

SPICE SQL System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of“SR050” in the reques t SQLCA.SPICE DL/I System Action: SPICE will return a s tatus code of “AI” in the reques t PCB.

SPICE Restart API System Action: SPICE will return an SRACODE of -681, an SRASTATEof “SR050” and an SRASTAT of “AI” in the SRACA.

Programmer/Operator Response: Increase the number of buffers for the file, by coding“DCB=BUFNO=value” in the JCL, and res tart the job.


SPI0101I *ABEND* SPICE JOB SUSPENDEDExplanation: SPICE is suspending execution of the job in response to a “CHANGE . . .SUSPEND” command from the SPICE utility program.System Action: SPICE will ABEND with user code 4090.

Programmer/Operator Response: Is sue the SPICE utility “CHANGE . . . RELEASE”command to allow the job to be res tarted from a commit point.

SPI0102I *ABEND* RESTART PSB CHANGED FROM LAST CHECKPOINTSPICE DL/I Explanation: The contents of the PSB used to res tart the program have changeds ince the las t success ful checkpoint.




SPI0104I *ABEND* RESTART PROGRAM AREA LIST CHANGED SINCE LAST CHECKPOINTSPICE DL/I Explanation: The lis t of program areas specified in the las t success ful checkpointcannot be fitted into the areas specified in the “XRST” call.System Action: SPICE will ABEND with user code 4090.


SPI0105W SPICE RESTART DATABASE DBDNAME INVALID, SPICE RESTART NOTAVAILABLE

SPICE DL/I Explanation: The las t update PCB in the PSB beginning “SPIC” does not have aprefix of “SPICH”, “SPICD” or “SPICM”. SPICE cannot use it for a res tart PCB. As SPICE hasno res tart database, it cannot perform SPICE res tart control.

System Action: Control is returned to the application.


SPI0106W NO SPICE RESTART DATABASE IN PSB, SPICE RESTART NOT AVAILABLESPICE DL/I Explanation: The PSB does not contain an update PCB with a prefix of “SPIC”. SPICE cannot find a res tart database PCB. As SPICE has no res tart database it cannot performSPICE res tart control.



SPI0107W SPICE RESTART DISABLED, SPICE RESTART NOT AVAILABLEExplanation: The entry in the SPICE database for the application has been flagged “RESTARTDISABLED”. SPICE will not perform SPICE res tart control.


Programmer/Operator Response: To prevent the message being issued, use the SPICE utility“CHANGE . . . SPICERESTART(YES)” option.

SPI0109I SPICE RESTART DATABASE CANNOT BE ACCESSED - DATABASE NOTINITIALIZED

Explanation: The SPICE res tart database has not been initialized for use by SPICE. It does notcontain a “DEFAULTS” entry.

System Action: If the program is res tartable, SPICE will is sue message SPI0117I and thenABEND with user code 4090. Otherwise, control is returned to the application.Programmer/Operator Response: To prevent a recurrence of the message or ABEND, initializethe database with the SPICE utility program and res tart the job.

SPI0110I [*ABEND*] BAD DL/I STATUS CODE FROM CALL TO SPICE RESTARTDATABASE, FUNCTION=ffff STATUS CODE=cc

SPICE DL/I Explanation: A DL/I call by SPICE DL/I to the res tart database, us ing functioncode “ffff”, returned the unexpected PCB status code “cc”.SPICE DL/I System Action: If the message includes the text “*ABEND*”, SPICE will ABENDwith user code 4090. Otherwise, control will be returned to the application program, with thes tatus code returned in the reques t PCB.SPICE SQL System Action: If the message includes the text “*ABEND*”, SPICE will ABENDwith user code 4090. Otherwise, control will be returned to the application program, with anSQLCODE of “-911” and an SQLSTATE of “SR110” returned in the reques t SQLCA.SPICE Restart API System Action: If the message includes the text “*ABEND*”, SPICE willABEND with user code 4090. Otherwise, control will be returned to the application program,with an SRACODE of “-911”, an SRASTATE of “SR110” and an SRASTAT of the s tatus codein error returned in the reques t SRACA.Programmer/Operator Response: Examine the reported IMS s tatus code. If the cause of theproblem is evident, correct it and res tart the job. If not, refer it to your technical support teamrespons ible for SPICE.

SPI0111I *ABEND* RESTART ENTRY INCOMPLETESPICE SQL Explanation: W hen performing res tart SPICE could not find all of the res tart datafor the job in the res tart database.

SPICE DL/I Explanation: W hen performing res tart SPICE could not find all of the res tart datafor the job in the res tart database. This can be caused by attempting to res tart a SPICE DL/Iprogram without firs t running IMS backout.

SPICE Restart API Explanation: W hen performing res tart SPICE could not find all of theres tart data for the job in the res tart database. This can be caused by attempting to res tart a DL/Iprogram without firs t running IMS backout.



Programmer/Operator Response (SPICE SQL): Refer the problem to your technical supportteam respons ible for SPICE.

Programmer/Operator Response: For IMS batch jobs , check if IMS backout has beenexecuted. If not, run backout and then res tart the job. Otherwise, refer the problem to yourtechnical support team respons ible for SPICE.

SPI0112I PROGRAM RESTARTED FROM ccccccccSPICE SQL Explanation: This message identifies which SPICE SQL commit point SPICE hasres tarted the program from.SPICE DL/I Explanation: This messages identifies which SPICE DL/I checkpoint SPICE hasres tarted the program from.

SPICE Restart API Explanation: This message identifies which SPICE Res tart API commitpoint SPICE has res tarted the program from.System Action: Control is returned to the application.

Programmer/Operator Response: None required.

SPI0113I *ABEND* MSDB RESTART DATABASE FULLSPICE DL/I Explanation: No segments are available in the Fas t Path res tart database for thisapplication.

System Action: SPICE will ABEND with user code 4090.Programmer/Operator Response: Wait until other applications us ing the same database havecompleted, thereby freeing off space, before rerunning the job. Alternatively increase the numberof segments in the database before rerunning.

SPI0115W SPICE COMMIT POINT WHEN RESTART PENDINGSPICE SQL Explanation: SPICE SQL loses synchronization with DB2 if database updates arerolled back, without the SPICE SAM file positions , or the res tart program areas , being reset. Thisoccurs if the program issues an SQL “ROLLBACK” s tatement, or if certain SQLCODEs arereturned from a commit s tatement, e.g. “-911”. This message is issued on the firs t commits tatement reques t after SPICE loses synchronization with DB2.

System SQL Action: SPICE SQL continues execution, but suspends SPICE commit process ing. SPICE preserves the res tart data for the program until it reques ts SPICE in-flight res tart, or until itterminates .SPICE DL/I Explanation: SPICE DL/I loses synchronization with IMS if the databases arebacked out, without the SPICE SAM file pos itions , or the res tart program areas , being reset. Thisoccurs if the program issues a “ROLB” call, or if certain PCB s tatus codes are returned from acheckpoint call, e.g. “FV”. This message is issued on the firs t checkpoint reques t after SPICEloses synchronization with IMS. SPICE DL/I System Action: SPICE continues execution, but suspends SPICE checkpointprocess ing. SPICE preserves the res tart data for the program until it reques ts SPICE in-flightres tart, or until it terminates .

SPICE Restart API Explanation: SPICE SQL loses synchronization with the databasemanagement sys tem if database updates are rolled back, without the SPICE SAM file pos itions , orthe res tart program areas , being reset. This occurs if the program issues a rollback reques t s t, or ifcertain SRACODEs are returned from a commit s tatement, e.g. “-911”. This message is is sued onthe firs t commit reques t after SPICE loses synchronization with the database management sys tem.

System Restart API Action: SPICE continues execution, but suspends SPICE commitprocess ing. SPICE preserves the res tart data for the program until it reques ts SPICE in-flightres tart, or until it terminates .


SPI0116I SPICE RESTART DATABASE CANNOT BE ACCESSED - OPEN FAILUREExplanation: The SPICE res tart database was not available.

System Action: If the program is res tartable, SPICE will is sue message SPI0117I and thenABEND with user code 4090. Otherwise, control is returned to the application.Programmer/Operator Response: To prevent a recurrence of the message or ABEND, correctthe cause of the database open error and res tart the job.

SPI0117I *ABEND* SPICE RESTART CANNOT PROCEEDExplanation: The application program reques ted a res tart when the SPICE res tart database wasnot available. SPICE was therefore unable to determine whether a res tart was required. Thismessage may follow SPICE error message SPI0109I or SPI0116I.

System Action: SPICE will ABEND with user code 4090.Programmer/Operator Response: Correct the cause of the SPI0109I or SPI0116I message, andres tart the program.


SPI0118I *ABEND* IN-FLIGHT RESTART FAILURE - RESTART LIMIT EXCEEDEDSPICE SQL Explanation: The application program attempted in-flight res tart too often withoutan intervening success ful commit point.SPICE DL/I Explanation: The application program issued too many in-flight res tart callswithout an intervening success ful checkpoint.

SPICE Restart API Explanation: The application program attempted in-flight res tart too oftenwithout an intervening success ful commit point.


Programmer/Operator Response: Inves tigate the cause of the prior in-flight res tart failures . Take any appropriate action before res tarting the job.

SPI0119I IN-FLIGHT PROGRAM RESTART FROM ccccccccSPICE SQL Explanation: This message indicates that the application program has success fullyres tarted in-flight, and identifies the associated commit point.

SPICE DL/I Explanation: This message indicates that the application program has success fullyissued an in-flight res tart, and identifies the associated checkpoint.SPICE Restart API Explanation: This message indicates that the application program hassuccess fully res tarted in-flight, and identifies the associated commit point.


Programmer/Operator Response: None required.

SPI0120I *ABEND* IN-FLIGHT RESTART FAILURE - INVALID REQUESTSPICE DL/I Explanation: The application program reques ted an in-flight res tart when thepreceding call had not resulted in the databases being backed out to the previous commit point. This can be invoked explicitly by the application program, with a DL/I “ROLB” reques t, orimplicitly by the hos t database management sys tem. e.g. IMS PCB s tatus code “FD”.System Action: SPICE will ABEND with user code 4090.


SPI0121I *ABEND* SSAM I/O ERROR DURING COMMITSPICE SQL Explanation: An I/O error was detected agains t a SPICE SAM dataset, during theprocess ing of an SQL “COMMIT” s tatement. SPICE was therefore unable to complete thecommit.

SPICE DL/I Explanation: An I/O error was detected agains t a SPICE SAM dataset, during theprocess ing of a DL/I checkpoint call. SPICE was therefore unable to complete the commit.

SPICE Restart API Explanation: An I/O error was detected agains t a SPICE SAM dataset,during the process ing of a commit reques t. SPICE was therefore unable to complete the commit.


Programmer/Operator Response: Determine the cause of the I/O error, making use of anyassociated SPI0037I, SPI0038I or SPI0041I messages . Correct the problem and res tart the job.

SPI0122I APPLICATION TERMINATION WHEN RESTART OUTSTANDING - RESTARTREQUIRED

SPICE SQL Explanation: SPICE has los t synchronization with DB2. This typically occurswhen an application issues an SQL “ROLLBACK” s tatement. The application program hasterminated. Application res tart is required.

SPICE DL/I Explanation: SPICE has los t synchronization with IMS. This typically occurswhen an application issues a DL/I “ROLB” call. The application program has terminated. Application res tart is required.

SPICE Restart API Explanation: SPICE has los t synchronization with the databasemanagement sys tem. This typically occurs when an application issues a rollback reques t. Theapplication program has terminated. Application res tart is required.

System Action: SPICE will retain the res tart data in its database. The program will terminate,normally or abnormally, according to the value of the SPICE Res tart Database Program/PSB entry“OUTOFSYNCTERM” option. If the application executes within the z/OS LanguageEnvironment, The SPICE User 4090 Abend will be intercepted by LE, which will then terminatewith User 4088 Abend reason code 00000063 of module CEEBINIT.Programmer/Operator Response: Res tart the job.

SPI0124I INVALID ITEM - RESTART ENTRY CANNOT BE PROCESSEDSPICE DL/I Explanation: An attempt was made to res tart from a res tart entry created under anearlier release of SPICE.System Action: W hen the problem occurs with a SPICE application program, SPICE willABEND with user code 4090. W hen it occurs with the SPICE operator subsys tem or utilityprogram, SPICE will continue process ing.


Programmer/Operator Response: Res tart the program, us ing the SPICE res ident library for theappropriate SPICE release.

SPI0150I *ABEND* BAD AIB CALL, FUNCTION ffff, RETURN CODE cccc, REASON rrrrSPICE DL/I Explanation: SPICE DL/I received unexpected return codes from an AIB call. Thefunction, return and reason codes are documented in the message.System Action: SPICE will retain the res tart data in its database.

Programmer/Operator Response: Examine the reported codes . If the cause of the message isapparent, correct the problem and restart the job. Otherwise refer the problem to your technicalsupport team respons ible for SPICE.

SPI0151I *ABEND* DBD LIBRARY NOT AVAILABLESPICE DL/I Explanation: SPICE DL/I was unable to process an AIB reques t, because it couldnot locate the appropriate DBD.


Programmer/Operator Response: Ensure that a DBD library containing the appropriate entriesis allocated to DDname “IMS”, and res tart the job.


SPI0201W ABEND SYSTEM sssSPI0201W ABEND USER uuuuSPI0201W ABEND SYSTEM sss IN SPICE SUBTASKSPI0201W ABEND USER uuuu IN SPICE SUBTASKExplanation: This message identifies the abend code with which the application, or the SPICEsubtask, is about to abend. Sys tem abends , “sss”, are displayed as three hexadecimal digits , anduser abends , “uuuu”, as 4 decimal digits .

System Action: The job s tep will abnormally terminate.Programmer/Operator Response: Dependent on the code and circumstances of the abend.

SPI0204I *ABEND* APPLICATION TERMINATION WITHOUT SPICE TERMINATIONExplanation: The application program has completed without SPICE automatic terminationbeing success fully invoked.



SPI0205I *ABEND* DUMP DATASET SPIUDUMP OPEN FAILUREExplanation: The SPICE formatted dump routine was unable to open its dump dataset.


Programmer/Operator Response: Check the DCB for the SPICE formatted dump dataset. Itshould be “RECFM=VBA,LRECL=125. . .”. If not, correct the JCL or file and res tart the job. Otherwise refer the problem to your technical support team respons ible for SPICE.

SPI0206I SPICE DUMP DYNAMICALLY ALLOCATED TO SYSOUT=cExplanation: The job did not have anything allocated to “SPIUDUMP”, the DD name used bySPICE for its formatted dump. SPICE has dynamically allocated a SYSOUT file of the reportedclass to it.

System Action: SPICE will write its formatted dump to the allocated dataset.

Programmer/Operator Response: Print the formatted dump and include it in the problemdocumentation.

SPI0207I *ABEND* SPICE DUMP DYNAMIC ALLOCATION FAILURE, ERROR CODE=eeee,INFO CODE=cccc

Explanation: The job did not have a dataset allocated to “SPIUDUMP”, the DD name used bySPICE for its formatted dump. SPICE attempted to dynamically allocate a SYSOUT file to it. The allocation failed with the indicated error and information codes .System Action: SPICE will ABEND with user code 4090.

Programmer/Operator Response: Inves tigate the identified codes , us ing z/OS documentation. If the cause is not due to SPICE, correct the problem and res tart the job. Otherwise, refer theproblem to your technical support team respons ible for SPICE.


SPI0208I SPICE HAS TAKEN A FORMATTED DUMPExplanation: SPICE has written its formatted dump to the dataset allocated to DD name“SPIUDUMP”.System Action: SPICE will continue its abnormal termination.

Operator Response: Include the SPICE formatted dump in the problem documentation.

SPI0209I *ABEND* APPLICATION CALLED SPICE AFTER SPICE TERMINATIONExplanation: The application has issued a reques t to SPICE after SPICE has terminated. Thiss ituation should never arise, as SPICE automatic termination should occur only after the programhas terminated.



SPI0211W APPLICATION TIMEOUT - EXECUTION CONTINUESExplanation: The application program has executed without issuing commit points for a periodin excess of the SPICE application timeout interval. SPICE has been configured to allowexecution of the program to continue.System Action: SPICE will allow the program to continue its execution.

Programmer/Operator Response: Report the problem as an application program error.

SPI0212W APPLICATION TIMEOUT - TERMINATE PROGRAM ?SPI0212A APPLICATION TIMEOUT - REPLY Y/NExplanation: The application program has executed without issuing commit points for a periodin excess of the SPICE application timeout interval. The operator is being asked whether SPICEshould terminate the program abnormally, or allow it to continue. The operator should reply “Y”to ins truct SPICE to terminate the program, or “N” to allow it to continue.

System Action: The application program will continue to process whils t SPICE awaits the replyfrom the operator.Programmer/Operator Response: Respond to the message, in accordance with operatingins tructions . Report the problem as an application program error.

SPI0213I APPLICATION TIMEOUT - EXECUTION WILL BE TERMINATEDExplanation: The application program has executed without issuing commit points for a periodin excess of the SPICE application timeout interval. SPICE has been configured to terminateexecution of the program abnormally.


Programmer/Operator Response: Report the problem as an application program failure.

SPI0214I APPLICATION TIMEOUT - TERMINATION DEFERREDExplanation: The application program has executed without issuing commit points for a periodin excess of the SPICE application timeout interval. SPICE has been configured to terminateexecution of the program abnormally. The hos t database management sys tem, however, wasexecuting when the timeout occurred, and could not be interrupted.System Action: As soon as the database management sys tem returns to SPICE, SPICE willABEND the program with user code 4092. If the database management sys tem does not return,SPICE will reissue the message, approximately every 5 minutes .Programmer/Operator Response: If the program terminates with a user 4092 abend, report theproblem as an application program failure. If not, follow the operating ins tructions for a loopingor waiting database management sys tem.

SPI0217I *ABEND* APPLICATION FRONT END PROCESSOR - APPLICATION PROGRAMNOT FOUND

SPICE DL/I Explanation: The SPICE application front-end interface was executed incorrectly. It was unable to locate an application program to execute.


Programmer/Operator Response: This problem is caused by the SPICE application front-endinterface having been incorrectly link-edited with the target application program. Link-edit theprogram correctly, and res tart the job.

SPI0220I SPICE ESTAE RECURSIONSPICE Explanation: The SPICE ESTAE exit is in a (probably infinite) loop.

System Action: SPICE will continue to process .

Programmer/Operator Response: Cancel the job, if necessary by forcing the partition toterminate. Refer the problem to your technical support team respons ible for SPICE.


SPI0250I *ABEND* DATABASE REQUEST FAILURE DURING TERMINATIONSPICE Explanation: SPICE encountered an error agains t the res tart database, duringtermination.System Action: SPICE will ABEND with user code 4090.

Programmer/Operator Response: Examine the preceding message(s ). If the cause is not due toSPICE, correct the problem and res tart the job. Otherwise, refer the problem to your technicalsupport team respons ible for SPICE.

SPI0251I *ABEND* SPICE SAM REQUEST FAILURE DURING TERMINATIONExplanation: SPICE encountered a problem when attempting to close a SPICE SAM file, duringtermination.

System Action: SPICE will ABEND with user code 4090.Programmer/Operator Response: Examine the preceding message(s ). If the cause is not due toSPICE, correct the problem and res tart the job. Otherwise, refer the problem to your technicalsupport team respons ible for SPICE.

SPI0260I *ABEND* SPICE SERVICES TESTING FACILITY - ABENDExplanation: The application program has is sued a SPICE services tes t reques t. Theapplication JCL included DD name “*****DIE”, where “*****” is the DD name prefix specifiedin the reques t.


Programmer/Operator Response: This problem should occur only in tes ting environments . Toprevent its recurrence, remove the appropriate “*****DIE” DD s tatement from the JCL. The jobmay then be res tarted.

SPI0261I *WARNING* SPICE SERVICES TESTING FACILITY - ERROR RAISEDExplanation: The application program has issued a SPICE services tes t reques t. The applicationJCL included DD name “*****ERR”, where “*****” is the DD name prefix specified in thereques t.

SPICE SQL System Action: SPICE SQL will return an SQLCODE of “-681” and anSQLSTATE of “SR261” in the SQLCA. Control is returned to the application program.SPICE DL/I System Action: SPICE DL/I will return a s tatus code of “ZZ” in the IMS PCB. Control is returned to the application program.SPICE Restart API System Action: SPICE will return an SRACODE of “-681”, anSRASTATE of “SR261” and an SRASTAT of “ZZ” in the SRACA. Control is returned to theapplication program.

Programmer/Operator Response: This problem should occur only in tes ting environments . Toprevent its recurrence, remove the appropriate “*****ERR” DD s tatement from the JCL. The jobmay then be res tarted.

SPI0262I *LOOP* SPICE SERVICES TESTING FACILITY - PROGRAM IS LOOPINGExplanation: The application program has is sued a SPICE services tes t reques t. Theapplication JCL included DD name “*****SPN”, where “*****” is the DD name prefix specifiedin the reques t.

System Action: SPICE will enter a permanent CPU loop.

Programmer/Operator Response: The program should be terminated by operator command. This problem should occur only in tes ting environments . To prevent its recurrence, remove theappropriate “*****SPN” DD s tatement from the JCL. The job may then be res tarted.


SPI0301I COMMAND INVALID, INVALID CHARACTER IN COMMANDExplanation: The command contained an invalid character.

System Action: Execution of the command is terminated.

Programmer/Operator Response: Correct the command and reissue it.

SPI0302I COMMAND INVALID, QUOTED TEXT STRING INCOMPLETEExplanation: The command contained a text s tring, without a clos ing quote.

System Action: Execution of the command is terminated.Programmer/Operator Response: Correct the command and reissue it.


SPI0303I COMMAND INVALID, COMMENT INCOMPLETEExplanation: The command contained a comment, without a clos ing “*/”.


SPI0305I COMMAND INVALID, MISSING ")"Explanation: The command contained more opening than clos ing parentheses .



SPI0306I COMMAND INVALID, KEYWORD CANNOT HAVE SUBLISTS, "kkkkkkkk"Explanation: A parameter was specified for keyword, “kkkkkkkk”, when none is allowed.


SPI0308I COMMAND INVALID, KEYWORD NOT FOUND, "kkkkkkkk"Explanation: The keyword “kkkkkkkk” is not applicable to this command.



SPI0309I *ABEND* SPICE PARSING SUBROUTINE FAILURE, NAME=name, RETURN CODEcode

Explanation: SPICE pars ing routine “name” has returned invalid return code “code”.

System Action: The SPICE utility program, SPIUTI00, will ABEND with user code 4091.Programmer/Operator Response: Refer the problem to your technical support team respons iblefor SPICE.

SPI0310I COMMAND EXECUTED SUCCESSFULLY AT yy.ddd hh:mm:ss.tExplanation: The command was executed, at the indicated time and date.

System Action: The next command is read from the input s tream.

Programmer/Operator Response: None.

SPI0311I NO COMMAND FOUNDExplanation: No further commands were found in the input s tream. This message normallyoccurs when end of file is reached.

System Action: The utility program terminates normally.


SPI0312I COMMAND EXECUTION FAILED AT yy.ddd hh:mm:ss.tExplanation: Execution of the command was terminated at the indicated time and date. Thismessage will be preceded by another, detailing the cause of the failure.

System Action: The next command is read from the input s tream.

Programmer/Operator Response: Dependent on the cause of the error.

SPI0313I PROCESSING TERMINATEDExplanation: The SPICE utility program has terminated.

System Action: Execution of the utility terminates .Programmer/Operator Response: None.

SPI0316I INTERNAL BUFFER OVERFLOW, COMMAND TOO LONGExplanation: The command was too long for the utility to process .


Programmer/Operator Response: Correct the command and reissue it. If the problem pers is ts ,refer it to your technical support team respons ible for SPICE.

SPI0317I COMMAND FAILURE - TOO MANY ")"Explanation: The command contained more clos ing than open parentheses .



SPI0318I COMMAND FAILURE - INVALID NUMERIC FIELDExplanation: A numerical parameter of the command was not in numeric format.




SPI0319I COMMAND FAILURE - NUMERIC FIELD TOO LONGExplanation: A numeric parameter of the command was too long.


SPI0320I COMMAND FAILURE - HEX FIELD TOO LONGExplanation: A hexadecimal parameter of the command was too long.



SPI0321I COMMAND FAILURE - INVALID HEX FIELDExplanation: A hexadecimal parameter of the command contained invalid characters .


SPI0322I COMMAND FAILURE - INVALID ITEM LENGTHExplanation: A parameter in the command was longer than the permitted length.



SPI0323I COMMAND FAILURE - VALUE OUTSIDE VALID RANGEExplanation: A parameter in the command was not in the permitted range of values .



SPI0401I *ABEND* SYSIN INPUT FILE OPEN FAILURESPICE Explanation: The SPICE utility program SPIUTI00 was unable to open the commandinput file, DD name “SYSIN”.SPICE System Action: The SPICE utility program, SPIUTI00, will terminate with ABENDcode 4091.

Programmer/Operator Response: Correct the job and res tart.

SPI0402I *ABEND* SYSPRINT OUTPUT FILE OPEN FAILURESPICE Explanation: The SPICE utility program SPIUTI00 was unable to open the report outputfile, DD name “SYSPRINT”.

SPICE System Action: The SPICE utility program, SPIUTI00, will terminate with ABENDcode 4091.

Programmer/Operator Response: Correct the job and res tart.

SPI0403I *ABEND* SPICE UTILITY SUBROUTINE FAILURE, NAME=name, RETURN CODEcode

Explanation: Routine “name” of the SPICE utility program SPIUTI00 has returned invalidreturn code “code”.

System Action: The SPICE utility program, SPIUTI00, will ABEND with user code 4091.


SPI0404I COMMAND FAILURE - KEYWORD IS REPEATED, "kkkkkkkk"Explanation: The keyword, “kkkkkkkk”, was specified more than once.



SPI0405I COMMAND FAILURE - VALUE LENGTH INVALID, KEYWORD "kkkkkkkk"Explanation: The length of a parameter of the keyword “kkkkkkkk” was invalid.



SPI0406I COMMAND FAILURE - KEYWORD CONTRADICTS PREVIOUS PARAMETER,"kkkkkkkk"

Explanation: The keyword “kkkkkkkk”, and its complement, were both specified in thecommand.System Action: Execution of the command is terminated.


SPI0407I COMMAND FAILURE - PCB NOT FOUND, DBDNAME "dddddddd"SPICE DL/I Explanation: The PSB the utility is run agains t does not contain a PCB fordatabase “dddddddd” with the required process ing options .System Action: Execution of the command is terminated.

Programmer/Operator Response: Correct the command and reissue it, or, if the command iscorrect, correct the PSB and rerun the utility.

SPI0408I COMMAND FAILURE - SEGLEN CAN BE SPECIFIED ONLY FOR THE DEFAULTENTRY

SPICE DL/I Explanation: Parameter “SEGLEN” was specified on an “INIT” command for aPSB.



SPI0409I COMMAND FAILURE - DBDNAME MUST BE SPECIFIEDSPICE SQL Explanation: The command omitted the keyword “SQL”.

SPICE DL/I Explanation: The command omitted the keyword “DBDNAME” and its value.System Action: Execution of the command is terminated.


SPI0410I COMMAND FAILURE - SEGLEN MUST BE SPECIFIEDSPICE DL/I Explanation: The “SEGLEN” parameter mus t be specified when issuing an “INIT”command for the “DEFAULTS” entry.


SPI0411I COMMAND FAILURE - BAD DL/I STATUS CODE OF cc FROM ffff CALLSPICE DL/I Explanation: A call to DL/I with a function code of “ffff” returned a s tatus code of“cc”.


Programmer/Operator Response: Examine the s tatus code and, if the cause of the error can bedetermined, correct it. If not, refer the problem to your technical support team respons ible forSPICE.

SPI0412I COMMAND FAILURE - PROGRAM/PSB IS NOT REGISTERED IN THE DATABASESPICE SQL Explanation: No entry could be found in the res tart database for the reques tedprogram name.SPICE DL/I Explanation: No entry could be found in the selected database for the reques tedPSB name.



SPI0413I COMMAND FAILURE - PROGRAM/PSB ALREADY REGISTERED IN THEDATABASE

SPICE SQL Explanation: The “INIT” command was is sued for a program name that wasalready regis tered in the res tart database.

SPICE DL/I Explanation: The “INIT” command was is sued for a PSB name that was alreadyregis tered in the selected database.System Action: Execution of the command is terminated.


SPI0414I COMMAND FAILURE - JOB IS NOT REGISTERED IN THE DATABASE FOR THISPROGRAM/PSB

SPICE SQL Explanation: No entry was found in the res tart database for the reques ted jobnameand program name.

SPICE DL/I Explanation: No entry was found in the database for the reques ted jobname, underthe specified PSB name.




SPI0415I COMMAND FAILURE - JOB IS ALREADY REGISTERED IN THE DATABASE FORTHIS PROGRAM/PSB

SPICE SQL Explanation: An entry already exis ts in the res tart database for the reques tedjobname and program name.

SPICE DL/I Explanation: An entry already exis ts in the database for the reques ted jobname,under the specified PSB name.System Action: Execution of the command is terminated.


SPI0416I COMMAND FAILURE - MSDB RESTART DATABASE IS FULL, ENTRY COULD NOTBE INSERTED

SPICE DL/I Explanation: There was not sufficient space in the selected MSDB database for theentry to be inserted.System Action: Execution of the command is terminated.

Programmer/Operator Response: Either delete some entries from the database, or increase thenumber of segments , before reissuing the command.

SPI0417I COMMAND FAILURE - OPTIONS SELECTED INVALID FOR "CHANGE ... JOB"SPICE SQL Explanation: An option specified in the command relates to program entries , and isinvalid for job entries .SPICE DL/I Explanation: An option specified in the command relates to PSB entries , and isinvalid for job entries .



SPI0418I COMMAND FAILURE - OPTIONS SELECTED WERE INVALID FOR PROGRAM/PSBENTRY CHANGE

SPICE SQL Explanation: An option specified in the command relates to job entries , and isinvalid for program entries .

SPICE DL/I Explanation: An option specified in the command relates to job entries , and isinvalid for PSB entries .System Action: Execution of the command is terminated.


SPI0419I COMMAND FAILURE - PROGRAM/PSB MUST BE SUPPLIEDSPICE SQL Explanation: The command did not specify a program name.

SPICE DL/I Explanation: The command did not specify a PSB name.



SPI0420I PROGRAM/PSB "pppppppp" ALREADY SUSPENDEDSPICE SQL Explanation: The “CHANGE ... SUSPEND” command was is sued agains t programname “pppppppp”, which was already suspended.

SPICE DL/I Explanation: The “CHANGE ... SUSPEND” command was is sued agains t PSBname “pppppppp”, which was already suspended.System Action: Execution of the command continues .


SPI0421I PROGRAM/PSB "pppppppp" NOT SUSPENDEDSPICE SQL Explanation: The “CHANGE ... RELEASE” command was is sued agains t programname “pppppppp”, which was not suspended.

SPICE DL/I Explanation: The “CHANGE ... RELEASE” command was is sued agains t PSBname “pppppppp”, which was not suspended.

System Action: Execution of the command continues .


SPI0422I PROGRAM/PSB "pppppppp" JOB "jjjjjjjj" ALREADY SUSPENDEDSPICE SQL Explanation: The “CHANGE ... SUSPEND” command was issued agains t job“jjjjjjjj” of program name “pppppppp”, which was already suspended.SPICE DL/I Explanation: The “CHANGE ... SUSPEND” command was issued agains t job“jjjjjjjj” of PSB name “pppppppp”, which was already suspended.

System Action: Execution of the command continues .Programmer/Operator Response: None.


SPI0423I PROGRAM/PSB "pppppppp" JOB "jjjjjjjj" NOT SUSPENDEDSPICE SQL Explanation: The “CHANGE ... RELEASE” command was issued agains t job“jjjjjjjj” of program name “pppppppp”, which was not suspended.SPICE DL/I Explanation: The “CHANGE ... RELEASE” command was issued agains t job“jjjjjjjj” of PSB name “pppppppp”, which was not suspended.

System Action: Execution of the command continues .Programmer/Operator Response: None.

SPI0424I PROGRAM/PSB "pppppppp" JOB "jjjjjjjj" IS NOT ACTIVESPICE SQL Explanation: The “CHANGE ... RERUN” command was issued agains t job“jjjjjjjj” of program name “pppppppp”, which did not have an active res tart point.

SPICE DL/I Explanation: The “CHANGE ... RERUN” command was issued agains t job“jjjjjjjj” of PSB name “pppppppp”, which did not have an active res tart point.System Action: Execution of the command is terminated.


SPI0425I COMMAND FAILURE - PROGRAM/PSB "pppppppp" JOB "jjjjjjjj" HASCOMPLETED

SPICE SQL Explanation: The “CHANGE ... RESTART” command was issued agains t job“jjjjjjjj” of program name “pppppppp”, which had completed its execution; the job entry “STOP”time was later than that of the las t commit point.

SPICE DL/I Explanation: The “CHANGE ... RESTART” command was issued agains t job“jjjjjjjj” of PSB name “pppppppp”, which had completed its execution; the job entry “STOP”time was later than that of the las t commit point.System Action: Execution of the command is terminated.


SPI0426I COMMAND FAILURE - SPECIFIC JOBNAME WITH PROGRAM/PSB(ALL) ISINVALID

SPICE SQL Explanation: A “PROGRAM” parameter of “ALL” was specified with a particularjobname. This combination of operands is not supported.SPICE DL/I Explanation: A “PSBNAME” parameter of “ALL” was specified with a particularjobname. This combination of operands is not supported.System Action: Execution of the command is terminated.


SPI0427I COMMAND FAILURE - JOBNAME MUST BE SPECIFIC WITH RERUN ORRESTART

Explanation: The “CHANGE ... RERUN/RESTART” command did not specify which job'sentry was to be changed.



SPI0428I COMMAND FAILURE - INVALID USE OF "ALL" OPTIONExplanation: A value of “ALL” has been specified for a keyword parameter of the command. The command supports only specific values .System Action: Execution of the command is terminated.


SPI0429I COMMAND FAILURE - JOBS EXIST FOR THE PROGRAM/PSB BEING DELETEDSPICE SQL Explanation: An attempt was made to delete a program entry, when it haddependent job entries . The “PURGE” operand was not specified.SPICE DL/I Explanation: An attempt was made to delete a PSB entry, when it had dependentjob entries . The “PURGE” operand was not specified.



SPI0430I COMMAND FAILURE - ACTIVE RESTARTS EXIST FOR JOB "jjjjjjjj"Explanation: An attempt was made to delete the entry for job “jjjjjjjj”, while it s till had an activecommit point. The “PURGE” operand was not specified.




SPI0431I COMMAND FAILURE - MSDB CORRUPT, PSB "pppppppp", JOB "jjjjjjjj"SPICE DL/I Explanation: The entry in the selected MSDB database, for PSB name “pppppppp”and jobname “jjjjjjjj”, is corrupt.System Action: Execution of the command is terminated.


SPI0432I COMMAND FAILURE - DATABASE SEGMENT TYPE INVALIDExplanation: An entry in the selected database was found to be corrupt.



SPI0433I *ABEND* SPICE UTILITY FAILURE, STATUS CODE OF "ss" RETURNED BY"TERM" CALL

SPICE DL/I Explanation: A DL/I s tatus code of “ss” was returned from a “TERM” call toSPICE.

System Action: The SPICE utility program, SPIUTI00, will ABEND with user code 4091.

Programmer/Operator Response: Examine the s tatus code and, if the cause is apparent, correctit and rerun the utility. If not, refer the problem to your technical support team respons ible forSPICE.

SPI0434I COMMAND FAILURE - ATTEMPT TO DELETE THE DEFAULT PROGRAM/PSBSEGMENT

SPICE SQL Explanation: A “DELETE ... PROGRAM('*DEFAULT')” command was is sued. The SPICE utility program will not allow the default entry to be deleted.

SPICE DL/I Explanation: A “DELETE ... PSBNAME('*DEFAULT')” command was is sued. The SPICE utility program will not allow the default PSB to be deleted.



SPI0435I *ABEND* SPICE UTILITY FAILURE, STATUS CODE OF "ss" RETURNED BY "ffff"IMS DC CALL

SPICE DL/I Explanation: An IMS s tatus code of “ss” was returned from a “ffff” call to the I/Oor alternate PCB.System Action: The SPICE utility program, SPIUTI00, will ABEND with user code 4091.

Programmer/Operator Response: Examine the s tatus and function codes and, if the cause isapparent, correct it and rerun the utility. If not, refer the problem to your technical support teamrespons ible for SPICE.

SPI0436I COMMAND FAILURE - ENTRY NOT FOUNDSPICE DL/I Explanation: No MSDB segment with the reques ted sequence number is present inthe database.


SPI0437I COMMAND FAILURE - ENTRY CANNOT BE DELETED AS IT IS IN USESPICE DL/I Explanation: The reques ted MSDB segment is pointed to by another segment inthe database, and therefore cannot be deleted.



SPI0438I COMMAND FAILURE - MSDBINDEX OPTION VALID AGAINST MSDB DATABASEONLY

SPICE DL/I Explanation: The requested database was not an MSDB, and cannot be accessedby MSDB sequence number.



SPI0450I COMMAND FAILURE - USER NOT ALLOWEDExplanation: The user is not authorised to is sue the reques ted command.System Action: Execution of the command is terminated.

Programmer/Operator Response: If the command is in error, correct it and reissue it. If thereques t is reasonable, consult the security adminis trator.


SPI0451I COMMAND FAILURE - ACCESS DENIEDExplanation: The user is not authorised to use the SPICE operator facilities .

System Action: Execution of the command is terminated.Programmer/Operator Response: If access to the SPICE operator facilities is required, consultthe security adminis trator.

SPI0452I COMMAND FAILURE - JOB NAME MUST BE SPECIFIEDExplanation: The command did not specify a job name.



SPI0453I COMMAND FAILURE - INFILE AND OUTFILE MUST BE SPECIFIEDExplanation: The command did not specify both INFILE and OUTFILE parameters .



SPI0454I COMMAND FAILURE - UTILITY RUNNING UNDER SAME JOBNAME ASCOMMAND TARGET

Explanation: The job that the SPICE utility programming is executing in has the same job nameas that specified in the command.System Action: Execution of the command is terminated.

Programmer/Operator Response: Change the jobname of the utility job and re-submit it.

SPI0455I COMMAND FAILURE - NO RESTART EXISTS FOR THE SPECIFIED JOBExplanation: The SPICE res tart database does not contain an entry for the specified job that isawaiting res tart.

System Action: Execution of the command is terminated.Programmer/Operator Response: If the database name, PSB name and job name are correct,then the program completed success fully. If so, the REPRO command is not appropriate. Otherwise, correct the command and reissue it.

SPI0456I COMMAND FAILURE - FILE NOT FOUND IN RESTART DATAExplanation: No entry was found in the res tart data of the job for a SPICE SAM output file withDDname as specified in the INDD keyword parameter of the command. Poss ible causes are:! The input DDname is spelt incorrectly.! The res tart checkpoint precedes the opening of the file. The checkpoint will not contain an

entry for the file.

The exis tence of res tart data for the file may be verified by obtaining a dump report of thecontents of the job entry, and locating the SSPD entry for the file name. The appropriate SPICEReference Manual details how this report is obtained.



SPI0457I COMMAND FAILURE - fffff FAILURE FOR FILE ddddddddExplanation: SPICE experienced a failure when process ing an “ffff” reques t agains t the SPICESAM file “dddddddd”.System Action: Execution of the command is terminated.

Programmer/Operator Response: Examine the preceding messages , and take appropriateaction. Reissue the command.

SPI0458I SUBSYSTEM FAILURE - INVALID IDENTIFY RETURN CODEExplanation: A z/OS IDENTIFY reques t returned an invalid code.System Action: Execution of the operator subsys tem is terminated.

Programmer/Operator Response: Refer the problem to your technical support team respons iblefor SPICE. Examine the preceding z/OS messages on the z/OS SYSLOG, and take appropriateaction.

SPI0459I COMMAND FAILURE - JOB ENTRY ALTERED DURING COMMAND EXECUTIONExplanation: SPICE detected a change to the repos ition address for a SPICE SAM file in theSPICE Restart Database whils t process ing a ‘REPRO’ reques t.


Programmer/Operator Response: Ensure that no other process is active before reissuing thecommand.


SPI0460I COMMAND FAILURE - RESTART INFILE POSITION NOT FOUNDExplanation: W hils t process ing a ‘REPRO’ reques t, SPICE was unable to find the SPICE SAMinput file’s res tart pos ition, as recorded in the reques ted job’s entry in the SPICE Res tartDatabase.


Programmer/Operator Response: Poss ible causes are:! The input DDname and file do not correspond to the reques ted job and program name.! The input file is a copy of the original, created in a way that did not preserve the original

block s tructure. ‘REPRO’ can only recover from either the original file or an identical copy.

SPI0461I COMMAND FAILURE - INFILE AND OUTFILE MUST DIFFERExplanation: The ‘REPRO’ command input and output files mus t be different.


Programmer/Operator Response: Correct the job and re-submit.


SPI0502I SQL REQUEST FAILURE: LENGTH VALUE INVALIDSPICE SQL Explanation: One of the hos t variables in the SPICE SQL reques t had an invalidlength value. The reques ted operation could not be processed.

System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of “SR502” in thereques t SQLCA.Programmer/Operator Response: Correct the problem and res tart the job.

SPI0503I SQL REQUEST FAILURE: DUPLICATE VALUESPICE SQL Explanation: The SPICE SQL reques t specified one of the SPICE hos t variablesmore than once. The reques ted operation could not be processed.


SPI0504I SQL REQUEST FAILURE: OMITTED VALUESPICE SQL Explanation: The SPICE SQL reques t omitted a required SPICE hos t variablevalue. The reques ted operation could not be processed.System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of “SR504” in thereques t SQLCA.


SPI0505I SQL REQUEST FAILURE: INVALID COMBINATION OF VALUESSPICE SQL Explanation: The SPICE SQL reques t specified an invalid combination of SPICEhos t variable values . The reques ted operation could not be processed.

A “!DDNAME!=...” value may have been specified on a “SPICE_PAM” reques t, for ins tance.System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of “SR505” in thereques t SQLCA.Programmer/Operator Response: Correct the problem and res tart the job.

SPI0506I SQL REQUEST FAILURE: INVALID ACTION VALUESPICE SQL Explanation: The SPICE SQL reques t included an invalid SPICE ACTION hos tvariable value. The reques ted operation could not be processed.

The only valid values are “!ACTION!=OPEN_IN”, “!ACTION!=OPEN_OUT”,“!ACTION!=CLOSE” and “!ACTION!=TEST”.


SPI0507I SQL REQUEST FAILURE: INVALID STATUS VALUESPICE SQL Explanation: The SPICE SQL reques t included an invalid SPICE STATUS hos tvariable value. The reques ted operation could not be processed.

The only valid values are “!STATUS!=STATIC” and “!STATUS!=ACTIVE”.System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of “SR507” in thereques t SQLCA.



SPI0509I SQL REQUEST FAILURE: AREA ALREADY STATICSPICE SQL Explanation: The SPICE SQL reques t reques ted a change in program area s tatus to“s tatic” when the area was already “s tatic”. The reques ted operation could not be processed.SPICE SQL System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of“SR509” in the reques t SQLCA.

SPICE Restart API Explanation: The SPICE Res tart API reques ted that the contents of aprogram area be frozen, when the program area was already frozen.

SPICE Restart API System Action: SPICE will return an SRACODE of -681, an SRASTATEof “SR509” and an SRASTAT of “RX” in the reques t SRACA.


SPI0510I [*ABEND*] SPICE UNABLE TO USE RESTART DATABASE, SQLCODE=s999SPICE SQL Explanation: An SQL s tatement from SPICE to the res tart database returnedSQLCODE “s999”.

SPICE DL/I System Action: If the message includes the text “*ABEND*”, SPICE will ABENDwith user code 4090. Otherwise, control will be returned to the application program, with a s tatuscode of “BC” returned in the reques t PCB.

SPICE SQL System Action: If the message includes the text “*ABEND*”, SPICE will ABENDwith user code 4090. Otherwise, control will be returned to the application program, with thediagnos tic information returned in the reques t SQLCA.SPICE Restart API System Action: If the message includes the text “*ABEND*”, SPICE willABEND with user code 4090. Otherwise, control will be returned to the application program,with the diagnos tic information s tored in SRACODE, SRASTATE and SRAERRM and anSRASTAT of “BC” returned in the request SQLCA.

Programmer/Operator Response: Examine the reported SQLCODE. If the cause of theproblem is evident, correct it and res tart the job. If not, refer it to your technical support teamrespons ible for SPICE.

SPI0511I SQL REQUEST FAILURE: AREA ALREADY SELECTEDSPICE Explanation: The SPICE reques t attempted to declare a program area that had alreadybeen declared. The reques ted operation could not be processed.

SPICE SQL System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of“SR511” in the reques t SQLCA.SPICE Restart API System Action: SPICE will return an SRACODE of “-681”, anSRASTATE of “SR511” and an SRASTAT of “RX” in the reques t SRACA.Programmer/Operator Response: Correct the problem and res tart the job.

SPI0512W SQL REQUEST ANOMALY: INVALID CATEGORY VALUESPICE SQL Explanation: The SPICE SQL reques t specified an 18 character hos t variableprefixed with “!SPICE!”, but not one of the valid category values . The s tatement was rejected asa SPICE SQL reques t.

This is usually a programming error.System Action: SPICE will pass the s tatement on to DB2 for execution.

Programmer/Operator Response: If inves tigation of the program indicates a SPICE SQLprogramming error, correct it and res tart the job. This message can be is sued for non-SPICE SQLstatements . If the number of these messages from a program becomes a problem, the message canbe suppressed. See topic SPICE Application Program Diagnostics in the SPICE SQL ProductReference Manual for details .

SPI0513I SQL REQUEST FAILURE: AREA/RECORD NOT CONTIGUOUSSPICE SQL Explanation: The SPICE SQL reques t specified a set of hos t variables for a SPICEPAM program area or SPICE SAM record I/O area that did not collate into a s ingle area ofs torage. The reques ted operation could not be processed.

This problem can be created when COBOL programs specify a hos t s tructure containing“FILLER” variables . The DB2 precompiler omits “FILLER” variables from the lis t of variablesthat are passed to SPICE. If this is the case, changing their names to other than “FILLER” willcorrect the problem.


SPI0514W SQL REQUEST ANOMALY: SPICE PARAMETER MAY BE INCORRECTSPICE SQL Explanation: The SPICE SQL reques t included a parameter beginning with thecharacter “!” that was not a valid SPICE SQL keyword. The s tatement was rejected as a SPICESQL reques t.


This message is typically caused by an error in the coding of the value of a SPICE SQL parameter,“!FILEDD!=FILE” ins tead of “!DDNAME!=FILE” for ins tance.

System Action: SPICE will pass the s tatement on to DB2 for execution.

Programmer/Operator Response: If inves tigation of the program indicates a SPICE SQLprogramming error, correct it and res tart the job. This message can be is sued for valid SPICESQL s tatements whose data hos t variables happen to have “!” as their firs t character. If thenumber of these messages from a program become a problem, the message can be suppressed. See topic SPICE Application Program Diagnostics in the SPICE SQL Product ReferenceManual for details .

SPI0516I SQL REQUEST FAILURE: INVALID RECLEN PARAMETERSPICE SQL Explanation: The SPICE SQL SAM reques t specified an invalid value ass igned tothe RECLEN column. The reques ted operation could not be processed.

The RECLEN parameter mus t take the value “!RECLEN!=<number>”, where “<number>”cons is ts only of the digits “0” to “9”.System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of “SR516” in thereques t SQLCA.


SPI0517I SQL REQUEST FAILURE: INVALID FILE RECORD LENGTHSPICE SQL Explanation: The record length of a SPICE SAM file did not comply with therecord length as defined in the SPICE SAM cursor declaration or file open reques t. The reques tedoperation could not be processed.

This can be caused by ass igning the wrong file to the program. It can also be caused by incorrectspecification of the RECLEN parameter.

SPICE SQL System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of“SR517” in the reques t SQLCA.SPICE Restart API Explanation: The record length of a SPICE SAM file did not comply withthe record length as defined in the open reques t. The reques ted operation could not be processed.

This can be caused by ass igning the wrong file to the program. It can also be caused by incorrectspecification of the record length parameter.

SPIE Restart API System Action: SPICE will return an SRACODE of -681, an SRASTATE of“SR517” and an SRASTAT of “AI” in the reques t SRACA.

Programmer/Operator Response: Correct the program or file and res tart the job.SPI0518I TEST REQUEST FAILURE - INVALID DDNAME PREFIXExplanation: A SPICE services tes t facility reques t specified a DDname prefix of less than therequired 5 characters .SPICE SQL System Action: SPICE will return an SQLCODE of -681 and an SQLSTATE of“SR518” in the reques t SQLCA.


SPICE Restart API System Action: SPICE will return an SRACODE of -681, an SRASTATEof “SR518” and an SRASTAT of “AI” in the SRACA.


SPI0520I CAF CONNECT FAILURE: RETURN CODE=xxxxExplanation: SPICE received invalid return code “xxxx” from a DB2 CAF CONNECT reques t.


Operator Response: Consult DB2 documentation for the meaning of the error codesdocumented in the message, correct the problem accordingly, and res tart the SPICE OperatorSubsys tem

SPI0521I CAF OPEN FAILURE: RETURN CODE=xxxxExplanation: SPICE received invalid return code “xxxx” from a DB2 CAF OPEN reques t.

System Action: SPICE will ABEND with user code 4090.Operator Response: Consult DB2 documentation for the meaning of the error codesdocumented in the message, correct the problem accordingly, and res tart the SPICE OperatorSubsys tem

SPI0522I CAF CLOSE FAILURE: RETURN CODE=xxxxExplanation: SPICE received invalid return code “xxxx” from a DB2 CAF CLOSE reques t.




SPI0523I CAF DISCONNECT FAILURE: RETURN CODE=xxxxExplanation: SPICE received invalid return code “xxxx” from a DB2 CAF DISCONNECTreques t.System Action: SPICE will ABEND with user code 4090.


SPI0524I INVALID CAF PARAMETER LISTExplanation: Internal SPICE failure.


Operator Response: Refer the problem to your technical support team respons ible for SPICE.


SPI0600I ISPF SUBSYSTEM FAILURE - ISPF INACTIVEExplanation: An attempt was made to execute the SPICE operator subsys tem outs ide of ISPF.

System Action: Execution of the operator subsys tem is terminated.

Programmer/Operator Response: Enter ISPF before s tarting the SPICE operator subsys tem.

SPI0601I ISPF SUBSYSTEM FAILURE - ATTACH FAILUREExplanation: The z/OS ATTACH of the SPICE utility program by the SPICE operatorsubsys tem failed.


Programmer/Operator Response: Refer the problem to your technical support team respons iblefor SPICE. Examine the preceding z/OS messages on the z/OS SYSLOG, and take appropriateaction.

SPI0602I ISPF SUBSYSTEM FAILURE - ISPEXEC FAILUREExplanation: An invalid return code was returned by ISPEXEC.


Programmer/Operator Response: Refer the problem to your technical support team respons iblefor SPICE. Examine the displayed message(s ), and take any appropriate action.

SPI0603I ISPF SUBSYSTEM FAILURE - INVALID REQUEST FROM SUBSYSTEMExplanation: An invalid reques t was made to the SPICE operator subsys tem.


Programmer/Operator Response: Refer the problem to your technical support team respons iblefor SPICE. Examine the displayed message(s ), and take any appropriate action.

SPI0604I UTILITY FAILURE - INVALID REQUEST TO ISPF SUB-SYSTEMExplanation: This message indicates a serious failure of the SPICE operator subsys tem.



SPI0605I ISPF SUBSYSTEM FAILURE - UTILITY ABENDExplanation: This message indicates a serious failure of the SPICE operator subsys tem.System Action: Execution of the operator subsys tem is terminated.


SPI0606I ISPF SUBSYSTEM FAILURE - CPPL NOT FOUNDExplanation: This message indicates a serious failure of the SPICE operator subsys tem.

System Action: Execution of the operator subsys tem is terminated.Programmer/Operator Response: Refer the problem to your technical support team respons iblefor SPICE.

SPI0607I ISPF SUBSYSTEM FAILURE - STACK FAILUREExplanation: This message indicates a serious failure of the SPICE operator subsys tem.




SPI0611I ISPF SUBSYSTEM FAILURE - INVALID LENGTHExplanation: An invalid parameter s tring was passed to the SPICE operator subsys tem.

System Action: Execution of the operator subsys tem is terminated.Programmer/Operator Response: Refer the problem to your technical support team respons iblefor SPICE. It is likely that the DB2 or IMS sys tem is defined in the SPICE operator subsys temsys tem table incorrectly. Examine the displayed message(s ), and take any appropriate action.

SPI0612I ISPF SUBSYSTEM FAILURE - UTILITY INACTIVEExplanation: The SPICE operator subsys tem attempted to pass a message to the SPICE utilityprogram when it was inactive.


Programmer/Operator Response: It will probably be necessary to log off from TSO. Refer theproblem to your technical support team respons ible for SPICE.

SPI0613I ISPF SUBSYSTEM FAILURE - DSN SUBTASK OMITTEDExplanation: The parameter s tring passed to the SPICE operator subsys tem is invalid.


Programmer/Operator Response: Refer the problem to your technical support team respons iblefor SPICE. It is likely that the DB2 or IMS sys tem is defined in the SPICE operator subsys temsys tem table incorrectly. Examine the displayed message(s ), and take any appropriate action.

SPI0614I ISPF SUBSYSTEM FAILURE - INVALID DSN COMMAND LENGTHExplanation: The parameter s tring passed to the SPICE operator subsys tem is invalid.



SPI0615I ISPF SUBSYSTEM FAILURE - INVALID DSN SUB-COMMAND LENGTHExplanation: The parameter s tring passed to the SPICE operator subsys tem is invalid.



SPI0616I ISPF SUBSYSTEM FAILURE - UTILITY ALREADY ACTIVEExplanation: An attempt was made to initiate the SPICE utility subsys tem whils t it was alreadyactive.System Action: Execution of the operator subsys tem is terminated.

Programmer/Operator Response: It will probably be necessary to log off from TSO. Refer theproblem to your technical support team respons ible for SPICE. Examine the displayedmessage(s ), and take any appropriate action.


SPI0701I *ABEND* RESTART API FAILURE: INCOMPLETE PARAMETER LISTSPICE Restart API Explanation: The parameter lis t specified in a call to the SPICE res tart APIhad less than 2 items . The reques ted operation could not be processed.System Action: SPICE will ABEND with a user code of 4090.


SPI0702I *ABEND* RESTART API FAILURE: INVALID SRACA CONTENTSSPICE Restart API Explanation: The SRACA supplied in the parameter lis t specified in a callto the SPICE res tart API was invalid. Either the identification s tring, field SRAID value “SRACA”, or the length, field SRALEN, was incorrect. The reques ted operation could not beprocessed.

System Action: SPICE will ABEND with user code 4090.Programmer/Operator Response: Correct the problem and res tart the job.


SPI0703I RESTART API FAILURE: INVALID REQUEST CODESPICE Restart API Explanation: The reques t code supplied in the parameter lis t specified in acall to the SPICE res tart API was not recognised. The reques ted operation could not beprocessed.

System Action: SPICE will return an SRACODE of “-681”, an SRASTATE of “SR703”, and anSRASTAT of “AD” in the reques t SRACA.Programmer/Operator Response: Correct the problem and res tart the job.

SPI0704I RESTART API FAILURE: PROGRAM AREA NAME OMITTEDSPICE Restart API Explanation: No program area name was specified in the parameter lis tspecified in a program area management call to the SPICE res tart API. The reques ted operationcould not be processed.System Action: SPICE will return an SRACODE of “-681”, an SRASTATE of “SR704”, and anSRASTAT of “AB” in the reques t SRACA.


SPI0705I RESTART API FAILURE: PARAMETERS OMITTEDSPICE Restart API Explanation: Parameter(s ) were miss ing from the parameter lis t specifiedin a call to the SPICE res tart API. The reques ted operation could not be processed.

System Action: SPICE will return an SRACODE of “-681”, an SRASTATE of “SR705”, and anSRASTAT of “AH” in the reques t SRACA.


SPI0706I RESTART API FAILURE: EXCESSIVE PARAMETERSSPICE Restart API Explanation: Too many parameters were supplied in the parameter lis tspecified in a call to the SPICE res tart API. The reques ted operation could not be processed.

System Action: SPICE will return an SRACODE of “-681”, an SRASTATE of “SR706”, and anSRASTAT of “AJ” in the reques t SRACA.Programmer/Operator Response: Correct the problem and res tart the job.

SPI0707I RESTART API FAILURE: FILE DD NAME OMITTEDSPICE Restart API Explanation: No file DD name was supplied in the parameter lis t specifiedin a SPICE file management call to the SPICE res tart API. The reques ted operation could not beprocessed.System Action: SPICE will return an SRACODE of “-681”, an SRASTATE of “SR707”, and anSRASTAT of “AB” in the reques t SRACA.


SPI0708I RESTART API FAILURE: INVALID FILE OPEN MODESPICE Restart API Explanation: The parameter, supplied in the parameter lis t specified in afile open call to the SPICE res tart API, that indicated whether the file was being opened for inputor output, was not recognised. The parameter should take the value “INPUT” or “OUTPUT”. The reques ted operation could not be processed.System Action: SPICE will return an SRACODE of “-681”, an SRASTATE of “SR708”, and anSRASTAT of “AJ” in the reques t SRACA.


SPI0709I RESTART API FAILURE: COMMIT NOT SUPPORTEDSPICE Restart API Explanation: The program has is sued a commit reques t to the SPICEres tart API, but there was no res tart database available. The reques ted operation could not beprocessed.

System Action: SPICE does not issue a commit to the database management sys tem. SPICE willreturn an SRACODE of “-681”, an SRASTATE of “SR709”, and an SRASTAT of “AL” in thereques t SRACA.


SPI0710I RESTART API FAILURE: ROLLBACK NOT SUPPORTEDSPICE Restart API Explanation: The program has is sued a rollback reques t to the SPICEres tart API, but there was no res tart database available. The reques ted operation could not beprocessed.

System Action: SPICE does not is sue a rollback to the database management sys tem. SPICEwill return an SRACODE of “-681”, an SRASTATE of “SR710”, and an SRASTAT of “AL” inthe reques t SRACA.



SPI0711I RESTART API FAILURE: INVALID RANGE SPECIFIEDSPICE Restart API Explanation: The address range, supplied in the parameter lis t specified ina call to the SPICE res tart API, was invalid. Either the second address in the range preceded thefirs t, or the second did not address a valid range terminator. The reques ted operation could not beprocessed.System Action: SPICE will return an SRACODE of “-681”, an SRASTATE of “SR711”, and anSRASTAT of “AJ” in the reques t SRACA.


SPICE SQL™ SQLCA and SRACA Codes 3118 June 2009 © 1991,2009 Span Software Consultants Limited

Chapter 3. SPICE SQL™ SQLCA andSRACA Codes

Introduction

W hen the application program issues SPICE reques ts to SPICE SQL us ing SQL s tatements ,SPICE SQL returns s tatus information in the SQL communication area, the SQLCA. SPICE SQLalways returns values in the SQLCODE and SQLSTATE fields . The values conform to thosereturned by DB2, in s imilar circumstances . W here appropriate SPICE will return warn codes infields SQLW ARN0-7 and/or descriptive tokens in field SQLERRM. In some s ituations SPICESQL also is sues a message.

W hen the application program issues SPICE reques ts to the SPICE Res tart API, SPICE returnss tatus information in the SPICE res tart API communication area, the SRACA. SPICE returnsvalues in the SRACODE, the SRASTATE, the SRAERRM and SRASTAT fields . TheSRACODE, SRASTATE and SRAERRM fields conform to values returned by DB2 in fieldsSQLCODE, SQLSTATE and SQLERRM of the SQLCA. The SRASTAT field conforms tovalues returned by IMS in the s tatus code field of the IMS PCB. In some s ituations SPICE SQLalso issues a message.

The ERRM tokens are documented in their expanded form, as would be returned by a call to theDB2 module DSNTIAR.

For each unique combination of CODE, STATE and ERRM values issued by SPICE the followinginformation is provided:

Warn Codes: W hich, if any, SQLW ARN fields are set.

Explanation: W hat the code and message means ; why it occurred; what caused it.System Action: W hat SPICE will do as a result of the condition.

Programmer and/or Operator Response: W hat the programmer and/or operator shoulddo when the condition occurs .

SPICE CODE, STATE & ERRM Values

CODE: 000STATE: 00000ERRM:Warn Codes: All blank.

Explanation: The reques ted process ing was success fully performed.


Programmer Response: None.

CODE: 000STATE: 01501ERRM: INPUT RECORD TRUNCATEDWarn Codes: SQLW ARN0 and SQLW ARN1 set to “W ”.

Explanation: For a SPICE SAM file record input reques t, the length of the specified hos tvariable(s ) is less than the length of the record in the reques ted file. The input record is truncated. The reques ted process ing was success fully performed.

This could be caused by ass igning the wrong file to the program. It could also be caused byincorrect specification of the record I/O area s tructure.


Programmer Response: Ensure that both the input file and the I/O area it is being read into arecompatible.


CODE: 000STATE: 01501ERRM: PROGRAM AREA TRUNCATEDWarn Codes: SQLW ARN0 and SQLW ARN1 set to “W ”.

Explanation: For a SPICE PAM program area declaration, the length of the specified programarea is less than the length of the area in the res tart database. The program area is truncated. Thereques ted process ing was success fully performed.

System Action: Control is returned to the application program.Programmer Response: Ensure that both the input file and the I/O area it is being read into arecompatible.

CODE: +100STATE: 02000ERRM:Warn Codes: All blank.

SPICE SAM Input Request Explanation: This indicates end of file.

SPICE Program Area Declaration Explanation: This indicates that no res tart data exits for thespecified identifier in the SPICE res tart database.

Other SPICE Program Area Request Explanation: This indicates that a reques t was is suedagans t a program area that had not been declared.

SQL Commit Request Explanation: This indicates that the reques t was suppressed, i.e. nocommit point occurred.



CODE: -302STATE: SR031ERRM: OUTPUT RECORD TRUNCATIONWarn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.

Explanation: For a SPICE SAM file record output reques t, The length of the specified hos tvariable(s ) exceeds the maximum record length of the reques ted file. The data is truncated to themaximum record length.This can be caused by ass igning the wrong file to the program. It can also be caused by incorrectspecification of the record I/O area s tructure.

System Action: Control is returned to the application program.Programmer Response: Correct the problem and res tart the job.

CODE: -681STATE: SR002ERRM: DDNAME NOT FOUNDWarn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.

Explanation: The program issued a SPICE SAM open reques t when no file was allocated to thespecified DD name.

System Action: This code is accompanied by message SPI0002I. Control is returned to theapplication program.


CODE: -681STATE: SR005ERRM: CHANGE OF USE FOLLOWING RESTARTWarn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.

Explanation: An attempt was made to open a SPICE SAM file for input, following a res tart,when the file was previous ly open for output, or vice-versa.System Action: This code is accompanied by message SPI0005I. Control is returned to theapplication program.


CODE: -681STATE: SR009ERRM: FILE ALREADY OPENWarn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.

Explanation: An attempt was made to open a SPICE SAM file, when the file was already open.




CODE: -681STATE: SR026ERRM: INVALID PROCESSING OPTIONWarn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.

Explanation: An input reques t was made agains t an output file, or vice-versa. The reques tedoperation could not be processed.

System Action: This code is accompanied by message SPI0026I. Control is returned to theapplication program.Programmer Response: Correct the problem and res tart the job.

CODE: -681STATE: SR028ERRM: FILE NOT OPENWarn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.

Explanation: A reques t was made agains t a SPICE SAM file that was not open, or could not beopened. The reques ted operation could not be processed.



CODE: -681STATE: SR030ERRM: OPEN FAILUREWarn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.

Explanation: The “OPEN” reques t failed. “OPEN” reques ts can fail for one of the followingreasons :! The file was already open! The operating sys tem “OPEN” reques t failedThe reques ted operation could not be processed.

This can be caused by re-opening a SPICE SQL sequential file cursor following a commit point. SPICE SQL file cursors remain open following commit points .System Action: For operating sys tem “OPEN” failures and invalid DCBs SPICE issues a“SPI0030” or “SPI0035” message, respectively. Control is returned to the application program.Programmer Response: Correct the program, or SPICE SAM file, and res tart the job.

CODE: -681STATE: SR032ERRM: INVALID INPUT RECORD LENGTHWarn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.

Explanation: For a SPICE SAM file record input reques t, the length of the specified hos tvariable(s ) exceeds the length of the record in the reques ted file. The reques ted operation couldnot be processed.

This can be caused by ass igning the wrong file to the program. It can also be caused by incorrectspecification of the record I/O area s tructure.


CODE: -681STATE: SR033ERRM: INVALID FILE ACCESS METHOD

Warn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.

Explanation: The “OPEN” reques t failed. The SPICE SAM file is of a type not supported bySPICE. The reques ted operation could not be processed.


Programmer Response: Copy the file to a supported file type and res tart the job.

CODE: -681STATE: SR035ERRM: INVALID JFCB


Explanation: The “OPEN” reques t failed. A SPICE SAM statement has been issued agains t afile whose type is not supported by SPICE SAM, e.g. ISAM.System Action: This code is accompanied by message SPI0035I. SPICE issues a “SPI0035”message. Control is returned to the application program.

Programmer Response: Copy the file to a supported file type and res tart the job.


CODE: -681STATE: SR037ERRM: BSAM DCB ABEND


Explanation: An ABEND occurred during BSAM process ing to a SPICE SAM file. Thereques ted operation could not be processed.




System Action: This code is accompanied by message SPI0037I. SPICE issues a “SPI0035”message. Control is returned to the application program.

Programmer Response: Correct the program, or SPICE SAM file, and res tart the job.

CODE: -681STATE: SR038ERRM: BSAM I/O ERROR


Explanation: BSAM encountered an I/O error when process ing the reques t. The reques tedoperation could not be processed.






CODE: -681STATE: SR045ERRM: BSAM DCB ABEND IN OPENWarn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.

Explanation: An ABEND occurred during BSAM OPEN process ing for a SPICE SAM file. Thereques ted operation could not be processed.

Poss ible causes of this message are:! Invalid file DCB specification


Programmer Response: Correct the program, or SPICE SAM file, and res tart the job.

CODE: -681STATE: SR050ERRM: TOO FEW BUFFERS FOR REPOSITIONWarn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.

Explanation: Repos ition of a SPICE SAM file, typically performed during res tart, requires morebuffers than are defined.


CODE: -681STATE: SR261ERRM: TEST FACILITY: ERROR

Warn Codes: All blank.

Explanation: The application program has issued a SPICE services tes t reques t. The applicationJCL included DD name “xxxxxERR”, where “xxxxx” is the DDname prefix specified in thereques t.System Action: This code is accompanied by message SPI0261I. Control is returned to theapplication program.

Programmer/Operator Response: This problem should occur only in tes ting environments . Toprevent its recurrence, remove DD name “xxxxxERR” from the JCL. The job may then beres tarted.


CODE: -681STATE: SR502ERRM: INVALID VALUE LENGTH


Explanation: One of the hos t variables in the SPICE SQL reques t had an invalid length value. The reques ted operation could not be processed.


CODE: -681STATE: SR503ERRM: DUPLICATE VALUE


Explanation: The SPICE SQL request specified one of the SPICE hos t variable values more thanonce. The reques ted operation could not be processed.


CODE: -681STATE: SR504ERRM: OMITTED VALUE


Explanation: The SPICE SQL request omitted a required SPICE hos t variable value. Thereques ted operation could not be processed.



CODE: -681STATE: SR505ERRM: INVALID VALUE COMBINATION


Explanation: The SPICE SQL request specified an invalid combination of SPICE hos t variablevalues . The reques ted operation could not be processed.

A “!DDNAME!=...” value may have been specified on a “SPICE_PAM” reques t, for ins tance.System Action: This code is accompanied by message SPI0505I. Control is returned to theapplication program.Programmer Response: Correct the problem and res tart the job.

CODE: -681STATE: SR506ERRM: INVALID ACTION VALUE


Explanation: The SPICE SQL request included an invalid SPICE ACTION hos t variable value. The reques ted operation could not be processed.

The only valid values are “!ACTION!=OPEN_IN”, “!ACTION!=OPEN_OUT”,“!ACTION!=CLOSE” and “!ACTION!=TEST”.


CODE: -681STATE: SR507ERRM: INVALID STATUS VALUE


Explanation: The SPICE SQL request included an invalid SPICE STATUS hos t variable value. The reques ted operation could not be processed.

The only valid values are “!STATUS!=STATIC” and “!STATUS!=ACTIVE”.System Action: This code is accompanied by message SPI0507I. Control is returned to theapplication program.



CODE: -681STATE: SR509ERRM: CHANGE FROM STATIC TO STATIC INVALID


Explanation: The SPICE s tatement requested a change in program area s tatus to “s tatic” whenthe area was already “s tatic”, i.e. it was already frozen. The reques ted operation could not beprocessed.


CODE: -681STATE: SR510ERRM: SPICE DATABASE FAILURE (SQLCODE=s999)


Explanation: SPICE SQL received an invalid SQLCODE when process ing agains t the SPICESQL res tart database. The SQLCODE is documented in the SQLERRM tokens . The reques tedoperation could not be processed.System Action: This code is accompanied by message SPI0510I. Control is returned to theapplication program.

Programmer Response: Examine the reported SQLCODE. If the cause of the problem isevident, correct it and res tart the job. If not, refer it to your technical support team respons ible forSPICE.

CODE: -681STATE: SR511ERRM: AREA ALREADY SELECTED


Explanation: The SPICE SQL reques t attempted to declare a program area that had already beendeclared. The reques ted operation could not be processed.System Action: This code is accompanied by message SPI0511I. Control is returned to theapplication program.


CODE: -681STATE: SR513ERRM: AREA/RECORD NOT CONTIGUOUS


Explanation: The SPICE SQL reques t specified a set of hos t variables for a SPICE PAMprogram area or SPICE SAM record I/O area that did not collate into a s ingle area of s torage. Thereques ted operation could not be processed.

This problem can be created when COBOL programs specify a hos t s tructure containing“FILLER” variables . The DB2 precompiler omits “FILLER” variables from the lis t of variablesthat are passed to SPICE. If this is the case, changing their names to other than “FILLER” willcorrect the problem.System Action: This code is accompanied by message SPI0513I. Control is returned to theapplication program.


CODE: -681STATE: SR516ERRM: INVALID RECLEN PARAMETER


Explanation: The SPICE SQL SAM reques t specified an invalid value ass igned to the RECLENcolumn. The reques ted operation could not be processed.

The RECLEN parameter mus t take the value “!RECLEN!=<number>”, where “<number>”cons is ts only of the digits “0” to “9”.System Action: This code is accompanied by message SPI0516I. Control is returned to theapplication program.


CODE: -681STATE: SR517ERRM: INVALID FILE RECORD LENGTH


Explanation: The record length of a SPICE SAM file did not comply with the value specified inthe OPEN reques t. The reques ted operation could not be processed.


This can be caused by ass igning the wrong file to the program. It can also be caused by incorrectspecification of the OPEN parameters .System Action: This code is accompanied by message SPI0517I. Control is returned to theapplication program.


CODE: -681STATE: SR518ERRM: INVALID DDNAME PREFIXWarn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.

Explanation: A SPICE services tes t facility reques t specified a DDname prefix of less than therequired 5 characters .



CODE: -681STATE: SR520ERRM: CAF CONNECT FAILUREWarn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.

Explanation: A call to DB2 CAF failed.

System Action: This code is accompanied by message SPI0520I.

Programmer Response: Correct the problem and retry.

CODE: -681STATE: SR521ERRM: CAF OPEN FAILUREWarn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.

Explanation: A call to DB2 CAF failed.System Action: This code is accompanied by message SPI0520I.


CODE: -681STATE: SR522ERRM: CAF CLOSE FAILUREWarn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.




CODE: -681STATE: SR523ERRM: CAF DISCONNECT FAILUREWarn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.Explanation: A call to DB2 CAF failed.



CODE: -681STATE: SR524ERRM: INVALID CAF PLISTWarn Codes: SQLW ARN0 and SQLW ARN6 set to “W ”.


System Action: This code is accompanied by message SPI0520I.Programmer Response: Correct the problem and retry.

CODE: -681STATE: SR703ERRM: INVALID REQUEST CODEExplanation: A SPICE res tart API reques t specified a reques t code unknown to SPICE.




CODE: -681STATE: SR704ERRM: PROGRAM AREA NAME OMITTEDExplanation: A SPICE res tart API program area management reques t did not specify a name forthe area.System Action: This code is accompanied by message SPI0704I. Control is returned to theapplication program.


CODE: -681STATE: SR705ERRM: PARAMETERS OMITTEDExplanation: A SPICE res tart API reques t missed out a required parameter.



CODE: -681STATE: SR706ERRM: EXCESSIVE PARAMETERSExplanation: A SPICE res tart API reques t specified too many parameters .System Action: This code is accompanied by message SPI0706I. Control is returned to theapplication program.


CODE: -681STATE: SR707ERRM: FILE DD NAME OMITTEDExplanation: A SPICE res tart API sequential file reques t did not specify the required DD name.



CODE: -681STATE: SR708ERRM: INVALID FILE OPEN PARAMETERExplanation: A SPICE res tart API sequential file OPEN reques t did not specify a process ingmode known to SPICE. Valid values are “INPUT” & “OUTPUT”System Action: This code is accompanied by message SPI0708I. Control is returned to theapplication program.


CODE: -681STATE: SR709ERRM: COMMIT NOT SUPPORTEDExplanation: The application reques ted a commit when no res tart database was available. Thecommit could not be performed.System Action: This code is accompanied by message SPI0709I. Control is returned to theapplication program.


CODE: -681STATE: SR710ERRM: BACKOUT NOT SUPPORTEDExplanation: The application reques ted a rollback when no res tart database was available. Therollback could not be performed.



CODE: -681STATE: SR711ERRM: INVALID RANGEExplanation: A SPICE res tart API reques t specified an invalid address range. Either the secondaddress did not succeed the firs t, or it did not address a valid terminating s tring.



CODE: -911STATE: 40000ERRM: THE CURRENT UNIT OF WORK HAS BEEN ROLLED BACKExplanation: A rollback has occurred. The database management sys tem has abandoned allupdates s ince the previous success ful commit point. This s ituation can occur when SPICE isunable to complete a commit point success fully, because of a failure to the res tart database.System Action: This code is accompanied by message SPI0110I. Control is returned to theapplication program.


SPICE DL/I™ & SPICE Restart API Status Codes 4118 June 2009 © 1991,2009 Span Software Consultants Limited

Chapter 4. SPICE DL/I™ andSPICE Restart API Status Codes

Introduction

When the application program issues SPICE requests to SPICE DL/I, SPICE DL/Ireturns a two byte status code in the IMS PCB. The values returned conform to thosereturned by IMS, in similar circumstances. In some situations SPICE DL/I also issues amessage.

When the application program issues SPICE Restart API requests, SPICE returns a twobyte status code in field SRASTAT of the SRACA. The values returned are compatiblewith those returned by IMS in the PCB status code. In some situations SPICE alsoissues a message.

For each SPICE status code the following information is provided, where applicable:

Explanation: What the status code means; why it occurred; what caused it.

System Action: What SPICE will do as a result of the condition.

Programmer and/or Operator Response: What the programmer and/or operatorshould do when the condition occurs.

SPICE Status Codes

blankExplanation: A blank s tatus code is returned when the reques ted operation was success fullyprocessed.



ABSPICE DL/I Explanation: No I/O area was specified in the application reques t. The reques tedoperation could not be processed.

SPICE Restart API Explanation: Required parameter(s ) were miss ing from the applicationreques t. The reques ted operation could not be processed.


ADSPICE DL/I Explanation: An invalid function code was specified. The reques ted operationcould not be processed.

SPICE Restart API Explanation: An invalid SPICE res tart API reques t code was specified. The reques ted operation could not be processed.System Action: Control is returned to the application program.


AFExplanation: The length of the record is invalid. The reques ted operation could not beprocessed.System Action: Control is returned to the application program.

Programmer Response: Correct the program, or input file, and res tart the job.


AHSPICE DL/I Explanation: No record search argument was specified in a “GU” call. Thereques ted operation could not be processed.SPICE Restart API Explanation: Required parameter(s ) were miss ing from the applicationreques t. The reques ted operation could not be processed.


AIExplanation: The “OPEN” reques t failed. “OPEN” reques ts can fail for the following reasons :SPICE DL/I & SPICE Restart API! The reques ted DDname was not allocated in the job JCL.! The file was already open.! The file was being opened for input following a res tart from a checkpoint, when the file had

been open for output, or vice-versa.! The record s ize specified in the open reques t does not match that of the file.! The operating sys tem open reques t failed.! The file type is not supported by SPICE SAM.! The DCB for the SPICE SAM file is invalid.! Fewer buffers defined than required for repos ition, probably during res tart.! A SPICE services tes t facility reques t specified a DDname prefix of less than the required 5

characters .SPICE DL/I! The reques t IO area did not contain “INP”, “OUT”, “OUTA” or “OUTM”.! A record reques t (“GU”, “GN” or “ISRT”) was made when the (non-GSAM) file had not yet

been opened.

The reques ted operation could not be processed.

System Action: For operating sys tem “OPEN” failures and invalid DCBs, SPICE issues a“SPI0030” or “SPI0035” message, respectively. For the other causes , SPICE issues anappropriate message. Control is returned to the application program.


AJSPICE DL/I Explanation: Too many parameters have been specified in the SPICE DL/I SAMreques t. The reques ted operation could not be processed.

SPICE Restart API Explanation: The reques ted operation could not be processed, for one ofthe following causes :! Too many parameters have been specified in the SPICE res tart API reques t! Parameters defining a range in s torage were invalid. Either the second address did not

succeed the firs t, or the second did not address a valid terminator value.


ALExplanation: SPICE was unable to process a commit or rollback reques t, because no res tartdatabase was available. The reques ted operation could not be processed.



AMExplanation: An input reques t was made agains t an output file, or vice-versa. The reques tedoperation could not be processed.



ATExplanation: An IO area was specified for a SPICE SAM DL/I reques t, when none was required. The reques ted operation could not be processed.



BCExplanation: A rollback has occurred. The database management sys tem has abandoned allupdates s ince the previous success ful commit point. This s ituation can occur when SPICE isunable to complete success fully a commit point, because of a failure to the res tart database.

SPICE DL/I™ & SPICE Restart API Status Codes 4318 June 2009 © 1991,2009 Span Software Consultants Limited



GBExplanation: End of file was detected upon a record input reques t. The input reques t could notbe processed.



GESPICE PAM Explanation:! Program area Declaration:

The SPICE res tart database contains no res tart data for the program area. This usuallyindicates that the program is being s tarted.

! Other Program area Requests:The program area has not been declared.

Commit Request Explanation: The commit point was suppressed by SPICE. DB2 cursorprocess ing and IMS database pos ition are unaffected.System Action: Control is returned to the application program.


NOExplanation: BSAM encountered an I/O error when process ing the reques t. The reques tedoperation could not be processed.System Action: SPICE issues a “SPI0038” message. Control is returned to the applicationprogram.


RXExplanation:! Declaration Request:

The program area has already been declared.! Status Change Request:

The application reques ted that a program area be made s tatic when it was already s tatic,i.e. frozen.



X9SPICE SAM Explanation: A SPICE SAM file record was longer than the record area, asdefined at open.

SPICE PAM Explanation: A program area in the SPICE restart database was longer than thearea within the program.System Action: SPICE truncates the input record, to fit into the record area. Control is returnedto the application program.

Programmer Response: Correct the problem, if appropriate.

ZZExplanation: The application program has issued a SPICE services tes t reques t. The applicationJCL included DD name “xxxxxERR”, where “xxxxx” is the DDname prefix specified in thereques t.

System Action: This code is accompanied by message SPI0261I. Control is returned to theapplication program.Programmer/Operator Response: This problem should occur only in tes ting environments . Toprevent its recurrence, remove DD name “xxxxERR” from the JCL. The job may then beres tarted.

SPICE SQL™ and SPICE DL/I™ Abend Codes 4518 June 2009 © 1991,2009 Span Software Consultants Limited

Chapter 5. SPICE SQL™ andSPICE DL/I™ User Abend Codes

Introduction

This chapter lists the user abend codes issued by SPICE. In each case SPICE will alsoissue an error message. The messages associated with user abends are all flagged“*ABEND*”. Chapter 2 of this manual lists the messages issued by SPICE.

For each user abend code the following information is provided, where applicable:

Explanation: What the abend means; why it occurred; what caused it.



User Abend Codes

4090Explanation: This user abend code is is sued when SPICE encounters an error condition fromwhich it cannot continue executing.

System Action: The program abnormally terminates .

Programmer/Operator Response: Refer to the appropriate entry in Chapter 2 of this manual fordetails of the associated message.

4091Explanation: This user abend code is issued by the SPICE utility program SPIUTI00 when itencounters an error condition from which it cannot continue executing.

System Action: Program SPIUTI00 abnormally terminates .


4092Explanation: This user abend code is is sued after SPICE has detected an application timeoutcondition. This arises when the application program has failed to is sue a checkpoint over a userdefined interval. Typical causes of application timeout are program loops , wait s tates and poorapplication logic. The ABEND indicates an application program problem, detected by SPICE.

System Action: The program abnormally terminates .

Programmer/Operator Response: Report the problem as an application program failure.

4088Explanation: This user abend code can occur following a SPICE initiated User Abend when theapplication executes within the z/OS Language Environment. LE module CEEBINIT will haveintercepted the SPICE termination which in turn terminated with the User 4088 Abend, reasoncode 00000063. The SPICE problem will be documented by the preceding SPICE message.

System Action: Program SPIUTI00 abnormally terminates .


SPICE SQL™ and SPICE DL/I™ Internal Failure Codes 4718 June 2009 © 1991,2009 Span Software Consultants Limited

Chapter 6. SPICE SQL™ andSPICE DL/I™ Internal Failure Codes

Introduction

This Chapter details the SPICE SQL and SPICE DL/I failure codes. Most SPICEdetected failures use the failure code as their message number. The cause of thesefailures can be determined by examining the related message descriptions given inChapter 2 of this manual. The other failure codes are reported by SPICE using message“SPI0000I”, with the failure number contained in the message text. In general, thesefailure conditions relate to error conditions caused by invalid conditions in the SPICEenvironment. In most cases, these problems should be referred to your technical supportteam responsible for SPICE.

For each SPICE internal failure code the following information is provided, whereapplicable:

Explanation: What the failure code means; why it occurred; what caused it; themeaning of any additional parameters in the message.



Internal Failure Codes

SPICE FAILURE CODE 002Explanation: Refer to the description of message SPI0002I for details .






SPICE FAILURE CODE 010Explanation: SPICE detected an invalid SPICE SAM file type.


Programmer and/or Operator Response: Refer the problem to your technical support teamrespons ible for SPICE.




SPICE FAILURE CODE 017Explanation: A SPICE control block has been corrupted.System Action: SPICE will ABEND with user code 4090.



SPICE FAILURE CODE 019Explanation: SPICE DL/I failed to determine the application IMS region type.System Action: SPICE will ABEND with user code 4090.

Programmer and/or Operator Response: Correct the problem and res tart the job.


SPICE FAILURE CODE 021Explanation: A SPICE “SIVT” control block has been corrupted.










SPICE FAILURE CODE 029Explanation: A SPICE control block has been corrupted.








SPICE FAILURE CODE 034Explanation: A SPICE control block has been corrupted.

System Action: SPICE will ABEND with user code 4090.Programmer and/or Operator Response: Refer the problem to your technical support teamrespons ible for SPICE.






SPICE FAILURE CODE 043SPICE SQL Explanation: SPICE failed to repos ition a SPICE SAM file, during res tartprocess ing.

SPICE DL/I Explanation: SPICE failed to repos ition a SPICE SAM file, during res tart or “GU”process ing.






SPICE FAILURE CODE 100Explanation: Exceptional condition has occurred in SPICE process ing.





SPICE FAILURE CODE 103Explanation: An item of a SPICE restart was found to be corrupt. This problem may occur withSPICE DL/I following a failure, when IMS database backout was not performed before a res tartwas attempted.


Programmer and/or Operator Response: For SPICE DL/I applications , ensure that IMSdatabase backout has been performed. If not, do IMS database backout and res tart the job. Otherwise, refer the problem to your technical support team respons ible for SPICE.










SPICE FAILURE CODE 114Explanation: The SPICE DL/I MSDB res tart database is corrupt.System Action: SPICE will ABEND with user code 4090.













SPICE FAILURE CODE 202Explanation: The “ATTACH” of the SPICE subtask failed. The attach return code isdocumented in message SPI0000I.System Action: SPICE will ABEND with user code 4090.

Programmer and/or Operator Response: Examine the value of the return code. If the cause ofthe problem is apparent, correct it and res tart the job. If not, refer the problem to your technicalsupport team respons ible for SPICE.


SPICE FAILURE CODE 203Explanation: The SPICE subtask has failed. Message SPI0000I identifies its failure code. Avalue of “4” indicates that an invalid reques t was made to the SPICE subtask.







SPICE FAILURE CODE 210Explanation: SPICE application timeout has occurred. This condition will be accompanied byone or more of the following messages : SPI0211W , SPI0212A, SPI0213I, SPI0214I or SPI0217I. Refer to the description of the displayed messages for details .

SPICE FAILURE CODE 216Explanation: SPICE application timeout has occurred, and execution of the application programis abnormally terminated. Message SPI0213I documents the failure.


Programmer and/or Operator Response: Report the problem as an application programfailure.


SPICE FAILURE CODE 218Explanation: SPICE application timeout has occurred, and execution of the application programis abnormally terminated. Message SPI0213I documents the failure.


Programmer and/or Operator Response: Report the problem as an application programfailure.







SPICE FAILURE CODE 304Explanation: The command being processed is incomplete. This is an internal failure of theSPICE utility pars ing routines .



SPICE FAILURE CODE 307Explanation: The command table being processed by the SPICE utility pars ing routines isinvalid.System Action: SPICE will ABEND with user code 4091.


SPICE FAILURE CODE 314Explanation: A SPICE pars ing routine “SPW A” control block has been corrupted.



SPICE FAILURE CODE 315Explanation: A critical error has occurred, in the execution of the SPICE pars ing routine“SPIPGCMD”.

























SPICE FAILURE CODE 500Explanation: Exceptional condition has occurred in SPICE SQL process ing.


SPICE FAILURE CODE 501Explanation: SPICE SQL could not process the SQL parameter lis t.
















SPICE FAILURE CODE 700Explanation: Exceptional condition has occurred in SPICE Res tart API process ing.System Action: SPICE will ABEND with user code 4090.













SPICE™ Format ted Dump Contents 5718 June 2009 © 1991,2009 Span Software Consultants Limited

Chapter 7. SPICE™ Formatted DumpContents

Introduction

This chapter explains the contents of the SPICE formatted dump. The dump is producedin two circumstances. Firstly, it is produced when SPICE determines an error in itsprocessing, from which it cannot recover. Alternatively, the dump is produced when theESTAE exit of the SPICE subtask is invoked by z/OS, after a program interrupt, forexample. In the second circumstance, it is possible that the failure was caused by theapplication, the database management system, or z/OS. Failures caused by SPICE canusually be distinguished by, either the issuing of a SPICE failure message, or the SPICEformatted dump summary section identifying a SPICE module.

The formatted dump contains all of the SPICE control blocks active in a failed job, in areasonably compact form. It is intended for use by the vendor's support staff. It usuallycontains sufficient information to determine an error in SPICE.

SPICE writes its dump to DD name SPIUDUMP. If nothing is allocated to the DD name,SPICE will dynamically allocates a class A SYSOUT dataset to it.

The dump begins with the highlighted message START OF FORMATTED DUMP. It endswith the message END OF FORMATTED DUMP. The contents of the dump are in threesections, namely, the SPICE failure summary, the SPICE control block and IMS PCBsection, and the SCP control blocks.

Formatted Dump Sections

• SPICE Failure Summary on page 57• SPICE Control Blocks and IMS PSB Contents on page 58• SCP Control Blocks on page 58

SPICE Failure Summary

This section attempts to identify the location of the failure, using the contents of theregisters at the time of the failure. If the conventions of using register 12 as baseregister, and identifying the module name at offset 5 from its origin, are followed, thename of the module in control at the time of the failure will be located. All SPICEroutines (and many operating system and database management system routines also)follow this convention. If possible SPICE will also report the offset of the point offailure from the beginning of the module. The following items may be reported in thissection:

SPICE FAILURE CODE ccc The failure was detected by SPICE, and assigned SPICEcode ccc. SPICE will typically issue error message SPI0ccc or, in thecase of SPICE internal failures, message SPI0000. After issuing thedump SPICE will ABEND with user code 4090.


USER ABEND CODE uuuu The failure was detected by the SPICE ESTAE exit,when the application issued a user ABEND code uuuu.

SYSTEM ABEND CODE sss The failure was detected by the SPICE ESTAE exit,when the application failed with a system ABEND code sss, inhexadecimal.

MODULE The first 24 bytes of the highlighter at the beginning of the module incontrol at the time of the failure, assuming register 12 as the baseregister. For SPICE modules this highlighter contains the name of themodule and its service level. If it cannot be determined, it is reported as********.

OFFSET The hexadecimal offset of the point of failure from the register 12address. If it cannot be determined, it is reported as ****.

REGISTER CONTENTS The contents of the registers at the time of the failure, inhexadecimal.

SPICE FAILURE MESSAGE The text of the SPICE message associated with thefailure.

SPICE Control Blocks and IMS PSB Contents

This section contains the contents of the major SPICE and database management systemcontrol blocks. Each item is identified by a message, prefixed with ======.

A brief description of the items reported in this section of the dump follows.

SPICE ITEM ID <...> KEY <SIVT ...> This message identifies a section of the SIVT controlblock. The title of the section is reported in the field labelledKEY <...>.

The SPICE Interface Vector Table is the central control block throughwhich SPICE addresses all its other control blocks, loaded routines etc. Their contents are included in the dump.

APPLICATION SQLCA The contents of the SQLCA for the application program modulethat issued the current, or last, SQL statement.

SPICE SQL DDM SQLCA The contents of the SQLCA for the SPICE SQL restart databasetable access routines.

SPICE ITEM ID <SSPD> KEY < value > This message identifies an SSPD control blockfor the named SPICE SAM sequential file.

The SSPD is used to store information about a SPICE SAM dataset,including the name of the DD statement that it is allocated to. There isone SSPD for each open SPICE SAM dataset. For SPICE SAM filesaccessed through SPICE DL/I, the GSAM or SSAM PCB used to accessthe dataset, addressed from the SSPD, is included in the dump, labelledSSAM PCB.

SPICE ITEM ID <SSBC> KEY <ddname number > This message identifies an SSBC

control block of the named SPICE SAM sequential file.The SSBC represents each of the buffers of an open SPICE SAM file. The contents of the buffer are also included in the dump, labelled I/OBUFFER.

SPICE ITEM ID <SPAD> KEY <name> This message identifies a SPAD controlblock for the named program area.

Each SPAD represents a declared restart area of the program.

SCP Control Blocks

This section contains a SNAP dump of the major z/OS control blocks for the applicationprogram. The TCBs for the application subtask and/or the SPICE subtask are reported.

Release 3.1 SPI 10 15 - spansoftware.com · the SQLCODE, SQLSTATE and SQLERRM fields. SPICE uses...

Documents

Transcript of Release 3.1 SPI 10 15 - spansoftware.com · the SQLCODE, SQLSTATE and SQLERRM fields. SPICE uses...