Make your own free website on Tripod.com

TOPICS.html

SYSTEM CODE

EXPLANATION

S000

Could mean that no IMS segments were selected by DLI call.

Look for status code of GE and check your SSA qualifications.

S001

Probably incorrect DCB information.

  • Checking RECORDING MODE and BLOCK CONTAINS clauses in

COBOL FD as compared with RECFM of JCL.

  • Check LRECL and BLKSIZE of JCL as compared with the number of characters in the 01 level(s) under the FD in the program.
  • Check for correct tape mounted.
  • The current release of COBOL II takes its recording mode from the 01 items below the FD in determining fixed or variable and maximum record length.
  • Trying to open a dataset that is cataloged but never has been opened or closed.

S002

Same as S001

S013

Same as S001

S02A

Sometimes happens in changeman for no apparent reason. It usually is no problem. Just press enter. Worst case, sign off changeman or tso and back on; problem gone.

S03B

· Check DCB info – information must be identical when using a file in more than one place

· Cannot dummy a VSAM file?

S04E

· Forgot to prime the pump with an initial FETCH (read) before trying to insert or replace using the cursor values (DB2)

· If DBUTIL abends set UTPROC = ‘RESTART’ when restarting job.

· DB2 jobs that abend with S04E usually means DB2 table was migrated and job issued recall and then abended waiting for HSM. Check reason code and DB2 sysprint for added information.

Eg. Dataset Names :

prod : NW40DB2P.DSNDBD.XXXXXX.YYYYYY.IXXX.AXXX

test : NW20DB2T.DSNDBD.XXXXXX.YYYYYY.IXXX.AXXX

test : NW20DB2T.DSNDBC.XXXXXX.YYYYYY.IXXX.AXXX

 

XXXXXX and YYYYYY are often in the sysprint information.

S04E

THIS HAPPENS WHEN A DB2 JOB ABENDS USING A UTILITY ID AND THE UTILITY ID HAS NOT BEEN CLEANED UP YET. GO INTO OPTION N.D.7 DISPLAY UTILITY IDS PENDING AND THEN TERM THE PENDING UTILID’S RELATED TO YOUR USER ID.

=N.D.7

DISPLAY UTILID’S 1 === > - DIS UTITILITY(*)

TERM UTILID’S 1 === > - TERM UTITILITY(TSTGML01.STEP20)

SOC1

· Program ID not right

· Probably a call to an unlinked module; ABEND at location 2, 4 or 6 usually.

· Can be the result of a call to ‘ABENDX’

· Sometimes caused by a read or write to an unopened file ABEND at location 48 or 4800 or 52 or 5200

· In each case, check register 14 for program error location

SOC4

· May be caused by bad subscripting or indexing

· More short record from input buffer; check for BUFL option in JCL DCB field.

· More parms in called module than in calling module

· Directory block full will cause SOC4 in module init routines.

· In TSO dialog – full profile, change call to use diff profile.

· SOC4 – 11 can be bad index on a VSAM file. Repro file to check.

· Can also be using incorrect PSB for database if segments are changed recently.

· "UNABLE TO OPEN D????X01" means you are using an update PSB and the database is allocated online.

· Mixed RES/NORES job – can cause other abends - often SOC4.

· ABEND in IGZ … module of link can be incompatible subroutines. Include IGZCPCO IGZENRI IGZENRT and ILBOSRV in the start of your link. Could also cause SOC6 or SOC1.

· Last data set of a concatenation empty.

· COBOL sort cannot concatenate disk and tape (JCL sort can )

· NOMAD read past end of file

· May need to execute DBAU03P instead of DBAU03T

· READY TRACE used in a module that is linked to a COBOL II module.

· Also make sure ‘if’ verbs end with ‘end-if’

SOC5

Same causes as OC4

SOC6

Same causes as OC1. ( May be executing an old version of the program. )

SOC7

Check for bad data – maybe defined as COMP, COMP-3 or incorrect location. Could also be bad subscripting.

SOCB

Divisor is zero

S106

· If register 15 contains a ‘C’, not enough core was available

· If register 15 contains an ‘F’, look for the message FETCH FAILED FOR MODULE XXXXXXXX RETURN CODE XX. If you find this message resubmit the job – if you still get a ‘F’ check your input data sets.

· Fixed by overriding the REGION size in DBTSTQLD JCL

S122

Job cancelled by operator with dump

S213

· Data set not found – check spelling of dsn

· Check vol-ser parameter.

· Check if data set has been scratched.

