Codes 401 - 4091

In this section:

About User Abend Codes

Explanations of Common User Abend Codes

When a Server for OS/390 and z/OS job terminates abnormally, it produces a user abend code that can help you resolve the problem.

Top of page

About User Abend Codes

The largest number that may be used for a user abend code is 4095. All abend codes are truncated to the low order three hex digits.

Top of page

Explanations of Common User Abend Codes

Provided here are explanations of common user abend codes as well as debugging instructions.

Abend Code

Description 

401

Invalid ID stamp in the HiperFOCUS control block. The following reason codes are associated with this abend:

101 HFMCB

201 HSMCB

202 HSBLOK

301 VIMCB

302 VIBLOK

303 MEMBLOK 

402

HiperFOCUS subsystem API usage error. The following reason codes are associated with this abend:

301 IODDN and ERRGET aren't allowed to share files.
302 Attempted call to VISET while file open.
303 Too many opens against non-PDS in VIOPN.
304 Invalid value for MODE in viopn.
305 Can't update a recfm-V file.
306 VIGETL may not be called on a BASRD-owned file. 

403

Integrity error in module HFINST. The following reason codes are associated with this abend:

101 Cannot load module HFINST.
102 Leading eye catcher mismatch.
103 Module name not HFINST0.
104 Module version not 00000001.
105 Table_entries not expected value.
106 Table_size .NE. calculated value.
107 Table_end .NE. calculated value.
108 Installed_flag not 0 or 1.
109 Trailer's calcents mismatch with expected.
110 Header status pointer aimed wrong.
111 Assembly status not zero.
112 Trailing eye catcher mismatched.
113 Opt_number mismatch.
114 Opt_name mismatch. 

404

Integrity error in HiperFOCUS data structures. The following reason code is associated with this abend:

301 Non-zero memblok count in kill_all_membloks. 

405

Error obtaining storage for the HiperFOCUS control block. The following reason codes are associated with this abend:

101 Cannot allocate an HFMCB.
201 Cannot allocate an HSMCB.
202 Cannot allocate an HSBLOK.
301 Cannot allocate a VIMCB. 

406

Error obtaining storage for the HiperFOCUS buffer. The following reason codes are associated with this abend:

201 Cannot allocate Hiperfile buffer during Hiperspace initialization.
301 Cannot get buffer in init_memblok. 

407

Error or unexpected results in system interface routine. The following reason codes are associated with this abend:

301 Error in rdjfcb call from vichk.
302 Handling of ABSTR space request. 

408

Unexpected error in Hiperspace creation, deletion, or manipulation. The following reason codes are associated with this abend:

201 Error closing a Hiperspace in HSTERM.
202 Error in DSPSERV CREATE.
203 Error in ALESERV ADD.
204 Error in ALESERV DELETE.
205 Error in DSPSERV DELETE.
206 Error in HSSWRITE.
207 Error in HSSREAD.
208 Error in HSEXTEND.
209 Error in HSRELEAS.
210 Spill to disk: no secondary space set - spill disabled.
211 Spill to disk: error while dynamic allocation of spill file. Is accompanied by DYNAM error message.
212 Spill to disk: internal error. Usually no memory, or TRACKIO is set to OLD, which is not allowed in HiperFOCUS with spill-over feature.
213 Spill to disk: track I/O get?put error.
214 System/user limits exceeded; file was to be reallocated. Allocation did not succeed. 

409

Internal processing error in the Hiperspace subsystem. The following reason codes are associated with this abend:

101 Cannot find mailbox after self-init.
102 Cannot allocate a mailbox.
201 Impossible code path reached in HSOPN.
301 Error killing a temp file in viterm.
302 Error in vicls call from vichk/case 1/1.
303 Error in viset call from vichk/case 1/1.
304 Error in vicls call from vichk/case 1/2.
305 Error in viset call from vichk/case 1/2.
306 Error in viset call from vichk/case 2.
307 Error in vikill call from vichk.
308 Error freeing Hiperspace pages in HSREL call from VIOPN.
309 Cannot get first buffer back (VIOPN or READ_VARIABLE).
310 Encountered MODE_APPEND/IO_TYPE_VARIABLE.
311 Error in viqry call from visnap.
312 Error making a Hiperspace in viutil/make_hiperspace.
313 Error closing a Hiperspace in kill_all_membloks.
314 A viblok not added in vichk.
315 Output buffer overflow in hfputtrc. 

