Package com.softwaremining.ims
Interface IMSStatusCodes
public interface IMSStatusCodes
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final Stringduring batch processing, an IPL is haltedstatic final Stringduring batch processing, IPL is restarted under UCFstatic final Stringduring batch processing both checkpoint and program haltedstatic final Stringduring an insert or update length of variable length segment is too longstatic final Stringdatabase is not openstatic final Stringduring index maintenance, a segment was not foundstatic final Stringunique secondary index but duplicate key encounteredstatic final Stringphysical I/O errorstatic final Stringinformation only, REPL DLET or ISRT may return BA status codestatic final Stringlength of message segment is less than 5 bytesstatic final Stringterminal symbolic error encounteredstatic final Stringtoken does not match any on an outstanding SETS callstatic final StringROLS call was rejectedstatic final Stringstorage space for I/O area unavailable on SETS callstatic final StringDL/I is not activestatic final Stringencountered conflict in scheduling intentstatic final Stringinvalid system DIB was foundstatic final Stringmessage scheduled before IMS was started and message retrieved by GU originated from an AOI user exitstatic final StringIMS rescheduled a message as a result of a call with the function GU since the last CMD call, message scheduled before IMS was started, and message retrieved by GU originated from an AOI user exitstatic final Stringarithmetic overflow errorstatic final Stringattempted to cross unit-of-work boundarystatic final Stringattempted to set 10 levels (only 9 are allowed)static final StringREPL or DLET attempted to change segment key fieldstatic final Stringduring batch processing, a checkpoint record was written to the utility control facility (UCF) datasetstatic final Stringa CHKP function issued a transaction oriented BMP or a message call has more than 4 parametersstatic final Stringbuffer limit for region exceededstatic final Stringcall not completed because data is not available, operations by current call up to this error have been backed outstatic final Stringcall not completed because data is not available, operations since last commit point have been backed outstatic final StringCICS command level failed because PSB is not definedstatic final StringCICS XDLIPRE exit cancelled a requeststatic final StringCMD function command from an AOI program not allowedstatic final StringCMD function command verb invalidstatic final Stringexception response occurred when executing a command issued via CMD callstatic final Stringafter command completed successfully, IMS returned one or more command responsesstatic final Stringprogram does not have authority to execute a command listed in this CMD functionstatic final Stringone or more databases not availablestatic final Stringerror opening databasestatic final StringDEDB was not accessible when database call was issued or commit point was reachedstatic final StringDLET violated delete rule for segmentstatic final Stringrandomizer did not return a DMAC addressstatic final StringFLD function received non blank status code in FSA and program has used all of buffer poolstatic final Stringfield name of FSA undefined in DBD and FLD function issuedstatic final StringISRT function message length exceeds allowable lengthstatic final Stringget hold issued after REPL or DLETstatic final StringGN requested but no more message segments existstatic final StringGN not followed by GU message requeststatic final StringGU message request failedstatic final Stringmessage retrieved by GU originated from an AOI user exitstatic final Stringhierarchical error on insert or get callstatic final StringI/O area address not accessible to programstatic final Stringcall type and segment type are incompatiblestatic final Stringfunction specified is not compatible with one of segment sensitivity, program type, or PCB processingstatic final Stringfunction argument is not coded correctlystatic final Stringsize of variable length record is invalid for GSAM get accessstatic final Stringparameter list specified incorrectly on ISRT or PURG callstatic final StringPCB specified incorrectly for a CHNG callstatic final StringPCB specified incorrectly for an ISRT or PURG callstatic final Stringfield name specified for qualified SSA is incorrectly codedstatic final Stringattempt to insert a segment with a duplicate keystatic final Stringinsert rule violationstatic final Stringinvalid SSA encountered on insert callstatic final Stringpath to segment is invalidstatic final Stringvalue in PSBIOAZ field is incorrectstatic final StringSSA specified for the call is invalidstatic final Stringinvalid hex or packed field in I/O areastatic final StringI/O area specified is too smallstatic final StringISRT function message to response alternate PCB ignored because SAMETRM=YESstatic final StringISRT function issued to a response alternate PCB must follow ISRT to I/O PCB and these statements are reversedstatic final StringISRT function number of messages added exceeds maximum allowedstatic final Stringlength for SSAs specified exceeds the maximum allowedstatic final Stringattempt to load a segment that already existsstatic final Stringhierarchical sequence in DBD does not match that in the segment to be loadedstatic final Stringattempt to load a segment out of sequencestatic final Stringattempt to load a segment whose parent does not existstatic final StringLOG request has an invalid log codestatic final Stringposition in database loststatic final Stringthe alternate PCB contains a transaction code instead of a logical terminal as a destinationstatic final Stringlogical terminal name specified incorrectly in I/O area for a CHNG callstatic final Stringterminal name invalid on ISRT message callstatic final Stringlogical terminal name found in a response alternate PCB has more than one physical terminal assignedstatic final Stringmessage scheduled before IMS was startedstatic final StringIMS rescheduled a message as a result of a call with the function GU since the last CMD call and message scheduled before IMS was startedstatic final StringIMS rescheduled a message as a result of a call with the function GU since the last CMD call and message retrieved by GU originated from an AOI user exitstatic final StringIMS rescheduled a message as a result of a call with the function GU since the last CMD callstatic final StringMSDB did not contain free space when ISRT was issuedstatic final Stringprogram has used all of buffer poolstatic final StringFLD function received non blank status code in FSAstatic final Stringnumber of SSAs exceeds limit of 15 for DEDB or 1 for MSDBstatic final Stringbatch program has issued a ROLS, ROLB, or SETS call and either the system log does not reside on disk or dynamic backout is not specifiedstatic final Stringpath replace error foundstatic final StringI/O PCB access not allowed in a local DL/I callstatic final Stringa physical I/O error has occurredstatic final Stringprocessing with procopt of GON or GOT and concurrent update activity is occurringstatic final StringPROCOPT invalidstatic final Stringno PSB scheduled for programstatic final Stringno PSB scheduled for programstatic final Stringunable to initialize the specified PSBstatic final StringPSB in use by previous requeststatic final Stringreplace rule violationstatic final Stringresource deadlockstatic final Stringsecurity violationstatic final Stringsegment not found - called by GetNextInParent (GNP)static final Stringsegment length longer than 64kstatic final StringSETS call was rejectedstatic final StringGNP issued but parentage was not previously establishedstatic final Stringverify operation failed at commit pointstatic final Stringsegment I/O area is missing from call statementstatic final Stringcall completed successfullystatic final Stringend of database reached on GN callstatic final Stringcall completed successfully but higher level crossed for GN or GNP callstatic final Stringcall completed successfully but different segment type on same level retrieved for GN or GNP callstatic final StringAutomated Operator Interface (AOI) encountered a system error, current command not ignoredstatic final Stringa PURG or ISRT was ignored in a conversational program
-
Field Details
-
IMS_RC_SUCCESS
-
IMS_RC_ERR_LTERM_1
the alternate PCB contains a transaction code instead of a logical terminal as a destination- See Also:
-
IMS_RC_MISSING_SEG_IO_AREA
segment I/O area is missing from call statement- See Also:
-
IMS_RC_ERR_HIER_INSERT
-
IMS_RC_ERR_INCORRECT_FUNC_ARGS
function argument is not coded correctly- See Also:
-
IMS_RC_ERR_INCORRECT_LEN
size of variable length record is invalid for GSAM get access- See Also:
-
IMS_RC_ERR_INVALID_INSERT_SSA
-
IMS_RC_ERR_DB_OPEN
-
IMS_RC_ERR_INVALID_SSA
-
IMS_RC_ERR_INCORRECT_SSA_FIELDNAME
field name specified for qualified SSA is incorrectly coded- See Also:
-
IMS_RC_ERR_ON_ROL_SET
batch program has issued a ROLS, ROLB, or SETS call and either the system log does not reside on disk or dynamic backout is not specified- See Also:
-
IMS_RC_ERR_INCOMPATIBLE_SENSEG_OR_PGM_OR_PCB
function specified is not compatible with one of segment sensitivity, program type, or PCB processing- See Also:
-
IMS_RC_ERR_PHYSICAL_IO
-
IMS_RC_ERR_BMP_CHKP_WITH_MORE_THAN_4_PARMS
a CHKP function issued a transaction oriented BMP or a message call has more than 4 parameters- See Also:
-
IMS_RC_ERR_IO_AREA_TOO_SMALL
-
IMS_RC_ERR_LENGTH_OF_SSA_EXCEDED
length for SSAs specified exceeds the maximum allowed- See Also:
-
IMS_RC_ERR_MORE_THAN_ONE_TERM_NAME
logical terminal name found in a response alternate PCB has more than one physical terminal assigned- See Also:
-
IMS_RC_WRN_PURGE_ISRT_IGNORED
a PURG or ISRT was ignored in a conversational program- See Also:
-
IMS_RC_ERR_LTERM_IN_IO_FOR_CHNG
logical terminal name specified incorrectly in I/O area for a CHNG call- See Also:
-
IMS_RC_ERR_INCORRECT_PCB_FOR_CHNG
PCB specified incorrectly for a CHNG call- See Also:
-
IMS_RC_ERR_INCORRECT_PCB_FOR_ISRT_PURG
PCB specified incorrectly for an ISRT or PURG call- See Also:
-
IMS_RC_ERR_SECURITY_VIOLATION
-
IMS_RC_ERR_INCORRECT_PARMS_ISRT_PURG
parameter list specified incorrectly on ISRT or PURG call- See Also:
-
IMS_RC_ERR_FUNC_MESS_LEN_EXCEDED
ISRT function message length exceeds allowable length- See Also:
-
IMS_RC_ERR_ISRT_TOO_MANY_MESS
ISRT function number of messages added exceeds maximum allowed- See Also:
-
IMS_RC_ERR_ISRT_A8
ISRT function issued to a response alternate PCB must follow ISRT to I/O PCB and these statements are reversed- See Also:
-
IMS_RC_ERR_ISR_SAMETRM
ISRT function message to response alternate PCB ignored because SAMETRM=YES- See Also:
-
IMS_RC_ERR_CALL_FAILED_DUE_TO_UNAVAIL_DATA__WITH_BU
call not completed because data is not available, operations by current call up to this error have been backed out- See Also:
-
IMS_RC_ERR_CALL_FAILED_DUE_TO_UNAVAIL_DATA__WITHOUT_BU
call not completed because data is not available, operations since last commit point have been backed out- See Also:
-
IMS_RC_ERR_CMB_HAS_INVALID_VERB
-
IMS_RC_ERR_CMB_FROMM_AOI_NOT_ALLOWED
CMD function command from an AOI program not allowed- See Also:
-
IMS_RC_ERR_CMD_HAS_MULTI_RESPONSES
after command completed successfully, IMS returned one or more command responses- See Also:
-
IMS_RC_ERR_CMD_SECURITY
program does not have authority to execute a command listed in this CMD function- See Also:
-
IMS_RC_ERR_MSSG_RESCHEDULED_FOR_GU
IMS rescheduled a message as a result of a call with the function GU since the last CMD call- See Also:
-
IMS_RC_ERR_MSSG_RESCHEDULED
-
IMS_RC_ERR_GU_MSSG_RETRIEVED_FROM_AOI_EXIT
message retrieved by GU originated from an AOI user exit- See Also:
-
IMS_RC_WRN_AOI_FAILED
Automated Operator Interface (AOI) encountered a system error, current command not ignored- See Also:
-
IMS_RC_ERR_MSSG_RESCHEDULED_CI
IMS rescheduled a message as a result of a call with the function GU since the last CMD call and message scheduled before IMS was started- See Also:
-
IMS_RC_ERR_MSSG_RESCHEDULED_CJ
IMS rescheduled a message as a result of a call with the function GU since the last CMD call and message retrieved by GU originated from an AOI user exit- See Also:
-
IMS_RC_ERR__MSSG_RESCHEDULED_CK
message scheduled before IMS was started and message retrieved by GU originated from an AOI user exit- See Also:
-
IMS_RC_ERR__MSSG_RESCHEDULED_CL
IMS rescheduled a message as a result of a call with the function GU since the last CMD call, message scheduled before IMS was started, and message retrieved by GU originated from an AOI user exit- See Also:
-
IMS_RC_ERR_CMD_EXCEPTION
exception response occurred when executing a command issued via CMD call- See Also:
-
IMS_RC_ERR_INVALID_PSBIOAZ_FIELD
-
IMS_RC_ERR_ATTEMPTED_TO_CHANGE_SEG_KEY_FIELD
REPL or DLET attempted to change segment key field- See Also:
-
IMS_RC_ERR_GH_AFTER_REPL_or_DLET
-
IMS_RC_ERR_DLET_VIOLATION
-
IMS_RC_ERR_ARITHMATIC_OVERFLOW
-
IMS_RC_ERR_INCOMPATIBLE_CALL_n_SEG_TYPE
call type and segment type are incompatible- See Also:
-
IMS_RC_ERR_RESOURCE_DEADLOCK
-
IMS_RC_ERR_NON_BANK_IN_FSA
FLD function received non blank status code in FSA- See Also:
-
IMS_RC_ERR_NO_FREE_SPCE_in_MSDB
MSDB did not contain free space when ISRT was issued- See Also:
-
IMS_RC_ERR_FLD_FSA_PRG_BUFFER_OVERLOAD
FLD function received non blank status code in FSA and program has used all of buffer pool- See Also:
-
IMS_RC_ERR_DEDB_INACCESSIBLE
DEDB was not accessible when database call was issued or commit point was reached- See Also:
-
IMS_RC_ERR_INACCESSIBLE_IO_AREA
I/O area address not accessible to program- See Also:
-
IMS_RC_ERR_DMAC_ADDRESS
-
IMS_RC_ERR_FSA_UNDEFINED_IN_DBD_n_FLD
field name of FSA undefined in DBD and FLD function issued- See Also:
-
IMS_RC_ERR_INVALID_VALUE_IN_IO_AREA
invalid hex or packed field in I/O area- See Also:
-
IMS_RC_ERR_BUFFER_LIMIT_EXCEEDED
-
IMS_RC_ERR_NUM_SSA_EXCEEDED
number of SSAs exceeds limit of 15 for DEDB or 1 for MSDB- See Also:
-
IMS_RC_ERR_VERFY_FAILED_AT_COMMIT
verify operation failed at commit point- See Also:
-
IMS_RC_ERR_NO_MORE_BUFFER_POOLS
-
IMS_RC_SUCCESS_HIERARCH_BOUNDRY_CROSSED
call completed successfully but higher level crossed for GN or GNP call- See Also:
-
IMS_RC_SUCCESS_END_OF_DB
-
IMS_RC_ERR_ATTEMPT_TO_CROSS_UOW_BOUNDRY
attempted to cross unit-of-work boundary- See Also:
-
IMS_RC_ERR_LOST_POS_IN_db
-
IMS_RC_ERR_SEG_NOT_FOUND
segment not found - called by GetNextInParent (GNP)- See Also:
-
IMS_RC_ERR_PROCOPT_GON_GOT
processing with procopt of GON or GOT and concurrent update activity is occurring- See Also:
-
IMS_RC_SUCCESS_WITH_DIFF_SEG_TYPE
call completed successfully but different segment type on same level retrieved for GN or GNP call- See Also:
-
IMS_RC_ERR_LOG_INVALID_CODE
-
IMS_RC_ERR_UNESTABLISED_PARENT
GNP issued but parentage was not previously established- See Also:
-
IMS_RC_ERR_INSERT_DUP_KEY
attempt to insert a segment with a duplicate key- See Also:
-
IMS_RC_ERR_INSERT_VIOLATION
-
IMS_RC_ERR_LOAD_EXISTING_SEGM
attempt to load a segment that already exists- See Also:
-
IMS_RC_ERR_LOAD_OUT_OF_SEQ_SEGM
attempt to load a segment out of sequence- See Also:
-
IMS_RC_ERR_LOAD_SEGM_INVALID_PARENT
attempt to load a segment whose parent does not exist- See Also:
-
IMS_RC_ERR_LOAD_INVALID_DBD_SEQ_DEFINIED
hierarchical sequence in DBD does not match that in the segment to be loaded- See Also:
-
IMS_RC_ERR_LTERM_INVALID_NAME
terminal name invalid on ISRT message call- See Also:
-
IMS_RC_ERR_DB_NOT_AVAILABLE
-
IMS_RC_ERR___NE
-
IMS_RC_ERR___NI
-
IMS_RC_ERR___NO
-
IMS_RC_ERR___NU
information only, REPL DLET or ISRT may return BA status code- See Also:
-
IMS_RC_ERR_GU_FAILED
-
IMS_RC_ERR_GN_NO_MORE_MESS_SEGMS
GN requested but no more message segments exist- See Also:
-
IMS_RC_ERR_GN_NOT_FOLLOWED_BY_GU
GN not followed by GU message request- See Also:
-
IMS_RC_ERR___QF
-
IMS_RC_ERR___QH
-
IMS_RC_ERR___RA
-
IMS_RC_ERR___RC
-
IMS_RC_ERR_REPL_VIOLATION
-
IMS_RC_ERR___SA
-
IMS_RC_ERR_ATTEMPT_TO_SET_10_LEVELS
attempted to set 10 levels (only 9 are allowed)- See Also:
-
IMS_RC_ERR_SETS_REJECTED
-
IMS_RC_ERR_CICS_FAILED
CICS command level failed because PSB is not defined- See Also:
-
IMS_RC_ERR_PSB__TC
-
IMS_RC_ERR_PSB___UNABLE_TO_INITIALIZE
unable to initialize the specified PSB- See Also:
-
IMS_RC_ERR_PSB___NOT_SCHEDULED
-
IMS_RC_ERR_PSB___NOT_SCHEDULED_TH
-
IMS_RC_ERR_INVALID_PATH_TO_SEGMN
-
IMS_RC_ERR___TJ
-
IMS_RC_ERR___TL
-
IMS_RC_ERR___TN
-
IMS_RC_ERR_PATH_REPLACE
-
IMS_RC_ERR_PROCOPT_INVALID
-
IMS_RC_ERR_PCB__TQ
-
IMS_RC_ERR_CICS_XDLIPRE_CANCELLED
CICS XDLIPRE exit cancelled a request- See Also:
-
IMS_RC_ERR___DB
-
IMS_RC_ERR_SEGM__64K
-
IMS_RC_ERR_BATCH___UC
during batch processing, a checkpoint record was written to the utility control facility (UCF) dataset- See Also:
-
IMS_RC_BATCH_ERR___IPL_RESTARTED
during batch processing, IPL is restarted under UCF- See Also:
-
IMS_RC_BATCH_ERR___IPL_HALTED
during batch processing, an IPL is halted- See Also:
-
IMS_RC_BATCH_ERR_CHK_POINT_n_PRGM_STOPPED
during batch processing both checkpoint and program halted- See Also:
-
IMS_RC_BATCH_ERR_VAR_LEN_TOO_LONG
during an insert or update length of variable length segment is too long- See Also:
-