· Check VSAM vs Sequential in select statement of COBOL program If 213-70 and are printing a member in a PDSE you can’t be in edit mode for that member.

S222

Job cancelled by operator without dump

S237

Abend at end of volume. If input tape, check end of output and if ok, ignore abend

S2F3

System crashed while running your program. Also gives a

Jcl error msg. Resubmit job

S30A

Add DCB=nnnn, to your JCL

S322

· Time out on a job. Check the class the job is running in. See TSO JOBCLASS for what types of jobs run in which classes

· Check for valid DSN or valid DISP

· USER=888, REASON=0000000 Try increasing region size, usually when IKJEFT01 utility

 

S4EC

If you have specified more than one volume in the JCL VOL=SER parm, remove all but one

S497

A program called the common abend module GPXCDABN and the error message is displayed. This reusable abend module allows more detailed messages up to 300 bytes

S522

Interactive session timed out

S706

Program not found:

· Check link to see program(s) were included

· Check link name

S722

OUTLIM maximum has been reached

S737

Missing or empty data set in a concatenation

S806

· Program not found :

  • Check program name being executed
  • Check JOBLIB or STEPLIB card
  • Check executive compiled DYNAM. Link to other modules via a link job will NOT resolve called modules.

· Dynamic environment :

  • Is a module compiled as DYNAM?
  • Is DYNAM LIB in the execute JCL?
  • If call to other than PROGRAM-ID, you need to LINK step of translate / link of called module change the SYSLIN to add a line ALIAS called-entry. ( A space ahead of ALIAS ).

· Has occurred when VSAM files dummied out.

S813

The tape VOL-SER number does not match the tape DSN. Either the tape VOL-SER number is wrong, the G000V00 is wrong, or the tape DSN is incorrect

S913

· If need access to data file, obtain RACF authority.

· If position 8 of a test DSN = P RACF thinks it is a production dataset

S923

DB2 is up but SAS job has something locked up.

S929

DLI - check for missing or misspelled PSB name

U929

PSB not found. Check your PSB lib or PSB spelling

9XX-12

BLP tapes must have USER=TSPRX7

S9EC

BLP tapes must have USER=TSPRX7

SA78

Cancelled / timed-out in middle of sort. Check other message / dump

SB37

Not enough space on output file – increase SPACE parameter on file named in console messages section of your output

SB78

Accessing the same database another job is currently using. Rerun after the other job completes.

SC03

This is believed to be MIXRES error problem. The executable module needs to have the following modules added to the beginning of its LINKMOD set :

- INCLUDE SYSLIB (ICZCPCO) *MODULES TO HELP RESOLVE

- INCLUDE SYSLIB(IGZENRI) * mixres error for the 3.0

- INCLUDE SYSLIB(IGZENRT) * rel of VS COBOL II

- INCLUDE SYSLIB(ILBOSRV) * these were pulled from LINKMOD

GRPL206A

SD37

Not enough space on output file – increase SPACE parameter on file named in console messages section of your output. For file expansions, reduce the size of the parm.

SE37

Not enough space on output file – increase SPACE parameter on file named in console messages section of your output.

U0003

· Usually a call to a non-existent program

· TMS volume number does not contain DSN

· Tried to access data set but missing - check console messages

· Call to abend – check displays on SYSOUT data set

U0016

· Usually abend on sort. Check sort message area for reason for bad sort. If insufficient core, increase REGION size, or if executing a ‘SORTD’ add a DYNALLOC and FILSZ as in this example :

//SYSIN DD *

SORT FIELDS=(438,12,CH,A), DYNALLOC=(SWORK,6),FILSZ=E10000

If still abend, try deleting the FILSZ=Ennnn part of the above card.

Sort cannot handle spanned records on sortout. See JR’s memo located in NW20GRPT.EBS.GTOOLKIT.ABEND.CNTL(M901126).

U0020-08

Means that the D????P01 file has zero space available. You need to do an unload reload with more space allocated.

U0039

If this is a batch DLI job with a return code of 20, try changing the job name and resubmitting – i.e., change TSxxx80A to TSxxx80. Or run IMS backout step or on rare situation change IRLM.

U0041

If this is a batch DLI job with a return code of 20, try changing the job name and resubmitting- i.e., change TXxxx80A to TSxxx80.

U0047

Try changing from production DLI database to test and/or change to exec DBAU03T. or change IRLM=N

Set //STEPLIB DD blanks with the number of lines = the number of steplib DD’s in the proc.

U0048

?? Invalid parm card or pds file being brought into the program