410

Hiperspace overflow. The following reason codes are associated with this abend:

201 Attempt to create Hiperspace larger than installation limits.
202 Attempt to expand Hiperspace past installation limits. 

411

Initialization error. The following reason codes are associated with this abend:

201 Error initializing HS subsystem.
301 Error initializing VI subsystem. 

412

Termination error. The following reason codes are associated with this abend:

201 Error terminating HS subsystem.
301 Error terminating VI subsystem. 

413

HIPERLOAD abends. 

414

HFS (High Performance FOCSORT I/O) abends.

HFS subsystem supports data base and FOCSORT I/O in non-hiper environment. The following reason codes are associated with this abend:

001 Invalid address of FSBLK on call to HFSOPEN.
002 Invalid address of FSBLK on call to HFSGET.
003 Invalid address of FSBLK on call to HFSPUT.
004 Invalid address of FSBLK on call to HFSCLOS.
005 Invalid address of FSBLK on call to HFSSIZE. 

494

Installation error. Called from HLIFOS if there is a problem with the size of LINREC and DATREC, or with FILCTL and BASCM. 

550

MASPAR:

001 Unable to obtain MasParm.
002 Unable to find MASPAR mailbox.
003 MasStack is full. 

589

FXCMEM (OLD)/OMMEM invalid condition.

501 - FXCINT: Fixed Core Subpool (FXCMEM DLL) init failed.
507 - FXCINT: Fixed Core Trace Initialization failed.
513 - FXCSBP: no more subpools available.
514 - FXCSBP: requested subpool already exists.
519 - FXCSBP: FXCMEM has not been initialized.
521 - FXCGET: improper Element size.
522 - FXCGET: invalid subpool name.
523 - FXCGET: no more subpools available.
524 - FXCGET: no more blocks available.
525 - FXCGET: insufficient core.
529 - FXCGET: FXCMEM has not been initialized.
531 - FXCFRE: Invalid subpool name.
532 - FXCFRE: Element was not obtained by FXCGET.
533 - FXCFRE: Element was already freed.
539 - FXCFRE: FXCMEM has not been initialized.
541 - FXCCLO: Invalid subpool name.
549 - FXCCLO: FXCMEM has not been initialized. 

590

FXCMEM (NEW) VARIOUS INVALID CONDITIONS

0 /* Out of memory */
1 /* Unable to initialize*/
2 /* Was not initialized */
3 /* Subpool exists alrdy*/
4 /* No more free subpls */
5 /* Cant create same sub*/
6 /* Pool not found */
7 /* Can not destroy pool*/
8 /* Invalid free request*/
9 /* Unable to create SP */
10 /* Invalid fxcfree req */
11 /* Too big len fxcall*/
12 /* Memory overly(CHECK)*/
13 /* Invalid length free*/
14 /* Internal block corpt*/ 

591

MALLOC/FREE/REALLOC/FRECOR problems. The following reason codes are associated with this abend:

1 - Attempt to malloc size <= 0.
2 - FREE noticed that 'MLLC' eyecatcher was trashed.
3 - Bad return code after FRECOR during FREE.
4 - Attempt to free ADDR=0 (currently not used).
5 - Attempt to free 0 bytes (subpool freemain).
6 - Failed fxcsbp call from Igetcor
7 - Failed fxcget call from Igetcor
8 - Failed fxcfre call from Ifrecor 

592

ODINMEM for CICS: FREE noticed that 'MLLC' eye catcher was trashed. 

600

A group of EDA abend codes. The following reason codes are associated with this abend:

0 - SSCTL was unable to issue IDENTIFY for MSFIND.
1 - SSCTL is abending (R2 will contain the original abend code).
2 - SSCTL was unable to GETMAIN storage for EDAPRINT
3 - SSCTL was unable to start all initial servers - insufficient storage. 

601

A group of the iWay subsystem abend codes. The following reason codes are associated with this abend:

0 - Invalid MSOCBMAN request (FREE request issued when the
slot is empty).
1 - Internal error in the IDEB chaining logic or in the KEY handling
logic.
2 - SSZPOST error (unable to obtain subsystem table).
3 - Invalid request code for MSOCBMAN. 

602

A group of IODDN - related abend codes. The following reason codes are associated with this abend:

0 - PUTREC was issued against a DDNAME, allocated to a library (not to a member). Open process was stopped as it could damage the data set.
1 - PUTREC was issued against a library member but DCB parameters are not compatible with the library.
2 - Internal error at GETMEMFR.
3 - Internal error: GFCB block not found.
4 - GETMEMGM was unable to get a new chunk of memory.
5 - PUTREC was issued against a library member with a RECFM=VB. However, LRECL is not less than BLKSIZE-4.
6 - ERRGET INVALID FIOBLK
7 - ERRGET GETCOR ERROR
8 - ERRGET FRECOR ERROR
9 - ERRGET FRECOR ERROR
10 - ERRCLOS FRECOR ERROR
11 - Internal error: number in concatenation reported by BLDL is bigger than number of concatenated data sets
100 - Number of opened ddnames/members exceeded the maximum (Max values: 380 ddnames, 5000 members) 

603

SASC 'L$CB' routine was called. R3 probably contains the length of memcpy/memset. R14 contains the return address. 

604

SSFIND was called under Open Edition. It is prohibited. 

609

FOCMAIN VM has had a CRITICAL error.

1 Cannot find FOCMAIN SCBLOCK environment
2 SCBWKWRD in SCBLOCK is zero 

610

GET2000 IBIPAGE validation failed 

611

GET2000 IBIPAGE validation failed 

612

GETNSS Error detected

1 - Overlay at end of segment
2 - Overlay of last call
3 - Length zero or negative
4 - Insufficient space in nss 

613 - 634

available for cms Obtain 

635

FRECOR/FRECRS Reason code = CMS RC 

636

FRECRN Reason code = CMS RC 

637

FRE2000 Reason code = CMS RC 

638

FRE2000 SVC Reason code = CMS RC 

639 - 659

available for cms release 

666

Abend Services: See Reason code for Abend code. 

700

Unable to find LIBENV SECT. 

701

Attempted to allocate 2nd stack frame in LIBSTKA. 

702

Couldn't find static stack in LIBENVF. 

703

RDA code on CMS attempted to call hermes, which is not yet a DLL. 

704

SETLOCK failed from MAKENV MACRO. 

705

Unable to get main C run-time environment blocks. 

706

FREEMAIN of C Runtime Environment failed. 

707

Unable to allocate control blocks for SAS/C Runtime Environment. 

708

SAS/C Runtime Environment not initialized. (No STACK). 

709

In GETCOR storage FREEMAIN/RELEASE failed. Reason code = CMS RC. 

710

STDPRLG GETMAIN failed. Reason code = R15. 

711

STDPRLG FREEMAIN failed. Reason code = R15. 

712

VXINIT cannot load FSASLIB Module. 

713

SAS/C Stack overflow. 

714

A COLD restart of FOCUS was attempted, but storage was not available. 

715

VXINIT: cannot load FSASLIB module. 

716

SAS/C Runtime Environment cannot locate FOCDIR Module. 

717

VXINIT: cannot load FSASLIB module. 

718

SAS/C Runtime Environment cannot locate FSASLIB Module. 

719

VXSTUB: SAS/C Stack overflow from IMPORT macro 

720

MVS/HLI SAS/C Runtime Environment not initialized. 

721

Attempt to create new ACVT mailbox failed because no more
available. 

722

EMGOUT (in EMGSRV) called with no output function available. 

723

VXFMOD: cannot load FOCDIR Module. 

724

EMGINIT could not get main an area for its control block. 

725

VXSTUB: Unable to load requested DLL Module (VXSTUB/VXDLL). 

726

VXDINT: cannot find FOCDIR Module. 

727

VXINIT: cannot load FOCDIR Module. 

728

VXFMOD: internal error in FOCDIR Module. 

729

VXFDIR cannot load FOCDIR Module. 

730

VXFMOD cannot load FOCDIR Module. 

731

VXFTEST: internal error in FOCDIR Module. 

732

VXSTUB: Stub code and DLLDIR do not match. 

733

VXSTUB: Stub code and Module's XPXPXPXP do not match. 

734

VXSTUB: Weak EXTRN is zero. See R2-R3 for DLL name and
R4-R5 for module name. Module is NOT resolved. 

735

VXSTUB: SAS/C Source Debugging Environment has not been
initialized or a module has an incorrect entry point. 

736

VXSTUB: attempt to load focus module is rejected 

737

CICS runtime problems, system not configured properly. 

738

VXEXIT: error in VXEXIT usage reason 1 - init error; 2 - vxexit called before init. 