U0403

If occurs during a DATAVANTAGE load of a database – correct by deleting the data portion of the database and reallocating that data portion.

U203

Same as S0CB

U0259

IMS compile with DATA(31)

U295

Look for unopened file that your program is trying to use or file being opened twice

U0476

Means your PSB does not match your COBOL ENTRY statement. Make sure the databases are in the same sequence in both & recompile.

YOU FORGOT TO PUT ‘Y’ IN THE CBLTDLI PARAMETER ON THE CHGMAN COMPILE OPTIONS FIELD!

You may have the wrong linkset for ims program

You may need to have procedure division using instead of entry DLITCBL.

U504

Check for too large of a block size.

U514

Check for missing GOBACK, especially within an entry point.

U0595

IMS get core failure – must call ‘DLITCBL’ before call ‘CBLTDLI’

U826

Happened when the key length and record length were incorrect in the initialize database index step.

U850

Pointer problem – reload from backup file.

U852

Your DBD stuff is not appropriate for the database !!\

Maybe looking for incorrect segment layouts and like that.

U853

Happened when the DRATEP01 DSN was different than DRATEX01 DSN.

U0868

Means something is wrong with your test database. Make a new database and try again.

U1002

Check for ‘block contain 0 records’ missing in FD. Record length does not agree with the copy member in the FD.

- If are working with a production program and you are dummy-ing out the file include the following in your JCL:

//*

//VSAMFILE DD DUMMY,AMP=AMORG

//QSAMFILE DD DUMMY,DCB=BLKSIZE=18

//

  • If are opening a dataset that has a card – as output :

//cardin dd *

- Could possibly indicate syntax error.

U1010

New COBOL calling old COBOL with DISPLAYs or READY TRACE. Job will process and put out DISPLAYs; however, upon completion or call to COBOL2 module it will abend with a 1010.

U1020

  • User logic error – see console message section for clue
  • Call ‘DLITCBL’ entry from IMS in middle of perform
  • Check for extraneous generated SYSIN DD statements
  • Read past end of file ?
  • Trying to close a file that is not open
  • The VSAM file is allocated online and must be de-allocated first (Use TZDA or TQDA to de-allocate the file online)

U1033

- Look at +IGZ033I error message. Attempt to call an AMODE(24) ‘callpgm’ … passing 16 meg. Recompile program with DATA(24) instead of DATA(31). Rerun job. You may need to set DATA(24) in the link step.

U1034

Same as SB37

U1044

Old cobol calling new cobol

U1035

VSAM LRECL does not match your COBOL record layout – 4 bytes.

DD statement missing.

Inconsistent between FD, 01, and/or JCL

COBOL II treats your recording mode line as comments and sets mode based on the 01’s under the FD.

U2658

Happened when using IDCAMS instead of UTYPAMS DB load.

U3003

VSAM return code 97 on open.

U3040

DGS6421 … Param exceeds max allowable length

IRLM param or one of the other ims parameters may be incorrect.

U3057

Check your DB2 stuff that is called from IMS.

Make sure you have DDOTV02 DD and MBR=DSNMTV01. Check your DDITV02 data

U4092

Build buffer error – increase region size

U4094

  • De-allocate file from online or make sure file is VSAM
  • Empty VSAM file

X900

File used by GLK0G3CM in security checking received a error on read. Check for file(s) closed.

1nnn

VSAM abend when ‘nnn’ is the feedback code in decimal-SHOWCB

2nnn

VSAM abend when ‘nnn’ is the feedback code in decimal-MODCB

3nnn

VSAM abend when ‘nnn’ is the feedback code in decimal-GENCB

IECTMS3

IMS needs oper VOL-SER-NO reply of input tape specified as BLP that is exactly equal to VOL=SER=…. Specified in JCL.

IEC141 013-20

Sequential dataset open. Error is either :

  1. BLKSIZE is not a multiple of LRECL
  2. LRECL = 0 when RECFM = FB or FBS,
  3. BLKSIZE is not 4 bytes greater than LRECL when RECFM = V

IGZnnnI

See appl program debugging guide no. SC26-4049

DFSnnnI

See IMS/VS messages and codes no. SC26-4174.

DFHnnnn

See CICS messages and codes no. SC33-0514.

DVDnnnn

See SDF/CICS messages and codes no. SH19-8107.

DVRTnnnn

See DXT messages and codes no. SC26-4091.

ADR****

See --- messages and codes no. SC26-4390.

DSN****

See --- messages and codes no. SC26-4379.