739

EDA bridge failed. Reason code = R15. 

740 - 743

IMPORT MACRO: SAS/C stack overflow IMPORT macro 

745

IMPORT MACRO: Weak EXTRN is zero. See R2-R3 for DLL name. 

746

VXFDEL: internal error in FOCDIR Module. R4-R5 for module name. Module is NOT resolved 

749

VXFMOD: Table FULL 

750

Unable to find FOCDIR Address for an HRMxx Exit. 

752

Unable to find FXCMEM Control Blocks for an HRMxx Exit. 

755

Unable to GETMAIN SAS/C HRMxx Exit Runtime environment blocks. 

756

FREEMAIN of SAS/C HRMxx Exit Runtime Environment failed. 

757

FOCAPI1 internal error: could not find requested function name in FOCAPI table. 

760

RDAPASO could not getmain a savearea. 

776

Too many recursive call levels to IODDN. 

777

FSXAIO called with unsupported macro code. 

778

LEVEL5 called L5CHAIN with unknown module name. 

779

Too many files open simultaneously. Focus error 32200 in IODDN. 

789

Problem in FOCECB.ASSEMBLE. 

795

Master-file parse internal error; the reason codes are described in REASON CODES795, currently on FOCDOC disk (FOCLIB 192). 

796

Internal error in one of the following areas of code: Compile MODIFY; DEFINE FUNCTION; SET command processing; MORE/FORECAST. The reason codes are described in REASON CODES796, currently on FOCDOC disk (FOCLIB 192). 

797

LET internal error. The reason codes are described in REASON CODES797, currently on FOCDOC disk (FOCLIB 192). 

798

BY TOTAL internal error. The reason codes are described in REASON CODES798, currently on FOCDOC disk (FOCLIB 192). 

799

Pooled Tables internal error. The reason codes are described in REASON CODES799, currently on FOCDOC disk (FOCLIB 192). 

800

Abend from DRDA Gateway or its DDF interface. On VM ABEND 800 will come from HLI code. A reason code should will also be presented. REASON codes are documented in IUCEQU MACRO. 

801

Error in sink machine ENQ on database (called from HLIQDQ). 

802

Error in L$CB* SAS/C routine. The routine was called from the iWay code while it was not expected to be called at all.

1 - L$CBMCP
2 - L$CBMCM
3 - L$CBMST

Note: When the length for memset exceeds X'FFFFFF'--which almost certainly indicates a bug--SAS/C code invokes XCMEM.L$CBMST (via BALR 1,1). --One occasion on which this can easily occur is free(ptr), where the length word (just before ptr) has been overlaid with garbage. When IBI$FCFC is allocated, just prior to freeing the storage an attempt is made to set the memory to X'FDFD...' 4 - L$CBMCL 5 - L$CBMML. 

806

FSROOT module not found either in FOCLIB or in STEP/JOB/LINKLIB. 

807

A module symbol table in FOCUS in out of synch with the corresponding one in a reentrant module. 

808

EDA only. A dynamic allocation of a required file failed at startup. DDnames are identified by the reason code:

1 - offline
2 - focsort 

809

809 Abend in 64-character name services.

001 - Not enough memory

002 - PDS is not RECFM=F

003 - Not enough temporary nam1s (more than 9999999)

004 - Not enough short names for PDS (more than 999999)

005 - Table ssftbl not found (for MSO only)

006 - Setting "LONGSYNM=ON" is absent (for MSO only) INTERNAL ABENDS for 64-character name services:

007 - Bad temporary name.

008 - Table of short names is broken.

009 - Table of long names is broken.

010 - Table of short & long names in lnddname structure. is broken.

011 - We can't find dd in the chain dd-names.

012 - Internal error in lnswap subr. (LNSWAP table is bad).

013 - Internal error in errdrxll subroutine 

810

Bad return from PDSSHR (64-character name services)

04 - DD is not allocated

08 - Data set is not the library

0C - I/O error reading directories

10 - Not enough memory

14 - Unable to open library

18 - Too many directory blocks

1C - Library structure error 

811

Bad return from LNREADP (64-character name services)

04 - Unable to open PDS

08 - PDS is not RECFM=F[B] && LRECL=80

0C - Member not found 

812

Independent Path Testing internal errors

01 - Delete Path

02 - Get Path

03 - Store Path 

817

Core initialization for server failed. 

818

Call to HRSET or HROPEN from server failed. The reason code for this abend is the 3-part HERMES error code as documented in HRERR DOC file on the same disk. 

819

Call to HRON from server failed. The reason code for this abend is the
3-part HERMES error code as documented in HRERR DOC file on the same disk. 

820

Call to HRGEVT from server failed. The reason code for this abend is the 3-part HERMES error code as documented in HRERR DOC file on the same disk. 

821

Core failure during initialization of TS-table. 

822

Error during the construction of TS-table. 

823

The lk system initialization for server failed. 

824

An lkrst or lkid failed, which should never happen. 

825

FOCUS cannot be loaded, FOCLOIN fails. Probably ran out of memory. 

826

External security structures invalid. Unable to check authority. 

850

BDEXIT was called during server processing. Check temporary data set allocations for space. 

851

Internal error during cross-task communications within the server address space. 

876

Server terminated due to use of feature inappropriate to this configuration. 

877

Call to OXSS subsystem failed. Subsystem not open either because it was never opened, or because it has been closed. Likely causes are that either a logic error occurred in a higher layer, or the subsystem was closed by ESTAE and a lower recovery routine was retried. Reason code indicates an abend routine based on Odin Function call numbers:

6 - send

7 - receive

9 - get event 

880

TFXCGET function called from one of the Hermes modules completed unsuccessfully - most likely because the program ran out of memory. 

888

Maintain:

Reason Code 1 - Message recipient called from C returned a failure condition. (negative rc).

Reason Code 2 - Message recipient called from Maintain returned a failure condition (negative rc).

Reason Code 3 - Failure in the execution of some quad.

Reason Code 4 - Maintain interpreter detected an attempt to jump to an invalid quad address (<0). 

900

Internal abend to tell MSO not to restart AUTOSTART=YES (HRPGATE) or abend Attach Manager in CMS.

For CS/2 Reason Codes:

901 - Load of service module failed.

Other reason codes correspond to Hermes errors.

For CS/3 Reason Codes:

A0DD0000 -Attach Mgr configuration file error, or ATM table could not be allocated (in CMS).

A0DD0001 -Failure during CS/3 Open call.

A0DD0002 -No listen was successful on any node.

A0DD0003 -Severe error during execution (for example, cancel VTAM) (these used to be xDEAD reason codes). 

909

Communications subsystem (ODIN/HERMES) abend:

Reason codes by subsystem:

ODIN MSO ATTACH MANAGER (OPSINIT):

A0DD9999 - atm pointers to priv serv information do not match previously FEEDBEEF reason code).

ODIN LU0 (OMLU0):00DD9999 - Error in MSOENDf sanity check failed.

01DD0xxx - Error in LOGONX in OMLU0A, xxx is return code FFF - no session parameters.

02DD0xxx - Error in TERMX, (not implemented).

03DD0xxx - Error in receive exit, xxx is return code from VTAM RECEIVE submitting receive or from SysAddMulti or hxAddQueue, or

103 - No session parameters, or

109 - Error allocating RPL.

04DD0xxx - Error in SCIPX in OMLU0A, xxx is return code FFF - no session parameters D0C - Error in InheritSes call to VTMINRPL failed.

00DD9FEE - Error in CompleteConnect, call to LU0FRBND in OMLU0A failed.

1Fxxxxxx - Receive exit, VTAM CLSDST failure.

22xxxxxx - Receive exit, VTAM SENDing positive response failure.

A1xxxxxx - Receive exit, VTAM CHECK RPL macroinstruction failure. 

909

ODIN LU2 (OMLU2):

20DD0007 - Erroneous level 1 call to subsystem - not supported

20DD0009 - ODINSYS/SYSGETENV could not find LU2 NODE block.

2DDDDDDD - Failure to shutdown lu2 subsystem

ODIN WEB (OMWEB):

B0DD0007 - Erroneous level 1 call to subsystem - not supported

B0F00004 - Failure reading parm block from mailbox in PostEvent 

909

ODIN LU62 (OMLU62):

60DD0007 - Erroneous level 1 call to subsystem - not supported (in CPIC).

60DD9999 - Error in MSOENDf sanity check failed

D0A - Error RplAlloc RPL allocation failed

D0C - Error RplAlloc RPL initialization failed

63DD0xxx - Error in receive exit, where xxx is:

    F02 - Unable to submit receive

65DD0xxx - Error in attention exit, where xxx is:

    F01 - ODIN could not create a session

    F02 - Unable to submit receive

    FFE - Unable to receive FMH5

66DD9FEE - Error in freerpl exit, actsess failed

6F000003 - Failure locating lu62 protocol block in Wait (CPIC)

xxxxyyyy - Failure activating session APPCCMD ACTSESS

R0=xxxx,R15=yyyy 

909

ODIN TCP (OMSOCK,OMTCP):

C0DD9999 - Error in MSOENDf sanity check failed

C0DD0007 - Erroneous level 1 call to subsystem - not supported

C0EDA010 - takesocket error

C0EDA020 - givesocket error

CF000003 - Failure reading protocol parms from mailbox in Wait

xxxxxxxx - Errors in OMITCP SRCV or it_que, xxxxxxxx=rc 

909

HERMES LU0 (HRM0):

DEAD0xxx - Error in scip exit, where xxx is:

3E7 - unable to allocate event block or queue element

FFF - CommSes could not be found/allocated

DEAD1xxx - Error in logon exit, where xxx is:

3E7 - unable to allocate event block or queue element

FFF - CommSes could not be found/allocated

DEAD3xxx - Error in receive exit, where xxx is

FFF - CommSes could not be found.

DEAD4xxx - Private task (under MSO) cannot end.

1Fxxxxxx - Receive exit, cldst failure

22xxxxxx - Receive exit, xposr failure

23xxxxxx - Receive exit, srecv failure

A1xxxxxx - Receive exit, check failure 

909

HERMES LU62 (HRM62):

DEAD3xxx - Error in receive exit, where xxx is:

3E7 - unable to allocate event block or queue element

BAs - State mismatch in subsys. s = state

BBs - State mismatch in hermes. s = state

BD1 - Sanity check on parms failed

DEAD5xxx - Error in attention exit, where xxx is:

3E7 - unable to allocate event block or queue element

FFF - CommSes could not be ound/allocated

DEAD8xxx - Error in receive, connect event processed by mistake

DEAD9FEE - Error in freerpl exit, actsess failed 

909

HERMES Interlink TCP/IP (HRMITCP)

0Axxxxxx - Error in logon exit

0Dxxxxxx - Error in receive exit, where xxxxxx is:

FFFFFF - Sanity check on tpl failed. 

910

Hermes/Odin Switch / H2O / SCHERMES failure. The following reason codes are associated with this abend:

0000BADC Old HERMES entry point used in H2O.

zBAD00xx Failure in hermes routine, where:

    z: 0 Sanity failure with HermesId.
    1 Unexpected empty mailbox.
    2 Unsupported routine in HERMES(HOSWTCH).
    3 Unsupported routine in SCHERMES.

    xx: 01 HRCLOS.
    02 HRON.
    03 HRSET.
    04 HRCNCT.
    05 HRDISC.
    06 HRSEND.
    07 HRGEVT.
    08 HRUSWD.
    09 HRFREE.
    10 HRGETC.
    11 HRFREC.
    12 HRGTID.
    13 HRGTSI.
    14 HRADPT.
    15 HRXACT.
    16 HRIDNT.
    17 HRUNID.
    18 HRCFG.
    19 HRQPK.
    20 HRPTID.
    21 ADD_UC_E.
    22 ADD_IE_E.
    23 FIND_COM. 

911

H2O out of sessions; Max Session limit reached. 

928

ODIN Event Handler failure: Reason code as follows:

EDA01001 - System Anchor block not found when expected

EDA01002 - No more events available

EDA01003 - Event specified for deletion was not found 

929

ODIN Memory failure: Reason codes as follows:

1001xxxx - OMMEM initialization failed

101wxxxx - OMMEM subpool creation error

102wxxxx - OMMEM subpool configuration error

201wxxxx - OMMEM subpool close error

3000FFFF - OMMEM memory requested too large

3001xxxx - OMMEM get memory error

4001xxxx - OMMEM free memory error 

999

Error linking rent and non-rent parts of the module. Most likely the parts do not match. For 7.0 and up, there are abend reason codes; odd numbers for RNTMAN and even numbers for FOCVFLIS:

1- non-rent table not linked in;
3- bad format of non-rent table;
5- unable to load the rent part of the module;
7- bad format of the rent table;
2- either RNTMAN routine or rent CSECT not linked in;
4- name or date/time of non-rent and rent CSECTs don't match;
8- 3-byte address constant found (Assembler only), not supported.
R8 and R9 contain the name of the routine that caused the error. 

1004

A COMMIT request caused the server or service to abend. 

1006

The ROLLBACK request caused the sync database to fail. 

1007

The COMMIT request failed. 

1010

General error code. See EDAPRINT for details. 

1020

General OMTERP error code. Abend codes are:

0 - SUCCESS (EXIT called from script)

1 - OPENLOG ERROR

2 - DUPLICATE DEFINES

3 - TOO MANY TOKENS

4 - SCRIPT TOO LONG

5 - INVALID LINE TYPE

6 - PARSER ERROR

7 - OPEN SCRIPT ERROR

8 - OPEN INCLUDE ERROR

9 - INCLUDE READ ERROR

10 - MEMORY ALLOCATION ERROR 

1050

Generic XMI server error. IGET/IPUT Sequence error. resulting from an attempt to execute two IGETS without intervening IPUT. 

1051

Generic XMI server error. IGET data length exceeds maximum buffer length. 

1052

Generic XMI server error. IPUT data length exceeds maximum buffer length. 

1406

MVC routine was called with DESTRUCTIVE parameters. Calling sequence error (calls to MVC, MVCX, MVCXA) 

1964

Hiperbudget internal error. Hiperbudget subsystem was called with a negative value that exceeds current hiperbudget usage. 

1965

IBISNAP internal abend; unable to continue. 

1992

The most common cause for this abend is a tso non-HiperFOCUS session after HiperFOCUS. The abend may also be caused by a mismatch between TRACKIO=OFF/ON in the same run, or TRACKIO=OF for FOCUS and TRACKEIO=ON for sink. 

1993

Issued from errdrxl when IBISYS00 has a recursively defined DDName, or when there are more than 20 alternates for a DDName in IBISYS00. 

1996

Experimental abend in new version of AXHTMM. This abend is issued when a mailbox is found corrupted. 

1997

This abend is issued when iWay software detects a CPU that is not authorized to execute iWay software. 

2000

Bad parameter list. 

2001

Attach of FNCHK failed. 

2002

FNCHK ended abnormally. 

2003

Program name unknown to FOCNET. 

2004

OPEN (FOCLIB) failed. 

2005

Attach of FNSTRT failed. 

2006

WAIT on FNSTRT initialization error. 

2007

FOCNET ended abnormally. 

2008

FNSTRT ended abnormally. 

2009

FNCHK ended abnormally. 

2010

OPEN(IMSLIB) failed. 

2011

VTAM HALT was issued. 

2100

Native S390 define compiler abend

reason=0 RIDSECT in CMPVEC ASSEMBLE out of sync with structure. 

4001

Cross-memory post failed in IOPEN 

4091

The next sequential instruction is a branch; it should happen only within SVCTEST, and is an SVCTEST problem if it occurs. This abend can also occur in the FOCUS SVC itself. One common cause of this abend is that the FOCUS SVC is linked as AMODE=24, when it should be linked as AMODE=31. Use SVCTEST to see what AMODE the SVC contains. 

SFxx

A system abend of Fxx (where 'xx' is the SVC number of the FOCUS SVC, given in hex):

1) If no reason code is given, the SVC probably was not installed. SVCTEST should be run to verify this.

2) The following reason codes may accompany this system abend, if it is issued by the SVC itself:

    0 - unable to establish FESTAE (user modified our SVC)

    1 - non-FOCUS caller of the SVC detected (*)

    2 - invalid storage key specified for instruction (*)

    3 - SVC was asked to execute a bad SVC number (*)

    4 - attempt to "EX" another "EX" (*)

    5 - options of called SVC are not allowed (*)

    6 - specification exception during MVCL (*)

    7 - fetch or storage exception reading SVC parm list (*)

    8 - opcode to invoke is not allowed (*)

    9 - attempt to move data abend with an S0C4 (*)

    10 - fetch violation on source operand (*)

    11 - store violation on target operand (*)

    12 - STIDP failed with a specification exception

    13 - tried to alter R14 or R15 inside SVC (*)

    14 - bad storage key for GETMAIN or FREEMAIN (*)

All reason codes marked with (*) indicate a high potential that the abend occurred due to an outside invasion of the SVC. These codes may, however, be due to a FOCUS problem as well; check circumstances of the abend.

iWay Software